Interfaces - Core Interface (CIF) and BAPIs

Purpose
The purpose of this page is to explain the Core Interface (CIF) functionality,
basic functions, related transactions, notes and documents, as well as BAPI
resources and explanations.
Overview
CIF is the standard interface between ERP (R/3 or ECC) and SCM APO, used to
transfer Master Data and Transactional Data. While Master Data transfer is
unidirectional, transaction data is bi-directional.
Initial CIF settings
CIF Settings in R/3

CIF Settings in APO

Check ALE settings or activate

ALE settings

Check ALE settings or activate

ALE settings

Define the logical system BD54

Define the logical system BD54

Assign logical system to a client

SCC4

Assign logical system to a client

SCC4

Set the RFC destination SM59

Set the RFC destination SM59

Assign target system and queue

type CFC1

Set up business system group

Maintain the SAP APO release

NDV2 (Refer Did you know)

Create BSG /SAPAPO/C1

Activate BTEs for SAP APO

integration BF11

Assign logical systems to BSG

/SAPAPO/C2 (Refer Did you know)

User parameters for CIF CFC2

(Refer Did you know)

Maintain distribution definitions

/SAPAPO/CP1

User parameters for CIF

/SAPAPO/C4

Did you know... how customizing will affect the CIF behavior
ECC side
NDV2 :
Target System Type: If you are using an SCM-EWM system or an SCM-SNC
system, you must not maintain SAP_APO in this field. During integration
system will call different function modules based on the target system type.
An SCM APO function module may not exist in a EWM or SNC system at all.
Calling a wrong function module can result in a dump termination. Note
1543842 also discusses it.

Release: Usually new functionalities are provided in higher releases which are
not available in lower ones. This field is especially important if you want to
use such new functionalities. Don't forget to update the entry here when
you're upgrading your APO system.
Release: Usually new functionalities are provided in higher releases only and
not available in lower ones. Sending data from new functionalities to lower
releases may have unexpected result. So this field is especially important if
you want to use such new functionalities. Here are some examples:
1. In FM CIF_PO_SEND, after CALL FUNCTION 'NDI_SYSTEM_RELEASE' there
are different handlings dependent upon the release of target APO system. In
higher releases like EhP 6, there are even specific check to see if the target
APO system is higher than 701, otherwise the data is not sent.
[IF (cl_ops_switch_check=>lo_mm_sd_sfws_dm_sc( ) EQ cl_ops_switch_check
=>switch_active_true ). "DRS switch active?
IF NOT lv_aporel GE '701'. "Direct shipment orders are available from SCM
7.0 EHP 1]
2. In Source code of LCUSLNTRTOSHI, there is special handling of
"overlapping functionality for APO releases equal and higher than 5.0
release.
LOOP AT lt_cif_planact ASSIGNING <ls_activity>.
... and restored for each new activity
lt_arbid_kapid = lt_arbid_kapid_tmp.
IF gv_aporel >= '50'
Remark: If your ECC is lower that 6.0 release, there is a further check on
variable gv_scm50 which can be activated by method ACTIVATE_PDS_2005 of
BAdI CUSLNTRTO_ADDIN. See Note 1147234 .
Don't forget to update the entry here when you're upgrading your APO
system. Cant find entries like 701 and 702? See Note 1608792. Pay attention
to the format of the entry- 701 instead of 7.01 or 7.1.
R/3 (ECC) system is below 600 and you cant find the APO release 5.1 (SCM
2007)? This is however, correct. See Note 1223963.
For relevant information, see SAP note 1398474
CFC2:
We recommend using copy as function when you need to create an entry
for your own user to debug, etc.
There was a case in which the Q in field RFC Mode was omitted by accident
so that the specific user can transfer nothing to APO.
APO Side

/SAPAPO/C2:
Field Release You may wonder why for an ECC system you cant find the
entries like 602, 603 and so on, please refer to note 1550348.
Cant find the APO entries like 700, refer to note 1236044.

Important CIF-related transactions

R/3:
Transac
tion
code

Description

APO:
Transact
ion code

CFM1

Create integration
model

/
SAPAPO
/C3

View CIF application

log

CFM2

Activate/deactivate
integration models

/
SAPAPO
/C4

Setting of user
parameters CIF

CFG1

View CIF application

log

/
SAPAPO
/C5

Send planning results

to R/3

/
SAPAPO
/C1

Create business
system group

/
SAPAPO
/C2

Assign logical
systems to a business
system group

/
SAPAPO
/CQ

SCM Queue Manager

/
SAPAPO
/CCR

Comparison/reconcili
ation tool

SMQ1/S
MQ2

qRFC monitor incl.

functions start, stop,
execute

CFC2

User parameters for

CIF

CFC3

Block sizes for initial

transfer

CFM5

Filter object search in

integration models

CFC1

Define logical systems

as APO systems

NDV2

SMQ1/
SMQ2

Setting of release level

of APO systems
qRFC monitor incl.
functions start, stop,
execute

Description

SM59

Definition of RFC
destinations

SALE

Definition of logical
systems

SM59

Definition of RFC
destinations

CFC7

Assignment of Log.
System and CIF App.
of RFC Dest.

SALE

Definition of logical
systems

/
SAPAPO

CIF Postprocessing

Transact
ion code
/CPP

Description