AP205 Master Data Integration

AP205

Master Data Integration

© SAP AG 2001

System R/3 Release 4.6C with Plug-in 2000_2 and APO Release 3.0A
Mai 2001
Material number 50041876

© SAP AG AP205 Preface-1

 Copyright

Copyright 2001 SAP AG. All rights reserved.

No part of this publication may be reproducedor transmitted in
any form or for any purpose without the express permission of
SAP AG. The information contained herein may be changed
without prior notice.

All rights reserved.

© SAP AG 2001

Trademarks:
Some software products marketed by SAP AG and its distributors contain proprietary software
components of other software vendors.
Microsoft®, WINDOWS®, NT®, EXCEL®, Word®, PowerPoint® and SQL Server® are registered
trademarks of Microsoft Corporation.
IBM®, DB2®, OS/2®, DB2/6000®, Parallel Sysplex®, MVS/ESA®, RS/6000®, AIX®, S/390®, AS/400®,
OS/390®, and OS/400® are registered trademarks of IBM Corporation.
ORACLE® is a registered trademark of ORACLE Corporation.
INFORMIX®-OnLine for SAP and INFORMIX® Dynamic ServerTM are registered trademarks of
Informix Software Incorporated.
UNIX®, X/Open®, OSF/1®, and Motif® are registered trademarks of the Open Group.
HTML, DHTML, XML, XHTML are trademarks or registered trademarks of W3C®, World Wide Web
Consortium, Massachusetts Institute of Technology.
JAVA® is a registered trademark of Sun Microsystems, Inc.
JAVASCRIPT® is a registered trademark of Sun Microsystems, Inc., used under license for technology
invented and implemented by Netscape.
SAP, SAP Logo, R/2, RIVA, R/3, ABAP, SAP ArchiveLink, SAP Business Workflow, WebFlow,
SAP EarlyWatch, BAPI, SAPPHIRE, Management Cockpit, [Link] Logo and [Link]
are trademarks or registered trademarks of SAP AG in Germany and in several other countries all over
the world. All other products mentioned are trademarks or registered trademarks of their respective
companies.

© SAP AG AP205 Preface-2

 SAP Advanced Planner and Optimizer (APO)

Level 2 Level 2 Level 3

SAP R/3 SAP APO SAP APO
AP210 5 days
LO050 5 days
Demand Planning
PP - Planning and
Execution for Discrete
and Repetitive AP215 3 days
Manufacturing AP010 2 days
Supply
SAP APO Overview Network Planning

AP205 2 days AP220 3 days

Integration Master Production Planning/
Data Detailed Scheduling

AP230 2 days
LO060 5 days
Global ATP
PP-PI BC555 2 days
Process Manufacturing
liveCache
Administration

© SAP AG 2001

© SAP AG AP205 Preface-3

 Course Prerequisites

Required Prerequisite

AP010 - SAP APO Overview

Recommended

LO050 PP - Manufacturing Planning &

Execution for Discrete & Repetitive
else
LO060 PP-PI Process Manufacturing

© SAP AG 2001

© SAP AG AP205 Preface-4

 Target Group

Participants:
Members of the project team responsible for
master data integration between APO systems
and an OLTP system.

Duration: 2 days

© SAP AG 2001

Notes to the user

The training materials are not teach-yourself programs. They complement the course instructor's
explanations. On the sheets, there is space for you to write down additional information.
There may not be sufficient time during the course to carry out all the exercises. The exercises consist
of additional examples that are dealt with during the course. The participants can use these examples to
further their understanding after the course.

© SAP AG AP205 Preface-5

 Course Overview

Contents:

Course Goals
Course Objectives
Course Content
Course Overview Diagram
Main Business Scenario
Overview of Integration of R/3 Systems with APO

© SAP AG 2001

© SAP AG AP205 Preface-6

 Course Goals

This course will prepare you to:

Gain a basic understanding of the integration of
the APO System with an R/3 System (or external
system)
Transfer master data from the R/3 System to the
APO System and to set up your system to transfer
transaction data between the systems.

© SAP AG 2001

© SAP AG AP205 Preface-7

 Course Objectives

At the conclusion of this course, you will be able to:

Describe the architecture of integration of ERP

systems with the APO System
Select master and transaction data to transfer
from R/3 into APO
Specify where in the APO System it may be
necessary to add to the master data transferred
from the R/3
Describe the monitoring and the
compare/reconcile functions used to ensure data
consistency in R/3 and APO

© SAP AG 2001

ERP System stands for Enterprise Resource Planning System. The R/3 System is an example of an
ERP System.

© SAP AG AP205 Preface-8

 Course Content

Preface

Unit 1 Course Overview Unit 5 Models and Planning

Version*
Unit 2 Architecture of Integration
Unit 6 Transfer of
Unit 3 Transfer of Master Data Transaction Data
Unit 4 APO Master Data Unit 7 Monitoring/Error
Handling*
Unit 8 Conclusion

Appendix

* These units contain more information and cannot be discussed in great

detail due to lack of time in the course.

© SAP AG 2001

© SAP AG AP205 Preface-9

 Overview Diagram (1)

11 Overview 1
2 Architecture of Integration

3 Transfer of Master Data

4 APO Master Data

5 Models and Planning

Versions

6 Transfer of Transaction Data

7 Monitoring/Error Handling

8 Conclusion

© SAP AG 2001

© SAP AG AP205 Preface-10

 Main Business Scenario

The Precision Pump Company has been in the

market since 1971 and offers a large number of
high-tech standard pumps. In the product catalog
you will find turbomolecular, centrifugal, rotary and
membrane pumps (that can be used for
manufacturing ultra-high vacuums, for example).

© SAP AG 2001

© SAP AG AP205 Preface-11

 Advantages of Production Planning in APO

Detailed scheduling with simultaneous quantities and capacity

planning (PP/DS)
Exact material requirements planning (in hours and minutes), for
dependent requirements too
Multilevel material and capacity availability check (ATP)
for sales orders
Multilevel forward scheduling of a sales order (pegging)
Optimization algorithm within the limits of detailed scheduling
(minimizing setup times, setup costs, date delays, alternative
selection of resources, ...)
Dynamic exception messages (alerts)
Capacity categories: Time, service, volume, piece

© SAP AG 2001

© SAP AG AP205 Preface-12

 APO Integration (1)

R/3 -> APO APO -> R/3

Master data Transaction data Planning results

Plants, vendors, customers Sales orders Manufacturing orders

Materials Planned/production orders Order proposals
Work centers (capacities) Purchase orders Result of availability
Routings and bills of Supplies check
material ... ...
...

APO
R/3 R/3
4.6C 3.1I
BW
© SAP AG 2001

As a rule, the SAP-APO System is used in connection with other components of the SAP System or
with non SAP Systems. There are two different integration concepts:
Linkage with non R/3 Systems: The required interfaces are implemented as BAPIs (Business
Application Programming Interfaces).
Linkage with R/3 Systems (one or more): The required interface is marked as an APO Core Interface
(CIF). A mutual system connection has been set up in Customizing to enable the system to transfer
data relevant for the planning processes, from the execution R/3 System into APO, and also to return
the planning results from APO into the R/3.
The main tasks of the APO Core Interface include:
Determining the source and target system in complex system environments
Providing the SAP-APO with the relevant master and transaction data
Transferring data changes (transaction data)
Returning planning results to the execution system (R/3 or external system).

© SAP AG AP205 Preface-13

 APO Integration (2)

SAP R/3
SD
LO Non-
Non-
R/3
R/3System
System
HR

BAPI
CIF
(Core Interface) BAPI BAPIs
SAP APO BAPI

© SAP AG 2001

The APO Core Interface (CIF) is responsible for the data exchange between APO and R/3 Systems.
The APO CIF is a real-time interface that links APO with one or several R/3 Systems.
The system only transfers the data objects needed in the data structures in APO for the different
planning and optimization processes, from the complex dataset of the R/3 into APO.
The APO Core Interface guarantees both the initial data transfer (initial transfer) and the data changes
(transfer of data changes) within APO.
The outbound delivery from APO CIF takes place as an R/3 Plug-in.
The integration of R/3 with the CIF is possible as of release 3.1I. Earlier releases or an R/2 System can
be connected with BAPIs as "Non-R/3 Systems". (BAPI = Business Application Programming
Interface).

© SAP AG AP205 Preface-14

 APO Integration (3)

R/3 APO live

Cache
Sales order
Planned order
Production order
CIF
Real-time
Order
• Production
• Procurement
• Replenishment
Purchase order
...

Plant, customer,... Location

Material master Product
Capacity
Routing and
CIF Resource
Production
bill of material process model

© SAP AG 2001

The planning in APO is based on its own master data, which is usually transferred automatically from
a R/3 System, but can also be created manually.
The transfer of master data from the R/3 is represented in the corresponding master data in APO. Only
the master data relevant for planning in APO is transferred (firstly in the form of an initial transfer, and
then later as a transfer of data changes).
The R/3 remains the execution system for the master data. You can only maintain the settings that the
system cannot transfer from the R/3 directly into APO.
The system transfers the transaction data relevant for planning, such as warehouse stock and sales or
production orders, from the R/3 into APO via the CIF interface. And vice versa, the results of the
planning in APO are returned to the R/3 via CIF and then performed there. This integration of
transaction data generally takes place in real-time.

© SAP AG AP205 Preface-15

 R/3 Plug-In Technology

CIF
APO
R/3
Plug-in CRM

BW
R/3
BBP

SEM

Information on R/3 Plug-in: SAPNet/R3-Plug-in

© SAP AG 2001

An R/3 interface is marked with an R/3 Plug-in, to enable the system to integrate a mySAP component
(for example, APO or BW) with one or several R/3 Systems. With R/3 Plug-ins, several mySAP
components can be inserted at the same time. Most Plug-ins concern Add-Ons (R/3 standard software
enhancements with additional functions).
Plug-ins supply the components with transaction and master data. In this way, the CIF interface does
not only provide the APO System with initial data records (initial supply), it also guarantees a step-by-
step supply with all the relevant data changes. The system only transfers the object data relevant for the
individual planning and optimization process in APO, from the complex data records into R/3. The
integration between R/3 and APO is possible as of release 3.1I.
For easy integration from R/3 and APO, it is necessary to install a Plug-In relevant to the R/3 release.
Also note that support packages are also delivered for the Plug ins.

© SAP AG AP205 Preface-16

 Course Overview: Unit Summary

The integration of the SAP-APO with R/3 Systems

takes place via the CIF interface, which is an
element of the R/3 Plug-in. Non R/3 Systems are
connected using BAPIs.
The system transfers the master data relevant for
planning in APO via the CIF interface, from R/3 into
APO.
The CIF interface is responsible for the transfer of
transaction data from the R/3 into APO and for the
retransfer of the planning results from APO back
into the R/3.

© SAP AG 2001

© SAP AG AP205 Preface-17

 Architecture of Integration

Contents:
RFC Links Between APO and the R/3 System
Business System Group
Basic Settings

© SAP AG 2001

© SAP AG AP205 Preface-18

 Architecture of Integration: Unit Objectives

At the conclusion of this unit, you will be able to:

Set up a RFC link between APO and the R/3

System
Explain the concept of the business system
group.

© SAP AG 2001

© SAP AG AP205 Preface-19

 Overview Diagram (2)

1 Overview

22 Architecture of Integration 2
3 Transfer of Master Data

4 APO Master Data

5 Models and Planning

Versions

6 Transfer of Transaction Data

7 Monitoring/Error Handling

8 Conclusion

© SAP AG 2001

© SAP AG AP205 Preface-20

 APO Integration with R/3 Systems

SAP R/3
SD
LO Non-
Non-
R/3
R/3System
System
HR

BAPI
CIF BAPIs
BAPI
(Core Interface)
SAP APO BAPI

© SAP AG 2001

The APO Core Interface (CIF) is responsible for the data exchange between APO and R/3 Systems.

© SAP AG AP205 Preface-21

 RFC: Link Between R/3 and APO

R/3 APO

Master/
transaction data

Core
Core Interface
Interface
(selection
(selection and
and Remote
APO master/
extraction
extraction of
of Function transaction data
data)
data) Call (RFC)
live
Cache

© SAP AG 2001

A RFC (Remote Function Call) connection connects an SAP R/3 System and an APO System. The
system transfers the data that is selected with the Core Interface (CIF), via this connection. (To avoid
confusion, an example of a data transfer from the R/3 into the APO System is shown on the slide. The
transfer of transaction data from APO to the R/3 System also takes place with RFC technology.)
The R/3 is a database-orientated system so stores the data in the database. The APO System, on the
other hand, is available next to the classic database via the LiveCache (main memory-orientated).

© SAP AG AP205 Preface-22

 Structure of a RFC Link: Overview

Between an R/3 and an APO System

1. Naming logical systems

Names for R/3 and APO exist in the R/3
Names for R/3 and APO exist in APO

2. Assign logical systems to clients

The logical R/3 System is assigned to R/3 clients
The logical APO System is assigned to APO clients

3. Define RFC destinations

Target host for the logical R/3 System is known
Target host for the logical APO System is known

4. Establish target systems

The APO target system is known in R/3

5. Specify APO release

The release of the APO target system is known
© SAP AG 2001

A RFC connection (Remote Function Call) sets up communication between an R/3 and an APO
System.
Firstly, the system defines logical system names: In R/3 and APO, a logical system is named for both
the R/3 and the APO Systems.
Secondly, the system assigns logical systems to the R/3 and APO clients.
Thirdly, the system determines the actual RFC destination by specifying a physical connection for the
logical system. The RFC destination also contains the logon data for the relevant system.
Fourthly, the system defines the APO target destination from the view of the R/3 System, and vice
versa. There is an obvious connection between both systems.
Finally, enter the release of the APO System in step 5.

© SAP AG AP205 Preface-23

 Defining Logical Systems

Naming logical
systems R/3 Naming logical
systems APO
R3CLNT800 R3CLNT800

APO APOCLNT800 APO APOCLNT800

Assign the logical R/3 Assign the logical APO

System to R/3 clients System to APO clients
R/3 APO
Client 800 Client 800

R3CLNT800 APOCLNT800

© SAP AG 2001

You can define logical systems in Customizing, under Name logical system, which can be found in
Basis Customizing under Application Link Enabling (transaction SALE). In both R/3 and APO, you
assign a logical system name and a description for the R/3 and APO Systems, so that the systems can
be uniquely addressed in a complex system landscape.
In the R/3 Customizing step Assign Logical System to a Client (likewise in Customizing in Basis, this
is found under Application Link Enabling (transaction SALE)) you assign the logical R/3 System to
the client that should be connected to the APO System.
Do the same in APO: You assign the logical APO System to the client that should be connected with
the R/3 System. This APO client is then reachable via his logical name.
We recommend that you name the logical system as follows: [System name]CLNT[Client name], for
example, OMOCLNT800 for client 800 in system OMO.

© SAP AG AP205 Preface-24

 Define RFC Destinations

Create RFC
destination for the R/3 Create RFC
destination for the
R/3 System
APO
APO System
Logical APO Logical R/3
System name System name
R/3 link R/3 link

RFC destination APOCLNT800 RFC destination R3CLNT800

Target host [Link] Target host [Link]

System number 00 System number 00

Logon Logon

Client 800 Client 800

User APOREMOTE User R3REMOTE

Password ******* Password *******

© SAP AG 2001

RFC connections create and reverse the link between the R/3 and the APO Systems. You define the
RFC connections that are "R/3 connections" (for both R/3 and for APO) in the administration of the
particular systems, where transaction RFC destinations is created. (Menu path in R/3 and APO: Tools -
> Administration -> Management -> Network -> RFC destinations, transaction SM59).
You create a RFC destination in R/3 under the logical APO System name that you have defined and
assigned an APO client to (in our example APOCLNT800). As a target machine, you enter the server
address of the APO server and the system number, so that the APO System can be addressed in the
network. Finally, you enter a user that will create the link to the APO System. This user must exist in
the APO System and have full authorization. This is necessary for the transfer of master and
transaction data into APO.
Do the same in APO: You create a RFC destination under the logical R/3 System name that you have
defined and assigned a R/3 client to (in our example, R3CLNT800). You enter the target machine and
system number of the R/3 System. Finally, you enter a user that exists in the R/3 System and has the
necessary authorization.
You can set the RFC connections between the R/3 and APO System, so that if an error in the transfer
occurs, a new attempt at transferring automatically starts (see the Monitoring/Error Handling unit).

© SAP AG AP205 Preface-25

 Determine Target System and Maintain APO
Release

Which of the different

RFC destinations is the
APO System?

Determine APO
target system R/3 APO
Integration Server:[Link]
Logical system Mode model
System number: 00
APOCLNT800 D APO
Client: 800

Release
defined?

© SAP AG 2001

Finally, you determine which RFC destination the APO System should have. In the Target systems
transaction in CIF of the R/3 System, (menu path: Logistics -> Central Functions -> Supply Chain
Planning Interface -> Core Interface Advanced Planner and Optimizer -> Settings -> Target systems,
transaction code CFC1), you define the APO target system via the logical system name (and the
appropriate RFC connection).
The operation mode behind the system is not maintained manually, but is assigned by the system.
As the system performs the integration in various ways for different APO releases, you must also enter
the release of the APO target system. (Transaction APO releases in the CIF settings).

© SAP AG AP205 Preface-26

 Business System Group (1)

Matl. A e.g. Additionally purchased plant

Plant Hamburg
Matl. A
Logical System 1 APO
Plant Dresden Logical
System 3
Matl. A
Matl.?
Plant Munich Logical
System 2

© SAP AG 2001

An APO System can be integrated with several R/3 Systems (logical systems). It may therefore be the
case that the number assignment for certain master data objects, for example, material masters, is not
the same in all these logical systems. In the example above, material number A in logical systems 1
and 2 signifies the same hammer, whereas the same material number in logical system 3 (perhaps a
subsequently purchased plant) is a screw.
If logical systems 1, 2 and 3 are planned with the same APO System, the problem arises that the
system cannot simply transfer the R/3 material numbers into APO, as they may be ambiguous.
The fact that the same material may have different material numbers in different logical systems, is not
discussed on this or the following pages. If this does occur, you can use a customer exit in APO
inbound processing where you map the relevant material numbers from the different logical systems
onto the unique material number in APO.

© SAP AG AP205 Preface-27

 Business System Group (2)

Business system group

(BSG):
Matl. A
Area of same naming
Plant Hamburg convention
Logical System 1
APO
Matl. A
Logical Matl. A
Plant Munich Logical System 0
System 2 Plant Dresden Logical
System 3
Business System Group (1)
Business System Group
(2)

© SAP AG 2001

To guarantee that the naming of master data in distributed system landscapes is unique, business
system groups are defined as areas of the same naming convention. A Business System Group (BSG)
groups different physical systems to form a higher-level logical unit.
If, for example, two logical systems (LS1 and LS3) exist in a system landscape in which APO is
integrated, and contain different materials with the same name (Matl. A is a hammer in LS1, but a
screw in LS2), this conflict must be resolved in APO Integration. First of all, both logical systems are
to be assigned to different business system groups (BSG1 and BSG2).
The logical systems were each assigned to one business system group. The APO System, as an
independent logical system, must also be assigned to a business system group. Each source system
(R/3) is assigned to a BSG. One BSG can consist of one or several source systems. but must contain at
least one R/3 source system.

© SAP AG AP205 Preface-28

 Business System Group (3)

Unique material numbers in APO

APO
Matl. A

Plant Hamburg A
Logical System 1 hammer

A Matl. A
Matl. A hammer
Plant Dresden
Plant Munich A_BSG2 Logical System 3
Logical System 2 screw

© SAP AG 2001

