Systems Integration EIN 5346 Logistics Engineering (MSEM, Professional) Fall, 2013

ERP & APO Integration Theories & Concepts

Outline of ERP & APO Integration Core interface (CIF) CIF Overview CIF Configuration Integration models for data transfer Object and data transfer Initial and delta transfer Master data integration Transactional data integration

Integration of ERP & APO via CIF (Review) Alternative Scenario Base Scenario 7.0

CIF Overview Core interface (CIF) is the central interface that connects SAP SCM to the existing SAP ECC system environment. Data transfer between the ECC and SCM systems is defined and controlled using the Core Interface (CIF). CIF is an integrated part of the ERP system (in SAP ECC 6.0) and also is an integrated part of SAP APO, 7.0.

CIF Overview CIF enables transferring master data from SAP ERP to SAP APO in one way only, and transferring transactional data in both ways between ERP and APO In the Core Interface, the user selects the objects to be transferred to SCM via the “integration models.” Only the planning-required parameters are transferred from the SAP ERP dataset to SAP SCM. Technically, the transfer is performed via the queued remote function calls (qRFC).

Core Interface (CIF) (Review)

APO Core Interface The APO Core Interface is used for both initial data transfer (initial transfer) and change transfer (transfer of data changes) to SCM.

Master Data (review) Resource views: The relevant master data for production planning: Location Product Resources PPM and PDS Quota arrangement, Set up Group & matrix, and Interchangeable group. Resource views: SNP and PP/DS require a different view of the capacity. SNP – in time buckets PP/DS – time-continuous capacity

Master Data Object PDS

Master Data Transferring Work station Production Version PDS

Transactional Data for Transferring

CIF Configuration To enable this communication, the user needs to configure the “Application Link Enabling” (ALE) settings and the parameters for communication (see Figure 25.1) The user needs to define the logical systems for both ERP (NAPCLTN550) and APO (CDFCLNT550) systems

CIF Configuration

CIF Configuration In the ERP system, the APO logical system has to be defined as the target system by assigning the system type and release with transaction code NDV2 and the queue type with the transaction code CFC1. The remote function calls (RFC) destination defines the address of the target system and the access data (user for the target system, password). The RFC destination has to have the same name as the logical system of the target system and that the name is case sensitive.

Integration Models for Data Transfer The integration model is used to specify selection criteria for master data objects and the logical name of the target (APO) system. The same integration model can be used to transfer more than one type of object but it is a good practice to use multiple integration models (one per object type) to avoid complex maintenance of the selection criteria. When ERP sends orders to APO, the integration models check whether the active integration model exists. Integration models are created (T-code CFM1) and activated (T-code CFM2) on the ERP side. Integration model can be deleted in ERP (T-code CFM7), but the integration model must be inactivated before deletion.

Objects of Integration Models Two types of objects: Material dependent such as orders Material independent such as resources and suppliers. Table 25.2 lists some of objects that can be included into integration models and transferred to APO.

Objects for Integration Models

Objects of Integration Models While creating the integration model, the objects which match the selection criteria, are read in and assigned to the model. The integration model is unique in its name, the target system, the application, and its version. The user can freely name the integration model and denotes its application. The target system is selected from the APO system that is defined in the CIF configuration.

Objects of Integration Model A new version is generated for the integration model, each time when the user modifies it. The user and the date of generation are part of the version name. The transfer of objects is sequence-dependent. For example, plants must be transferred prior to the transfer of work center. The transfer of data is triggered by activating the model with the transaction code, CFM2.

Initial and Delta Transfer Initial transfer During the initial transfer, CIF (the currently active version) transfers all objects to APO. Delta transfer If the new version is activated (while the older ones still remain active), CIF transfers only new objects (i.e., the objects that are not included in the old version). Usually a periodical delta transfer is used for data integration, to reduce the system load.

Initial and Delta Data Transfer

Master Data Integration Master data is usually one of the most crucial factors for the success of an implementation. Master data in ERP have to have a sufficient quality. Master data must be kept consistent between ERP and APO, otherwise planning will be inaccurate and lead to wrong results. Generally strongly recommend to maintain master data in ERP environment.

Master Data Integration The master data objects in SAP SCM are not identical to those in SAP ERP. During master data transfer, the relevant SAP ERP master data is mapped to the corresponding SAP SCM master data. The SAP ERP system is the owner of most of the master data. Only specific SCM master data (such as transport lanes) that does not exist in SAP ERP is maintained in SAP SCM.

Master Data Transfer Strategies BAdI: Business Add-In

Transactional Data Integration The transfer of transactional data is working two ways, from ERP to APO and from APO to ERP. From ERP to APO, there is usually one initial upload and from then onward a continuous online transfer of data changes. From APO to ERP, the default setting for the transfer is “immediately’ for PP/DS order and “periodically” for SNP orders. The data generated or changed by SAP APO in Supply Network Planning (SNP) or Production Planning and Detailed Scheduling (PP/DS) is transferred to SAP R/3. This operation is called the publication of planning results. There are two types or publication in SAP APO: Direct publication and periodic publication. You can choose between the two by using transaction /SAPAPO/C4

Dependencies for sequencing Integration Models

Systems Integration SAP Implementation

Transactions for System Connection Publication in SAP APO: For the transfer of transactional data from SAP APO to SAP ERP it is necessary to maintain the distribution definition per publication type (e.g. in-house production) and location to SAP ERP system.

Create Integration Model in ERP Publication in SAP APO: For the transfer of transactional data from SAP APO to SAP ERP it is necessary to maintain the distribution definition per publication type (e.g. in-house production) and location to SAP ERP system.

Activate/Deactivate Integration Model in ERP Publication in SAP APO: For the transfer of transactional data from SAP APO to SAP ERP it is necessary to maintain the distribution definition per publication type (e.g. in-house production) and location to SAP ERP system.

Confirm Data Transfer in APO Publication in SAP APO: For the transfer of transactional data from SAP APO to SAP ERP it is necessary to maintain the distribution definition per publication type (e.g. in-house production) and location to SAP ERP system.

Transactions and Reports for Data Transfer from ERP to APO

Exercises: (Due date: 12/14/1013) Planning with CTM Create requirement in APO-Production planning Plan network with CTM Check simulation for CTM Verify demand in CTM Execute evaluation with CTM Check CTM: results analysis Check CTM results in SNP Planning Board Check CTM: Supply Chain Viewer