The purpose of this page is to present the Frequently Asked Questions (FAQ) in the Core Interface (CIF) Area (SCM-APO-INT*).
Questions and Answers
List of Questions
What does CIF stands for?
CIF stands for Core Interface. It is the interface for data transfer between an ERP system (SAP R/3 or SAP ERP) and a connected SCM system, such as SAP Advanced Planning and Optimization (SAP APO) or SAP Supply Network Collaboration (SAP SNC).
The basis for the data transfer is the Integration Model on the ERP side.
How should I start on the Integration of the Systems?
The Integration is made by using Integration Models, which are packages of data to be transferred.
Examples of objects an Integration Model can contain:
- Material/Plant information
- Planned Orders and Production Orders
- Purchase Requisitions and Purchase Orders
- Sales Orders
You should generate Integration Models for all data you want to be present in the SCM system.
Depending on the volume of data, you might have to split your Integration Models.
How do I generate Integration Models?
- To start, go to transaction /CFM1 (report RIMODGEN) on the R/3 side.
- Select your logical system (maintained in /SM59 and in /CFC1).
- Name your Integration Model (e.g. "EMEA Data") and its Application (e.g "Sales Orders", "Prod. Orders").
- Select the data you want to send. Maintain additional information in the right panels (Material, Plant, etc.).
You might have to click the right arrow to expand specific panels for each option.
- Click Save. Models will be generated.
Please note that the Models are generated in a inactive mode. You have to activate the models to transfer the data.
How do I activate my Integration Models in foreground?
- Go through transaction /CFM2 (report RIMODACT) on the R/3 side.
- Enter your Integration Model data (Logical System and Model name is enough)
- Double click in the model you want to activate
- Click the red "X" icon. It will change to a green checkmark.
- Press "Start"
- Data will be transferred and Model will be active.
How do I activate my Integration Models in background?
- Go through transaction /CFM3 (report RIMODAC2) on the R/3 side.
- Enter your full Integration Model data (Model name, Logical System and Application)
- Choose the option "Activate Newest Version"
- In the Program Menu, select the option "Execute in Background (F9)".
- Data will be transferred and Model will be active.
You can also create a (periodic) job for this task in /SM36
My Material Master objects have changed. What do I do?
The objects already in an active Integration Model are automatically transferred to APO when changed in R/3 if you have activated the Immediate Transfer of Objects in the /CFC9 transaction. In this case the objects are immediately updated in APO.
My Transactional Data has changed. What do I do?
All transactional data that refers to a Material Master object that is in an active Integration Model is automatically transferred to the APO system.
I have created new data. Will this be transferred automatically to APO?
No. Your new data must be in an active Integration Model. For this, you will have to generate and activate your Integration Model again.
By generating the model again and by activating it, you will be able to transfer the objects that were changed or created since the last run.
Important! Note that the activation of the IM must be done in one step.
- Generate new IM (/CFM1)
- Enter RIMODACT (/CFM2). In the next screen, click on the red "X" of the first entry (just created).
- Hit save.
If you do this procedure in two steps (deactivate old model, save, activate new model, save), you will be doing an initial transfer one more time, which can lead to high volumes of data being transferred again.
How do I transfer all data again?
- Using the two-step Integration Model activation explained above or
- Running report RIMODINI
Can I schedule a job to update my Integration Models and transfer new data?
Yes, you can!
- Create a /CFM1 Variant
- Create a /CFM3 Variant
- In transaction /SM36, create a new job
- Add as step 1 the RIMODGEN execution
- Add as step 2 the RIMODAC2 execution
It's recommended that you also create a job for report RIMODDEL. There is no need create a variant to execute it. This job will clear the entries of the Inactive IMs in Table CIF_IMOD
Which operations of a routing or recipe in R/3 or ERP are transferred to APO PPMs?
When PPMs are created in APO from Receipes in R/3 only those phases containing non-zero machine times are brought over. Other phases having only labour (resource category 003) or machine time (resource category 001) = 0 does not come through.
What determines the validity period of a resource in liveCache?
CFC9 parameter in R/3 does not set the From/to validity date for Resources when Work Centres are CIFed from R/3 to APO. Actually that is set as per entry in table /SAPAPO/RESLCT - Length of Time Stream or Bucket Vector in liveCache.
What needs to be done to debug CIF related enhancements?
In order to debug CIF related user exits or other CIF queues, set the R/3 RFC user (e.g. STGUSER) to Dialog user and then set queues to Debugging On/Record T/QRFCs in the transaction CFC2 in R/3. This is for queues coming inbound to APO. For queues coming inbound to R/3 set the APO RFC user id (e.g. APSUSER)
How can transaction data be reconciled with APO from R/3 or ERP side?
Program RCIFORDT can be used to reconcile transaction data form R/3 side. Refer 733110 - as a long term solution implement this BADI on APO side
OSS Notes 627630, 804034 on R/3 side and with the BADI OSS note 800286 to be applied
Which table stores Change Pointers in ERP or R/3?
The table BDCPV is to store Change Pointers in both APO and R/3. Refer OSS Note 329110.
Which report can be used to clear Change Pointers in ERP or R/3?
Program RBDCPCLR can be used to clear change pointers from the Change Pointer table. The message type CIFSRC is for changes to Source of Supply (i.e. Purchasing Inforecords). The CIF Change Transfer program (CFP1) can fail due to a large number of records in the Change Pointer table. Other message types are CIFMAT for material, CIFVEN for Vendor Master, CIFCUS for Customer master.
What is Customer Consignment Stock and how is it transferred to APO?
Consignment stock at Customer is stock at customer premises but owned by the supplier. Prerequisite to have Consignment Stock at Customer is Customer as a Location and Product Master at that Customer Location. To transfer Customer Consignment Stock from ERP to APO both "Customer" and "Special Stock at Customer" should be part of an Integration Model during Initial Transfer. For Consignment Stock Batches "Storage Location Stock" object must be included in the Integration Model.
Reference: Note 409298
What is Vendor Consignment Stock and how is it transferred to APO?
Vendor Consignment stock is stock at the plant location and treated as normal storage location stock but owned by vendor. Vendor Consignment Stock is transferred from ERP to APO as part of "Storage Location Stock" Integration Model. However the Vendor must be part of an active Integration Model.
How is Stock information stored in APO?
Stock in SCM APO system (upto 4.1) consists of Stock Anchor stored in Database and Stock Item stored in liveCache. The liveCache Consistency Check (transaction /SAPAPO/OM17) carries out the consistency check between the APO Database and liveCache. It should be executed periodically to delete obsolete stock anchors from the database.
Reference: Note 492591
As of SCM 5.0 Stock information is stored in liveCache table /SAPAPO/STOCKANC.
Reference: Note 837744
What are the userexits for Integration of Stocks?
On R/3 side the userexit is enhancement CIFSTK01 while on APO side it is enhancement APOCF011. The source code in the userexit should be copied to the CIF Compare/Reconcile Report (Delta Report) BAdI (method RELEVANT_FOR_COMPARE_R3_STOCK of BAdI definition /SAPAPO/CIF_DELTA3) for correctness of the report.
Reference: Note 492591
How is Inspection Lots handled in APO?
From SCM 4.0 Inspection Lots are separate objects in APO retaining the end dates. Hence Inspection Lots quantities does not shows up as Stock in Quality Inspection.
How is Cross-company Stock In Transit handled in APO?
Cross-company Stock In Transit is determined dynamically in R/3 and hence not transferred to APO. In APO Stock In Transit at the receiving plant can be handled by transferring Inbound Shipping Notification or Goods Confirmations from R/3.