cif baseline config

8/18/2019 CIF Baseline Config

1/13

CIF Settings in R/3

1. Check ALE settings and activate, as required: T.Code: SALE

· Define the logical system BD54 - To enable the transfer of data via APO Core Interface (CIF), you

need to name both the ERP system in which you are working and the SAP APO system to

which you want to transfer data as logical systems.

· Assign logical system to a client SCC4 - In the SAP System the client corresponds to a logicalsystem. Therefore in ERP system we need to assign ERP client to the ERP logical system.

Similary, in SAP APO we need to assign SAP APO client to the SAP APO logical system.

SCM 5.1 Logical System

Name

R/3 Logical

System


2/13


3/13

SCM 5.1 Logical

System Name

SCM 5.1 IP

Address


4/13

3. Maintain the SAP APO release NDV2

4. Assign target system and queue type CFC1 - In this IMG activity, you add the target system thatyou have already defined to the definition of the RFC destination for the transfer. The data transferusing the APO Core Interface is made with queued remote function call (qRFC) technology. Thismeans that the data is stored temporarily in queues. The queue type (inbound or outbound)determines whether the queues processing is controlled by the receiving or sending system.In this step, you can set the queue type for the target system specified.

The system chooses outbound queues by default.

SCM 5.1 Logon

settings


5/13

5. User parameters for CIF CFC2 - In this IMG activity, you can make user-specific entries for thefollowing parameters:

· RFC mode (activate/deactivate transfer on a user-specific ba

· Logging (configure application log on a user-specific basis)

· Debug (activate/deactivate debugging on a user-specific basis)

Requirements

The settings for setting up the system landscape must already have been made.

Activities

1. Enter the user name specified in the user master.

2. Use input help to make the relevant settings for this user.


6/13

CIF Settings in APO

1. Check ALE settings and activate, as required: T.Code: SALE

· Define the logical system BD54 - To enable the transfer of data via APO Core Interface (CIF),

you need to name both the ERP system in which you are working and the SAP APO system to

which you want to transfer data as logical systems.

· Assign logical system to a client SCC4 - In the SAP System the client corresponds to a logicalsystem. Therefore in APO system we need to assign APO client to the APO logical system.

Similary, in SAP R/3 we need to assign SAP R/3 client to the SAP R/3 logical system.

SCM 5.1 Logical System

Name

R/3 Logical

System


7/13

2. Set Up the RFC destination SM59 - In this IMG activity, you create the connection to SAP R/3. Thename of the RFC destination has to match exactly the name of the logical target system thatwas already specified.

APO Logical

System Name


8/13

R/3 Logical

System Name

R/3 IP Address


9/13

3. Create BSG /SAPAPO/C1 -

4. Assign logical systems to BSG and queue type /SAPAPO/C2 - In this IMG activity, you assign alogical system to a business system group. Additionally, you assign a queue type (inbound queue oroutbound queue) to the BSG. The queue type (inbound or outbound) determines whether thequeues processing is controlled by the receiving or sending system . In this step, you can setthe queue type for the target system specified.

The system chooses outbound queues by default.

Proceed as follows:

· Field BusSystGrp: Enter the name of a valid business system group.

· Field LogSystem: Enter the name of the logical system that has been maintained for the current

client (source system SAP R/3).

· Description field: The system automatically copies the name of the BSG.

· Field R/3 flag : Set an indicator to define SAP R/3 as the source system.

· Field SAP Rel: Specify your valid SAP R/3 Release.

· Field Queue Type: Choose between outbound and inbound queues.


10/13

5. User parameters for CIF /SAPAPO/C4 - In this IMG activity, you can make user-specific entries forthe following parameters:

· Logging (configure application log on a user-specific basis)

· Debugging (activate/deactivate debugging on a user-specific basis)

· Recording (control event recording, that is, the publication of planning results)

Requirements

The settings for setting up the system landscape must already have been made.

Activities1. Enter the user name as specified in the user master.

2. Use the field and input help to make the relevant settings for this user.

6. Maintain distribution definitions /SAPAPO/CP1 - You use this IMG activity to define the distributionof the SAP APO planning results to the relevant logical systems. If you do not define a distributiondefinition, the system does not transfer any data.

Activities

You define the target system for the combination Publishing Type/Location.

· Select the publishing type.

· Specify a location.

· Specify the logical system to which the data is to be transferred.

· Save your entries.

A distribution definition is only required for the following object types if the objects are new:

· External procurement

· Schedule line for scheduling agreement item

·

In-house production· Production campaign

· Sales order

· Reservations

You can assign different distribution destinations for different locations to an object type.


11/13

7. Activate Change pointer and BTE for automatic update of transaction data in R/3 T.Code BD61


12/13

T.Code BD50 – Check all CIF* entries

T.Code CFC9 – Change Target system independent settings in CIF


13/13

T.Code BF11 – Turn on below two plug-ins for BTE

cif baseline config

Documents