If the situation arises that two different logical systems with identical number ranges are operating
when a distributed system landscape is constructed with APO, the identical names must be changed
with a customer exit. The following enhancements are available as customer exits for the inbound
processing in the APO System (transactions SMOD and CMOD):
APO_CIAPOCF001 EXIT_/SAPAPO/SAPLCIF_LOC_001: Location
APO_CIAPOCF002 EXIT_/SAPAPO/SAPLCIF_ATP_001: Maintain ATP check control
APO_CIAPOCF003 EXIT_/SAPAPO/SAPLCIF_IRQ_001: Reduction of planned indep. req.
APO_CIAPOCF004 EXIT_/SAPAPO/SAPLCIF_ORD_001: Production and planned order
APO_CIAPOCF005 EXIT_/SAPAPO/SAPLCIF_PROD_001: Products
APO_CIAPOCF006 EXIT_/SAPAPO/SAPLCIF_PU_001: Purchase order documents
APO_CIAPOCF007 EXIT_/SAPAPO/SAPLCIF_QUOT_001: Quotas and their schedules;
EXIT_/SAPAPO/SAPLCIF_QUOT_001: Customizing settings quotas
EXIT_SAPL_1004_001: Resource
APO_CIAPOCF009 EXIT_/SAPAPO/SAPLCIF_RSV_001: Reservation requirement
APO_CIAPOCF010 EXIT_/SAPAPO/SAPLCIF_SLS_001: Sales order
APO_CIAPOCF011 EXIT_/SAPAPO/SAPLCIF_STOCK_001: Stock
For further customer exits: see the online help.

© SAP AG AP205 Preface-29

 Business System Group (4)

A. Define business system groups

BSG Description
BSG1
BSG2
System group 1
System group 2
APO
B. Assign logical systems to a BSG
Logical system Business System Group
LS0 APO BSG1
LS1 Hamburg BSG1
LS2 Munich BSG1
LS3 Dresden BSG2

C. Display R/3 material numbers on APO material numbers

Material no. BSG Material APO material number
A BSG1 hammer A
A BSG1 hammer A
A BSG2 screw A_BSG2
Realization: Customer exits for master data in APO inbound
processing
© SAP AG 2001

If the situation arises that two different logical systems with identical number ranges are operating
when a distributed system landscape is being constructed, a unique mapping structure must be
constructed.
Firstly, you must define the business system groups in APO Customizing step Maintain business
system groups (in the basic settings in APO).
In the next step (Customizing step Assign logical system) you assign the diverse logical systems of
your system landscape to a BSG. You should be aware that, within a system group, the same naming
convention must apply, that is to say, the different master data objects must have unique names within
the group.
The last step states that the system can transfer master data objects from the different BSGs (the names
do not have to be uniquely cross-BSG) with unique names via a customer exit into APO. These
customer exits exist for all master data (see below).
You must maintain a BSG, even when only one R/3 is linked with one APO System, or when several
R/3 Systems are connected without the risk of ambiguities. You will only need more than one BSG
when there is no unique naming convention.
The APO System should preferably be assigned to the BSG, where its data must not be renamed.

© SAP AG AP205 Preface-30

 APO Integration with Non-R/3 Systems

SAP R/3
SD
LO Non-
Non-
R/3
R/3System
System
HR

BAPI
CIF BAPIs
BAPI
(Core Interface)
SAP APO BAPI

© SAP AG 2001

The data exchange between APO and non-R/3 Systems takes place via BAPIs (Business Application
Programming Interfaces).
BAPIs are documented standard interfaces that enable an object-orientated access to SAP Systems (via
C++, Java, Visual Basic, IDOCs, COM/DCOM, DelphiConnect, ...).

© SAP AG AP205 Preface-31

 Architecture of Integration: Unit Summary

The integration between APO and R/3 Systems is

created using a RFC link.
To guarantee that the naming of master data in
distributed system landscapes is unique, business
system groups are defined as areas of the same
naming convention.
You can use customer exits to transfer master data
from different system groups into APO.

© SAP AG 2001

© SAP AG AP205 Preface-32

© SAP AG AP205 Preface-33
 Exercises

Unit: Architecture of Integration

Topic: Review of Settings

At the conclusion of these exercises, you will be able to:

• Review the settings of the RFC connection between an R/3
and an APO System.

Before you familiarize yourself with the functions of the CIF

interface as a member of the project team, review the RFC
connection that connects the R/3 System with the APO System.

1-1 During the exercises, link an R/3 System with an APO System. The link between
these systems is based on a RFC connection that connects two logical systems.
1-1-1 Which R/3 client are you working with? _________________
1-1-2 View in R/3 Customizing, which logical system name is assigned to your
client. Note the logical name of the R/3 System: ________________
1-1-3 Which APO client are you working with? ________________
1-1-4 View in Customizing of the APO System, which logical system name is
assigned to your client. Note the logical name of the APO System:
________________

1-2 In the next step, view the RFC connection between the two systems.
1-2-1 In the R/3 System, display the RFC connection to the APO System. This
connection contains the name of the logical APO System that you noted
above. Which user name is used for logon to the APO System?
______________________________________
1-2-2 In the APO System, now display the RFC connection to the R/3 System. This
connection contains the name of the logical R/3 System that you noted above.
Which user name is used for logon to the R/3 System?
______________________________________

© SAP AG AP205 Preface-34

© SAP AG AP205 Preface-35
 Solutions

Unit: Architecture of Integration

Topic: Review of Settings

1-1
1-1-1 R/3 client: Varied, for example, client 800.
1-1-2 Menu path in Customizing of the R/3 System: Customizing-Basis
Components → Application Link Enabling (ALE) → Sending and
Receiving Systems → Logical Systems → Assign Client to Logical System
Assigned logical name of the R/3 System: Varied, for example,
T90CLNT800.
1-1-3 APO client: Varied, for example, client 800.
1-1-4 Menu path in Customizing of the APO System: Customizing R/3 Basis
Customizing → Application Link Enabling (ALE) → Sending and
Receiving Systems → Logical Systems → Assign Client to Logical System
Assigned logical name of the APO System: Varied, for example,
APOCLNT800.

1-2
1-2-1 RFC connection to the APO System: Menu path in the R/3 System Tools →
Administration → Administration → Network → RFC Destinations (R/3
Connections)
User name: USERADMIN
1-2-2 RFC connection to the R/3 System: Menu path in the APO System Tools →
Administration → Administration → Network → RFC Destinations (R/3
Connections)
User name: USERADMIN

© SAP AG AP205 Preface-36

 Transfer of Master Data

Contents:
Transfer of Master Data Between R/3 and APO Systems
Initial and Incremental Data Transfer
Integration Model for the Transfer of Master Data.

© SAP AG 2001

© SAP AG AP205 Preface-37

 Transfer of Master Data: Unit Objectives

At the conclusion of this unit, you will be able to:

Describe the concept of initial and incremental

data transfer of master data from an R/3 System
into an APO System
Create an integration model for the transfer of
master data
Transfer master data.

© SAP AG 2001

© SAP AG AP205 Preface-38

 Overview Diagram (3)

1 Overview

2 Architecture of Integration
3
33 Transfer of Master Data

4 APO Master Data

5 Models and Planning

Versions

6 Transfer of Transaction Data

7 Monitoring/Error Handling

8 Conclusion

© SAP AG 2001

© SAP AG AP205 Preface-39

 Master Data Interface: Core Interface (CIF)

R/3 APO

R/3 master data APO master data

Core Interface
Plant, Customer,... CIF Location
Material master Product
Capacity Integration Resource
Task list and model Production
Bill of material process model

© SAP AG 2001

The APO Core Interface (CIF) defines and controls the data transfer between R/3 and APO Systems.
The CIF is the central interface for connecting APO to the existing R/3 System environment.
A RFC connection with the R/3 System is a technical requirement for successful data transfer into
APO using the Core Interface.
The CIF interface is an add-on to the R/3 System that you install using the relevant plug-in. The exact
installation process is dependent, amongst other things, on the R/3 release you are working with. You
can find current detailed information on plug-ins in SAPNet, under the alias /R/3 plug-in.
The selection of master data that the system transfers into APO is determined in an integration model
that you define in the R/3.

© SAP AG AP205 Preface-40

 Master Data Objects of the CIF

Initial transfer

R/3 APO
R/3 master data APO master data
Plant Location
Customer
Product
Vendor
Material master Resource

Capacity Production
Routing and process model

bill of material

Incremental data transfer

© SAP AG 2001

The APO Core Interface concerns a real-time interface. The system only transfers the data objects from
the complex dataset in R/3 into APO, that are needed in the data structures of APO that have been
reconciled in the planning, for the respective planning and optimization processes.
Both the initial data transfer (initial transfer) and the data changes (transfer of data changes) within
APO take place using the APO Core Interface.
The master data objects in APO are not the same as those in R/3. For the master data transfer it is in
fact the relevant R/3 master data that is displayed in the corresponding planning master data in APO.
The R/3 System remains the dominant system for the master data. You only maintain the specific APO
master data that does not exist in R/3 directly in APO.

© SAP AG AP205 Preface-41

 Initial Data Transfer of Master Data: Overview

1. Generate integration model Name

Target system

Determine name and APO

Plant
target system Material master
Resource
Select master data ...

2. Activate integration model

Integration model is active

Start Master data will be transferred

© SAP AG 2001

You define the integration model that controls the transfer of master and transaction data in the R/3
System. You can find the menu option Core Interface Advanced Planner and Optimizer (the CIF
menu) under Logistics -> Central Functions -> Supply Chain Planning Interface.
The integration model distinguishes between master data and transaction data. We recommend that you
select the two types of data in separate integration models and then transfer them separately.
In the integration model, you select the dataset (master or transaction data) that you want to transfer.
You specify the following in the integration model:
- The APO target system for the data transfer
- The data objects you want to transfer
You can delete integration models that you no longer need. Note that you must first deactivate these
integration models.

© SAP AG AP205 Preface-42

 Generate Integration Model for Initial Data Transfer

Name + application = unique definition of integration model

Name PUMPS
Target sys. APOCLNT800
APO
Application MATERIALS System
Material master
Customers Vendors
Selection of master
Plants Work centers data types
Production process models
...
Relevant materials
Material
Selection criteria for
Plant 1000
the master data
MRP type X0
...
Execute + Save
© SAP AG 2001

The master data that the system will transfer for the first time (initial transfer), from the R/3 System
into the APO System, is defined in an integration model. The R/3 System generates this integration
model (transaction CFM1).
An integration model is uniquely defined by its name and application. It is useful to create several
integration models with the same name but as different applications. Ensure that the data pools of your
integration models are generally not too big. This enables you to handle errors more easily.
The target system that you specify in the integration model determines the APO System that the master
data is transferred into. The target system is a logical (APO) system that must have a RFC connection.
Finally, you use a particular integration model to specify which master data you want the system to
transfer. To do so, you first specify the master data types that flow into the integration model. In the
second step, you specify the selection criteria to be used for the selection of the individual master data
documents in the R/3 System.
You complete the generation of the integration model by "executing" the model (this means that the
data objects of the model are compiled) and then you save it.

© SAP AG AP205 Preface-43

 Activate Integration Model for Initial Data Transfer

Integration model
Name PUMPS
R/3
Material
Material master AA
Target system APOCLNT800 Materialmaster
master B
Application MATERIALS Material master A

"Activate" Active/Inact.

PUMPS APOCLNT800 MATERIALS 10:00:00

Start

Material
Material master
master A
Master data Product B A
APO in APO Product A

© SAP AG 2001

To transfer data into APO, you must activate an integration model that has previously been generated.
You activate an integration model with the transaction Activate integration model (transaction code
CFM2) in the CIF.
It is useful to have several integration models active at a time.
Choose the Start function to trigger the data transfer into APO: The master data, or the equivalent of
the R/3 master data in APO, exists in the APO System.

© SAP AG AP205 Preface-44

 Selection Criterion MRP Type "X0"

R/3 Material master D

Material master C
Integration model
Name PUMPS
Material master B TargSys. APOCLNT800
MRP type X0 Material master A
Applic. MATERIALS
MRP procedure X
W/out materials planning, Matl. A Material master
with BOM explosion
X0 Customers
...
Relevant materials
Matl. B Matl. C Matl. D Material
X0 X0 VB Plant 1000
MRP type X0
Product C Material status AP
Planning in ...
APO APO
Product B
Product A
Further restrictions
on the selection are possible
© SAP AG 2001

You do not necessarily need to perform the planning for all materials in APO. Remember that the
planning of critical materials takes place in APO, while less critical materials (for example,
consumption-based purchased materials) are only planned in the R/3.
Do not plan materials in the R/3 that have already been planned in APO - the system will transfer the
planning result in the form of planned or production orders from APO directly into the R/3 System. For
materials with a bill of material, however, the dependent requirements can if necessary be determined
in the R/3 (usually as a result of the requirements planning). Therefore, you assign a particular MRP
type with procedure X (without materials planning, with BOM explosion) to these materials. (This
MRP procedure exists as of Release 4.0; if you are working with earlier releases, use the MRP type P4
with a planning time fence of 999 days.)
The MRP type X0 for selecting APO-relevant materials is available here for use in the integration
model. If you provide materials that should be planned in APO with a particular plant-specific material
status, you can use this to limit the selection further.
Generally, it is advisable to be cautious when allocating APO-relevant and non APO-relevant
materials: For effective planning in APO, you must ensure that all materials playing an important part
in the planning process are also planned in APO. (Consider capacity planning: If the capacities in APO
are to be planned for the different resources, all materials using these resources for production must be
planned in the APO System).

© SAP AG AP205 Preface-45

 Transfer New APO-Relevant Master Data (1)

Name PUMPS
R/3 New
Target sys. APOCLNT800
Existing integration model

Application MATERIALS Execute + Save

Material master Q
X0 Material master ...
"Activate"
MRP type X0 Active/Inact.

PUMPS APOCLNT800 MATERIALS 11:00:00

PUMPS APOCLNT800 MATERIALS 10:00:00

Start Difference is transferred

New master data in

APO APO
Product Q

© SAP AG 2001

New APO-relevant master data (in the example on the slide above, a new material with MRP type X0),
that corresponds with the selection criteria of an existing integration model (in the example, materials
with the MRP type X0 are selected in the integration model), can be transferred into APO in the
following way: The system re-generates the existing model (the new master data is also selected here)
and then activates it. Two models with the same name are then active, the only differences being the
dates and times. If the data transfer starts in this situation, the system simply transfers the difference
data. The system compares the existing, active integration models with the new model. After the data
transfer, the system deactivates the "old" integration model, leaving the "new" complete integration
model as the active model.
If you want the system to retransfer all the master data of an existing integration model, you must
deactivate the old models and activate only the new one. A comparison of all active models then takes
place. As in this case, the model with the old time is not active, all data is transferred again.
If you have activated model 1 with the material masters A and B, and activate a model 2 in the second
step with material masters B and C, then when you activate model 2, only material C will be
transferred. Then when you deactivate model 1, the integration for material B remains.
To ensure that the system has transferred all the APO-relevant master data, it is possible to periodically
regenerate and activate the existing integration models.

© SAP AG AP205 Preface-46

 Transfer New APO-Relevant Master Data (2)

Execute integration model periodically

Generate integration model

Name PUMPS JOB_1
Target system APOCLNT800 Variant Execute
MATERIALS
PUMP_MAT + Step 1
Application
Save
...
RIMODGEN report alternative:
JOB_1_AND_2
Activate integration model
Name PUMPS
JOB_2
Variant Active/Inact.
Target system APOCLNT800
PUMP_MAT + Step 2
Application MATERIALS Start
RIMODAC2 report

© SAP AG 2001

Defining jobs enables the system to regenerate and then activate the integration models in regular
intervals, as the R/3 System is constantly creating new APO-relevant master data.
The system generates an integration model with the RIMODGEN report. You schedule this report by
entering a variant (that you must have defined previously) as a job.
The system activates an integration model via the RIMODAC2 report. You need a variant for this
report too, in order to schedule it in a job.
"Executing" an integration model consists of two steps: The generation and activation of an integration
model. You can schedule these two steps with a job, where you define the two activities as two
consecutive steps. For this procedure you also need the relevant variants for both steps.

© SAP AG AP205 Preface-47

 Incremental Data Transfer of Master Data (1)

Changes to APO-relevant master data are transferred - what

is APO-relevant master data?

Name PUMPS
Applicat. MATERIALS

Material master
...
Relevant materials
Material A
Materials (generally:
Material
Plant 1000 Material B Master data) are
MRP type X0 Material C APO-relevant
... ...
Integration model active
Pumps APOCLNT800 Materials

© SAP AG 2001

Any changes you make to the master data in the R/3 System that are also APO-relevant, must be
transferred into the APO System. The system does not usually carry out a new initial data transfer, but
just transfers the individual changes to the master data. In the same way, the system also transfers a
deletion flag for a material into APO.
An incremental data transfer assumes that an active integration model is available for the relevant
materials, and that the materials are APO-relevant.
With the transfer of master data changes, remember that the system will transfer the complete data
record. If, for example, you change a field in the material master, the entire material master will be
retransferred within the incremental data transfer.

© SAP AG AP205 Preface-48

 Real-Time Transfer of Master Data Changes

Configuration procedure for transfer of master data changes

Transaction CFC5
APO
Material master
Changed R/3 master data
Business Transaction Event, immed. objects are transferred into
ALE change pointer, periodic APO when the changes are
saved in real-time
no incremental data transfer

Customers
Business Transaction Event, immed. Changes to R/3 master data
ALE change pointer, periodic objects are recorded and the
transfer of the changes is
no incremental data transfer (periodically, for example)
triggered
Vendors
Business Transaction Event, immed.
ALE change pointer, periodic
no incremental data transfer

© SAP AG 2001

The system can transfer changes to APO-relevant master data (data contained in an active integration
model) the material master, customer and vendor in real-time, (directly when updating a data change in
the R/3 System) into the APO System.
You can access the settings for this function with transaction CFC5. In real-time transfer, the system
transfers the complete data record that has been changed directly to the APO System. (For numerous
changes there are corresponding repercussions on the system performance). In the periodic transfer, the
system collects and transfers the master data changes into the APO System, within a normal
incremental data transfer. The incremental data transfer can finally be deactivated.
You can control the incremental data transfer of master data with transaction CFC5. If the incremental
data transfer is set to "Business Transaction Event, immediately", the processing takes place without
using change pointers. If the incremental data transfer is set periodically, the change pointers are
automatically activated.

© SAP AG AP205 Preface-49

 Incremental Data Transfer of Master Data (2)

Master data Change pointer generally active?

change Relevant message type
active?
Material master A

Matls. planning Change pointer

MRP type X0 Mat B in-house [Link]

[Link] 10 days
Customizing Mat A [Link]
...

11 days

Incremental data transfer Incremental

Variant
DELTA_MAT Target sys. APOCLNT800 data transfer
Object types Execute
Material master ...
Changed master Product A
APO data in APO [Link] 11 days

© SAP AG 2001

The R/3 is the dominant master data system. As a rule, the system performs changes to the master data
in the R/3 System and transfers them from there into the APO System. With master data changes, it is
not necessary for the system to totally retransfer all the master data as an initial data transfer. Instead,
the system can transfer just the changed master data.
For an incremental data transfer, you must set in Customizing in the R/3 System, that ALE change
pointers are written for master data changes. First, you activate the change pointers (Activate change
pointer in Customizing in ALE, transaction BD61), before you determine (in Customizing, Change
pointer per message type, transaction BD50), which master data objects should have change pointers.
(CIFMAT message type for material masters, CIFVEN for vendors, CIFCUS for customers, CIFSRC
for info records)
If you use transaction CFC5, the settings for the message types CIFMAT, CIFVEN and CIFCUS are
automatically set.
The process of incremental data transfer reverts to the ALE change pointer. This change pointer selects
the master data for the system to retransfer. When you call up the transaction Incremental data transfer
of master data (CFP1), specify the the logical target systems and the master data objects (material
masters, vendors, sources of supply, customers), that have changes to be transferred.
You can save your settings for the incremental data transfer as variants, and, if necessary, use these
variants for the periodic scheduling of incremental data transfer as a job (RCPTRAN4 report).

© SAP AG AP205 Preface-50

 Transfer Master Data Changes Periodically

Evaluate and send change recordings

Schedule periodically
Target sys. APOCLNT800
Object types Variant JOB_DELTA
Material master
DELTA_MAT Execute
Customers ...
RCPTRAN4 report

Current master data

APO in APO

© SAP AG 2001

This gives you the chance to periodically schedule the transfer of master data changes as a job. Here
you define a variant (containing the target system and the selection of master data objects) for the
RCPTRAN4 report (hidden behind transaction CFP1), with which you can define the job.

© SAP AG AP205 Preface-51

 Integration Model: Other Functions

