7/27/2019 CIF Configuration http://slidepdf.com/reader/full/cif-configuration 1/25 CIF configuration Version: 1.0 draft File: CIF_configuration.doc Role Name Date Signature Reviewed By Sign for correctness and completeness Author Rudy Claassen 20/12/2000
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
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
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
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’.
Author : Rudy ClaassenStatus : ConceptProject name : STAR Chain
File name : 165505217.docLatest save date : 11/12/2002
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 .
Author : Rudy ClaassenStatus : ConceptProject name : STAR Chain
File name : 165505217.docLatest save date : 11/12/2002
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 .
Author : Rudy ClaassenStatus : ConceptProject name : STAR Chain
File name : 165505217.docLatest save date : 11/12/2002
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.
Author : Rudy ClaassenStatus : ConceptProject name : STAR Chain
File name : 165505217.docLatest save date : 11/12/2002
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.
Author : Rudy ClaassenStatus : ConceptProject name : STAR Chain
File name : 165505217.docLatest save date : 11/12/2002
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
Author : Rudy ClaassenStatus : ConceptProject name : STAR Chain
File name : 165505217.docLatest save date : 11/12/2002
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
Author : Rudy ClaassenStatus : ConceptProject name : STAR Chain
File name : 165505217.docLatest save date : 11/12/2002
Transaction BD61 IMG > Cross-Application Components > Distribution (ALE) > Set Up Data Distribution > Master Data Distribution >Activating Change Pointers (generally)
Author : Rudy ClaassenStatus : ConceptProject name : STAR Chain
File name : 165505217.docLatest save date : 11/12/2002
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
Author : Rudy ClaassenStatus : ConceptProject name : STAR Chain
File name : 165505217.docLatest save date : 11/12/2002
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
Author : Rudy ClaassenStatus : ConceptProject name : STAR Chain
File name : 165505217.docLatest save date : 11/12/2002
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
File name : 165505217.docLatest save date : 11/12/2002