APO SNP Part 1

© SAP AG AP205 Preface-1

? SAP AG 2001

AP205 Master Data Integration

AP205AP205

Master Data IntegrationMaster Data Integration

? SAP AG

??System R/3 Release 4.6C with Plug-in 2000_2 and APO Release 3.0A

??Mai 2001

??Material number 50041876


? SAP AG 2001

Copyright 2001 SAP AG. All rights reserved.

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

All rights reserved.

Copyright

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, mySAP.com Logo and mySAP.com 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 2001

SAP Advanced Planner and Optimizer (APO)

Level 2SAP R/3

Level 3SAP APO

Level 2SAP APO

SAP APO Overview

AP010 2 days

PP - Planning andExecution for Discreteand RepetitiveManufacturing

LO050 5 days

PP-PIProcess Manufacturing

LO060 5 days

liveCacheAdministration

BC555 2 days

Integration MasterData

AP205 2 days

Global ATP

AP230 2 days

Production Planning/Detailed Scheduling

AP220 3 days

SupplyNetwork Planning

AP215 3 days

Demand Planning

AP210 5 days


? SAP AG 2001

Course Prerequisites

Required Prerequisite

Recommended

? AP010 - SAP APO Overview

? LO050 PP - Manufacturing Planning &Execution for Discrete & Repetitive

else

? LO060 PP-PI Process Manufacturing


? SAP AG 2001

Target Group

? Participants:

Members of the project team responsible formaster data integration between APO systemsand an OLTP system.

? Duration: 2 days

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

? SAP AG 2001

? Course Goals

? Course Objectives

? Course Content

? Course Overview Diagram

? Main Business Scenario

? Overview of Integration of R/3 Systems with APO

Contents:

Course Overview

© SAP AG AP205 1-2

? SAP AG 2001

This course will prepare you to:

Course Goals

? Gain a basic understanding of the integration ofthe APO System with an R/3 System (or externalsystem)

? Transfer master data from the R/3 System to theAPO System and to set up your system to transfertransaction data between the systems.

© SAP AG AP205 1-3

? SAP AG 2001

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

Course Objectives

? Describe the architecture of integration of ERPsystems with the APO System

? Select master and transaction data to transferfrom R/3 into APO

? Specify where in the APO System it may benecessary to add to the master data transferredfrom the R/3

? Describe the monitoring and thecompare/reconcile functions used to ensure dataconsistency in R/3 and APO

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

© SAP AG AP205 1-4

? SAP AG 2001

Unit 5 Models and PlanningVersion*

Unit 6 Transfer ofTransaction Data

Unit 7 Monitoring/ErrorHandling*

Unit 8 Conclusion

Unit 1 Course Overview

Unit 2 Architecture of Integration

Unit 3 Transfer of Master Data

Unit 4 APO Master Data

Preface

Appendix

Course Content

* These units contain more information and cannot be discussed in greatdetail due to lack of time in the course.

© SAP AG AP205 1-5

? SAP AG 2001

Overview Diagram (1)

Transfer of Master Data

444

Architecture of Integration

333

22211 Overview

777

Transfer of Transaction Data

APO Master Data

555 Models and PlanningVersions

666

111

888

Monitoring/Error Handling

Conclusion

© SAP AG AP205 1-6

? SAP AG 2001

? The Precision Pump Company has been in themarket since 1971 and offers a large number ofhigh-tech standard pumps. In the product catalogyou will find turbomolecular , centrifugal, rotary andmembrane pumps (that can be used formanufacturing ultra-high vacuums, for example).

Main Business Scenario

© SAP AG AP205 1-7

? SAP AG 2001

Advantages of Production Planning in APO

? Detailed scheduling with simultaneous quantities and capacityplanning (PP/DS)

? Exact material requirements planning (in hours and minutes), fordependent 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, alternativeselection of resources, ...)

? Dynamic exception messages (alerts)

? Capacity categories: Time, service, volume, piece

© SAP AG AP205 1-8

? SAP AG 2001

APO Integration (1)

R/3 -> APOMaster data

? Plants, vendors, customers? Materials? Work centers (capacities)? Routings and bills of

material? ...

Transaction data

? Sales orders? Planned/production orders? Purchase orders? Supplies? ...

APO -> R/3Planning results

? Manufacturing orders? Order proposals? Result of availability

check? ...

R/34.6C

R/33.1I

APO

BW

??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 1-9

? SAP AG 2001

APO Integration (2)

SDSD LOLO

HRHR

SAP R/3SAP R/3

SAP APOSAP APO

Non-R/3 System

Non-Non-R/3 SystemR/3 System

BAPI

BAPI

BAPI

CIF(Core Interface) BAPIs

??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 1-10

? SAP AG 2001

APO Integration (3)

R/3 APOOrder• Production• Procurement• Replenishment

liveCachelive

Cache

LocationProductResourceProduction process model

Plant, customer,...Material masterCapacityRouting and

bill of material

Sales orderPlanned orderProduction orderPurchase order...

CIF

CIFReal-time

??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 1-11

? SAP AG 2001

R/3 Plug-In Technology

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

R/3

R/3Plug-in

BBP

CRM

BW

APO

SEM

CIF

??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 1-12

? SAP AG 2001

? The integration of the SAP-APO with R/3 Systemstakes place via the CIF interface, which is anelement of the R/3 Plug-in. Non R/3 Systems areconnected using BAPIs.

? The system transfers the master data relevant forplanning in APO via the CIF interface, from R/3 intoAPO.

? The CIF interface is responsible for the transfer oftransaction data from the R/3 into APO and for theretransfer of the planning results from APO backinto the R/3.

Course Overview: Unit Summary

© SAP AG AP205 2-1

? SAP AG 2001

? RFC Links Between APO and the R/3 System

? Business System Group

? Basic Settings

Contents:


© SAP AG AP205 2-2

? SAP AG 2001

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

? Explain the concept of the business systemgroup.

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

Architecture of Integration: Unit Objectives

© SAP AG AP205 2-3

? SAP AG 2001



444


333

22111 Overview

777


APO Master Data


666

222

888


Conclusion

© SAP AG AP205 2-4

? SAP AG 2001

APO Integration with R/3 Systems

SDSD LOLO

HRHR

SAP R/3SAP R/3

SAP APOSAP APO

Non-R/3 System


BAPI

BAPI

BAPI

BAPIsCIF(Core Interface)

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

© SAP AG AP205 2-5

? SAP AG 2001

RFC: Link Between R/3 and APO

R/3 APO

RemoteFunctionCall (RFC)

Core Interface(selection andextraction of

data)

Core InterfaceCore Interface(selection and(selection andextraction ofextraction of

data)data)

Master/transaction data


APO master/APO master/transaction datatransaction data

liveCache

liveCache

??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 2-6

? SAP AG 2001

Structure of a RFC Link: Overview

Between an R/3 and an APO System

1. Naming logical systems

2. Assign logical systems to clients

3. Define RFC destinations

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

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

? 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

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

? SAP AG 2001

Defining Logical Systems

Naming logicalsystems R/3

R3CLNT800

APOCLNT800

Assign the logical R/3System to R/3 clients

R/3Client 800

R3CLNT800

Naming logicalsystems APO

R3CLNT800

APOCLNT800

Assign the logical APOSystem to APO clients

APOClient 800

APOCLNT800

APO APO

??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 2-8

? SAP AG 2001

Define RFC Destinations

Create RFCdestination for theAPO System

R/3 APOCreate RFCdestination for theR/3 System

R/3 link

RFC destination APOCLNT800

Target host iwdf001.wdf.sap-ag.de

System number 00

Logon

Client 800