+ Deactivate integration model

Connection between R/3 and APO for the relevant
master and movement data will be cancelled

+ Delete integration model

Deactivated models can be deleted

+ Filter object search

Check whether the data objects are already
contained within an integration model

+ Consistency check
You can check the consistency of the selected data
in the integration model

© SAP AG 2001

Deactivate integration model: For example, relevant sales orders created in R/3 are no longer
transmitted to APO after you have deactivated the integration model for movement data (that contains
sales and planned orders). Planned orders that are created in APO after deactivation of the integration
model are not transmitted to APO either. After you deactivate the integration model for master data, no
data changes are transmitted.
Delete integration model: Deleting an integration model does not mean that the previously selected
data in APO is also deleted. (Note: For master data contained within an active integration model, and
for which you have set a deletion flag in R/3, the deletion flag is transmitted to APO using initial data
transfer).

© SAP AG AP205 Preface-52

 Transfer of Master Data: Unit Summary (1)

The R/3 is the dominant master data system. The

system transfers the master data from the R/3 into
the APO System with the help of a CIF integration
model.
During an initial transfer, the system automatically
creates the APO master data that corresponds
with the R/3 master data.
The system determines the scope of an initial
transfer with an integration model.
An incremental data transfer can help guarantee
that the system will transfer APO-relevant data
changes in the R/3 into the APO System.

© SAP AG 2001

© SAP AG AP205 Preface-53

 Transfer of Master Data: Unit Summary (2)

The system can schedule both the initial transfer

and the incremental data transfer as periodic jobs
using relevant existing reports.
The incremental data transfer of master data is
also possible as a real-time transfer.

© SAP AG 2001

© SAP AG AP205 Preface-54

 Exercises

Unit: Transfer of Master Data

Topic: Initial Transfer of Material Masters

At the conclusion of these exercises, you will be able to:

• Prepare R/3 material masters for planning in APO
• Create an integration model for the initial data transfer and
execute the transfer.

The pump T-F1## should be planned in APO. Therefore, you first

prepare the material master in the R/3, for plant 1000, for
planning in APO, and then create an integration model to transfer
into APO.

1-1 The material T-F1##, for plant 1000, should be planned in APO. Materials planning
in R/3 is controlled by the MRP type that you enter in the material master. If a
material is not to be planned in the R/3, it must have the corresponding MRP type.
1-1-1 Display the X0 MRP type in the R/3 Customizing. Which MRP procedure is
entered in this MRP type?
_________________________________________
1-1-2 What effect does this MRP procedure have?
_________________________________________
1-1-3 Which planning method is entered in this MRP type (in Additional selection
parameters)?
_________________________________________

© SAP AG AP205 Preface-55

 1-2 Change the material master T-F1## in plant 1000, MRP views 1 and 4, as follows:
