SCM120-CoreInterfaceSAPSCMParticipant.pdf

SCM210Core Interface SAP SCM

mySAP Supply Chain Management

Date

Training Center

Instructors

Education Website

Participant HandbookCourse Version: 2004 Q3Course Duration: 2 Day(s)Material Number: 50069930

An SAP course - use it to learn, reference it for work

Copyright

Copyright © 2004 SAP AG. All rights reserved.

No part of this publication may be reproduced or transmitted in any form or for any purposewithout the express permission of SAP AG. The information contained herein may be changedwithout prior notice.

Some software products marketed by SAP AG and its distributors contain proprietary softwarecomponents of other software vendors.

Trademarks

� Microsoft®, WINDOWS®, NT®, EXCEL®, Word®, PowerPoint® and SQL Server® areregistered 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.� Citrix®, the Citrix logo, ICA®, Program Neighborhood®, MetaFrame®, WinFrame®,

VideoFrame®, MultiWin® and other Citrix product names referenced herein aretrademarks of Citrix Systems, Inc.

� 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, SAP ArchiveLink, SAP Business Workflow, WebFlow,

SAP EarlyWatch, BAPI, SAPPHIRE, Management Cockpit, mySAP.com Logo andmySAP.com are trademarks or registered trademarks of SAP AG in Germany and inseveral other countries all over the world. All other products mentioned are trademarksor registered trademarks of their respective companies.

Disclaimer

THESE MATERIALS ARE PROVIDED BY SAP ON AN "AS IS" BASIS, AND SAP EXPRESSLYDISCLAIMS ANY AND ALL WARRANTIES, EXPRESS OR APPLIED, INCLUDINGWITHOUT LIMITATION WARRANTIES OF MERCHANTABILITY AND FITNESS FOR APARTICULAR PURPOSE, WITH RESPECT TO THESE MATERIALS AND THE SERVICE,INFORMATION, TEXT, GRAPHICS, LINKS, OR ANY OTHER MATERIALS AND PRODUCTSCONTAINED HEREIN. IN NO EVENT SHALL SAP BE LIABLE FOR ANY DIRECT,INDIRECT, SPECIAL, INCIDENTAL, CONSEQUENTIAL, OR PUNITIVE DAMAGES OF ANYKIND WHATSOEVER, INCLUDING WITHOUT LIMITATION LOST REVENUES OR LOSTPROFITS, WHICH MAY RESULT FROM THE USE OF THESE MATERIALS OR INCLUDEDSOFTWARE COMPONENTS.

About This HandbookThis handbook is intended to complement the instructor-led presentation ofthis course, and serve as a source of reference. It is not suitable for self-study.

Typographic ConventionsAmerican English is the standard used in this handbook. The followingtypographic conventions are also used.

Type Style Description

Example text Words or characters that appear on the screen.These include field names, screen titles,pushbuttons as well as menu names, paths, andoptions.

Also used for cross-references to otherdocumentation both internal (in thisdocumentation) and external (in other locations,such as SAPNet).

Example text Emphasized words or phrases in body text, titlesof graphics, and tables

EXAMPLE TEXT Names of elements in the system. These includereport names, program names, transaction codes,table names, and individual key words of aprogramming language, when surrounded by bodytext, for example SELECT and INCLUDE.

13-08-2004 © 2004 SAP AG. All rights reserved. iii

About This Handbook SCM210

Type Style Description

Example text Screen output. This includes file and directorynames and their paths, messages, names ofvariables and parameters, and passages of thesource text of a program.

Example text Exact user entry. These are words and charactersthat you enter in the system exactly as they appearin the documentation.

<Example text> Variable user entry. Pointed brackets indicatethat you replace these words and characters withappropriate entries.

Icons in Body TextThe following icons are used in this handbook.

Icon Meaning

For more information, tips, or background

Note or further explanation of previous point

Exception or caution

Procedures

Indicates that the item is displayed in theinstructor�s presentation.

iv © 2004 SAP AG. All rights reserved. 13-08-2004

ContentsCourse Overview ...... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vii

Course Goals.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .viiCourse Objectives .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .vii

Unit 1: Integration in SAP SCM...... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1Overview of Integrating SAP R/3 and SAP SCM.... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3Technical integration of SAP R/3 and SAP SCM .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8Generating and Activating Integration Models .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30Monitoring and Error handling tools for integrating SAP R/3 and SAP SCM... . . . . . 46Incremental Transfers for Master Data Changes .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69Organizing Integration Models ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83

Unit 2: Integrated SCM Master Data..... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93Locations in SAP SCM.... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96Material Masters in SAP SCM ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111Resources in SAP SCM ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .131Production Process Models (PPM).. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .156Run Time Objects (RTO)/ Production Data Structure (PDS).. . . . . . . . . . . . . . . . . . . . . . . .184Purchasing Information Records ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .193Transportation Lanes... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .201Master Recipes and the PPM.... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .209

Unit 3: Modeling in mySAP SCM...... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .225Models ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .226Versions in SAP SCM ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .234Modeling with the Supply Chain Engineer.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .246

Unit 4: Integrating Transactional Data..... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .263Setting up Transactional Data Transfer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .264Generating and Activating Integration Models .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .282

Index ..... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .305

13-08-2004 © 2004 SAP AG. All rights reserved. v

Contents SCM210

vi © 2004 SAP AG. All rights reserved. 13-08-2004

Course OverviewThis course is designed to instuctor consultants and super users on the innerworkings of the Core Interface. You will be instructed on the necessary stepsto connect the landscape as well as the congfiguration necessary to transfermaster data initially and any changes from SAP R/3 to SAP SCM. In additionyou will be introduced to the steps required to transfer transactional datafrom SAP R/3 to SAP SCM and back.

Target AudienceThis course is intended for the following audiences:

� Customers, Implementation Partners and SAP Consultants

Course PrerequisitesRequired Knowledge

� Basic knowledge of SAP R/3 Master Data

Recommended Knowledge

� Basic knowledge of Material Masters, Bills of Materials, Routings, WorkCenters and Location data.

� Basic understanding of supply chain planning concepts.

Course GoalsThis course will prepare you to:

� Understand the steps and tools to integrate an SAP SCM system with aSAP R/3 system to enable intensive supply chain modeling and planning

Course ObjectivesAfter completing this course, you will be able to:

� Identify the necessary steps to setup integration between and SAP R/3system and an SAP SCM (APO) system

13-08-2004 © 2004 SAP AG. All rights reserved. vii

Course Overview SCM210

� Identify the tools necessary to initiate and monitor the continuoustransfer for master data and transactional data between and SAP R/3and an SAP SCM system.

� Transfer master data from SAP R/3 to SAP SCM and familiarize yourselfwith the results.

� Review the master data modeling structure in SAP SCM� Review the steps of transactional data integration and transfer planning

results from SAP SCM to SAP R/3.

SAP Software Component InformationThe information in this course pertains to the following SAP SoftwareComponents and releases:

viii © 2004 SAP AG. All rights reserved. 13-08-2004

Unit 1Integration in SAP SCM

Unit OverviewIn this unit you will be instructed on the details of setting up integrationbetween SAP R/3 and SAP SCM. This will include linking the two systems anddemonstrating intial integration configuration. Users will setup integrationmodels to initally transfer master data, and review the steps necessary toinitiate a change or �delta� tansfer. Lastly, users will be instructed on varioustools that can be used to monitor and correct any data transfer issues.

Unit ObjectivesAfter completing this unit, you will be able to:

� Explain the basic concept of integrating SAP SCM to a OLTP (On-lineTransaction Processing System) system.

� Give a basic explanation as to how SAP R/3 and SAP SCM systemsintegrate.

� Explain the basic steps to integrate an SAP R/3 and an SAP SCM System� Demonstrate the need or use of RFC connections between SAP R/3 and

SAP SCM systems� Explain the use of Inbound and Outbound queues when integrating SAP

R/3 and SAP SCM.� Explain the purpose of Business system groups in integration SAP SCM

with one or more OLTP systems.�� Create integration models for transfer of transactional data using SAP

recommended selection methods.� Activate integration models for transfer of transactional data.� Describe the data transfer process, and how errors are recorded� Demonstrate the qRFC Monitor and explain its purpose in handling

transfer errors

13-08-2004 © 2004 SAP AG. All rights reserved. 1

Unit 1: Integration in SAP SCM SCM210

� Demonstrate the Application Log and explain its purpose n handlingtransfer errors

� Demonstrate the SCM Queue Manager and explain its purpose inhandling transfer errors

� Demonstrate the qRFC Alert and explain its purpose in handling transfererrors

� Explain the differences between the Post Processing and the previouslymentioned tools.

� Demonstrate the Compare/Reconcile functionality and explain itspurpose in handling transfer errors

� Explain how new SAP SCM relevant data is transfer automatically fromSAP R/3 via existing integration models

� Explain how changes in SAP R/3 to existing integrated data, will betransfer to SAP SCM via the CIF.

� Organize integration models according to SAP recommendations.

Unit ContentsLesson: Overview of Integrating SAP R/3 and SAP SCM.... . . . . . . . . . . . . . . . . . . . .3Lesson: Technical integration of SAP R/3 and SAP SCM.... . . . . . . . . . . . . . . . . . . . .8

Procedure: Defining Flexible RFC Destinations... . . . . . . . . . . . . . . . . . . . . . . . . . . 15Procedure: Business System Groups ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23Exercise 1: Architecture of Integration... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

Lesson: Generating and Activating Integration Models.. . . . . . . . . . . . . . . . . . . . . . . . 30Exercise 2: Transfer of Master Data ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

Lesson: Monitoring and Error handling tools for integrating SAP R/3 and SAPSCM.... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

Procedure: Monitoring transfer errors with the qRFC monitor. . . . . . . . . . . . . 52Procedure: Application Log for Error Processing .. . . . . . . . . . . . . . . . . . . . . . . . . . 55Procedure: Monitoring transfer errors with the SCM Queue Manager .. . 57Procedure: Managing transfer errors with the qRFC Alert .. . . . . . . . . . . . . . . . 59Procedure: Compare/Reconcile Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67

Lesson: Incremental Transfers for Master Data Changes.. . . . . . . . . . . . . . . . . . . . . 69Procedure: Setting Background jobs for Master Data Transfer .. . . . . . . . . . 72

Lesson: Organizing Integration Models .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83

2 © 2004 SAP AG. All rights reserved. 13-08-2004

SCM210 Lesson: Overview of Integrating SAP R/3 and SAP SCM

Lesson: Overview of Integrating SAP R/3 and SAP SCM

Lesson OverviewThis unit discusses the integration methods between and SAP SCM systemand one or more Online Transaction Processing Systems (OLTP)

Lesson ObjectivesAfter completing this lesson, you will be able to:

� Explain the basic concept of integrating SAP SCM to a OLTP (On-lineTransaction Processing System) system.

� Give a basic explanation as to how SAP R/3 and SAP SCM systemsintegrate.

Business ExampleYour organization currently uses SAP R/3 for planning and has acquired SAPSCM for more intensive supply chain modeling and planning. You need tohave a general understand for how these two separate systems will integrateto allow your company to leverage its SAP SCM investment for supply chainmodeling/planning.

Integrating SAP SCM to a On-line Transaction ProcessingSystem (OLTP)As you should already be aware SAP has divided supply chain planning andexecution into two discinct functions and has created two distinct softwarepackages, one to handle execution (SAP R/3) and another to handle advancedplanning (SAP SCM). These two systems have been developed separately,therefore they have two separated data bases for both transactional data andmaster data. However, in order for any business to function properly, thesetwo systems need to act as one. In order to ensure that businesses can functionin a real time environment, SAP has developed software that will allow thetwo systems to interact seamlessly in real time. The software that integratesSAP R/3 with SAP SCM is called the Core Interface (CIF)



Figure 1: Core Interface

The Core Interface (CIF) is responsible for the data exchange between SAPR/3 and SAP SCM Systems. The CIF is a real-time interface that links SAPSCM with one or several SAP R/3 Systems. Only the data objects needed inthe data structures in SAP SCM for the different planning and optimizationprocesses are transferred from the complex data set of the SAP R/3 systeminto SAP SCM. The Core Interface guarantees both the initial data transfer(initial transfer) and also the transfer of data changes within SAP SCM. Theintegration of SAP R/3 with the CIF interface is possible as of release 3.1I.Earlier releases or an R/2 System can be connected with BAPIs as "Non-SAPR/3 Systems". (BAPI = Business Application Programming Interface).

Integrating SAP R/3 to SAP SCMOnce a customer has purchased one of SAP�s �mySAP� products (SAP SCM,SAP BW, SAP CRM, etc....), a software component called the SAP R/3 Plug-inmust be installed if your SAP R/3 system is to integrate with any of the SAPExtension products. The Plug-in software will enable businesses to integrate amySAP component (for example, SAP SCM or SAP BW) with one or severalSAP R/3 Systems. With the SAP R/3 Plug-in, several mySAP componentscan be inserted at the same time. Most Plug-ins concern add-ons (SAPR/3 standard software enhancements with additional functions). DifferentmySAP components can be supplied with transaction and master data fromthe SAP R/3 Plug-in. In this way, the CIF interface not only provides theSAP SCM system with initial data records (initial supply), it also guaranteesa step-by-step supply with all the relevant data changes. In the case that



the BW within SAP SCM needs to be integrated with your SAP R/3 system,Extractors are provided by the plug-in to support data transfer of masterdata and transactional data.

Figure 2: SAP R/3 Plug-In Technology

The integration between SAP R/3 and SAP SCM is possible as of release 3.1I.For earlier releases, R/2 or non-SAP products standard BAPIs exist, and can befound by executing transaction BAPI in SAP SCM. However, the necessarycode will have to be written to link the transaction in the execution systemto the SAP SCM transaction.

One area of the CIF that users will become very familiar with is the integrationmodel. Integration models will be the mechanism that users will choosespecifically which master data and transactional data needs to pass betweenthe two systems. Planners will be responsible for determining when newmaster data is created, whether it is SAP SCM relevant data, and therefore,should be included in an integration model.



Figure 3: Integration Models and the CIF

Users will typically set up multiple integration models depending how theyhave arranged for the data to be transferred in large quantities. Integrationmodels are created in SAP R/3 with a specific SAP SCM system as it�sdestination or target. SAP has provided some rough guidelines that will assistcompanies in creating and monitoring the data transfer. Integration modelswill be used to perform both the initial data loads and delta updates.

Initial LoadThe first time specific master data or transactional data is set to therecieving SAP SCM system.

Delta UpdatesAs more SAP SCM relevant data is created, periodic background jobswill be run, to re-create the existing integration models allowing fornew master data to be sent to SAP SCM or terminating integration forobsolete master data.

For easy integration from SAP R/3 to SAP SCM, it is necessary to install thePlug-in relevant to the SAP R/3 release that your company is using. As of 2003,Plug-ins are released once a year pertaining to new functionality. Also notethat support packages are delivered periodically for the plug-ins. For moreinformation regarding how the plug-in might affect your implementationgo to:



Lesson Summary

You should now be able to:� Explain the basic concept of integrating SAP SCM to a OLTP (On-line

Transaction Processing System) system.� Give a basic explanation as to how SAP R/3 and SAP SCM systems

integrate.



Lesson: Technical integration of SAP R/3 and SAP SCM

Lesson OverviewThis lesson will describe the initial steps to setting up your SAP R/3 system tointegrate with your SAP SCM system.


� Explain the basic steps to integrate an SAP R/3 and an SAP SCM System� Demonstrate the need or use of RFC connections between SAP R/3 and



with one or more OLTP systems.�

Business ExampleYour organization currently uses SAP R/3 for planning and has acquired SAPSCM for more intensive supply chain modeling and planning. You need tounderstand some of necessary technical settings for connecting these twoseparate systems to enable your company to leverage its SAP SCM investmentfor supply chain modeling/planning.

Overview of Setting up integrationThe first steps in integrating SAP R/3 and SAP SCM will typically be doneby our Basis implementation team. Several of these settings are relevant formore than just integrating with SAP SCM. They are part of the fundamentalimplementation and upgrade methodology that is outlined by SAP. Themajority of these settings are also typically performed only once, and mayonly need to but updated based on the newest release of SAP SCM that youare using.


SCM210 Lesson: Technical integration of SAP R/3 and SAP SCM

Figure 4: Structure of an RFC Link: Overview

Defining Logical SystemsThe first step in integrating two distributed data bases is to identify the uniquesending and receiving systems in your SAP landscape. Every client in anSAP system must be uniquely identified in case data will be shared betweena particular client in another landscape or another OLTP system (non-SAP).The unique identifier is called the Logical System Name. You must createthese logical system names in both SAP R/3 and SAP SCM. SAP recommendsthat you name the logical system as follows: [System name]CLNT[Clientname], for example, OMOCLNT800 for client 800 in system OMO, and givea good description so it is easy to identify the purpose of the logical system(e.g. R/3, CRM, SCM).



Figure 5: Defining Logical Systems

Once both logical system names have been created in both the SAP R/3and SAP SCM systems, you must assign these logical system names to thephysical clients that exist in both systems, so that the systems can be uniquelyaddressed in a complex system landscape. Even though you created twological system names you will assign in the SAP R/3 system the SAP R/3 logicalsystem name to the SAP R/3 client and in the SAP SCM system the SCM logicalsystem name to the SCM client. Do not assign both names in both systems!

Caution: There are additional settings in this table that relate to astandard currency and how/if changes to configuration settings areallowed and managed. Consult you basis team or project manager todetermine what settings should be set.

RFC Link Destinations in SAP SCM integrationOnce all clients that will be integrating for your SCM solution has beenidentified in SAP terms, we must identify where the physical server/clientsits on the network infrastructure. In order to communicate between youSAP R/3 and SAP SCM systems you will establish an RFC (Remote FunctionCall) destination.



Remote Function CallAn SAP interface protocol based on CPI-C (Common ProgrammingInterface-Communication) used to simplify the programming ofcommunication processes between systems. RFC�s enable you to calland execute predefined functions in a remote system - or in the samesystem. They manage the communication process, parameter transferand error handling.

Figure 6: Defining RFC Destinations

RFC destinations create and reverse the link between theSAP R/3 and the SAPSCM Systems. You define the RFC destinations that are �R/3 connections�(for both SAP R/3 and for SAP SCM) in the administration of the particularsystems, transaction Define Target Systems for RFC Calls (transaction codesm59). In the SAP R/3 system, RFC destination in SAP R/3 under the logicalSCM System name that you have defined and assigned an SCM client to(in our example APOCLNT800). As a target machine, you enter the serveraddress of the SCM server and the system number, so that the SCM Systemcan be addressed in the network.



Figure 7: RFC Destination ConfigurationFigure 7: RFC Destination Configuration

Finally, you enter a user that will create the link to the SAP SCM System. Thisuser must exist in the SAP SCM System and have full authorization. This isnecessary for the transfer of master and transaction data into SAP SCM . Dothe same in SAP SCM : You create an RFC destination under the logical SAPR/3 System name that you have defined and assigned an SAP R/3 client to (inour example, R3CLNT800). You enter the target machine and system numberof the SAP R/3 System. Finally, you enter a user that exists in the SAP R/3System and has the necessary authorization. You can set the RFC destinationsbetween the SAP R/3 and SAP SCM System, so that if an error in the transferoccurs, a new attempt at transferring automatically starts.

Flexible RFC DestinationsAs of SCM 4.0, companies will have the opportunity to use multiple or flexibleRFC destinations. This change came about due the need of two types of datatransfer between SAP R/3 and SAP SCM, pure background data transfer, andcalling up user transactions like a Global ATP check. In the case of users callingtransactions from either SAP SCM or SAP R/3 , we need to assure that they infact have authorization to perform the transaction. In earlier releases the RFC



destination had only one user to log in under, and they had to have access toall necessary integration transactions. As of SCM 4.0 and Plug-in PI2003.1,users can now setup different RFC destinations for the following scenarios:

� In SAP R/3

� Debugging in SAP SCM� Calling up the QRFC monitor in SAP SCM� Displaying the Application log in SAP SCM� Carrying out availability checks in SAP SCM

� In SAP SCM

� Debugging in SAP R/3� Calling up the QRFC monitor in SAP R/3� Displaying the Application log in SAP R/3

Figure 8: Flexible RFC Destination ConfigurationFigure 8: Flexible RFC Destination Configuration



In order to use Flexible RFC Destinations you will have to follow three steps:

1. Create a separate user for each RFC context. Ensure that the user typeis set to Dialog so that users can perform the transactions interactively.Create and assign a user profile that covers the required tasks.

2. Create a separate RFC destination for each context with its own user forbranching into the application log of the corresponding SCM system.

Hint: You go to transaction code SM59 in SAP R/3 and setup anRFC destination called APOCLNTALOG which is to be usedfor branching into the application log only of the SCM systemAPOCLNT800.

3. Assign the RFC Destination to the corresponding logical system and �CIFApplication� using transaction CFC7 (or SM30, view, V_CIFRFCDS).



Defining Flexible RFC Destinations

1. Transaction code: SPRO

2. Follow menu path: Integration with other my SAP.com Components →Advanced Planning and Optimization → Basic Settings for Setting Up theSystem Landscape→ Assign RFC Destinations to Different Application Cases.

3. Review settings for the different applications.

Data Channels and Queues in SAP R/3 integrationOnce the RFC destinations have been established, we must define what therelease is of the receiving SCM system. In your SAP R/3 system, you will haveto identify the logical system name that represents your SAP SCM system,and identify at what release level it is operating.

Figure 9: Determine Target System and Maintain APO Release

As the system performs the integration in various ways for different SAPAPO/SCM releases, you must also enter the release of the APO target system.(Transaction APO Releases in the CIF settings). As SCM continues to evolvethis has an impact on how data is technically transferred to SAP SCM.



Once you have established the release level of your receiving system, we mustidentify the logical systems are available for the users to send the data fromSAP R/3 to the correct SAP SCM system. With this configuration activity youwill add all the logical system names with which your SAP R/3 system willbe integrating. The CIF uses a data transfer process called QRFC (queuedremote function call). This means that the data is stored temporarily in queuesAdditionally qRFCs may be grouped in LUWs.

LUWLogical unit of work (LUW) in which multiple queued remote functioncalls (qRFC) are collected for a data transfer using the Core Interface(CIF). The sequence of qRFCs within an LUW is determined in the sourcesystem and retained during posting to the target system. Changes to datathat are made using the qRFCs in an LUW are only posted if all qRFCs inthe LUW can be processed successfully.

The queue type (inbout or outbound) determines whether the queuesprocessing is controlled by the sending system or recieving system. Inaddition to this step you will identify the transfer mode type. In actuality thetransfer mode type is set by internal parameters.

Figure 10: Outbound and Inbound Queues

During integration of SAP SCM and SAP R/3, mass transactions such asplanning data in SAP SCM, where a large amount of data to be transferredis created, can cause considerable system loads in the receiving system. This



is caused by the missing workload distribution of the qRFC processing inthe target system. If inbound queues are used, the system load on the targetsystem is taken into account. If you are expecting high amounts of integrationdata and insufficient work process resources in the target system, it may beuseful to switch to inbound queues. The conversion from outbound (standard)to inbound queues takes place in the SAP R/3 when determining the APOtarget systems (transaction code CFC1) and in SAP SCM when assigning thelogical systems to a business system group (APO Customizing).

Figure 11: Data Transfer QueuesFigure 11: Data Transfer Queues

When you enter a logical target system in transaction CFC1, the systemautomatically suggests the type Outbound Queue. This setting means that thequeue processing is controlled by the sending system (SAP R/3). This maylead to problems if the receiving system (SAP SCM) does not currently haveenough free work processes to process the queue.

Hint: If you are processing large amounts of integration data and it isbelieved you have insufficient work process resources, it may be usefulto change this setting to Inbound Queues. This means that the queueprocessing is controlled by the receiving system (SAP SCM). IF thereare not enough work processes available here the data is saved whenentering SAP SCM and then processed at a later point in time.



Business System Groups

Figure 12: Business System Group (1)

An SAP SCM System can be integrated with several SAP R/3 Systems (logicalsystems). It may, therefore, be the case that the number assignment for certainmaster data objects, for example, material masters, is not the same in all theselogical systems. In the example above, material number A in logical systems1 and 2 signifies the same hammer, whereas the same material number inlogical system 3 (perhaps a subsequently purchased plant) is a screw. Iflogical systems 1, 2 and 3 are planned with the same SAP SCM System, theproblem arises that the system cannot simply transfer the SAP R/3 materialnumbers into SAP SCM, as they may be ambiguous. The fact that the samematerial may have different material numbers in different logical systems, isnot discussed on this or the following pages. If this does occur, you can use acustomer exit in SAP SCM inbound processing where you map the relevantmaterial numbers from the different logical systems onto the unique materialnumber in SAP SCM.




To guarantee that the naming of master data in distributed system landscapesis unique, business system groups are defined in SAP SCM as areas of thesame naming convention. A Business System Group (BSG) groups differentphysical systems to form a higher-level logical unit. If, for example, twological systems (LS1 and LS3) exist in a system landscape in which SAP SCMis integrated, and contain different materials with the same name (MaterialA is a hammer in LS1, but a screw in LS2), this conflict must be resolved forintegration in SAP SCM. First of all, both logical systems are to be assigned todifferent business system groups (BSG1 and BSG2). The logical systems wereeach assigned to one business system group. The SAP SCM System, as anindependent logical system, must also be assigned to a business system group.Each source system (SAP R/3 ) is assigned to a BSG. One BSG can consist of oneor several source systems but must contain at least one SAP R/3 source system.




If the situation arises that two different logical systems with identical numberranges are operating when a distributed system landscape is constructedwith SAP SCM, the identical names must be changed with a customer exit.The following enhancements are available as customer exits (transactionsSMOD and CMOD) for the inbound processing in the SAP SCM System (thelist is not complete):

APOCF001 EXIT_/SAPAPO/SAPLCIF_LOC_001: Location

APOCF002 EXIT_/SAPAPO/SAPLCIF_ATP_001: Maintain ATP check control

APOCF003 EXIT_/SAPAPO/SAPLCIF_IRQ_001: Reduction of planned indep.req.

APOCF004 EXIT_/SAPAPO/SAPLCIF_ORD_001: Production and plannedorders

APOCF005 EXIT_/SAPAPO/SAPLCIF_PROD_001: Products

APOCF006 EXIT_/SAPAPO/SAPLCIF_PU_001: Purchase order documents

EXIT_SAPL_1004_001: Resource

APOCF010 EXIT_/SAPAPO/SAPLCIF_SLS_001: Sales order



APOCF011 EXIT_/SAPAPO/SAPLCIF_STOCK_001: Stock For furthercustomer exits: see the online help.

Hint: As of SCM 4.0 all customer exits are located in the IMG.Menu Path: Integration with other my SAP.com Components →Advanced Planning and Optimization→ Application-Specific Settings andEnhancements → .........


If the situation arises that two different logical systems with identicalnumber ranges are operating when a distributed system landscape is beingconstructed, a unique mapping structure must be constructed. Firstly, youmust define the business system groups in APO Customizing step MaintainBusiness System Group (under Basis Settings in APO). In the next step(Customizing step Assign Logical System and Queue Type) you assign thediverse logical systems of your system landscape to a BSG. You shouldbe aware that within a system group, the same naming convention mustapply, i.e. the different master data objects must have unique names withinthe group. The last step mainly consists of the master data objects fromthe different BSGs being copied with unique names into SAP SCM usinga customer exit. These customer exits exist for all master data. You mustmaintain a BSG, even when only one SAP R/3 is linked with one SAP SCMSystem, or when several SAP R/3 Systems are connected without the risk of



ambiguities. You will only need more than one BSG when there is no uniquenaming convention. The SAP SCM System should preferably be assigned tothe BSG, where its data must not be renamed.



Business System Groups

1. Transaction code SPRO

2. Advanced Planning and Optimization → Basis Settings → Integration →Business system group → Maintain business system group

3. Review current business groups

4. Advanced Planning and Optimization → Basis Settings → Integration →Business system group→ Assign Logical System and Queue Type





Exercise 1: Architecture of Integration

Exercise ObjectivesAfter completing this exercise, you will be able to:� Review the technical settings of the RFC connection between the SAP R/3

System and an SAP SCM System.

Business ExampleAs your company implements SAP SCM , the integration needs to be set upbetween the two systems. This integration uses an RFC connection and thesesettings must be maintained to set up the integration.

Task:The link between an SAP R/3 System and the SAP SCM System is based on anRFC connection that connects two logical systems.

1. Which SAP R/3 client are you working in?

2. Which logical system name is assigned to your SAP R/3 client? Look inyour SAP R/3 system

3. Which SAP SCM client are you working in?

Continued on next page



4. Which logical system is assigned to your SAP SCM client?

5. In the SAP R/3 System, display the RFC connection to the SAP SCMSystem. Which user name is used for logon to the SAP SCM System?

6. In the SAP SCM System, display the RFC connection to the SAP R/3System. Which user name is used for logon to the SAP R/3 System?



Solution 1: Architecture of IntegrationTask:The link between an SAP R/3 System and the SAP SCM System is based on anRFC connection that connects two logical systems.

1. Which SAP R/3 client are you working in?

Answer: Varies, for example, 8##

2. Which logical system name is assigned to your SAP R/3 client? Look inyour SAP R/3 system

Answer: Varies, but should use the format T90CLNT090. Use thefollowing menu paths to check the system name assigned: Tools →Customizing→ IMG → Edit Project , Choose SAP Reference IMG, thenIntegration with Other mySAP.com Components → Advanced Planning andOptimization→ Basic Settings for Setting up the System Landscape→ AssignLogical System to a Client.

3. Which SAP SCM client are you working in?

Answer: Varies, should be the same as the SAP R/3 client, for example,8##.

4. Which logical system is assigned to your SAP SCM client?

Answer: Varies, but should use the format APOCLNT8##. Use thefollowing menu paths to check the system name assigned: Tools →Customizing→ IMG→ Edit Project , choose SAP Reference IMG, and thenSAP Web Application Server→ Application Link Enabling (ALE)→ Sendingand Receiving Systems→ Logical Systems→ Assign Client to Logical System.

5. In the SAP R/3 System, display the RFC connection to the SAP SCMSystem. Which user name is used for logon to the SAP SCM System?

Answer: USERADMIN.Use the following menu paths to check the user name: Tools →Administration→ Administration→ Network→ RFC Destinations (SAP R/3Connections), and then Locate the logical system name of the SAP R/3 Systemand double click to display the details..




6. In the SAP SCM System, display the RFC connection to the SAP R/3System. Which user name is used for logon to the SAP R/3 System?

Answer: USERADMIN.Use the following menu paths to check the user name:Tools→ Customizing→ IMG→ Edit Project , Choose SAP Reference IMG, then Integration withOther mySAP.com Components → Advanced Planning and Optimization→Basic Settings for Setting up the System Landscape→ Set Up RFC Destination,and then Locate the logical system name of the SAP R/3 System and doubleclick to display the details..



Lesson Summary

You should now be able to:� Explain the basic steps to integrate an SAP R/3 and an SAP SCM System� Demonstrate the need or use of RFC connections between SAP R/3 and



with one or more OLTP systems.�



Lesson: Generating and Activating Integration Models

Lesson OverviewAfter the RFC connection is set up between the SAP R/3 System and the SAPSCM System, an integration model controls the data objects that integrate.


� Create integration models for transfer of transactional data using SAPrecommended selection methods.

� Activate integration models for transfer of transactional data.

Business ExamplePlanning elements must be transferred from the SAP R/3 system to theSAP SCM system to derive a proper production plan. Upon completinga production plan, the results must be transferred back to the SAP R/3system to perform additional planning via MRP, or actual manufacturingor procurement activities. Now that you have reviewed the necessaryconfiguration to start the integration of transactional data between and SAPSCM system and an SAP R/3 system, you need to trigger the actual transfer ofthat data. In order to accomplish the bi-directional flow of transactional datayou will setup and activate an integration model for the necessary objects.

Integration Models: Creating and ActivatingThe data transfer between the SAP R/3 and SAP SCM systems is defined andcontrolled using the Core Interface (CIF). The CIF is the central interface forconnecting SAP SCM to the existing SAP R/3 system environment. An RFCconnection with the SAP R/3 System is a technical requirement for successfuldata transfer to SAP SCM using the Core Interface. The CIF interface is anadd-on to the SAP R/3 System that you install using the relevant plug-in. Theexact installation process is dependent, amongst other things, on the SAP R/3release you are working with. You can find current detailed information onplug-ins in SAPNet, under the alias /R3-plug-in. The selection of master datathat the system transfers to SAP SCM is determined in an integration modelthat you define in the SAP R/3 System.


SCM210 Lesson: Generating and Activating Integration Models

Figure 16: Master Data Interface: Core Interface (CIF)

