Systems Integration

EGN 5623 Enterprise Systems
(Professional MSEM)
Fall, 2011

ERP & APO Integration

Theories & Concepts

EGN 5623 Enterprise Systems Optimization
(Professional MSEM)
Fall, 2011
Outline of ERP & APO Integration
1. Core interface (CIF)
• CIF Overview
• CIF Configuration
2. Integration models for data transfer
• Object and data transfer
• Initial and delta transfer
3. Master data integration
4. Transactional data integration

Integration of ERP & APO via CIF
Controls data transfer
between ERP and SCM
SCM 5.0
Master Data Transactional Data
Forecast based on
data from BW
Supply Network
&Load Building
Aggregates data from
varous sources
Data from
flat file


Base Scenario

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, 5.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 ECC dataset to SAP SCM.

Technically, the transfer is performed via the queued remote
function calls (qRFC).
Core Interface (CIF) (Review)
APO Core Interface
• Data transfer between the ECC and SCM systems is
defined and controlled using the APO Core Interface

• CIF is the central interface that connects SAP SCM to the
existing SAP ECC system environment. It is available to
the ECC systems through a plug-in.

• In the APO Core Interface you select the objects that you
want to transfer to SCM via “integration models.”
APO Core Interface
Only the planning-relevant parameters from the complex
dataset of SAP ECC are transferred to SAP SCM.

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)
The relevant master data for production planning:

•PPM and PDS
•Quota arrangement,
•Set up Group & matrix, and
•Interchangeability 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
Master Data Transferring
Transactional Data for
CIF Configuration

The communication between ERP and APO systems is
based on queued remote function calls (qRFC).

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
and APO 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.
Objects of Integration Models
Two types of objects:
• Material dependent
o such as orders
• Material independent
o 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
Master Data Objects in SAP APO
and SAP ERP (review)
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.

Decision for Object Transfer
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

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
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

From APO to ERP, the default setting for the transfer is
“immediately’ for PP/DS order and “periodically” for SNP
Dependencies for sequencing
Integration Models

Systems Integration

SAP Implementation

EGN 5623 Enterprise Systems Optimization
(Professional MSEM)
Fall, 2011

Transactions for System Connection
Create Integration Model in ERP
Activate/Deactivate Integration
Model in ERP
Confirm Data Transfer in APO
Transactions and Reports for Data
Transfer from ERP to APO

HW 6:
Module 10: Supply Network Planning (SNP) - (Section 3)
10.1 Supply Chain Modeling
10.1.1 Supply Chain
10.1.2 Master Data in Supply Chain
10.1.3 APO Core Interface (CIF)
10.1.4 Active Model and Version 000
10.1.5 Supply Chain Engineer
10.2 Global Bike Company Supply Chain
10.3 Transactional Data used in Supply Chain
10.4 Planning Table
10.5 Supply Network Planning Heuristic
10.5.1 SNP Heuristic
10.5.2 Interactive SNP Planning
10.5.3 Selection Profile
10.5.4 Review Forecast Values for Production
10.5.5 Planning at Plant level

Additional HW:

1. Use Graphic method to solve LP a problem
1) Draw a graph
2) Plot the constraint function
3) Outline the feasible solution
4) Circle the optimal solution point.

2. Solve a transportation LP problem
1) Define the objective.
2) Define the decision variables.
3) Write the mathematical function for the objective.
4) Write the constraints.
5) Solve the LP problem (for extra credit).