1-2-1 Enter MRP type X0 in the MRP1 view.
1-2-2 The subsequent transfer of the task list and bill of material into the APO
System assumes that a valid production version exists in the R/3. Therefore,
create a production version for material T-F1## : Press the Production
version button in the MRP4 view of the material master. In the overview
screen, enter a new production version 0001 with the name Normal
production, which should be valid from today until the end of next year.
Using the Details button, go to the detail screen and enter the following data:
Lot size: from 1 (pc) to 999,999 (pc)
Task list: In the detailed scheduling row, transfer the Normal task list, that
you search for (and find) with the F4 Help, from the planning group field
using material (T-F1##).
Bill of material: Enter the alternative BOM 1 from BOM usage 1.
You exit the production version maintenance by pressing the button Continue
twice, then save the material master.

1-3 You create an integration model to transfer the material master to APO:
1-3-1 Generate an integration model with the following settings:
Model name: PUMP##
Target system: Logical APO system name that you noted above
Application: MAT T-F1##
Select the material masters to be included in the integration model. As
further relevant materials, enter the material T-F1## in plant 1000.

Do not execute the integration model yet!

1-3-2 Save your settings as the Mat. variant. T-F1##.

1-3-3 Execute the integration model by pressing the execute icon. On the following
results screen, make sure that the integration model selected your material T-
F1##.
1-3-4 To complete this process, save your integration model.

To transfer the master data to the APO System, you must

activate the integration model. To provide a better overview,
the instructor will activate all your models.

© SAP AG AP205 Preface-56

 1-4 The instructor activates your integration models.

1-5 Check the result of the material master transfers in APO. In the APO System, display
the product T-F1## in location 1000.
1-5-1 What is the name of product T-F1##?
______________________________________________
1-5-2 Look at the Administration tab page. Which user created the product master?
____________________
Where does this user come from?
____________________________________________________
1-5-3 Go to the Lot size tab page. Which lot-sizing procedure is set here?
____________________________________________________
1-5-4 Go to the Procurement tab page. Which procurement type is set?
____________________________________________________

© SAP AG AP205 Preface-57

© SAP AG AP205 Preface-58
 Solutions

Unit: Transfer of Master Data

Topic: Initial Transfer of Material Masters

1-1 Menu path in R/3 Customizing: Tools → Accelerated SAP → Customizing → Edit
Project (SPRO) → Reference IMG (button) → Production → Material
Requirements Planning → Master Data → Check MRP Types
1-1-1 MRP procedure in MRP type X0: X, Without MRP, with BOM explosion.
1-1-2 Effect: This MRP type means that the corresponding materials will not be
planned in the R/3. For planned orders that are created manually or
transferred from a non-SAP system (APO), a BOM explosion is still
performed, allowing for dependent requirements to be created.
1-1-3 Planning method: 1, Planned by external system.

1-2 Menu path in the R/3 System: Logistics → Production → Master Data → Material
Master → Material → Change → Immediately

1-3
1-3-1 Menu path in the R/3 System: Logistics → Central Functions → Supply
Chain Planning Interface → Core Interface Advanced Planner and
Optimizer → Integration Model → Generate → Create
1-3-2 Save as a variant: Enter the variant name in the integration model under Goto
→ Variant → Save as variant and then save.

1-4

© SAP AG AP205 Preface-59

 1-5 Menu path in the APO System: Master Data → Product, enter product T-F1##,
select Location view and enter location 1000, then press the Display button
1-5-1 Name of product: Pump PRECISION 100 (transferred from the R/3).
1-5-2 User who created the product master: USERADMIN.
Origin of this user: The product master was transferred via the CIF
interface that is based on a RFC connection between the R/3 and the APO
System. The user USERADMIN is defined in this RFC connection – the
CIF interface uses this user to logon to the APO System.
1-5-3 Lot-sizing procedure: The lot-sizing procedure Lot-for-Lot is set to
correspond with the exact lot size in the R/3.
1-5-4 Procurement type: E (In-house production) is set.

APO Master Data

Contents:
APO Master Data
Result of Transfer of R/3 Master Data into APO
Supplementing APO Master Data.

© SAP AG 2001

© SAP AG AP205 Preface-60

 APO Master Data: Unit Objectives

At the conclusion of this unit, you will be able to:

Describe the result of the transfer of R/3 master

data into APO
Explain the function of the individual master data
documents in APO
Specify where in the APO System it may be
necessary to add to the master data transferred
from the R/3.

© SAP AG 2001

© SAP AG AP205 Preface-61

 Overview Diagram (4)

1 Overview

2 Architecture of Integration

3 Transfer of Master Data

44 APO Master Data

5 Models and Planning Versions

6 Transfer of Transaction Data

7 Monitoring/Error Handling

8 Conclusion

© SAP AG 2001

© SAP AG AP205 Preface-62

 Master Data: Overview (1)

R/3 APO
R/3 master data APO master data

Plant
Customer Location

Vendor

Material master Product

Work center/capacity Resource

Routing and bill Production

of material process model

© SAP AG 2001

The system transfers the R/3 master data objects plant, customer and vendor into APO as locations
with different location types.
The system also transfers classes and characteristics from the R/3 into the APO System.

© SAP AG AP205 Preface-63

 Location Types

R/3 APO
Locations with
location type
CIF
Plant 1001 Production plant

Distribution center 1002 Distribution center

MRP area 1007 MRP area

Customer 1010 Customer

Transportation zone
1005 Transportation zone

Vendor 1011 Vendor

...

© SAP AG 2001

© SAP AG AP205 Preface-64

 Location Type Production Plant

Data transfer from the R/3 production plant

Customizing: Plant Master data: Location

APO
Plant 1000 Location 1000 Plant Hamburg
Name Plant Hamburg [Link] 1001 Production plant

General Address
Street Alsterstr. 13
Town 22222 Hamburg Street Alsterstr. 13

Country DE Germany Town 22222 Hamburg

Region 02 Country DE Germany

Hamburg
Region 02 Hamburg
Time zone CET
Language German Time zone CET
Language German

© SAP AG 2001

The system transfers a plant into the APO System as a location with location type 1001 (production
plant). The system also copies these basic settings for the plant: Description, address data, time zone
and regional assignment.

© SAP AG AP205 Preface-65

 Additional Data in APO Location

Master data: Location

APO DE Plant Hamburg
Location 1000
EN Plant Hamburg
[Link] 1001 Production plant
Short description of the
General Address SNP ...
location in several
languages
Street Alsterstr. 13
Town 22222 Hamburg
Country DE Germany
APO-specific planning
Region 02 Hamburg parameters
Time zone CET
Language German

© SAP AG 2001

For APO locations, you can maintain the short text in several languages (in contrast with the plant in
R/3, for example), so that after logon in a certain language, this language will appear.
As a rule, APO locations contain many additional planning parameters that have no equivalents in R/3.
You can then maintain these parameters in APO. The system cannot transfer them from the R/3.

© SAP AG AP205 Preface-66

 Location Type Distribution Center

Data transfer from R/3 distribution center (from Rel. 4.0)

Master data: Location APO
Customizing: Plant

Plant 2400 Location 2400 DC Milano

Name DC Milano [Link] 1002 Distribution center

General Address
Street Via Castaldi 1
Street Via Castaldi 1
Town 20100 Milano
Town 20100 Milano
Country IT Italy
... Country IT Italy
...
Definition as DC
Customizing: DRP
Plant Node type Name
1000 Hamburg plant
2400 DC DC Milano
© SAP AG 2001

As of Release 4.0, the system can define plants as distribution centers, within the frames of the DRP
functionality (DRP: Distribution Resource Planning) in R/3. For this, you use the corresponding entry
in the Customizing table (Customizing step Assign Node Type - Maintain Plant in the settings of DRP
Customizing).
When you transfer plants into APO that are defined in the R/3 as distribution centers, the system
transfers them to location type 1002 (distribution center). The transfer of the individual R/3 plant
settings (in R/3, a DC is a plant) takes place in exactly the same way as it does for production plants. If
you are working with an R/3 Release older than 4.0, where you cannot define DCs, use a customer exit
to transfer an R/3 plant as an APO-DC.

© SAP AG AP205 Preface-67

 Location Type MRP Area

Data transfer from R/3 storage location MRP area (as of Rel. 4.5)

Customizing: Reqts. planning

MRP area DB1099 APO

Name MRP area 1099 Master data: Location

MRP area type 02 Loc. DB1099 MRP area 1099

Plant 1000 Type 1007 MRP area
Receiving storage loc. 0099 Assignment to plant 1000
no other storage1000
Plant locations
are assigned! General Address

Hamburg plant Street Alsterstr. 13

Street Alsterstr. 13 Town 22222 Hamburg

Town Country DE Germany

22222 Hamburg
Country DE Germany
...
...
© SAP AG 2001

As of Release 4.5, MRP areas for the differentiation of requirements planning below the plant level are
available in the R/3. You can transfer storage location MRP areas, otherwise known as type 2 MRP
areas, into APO as locations with location type 1007.
In the R/3, MRP areas are organizational levels below the plant level, i.e. they are assigned to one
particular plant. This plant assignment remains in APO.
The system can only transfer storage location MRP areas into APO that have only one specific storage
location, corresponding to the receiving storage location, assigned to them. (It should be noted that
there are generally no storage locations in APO). The system cannot transfer subcontractor MRP areas
or plant MRP areas, but it can transfer the plants.
An R/3 material master can be included in the plant MRP data and MRP area segments, and enables
planning of this material in different MRP areas. When the system transfers such materials into APO,
the MRP area data can also be transferred: In APO, there is then a product master for the plant location
and the MRP area locations.

© SAP AG AP205 Preface-68

 Location Type Customer

Data transfer from the R/3 customer

Master data: Customer Master data: Location
APO
Customer 1000 Location 1000 Becker Berlin
Name Becker Berlin [Link] 1010 Customer

General Address
Street Calvinstr. 36
Town 13467 Berlin Street Calvinstr. 36

Country DE Germany Town 13467 Berlin

Region 11 Country DE Germany

Berlin
Region 11 Berlin
Language German
Language German
Time zone CET

Control data
Master data: Location
Transportation zone
Location D10000 Berlin region
D10000 Berlin region
[Link] 1005 [Link]
© SAP AG 2001

The system transfers customers from the R/3 as locations with type 1010 (Customer).
The system creates sales orders in the R/3 and transfers them as transaction data into APO.
You only need a customer in APO when the customer is to be planned in APO (for example,
Transportation Planning). If you create a sales order in R/3, and the demand is planned in APO, the
sales order can also be transferred to APO without customers.
When the system transfers a customer master from the R/3 into APO, the actual customer location is
transferred, as is the transportation zone that is assigned to a customer in the R/3, as location type 1005
(transportation zone). You then enter the missing data for use with this transportation zone in the APO
planning.

© SAP AG AP205 Preface-69

 Location Type Vendor

Data transfer from the R/3 vendor

Master data: Vendor Master data: Location

APO
Vendor L1000 Location L1000 C.E.B. Berlin
Name C.E.B. Berlin [Link] 1011 Vendor

Street Kolpingstr. 1 General Address

Town 12001 Berlin Street Kolpingstr. 1

Country DE Germany Town 12001 Berlin
Region 11 Berlin Country DE Germany

Language German Region 11 Berlin

Language German

© SAP AG 2001

The system transfers vendors from the R/3 as locations with type 1011 (vendor).
Note: If the vendor and the customer have the same number in the R/3 System (for example, customer
and vendor 1000), then you must rename one of them in the APO inbox, using the customer exit for the
vendor master. (For example, rename the vendor in S1000). Otherwise, you cannot distinguish between
the two locations.
The vendor must be known in APO in order for the vendor selection to take place in APO.

© SAP AG AP205 Preface-70

 External Procurement Relationship

Data transfer from the R/3 purchasing info record

APO
Ext. procurement relationship
Purch. info record General Data
Info rec. Vendor
Info rec. 53004711 R3CLNT800 Source loc. L1000 known
53004711 Product in APO?
Vendor L1000 PUMP

Material PUMP Target loc. 1000

Plant 1000 Valid from 01.01.2000

to 31.12.9999
Valid from 01.01.2000
to 31.12.9999 Settings
[Link] 12 days
[Link] 12 days
Transportation lanes
Valid 01.01.2000 to 31.12.9999

© SAP AG 2001

The system can transfer a purchasing info record from the R/3 into APO as an external procurement
relationship. You should be aware that the source location (that corresponds with the vendor in the
purchasing info record) must be recognized in APO, in order for a successful data transfer to take
place. If necessary, the system will transfer the vendor beforehand.
The system transfers the purchasing price from the purchasing info record into the external
procurement relationship. (Scale prices too).

© SAP AG AP205 Preface-71

 Master Data: Overview (2)

R/3 APO
R/3 master data APO master data

Plant
Customer Location

Vendor

Material master Product

Work center/capacity Resource

Routing and bill Production

of material process model

© SAP AG 2001

The system can transfer the R/3 material master into the APO System as a product master.

© SAP AG AP205 Preface-72

 Product Master in APO

Views of the APO product master

Administration Demand

Attributes Lot size

Units of measure SNP2

Classification Material PP/DS

SNP1 Procurement

ATP GR/GI

© SAP AG 2001

The product master in APO is divided into different views according to topic. The header data (tab
pages characteristics, units of measure, classification) is general and valid for more than one location.
You can specify the planning of a product in APO, according to the location. Locations can come from
plant type or MRP area (according to the R/3 storage location MRP areas).
Many of the fields for the product are automatically filled when the system transfers a material master
from the R/3. To guarantee the consistency of the data in the R/3 and APO Systems, only maintain
these fields in the R/3 System. The system then only changes the data during a transfer (from the R/3)
of the master data changes.
You can define the length of the APO product master number in APO Customizing (process step:
Determine Output Display Of Product Number). As is standard in R/3, an 18 digit product number is
used.

© SAP AG AP205 Preface-73

 General Data

Product A APO
R/3 Simple selection
Attributes
in the integration
model Material group 001
Transportation grp 0001
Mat A
Gross weight 280 KG
X0
Volume 0,75 M3

Units of measure
MRP type X0
1 pc equals 1 pc
MRP procedure X 1 pal equals 10 pc
W/out materials planning,
with BOM explosion
Classification
regarding classes and
characteristics that must exist
in APO

© SAP AG 2001

The system transfers the following general data from the R/3 material master into the APO product:
Material group (Basic data 1), transportation group (Sales and Distribution: gen./Plant), gross weight
and volume (Basic data 1), units of measure (Additional data), classification data (Classification).
Note that, for classification data, the system transfers the classes and characteristics into APO
beforehand.
Materials that the system transfers into APO must be part of the integration model. The selection of
APO-relevant materials can usually be easily defined by the use of MRP type X0.

© SAP AG AP205 Preface-74

 ATP Settings

Material A Product A
APO
MRP 3 ATP
Availability check ATP group 02
Availability check 02 [Link] 10 days
TRLT 10 days Calendar for
[Link] LOC1000
Planning
Check mode 050 Suggestion:
Strategy group 40 Production
calendar of
location

Planned [Link] Customer reqmt

type VSF Main strategy 40 type KSV
class 101 class 050

or: Enter customer requirement class

from schedule line of the sales order

© SAP AG 2001

After the transfer of ATP Customizing, the system can transfer the ATP settings from the material
master into the corresponding product.
The system transfers the checking group as the ATP group in the product and the total replenishment
lead time as the checking horizon directly from the masterial master.
The system transfers the check mode: It corresponds with the requirements class in R/3, in other
words, you enter here the indicator for the customer requirements class that is determined by the
strategy group of the material.
In the R/3, the requirements class is usually determined by the strategy group of the material but can
also be a result of the schedule line category in the sales order. In this case, the R/3 strategy should not
contain customer requirements classes. In other words, the system should not automatically transfer a
check mode. Then enter the corresponding customer requirements class as a check mode.
There is a calendar in APO for the checking horizon. The system now automatically suggests the
production calendar for the particular location. You can, of course, change this setting later.

© SAP AG AP205 Preface-75

 ATP Customizing

Integration model ATP Customizing

Prerequisite:
Application ATP_CUST Import Customizing
Availability check Permitted

ATP Customizing
R/3 Customizing
APO
Checking grp ATP group

Business event
Checking rule

Requirements Check mode

class Assignment mode
[Link] (standard/characteristics)

Check control
Scope of with scope of
check check
© SAP AG 2001

For the transfer of ATP settings from the R/3 material master into APO, note that the system must first
transfer the ATP Customizing into APO. You can select the ATP Customizing from an integration
model, where the import of Customizing settings in the APO System is permitted (Customizing step
Maintain Global Settings for Availability Check).
If you perform the availability check in APO and not in R/3, then you define an integration model,
where you choose the indicator availability check and enter the materials for which the ATP check
should perform in APO, in the material selection.
During the transfer of the ATP Customizing, the R/3 checking group is displayed in an ATP group
with the same indicator.
The system transfers the R/3 checking rule as a Business Event with the same name.
The system displays the requirements class in R/3 in the check mode in APO. This ATP check mode is
new and contains the assignment mode (that controls the function of allocation of customers and
planned independent requirements) and the production type (standard or characteristic for the planning
of variants).
The system then transfers the R/3 scope of check to the APO check control that contains the scope of
check.

© SAP AG AP205 Preface-76

 Requirements Strategies

Material A Product A
APO
MRP 3 Demand
Planning
Requirements strategy
Strategy group PP
Default strategy
10 10 Make-to-stock productn
40 20 Planning w. final assemb.
Main strategy
50 30 Planning w/out final ass.
60 40 Planning product
70 20 Planning w. final assemb.

Mixed MRP ind. 1 Subassembly planning

Strategy 70 Default strategy 20

+ equals +
Mixed MRP indic. 1 Subassembly planning
© SAP AG 2001

The system transfers the planning strategies in the R/3 material master into the APO product master,
via the R/3 APO interface. Note, therefore, that the logic varies in both systems (even the numbers that
indicate the strategy in R/3 and APO do not usually agree, because more R/3 planning strategies can be
displayed in APO with a requirements strategy).
The R/3 strategy group is maintained in the R/3 material master, and includes a planning strategy and
possible secondary strategies. The APO System always transfers the planning strategy from the R/3
strategy group: If strategy 10 (make-to-stock production),40 (planning with final assembly) or 70
(subassembly planning) appear as the planning strategy, the system will transfer the APO requirements
strategies relevant to these strategies into APO.
R/3 strategies of make-to-order production (strategy 20) are not explicitly transferred into APO, as
strategies are not needed for make-to-order production in APO. (APO strategies only basically concern
the planned independent requirements).
If you have copied a standard R/3 scheduling strategy in R/3 Customizing onto an individual
scheduling strategy, and entered this one as the main planning strategy in the strategy group of the
material master, (this main planning strategy is then called, for example, Z1 instead of 10) it will then
be analyzed in Customizing in the R/3 behind strategy Z1, so that the R/3 APO interface still transfers
a requirements strategy make-to-stock production in APO.
In the R/3 material master, you can also assign a strategy group to the material using an MRP group.
During the transfer of such a material into APO, the system also checks and, if necessary, transfers
these settings.

© SAP AG AP205 Preface-77

 Consumption

Material A Product A
APO
MRP 3 Demand
Planning Consumption
1 1
Consumption mode 2 Consumption mode 2
3 3

[Link] 30 [Link] 30
[Link] 20 [Link] 20

Settings for consumption

from the MRP group? Analog transfer
takes place

© SAP AG 2001

The system transfers the settings for the allocation of sales orders and planned independent
requirements from the R/3 material master via the R/3 APO interface. Because consumption mode 4
does not exist in APO and is not recommended by SAP, the system does not transfer this setting.
In the R/3 material master, you can also assign the consumption to the material via an MRP group.
During the transfer of such a material into APO, the system also checks and, if necessary, transfers
these settings.

© SAP AG AP205 Preface-78

 Individual and Collective Requirement

APO
Product A
Material A
Demand
MRP 4
Dependent requirements
Dependent requirements
always collective reqmts
Indiv./collective 2 exclusively coll.
poss. [Link] reqmts
Order netw. (fix. pegging)

Product A
APO
Material A
Demand
MRP 4
Dependent requirements
Dependent requirements
always collective reqmts
Indiv. and coll.
Indiv./collective 1 exclusively indiv. poss. [Link] reqmts
Order netw. (fix. pegging)

© SAP AG 2001

The system transfers the individual/collective requirement setting for dependent requirements from the
R/3 material master to the APO product master via the R/3 APO interface: If the individual/collective
indicator has a value of 2 (excluding the collective requirement), then you set always collective
requirement in the APO product, and the indicator possible individual customer requirement for the
values blank or 1.
In APO, you can only maintain the individual/collective indicator in the product master.

© SAP AG AP205 Preface-79

 Static Lot-Sizing Procedure

Material A Product A APO

MRP 1 Lot size
Lot-sizing data Procedure
EX Exact lot size Lot-for-lot
Lot size
HB Replenish to Fixed lot size
[Link] Maximum product
Max. stock level 100 warehouse capacity 100

Material A Product A APO

MRP 1 Lot size
Lot-sizing data Procedure

Lot size FX Fixed lot size Lot-for-lot

Fixed lot size 100 pc Fixed lot size 100 pc

Periodic [Link]
Customizing lot size FX
Lot size indicator F Fixed lot size

© SAP AG 2001

The system can transfer the static lot-sizing procedure of lot-for-lot order quantity, fixed lot sizes and
period lot size procedures from the R/3 material master to the APO product master, via the R/3 APO
interface.
The system transfers the lot-sizing procedure of Lot-for-lot order quantity in the R/3 material master
onto the equivalent Lot-for-Lot lot size in the APO product master.
The system transfers the fixed lot size in the R/3 into APO as a fixed lot size. The system reverts to the
Customizing of the R/3 lot-sizing procedure (see Customizing step Check lot-sizing procedure): If lot
size indicator F is defined, then set the fixed lot size in APO. The system also transfers the value for
the fixed lot size specified in the R/3 material master.
The system transfers the Replenish up to maximum stock level lot-sizing procedure in the R/3
material master, lot-for-lot into the APO product master, as APO displays the procedure of
replenishing to maximum stock level differently. Replenish up to max. stock level is possible in APO
in connection with consumption-based reorder point planning that is controlled in APO by a heuristic
in the product master, which can be combined with any other lot-sizing procedures (for example, the
fixed lot size in connection with rounding values). The system transfers the reorder point and
maximum stock level maintained in the R/3 material master into the R/3 APO interface, as reorder
point and maximum product warehouse capacity.
The system transfers the indicator Lot size of sales order planning in the R/3 lot-sizing procedure
(defined in Customizing) into the APO product master: If you are working with the lot size in the short
term horizon, in the sales order planning of the R/3, the indicator Always lot-size is set in the APO
product master.

© SAP AG AP205 Preface-80

 Periodic Lot-Sizing Procedure

Material A Product A APO

MRP 1 Lot size
Procedure
Lot size PL Period. lot size
Lot-for-lot
Customizing lot size PL Fixed lot size

Lot size proced. P Period. lot size Periodic

D Day D Day

Lot size indicator W Week Period indic. W Week

M Month M Month

Period number 1 Number of periods 1

Date determination
Reqmts date
Indic. avail. Period
Conf. of date 1 Start of period X 0
dates factor
2 End of period X 1

© SAP AG 2001

The system can also transfer the periodic lot-sizing procedure of the R/3 material master into the APO
System.
The system reverts to R/3 Customizing, that you can find behind the lot-sizing procedure in the R/3
(see R/3 Customizing step Check lot-sizing procedure). If the lot-sizing procedure P is defined for the
period lot size, a period lot size is set in APO too. The lot size indicator determines in Customizing,
which period indicator the system will transfer into APO: The period indicators D (day), W (week), M
(month) can be transferred. If you want to use periodicity H (hour) and transfer the data from the R/3,
then you use a customer exit (as the periodicity H (hour) is not implemented in the R/3). The system
also transfers the number of periods, within which the procurement quantity should be summarized.
In a similar way, the system then transfers the indicator Date determination in R/3 Customizing of the
lot-sizing procedure into APO: For the setting availability date=requirements date, the availability
date indicator in the product is set to blank, for the setting availability date=start of period the
availability date indicator is X and the period factor is 0, for the setting availability date=end of period
the availability date indicator is X and the period factor is 1.
In the APO product master, you can also use any period factor (for example, 0.5) to make the
availability date of the procurement element exactly half (0.5), for example, of the period. If you want
to use such a period factor and transfer the data from the R/3, then you use a customer exit (as the
period factor 0.5 is not implemented in the R/3).

© SAP AG AP205 Preface-81

 Lot Size Parameter

Product A APO
R/3 Lot size

Minimum lot size 10 pc

Maximum lot size 200 pc
Assembly scrap 10 %
Rounding value 5 pc
Matl. A APO Customizing:
Rounding profile 0001 Is the rounding
Lot size profile known?
data Safety stock 30 pc
Service level 95 %
Reorder point 80 pc
Prod. warehouse
Max. stock level 80 pc
capacity

© SAP AG 2001

The system can transfer many lot size parameters from the R/3 material master into APO.
APO contains planning functions that do not exist in the R/3. For this reason, extra maintenance of the
lot size parameters may be necessary in the APO product master, if functions without equivalents in
the R/3 are used.
The system transfers the assembly scrap from the R/3 material master into APO. Note that the logic for
the calculation of the scrap in R/3 does not totally agree with the logic in APO.

© SAP AG AP205 Preface-82

 SNP2, PP/DS, Procurement and GR/GI

R/3 Product A APO

Material A
Purchasing SNP2

Purchasing group 001 Purchasing group 001

MRP 2 PP/DS

[Link] key 001 Call horizon 10 days

Call horizon 10 days
Safety time 2 days Procurement
...
Procurement type E Procurement type E
[Link] 14 days [Link] time 14 days

GR/GI
GR processing 3 days GR processing time 3 days

S and D: gen./Plant Loading group 0001

© SAP AG 2001

The system transfers the purchasing group from the R/3 material into the APO product.
The call horizon is defined in the R/3 material by the scheduling margin key for floats. The system
transfers this call horizon into the APO product.
The procurement type, planned delivery time, goods receipt processing time and the loading group of
sales and distribution are also transferred.

© SAP AG AP205 Preface-83

 Maintaining Additional Product Master Fields in APO

Mass maintenance for product master fields in

APO (for those that cannot be transferred from the
R/3 System)
Alternative solution using modification:
Enhancement of the R/3 material master record
with customer-specific fields (Append structures)
and transfer of these fields in the integration
model (using a customer exit)

© SAP AG 2001

You can use mass maintenance to subsequently maintain product master records that you have copied
from R/3 (call from the initial screen in product master maintenance). In mass maintenance you can,
for example, maintain fields that are not transferred from R/3, because these fields do not exist there.
Alternative solution using modification: You can extend the R/3 material master using customer-
specific fields (Append structures, see SAP note 44410).
You can also enhance the R/3 material master, so that the you can maintain the settings for functions
that do not exist in R/3 in the R/3 material master. For the CIF transfer for these fields, you need to
note that you need to enhance CIF in the R/3 outbox and the APO inbox to define that these fields are
transferred (customer exits for material masters).

© SAP AG AP205 Preface-84

 Master Data: Overview (3)

R/3 APO
R/3 master data APO master data

Plant
Customer Location

Vendor

Material master Product

Work center/capacity Resource

Routing and Production

bill of material process model

© SAP AG 2001

An R/3 work center (for example, a PP-PI resource) can contain several capacities with different
capacity categories: For the production of a material in this work center, all capacities are necessary.
APO displays each capacity category as a single resource. The transfer of a work center into APO can
result in several resources.
Work center hierarchies from the R/3 are not supported in APO.

© SAP AG AP205 Preface-85

 Resource Categories

Transferable from R/3

Production Transport

Store Handling

© SAP AG 2001

The resource category determines the use of a resource.

The resources transferred from the R/3 are basically production resources (resource category P).
In APO, capacity planning can also take place for other resource categories (for example, Store). You
must create these resources manually in APO.

© SAP AG AP205 Preface-86

 Resources in APO

Single-activity resources (PP/DS)

Time-continuous
Available capacity for one activity
Multi-activity resources (PP/DS)
Time-continuous
Transferable from R/3 Available capacity for multiple activities
Bucket resources (SNP)
Time intervals
Available capacity per time interval
Mixed resources (PP/DS and SNP)
Transferable from R/3 with customer exit

© SAP AG 2001

Resources are APO master data, in which capacities and working times of machines, personnel,
vehicles and warehouses are defined.
Resources can be defined as single-activity resources, multi-activity resources or bucket resources.
The single/multi-activity resources can be used for continual and exact time scheduling. Production
Planning and Detailed Scheduling use single-activity and multi-activity resources. The system can
transfer them from the R/3.
Bucket-resources are used for medium and long-term scheduling in the Supply Network Planning
(SNP). The time periods are at least one day long.
Mixed resources can be used in both SNP (bucket-orientated scheduling) and in PP/DS (time-
continuous scheduling). You can transfer mixed resources from the R/3 with the help of a customer
exit.
There are also vehicle resources (for the APO transport planning) and line resources (for automotive
processes) available. The system cannot transfer both of them from the R/3.

© SAP AG AP205 Preface-87

 Work Center and Resources

An APO resource for each R/3 work center capacity

APO
Plant 1000 Resource
APO
2 multi mixed Customer exit:
Work center 1904 Mixed resource
Resource Cat. Location
Capacities

Cap. category 001 Machine W1904_1000_001 P 1000

Cap. category 002 Person W1904_1000_002 P 1000

"Work center" R/3 plant

© SAP AG 2001

During the transfer of a R/3 work center into APO, each capacity category is displayed in its own
resource. These resources are independent of each other in APO.
The resources in APO must have unique names. The transfer takes place according to the following
naming convention: The name of the work center will start with a W, then comes the plant from which
the work center, and then the capacity category comes at the end.
R/3 work center capacities are normally transferred as "production" type multi or single-activity
resources. Unlike mixed resources, these resources can only be used in PP/DS.
If you want the system to create mixed resources during the transfer, to be used in SNP as well as
PP/DS (bucket resources), then you use a customer exit. (Note 329733).
If you use mixed resources, then activate a customer exit for PPM (Note 321474).

© SAP AG AP205 Preface-88

 Single and Multi-Activity Resources

R/3 Plant 1000

Work center 1904
Resource
APO
Capacities

Cap. category 001 Machine Single-activity

Work center capacity Resource Cat. Location
Work. time 7:00 to 15:00
... W1904_1000_001 P 1000
No. [Link] 1
Several operations
Multi-activity
No. [Link] 1
Resource Cat. Location
Several operations
W1904_1000_001 P 1000
No. [Link] 3
Several operations

© SAP AG 2001

Single-activity resources can only be used by one operation, whereas with multi-activity-resources,
several operations can be scheduled at the same time. The system displays R/3 work center capacities
with only one individual capacity that cannot be used by several operations, on single-activity
resources. Similarly, the system displays R/3 work center capacities that either possess more than one
individual capacity or that can be used by more than one operation, on multi-activity resources.
During the transfer of the R/3 work center capacity, only the data from the standard available capacity
is considered (for the option of single or multi-activity resource) or copied. The system does not
transfer possible available capacity intervals that differ from the standard available capacity!
A R/3 work center capacity can have more than one individual capacity but cannot be used by several
operations. This case cannot be displayed in APO in this form, as this capacity is displayed on a multi-
activity resource.
You can only use setup matrices with single-activity resources.

© SAP AG AP205 Preface-89

 Resource Data

APO
Work center 1904 Resource W1904_1000_001
DE Machine cap. final assembly
Capacities
General data
Cap. category 001
Machine capacity Time zone CET
APO Customizing:
final assembly Factory calendar 01 Has factory calendar
been created?
Active version 1
Capacity
Factory calend. ID 01 Standard capacity
Active version 1
Work. time 7:00 to 15:00
Standard avail. capacity
Break duration 1 hour
Work. time 7:00 to 15:00
Break duration 1 hour Resource utilization 100%
Resource utilization 100% Capacities 3,000
No. [Link] 3
Planning parameters
Planning details
Rel. for finite scheduling Finite scheduling
R/3
© SAP AG 2001

During the transfer of an R/3 work center, the system creates one APO resource for each capacity
category. The corresponding resources adopt the short text of the capacity. You can maintain the short
text in APO in more than one language. If the R/3 work center capacity does not have a short text, then
the name of the work center is supplemented in APO with the capacity category (for example,
1904_001).
The system transfers the factory calendar ID and the active capacity version. The system does not
automatically transfer the factory calendar itself (the corresponding Customizing). Application
Customizing cannot generally be transferred via an integration model from the R/3. (Exception: Plant,
MRP area, ATP). Basis Customizing (factory calendar, units) can be transferred via the SAP transport
system.
The system transfers the standard available capacity of the active capacity version and the number of
individual capacities. The system does not automatically transfer intervals that vary from the standard
available capacity and that you have defined in the R/3!
The system transfers the rate of resource utilization of the R/3 capacity. The system does not transfer
the field Overload, with which you can allow a percentage overload on a capacity in the R/3, into the
APO resource. The rate of resource utilization represents the corresponding function.
When you set the indicator Relevant for finite scheduling in the R/3 capacity, the system activates the
indicator Finite scheduling in the relevant APO resource during the transfer.

© SAP AG AP205 Preface-90

 Reference Resource

R/3 Plant 1000

Work center 1905
Capacities Resource
APO
APO
Cap. category 001 Machine 2 multi mixed Customer exit:
Mixed resource
Ref. avail. capacity Resource Cat. Reference resource
Plant 1000 W1905_1000_001 P K1900_1000_001
Capacity K1900
K1900_1000_001 P
Cap. category 001

Standard avail. capacity

Work. time 7:00 to 15:00 Transfer of
1 hour
reference available capacity;
Break duration
APO name contains no
No. [Link] 3 W (for work center)

© SAP AG 2001

In the R/3, a reference available capacity can be assigned to a work center capacity: The system
transfers the available capacity of the reference available capacity.
The transfer of a work center capacity containing a reference available capacity results in two
resources in APO: The system transfers the reference available capacity as an individual resource
(reference resource), therefore this resource name does not start with a W. The system transfers the
work center resource (containing a copy of the capacity data of the reference resource), and the
reference resource is assigned to it.

© SAP AG AP205 Preface-91

 Definition of Capacity Variants (1)*

1st step: Create break pattern General

Data

Resource
master data
capacity
variants

Standard
capacity

Break 1
Break 2
Break 3 Break data
Break pattern B
Break pattern
Break 1
Break 2 Break number
Break 3 Planner
Break pattern C
Start / end of break
Break 1
Break 2 Break after hours / break duration
Break 3

© SAP AG 2001

The star (*) on this slide and the following slides means that they contain additional information, that
does not directly concern the integration of master data. These slides are intended as an appendix.
In a break pattern, you define breaks for a shift, independently of a particular shift.
You can define each break either by specifying a start and finish time, or by entering the break duration
and the start of the break in relation to the start of the shift.
You use a break pattern in a shift definition.

© SAP AG AP205 Preface-92

 Definition of Capacity Variants (2)*

2nd step: Create shift factors General

Data

Resources
master data
capacity
variants

Standard
capacity

Shift factors
Shift factor data
..
Capacity Shift factor definition
Resource utilization Validity
...
Planner
Capacity
Unit of measure
Resource utilization

© SAP AG 2001

In a shift factor definition, you define the resource utilization and the capacity for a shift,
independently of a particular shift.
The capacity and the unit of measure for the capacity are only relevant for multi-activity resources.
Single-activity resources have capacity 1 without a unit of measurement.
You use a shift factor definition in a shift definition.

© SAP AG AP205 Preface-93

 Definition of Capacity Variants (3)*

3rd step: Create shifts

General capacity
Data variants

Resources
master data

Standard
capacity

Break pattern B Shift factors

Break 1
Break 2 Capacity
Break 3 Resource utilization

Shift A

Break model data Shift data Shift factor data

Break pattern Shift definition Shift factor definition
Break number Validity Validity
Planner Planner Planner
Start/end of break Start/end Capacity
Break after hours Break pattern Unit of measure
Break duration Resource utilization
Shift factors

© SAP AG 2001

In a shift definition, you define the working times, breaks, resource utilization and capacity for a shift.
You use a shift factor definition to define the resource utilization and the capacity in the shift.
You can use a break pattern to define the breaks in a shift.
Instead of using a break pattern, you can specify the absolute duration of the breaks for the shift.

© SAP AG AP205 Preface-94

 Definition of Capacity Variants (4)*

4th step: Create shift sequences

General capacity
Data variants

Resources
master data

Standard
capacity

Shift C Shift C
Shift B
Shift Shift A
sequence
Shift B

Day Shift A
Shift sequence data
Shift sequence
Shift data
Day number Shift definition
Validity ...
Planner
Non-workdays
Shift 1
...
Shift 9
© SAP AG 2001

In a shift sequence, you define the daily sequence of shifts for as many consecutive days as you want.
For each day, you can specify up to nine shifts.
The shifts for one day can overlap, but they must have different start times.
The last shift of one day may finish the following day.
You can also use a shift sequence to define the working times and the capacity in a particular time
interval of a capacity variant.

© SAP AG AP205 Preface-95

 Definition of Capacity Variants (5)*

5th step: Create capacity variants

General capacity
Data variants

Resources
master data

Standard
capacity

Shift
sequence 1 2 3 4 5 1 2 3 4 5 12 23 34 15 2 3 1 21 32 3 4 5
per day

Interval 1 Interval 2
Interval 1 Interval 2
Var. 1 Interval 1
Time Interval 2

Var. 2 Time
Var. 3

Shift sequence data Capacity variant data

Shift sequence Resource
... Location
Capacity variant no.
Validity
Workdays
Shift sequence Interval
Day one
© SAP AG 2001

To define working times, break times, resource utilization and capacity in a particular time interval of a
capacity variant, you assign a shift sequence to the time interval.
First Day specifies which day of the shift sequence falls on the first day of the time interval.
Workdays specifies whether the days in the interval are workdays, non-workdays or workdays
according to the factory calendar.

© SAP AG AP205 Preface-96

 Capacity Definitions: Overview*

General capacity

Break 1 Data

Resources
variants

Break 2 Standard
master data

Break 3 capacity

Break pattern B
Break 1 Shift factors
Break 2 Capacity
Break 3 Resource utilization

Break pattern C
Break 1 Shift A
Break 2
Break 3

Shift
sequence 1 2 3 4 5 1 2 3 4 5 12 23 34 15 2 3 1 21 32 3 4 5
per day

Interval 1 Interval 2
Interval 1 Interval 2
Var. 1 Interval 1
Time Interval 2

Var. 2 Time
Var. 3
© SAP AG 2001

To define working times, break times, resource utilization and capacity in a particular time interval of a
capacity variant, you assign a shift sequence to the time interval.
To define shift sequences you use:
Break patterns
Shift factor definitions
Shift definitions

© SAP AG AP205 Preface-97

 Determination of Capacity in APO*

When is the reference resource relevant?

APO
Does an
No active Yes
capacity
variant
exist?

Does Does
Yes a reference No No a time interval Yes
with valid
resource
exist? capacity
exist?
Does
No a reference Yes
resource
exist?

Do the
same variants
Check carried out in:
with valid time
No intervals Resource
exist?
Reference resource
Capacity from:
Yes
Resource
Standard capacity Standard capacity Time interval of Time interval
of reference resource of resource reference resource of resource Reference resource

© SAP AG 2001

In APO, if a reference resource is assigned to a resource, the capacity of the reference resource is not
necessarily relevant for scheduling.
In a resource you can define the capacity data (working times, break times, resource utilization and
capacity of the multi-activity resource) in different forms:
a) as standard available capacity
b) in up to 99 capacity variants, one of which you can specify as the active variant
c) in the reference resource.
You can specify more than one record of capacity data (standard available capacity, active capacity
variant and capacity of reference resource) for a resource at a time. The slide shows which logic in
APO determines the capacity valid for a resource.