The Core Interface is a real-time interface. Only the data objects needed in thedata structures reconciled in planning in SAP SCM for the particular planningand optimization processes are transferred from the complex data set in SAPR/3 to SAP SCM. Both the initial data transfer (initial transfer) and the transferof data changes to SAP SCM are made through the Core Interface. The masterdata objects in SAP SCM are not identical to those in SAP R/3. During masterdata transfer, the relevant SAP R/3 master data is usually mapped ontocorresponding SAP SCM planning master data. The SAP R/3 system is alwaysthe dominant system for master data. Only specific SAP SCMmaster data thatdoes not exist in SAP R/3 is maintained directly in SAP SCM .



Figure 17: Master Data Objects of the CIF

You define the integration model that controls the transfer of master andtransaction data in the SAP R/3 System. You can find the menu option CoreInterface Advanced Planner and Optimizer (the CIF menu) under Logistics→Central Functions → Supply Chain Planning Interface. The integration modeldistinguishes between each data object. SAP recommends that you organizeyour integration models according to the list published in the CIF: Tips andTricks document. In the integration model, you select the data set that youwant to transfer. You specify the following in the integration model. TheSAP SCM target system for the data transfer - The data objects you want totransfer. You can delete integration models that you no longer need. Note thatyou must first deactivate these integration models.



Figure 18: Initial Data Transfer of Master Data: Overview

The master data that the system will transfer for the first time (initialtransfer), from the SAP R/3 System into the SAP SCM System, is defined in anintegration model. This integration model is generated in the SAP R/3 Systemusing transaction CFM1. An integration model is uniquely defined by itsname and application. It is useful to create several integration models withthe same name but as different applications. This will help ensure that thedata pools of your integration models are generally not too big. This enablesyou to handle errors more easily. The target system that you specify in theintegration model determines the SAP SCM System that the master data istransferred into. The target system is a logical ( SAP SCM) system that musthave an RFC connection. Finally, you use a particular integration model tospecify which master data you want the system to transfer. To do so, you firstspecify the master data types that flow into the integration model. In thesecond step, you specify the selection criteria to be used for the selection of theindividual master data documents in the SAP R/3 System. You complete thegeneration of the integration model by "executing" the model (this means thatthe data objects of the model are compiled) and then you save it.



Figure 19: Generate Integration Model for Initial Data TransferFigure 19: Generate Integration Model for Initial Data Transfer

To transfer data into SAP SCM, you must activate an integration model thathas previously been generated. You activate an integration model with theActivate Integration Model transaction (transaction code CFM2) in the CIF. Itis useful to have several integration models active at a time. Choose the Startfunction to trigger the initial data transfer into SAP SCM: The master data,or the equivalent of the SAP SCM master data in SAP SCM, exists in the SAPSCM System. Basically, only the master data that was not available in anyother active integration model is transferred (delta comparison). To be ableto carry out the delta matching that was executed during activation of anintegration model quickly, the system refers to the runtime version of theintegration models. The runtime version is formed in the background fromall active integration models, each with one object type and target system,formatted optimally and saved to the database. It is automatically updatedduring the activation of new models. You can access the runtime versionmanually from report RCIFIMAX. The initial data transfer usually runs in aparticular order: the objects are selected successively, transferred to SAP SCMand processed there in this sequence. For improved system performance, itis also possible to execute a parallel initial data transfer: several integrationmodels can be activated at the same time. You can set during parallel



processing whether to run the selection in SAP R/3, processing in SAP SCM orboth at the same time. Parallel processing takes place within an object type,whereas the different object types are still transferred in sequence.

Figure 20: Selection Criteria for MRP Type X0

Planning is not necessarily executed for all materials in SAP SCM. Planning forcritical materials can take place in SAP SCM, while less critical materials (suchas consumption-controlled purchasing materials) are planned exclusively inSAP R/3. Materials planned in SAP SCM should not be planned again in SAPR/3 - the planning result from SAP SCM is transferred directly in the formof planned or production orders to SAP R/3. However, for materials with aBOM, You should assign these materials a special MRP type with the MRPprocedure "X" ("without MRP, with BOM explosion"). This will ensure thatdependent requirements will be created in the SAP R/3 system for non-SAPSCM-relevant components. (This MRP procedure is available as of 4.0; if youwork with earlier releases, use MRP type "P4" with a planning time fenceof 999 days). It is also possible to use the MRP type X0 to select materialsrelevant for SAP SCM in the integration model. If you give materials that areto be planned in SAP SCM a special plant-specific material status, you canuse the material status to limit the selection further. In general, you shouldbe careful about separating SAP SCM-relevant materials from those that arenot SAP SCM-relevant: For effective planning in SAP SCM, you must be surethat all materials important for the planning process are actually planned



in SAP SCM. (Take capacity planning as an example: If the capacities areto be planned for the different resources in SAP SCM, all materials that areproduced on these resources must be planned in SAP SCM.)

Figure 21: Activate Integration Model for Initial Data Transfer



Exercise 2: Transfer of Master Data

Exercise ObjectivesAfter completing this exercise, you will be able to:� Prepare SAP R/3 material masters for planning in SAP SCM� Create an integration model for the initial data transfer and execute the

transfer

Business ExamplePrecision Petrol Pump company constitutes a number of independent businessunits located in different parts of the world. Each unit is headed by a businessunit head and operates as an independent entity under the parent company.As part of a move to centralize planning functions in SAP SCM, you musttransfers data from you SAP R/3 system to the SAP SCM system.

to initiate this transfer you will create an integration model that will select therelevant master data for integration to SAP SCM and activate this model.



Task 1: Review the Configuration of MRP Type X0To expedite the transfer of master data you wish to select the SAP SCMrelevant master data by filtering off of several field settings in the variousmaster data objects. When transferring the Material Master your plannerswill use the MRP type X0 to select SAP R/3 materials masters that need tobe transferred to SAP SCM.

1. Which MRP procedure is defined in the MRP type X0?

2. What effect does this MRP procedure have?

3. Which planning method is entered in this MRP Type?

Task 2: Manage SAP SCM relevant Master DataIn order to transfer your master data to SAP SCM as easily as possible we willset the material master up so that many different materials could possiblyselect at one time during the generation of the integration model

1. Change the material master T-F1## in plant 1000, so that the MRP Type isset to X0, and the MRP controller is set to 0##.




Task 3: Create an Integration Model to Transfer Materialsto SAP SCMCreate an integration model to transfer Material Master records from SAPR/3 to SAP SCM.

1. Create and generate an integration model for master data using plant1000, MRP Ctrlr 0##, and MRP Type X0. Use the data in the followingtable to identify your integrations model. After generating the model donot leave the transaction!

Field Data

Model Name PUMP##

Logical system APOCLNT8XX

APO Application MAT T-F1##

2. Save your settings as the variantMat. ## with the description T-F1##.

Task 4: Transfer Material to SAP SCMActivate your integration model to begin the initial data transfer and setupthe incremental data transfer.

1. Activate your integration model PUMP##.




Task 5: Review Transfer ResultsCheck the results of the master data transfer in the SAP SCM System.

1. What is the description of the product T-F1##?

2. Which user created this product master record?

3. Where does this user come from?



Solution 2: Transfer of Master DataTask 1: Review the Configuration of MRP Type X0To expedite the transfer of master data you wish to select the SAP SCMrelevant master data by filtering off of several field settings in the variousmaster data objects. When transferring the Material Master your plannerswill use the MRP type X0 to select SAP R/3 materials masters that need tobe transferred to SAP SCM.


Answer: MRP Type X0 has MRP procedure X, Without MRP, with BOMexplosion assigned to it.Display the configuration of the MRP type X0 by first going to the IMG ofthe SAP R/3 System using the menu path Tools → Customizing → IMG

→ Edit Project. Once in the IMG click the buttonon the tool bar to access the SAP Reference IMG. In the SAP ReferenceIMG use the menu path Production→Material Requirements Planning→Master Data → Check MRP Types.

Select the MRP Type X0 and click the button on the tool bar or simplydouble click on MRP Type X0.


Answer: This MRP procedure means that the corresponding materialswill not be planned in the SAP R/3 System during any MRP/MPSplanning runs. Note this setting is only relevant if you have items on theBOM that are still planned in SAP R/3. If a BOM change takes place toan SAP R/3 relevant item on the BOM, existing planned orders must beadjust to reflect the BOM changes. During the next SAP R/3 planningrun all existing planned orders will have the BOM re-exploded so thatthe SAP R/3 relevant changes can be consider and planned. No headerinformation on the planned order will change since this will be controlledby the orders in SAP SCM. If all items on the BOM are SAP SCM relevant,consider using MRP type ND (No Planning).


Answer: The Planning method assigned to MRP Type X0 is 1, Plannedby external system. Check the Additional selection parameters section tofind this information.






a) Menu path in the SAP R/3 Enterprise: Logistics → Production→ Master Data → Material Master → Material → Change →Immediately. (MM02)

b) Enter Material number T-F1##, and pressENTER.c) SelectMRP 1 view, and press ENTER.d) Enter Plant 1000, and press ENTER.e) Change the MRP type toX0, and the MRP Controller to 0##f) Select SAVE






Field Data

Model Name PUMP##



a) From the SAP R/3 main menu choose Logistics→ Central Functions→ Supply Chain Planning Interface→ Core Interface Advanced Planningand Optimizer→ Integration Model→ Generate→ Create

b) Enter the data in the above table in the header fields.c) Select theMaterials indicator on the left side of the screen.d) Enter the selection criteria in the table below, on the right side in the

general selections for materials section. Leave all other fields blank.

Field Data

Plnt 1000

MRP Ctrlr 0##

MRP Type X0

e) Execute .f) On the next screen click the button. You can check which

materials were selected by double clicking on the Materials line.

Note: Only when the message �Integration model PUMP##generated for target system APOCLNT8XX and applicationMAT T-F1## � appears have you successfully generatedand integration model:

g) Select Continueh) Select Back once.


a) Select Save.b) Enter the variant nameMat.## with the description T-F1##c) Select Save.






a) From the SAP R/3 menu, Logistics → Central Functions → SupplyChain Planning Interface → Core Interface Advanced Planning andOptimizer → Integration Model→ Activate

Your integration model information should default into the fieldssince that was the last one you used. If it doesn�t make sure thatthe fields are correct with the information from the previous stepand execute.

Double click on the date/time line or click it and click the

button on the tool bar. A green check shouldappear in front of it. To begin the initial data transfer, click the

button on the tool bar.



Answer: Pump PRECISION 100. Using SAP Menu→ Advance Planningand Optimization → Master Data → Product enter your product T-F1##,

plant 3100, select the location radio button, and click thebutton.


Answer: USERADMIN as found on the Administration tab.


Answer: The user USERADMIN is used by SAP R/3 to log on to the SAPSCM system during the CIF transfer of data. This user can be foundin the RFC destination and indicates this product master record wastransferred from SAP R/3 via the CIF.



Lesson Summary

You should now be able to:� Create integration models for transfer of transactional data using SAP

recommended selection methods.� Activate integration models for transfer of transactional data.



Lesson: Monitoring and Error handling tools for integratingSAP R/3 and SAP SCM.

Lesson OverviewUpon implementing SAP SCM, your organization has committed to transferlarge amounts of data between the SAP R/3 and SAP SCM data bases. Due tothe large volume of data that will pass between the systems, often times errorsor inconsistencies will occur. In order to correct these errors or inconsistencies,you will become familiar with the SCM queue manager, and various deltareports that can identify and correct inconsistencies in the data.


� Describe the data transfer process, and how errors are recorded� Demonstrate the qRFC Monitor and explain its purpose in handling

transfer errors� Demonstrate the Application Log and explain its purpose n handling

transfer errors� Demonstrate the SCM Queue Manager and explain its purpose in

handling transfer errors� Demonstrate the qRFC Alert and explain its purpose in handling transfer

errors� Explain the differences between the Post Processing and the previously

mentioned tools.� Demonstrate the Compare/Reconcile functionality and explain its

purpose in handling transfer errors

Business ExampleAssume your company is using SAP R/3 and SAP SCM, the integrationthrough the CIF needs monitoring to ensure the two systems stay in sync. Youneed to use the available tools to resolve any possible problems and ensuredata consistency and accuracy across systems.


SCM210 Lesson: Monitoring and Error handling tools for integrating SAP R/3 and SAP SCM.

Monitoring and Error HandlingAs data is transfer between the two systems, it is grouped into qRFC-LUWs(Logical Units of Work). The data within each LUW is only processed inthe receiving system if all data within that LUW can be sent successfully.If one or more LUW entries cannot be transferred, a queue entry with thestatus SYSFAIL is created for the entire LUW. This can quickly lead to whatis referred to as the �serialization :�affect. Serialization may take one of thefollowing forms

� One queue error might block a large number of subsequent queues� Random blocks of unrelated business data� A single error might cause immense inconsistencies between the systems.

Example: An error on a sales order might cause PP data not to berecorded in a timely fashion.

In this situation, the first LUW that fails, causes any other LUWs for the samedata channel to queue up and have a status WAITING.

Figure 22: Integration Monitoring



The Core Interface offers several basic monitoring functions to monitor thedata transfer from SAP R/3 to SAP SCM as well as from SAP SCM to SAP R/3:the qRFC monitor to display incorrect queue entries and the application log.

Note: As of SCM 4.0 companies can initiate a new �CIF errorhandling�process. It does not work in all applications, but the detailswill be explained later.

In addition, the qRFC alert monitor is used to monitor the queues in SAPSCM and SAP R/3 that are relevant to SCM-R/3 integration. If queue blocksare detected, an automatic message can be sent to a predefined destination.Instead of evaluating the analyses in both systems (SAP R/3 and SAP SCM) separately when errors occur, the user can use the central SCM QueueManager available in SAP SCM to monitor the queues and application logs inboth systems. Whereas the transactions qRFC monitor and qRFC alert are tobe carried out separately for outbound and inbound queues, both queue typescan be monitored at the same time in the SCM Queue Manager.

The communication between SAP R/3 and SAP SCM is based on theasynchronous transfer technology of the queued Remote Function Call (qRFC).A Remote Function Call (RFC) is calling a function module in a differentsystem. This technology is used in the integration between SAP SCM and SAPR/3 both for the initial data supply and transfer of data changes (from SAPR/3 to SAP SCM) as well as for the publication of planning results (from SAPSCM to SAP R/3). The data is first buffered by the sending system and thentransferred to the target system (outbound queues, inbound queues are alsopossible). The big advantage of this is that the application that triggered thedata transfer does not have to wait until the update has been completed in thetarget system. However, this means that return parameters cannot be passedon and potential error messages cannot be directly returned to the application.

Two types of errors are distinguished for the processing of qRFC calls:

1. Communication errors: This includes network problems, a non-existingRFC destination, and so on. Since the data transfer is repeated aftercertain periods, most of these communication errors should disappearonce the network connection is available again.

2. Application error: This includes program errors, non-posting of datain the target system, missing master data at a transaction date, etc.Application errors cannot be solved by the system independently andmust be processed by the system administrator.



The central instance for monitoring application errors is the SCM QueueManager, a central tool containing information about the SAP R/3 and SAPSCM qRFC monitors. The qRFC monitors are available in SAP R/3 andSAP SCM for outbound or inbound queues. All transfer fields (queues) aredisplayed for the target system, they can be activated or deleted.

qRFC Monitor for Error Processing

Figure 23: Using the qRFC Monitor

In the initial data transfer, transfer fields are recognized and displayed at thetime of the integration model activation. Repeat and Ignore functions areavailable in the dialog box. If you choose Repeat, the system attempts to startinitial data transfer again (for example, if there was only a temporary problemin system communication). The Ignore button can be used if the activation hasfailed due to an existing transaction data queue. As failed transaction datatransfers do not necessarily affect a master data transfer, the initial transfercan ignore this entry. This function cannot be used for previous failed initialdata transfers. In this case, the problem must be analyzed with the qRFCmonitor. During online transfer (for example, stock postings in SAP R/3 ),transfer fields are not displayed online for the runtime (asynchronous transfertechnology). This means that you do not have to check in the qRFC monitorduring non-transfers of data between SAP SCM and SAP R/3 whether entriesmarked in red are displayed. This check can be carried out automatically



by qRFC alert. There is a qRFC monitor in both SAP R/3 and SAP SCM.In the qRFC monitor, by double-clicking on the affected lines, all functioncalls for the selected transfer queue are displayed. The top function moduleblocks all following entries in the case of an error. You can display the currentstatus text from the error short text. A detailed error message is stored in theapplication log of the target system. In the example above, the user from theRFC destination is either locked in SAP SCM or does not exist.

Figure 24: Queue Channels for Data Transfer: Examples

In the example above, the PPM could not be transferred for material C becausethe material itself was not transferred. The queue for the next initial transfersof master data is therefore blocked. However, online transfers for transactiondata can still be carried out, provided that an active integration model existsfor the master or transaction data in question. There are various queuechannels available in the interface:

CF_ADC_LOAD - Initial data transfer

CFSTK* - Stocks,

CFPO* - Purchase Orders and Purchase Requisitions

CFPLO* - Planned Orders/Production Orders

CFSLS* - Sales Orders

CFRSV* - Manual Reservations



CFCNF - Confirmations

CFPIR* - Planned Independent Requirements

CFMAT* - Planned Independent Requirements Reduction

CFPCM* - Production Campaigns

CFCLA* - Master Data for Classes

CFCHR* - Master Data for Characteristics

CFSHP* - Shipments

CFCUVT* - Planning Tables(* stands for the number of the purchase order, sales order etc.)

Note: The status of these queues can be view via transaction CFP2

If only temporary communication errors occur in the network connection, thefailed transfers (entry in the qRFC monitor) can be started again (by choosingActivate queue in the qRFC monitor). If you only want to re-start an objecttype (for example, locations) within a queue, you can choose the Execute LUWfunction to repeat the transfer of locations. If there are communication errorsand you want to execute the new activation of the queue automatically, youcanmake a setting in the RFC destination (transaction SM59) so that the systemattempts in defined time intervals to transfer the data (in the RFC destinationunder TRFC Options; default setting - 30 attempts every 15 minutes).



Monitoring transfer errors with the qRFC monitor

1. SAP R/3 Menu Path: Logistics → Central Functions → Supply ChainPlanning Interface → Core Interface Advanced Planner and Optimizer →Monitoring → qRFC Monitor

2. There you will see the Queues that are blocked

