CIF Configuration

7/27/2019 CIF Configuration

http://slidepdf.com/reader/full/cif-configuration 1/25

CIF configuration

Version: 1.0 draftFile: CIF_configuration.doc

Role Name Date SignatureReviewed By Sign for correctness and

completenessAuthor Rudy Claassen 20/12/2000



1. Document management

1.1. Ascendant link informationTitle CIF configurationOwner Rudy ClaassenTeam BuildID Integration of APO and R/3 (Document library -> Other documents -> Binder -> Phase 4:

Detailed Design – Other documents (non-deliverables) -> Documentation

1.2. Change historyDate Details Author Version

23/11/2000 First draft Rudy Claassen 1.0

Author : Rudy ClaassenStatus : ConceptProject name : STAR Chain

File name : 165505217.docLatest save date : 11/12/2002



1.3. Table of contents1. Document management......................................................................................................................................2

1.1. Ascendant link information.....................................................................................................2

1.2. Change history..........................................................................................................................2

1.3. Table of contents.......................................................................................................................3

2. Introduction........................................................................................................................................................4

3. R/3 – Application Link Enabling (ALE)............................................................................................................4

4. R/3 – Remote Function Call (RFC)...................................................................................................................8

5. R/3 – CIF Target System..................................................................................................................................10

6. R/3 – CIF APO Release Level..........................................................................................................................11

............................................................................................................................................................................. ..117. APO – Logical System......................................................................................................................................12

8. APO – Assign Logical System..........................................................................................................................13

9. APO – Business System Group........................................................................................................................15

10. APO – Assign Logical Systems to Business System Group..........................................................................16

11. APO – Maintain Global Parameters..............................................................................................................17

12. R/3 – Maintain CIF Global Parameters........................................................................................................18

13. R/3 – Change Pointer Number Range...........................................................................................................19

14. R/3 – Activate Change pointer for message types ........................................................................................20

15. R/3 – Activate Change Pointers.....................................................................................................................21

16. R/3 – Maintain fields for message type..........................................................................................................22

17. APO – Maintain Number Range for Change Pointers.................................................................................23

18. APO – Activate Change Pointers...................................................................................................................24

19. APO – Activate Change Pointers Generally..................................................................................................25





2. IntroductionThe following illustrates the required activities to set up the CIF application between an R/3 system and the

APO system. This assumes that the relevant system software patches have been applied and that the networkinglayer is in place between machines.

There is a checklist of tasks in the APO documentation: APO Integration Scenarios > Integration of APOand R/3 > Setting Up the System Infrastructure > Checklist for Setting Up the System .In summary the tasks are:R/3 – define/ check ALER/3 – define/check RFC connectionR/3 – define/check CIF Target SystemR/3 – define/check CIF Release LevelAPO – define/check Business System groupAPO – define/check Logical SystemAPO – define/check Customer modifications (if required).

3. R/3 – Application Link Enabling (ALE)

ALE needs to be set up to allow SAP systems to communicate.To identify a SAP system a ‘logical name’ must be given to it. This must be unique for each system.This is done in the IMG using Define Logical System . Access via transaction SALE or

R/3 IMG > Cross-Application Components > Distribution (ALE) > Basic Settings > Define Logical System . For Heineken Starchain the name of the logical system consists of a combination of the machine name and theclient number, separated by ‘_’ (underscore). For example, client 080 on machine D25 will get logical systemname ‘D25_080’.





To link the internal SAP system id (‘client’) to its logical name use Allocate Logical System to Client .





In the details screen the Logical System name is assigned.





4. R/3 – Remote Function Call (RFC)

A connection must be defined between the R/3 system and the APO system.This is done in the IMG using Define RFC Destination . Access via transaction SM59 , or a menu option fromtransaction CIF or R/3 IMG > Cross-Application Components > Distribution (ALE) > Communication >

Define RFC Destination .





The R/3 connection is given a ‘logical name’ (preferably the logical system name of the destination). Then thecharacteristics are defined including the type of connection, the target machine (network address of APO box)and the sign on used. For security reasons the sign on user is a CPIC user called CIFREMOTE .





5. R/3 – CIF Target System

The CIF application must be told what RFC connection to use. The system will determine the operation mode(T = transaction events).

This is done using Maintain Target System . This can be accessed via transaction CFC1 or via a menu optionfrom the transaction CIF.





6. R/3 – CIF APO Release Level

To be able to control the downward compatibility of the APO Core Interface, the APO release level has to bemaintained in the CIF settings in R/3.

This can be accessed via transaction NDV2 or via a menu option from transaction CIF.

Once the R/3 side has been set up, the APO side needs configuring.





7. APO – Logical System

As in R/3, the APO system must be given a logical name. Note that the R/3 system is also defined.

APO IMG > R/3 Basis Customising > Application Link Enabling (ALE) > Sending and Receiving Systems > Logical Systems > Define Logical System.





8. APO – Assign Logical System

As in R/3, the system must be assigned to a client.

APO IMG > R/3 Basis Customising > Application Link Enabling (ALE) > Sending and Receiving Systems > Logical Systems > Assign Client to Logical System.





9. APO – Business System Group

As APO may be linked to more than one system, a ‘logical’ group must be set up to which systems may beassigned.

Use Maintain Business System Group. Access via transaction /SAPAPO/C1 or APO IMG > Advanced Planner and Optimizer (APO) >Basis Settings > Integration > Business System Group> Maintain Business System Group.





10. APO – Assign Logical Systems to Business System Group

Both the APO system and the R/3 system/s must be assigned to the Business System Group (BSG).More than one BSG is possible if there are R/3 systems with conflicting number ranges / coding (within a BSG,codes for Master Data are the same for the same item).One R/3 system is marked as the ‘master’ source of configuration data.The APO system must be in the same BSG as the ‘master system’, because this ensures correct sequencing of data changes.The Update mode is by Queued RFC (data is transmitted in sequence via a queue).

Use Assign Logical System . Access via transaction /SAPAPO/C2 or APO IMG > Advanced Planner and Optimizer (APO) >Basis Settings > Integration > Business System Group> Assign Logical System.





11. APO – Maintain Global Parameters

Per single user or for any user (‘*’), global parameters for the CIF can be defined. The parameters include‘Logging’, ‘Debugging’ and ‘Recording’.

Access via transaction /SAPAPO/C4.





12. R/3 – Maintain CIF Global Parameters

Allows control of APO data fed into R/3 and is related to the similar table in APO.‘D’ = directly loaded, ‘P’ = periodically.Access from CIF menu or transaction CFC2





13. R/3 – Change Pointer Number RangeChange pointers are used by the ALE message distribution. Changes to Master Data are recorded and given a

change number (if they are in an active message type).

Transaction BDCP IMG > Cross-Application Components > Distribution (ALE) > Basic Settings > Number Ranges > Maintain Number Range for Change Pointers





14. R/3 – Activate Change pointer for message typesCIF Message types must be activated for change recording.

Transaction BD50 IMG > Cross-Application Components > Distribution (ALE) > Set Up Data Distribution > Master Data Distribution >Activating Change Pointers for Message Types





15. R/3 – Activate Change Pointers

This activates change pointer recording.

Transaction BD61 IMG > Cross-Application Components > Distribution (ALE) > Set Up Data Distribution > Master Data Distribution >Activating Change Pointers (generally)





16. R/3 – Maintain fields for message type

The fields relevant to a message type can be viewed.Transaction BD52

APO has a similar mechanism for Change Distribution .





17. APO – Maintain Number Range for Change Pointers

Transaction BDCP APO IMG > R/3 Basis Customizing > Application Link Enabling (ALE) > Modelling and Implementing Business Processes > Master Data Distribution > Replication of Modified Data > Maintain Number Ranges for Change Pointers





18. APO – Activate Change Pointers

Transaction BD50 APO IMG > R/3 Basis Customizing > Application Link Enabling (ALE) > Modelling and Implementing Business Processes > Master Data Distribution > Replication of Modified Data > Activate Change Pointers for Message Types





19. APO – Activate Change Pointers Generally

Transaction BD61

APO IMG > R/3 Basis Customizing > Application Link Enabling (ALE) > Modelling and Implementing Business Processes > Master Data Distribution > Replication of Modified Data > Activate Change Pointers -Generally

Author : Rudy ClaassenStatus : ConceptP j STAR Ch i


CIF Configuration

Documents

Transcript of CIF Configuration