User APOREMOTE

Password *******

Logical APO System name

R/3 link

RFC destination R3CLNT800

Target host iwdf002.wdf.sap-ag.de

System number 00

Logon

Client 800

User R3REMOTE

Password *******

Logical R/3System name

??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 2-9

? SAP AG 2001

Determine Target System and Maintain APORelease

Determine APOtarget system R/3

APOCLNT800Logical system Mode

D

APOServer:iwdf002.wdf.sap-ag.de

System number: 00

Client: 800

Which of the different RFC destinations is the

APO System?

Releasedefined?

Integrationmodel

APO

??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 2-10

? SAP AG 2001

Business System Group (1)

Matl. A

Plant HamburgLogical System 1

Matl. A

Plant Munich LogicalSystem 2

Matl. A

Plant Dresden LogicalSystem 3

Matl.?

e.g. Additionally purchased plant

APO

??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 logic al systems onto the unique material number in APO.

© SAP AG AP205 2-11

? SAP AG 2001


Matl. A


Matl. A

Plant Munich LogicalSystem 2

Matl. A

Plant Dresden LogicalSystem 3

Business System Group (1)Business System Group

(2)

Business system group(BSG):

Area of same namingconvention

LogicalSystem 0

APO

??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 2-12

? SAP AG 2001


Matl. A

Plant DresdenLogical System 3

A

A_BSG2

hammer

screw

Ahammer

Unique material numbers in APO

Matl. A


Matl. A

Plant MunichLogical System 2

APO

??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 2-13

? SAP AG 2001


B. Assign logical systems to a BSG

LS0 APOLogical system Business System Group

BSG1LS1 Hamburg BSG1LS2 Munich BSG1LS3 Dresden BSG2

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

Material no.BSG Material APO material numberA BSG1 hammer AA BSG1 hammer AA BSG2 screw A_BSG2

Realization: Customer exits for master data in APO inboundprocessing

A. Define business system groups

BSG DescriptionBSG1 System group 1BSG2 System group 2

APO

??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 2-14

? SAP AG 2001

APO Integration with Non-R/3 Systems

SDSD LOLO

HRHR

SAP R/3SAP R/3

SAP APOSAP APO

Non-R/3 System


BAPI

BAPI

BAPI

BAPIsCIF(Core Interface)

??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 2-15

? SAP AG 2001

? The integration between APO and R/3 Systems iscreated using a RFC link.

? To guarantee that the naming of master data indistributed system landscapes is unique, businesssystem groups are defined as areas of the samenaming convention.

? You can use customer exits to transfer master datafrom different system groups into APO.

Architecture of Integration: Unit Summary

© SAP AG AP205 2-16

© SAP AG AP205 2-17

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 na me 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 2-18

© SAP AG AP205 2-19

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

? SAP AG 2001

? Transfer of Master Data Between R/3 and APO Systems

? Initial and Incremental Data Transfer

? Integration Model for the Transfer of Master Data.

Contents:


© SAP AG AP205 3-2

? SAP AG 2001

? Describe the concept of initial and incrementaldata transfer of master data from an R/3 Systeminto an APO System

? Create an integration model for the transfer ofmaster data

? Transfer master data.


Transfer of Master Data: Unit Objectives

© SAP AG AP205 3-3

? SAP AG 2001



444


33

222111 Overview

777


APO Master Data


666

888


Conclusion

33

© SAP AG AP205 3-4

? SAP AG 2001

Master Data Interface: Core Interface (CIF)

R/3 APO

LocationProductResourceProduction process model

Plant, Customer,...Material masterCapacityTask list and

Bill of material

R/3 master data APO master dataCore InterfaceCIF

Integrationmodel

??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 releas e 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 3-5

? SAP AG 2001

Master Data Objects of the CIF

R/3 APO

Location

Product

Resource

Production process model

R/3 master data APO master data

Plant

Customer

Vendor

Material master

Capacity

Routing and

bill of material

Initial transfer

Incremental data transfer

??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 3-6

? SAP AG 2001

Initial Data Transfer of Master Data: Overview

1. Generate integration model NameTarget system

PlantMaterial master

Resource...

Determine name and APOtarget system

Select master data

2. Activate integration model

Integration model is active

Master data will be transferredStart

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

? SAP AG 2001

Generate Integration Model for Initial Data Transfer

Name PUMPS

Target sys. APOCLNT800

Application MATERIALS

Material master

Customers

Plants

Vendors

Work centers

Production process models

Relevant materials

Material

Plant 1000

MRP type X0

Name + application = unique definition of integration model

APOAPOSystemSystem

Selection of masterdata types

Selection criteria forthe master data

Execute Save+...

...

??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 3-8

? SAP AG 2001

Activate Integration Model for Initial Data Transfer

Name PUMPS

Target system APOCLNT800


Integration model

"Activate" Active/Inact.

PUMPS APOCLNT800 MATERIALS

Start

Master datain APO

Master datain APO

R/3Material master A Material master A Material master B

Material master A

Material master A Material master A Product BProduct A

10:00:00

APO

??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 3-9

? SAP AG 2001

Selection Criterion MRP Type "X0"

MRP type X0MRP procedure XW/out materials planning,

with BOM explosion Matl. A

X0

Matl. B

X0Matl. C

X0Matl. D

VB

R/3

Planning inAPO

Product CProduct B

Product A

Material master DMaterial master CMaterial master B

Material master A

Integration model

Name PUMPS

TargSys. APOCLNT800

Applic. MATERIALS

Material master

Customers

Relevant materials

Material

Plant 1000

MRP type X0

...

...

Material status AP

Further restrictionson the selection are possible

APO

??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 3-10

? SAP AG 2001

Transfer New APO-Relevant Master Data (1)

PUMPS APOCLNT800 MATERIALS

Start

New master data inAPO

Material master Q

R/3

Product Q

11:00:00

X0

New

Name PUMPS



Material master

MRP type X0

...

PUMPS APOCLNT800 MATERIALS 10:00:00

Execute Save+

Existing integration model

"Activate"

Active/Inact.

Difference is transferred

APO

??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 3-11

? SAP AG 2001

Transfer New APO-Relevant Master Data (2)

Name PUMPS



Generate integration model

Name PUMPS



Activate integration model

Active/Inact.

...

Execute

Save+

VariantPUMP_MAT

RIMODGEN report

VariantPUMP_MAT

Start

RIMODAC2 report

JOB_1

+

JOB_2

alternative:

JOB_1_AND_2

Step 1

Step 2

Execute integration model periodically

??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 3-12

? SAP AG 2001

Incremental Data Transfer of Master Data (1)

Name PUMPS

Applicat. MATERIALS

Material master

Relevant materials

Material

Plant 1000

MRP type X0...

...

Changes to APO-relevant master data are transferred - whatis APO-relevant master data?

Material AMaterial B

Material C...

Pumps APOCLNT800 Materials

Integration model active

Materials (generally:Master data) are

APO-relevant

??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 3-13

? SAP AG 2001

Real-Time Transfer of Master Data Changes

Configuration procedure for transfer of master data changes

Transaction CFC5

Business Transaction Event, immed.

Material master

ALE change pointer, periodic

no incremental data transfer


Customers




Vendors



Changed R/3 master dataobjects are transferred intoAPO when the changes are

saved in real-time

APO

Changes to R/3 master dataobjects are recorded and the

transfer of the changes is(periodically, for example)

triggered

??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 3-14

? SAP AG 2001

Incremental Data Transfer of Master Data (2)

Material master A

Matls. planning

Plan.del.time 10 days

11 days

Master datachange

Change pointer

Mat A plan.deliv.time...