3. Select the queue that is related to your material (T-F2##) and selectDisplay Selections

4. Here you will see the LUW that has been formed with the transactionsthat have failed. Note the status SYSFAIL

5. Select the LUW and select Choose

Application Log for Error ProcessingYou can use the application log to trace when (time), and what (data objectsand integration model) was transferred by whom (user). In addition, theapplication log provides a detailed error message if an application erroroccurred. As a prerequisite, logging must have been switched on. The settingof the logging mode takes place in SAP R/3 or SAP SCM (transaction CFC2 inSAP R/3 and /SAPAPO/C4 in SAP SCM). The following settings are possible:

� Standard (only the headers of the data records are logged) �� Detailed (header and contents of the transferred data records are logged).�

The detailed logging can quickly lead to large data quantities and thereforeperformance problems in the production operation. For this reason, werecommend using detailed logging only when the detailed data is actuallyneeded, for example, in the implementation phase. The system does not deletethe logs automatically. To prevent extreme database load, we recommenddeleting the logs periodically (also possible in background processing). Ifyou do not make an entry in the date and time fields, all logs older than twoweeks are deleted.



Figure 25: Using the Application Log

In the example above, an initial data supply was carried out in SAP R/3 totransfer several different master data, including, for example, purchasing inforecords. One of the purchasing info records transferred was for a vendorthat does not exist in SAP SCM. This purchasing info record could thereforenot be transferred. You can select different subobjects for the CIF object inthe SAP R/3 and SAP SCM application log. These include, for example, EPExternal procurement, IP In-house production, or INITIAL Initial supplyand LOCATION Location: customer, plant, vendor (the entries for an initialsupply and an transfer of data changes are grouped under the subobjectINITIAL). The transaction ID of the sending application serves as the keyof an error message (TID field in the qRFC line of the qRFC monitor of thesending system). When you enter this number, you can display all messagesfor this qRFC call in the target system. In the application log, you enterthe number of the transaction ID in the External ID. field and execute theselection. The system displays all messages for the call in question. WithSAP R/3 transaction CFC6, you can set the interface parameters that are tobe executed in the application log.

In the example above, a planned order for a finished product and purchaserequisitions for the components of the finished product have been created inSAP SCM. However, these were not included in any active integration modelat the time of order creation. Therefore, the orders were not transferred to



SAP R/3 but kept in the queue. In the outbound log, you always recognize thelog of successful transfers. In the logging of the target system, error messagesare displayed if errors occurred during transfers.



Application Log for Error Processing

1. SAP R/3 Menu Path: Logistics → Central Functions → Supply ChainPlanning Interface → Core Interface Advanced Planner and Optimizer →Monitoring → qRFC Monitor

2. SAP SCM Menu Path: Advanced Planning and Optimization→ APOAdministration → Integration → Monitor → qRFC Monitor (OutboundQueues)

3. Find the most recent entry and double click on each entry and review thedetails of the transfer in the bottom section of the report.

SCM Queue Manager for Error Processing in SAP SCMThe SCM Queue Manager is a tool that is only accessible via SAP SCM. Thistool will allow an administrator to monitor all integration traffic, wether it beoutgoing data to SAP R/3, or an incoming availability check from an SAPCRM system.

Figure 26: SCM Queue Manager Selection

Instead of evaluating the application logs in both systems (SAP R/3 and SAPSCM) separately when errors occur, the user can use the central SCM QueueManager available in SAP[ SCM to monitor the queues and application logs in



both systems. With the SCM Queue Manager, you can monitor both outboundand inbound queues. To monitor the inbound queues, set the correspondingswitch when you enter the transaction.

Figure 27: Using the SCM Queue Manager

In the SCM Queue Manager, transfer failures are indicated by redthunderbolts, whereas correct transfer channels have a green check mark. Inthis way, you can immediately recognize whether incorrect transfers exist.Any errors can be analyzed directly in the SCM Queue Manager and solved



Monitoring transfer errors with the SCM Queue Manager

1. SCM menu path: Advanced planning and optimization → APOAdministration→ Integration→Monitor→ SCM Queue Manager

2. Select Expand node and deselect Only Show Blocked Queues andexecute

3. Review the data queues and you will see the STOCKS queue is blocked

4. Double click on the blocked queue

5. Select the first entry with your material number T-F2## and selectDisplay Queue

qRFC Alert for Error Processing in SAP SCMThe qRFC alert monitors all SAP SCM queues and the queues of the connectedlogical SAP R/3 systems. If there are queue errors or blocks, a message isgenerated from the status information and can be sent via SAP Office. Allincorrect outbound queues are issued as a list.

Figure 28: qRFC Alert for Automatic Notification



Automatic notification can take place at:

� The initiator of the block through SAP Office Inbox Mail (the initiatorof every queue block receives a message informing him or her that heor she has caused a block)

� The administrator, through an SAP Office Inbox or by Internet mail (oneperson is chosen to receive all messages).

If you want to send the messages to an e-mail address, you must have madethe necessary settings in SAPconnect. With the settings for Local Queues, youcan determine whether a notification is to take place if no queue appears inSAP SCM. In the Remote Queues group, the settings for monitoring queues ofthe connected SAP R/3 systems are defined.



Managing transfer errors with the qRFC Alert

1. SAP SCM Menu path Advanced Planning and Optimization → APOAdministration→ Integration→Monitor→ qRFC Alert (Outbound Queues)

2. In the notification section select To Administrator and put your logonSCM210-##.

3. Select Execute. This will bring up an overview screen identifyingwhat queues are block.

4. Exit the report and an email notification will pop up.

5. Select the mail and select Choose

CIF Error Handling (new SCM 4.0)In earlier releases, qRFC errors could be a common problem, and this couldlead to delays in recording critical information in either of the systems(serialization problems). As of SCM 4.0, companies can use new functionalitycalled Post Processing. This new functionality will allow companies to skipthe failed LUW and create a post processing record in order to allow otherLUWs to be recorded.

Figure 29: CIF Error Handling

As a result of using post processing records the errors will disappear fromthe qRFC monitor and the qRFC alert. They will no longer be visible fromtransactions SMQ1 and SMQ2.

The post processing functionality currently has some restrictions, andtherefore, will not work with all data transfers. As a result of this limitation,companies must activate the functionality in the IMG.



Figure 30: Configuring Post Processing

In SCM 4.0 post processing has the following restriction and therefore doesnot apply in the following situations:

� during initial loads� master data loads� BAPI integration� in the case of ABAP dumps or when LiveCache is not available� If an object is locked in the target system, the entire LUW is flagged as a

SYSFAIL, and will need to be monitored via the normal methods.� industry specific solutions (e.g. DI backflush)� TP/VS: changes from SAP SCM �> SAP R/3� Descriptive Characteristics: transfer from SAP R/3 �> SAP SCM, post

processing is deactivated automatically� Quota Arrangements: after transfer of errors with order-releated

goods movements have occurred, the quota-allocated quantities of thecorresponding sources of supply are not updated in SAP SCM.

� Planned independent requirements transfer between SAP SCM and SAPR/3.

Note: For more detailed information see note 602484

If errors occur during the transfer from SAP R/3 to SAP SCM, CIF errorhandling ensures that serialization is avoided. If errors continue to occur inthe target system when the data is re-transferred from SAP R/3 to SAP SCM,



serialization is again avoided. For new transfers, the sequence of RFCs (thatis, the block formation) must be the same as in the qRFC LUW of the originaltransfer. This requirement leads to the following system behavior:

� You send an object for which a postprocessing record already exists toSAP SAP SCM, but not from CIF postprocessing.

� If the transfer proceeds without errors, the object is posted tothe target system. The postprocessing record that already existscontinues to exist and its processing status does not change

� If an error occurs in the transfer, a new postprocessing record isgenerated. The postprocessing record that already exists continuesto exist and its processing status does not change.

� You retransfer an object for which a postprocessing record already existsto SAP SAP SCM from CIF postprocessing.

� If the transfer proceeds without errors, the object is posted in thetarget system and the existing postprocessing record receives thestatus Processed.

� If an error occurs again during the transfer, a new postprocessingrecord is generated. The postprocessing record that already existsreceives the status Processed.

When re-transfers occur from SAP SCM to SAP R/3, in this case, blockformation can occur arbitrarily. This leads to the following system behavior:

� You send an object for which a postprocessing record already exists toSAP R/3, but not from CIF postprocessing.

� If the transfer proceeds without errors, the object is posted in thetarget system and the existing postprocessing record receives thestatus Obsolete (automatically set by system).

� If an error occurs in the transfer, a new postprocessing record isgenerated. The postprocessing record that already exists receivesthe status Obsolete (automatically set by system).

� You retransfer an object for which a postprocessing record already existsto SAP R/3 from CIF postprocessing.

� If the transfer proceeds without errors, the object is posted in thetarget system and the existing postprocessing record receives thestatus Processed.

� If an error occurs in the transfer, a new postprocessing record isgenerated. The postprocessing record that already exists receivesthe status Processed.



To support the new post processing functionality SAP has delivered five newtransactions:

� /SAPAPO/CPP - CIF Post Processing (individual records)� /SAPAPO/CPP1 - CIF Post processing (multiple records)� /SAPAPO/CPP2 - CIF Post processing (display records)� /SAPAPO/CPPR - CIF Post processing (archive records)� /SAPAPO/CPPA - CIF Error Handling (alerts)

Postprocessing records that have been processed or that are set as obsoleteare not deleted automatically by the system. To delete them, use program/SAPAPO/CIF_POSTPROC_REORG. Only postprocessing records with thestatus Processed, Obsolete (set manually), or Obsolete (set automatically bysystem) can be deleted. If you want to delete postprocessing records with thestatus Still to be processed, you can use this program to set them as obsoleteand then you can delete them in a subsequent program run.

Hint: The actions �set as obsolete� and �delete� only refer to thepostprocessing records, not to the objects for which the postprocessingrecords were created.

The reorganization program offers you the following features:

� Set postprocessing records as obsolete If you set the Set PP Recs asObsolete indicator, all postprocessing records that meet the selectioncriteria, have the processing status Still to be processed, and that areolder than the specified number of days are assigned the status Obsolete(set manually).

� Delete postprocessing records. You can choose between two alternatives.

� If you set the indicators Delete PP Recs and Delete All PP RecsOlder Than, the system deletes all postprocessing records that meetthe selection criteria and for which the status was set to Processed,Obsolete (set automatically by system), or Obsolete (set manually)in the time frame specified. The standard setting is 7 days.

� If you set the Delete PP Recs indicator and choose Delete All PPRecs, the system deletes all postprocessing records that meet theselection criteria and that have the status Processed, Obsolete (setautomatically by system), or Obsolete (set manually).



You use the CIF postprocessing alert (program /SAPAPO/CIF_POST-PROC_ALERT) to check whether postprocessing records were generatedduring CIF error handling. You also use it to specify that the initiator of anerror or the system administrator should receive a message when errors occur.This makes it easier to monitor the change transfer for transaction data.

Figure 31: Post Processing Alert (NEW)

Compare/ReconcileData inconsistencies between SAP SCM and SAP R/3 can arise in certaincircumstances, for example, due to application errors or manual deletionof queue entries. The compare/reconcile function helps you to identify andcorrect such data inconsistencies.



Figure 32: CIF Compare/Reconcile Function



The CIF compare/reconcile report can only be initiated in SAP SCM. Youcan restrict the tool to a particular �partner system�, as well as material andlocation. The report compares the following objects:

� Production/Process orders*� Planned orders*� Purchase orders� Purchase requisitions� Confirmations� Sales orders� Planned independent requirements� Inspection Lots� Shipments� Stock and stock types

Note: * In addition to the orders themselves, the report can comparereceipts and requirements for each order. The following inconsistencieswill be identified in the following priority:

1. Existence2. Quantity3. ATP Category4. Difference in plant/storage location5. Difference in pegging area



Figure 33: Compare/Reconcile Transactions

When you use the compare/reconcile function, the system collects the relevantdata from SAP R/3 and SAP SCM and performs a comparison and lists anyinconsistent objects it identifies. Then you can select individual, several, or allobjects for the reconcile function. The selected data is then sent again fromSAP R/3 to SAP SCM or from SAP SCM to SAP R/3. After executing thecompare function, the results are displayed in an overview. Any existingerrors are also shown. You can remove the error (reconcile function) directlyfrom the display of the results.

The compare/reconcile report can be run in the background due to the lengthof the runtime, (anywhere from 5-8 hours for a large selection). Prior to SCM4.0, when the report was run in a background job, the results are sent in theform of a spool list. This spool list can not be processed. As of SCM 4.0 youhave the choice of processing the report interactively or saving it to a clustertable for later review. Upon reviewing the results at a later time, users canthen process the data that was run the in the background.



Compare/Reconcile Report

1. SAP SCM menu path: Advance Planning and Optimization → APOAdministration→ Integration→ CIF Compare/Reconcile Function→ ExecuteCompare/Reconcile

2. Enter Partner system T90CLNT090, material T-F2##, and Location 1000.

3. Select Storage location Stocks and select Execute

4. When the results tab appears, select storage location stocks and explainthat SAP R/3 has inventory, SAP SCM does not because the User Id forthe RFC destination was locked.

5. Select the item and choose Send to APO

6. Rerun the report with the same criteria and the situation should haveresolved itself.



Lesson Summary

You should now be able to:� Describe the data transfer process, and how errors are recorded� Demonstrate the qRFC Monitor and explain its purpose in handling






purpose in handling transfer errors


SCM210 Lesson: Incremental Transfers for Master Data Changes

Lesson: Incremental Transfers for Master Data Changes

Lesson OverviewNow that the integration models have been created and the initial data transferhas taken place, you will need to complete the setup for the incrementaltransfer of master data changes.


� Explain how new SAP SCM relevant data is transfer automatically fromSAP R/3 via existing integration models

� Explain how changes in SAP R/3 to existing integrated data, will betransfer to SAP SCM via the CIF.

Business ExampleThe integration of master data and transactional data for SAP SCM relevantdata objects needs to be organized to execute with minimal intervention. Itmust also include all relevant data including data objects that may be createdat a later date. You need to decide how frequently to update an integrationmodel, and create a batch job to do so.

Transfer of New Master Data to SAP SCMDepending upon the industry that your company competes in, the amountof new master data created may differ. In consumer packaging companies,where products are driven by marketing, products and related master dataare created daily. In a slowly changing industry like Aerospace, only a fewnew materials may be created a month. No matter what situation you are in,your organization should develop a process that simplifies how new data,or existing data that undergoes a change, makes it�s way into SAP SCM ina simple automatic method.



Figure 34: Transfer New SAP SCM-Relevant Master Data (1)

When integration models are initially created it makes good business sense tocreate program variants in order to reuse the selection criteria to pick up newdata. New SAP SCM-relevant master data (in the example on the slide above,a new material with MRP type X0), that corresponds with the selection criteriaof an existing integration model (in the example, materials with the MRP typeX0 are selected in the integration model), can be transferred into SAP SCM inthe following way: Manually or by scheduling a background job, the systemre-generates the existing model (the new master data is also selected here).There are then two models with the same name, the only differences being thedates and times. If the activation is performed in this situation, the differenceis then transferred (including any existing change pointers). The systemcompares the existing, active integration models with the new model. Afterthe data transfer, the system deactivates the old integration model, leaving thenew integration model as the active model.

If you have activated model 1 with the material masters A and B, and activatea model 2 in the second step with material masters B and C, then whenyou activate model 2, only material C will be transferred. Then when youdeactivate model 1, the integration for materials B and C remain, howeverA is no longer integrating with SAP SCM. To ensure that the system hastransferred all the SCM-relevant master data, it is possible to periodicallyregenerate and activate the existing integration models. As any existingchange pointers are also processed in this procedure, a separate transfer ofdata changes is no longer necessary.



Figure 35: Transfer New SAP SCM-Relevant Master Data (2)

Defining jobs enables the system to regenerate and then activate theintegration models in regular intervals, as the SAP R/3 System is constantlycreating new SAP SCM -relevant master data. The system generates anintegration model using the RIMODGEN report. You schedule this report bycreating a job and entering a variant (that you must have defined when youinitially created the integration model). The system activates an integrationmodel via the RIMODAC2 report. You need a variant for this report too, inorder to schedule it in a job. "Executing" an integration model consists oftwo steps: The generation and activation of an integration model. You canschedule these two steps with a job, where you define the two activities astwo consecutive steps. To avoid creating many old models that are no longerneeded during the regular generation and activation of the integration models,you should regularly delete the old models. You can also schedule deletionsperiodically with the RIMODDEL report. If you set the Log deactivatedmaterial masters switch during activation of an integration model, materialmasters that are no longer active after the activation of the new model arelogged (the new model may replace an old model with the same name).Report RCIFMTDE then allows you to display the corresponding list or setthe corresponding product masters in SAP SCM to external planning, so thatthey are not included in an SAP SCM planning run.



Setting Background jobs for Master Data Transfer

1. SAP R/3 menu path: System→ Services→ Jobs→ Define Job (SM36)

2. Enter Job NameMatTransfer, and select Define Steps

3. Select ABAP Program, and Enter Program name RIMODGEN, and enteryour variantMAT##, language EN.

4. Select SAVE

5. Select Start Condition

6. Select Immediate

7. Select SAVE

8. Select SAVE

9. Review how many models are available for activation. SAP R/3 Menupath: Logistics → Central functions → Supply Chain Planning Interface→ Core Interface Advanced Planner and Optimizer → Integration Model→Activate

10. Select the models using your integration model name PUMP##

Transfer Changes of Existing Integrated Data to SAP SCMIn several industries, when changes are made to existing products, instead ofgenerating new material numbers, customers continue to use existing materialnumbers. Some changes may be as simple as a differentplanned delivery time,or go as far as replacing a component in the bill of material.



Figure 36: Transfer of Master Data Changes (1)

Any changes you make to the master data in the SAP R/3 System that arealso SAP SCM -relevant, must be transferred into the SAP SCM System. Thesystem does not usually carry out a new initial data transfer, but just transfersthe individual changes to the master data. In the same way, the system alsotransfers a deletion flag for a material into SAP SCM . A transfer of datachanges requires that an active integration model is available for the relevantmaster data, and that the master data is SAP SCM -relevant. With the transferof master data changes, remember that the system will transfer the completedata record. If, for example, you change a field in the material master, theentire material master will be re-transferred in the transfer of data changes.



Figure 37: Transfer of Master Data Changes (2)

SAP R/3 is the dominant master data system. As a rule, the system performschanges to the master data in the SAP R/3 System and transfers them fromthere into the SAP SCM System. With master data changes, it is not necessaryfor the system to totally retransfer all master data objects as an initial datatransfer. Instead, the system can transfer just the changed master data records.There are several different methods of transfer for master data changes.

For a transfer of data changes, you must set in Customizing in the SAP R/3System, that ALE change pointers are written for master data changes. First,you activate the change pointers (Activate Change Pointers Generally inCustomizing in ALE, transaction BD61).

Figure 38: Activate Change Pointers Generally (BD61)Figure 38: Activate Change Pointers Generally (BD61)

Once the change pointers have been activated, you must determine (inCustomizing, Activate Change Pointers for Message Type, transaction BD50),which master data objects should have change pointers.



Figure 39: Activation of Change Pointers by Message TypeFigure 39: Activation of Change Pointers by Message Type

The following objects currently allow change pointers

� CIFCUS - Customer Master Records� CIFECM - Engineering Change Masters (only for Discrete Industry

Solution)� CIFMAT - Material Master Records� CIFMTMRPA - Material Master Records for MRP Areas� CIFPPM - Production Process Models (BOMs and Routings)� CIMPPPR - Planning Product (MRP planning Strategy 60)� CIFSRC - Purchasing Information Records� CIFVEN - Vendor Master Records.



Figure 40: Transfer Master Data Changes Periodically

Once specific fields in the object of choice are changed a simple change pointeris created for that specific object. This change pointer selects the master datafor the system to retransfer. When you call up the transaction Change Transfer- Master Data (CFP1), specify the logical target systems and the master dataobjects (material masters, vendors, sources of supply, customers), that havechanges to be transferred. You can save your settings for the transfer of datachanges as variants and, if necessary, use these variants for the periodicscheduling of transferring data changes as a job (RCPTRAN4 report). Changesmade to SAP R/3 routings or BOMs can be transferred to SAP SCM as a PPMtransfer of data changes. This transfer takes place with a separate transaction.



Figure 41: Master Data Change Transfer (CFP1)Figure 41: Master Data Change Transfer (CFP1)

Note: Currently SAP has determined which fields will set the changepointer for each message type. If your organization requires otherfields to set the change points, use transaction BD62. This will allowyou to define which fields can set the change pointers.

While most objects use the change pointers for periodic updates, some masterdata objects are not subject to a background job to update SAP SCM, but canbe transferred real time if there is a need for a faster update process. If you useBusiness Transfer Events (BTE), the settings for the message types CIFMAT,CIFVEN and CIFCUS are automatically set, and any changes to these objectswho are assigned to an active integration model are immediately updated inSAP SCM. This is carried out through transaction CFC9



Figure 42: Real-Time Transfer of Master Data Changes (CFC9)Figure 42: Real-Time Transfer of Master Data Changes (CFC9)

The system can transfer changes to SAP SCM-relevant master data (datacontained in an active integration model), the material master, customer, andvendor, in real-time, (directly when updating a data change in the SAP R/3System) into the SAP SCM System. The settings for this function are madein CIF transaction Configure Transfer of Data Changes. In real-time transfer,the system transfers the complete data record that has been changed directlyto the SAP SCM System. (For numerous changes there are correspondingrepercussions on the system performance, this function requires more settingsto be made according to the online documentation). In the periodic transfer,the system collects and transfers the master data changes into the SAP SCMSystem, within a normal transfer of data changes. If this is set to immediate,the periodic job to transfer data changes can be deactivated. If the transferof data changes is set to "Business Transaction Event, immediately", theprocessing takes place without using change pointers. If the transfer of datachanges is set to periodically, the change pointers are automatically activated.Similarly to the change pointers, the change is checked to see whether itis relevant for SAP SCM before the online transfer. This check takes placebased on the SCM master data structure: it is converted after the change of



the new SAP R/3 master data document into the SAP SCM document andcompared with the existing SAP SCM document � another transfer of masterdata changes only takes place if there are differences.

Caution: ALE change pointers are not deleted in SAP R/3 after thetransfer of data changes, they are marked as processed. To prevent adrop in system performance, we recommend that you delete ALEchange pointers regularly using the relevant IMG activity in the CIFIMG (Basic Settings for the Data Transfer → Change Transfer → ChangeTransfer for Master Data→ Reorganize ALE Change Pointers) or by callingtransaction BD61.

Use transaction SM30 to call the screen Maintain Table Views: Initial Screen.Call table CIFIMODGEN. You see the screen Change View "CustomizingAutomatic Generation of Integration Models". You determine the procedurefor adapting the integration model by making entries in this database table.The table contains the following columns: Connection Point: Contains oneof six different possibilities:

� Creation of new material master data (MAT_INS)� Changing of material master data (MAT_UPD)� Creation of customer master data (CUS_INS)� Changing of customer master data (CUS_UPD)� Creation of vendor master data (VEN_INS)� Changing of vendor master data (VEN_UPD)

Program: Contains the name of an ABAP/4 program. This program should beexecuted when one of these events occurs. Usually, you should specify thestandard program RIMODGEN for generating integration models.

Variant: Contains the name of a variant. This variant contains the inputparameters of the given program.

Counter: You can specify several program/variant combinations for the sameconnection point and determine their sequence using the Counter column

Note: As of SCM 4.0 and PI2003.1 it is now possible to update capacitychanges immediately to the SAP SCM resource master data. InTransaction CFC9, under the section Initial Data Transfer and ChangeTransfer For a resource, users can select Immediate Transfer. Inaddition they can choose if all data will be maintained in SAP R/3Rather than maintaining the data in SAP SCM.



Changes to SAP R/3 production versions, routings, master recipes or BOMscan be transferred to SAP SCM via the PPM transfer of data changes(transaction CFP3): The PPM that corresponds with these objects (or the iPPEruntime object) is created.

Figure 43: PPM Transfer of Data Changes

If one of the SAP R/3 objects mentioned above is changed, a PPM changepointer is written. These change pointers are processed with the PPM transferof data changes. If change pointers have been written that are not to lead toa transfer (for example, because the change is old), they can be deleted withtransaction CFP4. (Changes to the operation from classification at the workcenter do not require a change pointer.) Note the following restrictions in thePPM transfer of data changes: no change pointers are written for changes todummy BOMs, changes to referenced reference operation sets, changes toreferenced objects (for example, component scrap in the material master).



Figure 44: Integration Model: Other Functions

After deactivation of an integration model for transaction data, the affectedtransaction data is not exchanged between SAP R/3 and SAP SCM: forexample, sales orders that are created in the SAP R/3 after deactivation ofthe model are no longer transferred. Planned orders that are created inSAP SCM after deactivation of the corresponding integration model are nottransmitted to SAP R/3 either. Deleting an integration model does not meanthat the previously selected data in SAP SCM is also deleted. (For master datacontained within an active integration model, and for which you have set adeletion flag in SAP R/3, the deletion flag is transferred to SAP SCM usinga transfer of data changes).



Lesson Summary

You should now be able to:� Explain how new SAP SCM relevant data is transfer automatically from

SAP R/3 via existing integration models� Explain how changes in SAP R/3 to existing integrated data, will be

transfer to SAP SCM via the CIF.


SCM210 Lesson: Organizing Integration Models

Lesson: Organizing Integration Models

Lesson OverviewNow that you understand how to create and activate integration models forboth the initial data transfer and the incremental data transfer, you mustunderstand how to organize your integration models for efficient execution.


� Organize integration models according to SAP recommendations.

Business ExampleThe integration of master data and transactional data for SAP SCM relevantdata objects needs to be organized according to SAP recommendations.

Organizing Integration ModelsAs you plan your data integration between the SAP R/3 Systems and the SAPSCM System, you will want to organize your integration models. Theseshould be organized in a manner that will make master data integrationefficient and concise. SAP recommends that you organize your integrationmodels according to the following list.



Figure 45: Integration Models: Master Data

In addition to master data the transaction data must also be selected andintegrated using integration models. SAP recommends that you organize yourintegration models according to the following list.

Figure 46: Integration Models: Transaction Data


SCM210 Lesson: Organizing Integration Models

Lesson Summary

You should now be able to:� Organize integration models according to SAP recommendations.


Unit Summary SCM210

Unit SummaryYou should now be able to:� Explain the basic concept of integrating SAP SCM to a OLTP (On-line

Transaction Processing System) system.� Give a basic explanation as to how SAP R/3 and SAP SCM systems

integrate.� Explain the basic steps to integrate an SAP R/3 and an SAP SCM System� Demonstrate the need or use of RFC connections between SAP R/3 and



with one or more OLTP systems.�� Create integration models for transfer of transactional data using SAP

recommended selection methods.� Activate integration models for transfer of transactional data.� Describe the data transfer process, and how errors are recorded� Demonstrate the qRFC Monitor and explain its purpose in handling






purpose in handling transfer errors� Explain how new SAP SCM relevant data is transfer automatically from

SAP R/3 via existing integration models� Explain how changes in SAP R/3 to existing integrated data, will be

transfer to SAP SCM via the CIF.� Organize integration models according to SAP recommendations.


SCM210 Test Your Knowledge

Test Your Knowledge

1. What is the software that is used to connect you SAP R/3 system to othermySAP components?

2. What is the name of the component that will allow SAP R/3 to talk toSAP SCM?

3. What is the name of the tool that users will interface with to triggerintegration between SAP R/3 and SAP SCM?

4. What are the two ways that OLTP systems can interface with SAP SCM?

5. To integrate your SAP R/3 System to SAP SCM, it is as simple as Plugand Play.Determine whether this statement is true or false.□ True□ False


Test Your Knowledge SCM210

6. A Logical System Name can be assigned to one our more clients?Determine whether this statement is true or false.□ True□ False

7. A logical system name can have more than one RFC DestinationDetermine whether this statement is true or false.□ True□ False

8. Explain the difference between inbound and outbound queues?

9. If integrating with only one SAP R/3 client, no business system group(BSG) is needed.Determine whether this statement is true or false.□ True□ False

10. What is SAP SCM relevant data?

11. The actual selection of data by an integration model takes place whenthe model isFill in the blanks to complete the sentence.



12. List the 2 steps involved in integrating data between SAP R/3 and SAPSCM.

13. The Name and Target System uniquely identifies an integration model.Determine whether this statement is true or false.□ True□ False

14. Why is it better to use a generic selection criteria like MRP Type ratherthan specific material numbers to select data in an integration model?

15. Which of the following is a benefit of using MRP Type X0 as a selectioncriteria for SAP SCM relevant materials?Choose the correct answer(s).□ A It excludes the material from MRP planning in SAP R/3.□ B It ensures all dependent requirements are created even for

non-SAP SCM relevant components by exploding the BOMduring the next MRP planning run in SAP R/3.

□ C It automatically causes a product to be planned in SAP SCM.□ D It�s a good generic selection criteria for an integration model

which minimizes maintenance.



Answers

1. What is the software that is used to connect you SAP R/3 system to othermySAP components?

Answer: SAP R/3 Plug-in

2. What is the name of the component that will allow SAP R/3 to talk toSAP SCM?

Answer: CIF (Core Interface)

3. What is the name of the tool that users will interface with to triggerintegration between SAP R/3 and SAP SCM?

Answer: Integration Models

4. What are the two ways that OLTP systems can interface with SAP SCM?

Answer: For SAP R/3 3.1I and higher the SAP R/3 Plug-in. For non-SAPsystems or SAP R/3 3.1H and lower (R/2 also) will use the BAPI (BusinessApplication Programing Interfaces)

5. To integrate your SAP R/3 System to SAP SCM, it is as simple as Plugand Play.

Answer: False

No, you first need to install the plug-in. Follow the seven steps.

6. A Logical System Name can be assigned to one our more clients?

Answer: False

No, a logical system name is a unique identifier that is assigned to onlyone client on any of your SAP instances.



7. A logical system name can have more than one RFC Destination

Answer: True

As of SCM 4.0, companies can use "flexible" RFC. This allows companiesto set different authorizations to different types of function calls.

8. Explain the difference between inbound and outbound queues?

Answer: When using and inbound queue the sending system controlshow the data is saved. Outbound queues allow the recieving system tomanage the data recording process.

9. If integrating with only one SAP R/3 client, no business system group(BSG) is needed.

Answer: False

A minimum of one BSG is needed. Multiple BSGs are only necessary ifyou have maser data number ranges that overlap on different instances.This allows companies the opportunity to easily define unique data sets.


Answer: SAP SCM relevant data is any data that is contained in an activeintegration model with SAP SCM.

11. The actual selection of data by an integration model takes place when themodel is generated.

Answer: generated.


Answer:

� Generate the integration model. This consists of creating and saving.� Activate the integration model. This consist of the activation and

initial transfer.



13. The Name and Target System uniquely identifies an integration model.

Answer: False

The integration model is uniquely identified by the Name, Target System,and Application.


Answer: A generic selection criteria like MRP Type can helpautomatically include new products without adding a specific materialnumber to the selection criteria.

15. Which of the following is a benefit of using MRP Type X0 as a selectioncriteria for SAP SCM relevant materials?

Answer: A, B, D

MRP Type X0 by itself does not cause the product to be planned in SAPSCM. Only if you use MRP Type as a selection criteria in your integrationmodel does it then become an SAP SCM relevant material. Additionalsettings may need to be done in SAP SCM in order for the material to beincluded in SAP SCM planning.


Unit 2Integrated SCM Master Data

Unit OverviewIn this units, students will get an introduction to master data integration. Youwill discuss how various SAP R/3 objects will be mapped to SAP SCM


� Identify the type of locations that SAP SCM supports from a planningperspective.

� Explain how Plants are transferred to SAP SCM and demonstrate theresults

� Explain how MRP Areas are transferred to SAP SCM and demonstratethe results

� Explain how Customer Master records are transferred to SAP SCM anddemonstrate the results

� Explain how Vendor Master records are mapped to SAP SCM anddemonstrate the results

� Explain the effects of SAP SCM location types on supply chain modeling� Identify the dependencies created as a result of the integration between

the materials master in SAP R/3 and SAP SCM.� Transfer Material Masters from SAP R/3 to SAP SCM.� Identify how the SAP R/3 work center and resource will transfer to SAP

SCM via the Core Interface.� Review the results of a transferred resource from SAP R/3 to SAP SCM

via the Core Interface.� Identify the modeling options for maintaining a resource after it has been

transferred to SAP SCM from SAP R/3.� Identify the dependencies between the SAP R/3 production version, and

the SAP SCM production process models.


Unit 2: Integrated SCM Master Data SCM210

� Transfer a production version from SAP R/3 to SAP SCM via the CoreInterface.

� Identify the limitations of the PPM when modeling a manufacturingprocess in SAP SCM.

� Identify the dependencies between SAP R/3 production version, andSAP SCM Run Time Objects (RTO).

�� Identify how SAP R/3 Purchasing master data can transfer to SAP SCM

via the Core Interface.� Review the results of transferring a purchasing info record from SAP R/3

to SAP SCM via the Core Interface.�� Identify how the special procurement functionality in SAP R/3 will

transfer to SAP SCM via the Core Interface.� Review the results of a transferred transportation lane from SAP R/3 to

SAP SCM via the Core Interface.� Review an SAP SCM PPM that was generated by transferring a master

recipe via the Core Interface.� Identify the differences between transferring a Master Recipe and a Bill

of Material and Routing to SAP SCM.

Unit ContentsLesson: Locations in SAP SCM.... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96

Exercise 3: Locations in SAP SCM .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .105Lesson: Material Masters in SAP SCM .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111

Exercise 4: Material Master Updates in SAP SCM (Optional TimeDepending) .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .125

Lesson: Resources in SAP SCM ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .131Exercise 5: Displaying a resource in SAP SCM... . . . . . . . . . . . . . . . . . . . . . . . . .151

Lesson: Production Process Models (PPM).. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .156Exercise 6: Transferring a production process model to SAP SCM ... . .171

Lesson: Run Time Objects (RTO)/ Production Data Structure (PDS) .. . . . . .184Procedure: Create and Display RTO .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .190

Lesson: Purchasing Information Records ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .193Procedure: Display Procurement Relationships... . . . . . . . . . . . . . . . . . . . . . . . . .199

Lesson: Transportation Lanes ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .201Procedure: Create Transportation lane in SAP SCM from SpecialProcurement Key ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .207

Lesson: Master Recipes and the PPM... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .209


SCM210 Unit 2: Integrated SCM Master Data

Procedure: Recipes in SAP SCM ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .215



Lesson: Locations in SAP SCM

Lesson OverviewIn this lesson, you will learn how to transfer master data objects from SAP R/3Enterprise to SAP SCM as locations.


� Identify the type of locations that SAP SCM supports from a planningperspective.

� Explain how Plants are transferred to SAP SCM and demonstrate theresults

� Explain how MRP Areas are transferred to SAP SCM and demonstratethe results

� Explain how Customer Master records are transferred to SAP SCM anddemonstrate the results

� Explain how Vendor Master records are mapped to SAP SCM anddemonstrate the results

� Explain the effects of SAP SCM location types on supply chain modeling

Business ExampleAssume you are a manufacturer of pumps, and your company needs toperform distribution, manufacturing, and procurement activities. As thesupply chain engineer who is responsible for modeling your SAP R/3execution environment in SAP SCM , you must identify how your company�sbusiness can be planned using SAP SCM.

Master Data Objects as locationDuring the evaluation process in your implementation you must considerwhich elements of the supply chain are required to be planned in SAP SCM.Through the use of the CIF, you will have opportunities to transfer severaldifferent master data objects in SAP R/3 and Map them to a common type ofmaster data object in SAP SCM called a LOCATION.


SCM210 Lesson: Locations in SAP SCM

Figure 47: Locations in SAP SCM

The various location types are:

� Plant → Production Plant (1001)� Plant → Distribution Center (1002)� Transportation Zone → Transportation Zone(1005)� Storage Location→ MRP Area (1007)� Customer → Customer (1010)� Vendor → Vendor (1011)� Vendor → Carrier/Transportation Service Provider (1020)

Other location types such as Stock Transfer point, Terminal, or GeographicalArea are for industry specific solution.

Each location type will serve a specific purpose for planning which will bediscussed later. The main commonality between all location types is that youcan do typical planning activities, even though your company may not ownthe stock at the location or the location itself.



Plants and Distribution centers in SAP SCM

Figure 48: Location Type Production Plant

The system transfers a plant into the SAP SCM System as a location withlocation type 1001 (production plant). The system also copies the basicsettings for the plant, such as description, address data, time zone, andregional assignment. While the entire address maps to the location in SAPSCM, companies can also turn on Geocoding functionality. This functionalityallows companies to use the address in SAP R/3 to determine Longitude andLatitude for map placement and distance calculation in SAP SCM. Other itemssuch as the calendar however, do not transfer to the location in SAP SCM.



Figure 49: Additional Data in the SAP SCM Location

You can maintain the short text for the SAP SCM System locations in severallanguages in contrast with the plant in an SAP R/3 Enterprise. The languageselected at logon will be used to select the specific language for display.

As a rule, the SAP SCM System locations contain additional planningparameters that have no equivalents in an SAP R/3 Enterprise system. You candefine these parameters directly in an SAP SCM System. The system cannottransfer the parameters from an SAP R/3 Enterprise.



Figure 50: Location Type Distribution Center

In SAP R/3 Enterprise 4.0, the system can define plants as distribution centerswithin the frames of the Distribution Resource Planning (DRP) function inan SAP R/3 Enterprise. To achieve this, you use the corresponding entry inthe Customizing table. For this, follow Customizing step Assign Node Type -Maintain Plant in the settings of DRP Customizing.

When you transfer plants, which are defined in an SAP R/3 Enterprise, toan SAP SCM System as distribution centers, the system transfers them tolocation type 1002 (distribution center). The transfer of the individual SAP R/3Enterprise plant settings (in SAP R/3 Enterprise, a DC is a plant) takes placein exactly the same way as it does for production plants. If you are workingwith a release later than SAP R/3 Enterprise 4.0, where you cannot defineDCs, you need to use a customer exit to transfer an SAP R/3 Enterprise plantas an SAP SCM-DC.



MRP Areas in SAP SCM

Figure 51: Location Type MRP Area

In SAP R/3 Enterprise 4.5, MRP areas are available in the SAP R/3 Enterpriseto differentiate requirements planning below the plant level. You can transferstorage location MRP areas, known as type 2 MRP areas, to the SAP SCMSystem as locations with location type, 1007.

In the SAP R/3 Enterprise, MRP areas are organizational levels below the plantlevel; MRP areas are assigned to one particular plant. This plant assignmentremains in the SAP SCM.

Prior to SCM 4.0, PI2003.1, you could transfer a storage location MRP area tothe SAP SCM System only if the MRP area has exactly one storage locationassigned to it. As of SCM 4.0 and SAP R/3 4.7 x2.0, MRP Areas with more thanone storage location can be transferred to SAP SCM. In addition it was notpossible to transfer between MRP Areas until Extension set 2.0 of SAP 4.7.Prior to extension set 2.0 customers had to use a customer exit or BAPI wheninterfacing with SAP SCM.

Note: Plant MRP areas cannot be transferred but the plants can betransferred.



In the SAP R/3 Enterprise, the material master can be included in the plantMRP data and MRP area segments. This enables planning the material indifferent MRP areas. When the system transfers such materials to the SAPSCM System, the MRP area data can also be transferred: The SAP SCM Systemcontains a product master for the plant location and the MRP area locations.

Customers in SAP SCThe system transfers customers from the SAP R/3 Enterprise as locations oftype 1010 (Customer). You need a customer in the SAP SCM System when thecustomer is to be planned in the SAP SCM System, for example:

� Capable-to-Match for mapping prioritization of sales orders/independentdemand to production capacity or stock

� PP/DS for customer specific Independent requirement consumptionand reduction

� SNP/DEPL/TLB for Vendor managed inventory. (need to plan customerlocation like your own plant)

� TP/VS for planning shipments directly to customer locations

Figure 52: Location Type Customer



When transferring the Customer Master to SAP SCM, the address is theonly item that comes across via the CIF. If this is a VMI customer, there areadditional fields available where sales organizational data can be maintain.When the system transfers a customer master from the SAP R/3 Enterpriseto the SAP SCM System, the actual customer location is transferred, as isthe transportation zone that is assigned to the customer in the SAP R/3Enterprise, as location type 1005 (transportation zone). The transportationzone is configuration data in SAP R/3, but is transferred to SAP SCM as a newlocation type. This new piece of master data will need additional data enteredin SAP SCM in order to make it useful in planning, (e.g. geocoordinatesfor longitude/latitude.) In addition, the CIF will create a hierarchy for eachtransportation zone which will reference all the related customer masters.This becomes SAP SCM master data which is used for planning in TP/VSand in some instances TLB. The menu path for viewing these are AdvancedPlanning and Optimization→Master data→ Hierarchy. They can be listed underthe hierarchy name TZONE.

Vendors in SAP SCMThe system transfers vendors from the SAP R/3 Enterprise as locations withtype, 1011 (vendor). Vendors are not necessary data in SAP SCM, and thereare only a couple of reasons why vendors would be modeled in SAP SCM

� Source determination for buy parts. (More than one Vendor supportsthe procurement of a specific part

� You need to model the vendor as a constraint and may need bills ofmaterials and routings (PPM)

� Vendor is a contract manufacturer� Source determination, make versus buy.



Figure 53: Location Type Vendor

When the vendor is transferred via the CIF only the address informationcomes across. All other information is specific to SAP SCM.

Caution: If the vendor and the customer have the same number ornumber range, in the SAP R/3 Enterprise one or both will need to berenamed. For example, customer and vendor are both representedby the number 1000. You need to rename either the customer orthe vendor in the SAP SCM System inbox using the correspondingcustomer exit. For example, rename the vendor as S1000. Otherwise,you cannot distinguish between the two locations. Location type is nota key in the table /SAPAPO/LOC.

Note: There is currently no functional difference between the VendorLocation type and the plant and distribution center location type.

In addition to vendors with whom your organization purchases materialsfrom, companies can also models freight haulers as a location type inSAP SCM. If a vendor master record is created with account group 0005(Forwarding Agent), this will map to location type 1020 (TransportationService Provider). This type of location is used specifically in TP/VS to allowfor selection and planning of carries for the SAP R/3 shipments. In additionto the address information being transferred to SAP SCM, the SCAC codewill be transferred.



Exercise 3: Locations in SAP SCM

Exercise ObjectivesAfter completing this exercise, you will be able to:� Display various SAP SCM locations resulting from the transfer from

SAP R/3 Enterprise

Business ExampleAssume as a planning manager, you need to transfer all of your supplychain data to a centralized SAP SCM System for detailed planning. Whiletransferring data, you need to ensure that a proper location type is selectedin SAP SCM for detailed planning.

Task 1: Review SAP SCM Plant locationsTo insure that your data is being modeled correctly in SAP SCM, review thedata of one of your larger pump manufacturing plants.

1. Display production plant 1000 in the SAP SCM System. Display thislocation.

2. Use the F4 help in the Location type field on the initial screen of thelocation master, to enter the location type for the production plant.Which type is for production plants?

3. Display production plant 1000. The data is arranged on several tab pages.Go to the Address tab page:

What is the name of the location?

Which street and city address is entered for it?

Which time zone is assigned to plant 1000?

4. Display other tab pages for location 1000 in SAP SCM. Here you willfind a number of settings that have no corresponding settings in the SAPR/3 plant. If you want to use such functions in SAP SCM , you mustmaintain these settings after you have transferred your data to SAP SCM.Display other tab pages for location 1000 in SAP SCM.




Task 2: SAP R/3 Plant ConfigurationAs a new employee who is responsible for maintaining the supply chainrelevant master data you must familiarize your self with the existing plantconfigurations.

1. In SAP R/3, display the source of production plant 1000. In SAP R/3,plants are defined in Customizing. Display plant 1000 in Customizing.

2. What is the name of plant 1000?

3. Which address is entered for it?

4. What is the time zone hidden behind the Address icon?

Task 3: Distribution Center set up in SAP R/3 and SAPSCMAs the person responsible for supply chainmaster data, you have to familiarizeyourself with location specific data. Your organization wants to specific inSAP SCM those locations that only perform distribution activities. Explore inSAP R/3 how to differentiate between a Plant and a Distribution Center.

Display plant 2400 in SAP R/3 Customizing.


2. The name implies that this plant is a distribution center (DC). Where is itmaintained in SAP R/3 ?

Make sure that plant 2400 is actually a DC. Name of plant 2400: MilanoDistribution Center

3. Display SAP SCM location 2400 (location type 1002).

4. What is the name of this location?

SAP

This location is of the type distribution center because plant 2400 wastransferred from SAP R/3.



Solution 3: Locations in SAP SCMTask 1: Review SAP SCM Plant locationsTo insure that your data is being modeled correctly in SAP SCM, review thedata of one of your larger pump manufacturing plants.

1. Display production plant 1000 in the SAP SCM System. Display thislocation.

a) In the SAP SCM System, select Advance Planning and Optimization→ Master Data → Location → Location .

2. Use the F4 help in the Location type field on the initial screen of thelocation master, to enter the location type for the production plant.Which type is for production plants?

a) Production plant type: 1001

3. Display production plant 1000. The data is arranged on several tab pages.Go to the Address tab page:

What is the name of the location?

Which street and city address is entered for it?

Which time zone is assigned to plant 1000?

a) Location name: Hamburg

Address: Alsterdorferstr. 13, 22299 Hamburg

Time zone: CET

4. Display other tab pages for location 1000 in SAP SCM. Here you willfind a number of settings that have no corresponding settings in the SAPR/3 plant. If you want to use such functions in SAP SCM , you mustmaintain these settings after you have transferred your data to SAP SCM.Display other tab pages for location 1000 in SAP SCM.

a) Select each view and pay attention to the number of SCM onlyrelevant fields.




Task 2: SAP R/3 Plant ConfigurationAs a new employee who is responsible for maintaining the supply chainrelevant master data you must familiarize your self with the existing plantconfigurations.

1. In SAP R/3, display the source of production plant 1000. In SAP R/3,plants are defined in Customizing. Display plant 1000 in Customizing.

a) SAP R/3 menu path: Tools → Customizing → IMG → Edit project,Select SAP Reference IMG Enterprise Structure → Definition →Logistics - General → Define, copy, delete, check plant.


a) Plant 1000: Hamburg

3. Which address is entered for it?

a) Address: Alsterdorferstr. 13, 22299 Hamburg

4. What is the time zone hidden behind the Address icon?

a) Time zone: CET

Task 3: Distribution Center set up in SAP R/3 and SAPSCMAs the person responsible for supply chainmaster data, you have to familiarizeyourself with location specific data. Your organization wants to specific inSAP SCM those locations that only perform distribution activities. Explore inSAP R/3 how to differentiate between a Plant and a Distribution Center.

Display plant 2400 in SAP R/3 Customizing.


a) SAP R/3 menu path: Tools → Customizing → IMG → Edit project,Select SAP Refrence IMG Enterprise Structure → Definition →Logistics - General → Define, copy, delete, check plant.

b) Name of the plant 2400: Milano Distribution Center

2. The name implies that this plant is a distribution center (DC). Where is itmaintained in SAP R/3 ?




Make sure that plant 2400 is actually a DC. Name of plant 2400: MilanoDistribution Center

a) Distribution centers are defined in Customizing for DRP. SAP R/3menu path: Tools → Customizing → IMG → Edit project Production→ Distribution Resource Planning (DRP)→ Basic Settings→Maintainassignment of node type � plant.