© SAP AG AP205 Preface-98

 Pooled Capacities

R/3 Plant 1000

APO
Work center 1906 Resource
APO
Capacities 1 multi mixed Customer exit:
Cap. category 002 Person Mixed resource
Resource Cat. Location
Pooled capacity POOL
POOL_1000_002 P 1000
Standard avail. capacity
Work. time 7:00 to 15:00
Break duration 1 hour Transfer of pooled capacity
No. [Link] 10 APO name contains no
W (for work center)

© SAP AG 2001

The system can transfer into APO pooled capacities that are assigned to a R/3 work center. The system
does not only transfer the individual work center capacities, to which the pooled capacity is assigned,
but also the pooled capacity itself.
As far as the data transfer is concerned, the system transfers the pooled capacities just like it does
normal resources (the available capacity is also transferred), except that the resource name starts with a
W.

© SAP AG AP205 Preface-99

 Master Data: Overview (4)

R/3 APO
R/3 master data APO master data

Plant
Customer Location

Vendor

Material master Product

Work center/capacity Resource

Routing and Production

PPM
bill of material process model

© SAP AG 2001

The R/3 routing and bill of material are mapped in APO on a production process model.
In the same way, the R/3 master recipe (PP-PI) can be mapped onto an APO production process model
(see appendix).
The following technical BOM categories are supported in the CIF interface: Simple BOMs, multiple
BOMs (the relevant alternative is specified in the production version), variant BOMs (different
material numbers are produced with the same super BOM).

© SAP AG AP205 Preface-100

 Overview of Production Process Model

Header: Costs, output products, lot size range

Operations:
e.g.
Rotate Activities:
Weld Setup
Paint Produce Product Input/output
Check Tear down Relations Sequence
Resources

Resource consumption

© SAP AG 2001

The Production Process Model (PPM) defines the detailed information required for manufacturing a
product. It combines the routing and the bill of material into one master data object.
The PPM has validity parameters determined by lot size and time intervals. The variable costs defined
for a PPM include the costs of input material as well as the cost of production as penalty costs.
The PPM for Supply Network Planning requires less information than the PPM for Production
Planning/Detailed Scheduling (PP/DS). You can therefore set different uses in PP/DS and SNP PPMs.
The system can generate the PPM and usage PP/DS via the R/3 APO interface. There is a report in
APO, however, that helps with the generation of SNP PPM from the PP/DS PPM. (Call this up from
the initial screen of the PPM).

© SAP AG AP205 Preface-101

 R/3 Production Version and APO-PPM

R/3 Material A
MRP 4
Plan N500077010001
APO
Production version 0001
describes production process
Production process
No. 500077 model (PPM)
Routing
Product A

Bill of material

© SAP AG 2001

For the CIF transfer of the routing and bill of material as a production process model (PPM) into APO,
a valid production version must be available in the material master of the corresponding material. The
production version determines a manufacturing process by specifying a routing and a bill of material.
A PPM corresponds with the assignment of a product to a plan. A plan can be assigned to several
products, and therefore contain several PPMs.
In the R/3 material master, several production versions can be defined for different lot size intervals.
Each of these production versions is transferred into APO as an individual plan and PPM. The
individual plans differ by group counter.
The PPMs that are transferred from the R/3 have usage P: They can be used in APO for Production
Planning and Detailed Scheduling (PP/DS). If the plans are also used for the supply network planning
(SNP), they must be copied as PPMs with the usage S. There is a special report for this available in
APO.

© SAP AG AP205 Preface-102

 Task List Description in APO

R/3 Material A
Production version 0001

Routing
No. 500077
Group counter 01

Bill of
material

PPM
APO Plan No. N500077010001
Product A
© SAP AG 2001

When a plan or production process model is created in APO, as a transfer of a routing/bill of material
from an R/3 production version, the origin is clearly a derivation of the plan number: The plan number
in APO is composed of the routing number of the R/3 (expressed by a number that specifies the routing
type - for example, N for a normal routing, R for a line routing, 2 for a master recipe (process industry)
and A for a general maintenance task list), the group counter and the description of the production
version. The system transfers reference operation sets in routings in the same way as normal routings).
The system transfers a description of the routing into APO as a plan text, and the brief description of
the production version is transferred as a PPM text.
The standard APO System does not yet support these functions of the R/3 routings and bills of material
so can therefore not transfer them: Engineering change management, phantom assemblies and
dependencies.
If one routing is used in several production versions, the plan number in APO includes the material
number and plant. (For example, for material A in plant 1000: N500077010001A1000). The system
only transfers the production versions that are valid at the time of selection in the integration model. If
you set the selection date to indefinite (31.12.9999), then the system transfers everything that is valid.

© SAP AG AP205 Preface-103

 Structure of the Production Process Model (1)

APO Plan N500077010001

PPM Product A

Operation 10
Setup activity
Assembly
Components
Links

Produce activity

Links
Operation 20
Produce activity
Checks

...
© SAP AG 2001

The Production Process Model (PPM) in APO contains the information required for manufacturing a
product. It represents the combination of routing and bill of material for a master data object.
A PPM contains one or more operations (you can maintain the short texts of the APO-PPM operations
in different languages). Each operation includes at least one activity. (These activities may be produce,
setup, tear down or wait). The components consumed (or produced) by the activity are assigned to the
activities. The sequence of activities within the operation is defined by the relationships.
The transfer of R/3 master data can result in two types of relationship: Finish-start relationships, where
the end of one activity starts another, and start-start relationships, where two activities start at the same
time.

© SAP AG AP205 Preface-104

 Structure of the Production Process Model (2)

Activities and resources

PPM Product A Selection of mode

is dynamic when
Operation 10 scheduling

Produce activity

Mode 1
Primary resource W1904_1000_001

Secondary resource W1904_1000_002

Mode 2
Primary resource W1905_1000_001

Secondary resource W1905_1000_002

© SAP AG 2001

The mode determines the resource and the capacity requirement needed to execute an activity. As well
as the primary resource that is relevant for scheduling, you can enter one or more secondary resources
in a mode. Also during the scheduling of secondary resources, the system transmits capacity
requirements.
You can assign several modes to one activity, that is, several alternative resources (resource records)
can be assigned, and the system can then process the activity. During scheduling in PP/DS, the system
automatically selects a mode, the mode that starts last, in consideration of the available capacity.
It is possible to work with your preferred modes for the optimization in PP/DS. You can therefore give
the modes different priorities. (At the moment, only one mode is transferred from the R/3. Alternative
modes can be maintained manually in APO.)

© SAP AG AP205 Preface-105

 Operations in PPM

R/3 Material A
Plan N500077010001
APO
Routing 500077
PPM Product A
Operation 10
Assembly Operation 10
Control key Assembly
No control key
PP01 is transferred
in APO
Relevant to
scheduling
However, the following are not
Operation 20 transferred:
Control key Operations without work center
is not (in active integration model)
PP02 transferred
Operations without valid duration
(because formulas or standard
Relevant to
values are missing)
scheduling
© SAP AG 2001

The operations in a R/3 routing correspond with operations in APO PPM. The system transfers all R/3
operations that are relevant to scheduling and have a corresponding control key. The system does not
transfer operations that are not relevant to scheduling.
The system does not transfer operations if: There is no work center in the R/3 operation and no work
center in any active integration model, and if there are no scheduling results unequal to zero (partly
because there are no formulas or standard values available).
The operation numbers remain during the transfer.
The system transfers R/3 sub-operations as APO operations.
The system transfers parallel sequences of a R/3 routing into APO: The system then creates the
corresponding operations and provides them with relationships so that they operate as parallel
sequences.
You can transfer alternative sequences of an R/3 routing using a customer exit.

© SAP AG AP205 Preface-106

 Scheduling and Activities

Scheduling
basis
Operation 30 Assembly

Work center 1904

Operation 30 Assembly APO
Standard Cap. 001 002
value
Setup activity
[Link]
Setup 5 MIN CIF
1. Setup Primary res. W1904_1000_001
Fixed duration 0,083 H
Machine 15 MIN
Produce activity
HR
Primary res. W1904_1000_001
2. Processing Variable duration 0,250 H per 1 pc
Variable1
Secondary res. W1904_1000_002
Variable2
3. Tear down
Variable3

© SAP AG 2001

The operations of a production process model include activities where you will find a description of
the actual process steps for the operation. During the transfer of an R/3 routing, the system creates the
activities of the APO PPM operation relevant to the R/3 operation.
A work center is assigned to an R/3 operation. The work center specifies which time elements can be
taken into consideration during the scheduling (for example, setup time, machine time, personnel time)
with the help of a standard value key. The scheduling formulas stored in the work center define the
duration from the allowed time elements in the routing.
The setup, processing and tear down of an R/3 operation are all displayed in APO activities. During the
CIF transfer of a routing, the scheduling formulas of the relevant work center are also interpreted, in
order to create the corresponding activities in PPM with their durations.
The activities of the PPMs include a mode with a primary resource each. These primary resources
correspond with the capacity selected in the work center as a scheduling basis. Other possible
available capacities that are not relevant for scheduling are displayed using secondary resources.
The capacity requirements of the individual process steps result from the scheduling formulas defined
in the work center and the time elements of the routing. The system stores them in APO PPM as
variable or fixed durations (the variable durations relate to the output quantity of the last operation of
PPM).
The durations are specified in the APO activity, in the base unit of measure of the R/3 capacity relevant
for scheduling (shown in Hour (H) in the slide).

© SAP AG AP205 Preface-107

 Overview of Activity Relations

START-START FINISH-START
Activity 1 Activity 1
Min. time deviation Min. time deviation

Activity 2 Activity 2
Max. time deviation Max. time deviation

Time Time

© SAP AG 2001

There are two types of activity relationships:

1. Start-start relationship: The start times of two activities are correlated with each other.
2. Finish-start relationship: The end of one activity is linked with the start of the next activity.

© SAP AG AP205 Preface-108

 Activity Relations

Operation 30 Assembly Operation 30 Assembly APO

Work center 1904 Setup activity (S)
Formulas
1. Setup
Relation S(0030)-P(0030)

2. Processing Produce activity (P)

3. Tear down Relation P(0030)-T(0030)

Minimum wait time Setup activity (T)

Maximum wait time
Move time Relation T(0030)-P(0040)
Minimum/maximum duration
Operation 40 Checks
Work center 1905
Operation 40 Checks

Processing Processing activity (P)

© SAP AG 2001

The "activities" of an R/3 operation, setup, process and tear down are transferred in this order into
APO PPM as activities. The activity relationships define the order of APO activities. During the CIF
transfer of an R/3 operation, the system creates these activity relationships automatically, as preceding
and subsequent relationships within an operation.
The operation number determines the sequence of the individual operations of an R/3 routing. A
corresponding activity relationship between the last activity of one operation and the first activity of
the following operation defines this sequence in APO PPM too.
Possible available wait or move times that determine the time interval of the follow-up operation in the
R/3 operation, are divided between two PPM operations in the activity relationship: The sum of the
minimum wait time and the minimum move time is transferred as the minimum duration. (The
maximum wait time of the R/3 operation is not relevant for scheduling and is therefore not transferred
into APO.)
R/3 sub-operations are transferred as APO operations with the activity produce. As R/3 sub-operations
are not relevant for scheduling (their dates are determined according to the lower-level operation they
are assigned to), the sub-operation activity is linked to a start-start relationship at the start of the
operation. Relevant for scheduling is also still the original main operation in APO.

© SAP AG AP205 Preface-109

 Component Assignment

PPM Product A APO

R/3 Material A
Operation 10
Production version 0001
Activity S
Routing Bill of material Input
Prod. B

Operation 10 Matl. A Operation 20

Activity S
Matl. B
Operation 20 CIF Input
Prod. C
Matl. C Input
Prod. D
Operation 30
Matl. D Operation 30
Activity P
Component assignment in Materials in
active integration Output
routing Prod. A
model?
© SAP AG 2001

In the R/3, bill of materials components in the routing can be assigned to individual operations. This
assignment of components is transferred into APO: The component assignment is displayed by input
components in activities. The assignment takes place for the first activity of the relevant operation.
The result of the production, the end product, is marked in APO as an output component. The output
component is assigned to activity produce (P) in the last operation of PPM (if activity P does not exist
here, then it is assigned to setup).
The system only transfers the component assignment for materials contained in an active integration
model. Direct procurement items and non-stock items are not transferred.
If materials are assigned in the R/3 to an operation that is not transferred into APO, then they are
assigned to the first operation in APO PPM (or more precisely: the first activity of the first operation).

© SAP AG AP205 Preface-110

 CIF Transfer of PPMs: Miscellaneous

The indicator Tear down/parallel wait time in the R/3

+ operation can be transferred

corresponding relationships in APO

You can transfer the operation-related lead-time offset of

+ the R/3 BOM item

Time-based offset of logical input components in

PPM

© SAP AG 2001

The system can transfer the indicator Tear down/parallel wait time in the R/3 operation, into APO in
the form of corresponding relationships (see note 321956 for details).

© SAP AG AP205 Preface-111

 APO Master Data: Unit Summary (1)

Basically, master data relevant for production

planning in R/3 can be transferred from the R/3
into the APO System. The additional maintenance
of master data in APO is generally only necessary
for functions that have no equivalence in R/3.
The R/3 master data for the plant, customer,
vendor and MRP area are displayed in APO as
locations with corresponding location types.
You can transfer material masters into APO as
products.

© SAP AG 2001

© SAP AG AP205 Preface-112

 APO Master Data: Unit Summary (2)

Work centers are transferred into APO in the form

of their capacities: for each work center capacity a
resource is created in APO.
The production process model in APO is a
combination of routing and BOMs. The transfer of
R/3 master data assumes the use of a production
version in the material master.

© SAP AG 2001

© SAP AG AP205 Preface-113

 Exercises

Unit: APO Master Data

Topic: Locations

At the conclusion of these exercises, you will be able to:

• Display APO locations resulting from the transfer from R/3

The production of pump T-F2## in plant 1000 is to be planned in

APO. Plant 1000, along with other plants, has already been
transferred to the APO System via the CIF interface.

1-1 Display production plant 1000 in the APO System (display this location).
1-1-1 Use the F4 help (in the Location type field on the initial screen for location
data maintenance), to enter the location type for the production plant. Which
type is for production plants? ___________________
1-1-2 Display production plant 1000. The data is arranged on several tab pages.
Click the Address tab page:
What is the name of the location? ________________________
Which address is entered for it (street and city)?
_____________________________________________________
Which time zone is assigned to plant 1000? _____________

1-2 In R/3, display the source of production plant 1000. In R/3, plants are defined in
Customizing. Display plant 1000 in Customizing.
1-2-1 What is the name of plant 1000? ______________________
1-2-2 Which address is entered for it?
_____________________________________________________
1-2-3 What is the time zone (hidden behind the Address icon)?
___________________

© SAP AG AP205 Preface-114

 1-3 Display other tab pages for location 1000 in APO. Here you will find a number of
settings that have no corresponding settings in the R/3 plant. If you want to use such
functions in APO, you must maintain these settings after you have transferred your
data to APO.

1-4 Display plant 2400 in R/3 Customizing.

1-4-1 What is the name of plant 2400? ___________________
1-4-2 The name implies that this plant is a distribution center (DC). Where is it
maintained in R/3?
_____________________________________________________
Make sure that plant 2400 is actually a DC.

1-5 Display APO location 2400 (location type 1002).

1-5-1 What is the name of this location? _________________________
(This location is of the type distribution center because plant 2400 was
transferred from R/3.)
1-5-2 What are the location types with which the following R/3 master data is
represented in APO (use the F4 help in the Location type field to answer this
question)?
MRP area: __________________________
Customer: __________________________
Vendor: __________________________

© SAP AG AP205 Preface-115

 Unit: APO Master Data
Topic: Resources

At the conclusion of these exercises, you will be able to:

• Display a resource in APO
• Describe the result of the transfer of an R/3 work center to
APO

The resources required to produce the pumps in APO have

already been transferred from R/3. Check the result of the
transfer.

2-1 Work center T-L## in plant 1000 is required to produce the pumps. Display the work
center in R/3.
2-1-1 What is the name of this work center? ______________
2-1-2 Which two capacities (with which capacity categories) are defined for this
work center?
_____________________________________________________
Which capacity is relevant for scheduling? ___________
2-1-3 Display more detailed data for the capacity with capacity category 001
(machine). Which standard available capacity is defined for this capacity?
_____________________________________________________
How many individual capacities does this capacity have? ___________
Can it be used by several operations? __________________
Is it relevant for finite scheduling? _______________
2-1-4 Which result do you expect when you see the result of the transfer of work
center T-L## into APO? (To answer this question, consider the results for
question 2-1-3):
How many APO resources are relevant to the work center? _____
Is capacity category 001 mapped onto a single-activity resource or a multi-
activity resource? Why?
____________________________________________________

© SAP AG AP205 Preface-116

 2-1-5 What are the names of the APO resources that result from the CIF transfer of
the R/3 work center T-L## of plant 1000?
____________________________________________________

2-2 The capacities of the R/3 work center T-L## of plant 1000 were transferred to the
training system as mixed resources using a customer exit. Both the machine capacity
(capacity category 001) as well as the labor capacity (capacity category 002) were
transferred as single-activity resources.
2-2-1 Display the APO resources WT-L##* in location 1000. Look at the single
mixed resources: Does one of these resources represent the R/3 work center
T-L## in plant 1000? _____________
2-2-2 Displayed more detailed information for resource WT-L##_1000_001: What
is the name of this resource?
____________________________________________________
Which standard capacity is defined?
____________________________________________________
Is this resource planned finitely in APO?
____________________________________________________

© SAP AG AP205 Preface-117

 Unit: APO Master Data
Topic: Production Process Model