Mat B in-house pr.time

Customizing

Changed masterdata in APO

Execute

Incrementaldata transfer

Product APlan.del.time 11 days

Change pointer generally active?Relevant message type

active?


Material master ...Object types

VariantDELTA_MAT

MRP type X0

Incremental data transfer

APO

??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 3-15

? SAP AG 2001

Transfer Master Data Changes Periodically

Evaluate and send change recordings

Execute

VariantDELTA_MAT

RCPTRAN4 report

JOB_DELTATarget sys. APOCLNT800

Material masterCustomers ...

Object types

Schedule periodically

Current master datain APOAPO

??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 3-16

? SAP AG 2001

Integration Model: Other Functions

Deactivate integration model+Connection between R/3 and APO for the relevantmaster and movement data will be cancelled

+Deactivated models can be deleted

+You can check the consistency of the selected datain the integration model

Delete integration model

Consistency check

+Check whether the data objects are alreadycontained within an integration model

Filter object search

??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 3-17

? SAP AG 2001

? The R/3 is the dominant master data system. Thesystem transfers the master data from the R/3 intothe APO System with the help of a CIF integrationmodel.

? During an initial transfer, the system automaticallycreates the APO master data that correspondswith the R/3 master data.

? The system determines the scope of an initialtransfer with an integration model.

? An incremental data transfer can help guaranteethat the system will transfer APO-relevant datachanges in the R/3 into the APO System.

Transfer of Master Data: Unit Summary (1)

© SAP AG AP205 3-18

? SAP AG 2001

? The system can schedule both the initial transferand the incremental data transfer as periodic jobsusing relevant existing reports.

? The incremental data transfer of master data isalso possible as a real-time transfer.

Transfer of Master Data: Unit Summary (2)

© SAP AG AP205 3-19

Exercises

Unit: Transfer of Master Data

Topic: Initial Transfer of Material Masters


?? 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 pr ocedure 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 3-20

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 mainte nance 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 3-21

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

© SAP AG AP205 3-23

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

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.

© SAP AG AP205 4-1

? SAP AG 2001

? APO Master Data

? Result of Transfer of R/3 Master Data into APO

? Supplementing APO Master Data.

Contents:

APO Master Data

© SAP AG AP205 4-2

? SAP AG 2001

? Describe the result of the transfer of R/3 masterdata into APO

? Explain the function of the individual master datadocuments in APO

? Specify where in the APO System it may benecessary to add to the master data transferredfrom the R/3.


APO Master Data: Unit Objectives

© SAP AG AP205 4-3

? SAP AG 2001



44


333

222111 Overview

777


APO Master Data

555 Models and Planning Versions

666

888


Conclusion

© SAP AG AP205 4-4

? SAP AG 2001

Master Data: Overview (1)

R/3 APOR/3 master data APO master data

Plant

Customer

Vendor

Location

Product

Resource

Productionprocess model

Material master

Work center/capacity

Routing and billof material

??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 4-5

? SAP AG 2001

Location Types

R/3 APOLocations withlocation type

Plant 1001 Production plant

Distribution center 1002 Distribution center

MRP area 1007 MRP area

Customer 1010 CustomerTransportation zone

1005 Transportation zone

CIF

Vendor 1011 Vendor

...

© SAP AG AP205 4-6

? SAP AG 2001

Location Type Production Plant

Plant

Name

Customizing: Plant

Street Alsterstr. 13

Town 22222 Hamburg

Country DE

Region 02

Time zone CET

Language German

Plant Hamburg

1000

Master data: Location

Plant Hamburg1000

Loc.type Production plant1001

Alsterstr. 13

Town 22222 Hamburg

DE

02

Germany

Hamburg

Time zone CET

Language German

General Address

Data transfer from the R/3 production plant

Location

Street

Country

Region

Germany

Hamburg

APO

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

? SAP AG 2001

Additional Data in APO Location


1000

Loc.type Production plant1001

Alsterstr. 13

Town 22222 Hamburg

DE

02

Germany

Hamburg

Time zone CET

Language German

General Address

Location

Street

Country

Region

Plant Hamburg

Plant Hamburg

DE

EN

Short description of thelocation in severallanguages

APO-specific planningparameters

...SNP

APO

??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 4-8

? SAP AG 2001

Location Type Distribution Center

Plant

Name

Customizing: Plant

Street Via Castaldi 1

Town 20100 Milano

Country IT

DC Milano

2400


DC Milano2400

Loc.type Distribution center1002

Via Castaldi 1

Town 20100 Milano

IT Italy

General Address

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

Location

Street

CountryItaly

......

Definition as DCCustomizing: DRPPlant Node type Name

1000 Hamburg plantDC2400 DC Milano

APO

??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 4-9

? SAP AG 2001

Location Type MRP Area

Plant

Street Alsterstr. 13

Town 22222 Hamburg

Country DE

Hamburg plant

1000


MRP area 1099

Type MRP area1007

Alsterstr. 13

Town 22222 Hamburg

DE Germany

General Address

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

Loc.

Street

Country

Germany...

...

MRP area

Name

MRP area type 02

Plant 1000

Receiving storage loc. 0099

MRP area 1099

DB1099

Customizing: Reqts. planning

no other storage locationsare assigned!

Assignment to plant 1000

DB1099

APO

??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 sys tem 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 4-10

? SAP AG 2001

Location Type Customer

Customer

Name

Master data: Customer

Street Calvinstr. 36

Town 13467 Berlin

Country DE

Region 11

Language German

Becker Berlin

1000


Becker Berlin1000

Loc.type Customer1010

Calvinstr. 36

Town 13467 Berlin

DE

11

Germany

Berlin

Language German

General Address

Data transfer from the R/3 customer

Location

Street

Country

Region

Germany

Berlin

Transportation zone

D10000

Control dataMaster data: Location

Berlin region D10000

Loc.type Transport.zone1005

LocationBerlin region

APO

Time zone CET

??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 4-11

? SAP AG 2001

Location Type Vendor

Vendor

Name

Master data: Vendor

Street Kolpingstr. 1

Town 12001 Berlin

Country DE

Region 11

Language German

C.E.B. Berlin

L1000


C.E.B. BerlinL1000

Loc.type Vendor1011

Kolpingstr. 1

Town 12001 Berlin

DE

11

Germany

Berlin

Language German

General Address

Data transfer from the R/3 vendor

Location

Street

Country

Region

Germany

Berlin

APO

??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 4-12

? SAP AG 2001

External Procurement Relationship

Vendor

Material

Purch. info record

Valid from 01.01.2000

PUMP

L1000

Ext. procurement relationship

L1000

Product PUMP

Data transfer from the R/3 purchasing info record

Source loc.

Plant 1000

1000Target loc.

to 31.12.9999

Valid from 01.01.2000

to 31.12.9999

Plan.del.time 12 days

General Data

SettingsPlan.del.time 12 days

Info rec.

Info rec. 53004711 R3CLNT800

53004711

Transportation lanesValid 01.01.2000 to 31.12.9999

Vendorknown

in APO?

APO

??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 4-13

? SAP AG 2001



Plant

Customer

Vendor

Location

Product

Resource


Material master


Routing and billof material

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

© SAP AG AP205 4-14

? SAP AG 2001

Product Master in APO

Views of the APO product master

Administration

Attributes

Units of measure

Classification

SNP1

ATP

Demand

Lot size

SNP2

PP/DS

Procurement

GR/GI

Material

??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 4-15

? SAP AG 2001

General Data

R/3

Mat A

Product A

Attributes

001Material group

0001Transportation grp

280 KGGross weight

0,75 M3Volume

Units of measure