b) In the table that appears, define which plants are DCs.Distribution centers are noted by key�. DC� All other entries arenot SAP SCM relevant at this time.

3. Display SAP SCM location 2400 (location type 1002).

a) In the SAP SCM System, select Advance Planning and Optimization→ Master Data → Location → Location .

4. What is the name of this location?

SAP

This location is of the type distribution center because plant 2400 wastransferred from SAP R/3.

a) Name of location 2400: Milano Distribution Center



Lesson Summary

You should now be able to:� Identify the type of locations that SAP SCM supports from a planning

perspective.� Explain how Plants are transferred to SAP SCM and demonstrate the

results� Explain how MRP Areas are transferred to SAP SCM and demonstrate

the results� Explain how Customer Master records are transferred to SAP SCM and

demonstrate the results� Explain how Vendor Master records are mapped to SAP SCM and

demonstrate the results� Explain the effects of SAP SCM location types on supply chain modeling


SCM210 Lesson: Material Masters in SAP SCM

Lesson: Material Masters in SAP SCM

Lesson OverviewIn this lesson, you will learn how to transfer master data objects from SAP R/3to SAP SCM as product master. The lesson discusses two lot-sizing proceduresin detail, the static and periodic lot-sizing procedures. It also explains theprocess of defining the product master fields in the SAP SCM System.


� Identify the dependencies created as a result of the integration betweenthe materials master in SAP R/3 and SAP SCM.

� Transfer Material Masters from SAP R/3 to SAP SCM.

Business ExampleAssume your company manufactures many different types of pumps andpump sub-assemblies. In addition to manufacturing, your company mustprocure several raw materials that are in short supply or sourced by severalvendors.

Assume your company is currently using SAP R/3 to perform its planning,and is now moving towards implementing SAP SCM for more intensivesupply chain modeling and planning. Therefore, you need to transfermaterials from your SAP R/3 system to SAP SCM via the Core Interface, andreview the results.



Mapping Product Master Quantity Planning Components

Figure 54: Product Master in SAP SCM

The product master in the SAP SCM System is divided into different views.The header data (tab pages characteristics, units of measure, classification) isgeneral and valid for more than one location (global).

You can specify the planning of a product in the SAP SCM System, accordingto the location. Locations can be derived from plant type or MRP area(according to the SAP R/3 storage location MRP areas).

Many of the fields for the product are automatically filled when the systemtransfers a material master from the SAP R/3 . To guarantee the consistency ofthe data in the SAP R/3 and SAP SCM Systems, only maintain these fields inthe SAP R/3. The system then only changes the data during a transfer (froman SAP R/3) of the master data changes.

You can define the length of the SAP SCM System product master numberin the SAP SCM Customizing. Process step: Specify Output Format Of ProductNumber. As is standard in the SAP R/3 Enterprise, an 18-digit product numberis used.



Figure 55: General Data

The system transfers the following general data from the SAP R/3 materialmaster into the SAP SCM System product: Material group (Basic Data 1),transportation group (Sales: General/Plant Data), gross weight and volume(Basic Data 1), units of measure (Additional data), and classification data(Classification). Note that for classification data, the system transfers the classesand characteristics to the SAP SCM System beforehand.

Materials that the system transfers to the SAP SCM System must be part ofthe integration model. The selection of SAP SCM -relevant materials can bedefined using the MRP type X0 or any other selection criteria that suits yourcompanies requirements.



Figure 56: ATP Settings

After the transfer of ATP Customizing, the system can transfer the ATPsettings from the material master into the corresponding product.

The system transfers the checking group as the ATP group in the product andthe total replenishment lead time as the checking horizon directly from thematerial master.

The system transfers the check mode. It corresponds with the requirementsclass in an SAP R/3 , in other words, you enter the indicator for the customerrequirements class that is determined by the strategy group of the material.In an SAP R/3 , the requirements class is usually determined by the strategygroup of the material but can also be a result of the schedule line categoryin the sales order.

There is a calendar in the SAP SCM System for the checking horizon. Thesystem automatically suggests the production calendar for the particularlocation. You can change this setting later.



Figure 57: ATP Customizing

To transfer the ATP settings from the SAP R/3 material master to the SAPSCM System, the system first transfers the ATP Customizing into the SAPSCM System. You can select the ATP Customizing from an integration model,where the import of Customizing settings in the SAP SCM System is allowed.The Customizing step isMaintain Global Settings for Availability Check.

If you execute the availability check in the SAP SCM System and not in theSAP R/3 , then you need to define an integration model in which you choosethe indicator, Availability check and in the material selection, enter the materialsfor which the ATP check should take place in the SAP SCM System.

During the transfer of the ATP Customizing, the SAP R/3 checking group isdisplayed in an ATP group with the same indicator.

The system transfers the SAP R/3 checking rule as a Business Event with thesame name.

The requirements class in the SAP R/3 is displayed on the check modein the SAP SCM System. This ATP check mode is new and contains theassignment mode (that controls the function of allocation of customers andplanned independent requirements) and the production type (standard orcharacteristic for the planning of variants).

The system then transfers the SAP R/3 scope of check to the SAP SCM Systemcheck control that contains the scope of the check.



Figure 58: Requirements Strategies

The system transfers the planning strategies in the SAP R/3 material masterinto the SAP SCM product master, through the CIF.

Note: The logic varies slightly in both the systems. Even thenumbers that indicate the strategy in the SAP R/3 Enterprise andSAP SCM Systems do not usually agree, because several SAP R/3planning strategies can be mapped in the SAP SCM System with onerequirements strategy.

The SAP R/3 strategy group, which contains a main strategy and sometimesfurther secondary strategies, is maintained in the SAP R/3 material master.The main strategy from the SAP R/3 strategy group is always transferred tothe SAP SCM System.

The SAP R/3 strategy of make-to-order production (strategy 20) is notexplicitly transferred to the SAP SCM System as strategies are not neededfor make-to-order production in the SAP SCM System. SAP SCM Systemstrategies mainly concern the planned independent requirements. If thefield is left blank in SAP SCM the system will assume Make-to-Order (SAPR/3 strategy 20)



In the SAP R/3 material master, an MRP group can also be used to assign astrategy group to the material. When a material like this is transferred to theSAP SCM System, the system also checks and, if necessary, transfers thesesettings.

Figure 59: Consumption

The settings in the SAP R/3 material master for the consumption of plannedindependent requirements by sales orders are transferred through CIF. Thesystem does not transfer this setting because consumption mode 4 does notexist in an SAP SCM System and is not recommended.

In the SAP R/3 material master, an MRP group can also be used to assignconsumption to the material. When a material like this is transferred to theSAP SCM System, the system also checks and, if necessary, transfers thesesettings.



Figure 60: Individual and Collective Requirement

The settings for individual or collective requirements for dependentrequirements are transferred from the SAP R/3 material master to the SAPSCM product master through CIF. If the individual or collective indicator hasthe value 2 (collective requirement only), Always collective requirement is set in theSAP SCM product, and the Poss. individual customer requirements indicator isset for no value or 1.



Mapping Product Master Quantity Planning Components

Figure 61: Static Lot-Sizing Procedure

The system can transfer the static lot-sizing procedure of lot-for-lot orderquantity, fixed lot sizes and period lot size procedures from the SAP R/3material master to the SAP SCM product master, through the CIF.

The lot-sizing procedure lot-for-lot in the SAP R/3 material master is transferredaccordingly to the SAP SCM product master as the lot-for-lot lot size.

The SAP R/3 fixed lot size is transferred to the SAP SCM System as the fixedlot size. The system reverts to the Customizing of the SAP R/3 lot-sizingprocedure (see Customizing step Check Lot-Sizing Procedure): If lot sizeindicator F is defined, then set the fixed lot size in SAP SCM. The systemalso transfers the value for the fixed lot size specified in the SAP R/3 materialmaster.

The system transfers the Replenish to maximum stock level lot-sizing procedurein the SAP R/3 Enterprise material master, lot-for-lot into the SAP SCMproduct master, as SAP SCM displays the procedure of replenishing tomaximum stock level differently. In SAP SCM, this is possible in connectionwith the consumption-based reorder point planning that is controlled in theSAP SCM System by a heuristic in the product master. The values for the



reorder point and maximum stock level maintained in the SAP R/3 materialmaster are transferred to the product master through the SAP R/3 EnterpriseSCM interface.

The system transfers the indicator Lot size of sales order planning in the SAP R/3lot-sizing procedure (defined in Customizing) into the SAP SCM productmaster: If you are working with the lot size in the short term horizon, in thesales order planning in the SAP R/3 , the indicator, Always lot-size, is set inthe SAP SCM product master.

Figure 62: Period Lot-Sizing Procedure

The system can also transfer the periodic lot-sizing procedure of the SAPR/3 material master into the SAP SCM System. The system reverts to SAPR/3 Customizing, that you can find behind the lot-sizing procedure in SAPR/3 (see SAP R/3 Customizing step Check Lot-Sizing Procedure). If P (periodlot size) has been defined for the lot-sizing procedure here, a period lot sizewill also be set in the SAP SCM System. The lot size indicator determines inCustomizing, which period indicator the system will transfer into the SAPSCM System. The period indicators D (day), W (week), M (month) can betransferred. The system also transfers the number of periods, within whichthe procurement quantity should be summarized.

In a similar way, the system then transfers the indicator, Date determination inSAP R/3 Customizing of the lot-sizing procedure to the SAP SCM System. Forthe setting, availability date=requirements date, the availability date indicator



in the product is set to blank, for the setting availability date=start of periodthe availability date indicator is X and the period factor is 0, for the settingavailability date=end of period the availability date indicator is X and the periodfactor is 1.

Figure 63: Lot Size Parameter

The system can transfer many lot size parameters from the SAP R/3 materialmaster into the SAP SCM System.

The SAP SCM System contains planning functions that do not exist in the SAPR/3 . As a result, additional maintenance of the lot size parameters may benecessary in the SAP SCM product master, if functions without equivalents inthe SAP R/3 are used.

The system transfers the assembly scrap from the SAP R/3 material master tothe SAP SCM System. Note that the logic for the calculation of the scrap inthe SAP R/3 does not totally agree with the logic in the SAP SCM System. SeeSAP Note 390850 for more detailed information.



Figure 64: SNP2, PP/DS, Procurement and GR/GI

The system transfers the purchasing group from the SAP R/3 material intothe SAP SCM product.

The call horizon is defined in the SAP R/3 material by the scheduling marginkey for floats. The system transfers this call horizon into the SAP SCMproduct. The planning time fence is transferred from the SAP R/3 materialmaster record to the SAP SCM product master.

The procurement type, planned delivery time, goods receipt processing time,and the loading group of sales and distribution are also transferred.

Note: During transfer of the GR processing time the CIF makes acalculation, by multiplying the number of days for goods receipt by 24hours. This is done due to the fact that a day in the PP/DS horizon is 8hours, but in SNP it will be seen as a 24 hours.

� Mass maintenance for product master fields in SAP SCM (for those thatcannot be transferred from SAP R/3 ).

� Profiles for the product master.� Alternative solution: Enhancing the SAP R/3 material master record with

customer-specific fields (append structures) and transferring these fieldsto the integration model using a customer exit.



You can use mass maintenance to maintain product master records that youhave copied from SAP R/3 Enterprise. Call this from the initial screen inproduct master maintenance. In mass maintenance, you can maintain manyfields that cannot be transferred out of SAP R/3 Enterprise.

An alternative solution using an enhancement is to enhance the SAP R/3material master using customer-specific fields (append structures, see SAPnote 44410). You can also enhance the SAP R/3 material master so that youcan define the settings for functions that do not exist in SAP R/3 in the SAPR/3 material master. For the CIF transfer for these fields, note that you needto enhance CIF in the SAP R/3 outbox and the SAP SCM inbox to define thatthese fields are transferred. You can enhance CIF using the correspondingcustomer exits.





Exercise 4: Material Master Updates in SAPSCM (Optional Time Depending)

Exercise ObjectivesAfter completing this exercise, you will be able to:� Demonstrate how the SAP R/3 fields of the Material Master and the SAP

SCM fields of the Product Masters are linked.

Business ExampleYour company is constantly creating new products to meet an every changingconsumer demand. In order to plan the manufacturing and procurement ofyour materials, you must ensure that your OLTP system (SAP R/3) and yourplanning system (SAP SCM) are in sync. Assume your materials have alreadybeen transferred via the CIF. You will make specific changes to the SAP R/3material master and review the updates that the CIF will generate to the SAPSCM product master.

Task 1: Update Material Master in SAP R/3Assume that your role in the organization is that of a production planner. Assuch, you are responsible for the up keep of material/product masters in SAPR/3 and SAP SCM. Your material T-F1## has already been transferred to SAPSCM. Update the material master in SAP R/3 as directed in the following steps.

1. Your manufacturing manager at plant 1000 would like to run the shopfloor more efficiently for certain products. She has asked you to scheduleproduction of your Pump T-F1## by considering three days worth ofdemand at a time. In order to set up SAP R/3 and SAP SCM to do thisyou must set the appropriate lot size key.

Note: Do not save Material master yet!

2. The cost accountant for your pump products has brought to yourattention cost variances that have appeared on product T-F1## overthe last year. These increases are due to some manufacturing issues inmachining and assembly of the pump. This has also caused the cost of




materials up, due to inventories being short and having to expedite insome of the raw materials. You will try to resolve this issue by planningfor a 10 percent assembly scrap on the T-F1## at plant 1000.


3. Your distribution manager at Plant 1000 has been giving you feed back onyour delivery performance on material T-F1## from the production floorand asked to improve on it. On average your performance in regards tohitting your attainment schedule (planned vs. actual) has been off by oneday and has caused some delay in delivery. . In order resolve this issuewe will add Goods Receipt processing time of 2 days to improve the downstream planning process.




Task 2: Review CIF UpdatesOne of your responsibilities as a production planner is to keep your SAPR/3 system and SAP SCM system in sync. In the last task you made threechanges to an existing material master that was already integrated to SAPSCM via the CIF. Review your changes in SAP SCM to ensure that the datatransferred correctly.

1. How was the lot size key in SAP R/3 (3D) formatted in SAP SCM?

2. How was the assembly scrap value in SAP R/3 formatted in SAP SCM?

3. How was the goods receipt processing time value in SAP R/3 formattedin SAP SCM?



Solution 4: Material Master Updates in SAPSCM (Optional Time Depending)Task 1: Update Material Master in SAP R/3Assume that your role in the organization is that of a production planner. Assuch, you are responsible for the up keep of material/product masters in SAPR/3 and SAP SCM. Your material T-F1## has already been transferred to SAPSCM. Update the material master in SAP R/3 as directed in the following steps.

1. Your manufacturing manager at plant 1000 would like to run the shopfloor more efficiently for certain products. She has asked you to scheduleproduction of your Pump T-F1## by considering three days worth ofdemand at a time. In order to set up SAP R/3 and SAP SCM to do thisyou must set the appropriate lot size key.


a) Menu path:Logistics→ Production→Master Data→Material Master→Material → Change → Immediately

b) Enter material T-F1##c) Select �Select view(s)�, chooseMRP 1, and select �Organization

levels�, then enter plant 1000 and finally select Continue.d) In the �Lot size� field enter 3D (Three Day Lot Size)

2. The cost accountant for your pump products has brought to yourattention cost variances that have appeared on product T-F1## overthe last year. These increases are due to some manufacturing issues inmachining and assembly of the pump. This has also caused the cost ofmaterials up, due to inventories being short and having to expedite insome of the raw materials. You will try to resolve this issue by planningfor a 10 percent assembly scrap on the T-F1## at plant 1000.


a) While still in the MRP 1 view, in the section labeled �Lot Size data�enter an assembly scrap of 10%

3. Your distribution manager at Plant 1000 has been giving you feed back onyour delivery performance on material T-F1## from the production floorand asked to improve on it. On average your performance in regards tohitting your attainment schedule (planned vs. actual) has been off by one




day and has caused some delay in delivery. . In order resolve this issuewe will add Goods Receipt processing time of 2 days to improve the downstream planning process.

a) While still in the material master select theMRP 2 tab, and enter 2days for the GR processing time

b) After all three change have been made select SAVE

Task 2: Review CIF UpdatesOne of your responsibilities as a production planner is to keep your SAPR/3 system and SAP SCM system in sync. In the last task you made threechanges to an existing material master that was already integrated to SAPSCM via the CIF. Review your changes in SAP SCM to ensure that the datatransferred correctly.

1. How was the lot size key in SAP R/3 (3D) formatted in SAP SCM?

Answer: SAP SCM menu Path: Advanced Planning and Optimization→Master Data → ProductChoose product T-F1## at plant 1000 and selectChangeGo to the Lot Size tab, and select the Procedure tabThe product master in SAP SCM shows that the procedure was set to Byperiod , the period type was set to days, and the number of periodswas set to 3.

2. How was the assembly scrap value in SAP R/3 formatted in SAP SCM?

Answer: Go to the Lot Size tab, and select the Quantity and DateDetermination tabThe assembly scrap was set to 9.09%. This was due to the calculation thattakes place during the CIF transfer.

3. How was the goods receipt processing time value in SAP R/3 formattedin SAP SCM?

Answer: Go to the GR/GI tab.The GR processing time was set to 2.00 days. This was due to thecalculation that takes place during the CIF transfer.



Lesson Summary

You should now be able to:� Identify the dependencies created as a result of the integration between

the materials master in SAP R/3 and SAP SCM.� Transfer Material Masters from SAP R/3 to SAP SCM.


SCM210 Lesson: Resources in SAP SCM

Lesson: Resources in SAP SCM

Lesson OverviewIn this lesson, you will learn how to transfer master data objects from theSAP R/3 to the SAP SCM System as resources. The lesson discusses varioustypes of resource categories in SAP SCM and explains the process of definingcapacity variants in the SCM system.


� Identify how the SAP R/3 work center and resource will transfer to SAPSCM via the Core Interface.

� Review the results of a transferred resource from SAP R/3 to SAP SCMvia the Core Interface.

� Identify the modeling options for maintaining a resource after it has beentransferred to SAP SCM from SAP R/3.

Business ExampleAssume that in order to properly plan the manufacturing of the pumps atyour company, you will need to model the necessary resources. Therefore,you need to understand the SAP SCM options of modeling resources . Inaddition, you also need to understand the relationship between the SAP R/3work center/resource and the SAP SCM resource.

SCM Resource ComponentsResources are SAP R/3 and SAP SCM master data in which capacities andworking times of machines, personnel, means of transport, and storagefacilities are defined. The can represent a single constraint such as oneproduction line or multiple constraints such a group of production lineoperators.

In the definition of the SAP R/3, exists the capacity category. These capacitycategories define the available operating time of the work center/resource.Capacity categories can also exist as stand alone master data in SAP R/3. Forexample a group of line operators are not a constraint of one work centerbut possibly of many work centers.



Do to the sophistication of SAP SCM, the detail in which a resource is defineis more granular than that of SAP R/3. In SAP SCM each resource will bedefined relative to �categories�. The resource category determines the useof a resource.

Figure 65: Resource Categories

The resources transferred from SAP R/3 are basically production resources(resource category P).



In an SAP SCM System, capacity planning can also take place for otherresource categories, for example, storage. You must create these resourcesmanually in SAP SCM.

� Single-activity resources (PP/DS)� Single Mixed resources (PP/DS and SNP)� Multi-activity resources (PP/DS)� Multi-Mixed resources� Production Line (PP/DS - Discrete Solution)� Production Line-Mixed (PP/Ds and SNP Discrete Solution)� Bucket resources (SNP only)� Vehicle resources (TP/VS)� Transportation (4.0)/Shipment (3.1) - SNP only)� Calendar resources (PP/DS)� Calendar Mixed resources (PP/DS and SNP)

Single/Multi-Activity resourcesResources that can be used for continual and exact time scheduling (e.g tothe second). Therefore, in PP/DS you use either single-activity resourcesor multi-activity resources, for which you can define working times andbreaks and which you can schedule to the second. Only one activity canbe carried out at a time on a single-activity resource (capacity 1). Severalactivities can be carried out at the same time on a multi-activity resource.These types of production resources can be transferred from SAP R/3.

Mixed resourcesResource that can be used by both PP/DS and SNP. The capacity datafor each resource will bet stored both in Daily buckets so that it can beused by SNP In addition capacity will be store for PP/DS down to thesecond and allow planners to define the capacity in shifts as well. Thesecan be transferred from SAP R/3.



Bucket Resourcesusing a customer exit (see SAP Note 217210 �Mapping of AlternativeSequences in the SAP SCM System�) when transferring the PPM to SAPSCM. Note that alternatives should be chosen exclusively in SAP SCM.This is because SAP SCM plans capacities and has more comprehensiveoptimization capabilities at its disposal.

� Quantity (without reference to a period of time) For example, youcan use a quantity to define the transport capacity of a truck or thecapacity of a warehouse.

� Rate (quantity with reference to a period of time) You use a rate todescribe the consumption or production capacity of a resource, forinstance the quantity that is consumed or produced by a resourcein a workday.

Line ResourcesResource type that is specially designed for the requirements oftakt-based scheduling. The line resource determines the working timesand the rates of the line. A line resource is generated in SAP SCM foreach line you create in the DI system.

Vehicle ResourceResource that represents a separate resource type and is used inTransportation Planning/Vehicle Scheduling (TP/VS). The vehicleresource has the following features

� The vehicle resource can have several dimensions.� You assign a means of transport to the vehicle resource. You cannot

define the available capacity for this resource type dependent ontime.

� However, you can define a time-dependent availability using shiftsequences.

Transportation ResourcesThis resource used in Supply Network Planning that is identical to thebucket resource. It has its own resource type in SAP liveCache. Use Thetransportation resource is used in the same way as the bucket resource.It differs from the bucket resource in the scheduling of requirementson the resource.



Calendar ResourcesResource whose capacity is not utilized during scheduling. The systemonly takes the calendar of the resource into consideration duringscheduling. In contrast to single resources, the following constraints existfor calendar resources and calendar mixed resources:

� Since there is no capacity load for the calendar resource, it is notdisplayed in the Detailed Scheduling planning board.

� The capacity of a calendar resource is not taken into considerationduring scheduling of activities, so it cannot be scheduled finitely.

� You cannot define a capacity profile for a calendar resource. Youcan also specify downtimes for calendar resources.

� No setup time adjustment can be executed on a calendar resource.In the following cases, you define a resource as a calendar resource:

� You only want to take the resource calendar into consideration.� There are a lot of activities on the resource simultaneously; for

example, on a handling resource for scheduling the goods receiptprocessing time. If you use another resource type, the system hasto take the capacity into account when scheduling these activities,which may lead to performance problems.

As of PI2003.1 and SCM 4.0, changes were made to the way some of themaster data objects could be interfaced. Prior to this upgrade, companies whowanted SAP R/3 to create �mixed�resources in SAP SCM had to use a user exit



Figure 66: New Resource Integration SettingsFigure 66: New Resource Integration Settings

With this new functionality companies will be able to control how the initialtransfer and change transfer of the resources are handled. This replaces thatcustomer exit that was required before. Prior to PI2003.1 and SCM 4.0 alltransfers were handled through a periodic update or users maintained thedata solely in SAP SCM after the initial transfer. In transaction CFC9 there is aselection that users can now make to handle the changes transfer immediatelythrough a business transaction event (BTE -online transfer). In additionduring the initial transfer companies can decide what type of resource theexisting SAP R/3 work centers/resources will be transferred to SAP SCM as:

� 01 - Mulit-activity Resource� 02 - Single-Activity Resource� 04 - Single Mixed Resource� 05 - Mulit mixed Resource� 06 - Single Line Resource� 07 - Single Mixed Line Resource� 10 - Calendar Resource� 11 - Calendar Mixed Resource

This setting affects all resources, regardless of the target system. However,these settings can be defined separately for single and multi activity resources.



When users set up the change transfers process they have the opportunityto decide exactly how the resource will affect the version dependent andindependent resources. You can choose for which resources the changetransfer from SAP R/3 to SAP SCM should be activated or changed. You havethe following options:

� No change transfer (updates in SAP R/3 do not transfer)� Change transfer only for the planning-version-independent resource.� Change transfer for the planning-version-independent resource and for

the planning-version-specific copy of this resource that is assigned toplanning version 000. (Any new versions created will get the updatedcapacity.)

� Change transfer for the planning-version-independent resource and forall planning-version-specific copies of this resource that are assigned toa planning version of model 000.

Another new feature with PI2003.1 and SCM 4.0 is the use of ExternalCapacities. If you use SAP SCM with SAP R/3 (or another external OLTPsystem), SAP SCM can directly use the data defined in the external systemto calculate the available time-continuous capacity of single, multi, line, andcalendar resources as well as the relevant mixed types. If you assign thisexternal capacity to the resource, the system does not take any further settingsin SAP SCM into consideration that affect the capacity when determining thevalid capacity, except for downtimes and the variances defined in the capacity profile.

The capacity can only be specified in SAP R/3 without a dimension, sothe external capacity of multi-activity resources is also always without adimension. In the case of mixed resources, the system generates the bucketshare of the capacity from the external capacity, if you specify for the resourcethat the bucket capacity is generated from the time-continuous capacity.Using the external capacity setting in transaction CFC9, companies can definethe following options:

� Whether the capacity is not, in general, determined in SAP R/3� Whether the capacity for all resources that have been transferred from

this SAP R/3 system is determined externally in SAP R/3� Whether the capacity is only determined externally for the resources in

SAP SCM for which you have defined this explicitly in the master datain SAP SCM

If you choose to use SAP R/3 as the master for capacity your company canalso specify for how many days in the past the external capacity is generatedin SAP R/3. Enter at least as many days as you have specified in resource



master data in SAP SCM for the validity of the available capacity. If you donot specify a value, the external capacity is generated for 30 days in the pastand 600 days in the future.

Figure 67: External Capacities in SAP SCMFigure 67: External Capacities in SAP SCM

In SCM 4.0 a new tab has been added to the resource master called ExternalCapacity. If you have transferred the resource from a connected SAP R/3system through the CIF or from another system, you can use this indicatorto define that the data that the system uses to determine the capacity of theresource (shift definitions, shift programs and break models) is read directlyfrom this system. The CIF does not support any change transfer for shifts, shiftprograms and breaks. If you want to manage these settings in SAP R/3 (or inanother system connected using BAPIs), specify at the resource in SAP SCMthat the capacity is to be determined based on the external data in this system.

Note: If you have set this indicator, the system does not take theshifts, shift programs and breaks from the SAP SCM system intoconsideration. The bucket share of the capacity of a mixed resource canonly be determined from the external system if you have defined thatthe bucket capacity should be determined from the time-continuouscapacity.



Figure 68: Work Center and Resources

When an SAP R/3 work center is transferred to an SAP SCM, each capacitycategory is mapped to an individual resource. These resources areindependent of each other in an SAP SCM.

The resources in an SAP SCM must have unique names. The transfer takesplace according to the following naming convention: The name of the workcenter starts withW, followed by the plant were the work center is located,the work center name and then the capacity category.

SAP R/3 work center capacities are normally transferred as production typemulti- or single activity resources. Unlike mixed resources, these resourcescan only be used in PP/DS. This is due to the potential use of shifts and shiftsequences to define fluctuating capacity with a day or year.

Note: As of SCM 4.0 the user exit is not longer relevant. Due to changesin the Plug-in, users can now define in which manner resources aretransferred to SAP SCM. This setting can be made in transaction CFC9



Figure 69: Single and Multi-Activity Resources

Single activity resources can be used by only one operation, whereas inthe case of multi-activity-resources, several operations can be scheduledsimultaneously. In single activity resources, the system displays SAP R/3 workcenter capacities with only one individual capacity that cannot be used byseveral operations. Similarly, in multi-activity resources, the system displaysSAP R/3 work center capacities that either have more than one individualcapacity or that can be used by more than one operation.

Note: During the transfer of the SAP R/3 work center capacity, onlythe data from the standard available capacity is considered to selectsingle or multi-activity resource or copied. The system does nottransfer the available capacity intervals that differ from the standardavailable capacity.

An SAP R/3 work center capacity can have more than one individual capacitybut cannot be used by several operations. This case cannot be displayed in anSAP SCM in this form because this capacity is displayed on a multi-activityresource.

Set-up matrices can only be used with both single activity resources. In singleactivity resources, the setup matrixes will be used for variable/sequencedependent setups. The sequence dependent setup will depend upon the setupgroup in each operation of each PPM. In multi-activity resources, the systemuses Synchronization Start. When synchronizing (scheduling), the systemschedules the new activity either at the same start time as an activity with



the same duration and characteristic (which has already been scheduled)or, without overlap, before or afterwards. By synchronizing, you can createblocks of activities at the multi-resources that can be processed simultaneouslybecause they have the same duration and characteristic. You specify the valueof the characteristic by using a setup group or a setup key that you assign tothe operation in the production process model. For example, if modelingan oven, a scheduler wants all materials that have to be baked at the sametemperature.

Figure 70: Resource Data

During the transfer of an SAP R/3 work center, the system creates one SAPSCM resource for each capacity category. The corresponding resources adoptthe short text of the capacity. You can define the short text in the SAP SCMSystem in more than one language. If the SAP R/3 Enterprise work centercapacity does not have a short text, then the name of the work center issupplemented in the SAP SCM 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 (thecorresponding Customizing). Application Customizing cannot generallybe transferred through an integration model from an SAP R/3. (Exception:Plant, MRP area, ATP). Basis Customizing (factory calendar, units) can betransferred through the SAP transport system.



The system transfers the standard available capacity of the active capacityversion and the number of individual capacities. The system does notautomatically transfer intervals that vary from the standard available capacityand that you have defined in SAP R/3.

The system transfers the rate of resource utilization of the SAP R/3 capacity.The system does not transfer the field Overload, with which you can allow apercentage overload on a capacity in SAP R/3 , into the SAP SCM resource.The rate of resource utilization represents the corresponding function.

When you set the indicator Relevant for finite scheduling in the SAP R/3 capacity,the system activates the indicator Finite planning in the relevant SAP SCMresource during the transfer.

Figure 71: Reference Resource

In an SAP R/3 , a reference available capacity can be assigned to a work centercapacity. The system transfers the available capacity of the reference availablecapacity.

The transfer of a work center capacity containing a reference available capacityresults in two resources in SAP SCM. The system transfers the referenceavailable capacity as an individual resource, also called reference resource. Asa result, this resource name does not start withW. The system transfers thework center resource containing a copy of the capacity data of the referenceresource and the reference resource is assigned to it.



Defining Capacity ComponentsAs mentioned earlier, when transfer the SAP R/3 resource information, theCIF only passes the standard available capacity. If companies need modelcapacity that fluctuates within a day (labor pool) or throughout the course ofa yea (ramp up for seasonal demand), companies use intervals of availablecapacity SAP R/3. The intervals of available capacity in SAP R/3 are a mixtureof master data and customizing. In SAP SCM, intervals of available capacityare master data only.

To model different levels of capacity in SAP R/3 users can use versions.This is defined by using intervals of available capacity. In SAP SCM, todefine variations in capacity, users must define capacity variants. These areequivalent to SAP R/3 capacity versions. Capacity variants in SAP SCM canvery simple or more detailed relative to depicting events on the shop floor.Define a detailed capacity variant a user can follow the following five steps:

1. Create a Break Pattern2. Create Shift Factors3. Create Shift Definitions4. Create Shift Sequences5. Create Capacity Variants6.

Each step can be used in the subsequent steps depending upon the detailthe planner needs to obtain.

Figure 72: Defining Capacity Variants in SAP SCM (1)*



Break data consists of break pattern, break number, planner, start/end ofbreak, and break after hours/break duration.

The presentations contain additional information that does not directlyconcern the integration of master data. These presentations are intended asan appendix.

In a break pattern, you define breaks for a shift, independently of a particularshift. The breaks are valid independently of a particular shift. 0

You can define each break either by specifying a start and finish time or byentering the break duration and the start of the break in relation to the startof the shift.

You use a break pattern in a shift definition.


Shift factor data consists of shift factor definition, validity, planner, capacity,unit of measure, and resource utilization.

In a shift factor definition, you define the resource utilization and the capacityfor a shift, independent of a particular shift.

The capacity and the unit of measure for the capacity are only relevant formulti-activity resources. Single activity resources have capacity 1 without aunit of measurement.

You use a shift factor definition in a shift definition.




In a shift definition, you define the working times, breaks, resource utilization,and the capacity for a shift.

You use a shift factor definition to define the resource utilization and thecapacity 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 ofthe breaks for the shift.




In a shift sequence, you define the daily sequence of shifts for any numberof consecutive days.

For each day, you can specify up to nine shifts.

The shifts for one day can overlap but the shifts 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 capacityin a particular time interval of a capacity variant.




To define working times, break times, resource utilization, and capacity ina particular time interval of a capacity variant, you need to assign a shiftsequence to the time interval.