At the conclusion of these exercises, you will be able to:

• Display a production process model in APO
• Describe the result of the transfer of a production version with
BOM and routing to the APO System

The production process models required to produce the pumps in

APO have already been transferred from R/3. Check the result of
the transfer.

3-1 Display the R/3 material master for pump T-F2## in plant 1000:
3-1-1 Are production versions defined for this material? ______________
3-1-2 Display the detail screen for production version 0001 (version 0001). Which
routing is defined here?
Group: _______________________
Group counter: _________________
Which BOM is selected?
BOM usage: _____________
Alternative BOM: _____________

3-2 Display the R/3 routing for the production of materials T-F2## in plant 1000 (you
just wrote down the number of the routing).
3-2-1 Which operations are required for production (what are the operation
descriptions)?
Operation 10: _____________________________________
Operation 20: _____________________________________
Operation 30: _____________________________________
Operation 40: _____________________________________
Operation 50: _____________________________________
Operation 60: _____________________________________

© SAP AG AP205 Preface-118

 3-2-2 Which components are used to produce this material (see the component
assignment in the routing to answer this question)?
___________________________________________________
Are the components explicitly assigned to an operation other than the first
one? _______________

3-3 Display the production process model (PPM) for the production of product T-F2##
in location 1000 in APO.
3-3-1 Compare the operations of the PPM with the R/3 operations of the
corresponding routing (which you wrote down above). Are the operation
descriptions the same? ____________
3-3-2 Look at the input components of operation 10. Which components are
assigned to this operation?
__________________________________________________

You will discover that the component T-T3## is not

available in the APO PPM.
This is because this component is not to be planned in APO.
Material T-T3## is therefore not contained in an active
integration model, and the PPM does not contain this
component.

3-3-3 Display more detailed information for operation 30 of the PPM.

Which activities does this operation have?
__________________________________________________
How many modes does the activity "produce" have? ________
What is the primary resource of the mode?
__________________________________________________
Which variable duration is defined for the activity at this resource?
________________
To which base quantity of the finished product does the variable duration refer
(notice the output component of the last operation)? _____________

© SAP AG AP205 Preface-119

 Solutions

Unit: APO Master Data

Topic: Locations

1-1 In the APO System, choose Master Data → Location → Location.

1-1-1 Production plant type: 1001
1-1-2 Location name: Hamburg
Address: Alsterdorferstr. 13, 22299 Hamburg
Time zone: CET

1-2 In R/3 Customizing, choose Enterprise Structure → Definition → Logistics -

General → Define, copy, delete, check plant
1-2-1 Plant 1000: Hamburg
1-2-2 Address: Alsterdorferstr. 13, 22299 Hamburg
1-2-3 Time zone: CET

1-3

1-4
1-4-1 Name of plant 2400: Milan Distribution Center
1-4-2 Defining a distribution center (DC) in R/3: Distribution centers are defined
in Customizing for DRP. Choose Production → Distribution Resource
Planning (DRP) → Basic Settings → Maintain assignment of node type –
plant. In the table that appears, define which plants are DCs.

1-5 In the APO System, choose Master Data → Location → Location.

1-5-1 Name of location 2400: "Milan Distribution Center".
1-5-2 MRP area: 1007
Customer: 1010
Vendor: 1011.

© SAP AG AP205 Preface-120

© SAP AG AP205 Preface-121
 Unit: APO Master Data
Topic: Resources

2-1 In the R/3 System, choose Logistics → Production → Master Data → Work Centers
→ Work Center → Display.
2-1-1 Name of the work center: Paint shop.
2-1-2 Capacities assigned to work center: Machine (capacity category 001) and
Labor (capacity category 002)
Capacity for scheduling: Machine
2-1-3 Standard available capacity: Work time from 7:00 am to 3:00 pm, with a
one hour break
Number of individual capacities: One
No, the capacity cannot be used by several operations.
Yes, the capacity is relevant to finite scheduling.
2-1-4 Work center T-L## is transferred to APO in the form of two resources.
Capacity category 001 is to be represented at a single-activity resource as the
number of individual capacities is one and the capacity cannot be used by
several operations.
2-1-5 Names of the APO resources corresponding to work center T-L##:
WT-L##_1000_001 or WT-L##_1000_002

2-2 In the APO System, choose Master Data → Resource.

2-2-1 Yes, the resources WT-L##_1000_001 or WT-L##_1000_002 are displayed
as single mixed resources in APO.
2-2-2 Name of resource WT-L##_1000_001: Machine capacity paint shop.
Standard available capacity: Just as in R/3, a work time from 7:00 am to
3:00 pm, with a one hour break
Yes, the resource is scheduled finitely (as a result of the Relevant to finite
scheduling indicator that is set in the R/3 work center).

© SAP AG AP205 Preface-122

© SAP AG AP205 Preface-123
 Unit: APO Master Data
Topic: Production Process Model

3-1 In the R/3 System, choose Logistics → Production → Master Data → Material
Master → Material → Display → Display Current.
3-1-1 Yes, (several) production versions are defined for this material in the material
master.
3-1-2 Routing in the production version:
Group: Varies, for example 50000402
Group counter: 1
BOM in the production version:
Usage: 1
Alternative BOM: 1

3-2 In the R/3 System, choose Logistics → Production → Master Data → Routings →
Routings → Standard Routings → Display.
3-2-1 Operations for production:
Operation 10: Stage materials according to picking list
Operation 20: Press rotor in casing
Operation 30: Paint casing RAL 1015 white
Operation 40: Build wave in casing
Operation 50: Final assembly of pump
Operation 60: Deliver to stock
3-2-2 The components T-B1##, T-B22##, T-B3##, T-B4## and screw T-T3## are
used in production. A document item is also available.
No, the components are not assigned to a different operation.

© SAP AG AP205 Preface-124

 3-3 In the APO System, choose Master Data → Production Process Model.
3-3-1 Yes, the operation descriptions are the same.
3-3-2 Components T-B1##, T-B22##, T-B3## and T-B4## are assigned to this
operation.
3-3-3 Operation 30 has the activities "produce" (P) and "Setup" (S).
The activity "produce" has one mode.
The primary resource of this mode is WT-L##_1000_001.
The variable duration is 0.333 hours (per output quantity of the finished
product).
The variable duration refers to one piece of finished product T-F2##.

Models and Planning Versions

Contents:
Models and Planning Versions for Master Data and
Transaction Data
Maintaining Models via the Supply Chain Engineer

© SAP AG 2001

© SAP AG AP205 Preface-125

 Models and Planning Versions: Unit Objectives

At the conclusion of this unit, you will be able to:

Describe the function of models and planning

versions for master and transaction data
Display master data via the Supply Chain
Engineer

© SAP AG 2001

© SAP AG AP205 Preface-126

 Overview Diagram (6)

1 Overview

2 Architecture of Integration

3 Transfer of Master Data

4 APO Master Data

55 Models and Planning Versions

5
6 Transfer of Transaction Data

7 Monitoring/Error Handling

8 Conclusion

© SAP AG 2001

© SAP AG AP205 Preface-127

 Models and Planning Versions

Master data Non-

R/3
R/3 System

Master data in APO Simulation

Simulation model n
model Z01
Active model 000
Resources Resources
Locations Resources
PPM PPM
Products PPM
Transportation Planning
Planning version
version 11
Version-dependent
Version-dependent master
master
lane
data
data and
and transaction
transaction data
data

Active
Active planning
planning version
version 000
000 Planning
Planning version
version 11 Planning
Planning version
version nn
Version-dependent
Version-dependent master
master Version-dependent
Version-dependent master
master Version-dependent
Version-dependent master
master
data
data and
and transaction
transaction data
data data
data and
and transaction
transaction data
data data
data and
and transaction
transaction data
data

© SAP AG 2001

The Supply Chain Model (abbreviated as model) represents the entire supply chain network ranging
from suppliers over production and distribution sites up to the customer. It includes locations,
transportation lanes, products, resources, and Production Process Models (PPM). Thus, the model is
the basis for all planning functions in APO. It contains only master data.
Master data from the R/3 System (or a non-R/3 System) is automatically assigned to the active APO
model (model 000) during the master data transfer to the APO System. The active model represents
the supply chain actually used in the enterprise. In this way, all master data transferred is automatically
available for operational planning in the APO model 000. Master data that you create manually in APO
must be explicitly assigned to one model.
If you want to plan another supply chain (for example, a different distribution center) in the simulation,
you can create an inactive model in APO. If you want to use certain master data in both the active and
inactive model, or in the inactive model alone, you must assign this master data to the inactive model.
You can either use the Supply Chain Engineer (SCE) as the modeling tool in APO or a manual
assignment from within master data maintenance (from the R/3-APO interface, master data is
automatically assigned to the active model only).
For simulation purposes, you can create several planning versions for a given supply chain model.
Note, however, that only model 000 and planning version 000 are active. The planning version
comprises master data and transaction data. In an inactive planning version, you can, for example,
simulate increased planned independent requirements and plan production based on an increased
demand. You cannot transfer the planning results from the inactive planning version to the active
version. You must repeat the planning in the active planning version.
You can use version management to copy models and planning versions or create them manually.
Note, however, that their names must be unique, which means that there may not be two planning
versions of the same name in different models. The active planning version 000 only exists in model
000.

© SAP AG AP205 Preface-128

 Models and Planning Versions for Locations and
Products

R/3 APO
R/3 Master Data APO Master Data
Simulation model Z01

Active model 000 Assignment

Active
Active planning
planning version
version 000
000
Plant,
Create
customer, vendor Locations Reference
master data
Material master Products Reference
Planning
Planning version
version 001
001
Locations Planning
version-specific
Products fields may be
added
(only valid in
version 001)

Maintained during master data Master data added

© SAP AG 2001 transfer

If locations and products are created in APO via the R/3-APO interface, they are automatically created
in the active planning version 000 and assigned to the active model 000.
If planning is simulated in an inactive planning version (for example, planning version 001), the
master data fields of the location and the product master of the active planning version 000 are read
(location and product in an inactive planning version thus refer to the active planning version 000).
If you want to use modified master data in simulated planning (for example, different MRP attributes
of a product), you can maintain certain fields specifically for the planning version in the location or the
product master in APO (manually or mass maintenance). During planning in planning version 001,
these version-specific fields from planning version 001 are then read. For fields that are specific to a
planning version, and can be maintained as such, the system reads the fields from active planning
version 000 (reference) if no alternative settings have been made.
If you also want to use certain locations and products in inactive models, you must manually assign
these locations and products to the inactive model required. You can do so from within master data
maintenance or via the Supply Chain Engineer. Within the inactive model, planning can be carried out
in one or several inactive planning versions.

© SAP AG AP205 Preface-129

 Models and Planning Versions for Resources

R/3 APO
R/3 Master Data APO Master Data
Simulation model Z01

Active model 000 Assignment

Independent
Independent of
of planning
planning
version
version
Create Copy
Capacity Resource
master data
Active
Active planning
planning version
version 000
000
Copy

Resource Planning
version-specific
Planning
Planning version
version 001
001 fields may be
added
Resource
(only valid in
version 001)

Maintained during master data Master data added

© SAP AG 2001 transfer

If resources are created in APO via the R/3-APO interface, they are automatically created in a
planning version-independent version 000 (planning version "blank") and assigned to the active
model 000. In addition, these planning version-independent resources are automatically copied into all
planning versions (active planning version 000 as well as all inactive planning versions) that exist in
this model during master data transfer. You are left with a planning version independent resource, an
active planning version resource, and some inactive planning version resources.
When version management is used to create a new planning version at a later stage, all resources are
automatically copied to the new planning version (as a copy of the planning version-independent
resource) when the new version is created. If the same resource is transferred via the R/3-APO
interface again, only the planning version-independent resource is overwritten in APO. The planning
version-dependent resources (resources for active and inactive planning versions) are not adjusted.
If planning is simulated in a certain planning version (for example, in the active planning version 000
or the inactive planning version 001), the resource master data fields in the relevant planning version
are read. If you want to use modified master data in the simulated planning (for example, different
operating times of resources in simulation), you can change the resources specifically for a planning
version in APO.
If you also want to use certain resources in inactive models, you must manually assign these resources
to the required inactive model. You can do so from within master data maintenance or via the Supply
Chain Engineer. When you assign the resource to the inactive model, the resource is automatically
created in all planning versions of the inactive model (copy of the planning version-independent
resources to the planning version-specific resources of the active model).

© SAP AG AP205 Preface-130

 Models and Planning Versions PPMs

R/3 APO
R/3 Master Data APO Master Data
Simulation model Z01

Active model 000 Assignment

Valid
Valid for
for all
all planning
planning versions
versions
Routing and Create
master data PPM
bill of material

Maintained during master data Master data added

© SAP AG 2001 transfer

If PPMs are created in APO via the R/3-APO interface, they are automatically assigned to the active
model 000. However, the PPM is valid in all planning versions. This means it does not depend on a
certain planning version. The only exception are time-dependent parameters in PPM, such as scrap,
resource consumption, material consumption (component quantity). You can plan them specifically for
a planning version in APO but cannot use the R/3-APO interface.
If you simulate planning in an inactive planning version (for example, planning version 001), the
same PPM is used as for operational planning. Modified PPM fields for simulated planning only are
not supported.
If you also want to use certain PPMs in inactive models, you must manually assign these PPMs to the
required inactive model. You can do so from within master data maintenance or via the Supply Chain
Engineer.

© SAP AG AP205 Preface-131

 Supply Chain Engineer (SCE) as the Modeling Tool
for Models

Network
Network structure
structure

Overview
Overview
Work
Work map
map
area
area
folder
folder

Planning
Planning
Network
Network map
map
objects
objects

© SAP AG 2001

You maintain the supply chain network in the Supply Chain Engineer (SCE), by placing locations on
the map and create a network by adding transportation lanes. The lane direction shows the direction of
the product transportation flow.
The SCE enables you to look at the data that belongs to particular elements in your supply chain. In
addition, it allows you to maintain the model objects simultaneously. You can make queries about
information via individual or combined elements in your supply chain. For example, you can query a
list of all the products belonging to a specific location in your model. At the same time, you can add
products to this location or make changes in the location master.

© SAP AG AP205 Preface-132

 Objects in the Supply Chain Engineer

Locations

Vendor Plant DC Customer Transport- MRP Stock transfer Carrier

ation area point
Transportation lanes zone

© SAP AG 2001

As well as locations and transportation lanes, the supply chain model also allows you to keep track of
other supply chain elements. These include products, PPMs (production process models), and
resources.
During supply chain modeling, you may have to assign or delete large numbers of objects in your
model. Many of these objects can have dependent objects assigned to them. To guarantee consistency
within the model, you can automatically assign or delete the dependent objects, together with the
primary object. Automatic assignment guarantees not only consistency but also enables easier model
maintenance.

© SAP AG AP205 Preface-133

 Work Areas in the Supply Chain Engineer

Access to frequently used objects

Used for queries
Serve as filters
Configured for users

© SAP AG 2001

If you have a lot of master data, viewing it in the network map in the Supply Chain Engineer can
become very confusing. To limit your view to only the master data you want to concentrate on, you
can define work areas. The work area is used exclusively as a filter for displaying objects in the
Engineer. You can maintain different work areas. This enables you to obtain manageable amounts of
data.
In the work area of the Supply Chain Engineer, you can select:
Locations (plant, distribution center, vendor, customer)
Products
Resources
PPMs (production process models)

© SAP AG AP205 Preface-134

 Transportation Lanes

Procurement
Means of transport
Products that can be carried
by a means of transport
Transportation capacity by
volume, weight, pallets
Transportation costs per unit,
product, and means of
transport

© SAP AG 2001

The transportation between two locations is defined through transportation lanes that are assigned to
a means of transport and through transportation-relevant attributes that must be described; for example,
transportation time and transportation costs. Means of transport describes the type of transport used
to transport goods between locations, for example, truck, ship, or plane.
A transportation lane could consist of a procurement view for procuring stock and a means of transport
view for transferring stock. In addition, you can make the following settings:
You can define the product procurement parameters like lot sizes, cost functions, unit costs and lane
priorities.
You can define the means of transport for each lane and the related parameters like transportation
costs, distances, and times.
You can assign product-specific means of transport.
You can assign carriers.
The arrows on the lanes show the traffic direction between source location and destination location.
You can maintain the lane-relevant data via an action menu in the tree overview or on the map. You
can, for example, display a list of all products that are assigned to a particular lane, or you can change
the means of transport for a particular product within a specific time period.

© SAP AG AP205 Preface-135

 Models and Planning Versions: Unit Summary

Operational planning in the APO System is carried

out in the active planning version 000 of the active
model 000.
During master data transfer from an R/3 System,
the corresponding APO master data is
automatically assigned to the active version 000 of
the active model 000.
You can also use the APO master data in an
inactive planning versions. To do so, you must
assign them to the inactive versions.

© SAP AG 2001

© SAP AG AP205 Preface-136

 Transfer of Transaction Data

Contents:
Transfer of Transaction Data Between R/3 and APO
Systems
Initial and Incremental Data Transfer
Integration Model for the Transfer of Transaction Data

© SAP AG 2001

© SAP AG AP205 Preface-137

 Transfer of Transaction Data: Unit Objectives

At the conclusion of this unit, you will be able to:

Describe the concept of transaction data transfer

between R/3 and APO Systems
Define an integration model for the transfer of
transaction data
Transfer transaction data

© SAP AG 2001

© SAP AG AP205 Preface-138

 Overview Diagram (6)

1 Overview

2 Architecture of Integration

3 Transfer of Master Data

4 APO Master Data 6

5 Models and Planning Versions

66 Transfer of Transaction Data

7 Monitoring/Error Handling

8 Conclusion

© SAP AG 2001

© SAP AG AP205 Preface-139

 Transaction Data Interface: Core Interface (CIF)

R/3 APO

R/3 transaction data APO transaction data

Purchase orders Core Interface Orders
Purchase requisitions CIF - Replenishment order
Sales orders - Manufacturing order
Planned orders Integration - Procurement order
Planned [Link] model ...
Reservations (Distinction by
Stocks... ATP category)

© SAP AG 2001

The transaction data that is to be transferred into APO, is specified in an integration model that you
define in the R/3 System. The transaction data is mapped to orders in APO that differ by ATP
category.

© SAP AG AP205 Preface-140

 Transaction Data Objects of the CIF

APO
R/3
Initial data
R/3 transaction data APO transaction data
transfer Order with category
Purchase orders
BF (PchOrd)
Purchase requisitions
AG (PurRqs)
Sales orders BM (SalesOrder)
Planned orders AI (PlOrd.)
Planned [Link] FA (FC req.)
AM (PrdRes)
Reservations
Incremental CC (Stock)
Stocks ...
... data transfer
Real-
time
© SAP AG 2001

First, the initial data transfer of transaction data is performed via the APO Core Interface (CIF). This is
usually followed automatically by the incremental data transfer between R/3 and APO for transaction
data objects that are members of an active integration model. This means that new transaction data or
changes to existing transaction data are transferred automatically. (For the transaction data of the APO
component SNP, you can specify in Customizing whether a real-time or periodic retransfer is to be
performed.)
The APO transaction data objects are not generally identical to those of the R/3 System. The system
transfers various R/3 transaction data into APO as orders that differ by ATP category.
Planned independent requirements can only be transferred from the R/3 System to APO. The transfer
of planned independent requirements from APO into the R/3, that you need if you only perform
demand planning in APO, must be triggered from demand planning in APO using a separate
transaction.
You can specify in APO that planned orders and purchase requisitions are only transferred from APO
to the R/3 System if the conversion indicator has been set.

© SAP AG AP205 Preface-141

 Initial Data Transfer of Transaction Data: Overview

1. Generate integration model Name

Target sys.

Determine name and APO

Sales orders
target system Production/process orders
Storage location stock
Select transaction data ...

2. Activate integration model

Integration model is active

Start Initial transfer of transaction data is performed,

followed by a continuous real-time incremental
data transfer

© SAP AG 2001