1 pc equals 1 pc

1 pal equals 10 pc

regarding classes andcharacteristics that must existin APO

Classification

MRP type X0MRP procedure XW/out materials planning,

with BOM explosion

X0

Simple selectionin the integration

model

APO

??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 4-16

? SAP AG 2001

ATP Settings

Product A

ATP

02

10 days

LOC1000Calendar forcheck.horizon

050Check mode

Material A

MRP 3

02Availability check

10 daysTRLT

Availability check

40Strategy group

Planning

Main strategy 40Planned ind.reqmttype VSFclass 101

Customer reqmttype KSVclass 050

or: Enter customer requirement classfrom schedule line of the sales order

Suggestion:Productioncalendar of

location

Check.horizon

ATP group

APO

??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 4-17

? SAP AG 2001

ATP Customizing

Prerequisite: ATP Customizing

Import CustomizingPermitted

R/3Checking grp

Requirementsclass

Checking rule

Application ATP_CUST

ATP Customizing

Integration model

Availability check

Scope ofcheck

ATP group

Business event

Check mode

Assignment modeProduct.type (standard/characteristics)

Check controlwith scope ofcheck

Customizing APO

??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 4-18

? SAP AG 2001

Requirements Strategies

Product A

Demand

Default strategy

Requirements strategy

Material A

MRP 3

Strategy group

Planning

10

20

30

40

Make-to-stock productn

Planning w. final assemb.

Planning w/out final ass.

Planning product

Mixed MRP ind. 1 Subassembly planning

Strategy 70

Mixed MRP indic. 1+

Subassembly planning

Default strategy 20

+equals

PP

Main strategy

10

40

50

60

20 Planning w. final assemb.70

APO

??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 4-19

? SAP AG 2001

Consumption

Product A

Demand

Consumption

Material A

MRP 3

1

Consumption mode

Planning

2

3

1

2

3

30Cons.per.onwards

20Cons.per.backwards

30

20

Cons.per.onwards

Cons.per.backwards

Consumption mode

Settings for consumptionfrom the MRP group? Analog transfer

takes place

APO

??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 4-20

? SAP AG 2001

Individual and Collective Requirement

Product A

Demand

always collective reqmtsDependent requirements

poss. ind.customer reqmts

Order netw. (fix. pegging)

Material A

MRP 4

2Indiv./collective

Dependent requirements

exclusively coll.

Product A

Demand

always collective reqmtsDependent requirements

poss. ind.customer reqmts

Order netw. (fix. pegging)

Material A

MRP 4

Indiv./collective

Dependent requirements

Indiv. and coll.

1 exclusively indiv.

APO

APO

??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 4-21

? SAP AG 2001

Static Lot-Sizing Procedure

Lot size

Lot-for-lot

100 pc

Procedure

Fixed lot size

MRP 1

FXLot size

Lot-sizing data

Fixed lot size

Product AMaterial A

Periodic P.indicator

FLot size indicator Fixed lot size

Customizing lot size FX

Fixed lot size 100 pc

Product A

Lot size

Lot-for-lotProcedure

Fixed lot size

Material A

MRP 1

EXLot size

Lot-sizing data

Exact lot size

HB Replenish tomax.stk.level

Max. stock level 100Maximum productwarehouse capacity 100

APO

APO

??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 4-22

? SAP AG 2001

Periodic Lot-Sizing Procedure

Product A

Lot size

Lot-for-lot

Fixed lot size

Periodic

Period indic.

Material A

MRP 1

PLLot size Period. lot size

PLot size proced. Period. lot size

WLot size indicator

Customizing lot size PL

1Period number

Week

D Day

M Month

1Conf. of date Start of period

Reqmts date

2 End of period

W Week

D Day

M Month

1

Date determination

XIndic. avail.dates

X

0Periodfactor

1

Procedure

Number of periods

APO

??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 4-23

? SAP AG 2001

Lot Size Parameter

R/3

Matl. A

Product A

Lot size

10 pcMinimum lot size

200 pcMaximum lot size

10 %Assembly scrap

5 pcRounding value

Lot sizedata

0001Rounding profile

30 pcSafety stock

95 %Service level

80 pcReorder point

80 pcProd. warehousecapacity

Max. stock level

APO Customizing:Is the roundingprofile known?

APO

??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 maintena nce 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 4-24

? SAP AG 2001

SNP2, PP/DS, Procurement and GR/GI

Product A

SNP2

001Purchasing group

PP/DS

10 daysCall horizon

Procurement

EProcurement type

14 daysPlan.delivery time

R/3

GR/GI

3 daysGR processing time

0001Loading group

Material APurchasing

001Purchasing group

S and D: gen./Plant

MRP 2

001Sched.margin key

Call horizonSafety time

10 days2 days

...

EProcurement type

14 daysPlan.deliv.time

3 daysGR processing

APO

??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 4-25

? SAP AG 2001

Maintaining Additional Product Master Fields in APO

? Mass maintenance for product master fields inAPO (for those that cannot be transferred from theR/3 System)

? Alternative solution using modification:Enhancement of the R/3 material master recordwith customer-specific fields (Append structures)and transfer of these fields in the integrationmodel (using a customer exit)

??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 4-26

? SAP AG 2001



Plant

Customer

Vendor

Location

Product

Resource


Material master


Routing andbill of material

??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 trans fer 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 4-27

? SAP AG 2001

Transferable from R/3

TransportProduction

Store Handling

Resource Categories

??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 4-28

? SAP AG 2001

Resources in APO

? Single-activity resources (PP/DS)

? Time-continuous

? Available capacity for one activity

? Multi-activity resources (PP/DS)

? Time-continuous

? 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

Transferable from R/3 with customer exit

??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 on e 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 4-29

? SAP AG 2001

Work Center and Resources

Work centerCapacities

001Cap. category Machine

002Cap. category Person

1904

Plant 1000 Resource2 multi mixed

W1904_1000_001

Resource Cat. Location

P 1000

W1904_1000_002 P 1000

"Work center" R/3 plant

An APO resource for each R/3 work center capacity

APO Customer exit: Mixed resource

APO

??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 4-30

? SAP AG 2001

Single and Multi-Activity Resources

Work center

Capacities

Cap. category Machine

1904

Plant 1000

Work center capacity

7:00 to 15:00Work. time

R/3

001

Resource

Multi-activity

W1904_1000_001


P 1000

Single-activity

W1904_1000_001


P 1000

1No. indiv.capacitiesSeveral operations



...

APO

??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 4-31

? SAP AG 2001

Resource Data

R/3

Resource

General data

CETTime zone

01Factory calendarAPO Customizing:

Has factory calendarbeen created?

Work center 1904

Capacities

Cap. category 001

W1904_1000_001

Machine cap. final assembly

Planning details

Rel. for finite scheduling

Standard capacity

7:00 to 15:00Work. time

1 hourBreak durationStandard avail. capacity

Work. time

Break duration

Resource utilization

Capacity

01Factory calend. ID

1Active version

1Active version

No. indiv.capacities

100%Resource utilization

3,000Capacities

Machine capacityfinal assembly

7:00 to 15:00

1 hour

100%

3Planning parameters

Finite scheduling

DE

APO

??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 4-32

? SAP AG 2001

Reference Resource

Work center

Capacities

Cap. category Machine

1905

Plant 1000R/3

001

Ref. avail. capacity

1000Plant

K1900Capacity

001Cap. category

Standard avail. capacity

Work. time

Break duration


7:00 to 15:00

1 hour

3

Resource2 multi mixed

K1900_1000_001

Resource Cat. Reference resource

P


W1905_1000_001 P K1900_1000_001