The First Day field specifies which day of the shift sequence falls on the firstday of the time interval.

TheWorkdays field specifies whether the days in the interval are workdays,non-workdays, or workdays according to the factory calendar.



Figure 77: Capacity Definitions in SAP SCM: Overview*

To define working times, break times, resource utilization, and capacity ina particular time interval of a capacity variant, you need to assign a shiftsequence to the time interval.

To define shift sequences, you use:

� Break patterns� Shift factor definitions� Shift definitions



Figure 78: Pooled Capacities

The system can transfer to SAP SCM pooled capacities that are assigned tothe SAP R/3 work center. The system not only transfers the individual workcenter capacities to which the pooled capacity is assigned but also transfersthe pooled capacity itself.

The system transfers the pooled capacities similar to transferring normalresources the available capacity is also transferred, except that the resourcename starts with W.





Exercise 5: Displaying a resource in SAPSCM

Exercise ObjectivesAfter completing this exercise, you will be able to:� Display a resource in SAP SCM� Describe the result of the transfer of an SAP R/3 work center to the SAP

SCM resource

Business ExampleAs a planning manager, you need to transfer your work centers data to acentralized SAP SCM System for detailed planning. While transferring thedata, you need to ensure that the SAP R/3 work center is transferred from theSAP R/3 Enterprise to the SAP SCM system as a resource.

Task:1. Work center T-L## in plant 1000 is required to produce the pumps.

Display the work center in R/3.

2. What is the name of this work center?

3. Which two capacities (with which capacity categories) are defined forthis work center?

Which capacity is relevant for scheduling?

4. Display more detailed data for the capacity with capacity category 001(machine). Which standard available capacity is defined for this capacity?

5. Which result do you expect when you see the result of the transfer ofwork center T-L## into SAP SCM? . To answer this question, considerthe results for question 3. How many SAP SCM resources are relevant tothe work center? Is capacity category 001 mapped onto a single-activityresource or a multi-activity resource? Why? Work center T-L## istransferred to SAP SCM in the form of two resources.

6. What are the names of the SAP SCM resources that result from the CIFtransfer of the SAP R/3 work center T-L## of plant 1000?




7. The capacities of the SAP R/3 work center T-L## of plant 1000 weretransferred to the training system asmixed resources using a customerexit. Both the machine capacity (capacity category 001) as well as thelabor capacity (capacity category 002) were transferred as single-activityresources.

8. Display the SAP SCM resourcesWT-L##* in location 1000. Look at thesingle mixed resources: Does one of these resources represent the R/3work center T-L## in plant 1000?

9. Displayed more detailed information for resourceWT-L##_1000_001:What is the name of this resource? Which standard capacity is defined?Is this resource scheduled finitely in SAP SCM?



Solution 5: Displaying a resource in SAPSCMTask:1. Work center T-L## in plant 1000 is required to produce the pumps.

Display the work center in R/3.

a) In the SAP R/3 Enterprise, select Logistics → Production → MasterData → Work Centers → Work Center → Display .

2. What is the name of this work center?

a) Name of the work center: Paint shop.

3. Which two capacities (with which capacity categories) are defined forthis work center?

Which capacity is relevant for scheduling?

a) Capacities assigned to work center: Machine (capacity category001) and Labor (capacity category 002).

4. Display more detailed data for the capacity with capacity category 001(machine). Which standard available capacity is defined for this capacity?

a) Standard available capacity: Work time from 7:00h to 15:00h, with aone hour break Number of individual capacities: One

No, the capacity cannot be used by several operations.

Yes, the capacity is relevant to finite scheduling.

5. Which result do you expect when you see the result of the transfer ofwork center T-L## into SAP SCM? . To answer this question, considerthe results for question 3. How many SAP SCM resources are relevant tothe work center? Is capacity category 001 mapped onto a single-activityresource or a multi-activity resource? Why? Work center T-L## istransferred to SAP SCM in the form of two resources.

a) Capacity category 001 is to be represented at a single-activityresource as the number of individual capacities is one and thecapacity cannot be used by several operations.




6. What are the names of the SAP SCM resources that result from the CIFtransfer of the SAP R/3 work center T-L## of plant 1000?

a) Names of the SAP SCM resources corresponding to work centerT-L##: WT-L##_1000_001 or WT-L##_1000_002.

7. The capacities of the SAP R/3 work center T-L## of plant 1000 weretransferred to the training system asmixed resources using a customerexit. Both the machine capacity (capacity category 001) as well as thelabor capacity (capacity category 002) were transferred as single-activityresources.

a) In the SAP SCM system, select Advance Planning and Optimization→ Master Data → Resource .

8. Display the SAP SCM resourcesWT-L##* in location 1000. Look at thesingle mixed resources: Does one of these resources represent the R/3work center T-L## in plant 1000?

a) Yes, the resources WT-L##_1000_001 or WT-L##_1000_002 aredisplayed as single mixed resources in SAP SCM.

9. Displayed more detailed information for resourceWT-L##_1000_001:What is the name of this resource? Which standard capacity is defined?Is this resource scheduled finitely in SAP SCM?

a) Name of resource WT-L##_1000_001: Machine capacity paint shop.

Standard available capacity: Just as in SAP R/3, a work time from7:00h to 15:00h, with a one hour break

Yes, the resource is scheduled finitely (as a result of theRelevant tofinite scheduling indicator that is set in the SAP R/3 work center).



Lesson Summary

You should now be able to:� Identify how the SAP R/3 work center and resource will transfer to SAP



transferred to SAP SCM from SAP R/3.



Lesson: Production Process Models (PPM)

Lesson OverviewIn this lesson, you will learn how to transfer master data objects from SAP R/3to the SAP SCM System as a Production Process Model (PPM). The lessonexplains the structure of PPM and the process of transferring scheduling andactivity operations from SAP R/3 to the SAP SCM System.


� Identify the dependencies between the SAP R/3 production version, andthe SAP SCM production process models.

� Transfer a production version from SAP R/3 to SAP SCM via the CoreInterface.

� Identify the limitations of the PPM when modeling a manufacturingprocess in SAP SCM.

Business ExampleYour company manufactures several different models of pumps. In order toproperly prepare a manufacturing schedule, you need to properly model therequirements. These requirements will involve the necessary assemblies orraw materials as well as the manufacturing set-ups and relevant resources toproduce the end product. By using an existing Bill of Material and Routing inyour SAP R/3 system, you will transfer the production version to SAP SCMvia the Core Interface in order to generate an SAP SCM PPM.

Mapping PPMsA production process model (PPM) describes when a �plan�can be used tomanufacture a product. A plan consists of specific bill of material and tasklist or routing that matches the specified BOM. A plan then consists of oneor more PPMs, which identify output products from the process. A locationand lot-size interval are defined as validity criteria. The temporal validityis adopted from the output product.


SCM210 Lesson: Production Process Models (PPM)

Figure 79: Alternatives to PPM in SAP SCM

In addition to the PPM, there are alternative data structures available in SAPSCM for PP/DS. These data structures are then interesting if the technicalrestrictions of the PPM (no Engineering Change Management, no variants)aggravate the use of SAP SCM. With the Plan explosion indicator in theSAP SCM product master, you can determine which data objects the orderexplosion in an SAP SCM is based on. This setting can also be made in theSAP SCM IMG under Global Settings for PP/DS

The integrated Product and Process Engineering (iPPE) is not currentlyincluded in the SAP R/3 standard. SAP SCM 3.1 contains the iPPE but it canonly be transferred from one SAP R/3 -DI system.

The iPPE runtime object (iPPE-LZO) is a data structure generated from theiPPE. This object serves order explosion in SAP SCM because direct explosionof the iPPE would be expensive for each individual order. Alternatively, thisruntime object can be generated in SAP SCM, such as a PPM, through the CIFinterface from the SAP R/3 routing and BOM and used for order explosion.



If phantom assemblies are included in the BOM, they must be selectedseparately in the integration model as material BOMs when using theiPPE-RTO. Unlike the PPM, phantom assemblies are not exploded in theruntime object. As a result, you need to have one BOM for each phantomassembly.

Note: After SCM 4.1 PPMs will no longer be enhanced. The RTO orwhat will now be know as the Production Data Structure (PDS) willbe the master data object that will support integration with the BOMand Routing in SAP R/3.

Figure 80: SAP R/3 Enterprise Production Version and SAP SCM-PPM

To transfer the routing and Bill of Material (BOM) as a PPM to SAP SCM,a valid production version must be available in the material master of thecorresponding material. The production version determines a manufacturingprocess by specifying a routing and a BOM. These production versionsare valid based on date effectivity and lot size effectivity. In addition thealternative selection indicators 2 and 3 must also be set in the SAP R/3 materialmaster. Select according to production version.



Figure 81: Production Version Selection CriteriaFigure 81: Production Version Selection Criteria

When generating the integration model, users must identify how the PPMswill be chosen. This is related to the effectivity dates on the productionversion, which will carry over to the header of the PPM. An exact control ofthe explosion is possible; one of the following cases can be selected:

� 0 Explosion on selection date in the integration model

� 1 Explosion according to time of transfer� 2 Explosion according to start date of the production version� 3 Explosion according to end date of the production version.

The selection date is only relevant for case 0.

Due to the fact the PPM currently (SCM 4.0) does not support EngineeringChange Management (ECM), users will typically create several productionversions. The effectivity of the production version will typically mimic theeffectivity Parameters of the ECM changes for the BOM or task list.



Figure 82: Plan Number Description in SAP SCM

A PPM corresponds with the assignment of a product to a plan. A plan can beassigned to several products and can contain several PPMs.

Note: A plan number can only support multiple PPMs in the case ofco-product or by-product. This means that regardless of the desiredoutput product the input products are still the same. Quantities mayvary, but not the components.

In the SAP R/3 material master, several production versions can be defined fordifferent lot size intervals. Each of these production versions is transferredto SAP SCM as an individual plan and PPM. The individual plans differ bythe group counter.

The PPMs that are transferred from an SAP R/3 have usage P. The PPMs canbe used in an SAP SCM for PP/DS. If the plans are also used for SNP, theyneed to be copied as PPMs with usage S. A special report is available in SAPSCM for this.

Note: An SNP PPM or DP BOM generated from a PP/DS PPM are notupdated based on SAP R/3 changes. These options will be available ina later release with the use of RTO/PDS.



When a plan or a PPM is created in an SAP SCM as a transfer of a routing/BOMfrom an SAP R/3 production version, the origin is a derivation of the plannumber. The plan number in SAP SCM is composed of the routing numberof the SAP R/3 , the group counter, and the production version number (e.g0001). The routing number is represented by a number that specifies therouting type - for example, N stands for normal routing, R for rate routing,and 2 for a master recipe (process industry). The system transfers referenceoperation sets in routings similar to transferring normal routings.

The system transfers a description of the routing to SAP SCM as the plan textand the brief description of the production version as the PPM text.

If one routing is used in several production versions, the plan number in SAPSCM includes the material number and plant. For example, for material A inplant 1000, the plan number is N500077010001A1000.

The system only transfers the production versions that are valid at the time ofselection in the integration model.

Figure 83: Structure of the Production Process Model (1)

A PPM contains one or more operations. You can define the short texts of thePPM operations in different languages. Each operation includes at least oneactivity, such as produce, setup, tear down,or wait). The components consumedor produced by the activity are assigned to the activities. The sequence ofactivities within the operation is defined by the relationships. The sequenceof the individual activities in SAP SCM-PPM is generally displayed with



activity relationships, also cross-operation. A normal consecutive sequenceof activities, for example, Setup � Process � Tear down, is determined byrelevant finish-start relationships. The transfer of SAP R/3 master data canresult in two types of relationships, finish-start relationships, where the end ofone activity starts another and start-start relationships, where two activitiesstart at the same time.

Note: As of SCM 4.0 �Overlapping or Continuous�operations aresupported in the SAP SCM PPM as start-start relationships orfinish.-finish relationships.

Only those operations who have control keys set for scheduling, and whosework center is in an active integration model is sent to SAP SCM.

During a CIF transfer of an SAP R/3 operation to an SAP SCM activity, notethat only the scheduling formulae are interpreted. In other words, the SAPSCM capacity requirements basically result from the SAP R/3 schedulingformula. The number of splits that can exist in the SAP R/3 scheduling formulasis not considered in SAP SCM . Currently, splits are not generally supportedin SAP SCM.

Figure 84: Structure of the Production Process Model (2)

Attached to each activity will be one or more modes in which the productionmight be executed. The mode determines the resource and the capacityrequirement needed to execute an activity. In addition to the primary resource



that is relevant for scheduling, you can enter one or more secondary resourcesin a mode. The system also creates capacity requirements for the dependentresources during scheduling.

Several modes can be assigned to one activity, that is, several alternativeresources can be assigned and the activity can be processed. Duringscheduling in PP/DS, the system automatically selects a mode. The modeselected starts latest if you take the available capacity into consideration.

You can prioritize particular modes that you use for optimization in PP/DS.

Note: Number of operations in alternative sequence < number ofoperations in standard sequence

In principle, alternative sequences can be represented as alternativemodes in SAP SCM. For the display of alternative sequences, youhave to distinguish between different business backgrounds: If thealternative sequences in SAP R/3 are chosen dependent upon lot size(for example, because above a certain lot size an alternative resourceis more economical), you have to create in SAP R/3 a productionversion for each alternative sequence that is dependent on lot size.SAP SCM cannot carry out lot-size-dependent mode selection whenusing the PPM. In this way, you can carry out planning for the correctresources in SAP SCM. If the planning of alternative resources is notimportant, you can ignore this procedure and carry out a sequenceexchange in the SAP R/3 manufacturing order. In the associated SAPSCM manufacturing order, this leads to the deletion of the exchangedoperations in the standard sequence and to the addition of theexchanged operations to the alternative sequence. If the alternativesequence represents an alternative as regards capacity, you can showthese alternative sequences as alternative modes in SAP SCM. Forthis, there are three different cases:

� Number of operations in alternative sequence = number ofoperations in standard sequence

� Number of operations in alternative sequence < number ofoperations in standard sequence

� Number of operations in alternative sequence > number ofoperations in standard sequence



Using a customer exit (see SAP Note 217210 �Mapping of AlternativeSequences in the SAP SCM System�) when transferring the PPM to SAP SCM.Note that alternatives should be chosen exclusively in SAP SCM. This isbecause SAP SCM plans capacities and has more comprehensive optimizationcapabilities at its disposal.

Figure 85: Operations in PPM

The operations in an SAP R/3 routing correspond with operations in an SAPSCM PPM. The system transfers all the SAP R/3 operations that are relevantto scheduling and have a corresponding control key. The system does nottransfer operations that are not relevant to scheduling.

The system does not transfer operations if there is no work center in theSAP R/3 Enterprise operation and active integration model and if there areno scheduling results unequal to zero (partly because there are formulae orstandard values missing).

The operation numbers remain during the transfer.

The system transfers SAP R/3 sub-operations as SAP SCM operations.

The system transfers parallel sequences of an SAP R/3 routing to an SAP SCM.The system then creates the corresponding operations and provides themwith relationships so that they operate as parallel sequences. (Start-startrelationship).



Figure 86: Scheduling and Activities

The operations of a PPM include activities where you will find a descriptionof the actual process steps for the operation. During the transfer of SAP R/3task list, the system creates the activities of the SAP SCM PPM operationrelevant to the SAP R/3 operation.

A work center is assigned to an SAP R/3 operation. The work center specifieswhich time elements can be taken into consideration during scheduling usinga standard value key, for example, setup time, machine time, or personneltime. The scheduling formulae stored in the work center define the durationfrom the allowed time elements in the routing.

The set up, processing, and tear down of an SAP R/3 operation are displayedin SAP SCM as activities. During the CIF transfer of a routing, the schedulingformulae of the relevant work center are also interpreted to create thecorresponding 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 workcenter as a scheduling basis. Other possible available capacities that are notrelevant for scheduling are displayed using secondary resources.

The capacity requirements of the individual process steps result from thescheduling formulae defined in the work center and the time elements ofthe routing. The system stores them in an SAP SCM PPM as variable orfixed durations. The variable durations relate to the output quantity of the



last operation of PPM that is derived from the base quantity of the SAP R/3BOM. The durations are specified in the SAP SCM activity in the base unit ofmeasure of the SAP R/3 capacity relevant for scheduling (shown in Hour (H)in the graphic).

Figure 87: Overview of Activity Relationships

There are two types of activity relationships:

1. Start-start relationship: The start times of two activities are correlatedwith each other.

2. Finish-start relationship: The end of one activity is linked with the startof the next activity.



Figure 88: Activity Relationships

The activities of an SAP R/3 operation, setup, process, and tear down aretransferred in this order to the SAP SCM PPM. The activity relationshipsdefine the order of the SAP SCM activities. During the CIF transfer of the SAPR/3 operation, the system creates these activity relationships automatically, aspreceding and subsequent relationships within an operation.

The operation number determines the sequence of the individual operationsof an SAP R/3 routing. A corresponding activity relationship between thelast activity of one operation and the first activity of the following operationdefines this sequence in SAP SCM PPM.

Available wait or move times that determine the time interval of the follow-upoperation in the SAP R/3 operation are divided between two PPM operationsin the activity relationship: The sum of the minimum wait time and theminimum move time is transferred as the minimum duration. The maximumwait time of the SAP R/3 operation is not relevant for scheduling and is nottransferred to SAP SCM.

The SAP R/3 sub-operations are transferred as SAP SCM operations withthe activity produce. Because SAP R/3 sub-operations are not relevant forscheduling, the dates of the operations are determined according to thelower-level operation they are assigned to. The sub-operation activity islinked to a start-start relationship at the start of the operation. Relevant forscheduling is the original main operation in an SAP SCM.



Figure 89: Component Assignment in the PPM

In SAP R/3 , the BOM components in the routing can be assigned to individualoperations. This assignment of components is transferred to an SAP SCM: Thecomponent assignment is displayed by input components in activities. Thecomponents are assigned to the first activity of the relevant operation, whichif you have both production and setup in a particular operation the items willbe attached to setup. However, if you use a distribution key in the bill ofmaterial for a particular component, the CIF will assign the component to theactivity with a variable duration, usually produce.

Note: As of PI2002.2 and now SAP R/3 4.7, you can specify in R/3which individual operation segment to use as a basis for requirementsdata of allocated components. Previously it was linked to the startof the operation. You can choose between the segments setup,processing and tear down. The assignments then applies to allplanned or production orders created for that particular plant/ordertype/production controller.

Note: This function does not apply to by-products or co-products.



Caution: After changing this parameter, you need tore-transfer/reactivate the PPM�s in Question if you have existing,active, integration models .

The result of production, the finished product, is marked in SAP SCM as anoutput component. This output component is assigned to activity produce(P) in the last operation of PPM (if activity P does not exist, then the activityis assigned to setup).

The system only transfers the component assignment for materials containedin an active integration model. Direct procurement items are transferred asstock items.

If materials are assigned to an operation in SAP R/3 that is not transferred toSAP SCM, the materials are assigned to the first operation in the SAP SCMPPM or, more precisely, to the first activity of the first operation.

� The indicator Tear down/parallel wait time in the SAP R/3 operation canbe transferred

� Corresponding relationships in SAP SCM� You can transfer the operation-related lead-time offset of the SAP R/3

BOM item� Time-based offset of logical input components in PPM� Subcontracting PPM can be transferred (external procurement)� No manual maintenance of subcontracting PPMs in SAP SCM necessary

The system can transfer the indicator Tear down/parallel wait time in the SAPR/3 Enterprise operation to an SAP SCM as corresponding relationships (seenote 321956 for details).

You can transfer the operation-related lead-time offset of the SAP R/3Enterprise BOM item as a time-based offset of logical input components inPPM.

Subcontracting PPMs can be transferred through CIF to the source locationin an SAP SCM. Assign the production version to an info record in SAPR/3 Enterprise and select the Subcontracting PPM object accordingly in theintegration model. In addition to generating the PPM, the CIF can generateproduct masters for the header and item components at the subcontractorlocation. For more details see note565024 for details about transferring thePPM and note 483358 for generating product masters via the PPM.



PPM LimitationsIn SAP SCM production process models do not have variants. This meansthat they do not support the standard variant configuration model in SAPR/3. Variant configuration is now supported with the Run Time Object(RTO)/Production Data Structure (PDS). As of APO 3.1 this was not astandard practice and needed notes applied. As of SCM 4.0 the RTO/PDS issupported standard with the CIF. Additionally the PPM does not support anychanges made through engineering change management. As mentioned earlier,customers can use multiple production versions and their effectivity dates tocreate multiple PPMs that reflect the ECM updates.

Note: Alternative models for the integration of BOMs and routingsare therefore currently being developed: the iPPE runtime object (iPPE= integrated Product and Process Engineering). Note the iPPE is not�fully �integrated with core SAP R/3. The iPPE was developed for theDiscrete (Automotive) industry solution.

Lastly, the PPM does not support phantom bills of material. Through theCIF, the multilevel BOM will be flattened automatically, as most phantomsare not relevant for planning.

The Runtime object (RTO) offers the following functions:

1. Engineering Change Management is included in the iPPE RTO.2. Variants: you can use variants and configurable sales orders can be

processed.3. Dummy BOMs: you can use dummies. Dummy BOMs can be

additionally selected as BOMs in the integration model.



Exercise 6: Transferring a productionprocess model to SAP SCM

Exercise ObjectivesAfter completing this exercise, you will be able to:� Transfer a production process model to SAP SCM� Describe the result of the transfer of a production version with BOM and

routing to the SAP SCM System

Business ExampleThe Precision Petrol Pump company constitutes a number of independentbusiness units located in different parts of the world. Each unit is headedby a business unit head and operates as an independent entity under thecommon parent company. Currently, the data is maintained in a decentralizedpattern. As a planning manager, you need to transfer this data to a centralizedSAP SCM System for detailed planning. While transferring data, you need toensure that SAP R/3 routing and bill of material is transferred from The SAPR/3 Enterprise to the SAP SCM system as production process model.

Task 1: Create Production VersionAs the production planner responsible for Pump T-F1##, you must ensure thatyour data in SAP SCM is modeled correctly. In order to create a PPM in SAPSCM, you must have a valid production version to select the matching bill ofmaterial and routing. Create a production versions for the material T-F1## inplant 1000 in preparation for transfer to SAP SCM.

1. The subsequent transfer of the task list and Bill of Material (BOM) to theSAP SCM System assumes that a valid production version exists in SAPR/3 . Therefore, create a production version for material T-F1## at plant1000. In the MRP 4 view, enter a new production version 0001 with thename Normal production, which should be valid from today until theend of next year. Enter the following data:

Lot size: from 1 piece to 999,999 pieces

Task list: In the detailed planning row, transfer the Routing, that yousearch for (and find) with the F4 Help, from the planning group fieldusing material T-F1##.

Bill of material: Enter the alternative BOM 1 from BOM usage 1.Continued on next page



You exit the production version maintenance by pressing the button

Continue twice, then save the material master.

2. In the change mode, look at the SAP R/3 routing for the production ofmaterial T-F1## in plant 1000.

3. Which operations are required for production? Describe the operations.

Operation Description:Operation 10:

Operation 20

Operation 30Operation 40:

Operation 50:

Operation 60:

4. Which components are used to produce this material (see the componentassignment in the routing to answer this question)?

5. Assign component T-B1## to operation 40.

Task 2: Create PPM in SAP SCM via the CIFAs the production planner responsible for Pump T-F1##, you must ensure thatyour data in SAP SCM is modeled correctly. Now that you have reviewedthe relevant SAP R/3 data and created a valid production version, you needto create the PPM via the CIF. Upon successfully transferring the productionversion review the details of the PPM in SAP SCM.

1. In the following, create an integration model to transfer the routing andBOM to SAP SCM for material T-F1## at Plant 1000, as a productionprocess model (PPM). Use the general selection options for materials, enterthe material T-F1## in plant 1000Generate an integration model withfollowing setting




Field Data

Model Name PUMP##


APO Application PPM T-F1##

Hint: Do not execute the integration model yet!

2. Save your settings as the PPM T-F1## group ## PPM variant.

3. Generate the integration model. Ensure that the integration modelselected your production version 0001 for material T-F1##.

Hint: To transfer the master data to the SAP SCM System, youmust activate the integration model. To provide a better overview,the instructor will activate all your models.

4. The instructor activates your integration models.

Task 3: PPMs in SAP SCMAs a result of creating and activating your integration models to handleyour BOMs and Routings, we will now explore the result of the Transfer.In SAP SCM, the result with be the Production Process Model or PPM. Inorder to better understand the new data object we will explore the PPM andunderstand how it is built from the BOM and Routing.

1. Review the new PP/DS PPM that was generated via the CIF for T-F1## atplant 1000.

2. What are the Plan numbers that the CIF generated for your PPMs?

3. What is the lot size validity and PPM name for this PPM?




4. How many Operations Does your PPM contain?

5. How many activities does your PPM contain for you operation 0040Insert hollow shaft in Casing?

6. How many materials are contained in your in PPM versus the SAP R/3BOM?

7. Using work area on the right drill down to see what components areallocated to the production activity for operation 0010 Material staging bypicking and fill in the follow table with the results. Double click on the

operation or select Select row

, then select the production activity and select Select rowDrill into the logical components to get the quantities. Select Return to

activity to get back to the activity details screen.

Short Text I/O indicator Consumption type Variable Qty




8. Using work area on the right drill down to see what components areallocated to the production activity for operation 0040 Insert hollow shaftin casing and fill in the follow table with the results. Double click on the





9. How many modes does the produce activity use at operation 0040 Inserthollow shaft in casing, and what is the duration of this activity?

10. Does this Activity utilize any other resources during manufacturing?

11. Using work area on the right drill down to see what components areallocated to the production activity for operation 0060 Deliver to stock andfill in the follow table with the results. Double click on the operation or

select Select row






Solution 6: Transferring a productionprocess model to SAP SCMTask 1: Create Production VersionAs the production planner responsible for Pump T-F1##, you must ensure thatyour data in SAP SCM is modeled correctly. In order to create a PPM in SAPSCM, you must have a valid production version to select the matching bill ofmaterial and routing. Create a production versions for the material T-F1## inplant 1000 in preparation for transfer to SAP SCM.

1. The subsequent transfer of the task list and Bill of Material (BOM) to theSAP SCM System assumes that a valid production version exists in SAPR/3 . Therefore, create a production version for material T-F1## at plant1000. In the MRP 4 view, enter a new production version 0001 with thename Normal production, which should be valid from today until theend of next year. Enter the following data:

Lot size: from 1 piece to 999,999 pieces

Task list: In the detailed planning row, transfer the Routing, that yousearch for (and find) with the F4 Help, from the planning group fieldusing material T-F1##.

Bill of material: Enter the alternative BOM 1 from BOM usage 1.

You exit the production version maintenance by pressing the button




Continue twice, then save the material master.

a) Menu path in the SAP R/3 : Logistics→ Production→Master Data→Material Master→Material→ Change→ Immediately. (MM02)

b) Enter Material number T-F1##, and pressENTER.c) SelectMRP 4 view, and press ENTER.d) Enter Plant 1000, and press ENTER.e) Proceed to theMRP 4 view and select the Production versions push

button.f) Enter a new production version 0001 with the name Normal

production, which should be valid from today until the end of nextyear and select Details.

g) Enter a Lot size: from 1 piece to 999,999 piecesh) Enter in the detailed planning row, select Routing as your task list

type and , with the F4 Help (search by material), from the planninggroup field using material T-F1##, select your Routing groupnumber (e.g. 50000324)

i) Enter the alternative BOM 1 from BOM usage 1.j) Select Continue TWICEk) Select SAVE

2. In the change mode, look at the SAP R/3 routing for the production ofmaterial T-F1## in plant 1000.

a) SAP R/3 menu path: Logistics → Production → Master Data →Routings→ Routings→ Standard Routings→ Change (CA02).

b) Enter material T-F1## and plant 1000 and select Operation Overview

3. Which operations are required for production? Describe the operations.

Operation Description:Operation 10: Material staging by picking listOperation 20 Press fly wheel in casingOperation 30 Paint casingOperation 40: Insert hollow shaft in casingOperation 50: Final assembly of pumpOperation 60: Deliver to stock




4. Which components are used to produce this material (see the componentassignment in the routing to answer this question)?

a) From the operations overview screen select Comp. alloc.- gen. pushbutton.

b) The components, T-B1##, T-B2##, T-B3##, T-B4##, and screw T-T3##,are used in production. A document item is also available.

5. Assign component T-B1## to operation 40.

a) From the material Component overview screen, select the line forT-B1## and select New Assignment

b) Select Oper./act. listc) Select Seq 0, operation 0040, Insert hollow shaft in casing

d) Select ENTERe) Select SAVE

Task 2: Create PPM in SAP SCM via the CIFAs the production planner responsible for Pump T-F1##, you must ensure thatyour data in SAP SCM is modeled correctly. Now that you have reviewedthe relevant SAP R/3 data and created a valid production version, you needto create the PPM via the CIF. Upon successfully transferring the productionversion review the details of the PPM in SAP SCM.

1. In the following, create an integration model to transfer the routing andBOM to SAP SCM for material T-F1## at Plant 1000, as a productionprocess model (PPM). Use the general selection options for materials, enterthe material T-F1## in plant 1000Generate an integration model withfollowing setting

Field Data

Model Name PUMP##


APO Application PPM T-F1##

Hint: Do not execute the integration model yet!

a) SAP R/3 Menu path: Logistics → Central Functions → SupplyChain Planning Interface → Core Interface Advanced Planner andOptimizer → Integration Model → Generate → Create .




2. Save your settings as the PPM T-F1## group ## PPM variant.

a) Select SAVE.b) Enter PPM T-F1## and the description Group ## PPMc) Select SAVE.

3. Generate the integration model. Ensure that the integration modelselected your production version 0001 for material T-F1##.

Hint: To transfer the master data to the SAP SCM System, youmust activate the integration model. To provide a better overview,the instructor will activate all your models.

a) Select Execute.b) Select the filter object Production Process Model and select Detail view.c) Select BACKd) Select SAVE.

Hint: Only when the message �Integration model PUMP##generated for target system APOCLNT8XX and applicationPPM T-F1## � appears have you successfully generated andintegration model:

4. The instructor activates your integration models.

a)




Task 3: PPMs in SAP SCMAs a result of creating and activating your integration models to handleyour BOMs and Routings, we will now explore the result of the Transfer.In SAP SCM, the result with be the Production Process Model or PPM. Inorder to better understand the new data object we will explore the PPM andunderstand how it is built from the BOM and Routing.

1. Review the new PP/DS PPM that was generated via the CIF for T-F1## atplant 1000.

a) SAP SCM menu path:Advanced Planning and Optimization→MasterData→ Production Process Model→ Production Process Model

b) From the Choose plan screen, select Choose plan through PPM, Enteryou product T-F1##, plant 1000, and use of Plan P (PPM Productionplanning detailed scheduling). Select the First plan number thatshould contain 0001.

c) Select Change

2. What are the Plan numbers that the CIF generated for your PPMs?

Answer: The Plan number should look something like: N50000324010001.N - Standard Routing, 50000324 - Routing Group number, 01 - Groupcounter, 0001 - Production version.

3. What is the lot size validity and PPM name for this PPM?

a) From the plan header segment select Product plan assignmentb) The PPM is called something similar to T-F1##

1000000100000000N5000032401011. Your lot size is validfrom 1 to 999,999,999

4. How many Operations Does your PPM contain?

Answer: From within the window at the top left, drill down under theheading Operations. As a result of the simplified modeling of your highspeed filler, you should have six operations:0010 - Material staging by picking0020 - Press fly wheel in casing0030 - Paint casing0040 - Insert hollow shaft in casing0050 - Final assembly of pump0060 - Deliver to stock




5. How many activities does your PPM contain for you operation 0040Insert hollow shaft in Casing?

Answer: From the top left window continue to drill down under theoperation 0040 -Insert hollow Shaft in Casing. Based on the SAP R/3routing, your PPM should contain two activities P -Production and S- Setup

6. How many materials are contained in your in PPM versus the SAP R/3BOM?

Answer: In the top left window, choose the tab labeled Products. As aresult of the transfer, you should have four materials T-F1##,T-B1##,T-B3##, and T-B4## . T-T3## was left off because it was not included inan active integration model for SAP SCM.

7. Using work area on the right drill down to see what components areallocated to the production activity for operation 0010 Material staging bypicking and fill in the follow table with the results. Double click on the


, then select the production activity and select Select row

Drill into the logical components to get the quantities. Select Return to


Short Text I/O indicator Consumption type Variable QtyT-B3## I - Input S - Start of Activity 1 pc

T-B4## I -Input S - Start of Activity 1 pc

8. Using work area on the right drill down to see what components areallocated to the production activity for operation 0040 Insert hollow shaftin casing and fill in the follow table with the results. Double click on the








Short Text I/O indicator Consumption type Variable QtyT-B1## I - Input S - Start of Activity 1 pc