You define the integration model that controls the transfer of transaction data in the R/3 System. You
can find the menu option Core Interface Advanced Planner and Optimizer (the CIF menu) under
Logistics -> Central Functions -> Supply Chain Planning Interface.
The integration model distinguishes between master data and transaction data. We recommend that you
select the two types of data in separate integration models and then transfer them separately.
In the integration model, you select the transaction data you want to transfer. You specify the
following in the integration model:
- The APO target system for the data transfer
- The data objects you want to transfer
You can delete integration models that you no longer need, but note that you must first deactivate
them.
For any transaction data from the production planning that is contained in an active integration model,
the system usually performs a continuous real-time incremental data transfer between the R/3 System
and APO.

© SAP AG AP205 Preface-142

 Integration Model for Transaction Data

Name + application = unique definition of integration model

Name PUMPS
Target sys. APOCLNT800
APO
Application BEW_DATA System
Sales orders
Production/process orders
Selection of
Planned orders transaction data types
Storage location stocks
...
Relevant materials
Material
Selection criteria for
Plant 1000
the transaction data
MRP type X0
...
Execute + Save
© SAP AG 2001

The transaction data that is to be transferred from the R/3 System to the APO System is defined in an
integration model. The R/3 System generates this integration model (transaction CFM1).
An integration model is uniquely defined by its name and application. It is useful to create several
integration models with the same name but as different applications. Ensure that the data pools of your
integration models are generally not too big. This enables you to handle errors more easily.
The target system that you specify in the integration model determines the APO System that the
transaction data is transferred into. The target system is a logical (APO) system that must have a RFC
connection. The APO System determines the (R/3) target system to be used for a retransfer from APO
to R/3.
You use a particular integration model to specify which transaction data you want to transfer. To do so,
you first specify the transaction data types that are to be added to the integration model. Secondly, you
specify the selection criteria that will be used to select the individual documents in the R/3 System.
You complete the generation of the integration model by "executing" the model (this means that the
data objects of the model are compiled) and then you save it.

© SAP AG AP205 Preface-143

 Activate Integration Model for Transaction Data

Integration model
Name PUMPS
R/3 R/3
Material
Material master
master A
Target system APOCLNT800 Stor loc. stockAB
Application BEW_DATA Planned order A

"Activate" Active/Inact.
Stor loc. stock B
PUMPS APOCLNT800 BEW_DATA 10:00:00

Start Incremental
automatic data transfer

Material
Material master
master A
Transaction data Stor loc. stockAB
APO Planned order A
in APO Planned order A

© SAP AG 2001

To transfer transaction data between R/3 and APO, you must activate the integration model. You
activate an integration model with the transaction Activate integration model (transaction code CFM2)
in the CIF.
It is useful to have several integration models active at a time.
Choose the Start function to trigger the initial data transfer. This means that the transaction data you
have selected is transferred into APO for the first time. This initial transfer is usually automatically
followed by the real-time link between the R/3 System and the APO System, concerning the selected
transaction data. This means that once a storage location stock of a selected material changes due to a
goods movement posting, the new stock is transferred into APO. In the same way, production orders
that are generated in APO, for example, are immediately transferred to the R/3 System.

© SAP AG AP205 Preface-144

 Publication of Planning Results

APO Planning results in

APO
e.g. Planned order x

Collect the
or changes
Which
R/3 System?
Periodic
transfer

R/3 Planned order x R/3

Plant A Plant B

© SAP AG 2001

In APO transaction /SAPAPO/C4 you set how (in what form) new transaction data is to be transferred
from APO PP/DS into R/3. It is usually a real-time transfer (this is the default setting for PP/DS data).
There is also the possibility of collecting the changes in APO first, then transferring them to the R/3 as
a collected group (transaction /SAPAPO/C5).
For SNP, you set the form for transferring SNP planning results to the R/3 System with the
Customizing operation: Set transfer to OLTP system. The default setting for SNP is that the changes
are collected and transferred periodically.
In the Basic settings (publication of planning results) operation in APO Customizing, specify for each
plant and publication type (for example, in-house production or external procurement), which R/3
System you are going to publish your planning results in (name of the logical system). You must
complete this table, even if you only operate one R/3 System.

© SAP AG AP205 Preface-145

 Possible Scenarios (1)

Demand and Production Planning in APO, Shop Floor Control in R/3

Integration model
APO Demand Planning (DP) Name PUMPS

Planned [Link] TargSys. APOCLNT800

Applic. BEW_DATA
Production Planning (PP/DS)
Storage location stcks
Planned order
Manuf. order Planned orders
Prod./process orders
Relevant materials
Create Execute
Plant 1000

R/3 Manuf. order

Planned order
MRP type X0

Shop Floor Control (SFC) Do not plan materials in R/3 but

explode BOM if required

© SAP AG 2001

The transaction data you can select in the integration model depends directly on the planning process.
There are several useful models of how the R/3 System and APO System cooperate, all of which are
based on different integration models.
In the example above, the entire demand and production planning is to take place in APO. As a result
of the planning in APO, the system creates production orders and transfers them into the R/3 as the
executing system. The processing of manufacturing orders takes place in the R/3 System. The
processing progress must be known to APO for further planning.
Demand planning takes place in the corresponding component of APO. It is based on a forecast that is
carried out in APO using historical values from BW. As a result of demand planning, planned
independent requirements are created in APO.
The planned independent requirements are the starting point for production planning in APO. In
addition to the requirements, existing warehouse stock managed in the R/3 System should be included
in the planning. This means that storage location stocks must be added to the integration model.
Planned independent requirements in APO are a result of the production planning, and will be
transferred into the R/3 System for information. In the next step, they will be converted into
manufacturing orders in APO (production or process orders), that will be transferred into the R/3 for
execution.
To ensure that these materials are not planned again in the R/3 System, you should assign an MRP type
to them, excluding them from demand planning. If you want to explode the BOM in R/3, use MRP
type X0.

© SAP AG AP205 Preface-146

 Possible Scenarios (2)

Demand Management in R/3, Production Planning in APO,

Manufacturing Execution in R/3
Integration model

R/3 Demand management

Planned [Link]
Name PUMPS
TargSys. APOCLNT800
Applic. BEW_DATA
Create
Planned [Link]
APO Planned [Link]
Storage location stcks
Production Planning (PP/DS) Planned orders
Planned order
Prod./process orders
Manuf. order
Relevant materials

Create Execute Plant 1000

MRP type X0

R/3 Manuf. order

Planned order
Do not plan materials in R/3 but
Shop Floor Control (SFC) explode BOM if required
© SAP AG 2001

In this example, demand management is to take place in the R/3 System. The planned independent
requirements that result from this planning are transferred into production planning in APO. As a result
of the planning in APO, production orders are created and transferred to R/3 as the executing system.
Demand management in the R/3 System can be carried out manually, can be based on a forecast, or can
use the functions of Sales & Operations Planning (SOP). Planned independent requirements are created
as a result and are transferred into the APO System. Therefore, you must add planned independent
requirements to your integration model.
The planned independent requirements are the starting point for production planning in APO. Existing
storage location stocks should also be considered in the planning.
Planned independent requirements in APO are a result of the production planning, and will be
transferred into the R/3 System for information. In the next step, they will be converted into
manufacturing orders in APO (production or process orders), that will be transferred into the R/3 for
execution.
To ensure that these materials are not planned again in the R/3 System, you should assign an MRP type
to them, excluding them from demand planning. If you want to explode the BOM in R/3, use MRP
type X0.

© SAP AG AP205 Preface-147

 Transfer of Transaction Data: Unit Summary (1)

The transaction data that is to be transferred

between R/3 and APO is selected via an
integration model in CIF.
In an initial data transfer, the transaction data is
transferred to APO from R/3 for the first time. This
is followed by a real-time incremental data
transfer. This means that data changes to existing
transaction data or new transaction data are
immediately exchanged between the two systems.

© SAP AG 2001

© SAP AG AP205 Preface-148

 Transfer of Transaction Data: Unit Summary (2)

Which transaction data you select in the

integration model depends directly on the
planning process. There are several useful
scenarios of how the R/3 System and APO System
can cooperate, all of which are based on different
integration models.

© SAP AG 2001

© SAP AG AP205 Preface-149

© SAP AG AP205 Preface-150
 Exercises

Unit: Transfer of Transaction Data

Topic: Transfer of Planned Orders

At the conclusion of these exercises, you will be able to:

• Explain the result of planned orders and production order
transfers between APO and the R/3 System.

The production of pump T-F2## in plant 1000 is planned in APO:

The system transfers the result of this planning into the execution
R/3 System. An integration model for the transaction data of
pump T-F2## is already available and is active.

1-1 In the R/3, first view the current planning situation of the material T-F2## in plant
1000. Then call up the current stock/requirements list of the material.
1-1-1 Do planned or production orders exist for the material? ____________
1-1-2 How high is the current plant stock level? _______________

Call up the current stock/requirements list of the material, so

that you can view the result at the same time as the planning
data in APO.

1-2 You create a planned order manually in the APO System, for the pump T-F2## in
production plant 1000. Proceed as follows:
1-2-1 Call up the product view for product T-F2##:
Planning version: 000
Product: T-F2##
Location: 1000.
If necessary, skip any messages with Enter and access the product view. On
the tab page Elements, the current planning elements are displayed.
What is the warehouse stock level? ____________________

© SAP AG AP205 Preface-151

 1-2-2 Go to the change mode of the product view (where you press the icon
Change). Copy the suggested propagation range (SAPALL) with Save. Now
press the button Create order and create the following data for the order:
Planning version: 000
Product: T-F2##
Location: 1000
Yield: 5 pieces
Start date: Delete entry
Availability date: a week today
Create the order and save the planning. What is the number of the order you
have just created?
_______________________________________

1-2-3 Update the product view. What is the number of the planned order now?

___________________________

The planned order is transferred from APO into the R/3 and
then provided with the R/3 planned order number. This
number is then transferred from the APO System for the
corresponding planned order.
According to the system load, this operation may take a
while. It may therefore be necessary to update the product
view several times, until the planned order is displayed with
its new number.

1-3 Now go to the current stock/requirements list of materials T-F2## in the R/3 and
refresh the list.
1-3-1 Is a planned order displayed? _______________
1-3-2 What is the availability date of the planned order and how high is the order
quantity?
____________________________________________________
1-3-3 Finally, note the number of the planned order:
_____________________________
Make sure that the number in APO is the same as the order number that you
noted in task 1-2-3.

© SAP AG AP205 Preface-152

 1-4 Return to the product view in APO, then go to the change mode again. Select your
planned order and set the conversion indicator by pressing the corresponding button.
(This indicator means that the planned order is converted into a production order.)
Save the product view in APO, and then update it.

The planned order with a conversion indicator is transferred

from APO into R/3 as a production order, and provided with
the R/3 production order number. This number is then
transferred from the APO System for the corresponding
planned order.
According to the system load, this operation may take a
while. It may therefore be necessary to update the product
view several times, until the order is displayed with its new
number.

What is the (new) number of the APO order?

_____________________________________________

1-5 Finally, view the current stock/requirements list again in the R/3 and refresh the
list: Make sure that your planned order has been replaced with a production version in
the R/3.

© SAP AG AP205 Preface-153

© SAP AG AP205 Preface-154
 Solutions

Unit: Transfer of Transaction Data

Topic: Transfer of Planned Orders

1-1 In the R/3 System, choose Logistics → Production → MRP → Evaluations →

Stock/Requirements List (MD04)
1-1-1 Available planned or production orders: No, there are no planned or
production orders available.
1-1-2 Current plant stock: 0 pieces.

1-2 In the APO System, choose: Production Planning → Interactive Production

Planning → Product View
1-2-1 Stock level: 0 pieces.
1-2-2 Order number: Varied, for example 2638/1.
1-2-3 Current order number: Varied, for example 29423.

1-3
1-3-1 Planned order displayed: Yes, a firm planned order is displayed.
1-3-2 Availability date and order quantity: The planned order with a quantity of 5
pieces is available a week from today. (If this day is not a workday, then
the next workday).
1-3-3 Planned order number: Varied, for example 29423 (as above).

1-4 New number of APO order: Varied, for example 60002440.

© SAP AG AP205 Preface-155

 Monitoring/Error Handling

Contents:
Monitoring of Application Errors Using the qRFC
Monitor
Error Analysis in the Application Log
SCM Queue Manager
Notification about Queue Blocks Using qRFC Alert
Compare/Reconcile Functions to Ensure Data
Consistency in R/3 and APO

© SAP AG 2001

© SAP AG AP205 Preface-156

 Monitoring/Error Handling: Unit Objectives

At the conclusion of this unit, you will be able to:

Use the qRFC monitor to monitor application

errors
Use the application log to perform an error
analysis
Explain the concept of the SCM Queue Manager
Describe the compare/reconcile functions used to
ensure data consistency in R/3 and APO

© SAP AG 2001

© SAP AG AP205 Preface-157

 Overview Diagram (7)

1 Overview

2 Architecture of Integration

3 Transfer of Master Data

4 APO Master Data

5 Models and Planning Versions

6 Transfer of Transaction Data

77 Monitoring/Error Handling 7
8 Conclusion

© SAP AG 2001

© SAP AG AP205 Preface-158

 Integration Monitoring

R/3
qRFC Monitor (transaction CFQ1)
Application log (transaction CFG1)

APO
qRFC Monitor (transaction SMQ1)
Application log (transaction /n/SAPAPO/C3)
Monitoring both R/3 and APO from within APO:
SCM Queue Manager (transaction /n/SAPAPO/CQ)
qRFC Alert (transaction /n/SAPAPO/CW)

R/3 APO

© SAP AG 2001

The APO Core Interface (COF) offers two monitoring functions to monitor the data transfer from R/3
to APO as well as from APO to R/3: Application log evaluation, transfer queue(s) display.
In addition, the qRFC Alert is used to monitor the outbound queues in APO and R/3 that are relevant
to APO-R/3 integration. If queue blocks are detected, a message is sent to a predefined destination.
Instead of evaluating the application logs in both systems (R/3 and APO) separately when errors occur,
the user can use the central SCM Queue Manager available in APO to monitor the queues and
application logs in both systems.
You can find the Troubleshooting Guidelines Integration R/3 – APO on the R/3 Plug-in homepage on
SAPNet (alias: R/3 Plug-in) under Media Center -> Literature. This document is intended to help you
to localize and solve problems that arise when integrating R/3 and APO. It describes the transfer
technology, the prerequisites that a data transfer must fulfil, systematic troubleshooting, the steps that
must be taken when a particular error occurs, as well as special cases and how to deal with them. (See
note 334692).

© SAP AG AP205 Preface-159

 qRFC Monitor: Motivation

R/3 APO
qRFC Monitor
Remote APO
Function transaction data
Call (RFC)
Master/
Movement data - Communication errors
- Application errors

Asynchronous transfer technology

Core
Core Interface
Interface
(Selection
(Selection and
and Remote
APO master/
extraction
extraction of
of Function transaction data
data)
data) Call (RFC)
qRFC Monitor live
Cache

1. Buffer data
2. Transfer to target system
© SAP AG 2001

Usage: The communication between R/3 and APO is based on the asynchronous transfer technology of
the queued Remote Function Call (qRFC). A Remote Function Call (RFC) enables calling a function
module on a different server. This technology is used in the integration between APO and R/3 both for
the initial data supply and incremental data transfer (from R/3 to APO) as well as for the publication of
planning results (from APO to R/3).
The data is first buffered by the sending system and then transferred to the target system. The major
advantage of this is that the application that triggered the data transfer does not have to wait until the
update has been completed in the target system. However, this means that return parameters cannot be
passed on, and potential error messages cannot be returned to the application directly.
Two types of errors are distinguished for the processing of qRFC modules:
1. Communication errors: This includes network problems, a non-existing RFC destination, and so
on. Since the data transfer is repeated after certain periods, most of these communication errors should
disappear once the network connection is available again.
2. Application errors: This includes: program errors, failed data update in the target system, locking
of objects, missing master data for specific transaction data. Application errors cannot be solved by the
system and must be dealt with by the system administrator.
The main instance for monitoring application errors is the qRFC Monitor. It is available both in R/3
and APO. Any queue for the target system is displayed here. Current qRFC entries can be displayed,
activated, debugged, or deleted in the qRFC Monitor.

© SAP AG AP205 Preface-160

 Using the qRFC Monitor (1)

Example:
Example: qRFC
qRFC Monitor
Monitor in
in R/3
R/3
qRFC Monitor (Outbound queue)
Refresh R/3
Client Queue name Destination Entries Master data
800 CF_ADC_LOAD APOCLNT800 3 transfer
800 CRM_DELT_MATERIAL IPC 3

Refresh Activate queue Lock queue Unlock queue

...
...
Client Queue name Destination Status 1. Date
800 CF_ADC_LOAD APOCLNT800 3 SYSFAIL 02.10.2002

Refresh Execute LUW Debug LUW (Logical Unit of Work)

Client User Function module Status text

800 MUSTER /SAPAPO/CIF_LOC_INBOUND You are not authorized to logon
800 MUSTER /SAPAPO/CIF_PROD_INBOUN Transaction recorded
800 MUSTER /SAPAPO/CIF_RES_ INBOUND Transaction recorded

Queue channel CF_ADC_LOAD = initial data transfer

© SAP AG 2001

During the initial data supply, transfer errors are automatically detected when an integration model is
activated. A dialog box appears from which the user can navigate to the qRFC Monitor (by choosing
qRFC Monitor). In addition, you can choose the Repeat and Ignore functions in the dialog box. If you
choose Repeat, the system attempts to start initial data transfer again (for example, if there was only a
temporary problem in system communication). You can choose Ignore if an online transfer (for
example, stocks) is stuck in the qRFC Monitor. As online transfers (for example, stocks) do not block
the data channel completely, the initial data transfer can be carried out in the dialog mode, ignoring the
entry in the qRFC Monitor. If, however, an earlier initial data transfer (for example, master or
transaction data) has failed, it blocks further initial transfers. In this case, you must navigate to the
qRFC Monitor and analyze the problem.
During online transfer (for example, during stock posting in the R/3 System), transfer errors during
runtime are not displayed in the dialog mode. This means that if data has not been transferred between
APO and R/3, you need to check for red entries in the qRFC Monitor of the system sending the data.
This check can be carried out automatically by qRFC Alert.
A qRFC Monitor is available in R/3 outbound processing (transaction CFQ1) and in APO outbound
processing (transaction SMQ1). By double-clicking the relevant line, all function calls for the transfer
channel selected are displayed in the qRFC Monitor (you can find the INBOUND function modules
available in APO in the Object Navigator, transaction SE80, under development class /sapapo/cif). The
top function module blocks all following entries in the case of an error. You can display the current
status text from the error short text. A detailed error message is stored in the application log of the
target system. In the above example, the user from the RFC destination was either locked in APO or
did not exist.

© SAP AG AP205 Preface-161

 Queue Channels for Data Transfer: Example

Queue channels
R/3 Integration model X
APO
PPM for material A, B; material A, B (active) Material A
Material B
CF_ADC_LOAD
Integration model Y PPM Material A
PPM for material C, D, material D Material C PPM Material B
Initial transfer Integration model Z (Data channel blocked)
Master and
Material E
transaction data

CFMAT[[Link].]

Material A
Incremental APO master/
data transfer (if active integration models
Material B transaction data
Material exist for materials A and B)
live
CFPO[PO number] Cache
PO number 4711
Online
Material A
transfer
(if an active integration model
Purchase PO number 4712
exists for purchase orders for
orders Material A
material A)

© SAP AG 2001

In the above example, material C could not be transferred. It blocks the queue for the following data to
be transferred initially (to ensure data consistency, a queue is processed sequentially). However,
incremental data transfers for master data or online transfers for transaction data can still be carried out
at the same time, provided that an active integration model exists for the master or transaction data in
question.
The following queue channels The following queue channels are available in the interface: Initial
data transfer CF_ACD_LOAD, stocks CFSTK*, purchase orders and purchase requisitions CFPO*,
planned orders/production orders CFPLO*, sales orders CFSLS*, manual reservations CFRSV*,
confirmations CFCNF*, planned independent requirements CFPIR*, requirement reduction
independent requirements CFMAT*, production campaigns CFPCM*, master data classes CFCLA*,
master data characteristics CFCHR*, transportation CFSHP*, planning tables CFCUVT* (in online
transfers, * stands for the number of the purchase order, sales order, and so on, and in incremental data
transfers of master data, for example, * stands for the material number).
If only temporary communication errors occur in the network connection, the failed transfers (entry in
the qRFC Monitor) can be re-started (by choosing Activate queue in the qRFC Monitor). If you only
want to re-start one object type (for example, locations) within a queue, you can choose the Execute
LUW function to repeat the transfer of locations. If you want to specify that the queue is automatically
activated again if transfer errors occur, you can set up the RFC destination (transaction SM59) in such
a way that the system makes several new attempts to transfer the data at certain time intervals. To do
so, choose Destination → TRFC Options in the RFC destination and maintain, for example, the value
20 in the Connection attempts up to task field and the value 2 in the Time betw. 2 tries [mins] field.
The system then makes 20 attempts in 2-minute intervals to start the transfer (if no entries are made in
these fields, the default setting applies, that is, 20 attempts in 15-minute intervals). If you do not want
to use this function, enter X in the Suppress background job field.