Transfer of reference available capacity;

APO name contains no W (for work center)

APO

??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 cont aining 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 4-33

? SAP AG 2001

capacityvariants

GeneralData

Resource master data

Break 1 Break 2 Break 3


Break pattern B


Break pattern C

Standard capacity

Definition of Capacity Variants (1)*

? Break data

? Break pattern

? Break number

? Planner

? Start / end of break

? Break after hours / break duration

1st step: Create break pattern

??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 4-34

? SAP AG 2001

Shift factors..CapacityResource utilization...

capacityvariants

GeneralData

Resourcesmaster data

Standard capacity


? Shift factor data

? Shift factor definition

? Validity

? Planner

? Capacity

? Unit of measure

? Resource utilization

2nd step: Create shift factors

??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 4-35

? SAP AG 2001

Shift A


Break pattern B

CapacityResource utilization

Shift factors

capacityvariants

GeneralData


Standard capacity

? Break model data? Break pattern? Break number? Planner? Start/end of break? Break after hours

? Shift data? Shift definition? Validity? Planner? Start/end? Break pattern? Break duration? Shift factors

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


3rd step: Create shifts

??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 4-36

? SAP AG 2001

Shift A

Shiftsequence

Shift B

Shift CShift C Shift C

Day

GeneralData


capacityvariants

Standard capacity

? Shift sequence data? Shift sequence? Day number? Validity? Planner? Non-workdays? Shift 1? . . .? Shift 9

? Shift data? Shift definition

. . .

Shift AShift AShift BShift B


4th step: Create shift sequences

??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 4-37

? SAP AG 2001

Interval

GeneralData


capacityvariants

Standard capacity

? Shift sequence data? Shift sequence

. . .

Time

Interval 2Interval 1Interval 2Interval 1

Time

Interval 2

Shiftsequenceper day

Interval 1Var. 1

Var. 2Var. 3

32 4 5 321 4 532 4 5 321 4 51 1 2 3 1 2 3 1 2 3

? Capacity variant data? Resource? Location? Capacity variant no.? Validity? Workdays? Shift sequence? Day one


5th step: Create capacity variants

??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 4-38

? SAP AG 2001



Break pattern B


Break pattern C

CapacityResource utilization

Shift A

Shift factors

GeneralData


capacityvariants

Standard capacity

Time

Interval 2Interval 1Interval 2Interval 1

Time

Interval 2

Shiftsequenceper day

Interval 1Var. 1

Var. 2Var. 3

32 4 5 321 4 532 4 5 321 4 51 1 2 3 1 2 3 1 2 3

Capacity Definitions: Overview*

??To define working times, break times, resource utilization and capacity in a partic ular 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 4-39

? SAP AG 2001

Determination of Capacity in APO*

Check carried out in:

Resource

Reference resource

Capacity from:

Resource

Reference resource

Does anactive

capacityvariant exist?

YesNo

Doesa reference resource

exist?

Doesa reference resource

exist?

Doesa time interval

with validcapacityexist?

No

Do the same variants

with valid timeintervals

exist?

Standard capacityof resource

Time interval ofreference resource

Time intervalof resource

Yes

YesNo

Standard capacityof reference resource

Yes No

Yes

No

When is the reference resource relevant?APO

??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 4-40

? SAP AG 2001

Pooled Capacities

Work center

Capacities

Cap. category Person

1906

Plant 1000R/3

002

Resource1 multi mixed



POOL_1000_002 P 1000

Transfer of pooled capacity APO name contains no

W (for work center)

Pooled capacity POOL

Standard avail. capacity

Work. time

Break duration


7:00 to 15:00

1 hour

10

APO

??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 4-41

? SAP AG 2001



Plant

Customer

Vendor

Location

Product

Resource


Material master


Routing andbill of material PPM

??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 proces s 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 4-42

? SAP AG 2001

Operations:

e.g.

? Rotate

? Weld

? Paint

? Check

Activities:

? Setup

? Produce

? Tear down

? Product

? Relations

? Resources

Input/output

Resource consumption

Header: Costs, output products, lot size range

Sequence

Overview of Production Process Model

??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 4-43

? SAP AG 2001

R/3 Production Version and APO-PPM

Material AMRP 4

R/3

Production version 0001describes production process

No. 500077

Bill of material

Routing?

?

Production processmodel (PPM)

Plan N500077010001

Product A

APO

??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 transfer red 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 4-44

? SAP AG 2001

Task List Description in APO

R/3

Plan No. N500077010001

Material A

Production version 0001

Bill ofmaterial

RoutingNo. 500077Group counter 01

PPM

Product AAPO

??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 4-45

? SAP AG 2001

Structure of the Production Process Model (1)

PPM

Plan N500077010001

Product A

Operation 10Assembly

Setup activity

Components

Produce activity

Links

Operation 20Checks

Produce activity

Links

...

APO

??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 4-46

? SAP AG 2001

Structure of the Production Process Model (2)

Activities and resources

PPM Product A

Operation 10

Produce activity

Mode 2Primary resource

Secondary resource

W1905_1000_001

W1905_1000_002

Mode 1Primary resource

Secondary resource

W1904_1000_001

W1904_1000_002

Selection of modeis dynamic when

scheduling

??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 4-47

? SAP AG 2001

Operations in PPM

R/3

Operation 10

Control key

PP01

Relevant toscheduling

PPM

Plan N500077010001

Product A

Operation 10

Operation 20Control key

PP02

Relevant toscheduling

Material A

Routing 500077

is transferred

is nottransferred

No control keyin APO

AssemblyAssembly

However, the following are nottransferred:

Operations without work center(in active integration model)

Operations without valid duration(because formulas or standardvalues are missing)

APO

??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 4-48

? SAP AG 2001

Secondary res. W1904_1000_002

Scheduling and Activities

Operation 30 Assembly

Work center 1904

Cap. 001Standardvalue

Setup

Machine

HR

Variable1

Variable2

Variable3

Sch

edu

l.fo

rmu

la 5 MIN

15 MIN

CIF


Setup activity Primary res. W1904_1000_001

Fixed duration 0,083 H

Produce activity Primary res. W1904_1000_001

Variable duration 0,250 H per 1 pc

Schedulingbasis

1. Setup

2. Processing

3. Tear down

002

APO

??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 4-49

? SAP AG 2001

Overview of Activity Relations

Activity 1

Time

START-START

Min. time deviation

Max. time deviation

Activity 1

Activity 2

Time

FINISH-START

Activity 2Min. time deviation

Max. time deviation

??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 4-50

? SAP AG 2001

Activity Relations


Work center 1904

Fo

rmu

las


Setup activity (S)

Produce activity (P)

1. Setup

Setup activity (T)

2. Processing

3. Tear down

Relation S(0030)-P(0030)

Relation P(0030)-T(0030)

Operation 40 Checks

Processing activity (P)

Relation T(0030)-P(0040)Minimum/maximum duration

Operation 40 Checks

Work center 1905

Processing

Minimum wait timeMaximum wait time

Move time

APO

??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 4-51

? SAP AG 2001

Component Assignment

Operation 10

Routing

Operation 20

Operation 30

Bill of material

Matl. B

Matl. C

Matl. D

Matl. A

R/3 Material A

Production version 0001

Component assignment inrouting

PPM Product A

Operation 10

Activity S

InputProd. B

Operation 20

Activity S

InputProd. C

Prod. DInput

Operation 30

Activity P

OutputProd. A

CIF

Materials in active integration

model?

APO

??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 4-52

? SAP AG 2001

CIF Transfer of PPMs: Miscellaneous

The indicator Tear down/parallel wait time in the R/3operation can be transferred+