9. How many modes does the produce activity use at operation 0040 Inserthollow shaft in casing, and what is the duration of this activity?

a) Choose the Mode tab.b) The activity only has one resourceWT-E##_1000_001and has a

duration of .083 hours.

10. Does this Activity utilize any other resources during manufacturing?

a) Double click on the mode or select Select row .b) It is using the pooled resourceWT-E##_1000_002. This resource

is a multi-mixed resource and represents the labor pool requiredto staff the Painting equipment.

11. Using work area on the right drill down to see what components areallocated to the production activity for operation 0060 Deliver to stock andfill in the follow table with the results. Double click on the operation or

select Select row




Short Text I/O indicator Consumption type Variable QtyT-F1## O - Output E - End of Activity 1 pc



Lesson Summary

You should now be able to:� Identify the dependencies between the SAP R/3 production version, and

the SAP SCM production process models.� Transfer a production version from SAP R/3 to SAP SCM via the Core

Interface.� Identify the limitations of the PPM when modeling a manufacturing

process in SAP SCM.



Lesson: Run Time Objects (RTO)/ Production DataStructure (PDS)

Lesson OverviewIn this lesson, you will learn how to transfer master data objects from SAPR/3 to the SAP SCM System as a Run Time Object (RTO)/Production DataStructure (PDS). The lesson explains the structure of the RTO and the processof transferring scheduling and activity operations from SAP R/3 to the SAPSCM System.


� Identify the dependencies between SAP R/3 production version, andSAP SCM Run Time Objects (RTO).

�

Business ExampleYour company manufacturers several different models of pumps. In order toproperly prepare a manufacturing schedule, you need to properly model therequirements. These requirements will involve the necessary assemblies orraw materials as well as the manufacturing set-ups and relevant resources toproduce the end product. One particular material however, undergoes severalengineering changes in the course of a year. Using an existing Bill of Materialand Routing in your SAP R/3 system, you will transfer the production versionto SAP SCM via the Core Interface in order to Generate an SAP SCM RTOand review the results.

Run Time Objects (RTO) in SAP SCMIn some industries modeling the production and evolution of a certainproducts can be very complicated. When a customer had a product that hadmany variations due to customers choosing a combination of features andoptions they typically used the variant configuration solution in standard SAPR/3 or the Integrated Production and Process Engineer (iPPE) which is partof the SAP Discrete Industry Solution for SAP R/3. An example would be acar manufacturer who has three distinct models but customers can choose anumber of options from the exterior paint color to the type of transmission.Another complicated scenario in manufacturing is modeling changes to an


SCM210 Lesson: Run Time Objects (RTO)/ Production Data Structure (PDS)

existing product and ensuring that the changes are captured properly duringplanning and manufacturing. Customers using SAP R/3 were using theEngineering Change Management (ECM) functionality to model the necessarychanges to the SAP R/3 BOMs , Routings, and Master Recipes.

Since the Release of SAP SCM, SAP initially developed the Production ProcessModel (PPM) to model manufacturing master data. However, while the PPMdid allow companies to take advantage of a new data structure to use thenew functionality in PP/DS, the PPM did not support variant configurationor ECM. While the PPM that was generated from the SAP R/3 productionversion generated PP/DS relevant data, it did not allow for the generation orintegration into SNP. In order for companies to integrate the SNP solutioninto their business practices, SAP allowed companies to generate SNP PPMsfrom the PP/DS PPM that was created from the CIF. However, this did notwork well for companies who had large amounts of engineering changesthat would affect their SNP process.

Figure 90: Mfg. Master Data Modeling options

As of release APO 3.0 development of the RTO began to allow companieswho used the SAP R/3 Variant Configuration (VC) for modeling their masterdata, as well as those customers who required ECM functionality. With therelease of SAP SCM 4.0 the RTO has become the standard supported methodof integration of the SAP R/3 BOM, Task list, and Master Recipe copied to SAPSCM (APO). You can use the RTO in a similar way to the production processmodel (PPM) as a source of supply for in-house production. In contrast to thePPM, the PP/DS runtime object supports object dependencies and time-basedchange management.



The PP/DS runtime object allows multilevel configuration in the form ofnested K-MAT. Changes to the object dependencies are taken into account inthe same way as the changes to Bills of materials and routings. All typesof object dependencies are possible both for components and operations.Actions are mapped as procedures in SAP SCM. The priority sequence ofprocedures is retained in the runtime object. The object dependencies areexploded by the �valid as of� date of the component or operation. Multilevelconfiguration is supported in the same way as single-level configuration inSAP R/3. Components are marked as configurable in the runtime object if theyhave a valid configuration profile for nested K-MAT. The materials that can beassigned to a class node are selected when a runtime object is created. Thematerials are created as additional components in the runtime object andeach is assigned a selection criterion that is the same as the classification ofthe object. For the explosion, the evaluation of the parent is used to select thecomponent. When changing the classification, or deleting or adding newmaterials to the class, the runtime object must be transferred again. All classtypes for class nodes are supported.

Variant tables and variant functions must be defined in both SAP R/3 andthe SAP SCM. There is no data supply between SAP R/3 and SAP SCM.This also applies to the content of variant tables. Date effectivity changes ina Bill of materials and routing with and without change masters are nowsupported in SAP SCM for planning using PP/DS runtime objects. When youchange a component in a bill of materials with a valid from date for example,a new material 4711 at position 30, the changes will be considered after adelta transfer in the SAP SCM. You can also transfer a classic bill of materials,routings, and recipes into PP/DS runtime objects that will then be used insteadof PPMs for planning. This means that variant configurations, engineering



changes, Bills of materials, routings, and recipes can be transferred to PP/DSruntime objects. You can also replace Production Process Models with PP/DSruntime objects.

Note: Note the restrictions on the following slides and see note 517264.

� Characteristics Dependent Planning (CDP)� Block Planning� Extended Order Generation (EOG)/Mulitple Output Planning (MOP)� Trim Optimization� CTM/SNP� SNP PPM Creation� Parameter Effectivity� Batch Selection Criteria from BOM Positions� RTO is DISPLAY ONLY!� PPM CIF user exits are not supported.

Note: If you want to migrate from PPM to PP/DS runtime objects, youhave to maintain specific user exits.

Note: If migrating from PPM to RTO, users will have to set theindicator in the product master (or Global Setting - IMG) to decidewhether the SAP SCM uses PPMs or PP/DS runtime objects forplanning.



Figure 91: RTO in the Integration Mode

Prerequisites for using the PP/DS runtime objects are:

� You have to create and activate an integration model for runtime objects.Use the specific indicator iPPE Runtime object.

� All materials, plants and routings must be contained in active integrationmodels. This is also true for classes and characteristics if you are workingwith configurations.

� You have to create a production version for materials for which a runtimeobject is to be generated. The Bill of materials alternative and the routingfor detailed scheduling must be defined in the production version.

� If the Bill of materials contains phantom assemblies . These must betransferred separately and may not need a production version.

Phantom assemblies can be mapped in the runtime object. They are notexploded in SAP R/3 as in the PPM. Only phantoms with special procurementkey 50 are treated as phantom assemblies. They must be transferred separatelyfrom BOMs. The components of the phantom assembly contain the sameactivity as the phantom components of the superordinate assembly. Thephantom assembly must have exactly one BOM alternative if a productionversion was not created. In SAP SCM orders, the phantom assembliesthemselves are marked as not relevant to pegging. It is possible to transferphantom assemblies with production versions. Planned orders can also be



generated for these phantom assemblies. The distribution key is implementedin the runtime object and is hard-coded with linear distribution. The lead-timeoffset is taken into account.

To support the RTO delta transfer process several transactions and reports areavailable on the SAP R/3 side:

� CURTO_CREATE (Transaction)� CURTO_CREATE_BOM (Transaction for Phantoms)� CUSLNTRTO_CIF_REPORT(Report)� CUSLNTRTO_CIF_MAST (Report)� CUSLNTRO_ADDIN (BADI)

You can transfer a Bill of materials, and a routing to PP/DS runtime objectswith a production version. Use transaction CURTO_CREATE in SAP R/3.You define the target system and the planning versions to transfer completestructures into a planning version of SAP SCM . If you set the �changetransfer� indicator, only those runtime objects for which a master datachange has been made since the last transfer are transferred to the SAP SCM.Multiple, variant and super Bills of materials for configurable materials can betransferred. The following types are not supported:

� Bill of materials for function location� Equipment Bill of materials� Document structures� Work breakdown structure Bill of materials

Bill of materials can have different validity periods at both the header and itemlevel. Within the validity period of the production version, all engineeringchange statuses for headers and items are transferred.

� The release key for change numbers is not taken into account.� Only the base quantity is transferred from the Bill of materials header.� Only those Bills of materials relevant to production are transferred. This

takes into account its status and usage.� Sub items are not integrated because sub items from the BOM are

not included in the SAP R/3 production order. They are therefore notrelevant to SAP SCM.

After transferring the RTO, you can assign PP/DS runtime objects fromplanning version 000 to new planning versions in the SAP SCM. You generatea link to the PP/DS runtime object in the active version but do not duplicatethe objects. Changes made to PP/DS runtime objects in the active planningversion 000 will be considered in the linked planning versions.



Create and Display RTO

1. SAP R/3 menu path: Logistics → Central Functions → Supply ChainPlanning Interface → Core Interface Advanced Planner and Optimizer →Integration Model → Generate → Create

2.

Use the following parameters:

Field Name ValueModel Name PUMP##

Logical System APOCLNT8XX

Application RTO T-F1##

3. In the General Selection Options for materials enter Material T-F1##and plant 1000.

4. Select the PPDS Runtm Obj. Indicator.

5. Select Execute

6. Select Save

7. SAP R/3 menu path: Logistics → Central Functions → Supply ChainPlanning Interface → Core Interface Advanced Planner and Optimizer →Integration Model → Activate

8. Enter the following values:

Field Name ValueModel Name PUMP##

Logical System APOCLNT8XX

Application RTO T-F1##

Double click on your integration model you just created, and selectStart Activation

9. SAP SCM menu path: Advance Planning and Optimization→Master Data→ PP/DS Runtime Object→ Display PP/DS Runtime Object




10. Enter the following Values:

Field Name ValuePlanning Version 000

Product T-F1##

Location 1000

Select Execute.



Lesson Summary

You should now be able to:� Identify the dependencies between SAP R/3 production version, and

SAP SCM Run Time Objects (RTO).�


SCM210 Lesson: Purchasing Information Records

Lesson: Purchasing Information Records

Lesson OverviewIn this lesson we introduce purchasing info records and define them and theiruse. We discuss the advantage of transferring info records via the CIF fromthe SAP R/3 system.


� Identify how SAP R/3 Purchasing master data can transfer to SAP SCMvia the Core Interface.

� Review the results of transferring a purchasing info record from SAP R/3to SAP SCM via the Core Interface.

�

Business ExampleAssume your company which manufactures pumps, needs to procure severalraw materials for manufacturing their sub-assemblies and final assemblies.To ensure that your manufacturing schedules are not affected in a negativemanner based on procurement plans, you need to include several rawmaterials during the planning runs in SAP SCM.

SAP R/3 Purchasing Info RecordsThe SAP R/3 Purchasing Info Record serves as a source of information forPurchasing. The purchasing info record contains information on a specificmaterial and the vendor supplying that material.



The SAP R/3 Purchasing info record contains the following data:

� Data such as prices and conditions that you can store for the relevantpurchasing organization or plant

� The number of the last purchase order� Tolerance limits for over-deliveries and under-deliveries� The planned delivery time (lead time required by the vendor to deliver

the material)� Vendor evaluation data� An indicator showing whether the vendor counts as the regular vendor

for the material� The vendor sub-range to which the material belongs� The availability period during which the vendor can supply the material� The info record contains quotation and ordering data.� The data in the info record (such as price) is also used as default data

for purchase orders. For instance, you can store the current and futurequotation conditions (discounts, fixed costs etc.) in the info record. Youcan also maintain the vendor�s conditions directly in the info record.

A purchasing info record can be created at either the plant or purchasingorganization organizational levels.

A purchasing info record allows buyers to quickly determine:

� Which materials have been previously offered or supplied by a specificvendor

� Which vendors have offered or supplied a specific material

A purchasing info record can be created:

� Manually for a plant or a purchasing organization.� Automatically if you set the Info update indicator when maintaining a

quotation, a purchase order, or an outline agreement. Ordering data willthen be recorded/updated automatically in an info record



Figure 92: Transferring SAP R/3 Purchasing info Recs to SAP SCM

Purchasing info records in the SAP R/3 system can be transferred to theSAP SCM system as external procurement relationships. The conditions aretransferred from the purchasing info record to the external procurementrelationship in SAP SCM. Purchasing info records without conditions arecreated as external procurement relationships without costs. The type ofinfo record (standard, consignment, or subcontracting) defines the formof procurement.

The info record links the transportation lane with information from theOLTP system. The transportation lane defines the relationship between thesource (vendor) location and the destination (plant) location. The externalprocurement relationship extends the information of the transportation laneby establishing a link to the info record, contract, or scheduling agreementthat exists in the OLTP system for that specific product, source location, anddestination location combination. If a transportation lane currently exists atthe time of transfer the info record will be linked to it. If a transportation lanedoes not exist at the time of transfer the system will automatically create onefor the specific locations since the info record contains all the data needed tocreate it.



Figure 93: External Procurement Process In SAP SCM System

Caution: If you transfer info records that were created at thepurchasing organization level (not plant specific), the system willcreate a transportation lane from the specified vendor location toevery plant assigned to that purchasing organization that exists in theSAP SCM system.

When considering transfering purchasing master data to SAP SCM weneed to understand just which objects can be transferred. The followingpurchasing data can be sent to SAP SCM in the form of External ProcurementRelationships:

� Standard Purchasing Info Record� Consignment Purchasing Info Records� Sub-Contracting Purchasing Info Records� Scheduling Agreements

Scheduling agreements can be handled differently in SAP SCM than normalexternal procurement relationships. Scheduling agreements can be maintainedin either SAP R/3 or SAP SCM. If you choose to maintain the schedullingagreements in SAP SCM, at the item level, in the additional data section, youmust set the external planning indicator to 1 - Planning and release generation in



APO. Once this is set and the record is transfered to SAP SCM, you will needto make additional configuration settings in the SAP SCM IMG to suppot therelease generation methodology. You must maintain the following tables:

� Maintain Release Profile� Define Actions for Issuing Scheduling Agreement Releases� Confirmation Receipts

Note: These settings can be found in the IMG under:Advance Planningand Optimizaiton→ Supply Chain Planning→ Collaborative Procurement→ Procurement Scheduling Agreement

Sub-contracting can take many forms in SAP SCM:

� Sub-contracting without planning at the vendor location� Sub-contracting with planning at the vendor location

When not includeing the vendor in your model, during the planning run,requirements of the supply chain end product are planned at the plantlocation. The system generates a purchase requisition at the plant location,and a planned order linked to the requisition. The planned order contains therequirements of the subcontracting components. These are then planned atthe plant location. However, the transportation of the components cannotbe planned in the SAP SCM system. In contrast to planning with a vendorlocation, this scenario necessitates less system maintenance but is restrictedto the case in which you have just one subcontractor for the supply chainproduct and do not allow in-house production.

When including the vendor in your model,during the planning run,requirements of the subcontracted end product are planned at the plantlocation. The system covers requirements through purchase requisitionsfor external procurement from the subcontractor location, so that acorresponding requisition release is created at the subcontractor location.This requisition release is covered by a planned order containing therequirements of the subcontracting components at the subcontractor location.



The subcontracting components are subsequently planned at the vendorlocation and a plant-to-vendor stock transport order generated. This enablesthe transportation of the components to be planned in the SAP SCM system.

Note: When planning at the vendor location, PPMs and productmasters can be generated at the Vendor location via the CIF. In orderto due so you must have a BOM and production version set up at theSAP R/3 Plant, and include the production version in the purchasinginfo record. For more details see notes 565024 (PPM) and 483358(materials).



Display Procurement Relationships

1. SAP SCMMenu path Advanced Planning and Optimization→Master Data→ Procurement Master Data→ Procurement Relationships→

2. Select Destination location 1000 and select Execute

3. Drill down under Info Rec→ T90CLNT090→ 530000117 and double click

to view the detail of the record.

4. Select Costs to review the currency value of the record relative specificlot sizes.

5. Show Transporation lane information by selecting a record andEnvironment → Transportation Lane → Display



Lesson Summary

You should now be able to:� Identify how SAP R/3 Purchasing master data can transfer to SAP SCM


to SAP SCM via the Core Interface.�


SCM210 Lesson: Transportation Lanes

Lesson: Transportation Lanes

Lesson OverviewTo properly model the enterprise supply chain network it is important tounderstand how the various sources and destinations of material flows areconnected to form the network. The object used to make these connections inthe supply chain network is the Transportation Lane. In this lesson you willlearn the characteristics of transportation lanes, how to create them and thevarious parameters and attributes that must be assigned to the transportationlanes to properly plan the material flows within your supply chain network.


� Identify how the special procurement functionality in SAP R/3 willtransfer to SAP SCM via the Core Interface.

� Review the results of a transferred transportation lane from SAP R/3 toSAP SCM via the Core Interface.

Business ExampleAssume your pump company sells mostly from pre-existing stock that wasdriven by a forecast at the distribution centers. In order for the distributioncenters to generate stock transport requests, a determination of whichlocations they can source from must be made. You decide to use the specialprocurement functionality in SAP R/3, to generate transportation lanes in SAPSCM. These transportation lanes will be the key to help determine from wherea product can be shipped or bought.



Transportation Lanes

Figure 94: Basic Transportation Lane Relationships

A transportation lane in SAP SCM represents a direct route between twolocations that can be used to source and transport products between them.Each lane is defined by its source and target locations, depending on thedirection of traffic, and is assigned products to be transported along the route.If you want to transfer products between two locations in the supply chain(for example, from a vendor to a production plant), a transportation lane hasto exist between the two locations. Transportation lanes are created in SAPSCM for this reason.

The lanes and locations represent the supply chain network. Each lane isalso assigned available transportation methods. The following SAP SCMcomponents make use of transportation lanes and their associated data:

� Supply Network Planning (SNP)� Network Design (ND)� Production Planning/Detailed Scheduling (PP/DS)� Transportation Planning/Detailed Scheduling (TP/VS).



Figure 95: Basic Transportation Lane Data

Creation of transportation lanes enables you to:

� Define the product procurement parameters, such as lot sizes, costfunctions, unit costs, and lane priorities. This data is used in SupplyNetwork Planning.

� Define the means of transport (transportation method) for each lane(truck, ship, rail, air, for example) and the related parameters, such astransportation costs, distances and shipment duration.

� Assign product-specific means of transport (transportation method). Thedata assigned in this process is used in Supply Network Planning.

� Assign transportation service providers (carriers) to the lanes.Transportation service providers assigned to transportation lanes areused in the TP/VS component to assign transportation service providersto planned shipments.

Considered part of SAP SCMmaster data, transportation lanes usually remainunchanged over a period of time. Transportation lanes can be maintainedindividually or in groups. Mass maintenance of transportation lanes facilitatethe generation and maintenance of large quantities of transportation supplychain data. There is no equivalent master data structure in the SAP R/3System. However, the information in the SAP R/3 System that correspondsto a transportation lane such as the special procurement key can be definedin the material master.



In the SAP R/3 Sales and Distribution and Logistics Execution applicationsthere is an organizational element, the Route, that is used to representan itinerary connecting a shipping point and a customer ship-to address.Although the route definition in the SAP R/3 System contains some deliveryand shipment planning data, the transfer of route-related information is notperformed for SAP SCM. Generally, the SAP SCM transportation lane masterdata is much more precise and flexible for use in the SAP SCM planningcomponents.

Special Procurement Key and Transportation LanesAs of SCM 4.0 and PI2003.1, using the special procurement key, the CIF cancreate Transportation lanes.

Storing a special procurement type with procurement type F: ExternalProcurement and special procurement U: Stock Transfer (in the MRP 2 viewof the SAP R/3 material master record), means that the material has to beprocured externally from another plant (supplying plant) or transferred fromanother plant. To also be able to perform stock transfers for this materialin the SAP SCM, system, there has to be a transportation lane from thesupplying plant to the receiving plant. If you have transferred a materialwith this special procurement type from the SAP R/3 system, the SAP SCMsystem automatically creates a corresponding transportation lane from thesupplying plant to the receiving plant for the supplying plant (from the specialprocurement type) and material/plant combination. The transportation lane isgiven the creation indicator �S� for special procurement.



Figure 96: Transfer of Special Procurement Key to SAP SCM

Caution: When the material master record is transferred from the SAPR/3 system to the SAP SCM system, if there is already a manuallycreated transportation lane with exactly the same supplying plant andreceiving plant combination, this is kept and no new transportationlane is created.

In the SAP R/3 system, if you have changed the supplying plant in the specialprocurement type, the SAP SCM system creates a new transportation lane forthe new supplying plant (from special procurement type) and material/plantcombination. The already existing transportation lane and now invalidcombination between supplying plant and receiving plant in the SAP R/3system is locked for orders in the SAP SCM system. This can be recognizedby the lock indicator X that is set by the system.

If you have removed the special procurement type from the material masterrecord in the SAP R/3 system, the SAP SCM system locks the already createdtransportation lane so that it cannot be used in orders.

If transportation lanes (that were generated or manually created whenpurchasing data was transferred from the SAP R/3 system) already existin the SAP SCM system, the SAP SCM system takes these transportation



lanes into account when determining sources of supply. In this instance, thetransportation lanes that were automatically generated from the SAP R/3material master are not taken into account.

Figure 97: External Procurement Relationships

One of the main data structures that can be defined within a transportationlane is the External Procurement Relationships. These relationships are usedin Supply Network Planning. Purchasing info records, contracts or outlineagreements, with which you create price and supply agreements with certainsuppliers in the SAP R/3 System can be transferred to the SAP SCM System asexternal procurement relationships. A corresponding transportation lane isthen created in the SAP SCM system. In principal, transportation lanes aremaintained on a product-specific basis. However, they can be used for allproducts. A transportation lane contains one or more transportation methods,also referred to as transport methods, that can be used for transporting theproduct (truck or rail, for example). You can define costs and duration timesin the transportation lane. You can then set priorities to enable the system tomake stock transfer decisions.



Create Transportation lane in SAP SCM from SpecialProcurement Key

1. Display the material master (MRP 2 view) for T-F1## (instructors materialnumber) at plant 1000. SAP R/3 menu path:Logistics → Production →Master Data→Material Master→Material→ Change→ Immediately

2. Note the procurement key and the special procurement key

3. Display the transportation lane in SAP SCM for :

SAP SCMMenu path: Advanced Planning and Optimization→Master Data→ Transportation Lane → Transportation Lane

Field Name ValueModel 000

Start Location 1200

Destination Location 1000

Select Display

4. Select the instructors product T-F1## and select Details Screen

5. Note in the section labeled Parameters the field Block indicator shouldbe set to Available. If the instructor has already removed the specialprocurement key, the field should be set to Locked and Flagged fordeletion.

6. Note in the section labeled Form of procurement, the creation indicatorset to S - Creation from special procurement



Lesson Summary

You should now be able to:� Identify how the special procurement functionality in SAP R/3 will

transfer to SAP SCM via the Core Interface.� Review the results of a transferred transportation lane from SAP R/3 to

SAP SCM via the Core Interface.


SCM210 Lesson: Master Recipes and the PPM

Lesson: Master Recipes and the PPM

Lesson OverviewIn this lesson we will learn, how the transfer of Master Recipe master data inSAP R/3 are going to be handled through the CIF integration model, and theirrelationships to the corresponding PPM master data generated in SCM.


� Review an SAP SCM PPM that was generated by transferring a masterrecipe via the Core Interface.

� Identify the differences between transferring a Master Recipe and a Billof Material and Routing to SAP SCM.

Business ExampleAssume your company manufactures bulk liquid detergent. In order toproperly prepare a manufacturing schedule, you need to properly model therequirements. These requirements will involve the necessary assemblies orraw materials as well as the manufacturing set-ups and relevant resources toproduce the end product. You need to understand how the SAP R/3 masterrecipe will transfer to the SAP SCM PPM.

Master Recipes in SAP SCMMaster recipes are SAP R/3 master data that describe an enterprise-specificproduction process in SAP�s process industry module, and is used inconstructing individual process orders or for rendering services. Themaster recipe is another type of �task list�, which is similar to a discretemanufacturing routing. Master recipes are mainly used by MRP for planning,and subsequently in Process Orders management, for the manufacture ofproducts, and performing in-process inspections. You can also use them todescribe the clean-out or changeover of a production line. Master recipesare also used by product costing as the basis for developing unit costs.Furthermore, the engineering change approval procedure for master recipes,and their functions for planning and documenting changes, meet the mostimportant requirements of Good Manufacturing Practices (GMP).



Figure 98: Functions of a Master Recipe

The features of the master recipe were defined in accordance with theinternational standards of the European Batch Forum (EBF), the normsworking committee for measuring and control techniques in the chemicalindustry (NAMUR), as well as in accordance with standard S88 of theInstrument Society of America (ISA). In a master recipe, you model:

� Phases - the individual steps to be carried out in a process, that is, theoperations and its subdivisions

� Activities - (ex. - setup/charge, processing, tear down/discharge) thatare to be carried out in a phase and are used as the basis for determiningdates, capacity requirements, and costs

� Process Sequence - by defining predecessor-successor relationships (ex.- finish-start, start-start) between phases

� Materials - the use and production of in the course of the process(component/finished good quantities)

� Resources - the use of equipment or people by operations and phases bydefining activities times (ex. - fixed time, variable time)

� Quality inspections - to be carried out during production to supportquality manufacturing

� Process Instructions - used to collected data for costing, materialmovements, and quality information (digital signatures) via a web basedtool, or via process control system (PLC).



We will now discuss how the Master Recipe is different from the routing andhow those differences are modeled in SAP SCM

Rules for Transferring Master Recipes�s to PPM�sIn many ways, the rules for transferring the elements of a SAP R/3 MasterRecipe to a PPM, are similar to how the elements of a routing are converted toa PPM.

Figure 99: Master Recipe and PPM: Basics

The transferred PPM�s name is made up from the routing type (2),group/counter number, version number, and with usage P. For example,25000004001A001T-FD100 3100. 2 is the task-list type, 50000040 is the recipegroup number, 01 is the recipe group counter, A001 is the production version,T-FD100 represents the material assignment in the recipe (18 charactersreserved), and 3100 is the plant where the recipe is maintained.

The lot size and PPM validity time intervals are determined from the materialmaster production version. The lot size of the recipe has no impact. Therecipe text transfers as the plan text, and the production version descriptionas the PPM text.

PI Operations with resources/work centers in an active integration model,that have scheduling relevant control keys, will transfer across to SAP SCMas operations (type 1), however they will not have activities. As of SAP APO



3.0, the recipes are transferred to a new PPM structure. Operation types havebeen introduced so that the recipe operations, the phases and the dependentresources of the recipe are transferred as separate operation types.

� 0 - PP operation� 1 - PI operation� 2 - PI phase� 3 - PI dependent resource)

PI phases with resources/work centers in an active integration model, thathave scheduling relevant control keys, will transfer across to SAP SCM asoperations (type 2). Each new �operation� will have activities to whichcomponents and resources will be allocated. The scheduling relevant capacitycategory of the primary operation resource in the SAP R/3 master recipe, istransferred as the primary operation resource in the PPM. Additional capacitycategories of the primary operation resource in the SAP R/3 recipe, aretransferred as secondary resources in the PPM. (not to be confused with SAPR/3 secondary resources). After the activities transfer across to the SAP SCMPPM, the single primary resource and also the possible multiple secondaryresources, are grouped under one activity mode. The rules for creation ofPPM activities are different in Master Recipes than in routing transfers. In arouting, each operation time segment (setup, process, tear down), that itselfhas been calculated from activities and Work Center scheduling formula, isthen converted to an SAP SCM activity. In contrast, in the master recipe, eachphase is converted to an SAP SCM operation and activity.

The BOM with its components are transferred to SAP SCM, as long as it isdefined with the usage and alternative in the production version of the headermaterial. Component assignments to the phases of the SAP R/3 master recipe,are now assigned to the first activity of the first operation (type 2) of thecorresponding operation (type 1), and the output product is assigned to thelast activity of the last operation (type 2) of the last operation (type 1)in theSAP SCM PPM.



Figure 100: Relationships/Activity Relationships

When master recipes are transferred to SAP SCM several differencesbetween Routing transfers and Recipe transfers exists. In a PPM, Finish-Startrelationships are generated from ascending sequential numbered operations ofa routing. In Master Recipes the original phase time sequencing relationships,that were built into the master recipe, are preserved. Only FINISH-STARTand START-START relationships are modelled however. The variable andfixed time durations of a phase in a master recipe, come across directly to thePPM activity, as variable and fixed time durations. There are no Wait andMove times in a Master Recipe operation to consider. All time segments aremodelled as phases.

In SAP R/3, companies can use resource networks to model some of theproduction dependencies between several different resources. In addition tothis functionality, the master recipe can use resource selection. This is doneby classifying each resource with specific information regarding its� usage,and then by classifying a specific operation in a recipe with certain selectioncriteria. The operation in question receives a �dummy �resource that willnot be used in production, but at order release time a specific resource mustbe chosen that will allow production. During the master recipe transfer toSAP SCM, the resource selection condition of the planning resource in anoperation is triggered. The PPM activity, now contains any resources thatmeet the selection condition of the operations in the recipe that match theselection condition.



Caution: During the transfer, the CIF is not limited to the resourcenetwork. It will add any resource to the PPM as an alternative mode ifit meets the operations classification selection conditions.

If an SAP R/3 phase has a secondary resource attached, an additionaloperation (type 3) will be created in SAP SCM. This operation will have aSTART - START relationship with its �parent�phase. Any offset times willbe transferred as well.

If there are any components that are directly assigned to the phases in theSAP R/3 Master Recipe, these assignments are kept intact, in the SAP SCMPPM. If no assignment has been made, all components will be assigned to thefirst operation (type 2) in the PPM. Companies have the option of modelingco-products and by-products in SAP R/3. If a recipe contains one or both,the materials will be transferred to SAP SCM if the material master for theby-product or co-product is in an active integration model. Each of thesesecondary materials will receive a PPM name in the PPM. In addition, onthe header material, the Primary material flag will be set in the componentoverview where the header material is received.



Recipes in SAP SCM

1. SAP R/3 menu path: Logistics → Production - Process → Master Data →Master Recipes → Recipe and Material List → Display

2. Enter Material T-FD100, Plant 3100, and select GeneralData

3. Enter Material T-FD100, Plant 3100, and select GeneralData

4. Review the details of the resource network that will be used at operation200 to portray your production resource options. Select Res. NetworkGraphic

5. In the graph select resource T-DTR200, menu path Goto→ work center→Display. At the bottom of the Basic Data tab, select Classification. Showthe students how each resource can be classified.

6. Select Back Twice.

7. From the Recipe header screen select the Operations tab.

8. Select operation 200 and select Resource selection criteria

9. Select Back.

10. Double click on operation/phase 130 and choose the relationships tab

11. Select Back.

12. Return to the operations overview and double click on phase 330 -Discharge

13. Double click on Secondary Resource item 001 to show the schedulingof the truck.

14. SAP SCM menu path Advanced Planning and Optimization→Master Data→ Production Process Model→ Production Process Model

15. Select option for choose plan through PPM. Enter material T-FD100,location 3100and hit ENTER

16. Select Display




17. In the top left windowDrill down on the operations sections to review thePPM. Drill down on operation 200 - Reactionand operation 210 - Charge.

18. Drill down on operation 330 - Discharge and operation 0001 - Discharge

19. Drill down on the Activity overview.



Lesson Summary

You should now be able to:� Review an SAP SCM PPM that was generated by transferring a master

recipe via the Core Interface.� Identify the differences between transferring a Master Recipe and a Bill

of Material and Routing to SAP SCM.


Unit Summary SCM210

Unit SummaryYou should now be able to:� Identify the type of locations that SAP SCM supports from a planning

perspective.� Explain how Plants are transferred to SAP SCM and demonstrate the

results� Explain how MRP Areas are transferred to SAP SCM and demonstrate

the results� Explain how Customer Master records are transferred to SAP SCM and

demonstrate the results� Explain how Vendor Master records are mapped to SAP SCM and

demonstrate the results� Explain the effects of SAP SCM location types on supply chain modeling� Identify the dependencies created as a result of the integration between

the materials master in SAP R/3 and SAP SCM.� Transfer Material Masters from SAP R/3 to SAP SCM.� Identify how the SAP R/3 work center and resource will transfer to SAP



transferred to SAP SCM from SAP R/3.� Identify the dependencies between the SAP R/3 production version, and

the SAP SCM production process models.� Transfer a production version from SAP R/3 to SAP SCM via the Core