© SAP AG AP205 Preface-162

 Using the qRFC Monitor (2)

Example:
Example: qRFC
qRFC Monitor
Monitor in
in APO
APO
qRFC Monitor (Outbound queue)
Refresh
APO
Planned order
Client Queue name Destination Entries
created in APO
800 CFEP3040 R3CLNT800 1
800 CFIP3056 R3CLNT800 1

Refresh Activate queue Lock queue Unlock queue

...
...
Client Queue name Destination Status 1. Date
800 CFIP3056 R3CLNT800 1 SYSFAIL 02.10.2002

Refresh Execute LUW Debug LUW (Logical Unit of Work)

Client User Function module Status text

800 MUSTER CIF_ORDER_INBOUND_30A No active integration model
800 MUSTER CIF_ORDER_INBOUND_30A Transaction recorded

Queue channel "CFIP*" = In-house production

© SAP AG 2001

In the example above, a planned order for a finished product and purchase requisitions for the
components of the finished product were created in APO. However, they were not included in any
active integration model in the R/3 System at the time when the order was created in APO.

© SAP AG AP205 Preface-163

 Application Log: Motivation

Application
R/3 log
APO
R/3:
Error
RFC

Master/ - Communication errors

transaction data - Application errors

RFC APO master/

Core
Core Interface
Interface
transaction data

live
Application
Cache
log
APO:
Error

© SAP AG 2001

Display entries: You can use the application log to trace when (time), and what (data objects and
integration model) was transferred by whom (user). In addition, the application log provides a detailed
error message if an application error occurred. As a prerequisite, logging must have been switched on.
If errors occurred during transfers, detailed error messages are stored in the application log of the target
system.
Prerequisite: Logging mode switched on (transaction CFC2 in R/3 and /SAPAPO/C41 in APO; you
can make settings as required under Logging).
• Normal (only the number of data records transferred is logged)
• Detailed (the number and content of the data records transferred is logged): Detailed logging can
easily lead to large database tables and decreased performance when used in a productive system.
For this reason, we recommend using detailed logging only when the data is needed, this means, for
example, in the implementation phase.
Delete entries: You can delete logs of the application log in R/3 and APO. The system does not delete
the logs automatically. To prevent extreme database load, we recommend deleting the logs
periodically. If you want, you can schedule background processing for this. If you do not make an
entry in the date and time fields, all logs older than two weeks are deleted automatically.

© SAP AG AP205 Preface-164

 Using the Application Log (1)

Example:
Example: Application
Application Log
Log in
in R/3
R/3
qRFC Monitor
Refresh R/3

Client User Function module Status text

800 MUSTER /SAPAPO/CIF_TPSRC_INBOU Loc. 0000001003 does not exist
800 MUSTER /SAPAPO/CIF_GEN_EVENT Transaction recorded
R/3 Application Log
Date User Number Subobject type
02.10.2002 MUSTER 530 Initial data supply

Function: CIF_LOCATION_SEND: Plant 1000

APO Application Log

Date User Number Subobject type
02.10.2002 USERADMIN 4 Sources of supply
Problem class: very important
Problem class: medium
Problem class: additional information
Location 0000001003 does not exist

© SAP AG 2001

In the example above, an initial data supply was carried out in the R/3 System to transfer several
different master data, including, for example, purchasing info records. One of the purchasing info
records transferred was for a vendor that does not exist in APO.
Message display: You can select different subobjects for the CIF object in the R/3 and APO
application log. These include, for example, EP External procurement (inbound), IP In-house
production (inbound), or INITIAL Initial supply and LOCATION Location: customer, plant, vendor
(For performance reasons, the entries for an initial supply and an incremental data transfer are grouped
under the subobject INITIAL). For more subobjects, choose F4 for the Subobject field on the initial
screen of the application log.
By double-clicking on a subobject, you can navigate to Messages for the relevant transfer log. This
provides an overview of the data objects that have been sent between the systems. This function is
particularly helpful when determining errors.
qRFC Monitor: The transaction ID of the sending application serves as the key of an error message
(TID field in the qRFC line of the qRFC Monitor of the sending system). When you enter this number,
you can display all messages for this qRFC call in the target system. In the application log, you enter
the number of the transaction ID in the Ext. identif. field and execute the selection. The system displays
all messages for the call in question.

© SAP AG AP205 Preface-165

 Using the Application Log (2)

Example:
Example: Application
Application Log
Log in
in APO
APO
APO qRFC Monitor
Refresh

Client User Function module Status text

800 MUSTER CIF_ORDER_INBOUND_30A No active integration model
800 MUSTER CIF_ORDER_INBOUND_30A Transaction recorded

APO Application Log

Date User Number Subobject type
02.10.2002 MUSTER 120 In-house production

Function: /SAPAPO/CIF_IP_OUTBOUND: Order material P-102, plant 1000

R/3 Application Log

Date User Number Subobject type
02.10.2002 USERADMIN 1 In-house production
Problem class: very important
Problem class: medium
Problem class: additional information
Inbound R3CLNT800: For system APOCLNT800 no active integration
model for type T_PLO filter object P-102 1000

© SAP AG 2001

In the example above, a planned order for a finished product and purchase requisitions for the
components of the finished product have been created in APO. However, they were not included in any
active integration model in the R/3 System at the time when the order was created in APO. Therefore,
the orders were not created in R/3 but kept in the queue. In the outbound log, you always recognize the
log of successful transfers. In the logging of the target system, error messages are displayed if errors
occurred during transfers.

© SAP AG AP205 Preface-166

 SCM Queue Manager (1)

APO Execute
R/3 SCM Queue Manager
Systems
Expand nodes
Systems R3CLNT800

Object types
APO outbound types EP
Plug-in outbound types T_INITIAL

EP Ext. Procurement T_INITIAL Initial trans.

IP In-House Production T_ORD Planned ords,..
... ...

R/3 RFC APO

- Communication errors
- Application errors

RFC

© SAP AG 2001

Instead of evaluating the application logs in both systems (R/3 and APO) separately when errors occur,
the user can use the central SCM Queue Manager available in APO (transaction /n/SAPAPO/CQ) to
monitor the queues and application logs in both systems.

© SAP AG AP205 Preface-167

 SCM Queue Manager (2)

APOCLNT800 System: APOCLNT800 Type: In-house production

External procurement
In-house production
Refresh [Link]
Planned ind. reqmnts
Planning file entries
Production campaigns Queue Destination Error text User Date
Sales order CFIP3056 R3CLNT800 No active integration MUSTER ...
Transportation model
Delivery
Reservations
...
R3CLNT800
Initial supply
Purchase orders
Planned orders
Production orders
Sales orders
Planned ind. requirements.
Manual reservations
Production campaigns
Confirmations
Transportations
Stocks
Characteristics
Classes

R32CLNT800
Initial data supply...
© SAP AG 2001

© SAP AG AP205 Preface-168

 qRFC Monitoring: Notification about Exception
Messages (1)

R/3 APO

RFC

Master/ - Communication errors

Movement data - Application errors
APO master/
transaction data

Core
Core Interface
Interface RFC

Mail to initiator or live

Cache
administrator

© SAP AG 2001

Usage: Application errors that occur during data transfer are not reported directly to the user because
data transfer between APO and R/3 is asynchronous. Instead, the qRFC entries block the outbound
queue. Any subsequent data transfers cannot pass the outbound queue. By monitoring the qRFC
exception message, queue blocks are detected and the following are notified:
• The initiator of the block via SAPOffice Inbox Mail (the initiator of every queue block receives a
message informing him or her that he or she has caused a block)
• The administrator, via SAP Office Inbox or an Internet mail (one person is chosen to receive all
messages). If you want to send the messages to an e-mail address, you must have made the necessary
settings in SAPconnect.
Features: The report (transaction /N/SAPAPO/CW) monitors all APO outbound queues, and the
queues of the logical R/3 Systems connected to APO. Depending on the settings on the selection
screen, local qRFC-API modules in the APO system, or qRFC-API modules in the connected R/3
System, or both are called up synchronously and the status of the relevant outbound queues is queried.
You can find out the names of the relevant logical systems from the selection screen entries, and from
the entries in the /SAPAPO/SYSDIR table (to maintain, use /SAPAPO/C2).
If the system recognizes queue errors or blocks, a message is generated from the status information.
The message is sent via the SAPOffice API to the relevant destination(s) or administrator(s), provided
the settings are made accordingly. In addition, the list of all incorrect outbound queries is output in list
form.

© SAP AG AP205 Preface-169

 qRFC Monitoring: Notification about Exception
Messages (2)

APO Execute
R/3 qRFC Monitoring
Local outbound queues
Target systems *
Local queue names CF*
Queue errors only
Notification
No
To initiator
To administrator MUSTER B

Remote outbound queues

Remote systems
Destinations
Remote queue names CF*
Queue errors only (remote system)
Notification
...

© SAP AG 2001

Local outbound queues: 1. Enter the target system (logical system). You can use placeholders. 2.
Enter the name of the queue to be monitored. 3. (Queue errors only indicator). Specify whether you
want the monitor to only find real application errors (SYSFAIL) (i.e. indicator set) temporary errors,
such as communication errors (CPICERR), or errors caused by temporary application locks (i.e.
indicator not set). 4. Specify where the message is to be sent: No notification (the message is not sent
and is only displayed), To initiator (the message is sent to the initiator of the block), To administrator
(All messages are sent to one person): You can change the entry in the address field (the current user is
set as the default value). 5. Choose a recipient type. The recipient type determines the message format.
You can now choose between B (SAP user) and U (Internet address). If you choose recipient type U,
ensure that you have made the relevant entries in SAPconnect. 6. Execute the report program. The
message is sent or displayed on the screen.
Remote outbound queues: In the Remote outbound queue groupbox, you define the settings for
monitoring the outbound queues of connected R/3 Systems: 1. In the Remote systems field, enter the
name of the RFC destinations whose outbound queues you want to monitor. You may use wildcards
(for example SX*). If you do not enter anything, none of the outbound queues of the connected
systems are monitored. 2. In the Destinations in the remote system field, enter the name of the target
systems called in the remote system (usually the APO system itself). You may use wildcards (for
example SX*). 3. In the Remote queue name field, enter the names of the R/3 outbound queues to be
examined in the remote systems to be monitored. All R/3 outbound queues that are addressed via the
APO CIF integration have CF as the prefix. 4. All other entries are made in the same way as for local
outbound queues. If you want to run the qRFC Alert periodically, you must schedule the report via the
SAP job definition (transaction SM37).

© SAP AG AP205 Preface-170

 Compare/Reconcile Function for Data
Inconsistencies in R/3 and APO: Compare

APO
R/3 Report /SAPAPO/CIF_DELTAREPORT2

Partner system (R/3) R3CLNT800

Material P-102 (optional)

Plant 100 (optional)

Integration model Pump (optional)
Objects to be checked
Sales orders
Production/process orders
Purchase requisition
... ...

Storage location stocks

Sales order stocks
... ...

Compare live
Database Cache

© SAP AG 2001

Usage: Data inconsistencies between APO and R/3 can arise in certain circumstances, for example, due
to application errors or manual deletion of queue entries. The compare/reconcile function helps you to
identify and correct such data inconsistencies. In APO, the function covers the following objects:
Stock, sales order, planned order, production order, purchase order, and purchase requisition.
When you use the compare/reconcile function, the system performs a comparison and lists any
inconsistent objects it identifies. Then you can select individual, several, or all objects for the reconcile
function. The selected data can be sent from R/3 to APO.
Procedure: Start report program /SAPAPO/CIF_DELTAREPORT2 in the ABAP Editor of APO
(transaction SE38). Choose the R/3 System in the Partner system field. In addition, you can restrict the
compare/reconcile function to certain products, locations, integration models, or stocks and transaction
data by entering selection parameters, and therefore reducing the runtime of the transaction.
After the report has been executed, an overview of the results of the comparison is shown on the next
output screen, separated according to orders and stocks. A line with the following information is
displayed for every object type checked: Total (total number of R/3 objects selected for comparison),
Errors (total number of errors found), All other columns: (distribution of the errors to individual error
areas).

© SAP AG AP205 Preface-171

 Compare/Reconcile Function for Data
Inconsistencies in R/3 and APO: Reconcile

APO Execute
R/3 Report results list

Results Sales orders Storage loc.

stocks
Deviations in APO

Send
Send to
to APO
APO
Storage Quantity
Sent Material Plant location Stock APO Reason
P-102 1000 0002 11 10 ...
Documents
Sales orders
Production/process orders
...
Supplies
Storage location stocks
...

Reconcile live
Database Cache

© SAP AG 2001

© SAP AG AP205 Preface-172

 Monitoring/Error Handling: Unit Summary

Data transfer between R/3 and APO is carried out

asynchronously. Errors occuring during the data
transfer can therefore be processed separately.
Technical problems or application errors can cause
these errors.
There are different functions for error handling
available in R/3 and APO: the qRFC Monitor and the
application log.
You can use the compare/reconcile function to
remove data inconsistencies between R/3 and APO.

© SAP AG 2001

© SAP AG AP205 Preface-173

 Conclusion

1 Overview

2 Architecture of Integration

3 Transfer of Master Data

4 APO Master Data

5 Models and Planning

Versions

6 Transfer of Transaction Data

7 Monitoring/Error Handling

8 Conclusion

© SAP AG 2001

© SAP AG AP205 Preface-174

 Course Objectives

You are now able to:

Describe the architecture of integration of ERP
systems with the APO System
Select master and transaction data to transfer
from R/3 into APO
Specify where in the APO System it may be
necessary to add to the master data transferred
from the R/3
Describe the monitoring and the
compare/reconcile functions used to ensure data
consistency in R/3 and APO

© SAP AG 2001

© SAP AG AP205 Preface-175

 Recommended Follow-up Courses

Integration of transaction data is directly dependent on the

individual APO planning functions. It is therefore described in
greater detail in the APO application courses. These courses
also provide more detailed information on master data.

AP215 Supply Network Planning (SNP)

AP220 Production Planning & Detailed Scheduling (PP/DS)
AP230 Global Available to Promise (ATP)

© SAP AG 2001

© SAP AG AP205 Preface-176

 Recommended Follow-up Activities

Go through the exercises using IDES data or your own data

Read on-line documentation
Read IMG documentation
Read release notes

© SAP AG 2001

© SAP AG AP205 Preface-177

 Appendix: Supplement to BSGs

Contents:
Mapping different material numbers from several R/3
Systems onto one product in APO.

© SAP AG 2001

© SAP AG AP205 Preface-178

 Business Situation

Several R/3 Systems are linked with one APO System.

Some products are planned in the R/3 Systems under
different material numbers.
These materials are planned as one product in different
plants in APO.
The retransfer of the planning results from APO into the R/3
Systems will take place with the R/3-dependent material
numbers.

© SAP AG 2001

© SAP AG AP205 Preface-179

 Concrete Example

R/3-1
R/3-1 APO
APO R/3-2
R/3-2
Material master Material master
Material 70015 Material 60015
Plant 0002 Plant 0001

Initial
Initialtransfer
transferof
of Initial
Initialtransfer
transferof
of
material
material70015,
70015, material
material60015,
60015,
plant
plant0002
0002 Product plant
plant0001
0001
Product 60015
Location 0001
Location 0002

Planning
Planningfor
for
product
product60015
60015

Planned orders Transfer

Transfer Planned orders
Material 70015 planning
planningresult
result Material 60015
Plant 0002 to
tothe
theR/3
R/3 Plant 0001
Systems
Systems

© SAP AG 2001

© SAP AG AP205 Preface-180

 Solution to the Problem using BSGs (1)

R/3-1
R/3-1 R/3-2
R/3-2
Bu
e ss s
Sy ines
sin e m s s
t
Bu ys up Gr tem
S ro _1 BS oup
G G G_
2
BS
APO
APO

© SAP AG 2001

© SAP AG AP205 Preface-181

 Solution to the Problem using BSGs (2)

For each R/3 System, define a separate business system

group.
Assign the (logical) R/3 Systems to their business system
groups.
Activate the customer exit
EXIT_/SAPAPO/SAPLCIF_PROD_001 (APOCF005) for the
initial transfer of material masters.

© SAP AG 2001

© SAP AG AP205 Preface-182

 Example for the programming of customer exits:

*---------------------------------------------------------------------
-*
* INCLUDE ZXCIFUSERU08
*
*---------------------------------------------------------------------
-*
loop at it_matkey.
* set external material number
et_matmap-ext_matnr = it_matkey-ext_matnr.
* set APO-internal material number per default
et_matmap-matnr = it_matkey-ext_matnr.
* start of customer specific material mapping
if cf_dst_bsg = 'BSG_1' and
et_matmap-matnr(1) = ‘7'.
et_matmap-matnr(1) = ‘6'.
endif.
* start of customer specific material mapping
collect et_matmap.
endloop.
* set control flags
if not et_matmap[] is initial.
* tell system to use customer specific material mapping
ef_map_use = 'X'.
* tell system to allow duplicate product numbers for different BSGs
ef_dup_check = 'A'.
endif.

© SAP AG AP205 Preface-183

 Solution to the Problem using BSGs (3)

Prerequisites

APO 3.0 with Support Package 4

The parameter EF_DUP_CHECK in the customer exit
EXIT_/SAPAPO/SAPLCIF_PROD_001 (APOCF005) must be
set to 'A', so that multiple entries are allowed (for the internal
material number).

© SAP AG 2001

© SAP AG AP205 Preface-184

 Appendix: Master Recipe (PP-PI)

Contents:
Mapping a R/3 master recipe (PP-PI) onto an APO
production process model.

© SAP AG 2001

© SAP AG AP205 Preface-185

 Master Recipe and PPM: Basics

Operations and phases (and also secondary resources)

of the R/3 recipe are transferred as operations with
different operation types to APO-PPM.
Relationships between R/3 phases are transferred as
activity relationships between APO activities.
For more detailed information on the integration of PPMs
in PI and PM/SM, see the SAP Online Documentation
in the 'Supply Chain Management (SCM) Business
Scenarios' unit, in the section 'Master Data ®
Production Process Model'.

© SAP AG 2001

© SAP AG AP205 Preface-186

 Master Recipe and PPM in APO 3.0

Master Recipe PPM

Operation 10 Operation 10 - operation type 1 (PI operation)

Operation 11 - transfer oper. 10, [Link] 2 (PI phase)

Phase 11 Act. 11 - Setup/Produce

Phase 12 Res. A
Res. A
Operation 12 - transfer oper. 10, [Link] 2 (PI phase)
Res. A Act. 12 - Produce
[Link]. 400
Res. A

Res. X Operation 400 - transfer op. 11, op. type 3 (PI [Link].)

Act. 400 - Produce

Secondary resource 500 Res. X

Operation 500 - transfer op. 10, op. type 3 (PI [Link].)

Res. Y
Act. 500 - Produce

Res. Y

© SAP AG 2001

© SAP AG AP205 Preface-187

 Relationships/Activity Relationships

Operation 10 Operation 20

R/3 Phase 11 Phase 12 Phase 21 Phase 22 Phase 23

[Link]
400 Relationships

[Link] ( Assignment of secondary resources )

500

APO Act. 11 Act. 12 Act. 21 Act. 22 Act. 23

Act. 400 Operation-internal activity relationships

Order-internal activity relationships

Act. 500

© SAP AG 2001

© SAP AG AP205 Preface-188