Select language:
Entering content frame!--a11y-->

Function documentation CIF Customizing in SAP APO 


CIF Customizing in SAP APO is used to set up the system infrastructure and to configure the data transfer between SAP Advanced Planning and Optimization (SAP APO) and the ERP system via SAP APO Core Interface (CIF). CIF Customizing also covers application-specific settings and enhancements for CIF.

An Implementation Guide (IMG) is available for CIF Customizing. The IMG provides you with a clear overview and explanation of all steps that are necessary for integration via CIF. With the exception of organizational IMG activities that only contain a description, you can go directly to the relevant transaction and execute the action.


In addition to the Customizing settings in SAP APO, you must also make the necessary Customizing settings in the ERP system. For more information, see CIF Customizing in the ERP System.


The Implementation Guide for CIF consists of three main areas:

·  Basic Settings for Creating the System Landscape

Here you can find all the IMG activities that are necessary for the partner systems to be able to communicate with each other using CIF (for example, naming the logical systems, naming RFC destinations, and making qRFC settings).

·  Basic Settings for the Data Transfer

Here you can find all the IMG activities that are necessary for the data transfer itself and for monitoring the transfer, for example, settings for publishing the planning results from SAP APO, CIF error handling, and the CIF comparison/reconciliation of transaction data.

·  Application-Specific Settings and Enhancements

Here can you find customer exists, Business Add-Ins (BAdIs), and settings for individual applications such as for stocks, for sales scheduling agreements, or for in-house production.


  1.  You call the IMG in SAP SCM. In the SAP Reference IMG, choose Integration with SAP Components ® Integration via APO Core Interface (CIF).

  2.  You make the relevant settings.

Note that some of the basic settings are target-system-dependent or client-specific. These settings are not transported from the Customizing client to the productive client. This means you also have to make the settings in the productive client.


Leaving content frame