Interface.� Identify the limitations of the PPM when modeling a manufacturing

process in SAP SCM.� Identify the dependencies between SAP R/3 production version, and

SAP SCM Run Time Objects (RTO).�� Identify how SAP R/3 Purchasing master data can transfer to SAP SCM


to SAP SCM via the Core Interface.�� Identify how the special procurement functionality in SAP R/3 will

transfer to SAP SCM via the Core Interface.


SCM210 Unit Summary

� Review the results of a transferred transportation lane from SAP R/3 toSAP SCM via the Core Interface.

� Review an SAP SCM PPM that was generated by transferring a masterrecipe via the Core Interface.

� Identify the differences between transferring a Master Recipe and a Billof Material and Routing to SAP SCM.


Unit Summary SCM210



Test Your Knowledge

1. What are the location types with which the following SAP R/3 masterdata is represented in SAP SCM?MRP area: CustomerVendor:Fill in the blanks to complete the sentence.

2. When Transferring vendors and customers to SAP SCM what to youhave to ensure

3. Plants and DC�s are represented differently in SAP SCM because theyeach have specific functionality to represent?Determine whether this statement is true or false.□ True□ False

4. Freight carriers are represented in SAP R/3 as vendors?Determine whether this statement is true or false.□ True□ False

5. Transportation Zones are master data in SAP R/3?Determine whether this statement is true or false.□ True□ False

6. What is the standard length of the SAP SCM product master numberin SAP SCM customizing?Choose the correct answer(s).□ A 10 digits□ B 12 digits□ C 15 digits□ D 18 digits



7. What material types are supported in SAP SCM?

8. If there is no strategy group in the SAP R/3 Material Master, what willthe strategy be set to in SAP SCM?

9. While transferring lot-sizing procedures to SAP SCM the CIF reads theSAP R/3 in order to set the SAPSCM field parameters.Fill in the blanks to complete the sentence.

10. While transferring periodic lot-sizing procedures, to set availabilitydate = requirements date, the availability date indicator of the productis left .Fill in the blanks to complete the sentence.



Answers

1. What are the location types with which the following SAP R/3 masterdata is represented in SAP SCM? MRP area:1007 Customer1010 Vendor:1011___

Answer: 1007 , 1010, 1011___

2. When Transferring vendors and customers to SAP SCM what to youhave to ensure

Answer: That the numbers, or number ranges are unique. If not you willhave to use a user exit to separate the two in SAP SCM.

3. Plants and DC�s are represented differently in SAP SCM because theyeach have specific functionality to represent?

Answer: False

Plant�s and DC�s are represented differently in SAP SCM only to identifythat different activities take place at these different location types. Thereis no functional difference between them.

4. Freight carriers are represented in SAP R/3 as vendors?

Answer: True

Freight carrier are vendors in SAP R/3, however they have a differentaccount group then vendors from which we procure products. Inaddition we model them as a different location type in SAP SCM andhave Functionality to support carrier selection.

5. Transportation Zones are master data in SAP R/3?

Answer: False

Transportation zone are defined in configuration with no othersupporting data. They are then assigned to each Customer Master as away of grouping customers in a geographical manner.



6. What is the standard length of the SAP SCM product master numberin SAP SCM customizing?

Answer: D

In SAP R/3 , an 18-digit product number is used.

7. What material types are supported in SAP SCM?

Answer: All! There is no such thing as material type in SAP SCM.

8. If there is no strategy group in the SAP R/3 Material Master, what willthe strategy be set to in SAP SCM?

Answer: It depends! If there is an MRP group set in the SAP R/3 materialmaster, the CIF will read the MRP group for the strategy. If no strategy isset then the system will transfer a �blank�to SAP SCM.

9. While transferring lot-sizing procedures to SAP SCM the CIF readsthe SAP R/3 Customizing values in order to set the SAP SCM fieldparameters.

Answer: Customizing values

10. While transferring periodic lot-sizing procedures, to set availability date= requirements date, the availability date indicator of the product is leftblank.

Answer: blank


Unit 3Modeling in mySAP SCM

Unit OverviewOnce your data has been transferred to SAP SCM, you will familiarize yourselfwith the modeling and simulation tools. As SAP SCM is a pure �planning�tool simulations and �what if� will be part of your daily job.


� Explain what a model means in SAP SCM� Explain the use of Model consistency checks� Explain what a version means in SAP SCM� Explain how SAP R/3 integrates with versions in SAP SCM� Explain the purpose of the supply chain engineer� Explain and demonstrate the user settings for the Supply Chain Engineer� Explain and demonstrate how the Supply Chain Engineer is used.

Unit ContentsLesson: Models .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .226

Procedure: Creating Models in SAP SCM ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .229Procedure: Model Consistency Check ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .232

Lesson: Versions in SAP SCM.... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .234Procedure: Creating Planning Versions .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .241

Lesson: Modeling with the Supply Chain Engineer .. . . . . . . . . . . . . . . . . . . . . . . . . . .246Procedure: Navigating the SCE ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .249


Unit 3: Modeling in mySAP SCM SCM210

Lesson: Models

Lesson OverviewIn this lesson we will discuss the options of simulation planning. Models arethe first step in strategic supply chain planning and simulation.


� Explain what a model means in SAP SCM� Explain the use of Model consistency checks

Business ExampleAssume your business has decided to implement SAP SCM for supply chainplanning. You need to explain the master data environment to users. Forcontinuous planning, users use model 000. However, a simulation needscreating periodically . Users will demostrate how a model is created.

LiveCache Supply Chain Models in SCMThe Supply Chain Model (abbreviation: Model) represents the entire supplychain network ranging from suppliers to production and distribution sites,through to the customer. It contains locations, transportation lanes, products,resources, and production process models. The model is therefore the basisfor all planning functions in SAP SCM. A model is a set of master data. Masterdata from SAP R/3 is automatically assigned to the active model (model 000)during the transfer to SAP SCM. Model 000 is the only active model and allothers are simulation models.


SCM210 Lesson: Models

Figure 101: LiveCache Supply Chain Models in SAP SCM

All master data that is transferred from SAP R/3 using the CIF is automaticallyassigned to model 000, the active model. The active model represents thesupply chain actually used in the company. In this way, all the transferredmaster data is automatically available for operational planning in model000. Master data that is created directly in the SAP SCM System is modelindependent master data and must be assigned to a model. You can useversion management to copy models or create them manually.

You maintain the supply chain network in the Supply Chain Engineer (SCE),by placing locations on the map and create a network by adding transportationlanes. The lane direction shows the direction of the product transportationflow. The SCE allows you to view data pertaining to different elements in yoursupply chain. It also allows you to maintain the model objects simultaneously.You can submit requests for information on individual or combined elementsin your supply chain. For example, you can request a list of all the productsassigned to a specific location in your model. At the same time, you can addproducts to this location or make changes in the location master.

As well as locations and transportation lanes, the supply chain model alsoallows you to keep track of other supply chain elements. These includeproducts, PPMs (production process models), and resources. During supplychain modeling, you may have to assign or delete large numbers of objectsin your model. Many of these objects can have dependent objects assignedto them. To guarantee consistency within the model, you can automaticallyassign or delete the dependent objects, together with the primary object.



Automatic assignment guarantees not only consistency but also enables easiermodel maintenance. If you have a lot of master data, viewing it in the networkmap in the Supply Chain Engineer can become very confusing. To limit yourview to only the master data you want to concentrate on, you can define workareas. The work area is used exclusively as a filter for displaying objects inthe Engineer. You can maintain different work areas. In the work area of theSupply Chain Engineer, you can select: Locations (plant, distribution center,vendor, customer) Products Resources PPMs (production process models).



Creating Models in SAP SCM

1. SAP SCM menu Path: Advanced Planning and Optimization→Master Data→ Planning and Version Management→Model and Version Management

2. Select Create Model/Planning Version → Model

3. Create model A## with description Instructor Demo

4. Select Create and Save

Model Consistency CheckAfter updating or creating a model in SAP SCM, users need to ensure thatthe data is correcting in all the dependencies that will be required by theplanning algorithms. As of SCM 4.0, companies have the ability to use amodel consistency check:

Figure 102: Model Consistency Check

The first step in managing the consistency check process is to define a profile.You use this function to display, create, select, and process check profiles forthe model consistency check. All of the individual checks to be executed in themodel consistency check are contained in a profile. It determines the scope



of the model consistency check. Individual checks of the following masterdata and applications are available in the model consistency check and arevisible in the graphic above.

When performing aMaster Data check, you can check the consistency of thedata within individual master data objects. The system determines whetherall necessary information (on a field level) is maintained. We recommend thatyou always execute a master data check after maintaining a model in theSupply Chain Engineer (SCE).

When performing Cross-Master data checks, you can search forinconsistencies between master data objects. In-house production: If in-houseproduction is defined for a location product, the system checks whethera PPM exists for the location product. External procurement: If externalprocurement is defined for a location product, the system checks whether theproduct is defined for a transportation lane that leads to the location.

When performing Application Checks, you can check that master data objectsare used consistently in the applications. Use this check depending on yourbusiness process.

You can execute a model consistency check for a planning version. In additionto the planning version, specify a profile and a check date. All master dataobjects assigned to the planning version form the object selection:

� The system uses planning version-dependent data for individual masterdata objects, if it exists.

� If it does not exist, the system uses the planning version-independentmodel data for the check.

If you specify a check date, the system considers the time specifications (forexample, validities of objects or time-dependent attributes) of the particulardate. If you specify a work area, you can limit the amount of data to bechecked. The system then checks the objects in this work area only.

In the setup of the consistency check with the Strict Check Criteria indicator,you can define criteria for the check of objects from the object selection andfor the favored message type. If you set the indicator (check type 1), the



system checks the objects of the object selection to see whether they display aconsistent (partial) model. In this case, the system assigns the message typeusing the following criteria:

� Error (E): This message refers to an inconsistency.� Warning (W): This message indicates that the current data situation may

lead to problems in the applications, especially in the planning functions.� Information (I): This message informs you about the current data

situation.

If you do not set the indicator (check type 2), then the system assumes theobjects in the object selection are work areas, in Supply Chain Cockpit (SCC)terms. A work area is a quantity of objects in a planner�s area of responsibility.In this case, the system assigns the message type using less strict criteria: Ifonly the relevant start location exists in the object selection of a transportation lane,the message The target location of transportation lane XY is not found in the objectselection, that results from the model consistency check, is an error message in checktype 1, and a warning message in check type 2.



Model Consistency Check

1. SAP SCM menu Path: Advanced Planning and Optimization→Master Data→ Model Consistency Check → Maintain Profile

2. Create a profile SCM210_## ( GR##Demo) and Select Create

3. Select the following Settings:

� Location Checks� Resource Checks� Production Process Model Checks� General Checks (General Master Data)� Location Network

� General Checks (Transportation Lanes)� Existence of Products at Start and Destination Locations� Assignment of Location Products to Model� Qty Conversion of Transportation Costs� Transprt. Dstnce.� Trans. Duration� General Checks (Quota Arrangements)

4. SAP SCM menu Path: Advanced Planning and Optimization→Master Data→ Model Consistency Check → Model Consistency Check

5. Enter Planning Version 000, work area PUMP_SCM, Profile SCM210.

6. Select Execute and explain the log results by drilling down and reviewingany errors or warnings.



Lesson Summary

You should now be able to:� Explain what a model means in SAP SCM� Explain the use of Model consistency checks



Lesson: Versions in SAP SCM

Lesson OverviewThe active version is used to integrate planning with the SAP R/3 Systemor other transaction system. At times planners may want to run simulationplanning runs that will not affect the active plan. In this lesson we will createan inactive version for simulation planning purposes. In addition, we willinvestigate how the master data transfer interacts with these inactive versions.


� Explain what a version means in SAP SCM� Explain how SAP R/3 integrates with versions in SAP SCM

Business ExampleAssume your company has decided to implement SAP SCM for supply chainplanning. You need to explain the transaction data environment to users. Forcontinuous integrated planning, users use version 000. However, to assistusers to gain a better understanding of SAP SCM�s simulation environmentand version you use B## for model A##.

The Supply Chain VersionThe Supply Chain Model (abbreviation: Model) represents the entire supplychain network ranging from suppliers to production and distribution sites,through to the customer. It contains locations, transportation lanes, products,resources, and production process models. The model is therefore the basisfor all planning functions in SAP SCM. It only contains master data. Masterdata from SAP R/3 is automatically assigned to the active model (model 000)during the transfer to SAP SCM. The active model represents the supply chainactually used in the company. In this way, all the transferred master data isautomatically available for operational planning in model 000. You mustassign master data that you create manually in SAP SCM to a model. Forsimulation purposes, it is possible to create several planning versions for eachsupply chain model. However, only the model 000 and the planning version000 are active. The planning version contains version specific master dataand transaction data. In an inactive planning version, you can, for example,simulate increased planned independent requirements and plan productionbased on an increased demand. As of SCM 4.0 it is possible to copy an inactive


SCM210 Lesson: Versions in SAP SCM

version back to the active version 000 but both must belong to model 000. It isnot possible to copy versions across models. You can use version managementto copy models and planning versions, or create them manually. They mustbe uniquely identifiable, however, which means that two planning versionsin different models must have different names. The active planning version000 only exists in model 000.

Figure 103: Version Creation Screen

SNP: Net Change Planning Active -This indicator is only relevant for the active version. If you set thisindicator, a planning file entry is generated for the SNP heuristic foreach change that is relevant to Supply Network Planning (SNP). Aplanning-relevant change might be a change in the demand situation of alocation product. You have to set this indicator so that you can executethe SNP Heuristic in net change mode



SNP: No Planned Order Without PPM -This indicator is relevant only if procurement type E (in-houseproduction) has been specified for a location product,. The SNPoptimizer checks (during planning) if a production process model (PPM)exists for this product. You can use this indicator to specify the courseof action that you want the SNP optimizer take when there is no PPMfor the location product. If you set this indicator, the SNP optimizer willnot create any planned orders if a PPM does not exist. Instead it willcreate purchase requisitions. If you do not set this indicator, the SNPoptimizer creates planned orders even if no PPM exists and the plannedorder will not reference any PPM

Production Planning and Detailed Scheduling active -This specifies that the planning version is used for Production Planningand Detailed Scheduling (PP/DS). If you set this indicator, the SAPSCM system reacts to each planning-relevant change for a product,according to the planning procedure set in the location product master.For performance reasons, you should only set this indicator if you reallywant to work with PP/DS in this planning version.

PP/DS Horizon in Calendar Days -The system uses the PP/DS horizon for the planning version that is sethere if you have not specified a product-specific PP/DS horizon in thelocation product master.



Determination of Order Priorities in PP/DS -You have the following options for determining the priority of an orderin Production Planning and Detailed Scheduling (PP/DS):For make-to-order production from a sales order or from a product- Orders for products that you plan using a make-to-order planningstrategy adopt the priority of the sales order. Orders for products thatyou plan using a make-to-stock production strategy have the prioritythat is specified in the location product master.Always adopted from requirement -An order always adopts the priorityof the requirement that it was created to cover.For make-to-order production, the sales order adopts its priority fromall production levels and make-to-stock levels at which the dependentand stock transport requirements, and thus also the orders, that are tocover this requirement, are created.The make-to-stock levels are usually used for lot size creation; a suitableorder can be used to cover several requirements that have differentpriorities. Different priorities may result from changes to receipts orrequirements, since the dynamic pegging relationships can also changeif the receipts or requirements are changed. You can use the heuristicSAP_PP_013 to reprioritize the receipt elements.Orders that are created to cover planned independent requirements arenot prioritized, since the planned independent requirements do nothave a priority.Always adopt from product - An order has the priority that is specifiedin the location product master for the product created.

PP/DS No Order Without Source of Supply- If you set this indicator, the system does not create an order for aproduct in PP/DS if it cannot find a valid source of supply. If you do notset the indicator, the system creates an order without requirements andoperations if a valid source of supply cannot be found for a product.

Safety Stock Consideration -In this field, you define if and how Production Planning and DetailedScheduling (PP/DS) and Capable-to-Match (CTM) should take safetystock into consideration. You have the following options:

� Usage in PP/DS In this option, PP/DS does not take safety stockinto consideration.

� Usage in CTM This option has no effect on CTM planning. CTMtakes account of the Build up safety stock indicator in the CTMprofile.



� Usage in PP/DS: In this option, you can work in PP/DS with staticand dynamic safety stock methods. The safety stock of a locationproduct is represented by virtual safety stock elements (safety stockrequirements or safety stock receipts), which PP/DS only takes intoconsideration during the net requirements calculation but which donot exist as orders in SAP liveCache (therefore, they are virtual). Forthat reason, dynamic pegging cannot take safety stock elementsinto consideration and create dynamic pegging relationships tothem. Procurement planning in PP/DS therefore creates receipts fora static safety stock method, for example, to cover an uncoveredsafety stock requirement; however, dynamic pegging cannot createany dynamic pegging relationships between the safety stockrequirement and the receipts that could cover it. This results in"incorrect" over-coverage alerts for the receipts that have beencreated to cover the safety stock requirement. The missing peggingrelationships are not only relevant to the creation of alerts, but toall functions that evaluate dynamic pegging relationships. PP/DSoptimization cannot consider the requirements dates/times of thesafety stock during the optimization of delays, due to the missingpegging relationships, for example.

� Usage in CTM This option has no effect on CTM planning. CTMtakes account of the Build up safety stock indicator in the CTMprofile.

� Usage in PP/DS: You can only use this option in the standardsystem for make-to-stock production and static safety stockmethods (SB and SM). Using a heuristic, you create safety stockrequirements in SAP liveCache, on the basis of the algorithm/SAPAPO/HEU_PLAN_SAFETY_STOCK. The safety stock of alocation product is represented in SAP liveCache by an order ofthe type GC_OM_SAFETY_STOCK that consists of a requirementselement with the standard category SR in the standard system. Thiskind of safety stock requirement is not only taken into considerationby the net requirements calculation in PP/DS, but also by dynamicpegging. PP/DS does not consider virtual safety stock requirements.If, in this option, you want to work with dynamic safety stockmethods or with a scenario other than make-to-stock production,you use the BAdI /SAPAPO/RRP_SFTY_STK.

� Usage in CTM: You can only use this option in the standardsystem for make-to-stock production and static safety stockmethods (SB and SM). Using a heuristic, you create safetystock requirements in SAP liveCache, based on the algorithm/SAPAPO/HEU_PLAN_SAFETY_STOCK. The safety stock of a



location product is represented in SAP liveCache by an orderof the type GC_OM_SAFETY_STOCK, which consists of arequirements element with the category SR in the standard system.Dynamic pegging takes this kind of safety stock requirement intoconsideration. CTM planning handles safety stock requirementslike any other requirements in requirement prioritization. If youchoose this option, CTM ignores the Build up safety stock indicatorin the CTM profile.

Update from ATP Time Series -This indicator is only relevant for the active version (000) and can only beset during creation. If you need to make any changes, you must deletethe active version and create a new one. Set this indicator, so that theATP time series, which the product availability check uses, is updated. Ifyou do not want to use the product availability check in SAP SCM, youare advised not to switch on the ATP time series update. By doing thisyou improve system performance and increase memory capacity. If youdo want to use the product availability check in SAP SCM, you mustset the relevant indicator.

Local Time ZoneIf you want to use local time zones when planning in Supply NetworkPlanning (SNP), you must set this indicator. If you do not set it, you canonly plan in SNP with time zone UTC. If you do not set the indicator,enter, where possible, UTC in the corresponding time zone fields of thelocation and resource master, and in the planning calendar. If you do setthe indicator, use, where possible, the same time zone for the locationand the resource or for the location and the planning calendar.



Consider Stock Transfer Horizon of Source LocationIf you set this indicator, Supply Network Planning and Capable-to-Match(CTM) take into account the SNP stock transfer horizon of the sourcelocation. By default, this indicator is not set and the system takes intoaccount the SNP stock transfer horizon of the destination location. In amulti-sourcing environment, where demand is fulfilled from multiplesource locations, you can set this indicator to take better consideration ofthe SNP stock transfer horizon of different source locations and reducedelivery time, if necessary.

Note: If the SNP stock transfer horizon of the destination locationis longer than that of the source location, the system takes intoaccount the stock transfer horizon of the destination location.

Example: Two source locations deliver to one distribution center (DC).Source location A has an SNP stock transfer horizon of 3 days and sourcelocation B one of 5 days. If you set this indicator, the demand at theDC can be fulfilled after 3 days, if you do not set it, the demand will befulfilled after 5 days.

A version can be created either on line or in the background by choosingthe appropriate setting.



Creating Planning Versions

1. SAP SCMMenu Path: Advanced Planning and Optimization→Master Data→ Planning Version Management→Model and Version Management

2. Select version 000, then select Copy Model/Planning Version →Model/Version

3. Enter Version B## (GR## Demo Version)

4. Select Copy and Save

Caution: DO NOT EXECUTE! Training system may not haveenough resources allocated to perform this task.

Interaction of Version and Master Data ObjectsAs Master Data object are transferred from SAP R/3, they react with versiondifferently. In the next few pages, we will look at each data object and howit interacts with LiveCache versions in SAP SCM.

Figure 104: Locations and Products Interaction with Planning Versions

If locations and products are created in SAP SCM via the SAP R/3 -SAP SCMinterface, they are automatically created in the active planning version 000and assigned to the active model 000. If planning is simulated in an inactive



planning version (for example, planning version 001), the master data fieldsof the location and the product master of the active planning version 000are read (location and product in an inactive planning version thus refer tothe active planning version 000). If you want to use modified master data insimulated planning (for example, different MRP attributes of a product), youcan maintain certain fields specifically for the planning version in the locationor the product master in SAP SCM (manually or mass maintenance). Duringplanning in planning version 001, these version-specific fields from planningversion 001 are then read. For fields that are specific to a planning version, andcan be maintained as such, the system reads the fields from active planningversion 000 (reference) if no alternative settings have been made. If you alsowant to use certain locations and products in inactive models, you mustmanually assign these locations and products to the inactive model required.You can do so from within master data maintenance or via the Supply ChainEngineer. Within the inactive model, planning can be carried out in one orseveral inactive planning versions.

Figure 105: Resources Interaction with Planning Versions

If resources are created in SAP SCM via the SAP R/3 -SAP SCM interface,they are automatically created in a version that is independent of a planningversion (planning version "blank") and assigned to the active model 000. Inaddition, these planning version-independent resources are automaticallycopied into all planning versions (active planning version 000 as well as allinactive planning versions) that exist in this model during the master data



transfer. You are left with a planning version-independent resource, an activeplanning version resource, and some inactive planning version resources.When version management is used to create a new planning version at a laterstage, all resources are automatically copied to the new planning version (as acopy of the planning version-independent resource) when the new versionis created. If the same resource is transferred via the SAP R/3 -SAP interfaceagain, only the planning version-independent resource is overwritten inSAP SCM. The planning version-dependent resources (resources for activeand inactive planning versions) are not adjusted. If planning is simulated ina certain planning version (for example, in the active planning version 000or the inactive planning version 001), the resource master data fields in therelevant planning version are read. If you want to use modified master data inthe simulated planning (for example, different operating times of resources insimulation), you can change the resources specifically for a planning versionin SAP SCM. 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 ChainEngineer. When you assign the resource to the inactive model, the resource isautomatically created in all planning versions of the inactive model (copy ofthe planning version-independent resources to the planning version-specificresources of the active model).

Figure 106: PPM�s Interaction with Planning Versions



If PPMs are created in SAP SCM via the SAP R/3 -SAP SCM interface, they areautomatically assigned to the active model 000. However, the PPM is valid inall planning versions. This means it does not depend on a certain planningversion. The only exception are time-dependent parameters in PPM, such asscrap, resource consumption, material consumption (component quantity).You can plan them specifically for a planning version in SAP SCM but cannotuse the SAP R/3 -SAP SCM interface. If you simulate planning in an inactiveplanning version (for example, planning version 001), the same PPM is usedas for operational planning. Modified PPM fields for simulated planning onlyare 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 cando so from within master data maintenance or via the Supply Chain Engineer.



Lesson Summary

You should now be able to:� Explain what a version means in SAP SCM� Explain how SAP R/3 integrates with versions in SAP SCM



Lesson: Modeling with the Supply Chain Engineer

Lesson OverviewWith this component you can create and maintain supply chain networkmodels. The network model represents a specific supply chain and consists ofindividual nodes and links. A model can have different planning versions.You also have the option of creating several models, each with differentversions for simulation purposes.


� Explain the purpose of the supply chain engineer� Explain and demonstrate the user settings for the Supply Chain Engineer� Explain and demonstrate how the Supply Chain Engineer is used.

Business ExampleAssume your company is integrating SAP SCM with its existing SAP R/3system so that it can undertake more intensive supply chain modeling andplanning. Once your master data has been transferred from the SAP R/3 viathe Core Interface, users will have a need to maintain and expand their supplychain model. Instead of looking at individual pieces of the supply chain, userswill need to look at segments or areas of the supply chain. You need to allowusers to look at portions of the supply chain for which they are responsible.

Supply Chain Engineer (SCE)The Supply Chain Engineer is a fully integrated component of SAP SCMused for creating models. The model is the basis for all SAP SCM planningfunctions. It covers all areas of the network chain from supplier�s supplier, tocustomer�s customer, and is determined by importing the relevant data objectsfrom source systems into SAP SCM.


SCM210 Lesson: Modeling with the Supply Chain Engineer

Figure 107: Supply Chain Engineer

Figure 107: Supply Chain Engineer

Nodes and links are used to construct a supply chain model. A noderepresents a location, or business entity, in SAP SCM, and links betweenlocations are called transportation lanes. Locations include production plant,distribution center, customer, and supplier.

Besides locations and lanes, the model also allows you to keep track of othersupply chain elements including products, PPMs (production process models)and the following resources:

� handling� production� storage� transportation



Figure 108: Locations in the SCE

The SCE enables you to view data pertaining to the different elements in yourchain. You can submit queries for information on individual or combinedelements in the chain. For example, you can query for a list of all productsassigned to a specific location in your model. You can also perform massmaintenance of product attributes



Navigating the SCE

1. SAP SCM menu path:Advanced Planning and Optimization→Master Data→ Supply Chain Engineer → Maintain Model

2. Enter Model 000 and work are PUMP and select Display Model

3. In the bottom half of the screen, drill down under location, select plant1000, and right mouse click Change→ Location then return to SCE

4. In the work area, choose the Location Products button.

5. Locate product P-102 at location 1000

6. In the Network graphic, select location 1000, right mouse click Queries→Transportation Net (Map)

Users Settings in the SCEEvery supply chain planner will look at data differently. In order toaccommodate each individual�s preferences, user specific settings can betailored to enhance the view of the supply chain.



Figure 109: General User SettingsFigure 109: General User Settings

In the General Settings view, users can define how they want to see theirmaster data objects:

Display Maintenance Objects

Use work area as a filter for graphical displaySet this flag if you want only the objects of the model that are also in thework area to appear on the map. Otherwise, all locations are displayedwhether or not they are assigned to the work area.

Use HierarchiesSet this flag is you want to use hierarchies in the Supply Chain Cockpitand Engineer.

Use Work Area for Hierarchy DisplaySet this flag if you want only the objects in your work area to be displayedon the map.



Figure 110: Model Maintenance FeaturesFigure 110: Model Maintenance Features

The settings in the model maintenance view are to speed up the inclusion ofmaster data. Users will use the SCE for one of two things:

1. View a segment of the �Active�supply chain. Active meaning that masterdata that is integrated with the ERP/exection system.

2. Build a simulation model to adjust the supply chain due to strategicchanges. For example, buying and new piece of equipment, buildinga new distribution center, launching a new product line with limitedcapital investment.

Assign Dependent ObjectsSet this indicator for automatic assignment/deletion of dependentobjects to and from a model to assure model consistency. When youassign or delete an object to or from a model, all its dependent objectsare automatically included in the activity. Example: If you assigna production process model (PPM) to your supply chain model, allresources and products attached to it will also be assigned to the model.



Include dependent location products when assigning locationIf you set this indicator, all location products assigned to a locationare automatically assigned to a model when you assign the location.Automatic assignment of objects ensures model consistency.

Include dependent resources when assigning a locationYou set this indicator, all resources assigned to a location areautomatically assigned to a model when you assign the location.Automatic assignment of objects ensures model consistency

Include dependent PPMs when assigning locationIf you set this indicator, all PPMs assigned to a location are automaticallyassigned to a model when you assign the location. Automatic assignmentensures model consistency

Maintain Geographical coordinatesIf you set this indicator, whenever you move locations on the map youwill get a popup asking you to confirm the geographical coordinates.If you do not set the indicator, the system automatically assigns thecoordinates.

Caution: By allowing users to change geographic coordinates,they can also impact the distance and duration that can becalculated in the dependent transportation lane.



Figure 111: Query settings for the userFigure 111: Query settings for the user

While viewing the supply chain several queries or reports can be generatedagainst the master data. For example, if a user wants to know whichtransportation lanes a product can flow across they can run a query and geta text report, or have the network map highlight which transportation lanesthe product can move across.

Users can look at the query based on a relative time interval or a fixed timeinterval. A relative time interval will use the current date as a starting pointand calculate the number of specified periods going forward. To use a fixedtime interval users must select �absolute� or a specific date range to vie thedata.



Figure 112: Selection Dialog BoxFigure 112: Selection Dialog Box

Users will also be able to distinguish which type of dialog box they wish to usewhen selecting data for a query. By choosing 0 or blank the SAP default willcome up. By using 1 or 2 the dialog box can contain date and time information.

Note: The user will be able to change some of these settings fromwithin the SCE but not all settings are available.

The Supply Chain Engineer ScreenThe Supply Chain Engineer screen provides an overview of your model. Hereyou perform the following tasks

� supply chain model maintenance� transportation lane maintenance� launching of queries� viewing quota arrangements



Figure 113: Make up of the SCE

The SCE screen is divided in the following way:

� Header toolbar� The right panel displays the current graphical or logical depiction of the

supply chain is displayed.� The left panel displays a tree structure which allows users to view the

objects in your work area selection. Users can navigate to detailed viewsof the master data objects or run master data queries.

Header BarThe Supply Chain Engineer relies heavily on graphics to view a large amountof information at once. The header tool bar helps users define the model orportion of the model they are working with

- Switch to Display mode: Allows the user to toggle betweendisplay/change mode

- Model and Version Management: go to model/version management



- Objects in Model: display list of all objects in the model

- Add objects to model: Add selected objects to model

- Delete objects in model: Delete selected objects from model

- Add dependent objects to model: For items like a location, it will add allproduct masters that exist in that location.

The Work AreaViewing your entire supply chain at once can be cumbersome. You canlimit your view to those supply chain objects you want to concentrate onby defining work areas. The defined work area is the basis for the queriesthrough which you retrieve information from the SAP SCM system on allaspects of your supply chain. The transportation lanes in your work area aredetermined by the model you are working in. For all intensive purposes thework area will be a sub-set of your model.

Figure 114: Work Areas

Upon entering the SCE users can choose between an existing work area, orcreating a new work area. Once a work area is selected, if a user wishes toswitch between work areas they will need to exit and re-enter the SCE andchoose another work area. In order to create a new work area users must add



objects as needed ( Work Area → Add Objects). Upon adding all necessaryobjects users must save the work area with an id ( Work Area → Save WorkArea as.....).

Graphics windowIn the left window users can see the master data in a text version. In thewindow on the right users can see their locations laid out geographically orlogically. By right mouse clicking on any of the objects in the graphics window,users can run queries, display or change master data via a context menu.

Figure 115: Graphics windowFigure 115: Graphics window

The graphics window is interactive and can be used in conjunction with thework area window to the left. For example, by selecting a location on themap, and selecting a product from the work area on the left, with a rightmouse click the user can get to product/location specific queries or masterdata with out having to type.

Users will also have the opportunity to create data. Currently only quotaarrangements and transportation lanes can be created in the SCE. All masterdata can be updated individually or through mass processing in the SCE.



- fit to objects centers all objects in the display

- zoom in shows model details

- zoom in and out shows model overview

- Switches to the world overview

- switch overview opens a small window showing model�s global position

- show layer dialog opens the map maintenance screen. You can use mapsother than those provided with the standard application. First, save the mapfiles locally, then activate the Add function button in the map maintenancescreen to add map layers. In this screen you can also customize the fill andline colors on the map as well as the width of the lines

- filter allows you to filter objects displayed on the map, just plantsand DCs.

- select allows you to select a location on the map, possibly to run aquery on.

- highlight the in and outbound lanes of a location by selecting thelocation and activating this icon

- move a location that you have first selected

- connect icon for creating lanes between locations (select location first,click on connect, draw line to other location, lane maintenance screen appears)

- switch lane display will create lanes around objects versus goingthrough them.

Other navigation features of the map are:

� By moving your mouse toward the edges of the box an arrow will appear.Click the left mouse button and the map will move in that direction

