cif documentation.pdf

8/11/2019 CIF Documentation.pdf

http://slidepdf.com/reader/full/cif-documentationpdf 1/8

1. CIF Documentation

The data is exchanged between the ECC and APO systems through of standard interface called

CIF (Core Interface) that is included in the SAP ECC Plug-In.

A RFC connection (Remote Function Call) connects the SAP ECC System and APO System. The

system transfers the data selected in the CIF via this connection.

The Master data and Transactional data that must be transferred from ECC to APO system are

determined in the CIF, which is responsible to control this transfer. The CIF is a real-time

interface that works through Integration Models generated in SAP ECC system. Integration

Models contain all data to be transferred from SAP ECC to SAP APO (Material, Plants, Sales

Orders, Inventory).

The transfer of data via CIF is done asynchronously through qRFC – queued Remote Function

Call and it could be configured with Outbound or Inbound queue methods.

2. CIF Configuration

The next steps were based on scenario in the MGS System landscape. Pay attention with the

nomenclature about your landscape.

2.1 ECC System

A) Create an user for ALE communication (Tcode: SU01);



E.g.: ECCREMOTE (SAP Note 727839 - Authorization role for the SAP SCM - SAP R/3

integration).

Generally we create an user with communication or service type with SAP_ALL authorization

copy less than securities roles.

B) Define the APO and ECC logical systems (BD54);

E.g.: <SID>CLNT<MDT>

C) Assign the ECC logical system to a client (SCC4);

D) Specify SAP SCM release (NDV2);

E.g.: APOCLNT100 with System Type = SAP_APO and Release = 701

E) Set RFC destination for the CIF communication usage (SM59);

Always use the RFC destination with the APO logical system name to becomes more easy to

administrate.

Obs: Insert into /ect/hosts files in both servers (ECC & APO) the IP Addresses and the hostnames

about CIF servers to be known by SM59.

E.g.: <SID>CLNT<MDT> = APOCLNT100



F) Set target system and queue type (CFC1);

G) Set user parameters (CFC2);

H) Define filter and selection block size (CFC3);

Apply values using the following SAP Notes:

Note 436527 - CFC3 - Block Size Recommentations

Note 1508632 - CIF: Timeout during initial transfer for batches

Note 1654328 - CIF SLS: Small LUWs with select size param. of initial load

K) Determine number ranges for parallelization (CFC8);

https://service.sap.com/sap/support/notes/436527











L) Define the Changes to CIF Master Data (CFC9).

Define the filters to use the option Matl ChangeTtans = 2 (BTE Transfer, Immediately).

M) Maintain QOUT Scheduler for APO & ECC Systems (SMQS);



N) Maintain QIN Scheduler for queue name = CF*(SMQR);

2.2 SCM System

A) Create an user for ALE communication (Tcode: SU01);

E.g.: SCMREMOTE (SAP Note 727839 - Authorization role for the SAP SCM - SAP R/3

integration).

Generally we create an user with communication or service type with SAP_ALL authorization

copy less than securities roles.

B) Define the APO and ECC logical systems (BD54);

E.g.: <SID>CLNT<MDT>

C) Assign the APO logical system to a client (SCC4);

D) Create BSG -Business System Group (/SAPAPO/C1);

E) Assign logical systems to BSG - Business System Group (/SAPAPO/C2);



E.g.:

APO System

BusSystGrp = BSG I

Logical System = <SID>CLNT<MDT>

SAP Ind. = " "

Release = 70

Queue Type = Inbound Queues

Err. Hndlg = Postprocessing

ECC System

BusSystGrp = BSG I

Logical System = <SID>CLNT<MDT>

SAP Ind. = X

Release = 600

Queue Type = Inbound Queues

Err. Hndlg = Postprocessing

F) Maintain distribution definitions for some publications types(/SAPAPO/CP1);

G) Define User parameters for CIF Users (/SAPAPO/C4);

E.g.: Generally in User column we set for "*" that will be used for all users in the system.



H) Maintain QOUT Scheduler for APO & ECC Systems (SMQS);

I) Maintain QIN Scheduler for queue name = CF*(SMQR);

cif documentation.pdf

Documents