corresponding relationships in APO

You can transfer the operation-related lead-time offset ofthe R/3 BOM item+

Time-based offset of logical input components inPPM

??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 4-53

? SAP AG 2001

? Basically, master data relevant for productionplanning in R/3 can be transferred from the R/3into the APO System. The additional maintenanceof master data in APO is generally only necessaryfor 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 aslocations with corresponding location types.

? You can transfer material masters into APO asproducts.

APO Master Data: Unit Summary (1)

© SAP AG AP205 4-54

? SAP AG 2001

? Work centers are transferred into APO in the formof their capacities: for each work center capacity aresource is created in APO.

? The production process model in APO is acombination of routing and BOMs. The transfer ofR/3 master data assumes the use of a productionversion in the material master.

APO Master Data: Unit Summary (2)

© SAP AG AP205 4-55

Exercises

Unit: APO Master Data

Topic: Locations


?? 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 4-56

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 he lp in the Location type field to answer this question)?

MRP area: __________________________

Customer: __________________________

Vendor: __________________________

© SAP AG AP205 4-57


Topic: Resources


?? 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 4-58

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


Topic: Production Process Model


?? 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 4-60

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

Solutions


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

© SAP AG AP205 4-63


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 cente r 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 4-64

© SAP AG AP205 4-65


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 t his 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 diffe rent operation.

© SAP AG AP205 4-66

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 activ ities "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##.

© SAP AG AP205 5-1

? SAP AG 2001

? Models and Planning Versions for Master Data andTransaction Data

? Maintaining Models via the Supply Chain Engineer

Contents:

Models and Planning Versions

© SAP AG AP205 5-2

? SAP AG 2001

? Describe the function of models and planningversions for master and transaction data

? Display master data via the Supply ChainEngineer


Models and Planning Versions: Unit Objectives

© SAP AG AP205 5-3

? SAP AG 2001



444


333

222111 Overview

777


APO Master Data


666

888


Conclusion

55

© SAP AG AP205 5-4

? SAP AG 2001

Models and Planning Versions

PPM

Resources

PPM

Resources

Master data

Master data in APO

Active model 000

Locations

Simulationmodel Z01


R/3

Planning version 1 Version-dependent masterdata and transaction data


Simulationmodel n

PPMTransportation

lane

Resources

Active planning version 000 Version-dependent masterdata and transaction data

Active planning version 000 Version-dependent masterdata and transaction data

Planning version n Version-dependent masterdata and transaction data

Planning version n Version-dependent masterdata and transaction data



Products

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

© SAP AG AP205 5-6

? SAP AG 2001

Active planning version 000Active planning version 000

Models and Planning Versions for Locations andProducts

R/3 APOR/3 Master Data APO Master Data

Locations

Products

Active model 000

Planning version 001Planning version 001

Locations

Products

Reference

Planningversion-specificfields may beadded(only valid inversion 001)

Reference

Simulation model Z01

Plant,customer, vendor

Material master

Assignment

Createmaster data

Maintained during master datatransfer

Master data added

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

? SAP AG 2001

Independent of planningversion

Independent of planningversion

Models and Planning Versions for Resources


Resource

Active model 000

Copy

Planningversion-specificfields may beadded(only valid inversion 001)

Copy


Capacity

Assignment

Createmaster data


Master data added

Active planning version 000Active planning version 000

Resource

Planning version 001Planning version 001

Resource

??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 5-8

? SAP AG 2001

Valid for all planning versionsValid for all planning versions

Models and Planning Versions PPMs


PPM

Active model 000


Routing andbill of material

Assignment

Createmaster data


Master data added

??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 5-9

? SAP AG 2001

Supply Chain Engineer (SCE) as the Modeling Toolfor Models

Network structureNetwork structure

Network mapNetwork map

Overviewmap

Overviewmap

PlanningobjectsPlanningobjects

Workareafolder

Workareafolder

??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 5-10

? SAP AG 2001

? Locations

? Transportation lanes

Objects in the Supply Chain Engineer

CarrierCarrierMRPMRPareaarea

Stock transferStock transferpointpoint

Transport-Transport-ationationzonezone

VendorVendor PlantPlant DCDC CustomerCustomer

??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 5-11

? SAP AG 2001

Work Areas in the Supply Chain Engineer

? Access to frequently used objects

? Used for queries

? Serve as filters

? Configured for users

??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 5-12

? SAP AG 2001

Transportation Lanes

? Procurement

? Means of transport

? Products that can be carriedby a means of transport

? Transportation capacity byvolume, weight, pallets

? Transportation costs per unit,product, and means oftransport

??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 5-13

? SAP AG 2001

? Operational planning in the APO System is carriedout in the active planning version 000 of the activemodel 000.

? During master data transfer from an R/3 System,the corresponding APO master data isautomatically assigned to the active version 000 ofthe active model 000.

? You can also use the APO master data in aninactive planning versions. To do so, you mustassign them to the inactive versions.

Models and Planning Versions: Unit Summary

© SAP AG AP205 6-1

? SAP AG 2001

? Transfer of Transaction Data Between R/3 and APOSystems

? Initial and Incremental Data Transfer

? Integration Model for the Transfer of Transaction Data

Contents:


© SAP AG AP205 6-2

? SAP AG 2001

? Describe the concept of transaction data transferbetween R/3 and APO Systems

? Define an integration model for the transfer oftransaction data

? Transfer transaction data


Transfer of Transaction Data: Unit Objectives

© SAP AG AP205 6-3

? SAP AG 2001



444


333

222111 Overview

777


APO Master Data


66

666

888


Conclusion

© SAP AG AP205 6-4

? SAP AG 2001

Transaction Data Interface: Core Interface (CIF)

R/3 APO

Orders- Replenishment order- Manufacturing order- Procurement order...(Distinction by ATP category)

Purchase ordersPurchase requisitionsSales ordersPlanned ordersPlanned ind.reqmtsReservationsStocks...

R/3 transaction data APO transaction dataCore Interface

CIF

Integrationmodel

??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 6-5

? SAP AG 2001

Initial datatransfer

Transaction Data Objects of the CIF

R/3 APO

Order with category BF (PchOrd) AG (PurRqs) BM (SalesOrder) AI (PlOrd.) FA (FC req.) AM (PrdRes) CC (Stock) ...

R/3 transaction data APO transaction data

Purchase orders

Purchase requisitions

Sales orders

Planned orders

Planned ind.reqmts

Reservations

Stocks...

Real-time

Incrementaldata transfer

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

? SAP AG 2001

Initial Data Transfer of Transaction Data: Overview

1. Generate integration model NameTarget sys.

Sales ordersProduction/process orders

Storage location stock...

Determine name and APOtarget system

Select transaction data

2. Activate integration model

Integration model is active

Initial transfer of transaction data is performed,followed by a continuous real-time incrementaldata transfer

Start

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

? SAP AG 2001

Integration Model for Transaction Data

Name PUMPS


Application BEW_DATA

Sales orders

Production/process orders

Planned orders

Storage location stocks

Relevant materials

Material

Plant 1000

MRP type X0

Name + application = unique definition of integration model

APOAPOSystemSystem

Selection oftransaction data types

Selection criteria forthe transaction data

Execute Save+...

...

??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 6-8

? SAP AG 2001

Activate Integration Model for Transaction Data

Name PUMPS


Application BEW_DATA

Integration model

"Activate" Active/Inact.

PUMPS APOCLNT800 BEW_DATA

Start

Transaction datain APO

Material master A Material master A Stor loc . stock BPlanned order A

R/3

Material master A Material master A Stor loc . stock BPlanned order A