� Hold down the left mouse button and drag the mouse to create a window.This will zoom in on the details within the window created by the mouse.



Lesson Summary

You should now be able to:� Explain the purpose of the supply chain engineer� Explain and demonstrate the user settings for the Supply Chain Engineer� Explain and demonstrate how the Supply Chain Engineer is used.


Unit Summary SCM210

Unit SummaryYou should now be able to:� Explain what a model means in SAP SCM� Explain the use of Model consistency checks� Explain what a version means in SAP SCM� Explain how SAP R/3 integrates with versions in SAP SCM� Explain the purpose of the supply chain engineer� Explain and demonstrate the user settings for the Supply Chain Engineer� Explain and demonstrate how the Supply Chain Engineer is used.



Test Your Knowledge

1. Model represents the Active model which is updated by theCIF from SAP R/3.Fill in the blanks to complete the sentence.

2. Inn SAP SCM, users can activate more than one model?Determine whether this statement is true or false.□ True□ False

3. Model Consistency checks are only applicable for the "active" model?Determine whether this statement is true or false.□ True□ False

4. The purpose of the SCE is to review your planning situation and makeadjustments as necessary?Determine whether this statement is true or false.□ True□ False

5. Select the following items that can be created in the SCE:Choose the correct answer(s).□ A Quota Arrangements□ B Products□ C Transportation Lanes□ D PPMs□ E Resources



Answers

1. Model 000 represents the Active model which is updated by the CIFfrom SAP R/3.

Answer: 000

2. Inn SAP SCM, users can activate more than one model?

Answer: False

Model 000 is the only allowed "Active" model. All other models aresimulation models.

3. Model Consistency checks are only applicable for the "active" model?

Answer: False

Model consistency checks are applicable to all models. It�s purpose isto ensure that any dependent master data is assigned to the model tosupport the necessary planning functions.

4. The purpose of the SCE is to review your planning situation and makeadjustments as necessary?

Answer: False

The purpose of the SCE is to review and manage your master data modelIt allows as user to graphically review all the interdepencies that allowthe supply and demand to flow up and down the supply chain.

5. Select the following items that can be created in the SCE:

Answer: A, C

Products, Resources, and PPMs can be changes or added to model, butcan not be created. Transportation lanes and Quota Arrangements areModel Dependent Data.


Unit 4Integrating Transactional Data

Unit OverviewThis particular unit will deal with setting up transaction data transfer. Thissetup will be different than master data due to it�s bi-directional nature. Thiswill include configuration on the SAP SCM system to intiate the return ofplanning data for execution.


� Discuss the general concept of transactional data integration� Identify the necessary configuration to send transactional data between

an SAP R/3 system and an SAP SCM system (bi-directional)� Transfer transactional data from SAP SCM to SAP R/3� Create integration models for transfer of transactional data using SAP


Unit ContentsLesson: Setting up Transactional Data Transfer. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .264

Procedure: ATP Categories in SAP SCM ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .267Procedure: SAP SCM Transactional Data Publication Settings.. . . . . . . . .273Exercise 7: Transferring planned orders .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .275

Lesson: Generating and Activating Integration Models... . . . . . . . . . . . . . . . . . . . . .282Exercise 8: Transfer of Master Data ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .289


Unit 4: Integrating Transactional Data SCM210

Lesson: Setting up Transactional Data Transfer

Lesson OverviewIn addition to setting up the master data integration, the transactional dataintegration must also be set up using an integration model.


� Discuss the general concept of transactional data integration� Identify the necessary configuration to send transactional data between

an SAP R/3 system and an SAP SCM system (bi-directional)� Transfer transactional data from SAP SCM to SAP R/3

Business ExampleAssume your company is integrating SAP SCM with its existing SAP R/3system so that it can undertake more intensive supply chain modeling andplanning. In order to complete this integration and finalize your SCMsolution, you must be able to transfer the planning results from SAP SCM,back to your SAP R/3 system. Therefore you must, configure the SAP SCMsystem to pass the data back to the appropriate execution instance (SAP R/3).

Overview of Transactional Data IntegrationThe selection of transaction data that the system transfers to SAP SCM isdetermined in an integration model that you define in the SAP R/3 System. Alltransaction data is mapped to orders in SAP SCM, which are distinguishedby their ATP category.


SCM210 Lesson: Setting up Transactional Data Transfer

Figure 116: Transaction Data Objects of the CIF

In SAP R/3 the different transactional data elements are referred to as MRPElements. Through the use of the core interface each MRP Element will bemapped to one or more ATP Categories. The CIF interprets the MRP elementand potentially the MRP element status to MAP to the appropriate ATPCategory.

Figure 117: ATP CategoriesFigure 117: ATP Categories



In SAP R/3 there is only one MRP Element for a production order. However,production orders have system statuses, for example created (CRTD) andreleased (REL). The CIF reviews the system status of the orders and mapsthem to the corresponding ATP Category.



ATP Categories in SAP SCM

1. SAP SCM menu Path: SPRO→ Reference IMG→ Advanced Planning andOptimization→ Global Available to Promise→ General Settings→MaintainCategory

2. Select ATP category AC and AD and select Details

Setting up Transactional Data Transfer from SAP SCM

Figure 118: SAP SCM Data Transfer

First, the initial data transfer of transaction data takes place through theCore Interface. As a rule, the change transfer between SAP R/3 and SAPSCM flows automatically for transaction data objects belonging to an activeintegration model. New transaction data or changes to existing transactiondata are transferred automatically. The SAP SCM transaction data objects arenot generally identical to those in SAP R/3. The system transfers various SAPR/3 transaction data into SAP SCM as orders that differ by ATP category.Planned independent requirements can only be transferred from SAP R/3 toSAP SCM through CIF. The transfer of planned independent requirementsfrom SAP SCM to SAP R/3 must be triggered from demand planning in SAPSCM using a separate transaction. You can specify in SAP SCM that plannedorders and purchase requisitions are only transferred from SAP SCM to SAPR/3 if the conversion indicator has been set.



Figure 119: Publication DefinitionsFigure 119: Publication Definitions

Prior to initiating any data transfer, several settings must be made in SAP SCMto allow data to be transmitted to the OLTP systems. The first configuration istoMaintain Distribution Definitions, which authorizes SAP SCM to transmitvarious liveCache order types to the respective OLTP system.

� 021 - External Procurement� 026 - Confirmation for Scheduling Agreement� 031 - In-house Production� 033 - Work Package Maintenance� 051 - Planned Independent Requirements� 053 - Sales Order� 300 - Production Campaign� 310- Planning File Entry (IS Automotive)� 330 - Shipment� 340 - Delivery� 350 - Confirmation (IS Automotive)� 351 - Confirmations of Deletions (IS Automotive)� 352 - Reporting Points (IS Automotive)� 360 - Reservations



In order to pass these objects back to SAP R/3 you must allow each ordertype by location and logical system to transfer. An entry in this table is anauthorization to transmit data. With transaction /SAPAPO/CP2, companiescan mass maintain the distribution definitions.

Figure 120: Object Specific Settings for PublicationFigure 120: Object Specific Settings for Publication

In addition defining the distribution, companies can also configure transfersettings for the in-house order type transfers. The Re-transfer setting, for thein-house production object type, defines in which cases changes made toplanned or manufacturing orders in SAP R/3, which lead to rescheduling inSAP SCM , should automatically be re-transferred to SAP R/3. The options are:

No Re-transferChanged planned orders will not be transferred to SAP R/3.

Always Re-transferObjects changed in SAP R/3 are re-transferred to SAP R/3 both after theinitial data transfer to SAP SCM and after online transfer. This settinghas a negative effect on performance during the initial data supply.Therefore you should check whether your business processes actuallyneed this setting. A retransfer after an initial data supply is not requiredif you only want to carry out optimization in SAP SCM after the initialdata supply, for example.



Only Re-transfer after online transferObjects changed in SAP R/3 are only retransferred to SAP R/3 after onlinetransfer to SAP SCM (that is, after manual changes to SAP R/3 orders).There is no retransfer after the initial data supply. This setting can alsohave a negative effect on performance. For example, this setting is notrecommended if your business process involves a daily optimizationusing an optimization run in SAP SCM and SAP R/3 is supposed to adoptthe results of this optimization run.

Figure 121: Transactional Data Publication SettingsFigure 121: Transactional Data Publication Settings

In the SAP SCM transaction User Settings (transaction code /SAPAPO/C4) youcan set the format in which the new SAP SCM transaction data (planningresults) is transferred to SAP R/3. The transfer usually takes place for PP/DSin real-time (default setting for PP/DS data). There is also the possibility ofcollecting the changes, then transferring them to SAP R/3 in a second step(transaction Process change pointer /SAPAPO/C5).



Figure 122: SNP Transfer SettingsFigure 122: SNP Transfer Settings

The default setting for SNP ensures that the changes are collected andtransferred periodically. For the real-time transfer of SNP planning results,you set the form for transferring planning results to SAP R/3 with theCustomizing operation: Set transfer to OLTP system.

� No Transfer - All planning is self contained in SAP SCM and onlyexecution or short term plans will be passed to SAP R/3

� Periodic Transfer - SNP is not run that frequently (once a week) so theplans will be transferred when system is idle

� Immediate Transfer - SNP is generating short term plans which will needto executed in a short time horizon

Due to the fact that SNP is a mid to long range planning tool, companiesneed the opportunity to queue up the changes and transfer to the OLTPsystem when the system load is smaller (evenings or weekends). However,deployment (DEPL) and truck load builder (TLB) use the SNP data format, yet



they are often performed in the short term and by the logistics execution (LES)group. Therefore companies need to control the data transfer in accordancewith their business process.

� No Transfer - All planning is self contained in SAP SCM and only stocktransfer orders (STO) will be passed to SAP R/3

� Periodic Transfer - Deployment is not run that frequently (once a week)so the plans will be transferred when system is idle

� Immediate Transfer - Deployment is generating short term plans whichwill need to executed in the near term horizon

� Purchase Requisition - Upon executing deployment SAP SCM will create�confirmed� stock transfer requests. TLB will be handling the generationof STOs

� Purchase Order - Your company is not using TLB to generate StockTransfer Orders, so you wish deployment to handle this step.

� VMI Settings - These settings are only relevant if you are performingdeployment from a plant or DC to a Customer location in SAP SCM. Youwill identify that SNP will be generating special orders inside of SAPSCM in anticipation of and SAP R/3 sales order.

� No Transfer - TLB is not being used to generate Stock Transfer Orders� Periodic Transfer - TLB is running far into the future so the plans will

be transferred when system is idle� Immediate Transfer - TLB is generating short term plans which will need

to executed in the near term horizon by SAP R/3 LES



SAP SCM Transactional Data Publication Settings

1. SAP SCM menu Path: SPRO→ Reference IMG→ Advanced Planning andOptimization → Basis Settings → Integration → Publication → MaintainDistribution Definition

2. Select publication type and perform a drop down to see the field options.

3. SAP SCM menu Path: SPRO→ Reference IMG→ Advanced Planning andOptimization→ Basis Settings→ Integration→ Publication→ Generate andDelete Distribution Definition

4. Review the settings so you can mass maintain the distribution definitions.

5. SAP SCM menu Path: SPRO→ Reference IMG→ Advanced Planning andOptimization → Basis Settings → Integration → Publication → MaintainObject Specific Settings

6. Perform a drop down on the �Re-transfer Settings �to review the fieldoptions

7. SAP SCM menu Path: SPRO→ Reference IMG→ Advanced Planning andOptimization→ Supply Chain Planning→ Supply Network Planning (SNP)→ Basic Settings → Configure Transfer to OLTP Systems

8. Discuss field options. Make sure to point out that the purchase re/ordersettings are to determine if DEPL will create STRs or STOs.

9. Create a new session and SAP SCM menu Path: Advanced Planning andOptimization → APO Administration→ Integration → Settings → UsersSettings

10. Discuss field options for recording

11. Create a new session and SAP SCM menu Path: Advanced Planning andOptimization → APO Administration→ Integration → Settings → UsersSettings

Integration of Transaction DataTo transfer transaction data between SAP R/3 and SAP SCM , you mustactivate an integration model. You activate an integration model with theActivate Integration Model transaction (transaction code CFM2) in the CIF.



Figure 123: Activate Integration Model for Transaction Data

It is useful to have several integration models active at a time with differenttransactional data objects in each one. Choose the Start function to triggerthe initial data transfer. This means that the transaction data you haveselected is transferred into SAP SCM for the first time. This initial transfer isautomatically followed by the real-time link between SAP R/3 and SAP SCM.This means that once a selected storage location stock of a material changesdue to a goods movement posting, the new stock is transferred to SAP SCM.

1. Stocks (special stock → relevant customers/suppliers)2. Sales Orders3. Purchase orders and purchase requisitions4. Production/Process/Planned orders (mfg)5. Manual reservations and planned independent requirements6. Production campaign and Process/planned orders7. Shipments



Exercise 7: Transferring planned orders

Exercise ObjectivesAfter completing this exercise, you will be able to:� Explain the result of planned orders and production order transfers

between SAP SCM and the SAP R/3 Enterprise

Business ExampleCurrently, the transaction data is maintained in a decentralized pattern inyour SAP R/3 system. As a planning manager, you need to transfer thistransaction data to a centralized SAP SCM System for detailed planningacross the company.

Task 1: Current planning positionPrior to integrating your transactional data SAP SCM system to your SAP R/3system, identify your current planning situation.

1. View the current planning situation of the material T-F2## in plant 1000 inSAP R/3. Then call up the current stock/requirements list of the material.

2. Do planned or production orders exist for the material?

3. How high is the current plant stock level?

Task 2: SAP SCM and SAP R/3 transactional dataintegrationAs a production planner you need to better understand how the two systemsintegrate in a real time fashion with transactional data, create data in yourSAP SCM system and review the changes in SAP R/3.

1. Call up the product view.

Planning Version: 000

Product: T-F2##

Location: 1000

Confirm current messages using Enter and enter the product view. Onthe tab page Elements, the current planning elements are displayed.What is the warehouse stock level?





3. From the product view enter change mode and create a planned orderfor 5 pieces with an availability date of one week from today. Copy thesuggested propagation range (SAPALL) with Save.

4. What is the number of the order you have just created?

5. Refresh the Product view. What is the number of the planned order now?

Task 3: Integration TestAs a production planner you need to be aware of the speed and accuracy ofthe data transfer. Review the results in SAP R/3.

1. Now go to the current stock/requirements list of materials T-F2## atplant 1000 is SAP R/3 and refresh the list.

Is a planned order displayed?

2. What is the availability date of the planned order and how high is theorder quantity?

3. Finally, note the number of the planned order:

Make sure that the number in SAP SCM is the same as the order numberthat you noted in task 1, 2 and 3.

4. Return to the product view in SAP SCM,and then go to the changemode again. Select your planned order and set the conversion indicatorby clicking the corresponding button. This indicator means that theplanned order is converted into a production order. Save the productview in SAP SCM, and then update it.

What is the (new) number of the SAP SCM order?

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



Solution 7: Transferring planned ordersTask 1: Current planning positionPrior to integrating your transactional data SAP SCM system to your SAP R/3system, identify your current planning situation.

1. View the current planning situation of the material T-F2## in plant 1000 inSAP R/3. Then call up the current stock/requirements list of the material.

a) In the SAP R/3 , select Logistics → Production → MRP →Evaluations → Stock/Requirements List (MD04) .

2. Do planned or production orders exist for the material?

a) No, there are no planned or production orders available.


a) Current plant stock: 0 pieces

Hint: Call up the current stock/requirements list of thematerial, so that you can view the result at the same time asthe planning data in SAP SCM.

Task 2: SAP SCM and SAP R/3 transactional dataintegrationAs a production planner you need to better understand how the two systemsintegrate in a real time fashion with transactional data, create data in yourSAP SCM system and review the changes in SAP R/3.

1. Call up the product view.

Planning Version: 000

Product: T-F2##

Location: 1000

Confirm current messages using Enter and enter the product view. Onthe tab page Elements, the current planning elements are displayed.What is the warehouse stock level?

a) In the SAP SCM System, select: Advanced Planning andOptimization → Production Planning → Interactive ProductionPlanning → Product View





a) Stock level: 0 pieces

3. From the product view enter change mode and create a planned orderfor 5 pieces with an availability date of one week from today. Copy thesuggested propagation range (SAPALL) with Save.

a) Select Changeb) Now click the button Create order and create the following data for

the order:

Field ValuePlanning Version 000

Product: T-F2##

Location: 1000

Receipt/Reqmts Quantity 5 pieces

: Start Date: Delete entry

Avail/Reqmt Date week today

c) Select Save

4. What is the number of the order you have just created?

Answer: Order number: Varied, for example 61109

5. Refresh the Product view. What is the number of the planned order now?

a) Select Updateb) Current order number: Varied, for example 29423

Hint: The planned order is transferred from SAP SCM toSAP R/3 and then provided with the SAP R/3 planned ordernumber. This number is then transferred from the SAP SCMSystem for the corresponding planned order. According tothe system load, this operation may take a while. It maytherefore be necessary to update the product view severaltimes, until the planned order is displayed with its newnumber.




Task 3: Integration TestAs a production planner you need to be aware of the speed and accuracy ofthe data transfer. Review the results in SAP R/3.

1. Now go to the current stock/requirements list of materials T-F2## atplant 1000 is SAP R/3 and refresh the list.

Is a planned order displayed?

a) In the SAP R/3 , select Logistics → Production → MRP →Evaluations → Stock/Requirements List (MD04) .

b) Planned order displayed: Yes, a firm planned order is displayed.

2. What is the availability date of the planned order and how high is theorder quantity?

a) Availability date and order quantity: The planned order with aquantity of 5 pieces is available a week from today. (If this dayis not a workday, then the next workday).

3. Finally, note the number of the planned order:

Make sure that the number in SAP SCM is the same as the order numberthat you noted in task 1, 2 and 3.

a) Planned order number: Varied, for example 29423 (as above)

4. Return to the product view in SAP SCM,and then go to the changemode again. Select your planned order and set the conversion indicatorby clicking the corresponding button. This indicator means that theplanned order is converted into a production order. Save the productview in SAP SCM, and then update it.

What is the (new) number of the SAP SCM order?

a) New number of SAP SCM order: Varied, for example 60002440

Hint: The planned order with a conversion indicator istransferred from SAP SCM into SAP R/3 as a productionorder, and provided with the SAP R/3 production ordernumber. This number is then transferred from the SAP SCMSystem for the corresponding planned order. According tothe system load, this operation may take a while. It maytherefore be necessary to update the product view severaltimes, until the order is displayed with its new number.




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

a)



Lesson Summary

You should now be able to:� Discuss the general concept of transactional data integration� Identify the necessary configuration to send transactional data between

an SAP R/3 system and an SAP SCM system (bi-directional)� Transfer transactional data from SAP SCM to SAP R/3



Lesson: Generating and Activating Integration Models

Lesson OverviewAfter the RFC connection is set up between the SAP R/3 System and the SAPSCM System, an integration model controls the data objects that integrate.


� Create integration models for transfer of transactional data using SAPrecommended selection methods.

� Activate integration models for transfer of transactional data.

Business ExamplePlanning elements must be transferred from the SAP R/3 system to theSAP SCM system to derive a proper production plan. Upon completinga production plan, the results must be transferred back to the SAP R/3system to perform additional planning via MRP, or actual manufacturingor procurement activities. Now that you have reviewed the necessaryconfiguration to start the integration of transactional data between and SAPSCM system and an SAP R/3 system, you need to trigger the actual transfer ofthat data. In order to accomplish the bi-directional flow of transactional datayou will setup and activate an integration model for the necessary objects.

Integration Models: Creating and ActivatingThe data transfer between the SAP R/3 and SAP SCM systems is defined andcontrolled using the Core Interface (CIF). The CIF is the central interface forconnecting SAP SCM to the existing SAP R/3 system environment. An RFCconnection with the SAP R/3 System is a technical requirement for successfuldata transfer to SAP SCM using the Core Interface. The CIF interface is anadd-on to the SAP R/3 System that you install using the relevant plug-in. Theexact installation process is dependent, amongst other things, on the SAP R/3release you are working with. You can find current detailed information onplug-ins in SAPNet, under the alias /R3-plug-in. The selection of master datathat the system transfers to SAP SCM is determined in an integration modelthat you define in the SAP R/3 System.



Figure 124: Master Data Interface: Core Interface (CIF)

The Core Interface is a real-time interface. Only the data objects needed in thedata structures reconciled in planning in SAP SCM for the particular planningand optimization processes are transferred from the complex data set in SAPR/3 to SAP SCM. Both the initial data transfer (initial transfer) and the transferof data changes to SAP SCM are made through the Core Interface. The masterdata objects in SAP SCM are not identical to those in SAP R/3. During masterdata transfer, the relevant SAP R/3 master data is usually mapped ontocorresponding SAP SCM planning master data. The SAP R/3 system is alwaysthe dominant system for master data. Only specific SAP SCMmaster data thatdoes not exist in SAP R/3 is maintained directly in SAP SCM .



Figure 125: Master Data Objects of the CIF

You define the integration model that controls the transfer of master andtransaction data in the SAP R/3 System. You can find the menu option CoreInterface Advanced Planner and Optimizer (the CIF menu) under Logistics→Central Functions → Supply Chain Planning Interface. The integration modeldistinguishes between each data object. SAP recommends that you organizeyour integration models according to the list published in the CIF: Tips andTricks document. In the integration model, you select the data set that youwant to transfer. You specify the following in the integration model. TheSAP SCM target system for the data transfer - The data objects you want totransfer. You can delete integration models that you no longer need. Note thatyou must first deactivate these integration models.



Figure 126: Initial Data Transfer of Master Data: Overview

The master data that the system will transfer for the first time (initialtransfer), from the SAP R/3 System into the SAP SCM System, is defined in anintegration model. This integration model is generated in the SAP R/3 Systemusing transaction CFM1. An integration model is uniquely defined by itsname and application. It is useful to create several integration models withthe same name but as different applications. This will help ensure that thedata pools of your integration models are generally not too big. This enablesyou to handle errors more easily. The target system that you specify in theintegration model determines the SAP SCM System that the master data istransferred into. The target system is a logical ( SAP SCM) system that musthave an RFC connection. Finally, you use a particular integration model tospecify which master data you want the system to transfer. To do so, you firstspecify the master data types that flow into the integration model. In thesecond step, you specify the selection criteria to be used for the selection of theindividual master data documents in the SAP R/3 System. You complete thegeneration of the integration model by "executing" the model (this means thatthe data objects of the model are compiled) and then you save it.



Figure 127: Generate Integration Model for Initial Data TransferFigure 127: Generate Integration Model for Initial Data Transfer

To transfer data into SAP SCM, you must activate an integration model thathas previously been generated. You activate an integration model with theActivate Integration Model transaction (transaction code CFM2) in the CIF. Itis useful to have several integration models active at a time. Choose the Startfunction to trigger the initial data transfer into SAP SCM: The master data,or the equivalent of the SAP SCM master data in SAP SCM, exists in the SAPSCM System. Basically, only the master data that was not available in anyother active integration model is transferred (delta comparison). To be ableto carry out the delta matching that was executed during activation of anintegration model quickly, the system refers to the runtime version of theintegration models. The runtime version is formed in the background fromall active integration models, each with one object type and target system,formatted optimally and saved to the database. It is automatically updatedduring the activation of new models. You can access the runtime versionmanually from report RCIFIMAX. The initial data transfer usually runs in aparticular order: the objects are selected successively, transferred to SAP SCMand processed there in this sequence. For improved system performance, itis also possible to execute a parallel initial data transfer: several integrationmodels can be activated at the same time. You can set during parallel



processing whether to run the selection in SAP R/3, processing in SAP SCM orboth at the same time. Parallel processing takes place within an object type,whereas the different object types are still transferred in sequence.

Figure 128: Selection Criteria for MRP Type X0

Planning is not necessarily executed for all materials in SAP SCM. Planning forcritical materials can take place in SAP SCM, while less critical materials (suchas consumption-controlled purchasing materials) are planned exclusively inSAP R/3. Materials planned in SAP SCM should not be planned again in SAPR/3 - the planning result from SAP SCM is transferred directly in the formof planned or production orders to SAP R/3. However, for materials with aBOM, You should assign these materials a special MRP type with the MRPprocedure "X" ("without MRP, with BOM explosion"). This will ensure thatdependent requirements will be created in the SAP R/3 system for non-SAPSCM-relevant components. (This MRP procedure is available as of 4.0; if youwork with earlier releases, use MRP type "P4" with a planning time fenceof 999 days). It is also possible to use the MRP type X0 to select materialsrelevant for SAP SCM in the integration model. If you give materials that areto be planned in SAP SCM a special plant-specific material status, you canuse the material status to limit the selection further. In general, you shouldbe careful about separating SAP SCM-relevant materials from those that arenot SAP SCM-relevant: For effective planning in SAP SCM, you must be surethat all materials important for the planning process are actually planned



in SAP SCM. (Take capacity planning as an example: If the capacities areto be planned for the different resources in SAP SCM, all materials that areproduced on these resources must be planned in SAP SCM.)

Figure 129: Activate Integration Model for Initial Data Transfer



Exercise 8: Transfer of Master Data

Exercise ObjectivesAfter completing this exercise, you will be able to:� Prepare SAP R/3 material masters for planning in SAP SCM� Create an integration model for the initial data transfer and execute the

transfer

Business ExamplePrecision Petrol Pump company constitutes a number of independent businessunits located in different parts of the world. Each unit is headed by a businessunit head and operates as an independent entity under the parent company.As part of a move to centralize planning functions in SAP SCM, you musttransfers data from you SAP R/3 system to the SAP SCM system.

to initiate this transfer you will create an integration model that will select therelevant master data for integration to SAP SCM and activate this model.



Task 1: Review the Configuration of MRP Type X0To expedite the transfer of master data you wish to select the SAP SCMrelevant master data by filtering off of several field settings in the variousmaster data objects. When transferring the Material Master your plannerswill use the MRP type X0 to select SAP R/3 materials masters that need tobe transferred to SAP SCM.











Field Data

Model Name PUMP##















Solution 8: Transfer of Master DataTask 1: Review the Configuration of MRP Type X0To expedite the transfer of master data you wish to select the SAP SCMrelevant master data by filtering off of several field settings in the variousmaster data objects. When transferring the Material Master your plannerswill use the MRP type X0 to select SAP R/3 materials masters that need tobe transferred to SAP SCM.


Answer: MRP Type X0 has MRP procedure X, Without MRP, with BOMexplosion assigned to it.Display the configuration of the MRP type X0 by first going to the IMG ofthe SAP R/3 System using the menu path Tools → Customizing → IMG

→ Edit Project. Once in the IMG click the buttonon the tool bar to access the SAP Reference IMG. In the SAP ReferenceIMG use the menu path Production→Material Requirements Planning→Master Data → Check MRP Types.

Select the MRP Type X0 and click the button on the tool bar or simplydouble click on MRP Type X0.


Answer: This MRP procedure means that the corresponding materialswill not be planned in the SAP R/3 System during any MRP/MPSplanning runs. Note this setting is only relevant if you have items on theBOM that are still planned in SAP R/3. If a BOM change takes place toan SAP R/3 relevant item on the BOM, existing planned orders must beadjust to reflect the BOM changes. During the next SAP R/3 planningrun all existing planned orders will have the BOM re-exploded so thatthe SAP R/3 relevant changes can be consider and planned. No headerinformation on the planned order will change since this will be controlledby the orders in SAP SCM. If all items on the BOM are SAP SCM relevant,consider using MRP type ND (No Planning).


Answer: The Planning method assigned to MRP Type X0 is 1, Plannedby external system. Check the Additional selection parameters section tofind this information.






a) Menu path in the SAP R/3 Enterprise: Logistics → Production→ Master Data → Material Master → Material → Change →Immediately. (MM02)

b) Enter Material number T-F1##, and pressENTER.c) SelectMRP 1 view, and press ENTER.d) Enter Plant 1000, and press ENTER.e) Change the MRP type toX0, and the MRP Controller to 0##f) Select SAVE






Field Data

Model Name PUMP##



a) From the SAP R/3 main menu choose Logistics→ Central Functions→ Supply Chain Planning Interface→ Core Interface Advanced Planningand Optimizer→ Integration Model→ Generate→ Create

b) Enter the data in the above table in the header fields.c) Select theMaterials indicator on the left side of the screen.d) Enter the selection criteria in the table below, on the right side in the

general selections for materials section. Leave all other fields blank.

Field Data

Plnt 1000

MRP Ctrlr 0##

MRP Type X0

e) Execute .f) On the next screen click the button. You can check which

materials were selected by double clicking on the Materials line.

Note: Only when the message �Integration model PUMP##generated for target system APOCLNT8XX and applicationMAT T-F1## � appears have you successfully generatedand integration model:

g) Select Continueh) Select Back once.


a) Select Save.b) Enter the variant nameMat.## with the description T-F1##c) Select Save.






a) From the SAP R/3 menu, Logistics → Central Functions → SupplyChain Planning Interface → Core Interface Advanced Planning andOptimizer → Integration Model→ Activate

Your integration model information should default into the fieldssince that was the last one you used. If it doesn�t make sure thatthe fields are correct with the information from the previous stepand execute.

Double click on the date/time line or click it and click the

button on the tool bar. A green check shouldappear in front of it. To begin the initial data transfer, click the

button on the tool bar.



Answer: Pump PRECISION 100. Using SAP Menu→ Advance Planningand Optimization → Master Data → Product enter your product T-F1##,

plant 3100, select the location radio button, and click thebutton.


Answer: USERADMIN as found on the Administration tab.


Answer: The user USERADMIN is used by SAP R/3 to log on to the SAPSCM system during the CIF transfer of data. This user can be foundin the RFC destination and indicates this product master record wastransferred from SAP R/3 via the CIF.



Lesson Summary

You should now be able to:� Create integration models for transfer of transactional data using SAP



Unit Summary SCM210

Unit SummaryYou should now be able to:� Discuss the general concept of transactional data integration� Identify the necessary configuration to send transactional data between

an SAP R/3 system and an SAP SCM system (bi-directional)� Transfer transactional data from SAP SCM to SAP R/3� Create integration models for transfer of transactional data using SAP




Test Your Knowledge


2. The actual selection of data by an integration model takes place whenthe model isFill in the blanks to complete the sentence.


4. The Name and Target System uniquely identifies an integration model.Determine whether this statement is true or false.□ True□ False




6. Which of the following is a benefit of using MRP Type X0 as a selectioncriteria for SAP SCM relevant materials?Choose the correct answer(s).□ A It excludes the material from MRP planning in SAP R/3.□ B It ensures all dependent requirements are created even for

non-SAP SCM relevant components by exploding the BOMduring the next MRP planning run in SAP R/3.

□ C It automatically causes a product to be planned in SAP SCM.□ D It�s a good generic selection criteria for an integration model

which minimizes maintenance.



Answers


Answer: SAP SCM relevant data is any data that is contained in an activeintegration model with SAP SCM.

2. The actual selection of data by an integration model takes place when themodel is generated.

Answer: generated.


Answer:

� Generate the integration model. This consists of creating and saving.� Activate the integration model. This consist of the activation and

initial transfer.

4. The Name and Target System uniquely identifies an integration model.

Answer: False

The integration model is uniquely identified by the Name, Target System,and Application.


Answer: A generic selection criteria like MRP Type can helpautomatically include new products without adding a specific materialnumber to the selection criteria.



6. Which of the following is a benefit of using MRP Type X0 as a selectioncriteria for SAP SCM relevant materials?

Answer: A, B, D

MRP Type X0 by itself does not cause the product to be planned in SAPSCM. Only if you use MRP Type as a selection criteria in your integrationmodel does it then become an SAP SCM relevant material. Additionalsettings may need to be done in SAP SCM in order for the material to beincluded in SAP SCM planning.


SCM210 Course Summary

Course SummaryYou should now be able to:

� Identify the necessary steps to setup integration between and SAP R/3system and an SAP SCM (APO) system

� Identify the tools necessary to initiate and monitor the continuoustransfer for master data and transactional data between and SAP R/3and an SAP SCM system.

� Transfer master data from SAP R/3 to SAP SCM and familiarize yourselfwith the results.

� Review the master data modeling structure in SAP SCM� Review the steps of transactional data integration and transfer planning

results from SAP SCM to SAP R/3.


Course Summary SCM210


IndexAActivity Relationships, 166PPeriodic Lot-sizingProcedure, 120

RResource, 131SStatic Lot-sizing Procedure,119


Index SCM210


FeedbackSAP AG has made every effort in the preparation of this course to ensure theaccuracy and completeness of the materials. If you have any corrections orsuggestions for improvement, please record them in the appropriate place inthe course evaluation.


Date post:	25-Oct-2015
Category:	Documents
Upload:	dsreddy00
View:	112 times
Download:	2 times

SCM120-CoreInterfaceSAPSCMParticipant.pdf

Documents