10:00:00

R/3

Stor loc . stock B

Planned order A

Incrementaldata transferautomatic

APO

??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 in to 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 6-9

? SAP AG 2001

Publication of Planning Results

Planning results inAPO

APO

e.g.

Planned order xR/3

or Collect thechanges

Planned order x

Periodictransfer

WhichR/3 System?

R/3Plant A Plant B

??In APO transaction /SAPAPO/C4 you set how (in w hat 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 6-10

? SAP AG 2001

Possible Scenarios (1)

Demand Planning (DP)

Planned ind.reqmt

Production Planning (PP/DS)

Planned order

Manuf. order

Planned order

Shop Floor Control (SFC)

R/3Create

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

Name PUMPS

TargSys.APOCLNT800

Applic. BEW_DATA

Storage location stcks

Planned orders

Prod./process orders

Relevant materials

Plant 1000

MRP type X0

Integration model

Do not plan materials in R/3 butexplode BOM if required

APO

Manuf. order

Execute

??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 6-11

? SAP AG 2001

Create

Possible Scenarios (2)

Demand managementPlanned ind.reqmt

Production Planning (PP/DS)Planned order

Manuf. order

Shop Floor Control (SFC)

R/3Create

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

Name PUMPS

TargSys.APOCLNT800

Applic. BEW_DATA

Storage location stcks

Planned orders

Prod./process orders

Relevant materials

Plant 1000

MRP type X0

Integration model

Do not plan materials in R/3 butexplode BOM if required

Planned ind.reqmt

R/3

Planned ind.reqmtsAPO

Planned order

Manuf . order

Execute

??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 6-12

? SAP AG 2001

? The transaction data that is to be transferredbetween R/3 and APO is selected via anintegration model in CIF.

? In an initial data transfer, the transaction data istransferred to APO from R/3 for the first time. Thisis followed by a real-time incremental datatransfer. This means that data changes to existingtransaction data or new transaction data areimmediately exchanged between the two systems.

Transfer of Transaction Data: Unit Summary (1)

© SAP AG AP205 6-13

? SAP AG 2001

? Which transaction data you select in theintegration model depends directly on theplanning process. There are several usefulscenarios of how the R/3 System and APO Systemcan cooperate, all of which are based on differentintegration models.

Transfer of Transaction Data: Unit Summary (2)

© SAP AG AP205 6-14

© SAP AG AP205 6-15

Exercises

Unit: Transfer of Transaction Data

Topic: Transfer of Planned Orders


?? 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 6-16

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

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

© SAP AG AP205 6-19

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

? SAP AG 2001

? Monitoring of Application Errors Using the qRFCMonitor

? Error Analysis in the Application Log

? SCM Queue Manager

? Notification about Queue Blocks Using qRFC Alert

? Compare/Reconcile Functions to Ensure DataConsistency in R/3 and APO

Contents:


© SAP AG AP205 7-2

? SAP AG 2001

? Use the qRFC monitor to monitor applicationerrors

? Use the application log to perform an erroranalysis

? Explain the concept of the SCM Queue Manager

? Describe the compare/reconcile functions used toensure data consistency in R/3 and APO


Monitoring/Error Handling: Unit Objectives

© SAP AG AP205 7-3

? SAP AG 2001



444


333

222111 Overview

77


APO Master Data


666

888


Conclusion

77

© SAP AG AP205 7-4

? SAP AG 2001

Integration Monitoring

R/3 APO

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

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

? SAP AG 2001

qRFC Monitor: Motivation

R/3 APO

RemoteFunction

Call (RFC)

Core Interface(Selection andextraction of

data)

Core InterfaceCore Interface(Selection and(Selection andextraction ofextraction of

data)data)

Master/Movement data


APO master/transaction data

liveCachelive

Cache

Asynchronous transfer technology

1. Buffer data2. Transfer to target system

- Communication errors- Application errors

RemoteFunction

Call (RFC)

APO transaction data

qRFC Monitor

qRFC Monitor

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

? SAP AG 2001

Using the qRFC Monitor (1)

CF_ADC_LOAD

qRFC Monitor (Outbound queue)

Client Queue name Destination Entries

APOCLNT800 3800

Refresh

CRM_DELT_MATERIAL IPC 3800

CF_ADC_LOAD APOCLNT800 3800StatusSYSFAIL

1. Date02.10.2002

......Refresh Activate queue Lock queue Unlock queue

MUSTER /SAPAPO/CIF_LOC_INBOUND800Status textYou are not authorized to logon

Refresh Execute LUW

Client User Function module

Client Queue name Destination

Debug LUW (Logical Unit of Work)

MUSTER /SAPAPO/CIF_PROD_INBOUN800 Transaction recordedMUSTER /SAPAPO/CIF_RES_ INBOUND800 Transaction recorded

Queue channel CF_ADC_LOAD = initial data transfer

R/3Master datatransfer

Example: qRFC Monitor in R/3Example: qRFC Monitor in R/3

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

? SAP AG 2001

Material C

R/3 APO

Queue Channels for Data Transfer: Example

CF_ADC_LOAD

Initial transferMaster and

transaction data

Queue channels

PPM for material C, D, material D


liveCache

liveCacheCFPO[PO number]

PO number 4711Material AOnline

transferPurchaseorders

PO number 4712Material A

CFMAT[mat.no.]

Material AIncrementaldata transferMaterial Material B

(if an active integration modelexists for purchase orders for

material A)

Material AMaterial BPPM Material APPM Material B

Material E

Integration model Y

Integration model Z

PPM for material A, B; material A, BIntegration model X

(active)

(Data channel blocked)

(if active integration modelsexist for materials A and B)

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

? SAP AG 2001

Example: qRFC Monitor in APOExample: qRFC Monitor in APO

Using the qRFC Monitor (2)

CFEP3040

qRFC Monitor (Outbound queue)

Client Queue name Destination Entries

R3CLNT800 1800

Refresh

CFIP3056 R3CLNT800 1800

CFIP3056 R3CLNT800 1800StatusSYSFAIL

1. Date02.10.2002

......Refresh Activate queue Lock queue Unlock queue

MUSTER CIF_ORDER_INBOUND_30A800Status textNo active integration model

Refresh Execute LUW


Client Queue name Destination

Debug LUW (Logical Unit of Work)

MUSTER CIF_ORDER_INBOUND_30A800 Transaction recorded

Queue channel "CFIP*" = In-house production

APOPlanned ordercreated in APO

??In the example above, a planned order for a finis hed 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 7-9

? SAP AG 2001

ApplicationlogR/3:Error

R/3 APO

RFCCore InterfaceCore InterfaceCore Interface




liveCachelive

Cache


Application Log: Motivation

RFC

Applicationlog

APO:Error

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

? SAP AG 2001

Using the Application Log (1)

MUSTER /SAPAPO/CIF_TPSRC_INBOU800Status textLoc. 0000001003 does not exist

Refresh


MUSTER /SAPAPO/CIF_GEN_EVENT800 Transaction recorded

qRFC Monitor R/3

MUSTER Initial data supply02.10.2002 530

User Subobject typeDate Number

R/3 Application Log

USERADMIN Sources of supply02.10.2002 4


APO Application Log

Problem class: very importantProblem class: mediumProblem class: additional information

Location 0000001003 does not exist

Function: CIF_LOCATION_SEND: Plant 1000

Example: Application Log in R/3Example: Application Log in R/3

??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 fie ld 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 7-11

? SAP AG 2001

Using the Application Log (2)

Example: Application Log in APOExample: Application Log in APO

RefreshAPO qRFC Monitor

MUSTER In-house production02.10.2002 120


APO Application Log

USERADMIN In-house production02.10.2002 1


R/3 Application Log

Problem class: very importantProblem class: mediumProblem class: additional information

Inbound R3CLNT800: For system APOCLNT800 no active integrationmodel for type T_PLO filter object P-102 1000

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

MUSTER CIF_ORDER_INBOUND_30A800Status textNo active integration model


MUSTER CIF_ORDER_INBOUND_30A800 Transaction recorded

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

? SAP AG 2001

SCM Queue Manager (1)

R/3 SCM Queue Manager

Systems

APO Execute

Object types

Systems R3CLNT800Expand nodes

APO outbound types EPPlug-in outbound types T_INITIAL

EP Ext. ProcurementIP In-House Production...

T_INITIAL Initial trans. T_ORD Planned ords,.....

R/3 APO- Communication errors- Application errors

RFC

RFC

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

? SAP AG 2001

SCM Queue Manager (2)

R3CLNT800

System: APOCLNT800 Type: In-house production

Queue Destination User Date

MUSTER ...No active integrationmodel

Error text

CFIP3056

APOCLNT800

R3CLNT800

External procurementIn-house productionPlanned ind. reqmntsPlanning file entriesProduction campaignsSales orderTransportationDeliveryReservations...

Initial supplyPurchase ordersPlanned ordersProduction ordersSales ordersPlanned ind. requirements.Manual reservationsProduction campaignsConfirmationsTransportationsStocksCharacteristicsClasses

R32CLNT800Initial data supply...

Refresh Appl.log

© SAP AG AP205 7-14

? SAP AG 2001

qRFC Monitoring: Notification about ExceptionMessages (1)

R/3 APO

RFCCore InterfaceCore InterfaceCore Interface



APO master/APO master/transaction datatransaction data

liveCachelive

Cache


RFC

Mail to initiator oradministrator

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

? SAP AG 2001

qRFC Monitoring: Notification about ExceptionMessages (2)

R/3 qRFC Monitoring

Local outbound queues

APO Execute

Remote outbound queues

Target systems *Local queue names CF*

Queue errors onlyNotification

NoTo initiatorTo administrator MUSTER B

Remote systemsDestinations

Queue errors only (remote system)Notification...

Remote queue names CF*

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

? SAP AG 2001

R/3

Compare/Reconcile Function for DataInconsistencies in R/3 and APO: Compare

Report /SAPAPO/CIF_DELTAREPORT2

Sales orders

Objects to be checked

Production/process ordersPurchase requisition

APO

Partner system (R/3) R3CLNT800

Material P-102

Plant 100

Integration model Pump

......

Storage location stocksSales order stocks

......

(optional)

(optional)

(optional)

liveCacheDatabase

Compare

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

? SAP AG 2001

Compare/Reconcile Function for DataInconsistencies in R/3 and APO: Reconcile

R/3 Report results list

Sales orders

Documents

Production/process orders

APO

...

Storage location stocks...

liveCacheDatabase

Sales orders

Supplies

Reconcile

Results Storage loc.stocks

P-102

? Deviations in APO

Sent Material StockQuantity

APO Reason

? Send to APO? Send to APO

11 10 ...1000

Plant

0002

Storagelocation

?

Execute

© SAP AG AP205 7-18

? SAP AG 2001

? Data transfer between R/3 and APO is carried outasynchronously. Errors occuring during the datatransfer can therefore be processed separately.Technical problems or application errors can causethese errors.

? There are different functions for error handlingavailable in R/3 and APO: the qRFC Monitor and theapplication log.

? You can use the compare/reconcile function toremove data inconsistencies between R/3 and APO.

Monitoring/Error Handling: Unit Summary

© SAP AG AP205 8-1

? SAP AG 2001

Conclusion


444


333

222111 Overview

777


APO Master Data


666

888


Conclusion

© SAP AG AP205 8-2

? SAP AG 2001

Course Objectives

You are now able to:

? Describe the architecture of integration of ERPsystems with the APO System

? Select master and transaction data to transferfrom R/3 into APO

? Specify where in the APO System it may benecessary to add to the master data transferredfrom the R/3

? Describe the monitoring and thecompare/reconcile functions used to ensure dataconsistency in R/3 and APO

© SAP AG AP205 8-3

? SAP AG 2001

Recommended Follow-up Courses

? AP215 Supply Network Planning (SNP)

? AP220 Production Planning & Detailed Scheduling (PP/DS)

? AP230 Global Available to Promise (ATP)

Integration of transaction data is directly dependent on theindividual APO planning functions. It is therefore described ingreater detail in the APO application courses. These coursesalso provide more detailed information on master data.

© SAP AG AP205 8-4

? SAP AG 2001

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 AP205 Appendix I-1

? SAP AG 2001

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

Contents:

Appendix: Supplement to BSGs


? SAP AG 2001

Business Situation

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

? Some products are planned in the R/3 Systems underdifferent material numbers.

? These materials are planned as one product in differentplants in APO.

? The retransfer of the planning results from APO into the R/3Systems will take place with the R/3-dependent materialnumbers.


? SAP AG 2001

Concrete Example

R/3-1R/3-1 APOAPO

Planning forproduct 60015Planning for

product 60015

Material 70015Plant 0002

Material master

Product 60015Location 0001Location 0002

Product

Transferplanning result

to the R/3Systems

Transferplanning result

to the R/3Systems

Planned orders

Initial transfer ofmaterial 70015,

plant 0002


plant 0002


R/3-2R/3-2


Material master

Planned orders


plant 0001


plant 0001



? SAP AG 2001

Solution to the Problem using BSGs (1)

R/3-1R/3-1

APOAPO

R/3-2R/3-2

Busine

ss

System

Group

BSG_1

BusinessSystemGroupBSG_2


? SAP AG 2001


? For each R/3 System, define a separate business systemgroup.

? Assign the (logical) R/3 Systems to their business systemgroups.

? Activate the customer exitEXIT_/SAPAPO/SAPLCIF_PROD_001 (APOCF005) for theinitial transfer of material masters.


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


Prerequisites

? APO 3.0 with Support Package 4

? The parameter EF_DUP_CHECK in the customer exitEXIT_/SAPAPO/SAPLCIF_PROD_001 (APOCF005) must beset to 'A', so that multiple entries are allowed (for the internalmaterial number).

© SAP AG AP205 Appendix II-1

? SAP AG 2001

? Mapping a R/3 master recipe (PP-PI) onto an APOproduction process model.

Contents:

Appendix: Master Recipe (PP-PI)


? SAP AG 2001

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

Master Recipe and PPM in APO 3.0

Res. Y

Secondary resource 500

Sec.res. 400

Res. X

Operation 10

Phase 11

Phase 12

Res. A

Res. A

Master Recipe PPM

Res. Y

Operation 10 - operation type 1 (PI operation)

Operation 11 - transfer oper. 10, oper.type 2 (PI phase)

Act. 11 - Setup/Produce

Res. A

Res. A

Res. X

Operation 12 - transfer oper. 10, oper.type 2 (PI phase)

Act. 12 - Produce

Operation 400 - transfer op. 11, op. type 3 (PI sec.res.)

Act. 400 - Produce

Operation 500 - transfer op. 10, op. type 3 (PI sec.res.)

Act. 500 - Produce


? SAP AG 2001

Relationships/Activity Relationships

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

Act. 500

Act. 400

Operation 10 Operation 20

R/3

APO

Order-internal activity relationships

Operation-internal activity relationships

Phase 11 Phase 12

Sec.res 400

Sec.res 500

Phase 21 Phase 22 Phase 23

Assignment of secondary resources

Relationships

( )