Vous êtes sur la page 1sur 120

Master Data

PDF download from SAP Help Portal:


http://help.sap.com/saphelp_scm50/helpdata/en/2a/847337613fbc40e10000009b38f8cf/content.htm
Created on January 29, 2015

The documentation may have changed since you downloaded the PDF. You can always find the latest information on SAP Help Portal.

Note
This PDF document contains the selected topic and its subtopics (max. 150) in the selected structure. Subtopics from other structures are not included.
The selected structure has more than 150 subtopics. This download contains only the first 150 subtopics. You can manually download the missing subtopics.

2015 SAP SE or an SAP affiliate company. All rights reserved. No part of this publication may be reproduced or transmitted in any form or for any purpose
without the express permission of SAP SE. The information contained herein may be changed without prior notice. Some software products marketed by SAP SE
and its distributors contain proprietary software components of other software vendors. National product specifications may vary. These materials are provided by
SAP SE and its affiliated companies ("SAP Group") for informational purposes only, without representation or warranty of any kind, and SAP Group shall not be
liable for errors or omissions with respect to the materials. The only warranties for SAP Group products and services are those that are set forth in the express
warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty. SAP and other
SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP SE in Germany and other
countries. Please see www.sap.com/corporate-en/legal/copyright/index.epx#trademark for additional trademark information and notices.

Table of content

PUBLIC
2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 1 of 120

Table of content
1 Master Data
1.1 Supply Chain Model, Planning Version, and Supply Chain Engineer
1.1.1 Creating, Copying, and Deleting Model/Planning Version
1.1.2 Planning Version Copy with Parallel Processing
1.1.3 Merge Master Data of Active Version with Inactive Version
1.1.4 Planning-Vers.-Depend. and Planning-Vers.-Independ. Master Data
1.1.5 Model Consistency Check
1.1.5.1 Profile Maintenance
1.1.5.2 Executing the Model Consistency Check
1.1.5.3 Log Selection
1.1.5.4 User-Specific Checks
1.1.6 Supply Chain Engineer (SCE)
1.1.6.1 The Supply Chain Engineer Screen
1.1.6.2 SCE Settings Maintenance
1.1.6.2.1 Maintaining the SCE User Profile
1.1.6.2.2 Maintaining Units of Measure for Display
1.1.6.2.3 Maintaining Time Zone for Display
1.1.6.2.4 Maintaining Cost Functions
1.1.6.2.5 Defining Work Area
1.1.6.2.6 Using Supply Chain Hierarchies
1.1.6.3 APO Model Maintenance
1.1.6.3.1 Creating a Model
1.1.6.3.2 Maintaining SCE Views
1.1.6.3.3 Maintaining Objects in Model
1.1.6.3.4 Maintaining Dependent Objects in Model
1.1.6.3.5 Deleting Objects from Model
1.1.6.4 Supply Chain Queries and Data Maintenance
1.1.6.4.1 Displaying and Maintaining Location Data
1.1.6.4.2 Displaying and Maintaining Location Product Data
1.1.6.4.3 Displaying and Maintaining Resource Data
1.1.6.4.4 Displaying and Maintaining PPM Data
1.1.6.4.5 Displaying and Maintaining Transportation Lane Data
1.2 Location
1.2.1 Displaying, Creating, and Changing a Location
1.2.2 Deleting a Location
1.2.3 Location Hierarchy
1.2.4 Application Log for Location
1.2.5 Geocoding
1.2.5.1 Calculation of Transportation Zone Coordinates
1.2.5.2 Interface for Third-Party Geo-Coding
1.2.5.2.1 Parameter Description
1.2.5.2.2 Data Types of the ABAP interface
1.2.5.2.3 Data Types of the RFC interface
1.3 Product
1.3.1 Global Product Master Data
1.3.1.1 Maintaining Global Product Master Data
1.3.1.2 Maintaining Properties
1.3.1.3 Maintaining Units of Measure
1.3.1.4 Maintaining Classifications
1.3.1.5 Maintaining Product-Related Data for SNP1
1.3.1.6 Maintaining Product-Relevant Data for ATP
1.3.1.7 Product Group
1.3.1.8 Alternative Product Number
1.3.2 Location-Dependent Product Master Data
1.3.2.1 Maintaining Location-Dependent Product Master Data
1.3.2.2 Maintaining Administration Data
1.3.2.3 Maintain Requirements Data
1.3.2.4 Maintain Lot Sizes
1.3.2.5 Maintaining Product-Related Data for SNP2
1.3.2.6 Maintaining Procurement Data

PUBLIC
2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 2 of 120

1.3.2.7 Maintaining GR/GI Data


1.3.2.8 Maintaining Additional Data
1.3.3 Mass Maintenance of Location Products
1.3.4 Mass Maintenance of Penalty Costs for Products
1.3.5 Mass Maintenance of Penalty Costs for Location Products
1.3.6 Setting the Planning Version
1.3.7 Deleting Planning Versions
1.3.8 Assigning Models
1.3.9 Deleting a Product
1.3.10 Product Hierarchy
1.3.11 Defining Free Attributes
1.3.12 Inheritance of Product Master Attributes
1.3.12.1 Extending Table Structures for Inheritance
1.3.12.1.1 Creating an Append Structure for Include /SAPAPO/MLREF_I
1.3.12.1.2 Creating an Append Structure for Include /SAPAPO/MATLOC_R_I
1.3.12.1.3 Creating an Append Structure for Include /SAPAPO/MATL_SPP1_R_I
1.4 Resource
1.4.1 Resource Types
1.4.1.1 Single Activity and Multiactivity Resource
1.4.1.2 Single-Mixed and Multimixed Resources
1.4.1.3 Bucket Resources
1.4.1.4 Resource with Storage Characteristics (Container Resource)
1.4.1.4.1 Storage Characteristics
1.4.1.4.2 Creating a Container Resource
1.4.1.5 Line Resource
1.4.1.6 Calendar Resource and Calendar Mixed Resource
1.4.1.7 Transportation Resource
1.4.1.8 Vehicle Resource
1.4.2 Creating and Changing Resources
1.4.2.1 Integration of Resources
1.4.2.2 Tab Pages in Resource Maintenance
1.4.2.2.1 General Data
1.4.2.2.1.1 Validity Period for Available Capacity
1.4.2.2.2 Time-Continuous Capacity
1.4.2.2.3 PP/DS Bucket Capacity
1.4.2.2.4 SNP Bucket Capacity
1.4.2.2.5 External Capacity
1.4.2.2.6 Downtimes
1.4.2.2.6.1 Downtimes for Maintenance Orders
1.4.2.3 Define Data for Multiple-Shift Operations
1.4.2.3.1 Defining Capacity Variants
1.4.2.3.1.1 Definitions
1.4.2.3.1.1.1 Creating Capacity Variants
1.4.2.4 Create and Change Resources Manually in SAP APO
1.4.2.5 Copying Resources
1.4.2.6 Deleting Resources
1.4.3 Determining the Valid Available Capacity
1.4.3.1 Invoking the Capacity Profile
1.4.3.2 Standard capacity
1.4.3.3 Reference Resource
1.5 Production Process Model, Production Data Structure and iPPE
1.5.1 Production Process Model
1.5.1.1 PPM Plan
1.5.1.1.1 Product Flow
1.5.1.1.2 Production Process Model Plans for CDP and Block Planning
1.5.1.2 Creating Production Process Models
1.5.1.3 Generating SNP PPMs from PP/DS PPMs
1.5.1.3.1 SNP PPM Generation With Lot Size Margin
1.5.1.3.1.1 Specifying Mode Combinations for SNP PPM Generation
1.5.1.3.2 SNP PPM Generation Without Lot Size Margin
1.5.2 Production Data Structure (PDS)
1.5.2.1 Production Data Structure Generated from iPPE Data

PUBLIC
2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 3 of 120

1.5.2.1.1 Generating Production Data Structures (PDS) from iPPE Data


1.5.2.1.2 Checking Master Data in Inactive Planning Versions
1.5.2.1.3 Generating Production Data Structures (PDS) from iPPE Data for A
1.5.2.2 Production Data Structure Generated from R/3 Master Data
1.5.2.2.1 Create Integration Model for Transferring R/3 Data
1.5.2.2.2 Comparison of PP/DS Production Data Structure
1.5.2.3 Generating DP Production Data Structures (DP PDS)
1.5.2.4 Display Production Data Structures
1.5.2.4.1 Simulating a Production Data Structure
1.5.2.4.2 Selecting a Production Data Structure
1.5.2.5 Deleting Production Data Structures (PDS) in SAP SCM
1.5.3 Integrated Product and Process Engineering (iPPE)
1.6 Hierarchy
1.6.1 Hierarchy Structure
1.6.2 Maintain Hierarchy
1.6.3 Schema Hierarchy
1.6.4 Extended Hierarchy
1.7 Transportation Lane
1.7.1 Automatic Creation of Transportation Lanes
1.7.2 You have created transportation lanes
1.7.3 Transportation Lane Maintenance Screen
1.7.4 Defining Product Procurement
1.7.4.1 Transportation Lanes for Product Groups
1.7.5 Defining Means of Transport
1.7.6 Duration Time and Distance Determination for Means of Transport
1.7.7 Assigning Products to Means of Transport
1.7.8 Assigning External Transportation Service Providers
1.7.9 Creating Multiple Lanes

PUBLIC
2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 4 of 120

!--a11y-->

1 Master Data
Purpose
Master data is used in different components of SAP Supply Chain Management (SAP SCM).
Master data is stored in individual master records, which can be changed either individually or through Mass Maintenance.

Integration
Master data is created directly in the relevant component. However it can also be transferred from SAP R/3 via the APO Core Interface (CIF) for use in SAP
Advanced Planning and Optimization (SAP APO). For more information on the integration of master data in SAP APO and SAP R/3, see Integration of Master
Data.

!--a11y-->

Supply Chain Model, Planning Version, and Supply Chain Engineer


Use
The supply chain model is the basis for planning in SAP SCM. The system takes only master data that is assigned to a model into account in the planning. You
can assign the master data to a model either in the Supply Chain Engineer or in the maintenance transaction for the master data in question. You can also assign
products and location products to the model in the product master.
You can assign one or more planning versions to a model. By creating different planning versions with different planning datasets, you can investigate all the
aspects and options of a given supply chain situation and simulate the effects of different parameters. You can also create several models for simulation
purposes.
All the master data released for the planning must be assigned to the active model and the active planning version (model 000 and planning version 000
respectively) in the production system. Master data transferred from SAP R/3 is automatically assigned to the active model and the active planning version.
You can create models and planning versions in planning version management ( Master Data Planning Version Management ) or in the Supply Chain
Engineer. For more information, see Creating, Copying, and Deleting Model/Planning Version.
You can use the model consistency check to check the consistency of your supply chain model.

!--a11y-->

Creating, Copying, and Deleting Model/Planning Version


From the SAP Easy Access screen, choose mySAP Supply Chain Management
Version Management Model and Version Management.

Advanced Planning and Optimization M aster Data Planning

The Model and Version Management screen appears.


You can also create, copy, and change your model or planning version in the Supply Chain Engineer.
Function
Create Model

Navigation
Create Model/Planning Version Model

What you should know


You assign master data such as locations, products, or
resources to the model you have created either in the
Supply Chain Engineer or through master data
maintenance.

Create Planning Version


Copy Model/Planning Version

Create Model/Planning Version Planning Version


Select the model or planning version you wish to copy in

To perform the copying of the planning version with

the left-hand part of the screen and choose Copy


Model/Planning Version Model/Planning Version.

parallel processing and thus significantly improve


performance in the case of large data volumes, you can
make use of the program
/SAPAPO/VERSION_COPY_PAR. For more
information, see Planning Version Copy with Parallel
Processing.

Copy Model with Planning Versions

Select the model and the associated planning versions you


wish to copy in the left-hand part of the screen and choose
Copy Model/Planning Version Model with Versions.

Delete Model/Planning Version

Select the model or planning version you wish to delete in Deletion is only possible if you have the authorization to
the left-hand part of the screen and choose Delete
Model/Planning Version.

delete.
When you delete a model, all planning versions of the
model are also deleted.

PUBLIC
2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 5 of 120

You can carry out the copying and deletion of models/planning versions either in the foreground or in the background.
If you are copying in the foreground, the copy log is displayed, and the copies are added in the left-hand area of the screen.
If you are copying or deleting in the background, you receive a mail when the copying or deletion process is completed.

!--a11y-->

Planning Version Copy with Parallel Processing


Use
You can use the Copy Planning Version program (/SAPAPO/VERSION_COPY_PAR) to completely or partly adopt the data of one planning version in another.
The program supports parallel processing. In parallel processing, the program carries out different tasks not one after the other but concurrently.
With parallel processing, you can usually considerably improve performance when copying the planning version. Due to the greater number of tasks to be
performed in parallel, however, the load on the system is likely to be higher.

Prerequisites
If you want to make use of the parallel processing option, you must have created a parallel processing profile in Customizing for the master data under Model and
Version Management Create Parallel Processing Profile for Planning Version Copy .

Features
The program provides you with the following options:
Improved performance due to parallel processing
Additional improvement in performance when copying the active planning version if you unset the Also Copy Location Products indicator
Determination of scope of copying
Copy master data only
If you choose this option, the system copies the master data only.
You can additionally restrict the scope of copying for location products.
Copy master and transactional data
If you choose this option, the system copies all master data. In the Copying Scope in Detail section of the screen, you have additional selection options
for transactional data. Only the transactional data selected here is copied.
You can also restrict orders and stocks by selecting certain location products.
To prevent inconsistencies arising from transfers per APO Core Interface (CIF) that take place parallel to the copying of the active planning version, two Business
Add-Ins (BAdIs) are also available:
BAdI: Deactivation of CIF Prior to Copying of Planning Version (/SAPAPO/MVM_COPY1)
BAdI: Activation of CIF After Copying of Planning Version (/SAPAPO/MVM_COPY2)
You will find the BAdIs in Customizing for the master data under Model and Version Management Business Add-Ins for Planning Version Copy .

Activities
1. To invoke the program, from the Advanced Planning and Optimization menu, choose Master Data Model and Version Management Copy Planning
Version.
2. Under Source Version , enter the planning version whose data you want to copy.
If you enter the active planning version, the Also Copy Location Products indicator additionally appears. In the standard system, this indicator is set. If you
unset this indicator, the location products of the active planning version are merely referenced. This facilitates an additional improvement in performance.
3. Under Target Version , enter the planning version to which you want to copy the data.
If a planning version with this name already exists, its data is overwritten with the data of the source version. The name and the GUID of the planning version
are retained so that you can continue to use it in variants and profiles.
If no planning version of this name yet exists, it is created automatically.
4. To use the parallel processing facility, specify a parallel processing profile under Profile .
5. Define the scope of copying.

Example
You want to optimize your planning by changing the data of your active planning version. Before making these changes to the active planning version, you
simulate a planning run. To do so, copy the data of the active planning version into a new planning version. You change the data of this planning version and
execute simulation runs. Where appropriate, adopt the optimized data in the active planning version.

!--a11y-->

Merge Master Data of Active Version with Inactive Version


PUBLIC
2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 6 of 120

Use
You have created a planning version and have used it to simulate planning runs. You have changed the master data attributes of this planning version until you
have reached an optimal planning run. Now you wish to adopt the master data attributes of this planning version in the active planning version. You do not have to
change the relevant master data attributes in the active planning version individually this function provides the option of doing so on a collective basis.
As standard, the system merges all version-dependent attributes of the master data object location product. You can also select the following master data objects
for merging:
Location
Transportation lane
Quota arrangement
The system also only merges the version-dependent attributes for these master data objects.

Note that making mass-changes to the active planning version can have major implications for the planning. You should therefore use this function
with the greatest care.

To improve performance and achieve a better overview, we recommend that you work with template planning versions that only affect the master
objects that are relevant to the planner in question in each case. You should have created these template planning versions manually, that is,
without a planning version copy. With this approach, the changes transferred back to the active planning version are minimized.

Procedure
1. On the SAP Easy Access screen, choose Advanced Planning and Optimization Master Data Application-Specific Master Data Service Parts
Planning (SPP) Merge Master Data of Inactive Version with Active Version .
2. Enter the planning version you wish to use as a source version.
3. Enter the planning version you wish to use as a target version.
4. You can also specify specific products and locations whose master data you want the system to merge.
5. You can also choose additional master data attributes whose version-dependent attributes you want the system to merge.
6. Choose Merge Versions .

Results
The system adopts the master data attributes of your template planning version in the active planning version. Master data attributes for which there are no
parameters in the template planning version remain unchanged in the active planning version. Transaction data attributes likewise remain unchanged.

!--a11y-->

Planning-Vers.-Depend. and Planning-Vers.-Independ. Master


Data
The following sections contain information on which master data is planning-version-dependent and which is planning-version-independent.

Global Product Master


The data in the global product master is independent of a planning version.

Location
By choosing a planning version and the change mode on the initial screen for location master data maintenance, you can process all fields that are dependent on
the planning version.
For more information, see Displaying, Creating and Changing a Location.

Location Product
By choosing a planning version (via Extras Choose Planning Version ) and choosing the change mode on the initial screen of the location-specific product
master, you can process all fields that are dependent on the planning version.
If you did not choose a planning version on the initial screen, the values you specified in the planning-version-dependent fields will automatically be assigned to
planning version 000 (this applies in any case to planning-version- in dependent fields).
If you change the planning-version-dependent data in the location product master without explicitly specifying a planning version, you will also change the
planning-version-dependent values of version 000 and all versions for which no planning-version-dependent data has previously been defined.
Only the location products for which you have explicitly created planning-version-dependent data use separate data and not the planning-version-dependent data
of planning version 000.
For more information, see Maintaining Location-Dependent Product Master Data.

PUBLIC
2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 7 of 120

Production Process Model (PPM)


Time-dependent parameters of a PPM are dependent on the planning version. You can define time-dependent parameters in the PPM for the following data:

Scrap of an activity
The duration of an activity defined at the mode
The capacity requirement of an activity defined at the resource
The material consumption defined at an alternative component

If you define one of these parameters dependent on time, you can specify a planning version for which this setting is valid.
If you specify a planning version, the system only uses this setting for the specified planning version.
If you copy this planning version, the system also copies the time-dependent parameters. If you change the parameters in the original planning version later,
this has no effect on the parameters of the copy.
If you do not enter a planning version, the system uses this setting for all planning versions for which you have not defined any other time-dependent
parameters. If you change this parameter, this also affects all planning versions for which you have not defined any individual settings.
If you copy a planning version for which no planning-version-dependent data and no time-dependent parameters have been defined, the copy also uses this
information.
For more information, see PPM Plan.

Resource
All the data of a resource is dependent on the planning version. Specific data for the resource, such as the resource type, cannot be changed; some data can only
be changed depending on the status of the activities scheduled on the resource.
If you assign a resource to a model, the system automatically assigns it to all planning versions of this model. If you create a new planning version for this model
later, the system also automatically assigns the resource to the new planning version.
If you change the data for a resource, you only change it in the planning-version-specific copy; in other words, if necessary, you have to change the data in all
planning-version-dependent copies of the resource.

On the initial screen of the master data for the resources, you can copy the resource data of all planning versions of a model via Tools Copy
Resources .
Behavior of the planning-version-dependent resource master data when a planning version is copied
Source version

Copy

Planning version 000 without separate planning-version-dependent data

Not possible

Planning version 000 with separate planning-version-dependent data including capacity

Separate planning-version-dependent data, separate variant data; uses the data of the

variant data; uses the data of the shift definition

shift definition

Planning version XYZ without separate, planning-version-dependent data

Not possible

Planning version XYZ with separate planning-version-dependent data including capacity

Separate planning-version-dependent data, separate variant data; uses the data of the

variant data; uses the data of the shift definition

shift definition as in the source version

For more information, see Creating and Changing Resources.

Quota Arrangement
All quota arrangements can be defined as dependent on the planning version. However, you can also define planning-version- in dependent quota arrangements.
Planning-version- in dependent data is used in all quota arrangements for which there is no planning-version-dependent data.
If you wish to explicitly assign quota arrangement data to planning version 000, you must specify the planning version 000 while in quota arrangement
maintenance mode ( Master Data Quota Arrangements from the SAP Easy Access screen). If you change this data, the change will have no effect on other
planning versions.
If you copy a planning version for which no planning-version-dependent data has been defined, the copy contains no planning-version-dependent data and also
uses the planning-version- in dependent data.
If you copy a planning version for which separate, planning-version-dependent data has been defined, this data is also copied. If you change the original version
(after copying), this change has no effect on the data of the copy.
If you copy planning version 000, all planning-version-dependent data is copied at the same time. If you change the data in planning version 000, this change
has no effect on the data of the copy.
Changes to the planning-version- in dependent quota arrangement data affect all planning versions for which no planning-version-dependent data has been
defined.
For more information, see Validity of Quota Arrangements.

!--a11y-->

1.1.5 Model Consistency Check


Purpose
The model consistency check checks the master data assigned to a

PUBLIC
2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 8 of 120

model or
work area
to make sure it is complete and does not contain inconsistencies regarding its use as an
APO supply chain model.
The check provides important information about the maintenance of master data and its suitability for use in APO scheduling functions.

The model consistency check only includes checks from a business view, not technical (such as
liveCache-oriented) checks.
You can either execute the model consistency check manually or in the background. For more information about executing the model consistency check in the
background, see
Executing the Model Consistency Check under Saving Messages to the Database .

Integration
You should execute a model consistency check after you maintain the model in the
Supply Chain Engineer (SCE). The results of the check point out the following master data inconsistencies:
error
wrongly maintained
not needed for the APO scheduling functions.
You can easily correct these inconsistencies from the model consistency check.
The model consistency check is a useful tool when creating and changing APO models.
See also:
Create profile
For more information, see
Profile Maintenance.
Execute model consistency check
For more information, see
Executing the Model Consistency Check.
Display a log that is saved to the database of a model consistency check that has already been executed
For more information, see
Log Selection.

You have the option of including user-specific individual checks. For more information, see
User-Specific Checks.
!--a11y-->

1.1.5.1 Profile Maintenance


Use
You use this function to display, create, select, and process check profiles for the model consistency check.

Integration
All of the individual checks to be executed in the model consistency check are contained in a profile. It determines the scope of the model consistency check.

Features
Individual checks of the following master data and applications are available in the model consistency check:

PUBLIC
2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 9 of 120

Master Data Checks:


Here you can check the consistency of the data within individual master data objects. The system determines whether all necessary information (on a field level)
is maintained.

We recommend that you always execute a master data check after maintaining a model in the Supply Chain Engineer (SCE).
Cross-Master Data Checks:
Here you can search for inconsistencies between master data objects.

In-house production: If in-house production is defined for a location product, the system checks whether a PPM exists for the location product.

External procurement: If external procurement is defined for a location product, the system checks whether the product is defined for a
transportation lane that leads to the product.
Application Checks:
Here you can check that master data objects are used consistently in the applications. Use this check depending on your business process.

For more information on individual checks, see the corresponding field helps.

Activities
To create a profile, take the following steps in the SAP APO Easy Access menu:
1. Choose Master Data Model Consistency Check Maintain Profile.
You are now on the Model Consistency Check: Administration Check Profiles screen.
2.
3.
4.
5.

To create a new profile, enter a profile name and a short description.


Choose Create .
Select the relevant checks.
Choose Save .

!--a11y-->

1.1.5.2 Executing the Model Consistency Check


Use
You can use this function to execute and evaluate the model consistency check.

Prerequisites
Before you execute the model consistency check, ensure the following prerequisites have been met:
You have created a profile in the profile maintenance containing the individual check to be executed.
You can only specify a work area if you have already created it in the Supply Chain Engineer (SCE).
For further information, see
Defining Work Areas.

PUBLIC
2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 10 of 120

You can also call the model consistency check from the Supply Chain Engineer. Choose Master Data Supply Chain Engineer Display Model
Goto Model Consistency Check.
You can call the CTM-specific parts of the model consistency check directly from the CTM Profile Maintenance.
1. Choose Multi-Level Supply & Demand Matching Planning Capable-to-Match (CTM ) Planning .
2. On the Settings tab page under Profiles, specify a check profile of the model consistency check.
3. Choose Check Profile .

Features
You can execute a model consistency check for a planning version. In addition to the planning version, specify a profile and a check date. All master data objects
assigned to the planning version form the object selection:
The system uses planning-dependent data for individual master data objects, if it exists.
If it does not exist, the system uses the planning version-independent model data for the check.
If you specify a check date, the system considers the time specifications (for example, validities of objects or time-dependent attributes) of the particular date.

If you specify a work area, you can limit the amount of data to be checked. The system then checks the objects in this work area only.
The following options are also possible:
Use Strict Check Criteria
With this indicator, you can define criteria for the check of objects from the object selection and for 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 a consistent (partial) model.
In this case, the system assigns the message type using 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 the objects in the object selection are
work areas, in Supply Chain Cockpit (SCC) terms. A work area is a quantity of objects in a planners area of responsibility.
In this case, the system assigns the message type using less strict criteria:

If only 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 object selection, that results from the model consistency check, is an error message in check type 1, and a warning
message in check type 2.
Information
Here you can display the existing objects in the object selection.
Object Selection
Here you can display the following information regarding the object selection:
Number of
objects that exist in the object selection for each object type
location products for each location in the object selection
PPMs for each location in the object selection
Resources for each location in the object selection
Check Results
After executing the model consistency check, the system displays the relevant check messages. You can process these later.
There are different ways of doing this:
Select Messages
You can select the displayed messages according to the following criteria:
Message type: The messages are displayed as error, warning, or information messages.
Check area: Messages regarding the affected master data and application area for the following areas are displayed:
Locations
(Location) products
Resources
Production Process Models (PPMs)
Integrated Product and Process Engineering (iPPEs)
Transportation lanes/quota arrangements
Master data, general
Characteristics-Dependent Planning (CDP)
Supply Network Planning
Capable-To-Match (CTM)
Vehicle Scheduling
User-Specific Checks
Check object: Messages about the affected master data objects are displayed.
To select the messages, choose Sort .

PUBLIC
2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 11 of 120

Marker in the Master Data Maintenance


You can use the Master data maintenance button to go to the relevant master data transactions, where you can make changes.
Saving Messages to the Database
To save the displayed messages, choose Further functions Save messages to database.

You have the option of executing the model consistency check in the background, using report /SAPAPO/CONSCHK. In this case, the
check messages are automatically saved to the database.

The duration of a run depends on the number of executed checks. We recommend you to execute the checks in the background if you have
several master data and application areas. There is no time difference between a manual check run and a check run executed in the
background.

!--a11y-->

1.1.5.3 Log Selection


Use
You can use this function to display a model consistency check log.

Prerequisites
You have saved the check messages to the database and executed the model consistency check in the background.

Features
You can select the check log using the following criteria:
Date and time of log creation
User
Profile
Planning version
Check date
Work area

If you want to display the logs saved in the database, the display options described in
Executing the Model Consistency Check under Check Results are also relevant here.
!--a11y-->

1.1.5.4 User-Specific Checks


You have the option of including user-specific individual checks.
You can also
create one or more function module(s) with defined interfaces, where these checks are performed
enter the names of the function modules in SAP Advanced Planner and Optimizer (SAP APO) Customizing, under Master Data Model and Version
Management Configure User-Specific Model Consistency Check .
The function modules entered here are considered in the model consistency check.
Implementation
To implement a function module with user-specific consistency checks, see function module /SAPAPO/MVM_CONS_CHK_EXAMPLE. All function modules you
have implemented must have the same interface as this function module.

For more information, see the function module documentation.


!--a11y-->

Supply Chain Engineer (SCE)


Purpose
You can use this component to create and maintain network models of supply chains. The network model represents a specific supply chain and consists of

PUBLIC
2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 12 of 120

various nodes and links. A model can have different planning versions. This gives you the option of creating different models, each with different versions for
simulation purposes.

Integration
The Supply Chain Engineer is a fully integrated component of SAP Advanced Planning and Optimization ( SAP APO ) which is used to create models. The
model is the basis for all APO planning functions. It covers all areas of the network chain, from the suppliers supplier to the customers customer. Here the
relevant data objects are imported from the source system into SAP APO.

Features
Nodes and links are used to construct a supply chain model. A node denotes to a location or business entity in SAP APO. The connections between the locations
are the transportation lanes. Locations include production plants, distribution centers, customers, and suppliers.
In addition to locations and transportation lanes, the model also enables you to keep an eye on other supply chain elements, such as products, production
process models (PPMs), and the following resources:
Handling
Production
Storage
Transportation
The SCE enables you to view data pertaining to the different elements in your chain. You can submit queries for information about individual or combined elements
in your supply chain. For example, you can launch a query that will generate a list of all products belonging to a specific location in your model.
You can display your supply chain model either geographically on the map or as a logical view.
For more information, see:
The SCE Screen
SCE Settings Maintenance
APO Model Maintenance
Transportation Lanes
SCE Queries
Supply Chain Model, Planning Version, and Supply Chain Engineer

!--a11y-->

1.1.6.1 The Supply Chain Engineer Screen


Use
The Supply Chain Engineer screen provides an overview of your model. Here you can perform the following tasks:
Supply chain model maintenance
Transportation lane maintenance
Execution of queries

Structure
The layout of the SCE screen is as follows:
The upper section is a graphical representation of your current model.
The middle section has a number of pushbuttons that you can use to select objects for the work area.
The lower section is a tree structure containing all the objects in the work area.
Supply Chain Engineer
Screen Elements

Functionality

Header

The SCE menu toolbar contains the following function icons:


Switch between view and change mode
Go to model/planning version management
Display list of all objects in the model
Reset display
Access user-specific settings
Show and hide graphical display

Graphical Display

The graphical display toolbar contains the following function icons:

Adjust to Objects : This centers all objects in the display


Reduce/Increase Size : Shows the model in detail or overview
Enlarge to World View : Positions the model on a global scale
Switch On Overview: Opens a small window showing the model's global
position
Display Layers: Opens a dialog box for map maintenance. Apart from the
maps provided by the standard application, you can also use further

PUBLIC
2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 13 of 120

maps. First, save the map files locally, then activate the Add button in
the map maintenance screen to add map layers. On this screen you can
also customize the fill and line colors on the map as well as the width of the
lines
Filter: This enables you to filter objects displayed on the map
Choose: Enables you to select a location on the map
Highlight: You can highlight the inbound and outbound lanes of a location
by selecting the location and activating this icon
Move: You can move a location that you have first selected
Connect : You use this to connect (create transportation lanes between)
locations. (First choose locations by clicking on Connect draw line to
other location lane maintenance screen appears)
Change Representation of Connection : You use this to change the way that
transportation lanes are displayed
Print/Save : You choose this to print and save the view

Use the context menus on nodes and links (click once with right-hand mouse button) as
described in Object Selection.
Object Selection

Tree structure with different pushbuttons for locations, products, resources, PPMs, and
transportation lanes. Context menus on nodes and links (single click on right-hand
mouse button) enable you to:

Add or delete objects


Launch queries
Display and change master data
Display supply chain data

For more information, see Supply Chain Queries and Data Maintenance

!--a11y-->

1.1.6.2 SCE Settings Maintenance


Purpose
The SCE user settings give you the opportunity to set up the Engineer according to your own needs as a supply chain modeler.

Prerequisites
You have maintained all relevant SAP APO master data.

Process Flow
Perform the following procedures:
Maintaining the SCE User Profile
Maintaining Time Zone for Display.
Defining SCE Work Areas

!--a11y-->

1.1.6.2.1 Maintaining the SCE User Profile


Use
This profile enables you to maintain all necessary settings for the Supply Chain Engineer. Use this profile to:

Define parameters
Set a work area filter for graphical and/or hierarchical display
Choose means of transport
Set parameters for the Selections for Query screen

This profile is divided into four tab pages:


General Settings
Model Maintenance

PUBLIC
2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 14 of 120

Queries
Transportation Lanes

Procedure
1. From the SAP Easy Access menu, choose Master Data Supply Chain Engineer Make Settings .
The view for user-specific settings appears.
2. Maintain the profile as described below:

You can also access the profile from the SCE menu ( Settings User profile ). In this case, however, you will only find a reduced version of the
General tab page from the settings screen.
Pushbuttons of the Menu Bar
Field

Procedure

Load User Parameters

Reset settings to previously saved ones.

Load Default

Use default values for all settings

Time Zones

Maintain time zone for display

General Settings
Field.

Procedure

Display Work Area

If you want maintenance objects to be displayed, set the corresponding indicator.

Display Supply Chain

If you want the work area to be used as a filter for the graphical display, set the
corresponding indicator.

Hierarchies

Set the indicator according to whether or not you want to display hierarchies in the SCE.
For more information, see:
APO Hierarchy

Model Maintenance
Field.

Procedure

Add and Delete Dependent Objects

Set this indicator for the automatic assignment/deletion of dependent objects to/from a
model. All dependent objects are automatically included in the activity.

Geographical Coordinates

Activate this indicator if you want to confirm geographical coordinates each time you
move locations on the map.

Queries
Field.

Procedure

Query Time Period

Define your query horizon. Choose:


Relative Interval if you want to work with time periods such as days or weeks (starting
from the present moment).
Fixed Interval if you want to work within an exactly defined period. (From/To dates)

Relative Interval

If you have chosen Relative Interval, activate the radio button that corresponds to the time
period you want to work with.
Enter the number of periods.

Fixed Interval

Enter the to and from data for the specific interval.

Use Query Selection screen

The selection you make defines the parameter for the Selection for Query screen. This
is an intermediate screen that always appears when you want to run a query. The query
objects entered and other options are displayed. This enables you to view your current
selection and change it if necessary before proceeding. (See APO document: APO
Supply Chain Cockpit)
Use the input help to make your selection.
Use standard SAP settings. The selection screen for queries always appears if it might
make sense to change the query selection.
Always use standard selection screen. Choose this option if you always want to see the
selection screen.
Do not use standard selection screen. Choose this option if you never want to see the
selection screen.

Transportation Lanes
Field

Procedure

PUBLIC
2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 15 of 120

Product Procurement

Set the corresponding indicator if necessary.

!--a11y-->

Maintaining Units of Measure for Display


Use
In this step, you define units of distance and velocity that are to be seen in the view. This setting is relevant to the maintenance of transportation lanes and means
of transport.

This setting is user-specific.

Procedure
1. From the SAP Easy Access menu, choose Master Data Supply Chain Engineer Maintain Model
Result: The SCE initial screen appears.
2. Choose the model you want to maintain.
Result: The SCE main screen appears.
3. From the SCE menu, choose Settings Unit .
4. Enter the units of measure for distance and velocity.
5. Save.

!--a11y-->

1.1.6.2.3 Maintaining Time Zone for Display


Use
You use this setting you define the time zone for display. Options include:

Time zone of location


Local time zone of user
All times displayed in UTC
Any time zone

Procedure
1. From the SCE menu, choose Settings Time Zones .
Result: The Time Zone for Display screen appears .
2. Make your selection.
3. Choose Continue.

!--a11y-->

1.1.6.2.4 Maintaining Cost Functions


Use
Use the cost function for setting fixed and variable costs per unit. These functions are used in optimization runs for calculating the cost of procuring, producing, or
transporting a specific quantity of product within the specified interval.
The fixed costs represent the baseline costs. No matter how large or small the quantity within the interval, the fixed costs always apply.
The variable costs for the specified interval are used by the optimizer to determine the effect on costs of producing, procuring, or transporting varying quantities of
the product within the interval. In general, a higher quantity of product within the interval should mean lower variable costs.

Procedure
PUBLIC
2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 16 of 120

Tocreate cost functions:


1.
2.
3.
4.
5.
6.
7.
8.

Access the Supply Chain Engineer menu in Change mode.


Choose GoTo Cost Function .
In the Cost Function: Initial Screen , enter a name for the cost function.
Select the procurement method for the unit: transport, production or external procurement.
Choose Create.
In the Change Function screen, enter a descriptive text for the cost function.
Maintain the table as shown in the example below.
Save.

Result
The cost function will be included in the Possible Entries for cost functions in the Product Procurement maintenance screen.

Cost Function Maintenance:


Unit quantities
From:

Costs per unit


To:

Fixed costs

Variable costs

0000

5,000

1.8

5,000

10,000

1.6

10,000

20,000

1.4

!--a11y-->

1.1.6.2.5 Defining Work Area


Use
Viewing your entire supply chain at once can be cumbersome. You can limit your view to those supply chain objects you want to concentrate on by defining work
areas.
The defined work area is the basis for the queries through which you retrieve information from the APO system on all aspects of your supply chain. The
transportation lanes in your work area are defined by the model you are working in.
The supply chain work areas include:

Locations (plant, DC, supplier, customer)


Resources (production, storage, handling, transportation)
Location products
Production process models (PPMs)

Procedure
1. Access your model from the SAP Easy Access menu. Choose Master Data Supply Chain Engineer Maintain Model
The Supply Chain Engineer: Choose Model screen appears.
2. Choose the model and work area you want to use. Choose Display, Change or Create , depending on the activity you want to perform.
Result: The SCE main screen appears. The objects of the work area/model appear in the overview tree and on the map.
The map shows all locations that the model contains. In the user-specific settings, you can specify that only those locations that are included both in the
model and in the work area are to be displayed.
Maintain Work Areas
Field

Procedure

The work area dimensions include:


Location

1. Choose the Work Area pushbutton and select the Add Objects option.
Result: The Select Work Area screen appears.

Resource
Production process model
iPPE

2. On the left-hand side, select the dimension from which you wish to add objects.
3. On the right-hand side, enter the objects or use the input help.
4. Choose Adopt .

Location product

Result: The objects are adopted in the current work area.


5. To save the work area, from the SCE menu, choose Settings Save Work Area
or use the Save button in the SCE main menu.
6. Repeat this procedure for each work area.

Pushbutton...

Procedure

Adopt

Access the SCE screen.

Save Selection

Assign a name or ID to a new set of selections.

Load Selection

Access list of existing work area selections.


Choose the selection you want to include in the work area.

PUBLIC
2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 17 of 120

Delete Line

Delete an entry from the value field.

Selection Options

Access the Maintain Selection Options screen.


For detailed information about this screen, choose the information icon located at the
bottom of the screen.

Cancel

Terminate the transaction.

You can use the Work Area pushbutton to do the following:

Display an object
Add objects
Remove objects
Clear the work area
Save the work area
Save work area as...

Delete Work Area


If you wish to delete the work area, from the initial screen, choose Supply Chain Engineer: Choose Model and then the Delete Work Area pushbutton.

Result
The objects in the work area you created appear in the SCE tree structure.

!--a11y-->

1.1.6.2.6 Using Supply Chain Hierarchies


Use
In order to facilitate the handling of large amounts of data, you can group master data objects into hierarchical relationships. A hierarchy consists of a structure
divided according to levels. To make handling even easier, you have the option to filter the objects that will be displayed on the map via a work area.
Hierarchies are master data objects that can be displayed in the Cockpit and Engineer. They are used for planning aggregated levels in the Supply Network
Planning application.
For detailed information, see the following topics:
APO Master Data: Hierarchy
Supply Chain Hierarchies
!--a11y-->

1.1.6.3 APO Model Maintenance


Purpose
The Supply Chain Engineer (SCE) is your tool for creating and maintaining supply chain network models. The network model represents a specific supply chain
and consists of individual nodes and links. A node denotes to a location or business entity in SAP APO. The connections between the locations are the
transportation lanes. The locations include the following:

Production plant
Distribution center
Customer
Supplier

The supply chain model also enables you to keep track of other supply chain elements, in addition to locations and transportation lanes, such as products,
production process models (PPMs), and the following resources:

Handling
Production
Storage
Transportation

Features
A model can have different planning versions. This gives you the option of creating different models, each with different versions for simulation purposes.
The SCE modeling screen is divided into two areas:
The upper part of the screen provides the view of your model.
The lower part shows you a hierarchical display of the objects in your work area.

PUBLIC
2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 18 of 120

Prerequisites
Create master data (model-independent data):

Locations
Location products (define the global and location-specific data for the product)
Resources
Production process models (PPMs)
Means of transport (APO Customizing)

Process
Before starting, you must create master data for locations, location products, resources, and other model-independent elements. You create and maintain the
supply chain model in the SCE by placing the locations on the map and using transportation lanes to connect the locations together and form a network. The
direction of the lanes shows the direction of the product transportation flow. To assign the products to the locations, simply use the drag and drop function. You must
also assign a quota arrangement to your products to specify which percentage of the product quantity is to be transported to other locations in the chain.

For more information, see:

Creating a Model
Defining SCE Work Areas
Maintaining SCE Views
Maintaining Objects in Model
Maintaining Dependent Objects in Model
Deleting Objects from Model
Supply Chain Model, Planning Version, and Supply Chain Engineer.

!--a11y-->

1.1.6.3.1 Creating a Model


Procedure
1. From the SAP menu, choose Master Data Supply Chain Engineer Maintain Model . You can also create a model under Master Data Planning
Version Management Model and Version Management .
2. The Supply Chain Engineer: Choose Model screen appears. Enter the name of the model. On this screen, you also have the option of displaying or
changing an existing model.
3. Choose Create .
The Supply Chain Engineer initial screen appears.

You can create a work area at the same time as you create a model. However, this step is optional at this point. The purpose of the work area is to
restrict the number of objects you want to work with at any given time. It makes sense to create the complete supply chain model first, and then
create the necessary work areas. If you do not enter a work area when you create the model, you will have an unnamed, user-dependent work
area containing your entire model.
For more information, see:
Defining SCE Work Areas
Supply Chain Model, Planning Version, and Supply Chain Engineer

!--a11y-->

1.1.6.3.2 Maintaining SCE Views


Use
The SCE offers two different ways to view your model, enabling you to examine your entire supply chain from different perspectives.
The geographical view shows the locations realistically but not always clearly. For example, if several locations are close together, your view will be crowded and
it may not possible to distinguish the locations from each other.
The logical view, on the other hand, depicts the supply chain in its logical format, irrespective of its geographical coordinates. When you open a logical view for
the first time, all objects are grouped together in the upper left-hand corner. You can either drag and drop the locations into your map area, or use the Default
Position icon that prompts the system to automatically place the locations according to their normal sequence in the supply chain, that is Su pplier Plant
DC Customer . You can rearrange the locations by using the left-hand mouse button to move them around. The logical view provides exactly the same
functionality as the geographical one.

PUBLIC
2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 19 of 120

Procedure
1.
2.
3.
4.

Invoke your model from the SAP menu.


Specify the view (geographical or logical) under Settings Logical View .
Enter the name of the view. Use the input help to retrieve an existing one, or create a new one by entering a view name.
You can choose between:
Set items to default
Load view
Save view
Delete view
Display view attributes

!--a11y-->

1.1.6.3.3 Maintaining Objects in Model


Use
An important aspect of supply chain modeling is to maintain individual objects in the model. However, to simplify maintenance, you can also maintain all the
object types in one step. In this step, you can simultaneously add or delete objects to or from a model.

Prerequisites
Maintain the master data for the individual objects.

Procedure
1. Go to the SAP menu and access your supply chain model in Change mode.
2. From the SCE main menu, choose Model O bjects All Object Types Add to/Delete from Model.
Result: The Selections for Chosen Function screen appears.
3. Choose the objects you want to include in or delete from the model. You can choose:
Location
For locations, you can also maintain transportation lanes and quota arrangements in the SCE.
Location products
Resources
Production process models (PPMs)
4. Limit your selection to the work area (optional).

You can maintain individual objects from the SCE main menu or using the context menus attached to the objects displayed in the tree and on the
map. You can also use the following SCE menu pushbuttons for model maintenance (see the quick info under the icons).
Model/planning version management
Objects in model (display list of all objects in the model)
Add objects to model (access context menu: Selections for Chosen Function ).
Delete objects from model (access context menu: Selections for Chosen Function ).
Assign dependent objects to model (automatic assignment of dependent objects to ensure model consistency)
Reset display
User-specific settings (access SCE user profile)

Result
The objects you selected have been added to or deleted from the model.
For more information about maintaining individual object types such as locations or products, see also:
Supply Chain Queries and Data Maintenance
Maintaining Dependent Objects in Model

!--a11y-->

Maintaining Dependent Objects in Model


Use
During supply chain modeling, you may find yourself assigning or deleting large numbers of objects to or from your model. Many of these objects may have

PUBLIC
2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 20 of 120

dependent objects assigned to them. To ensure model consistency, you can automatically assign or delete the dependent objects along with the primary object.
Automatic assignment not only ensures consistency, but also makes model maintenance much easier.

Example
If you assign a production process model (PPM) to your supply chain model, the location and all associated resources and products will automatically be
assigned as well.

Procedure
1. From the SAP Easy Access menu, choose Master Data Supply Chain Engineer Make Settings .
2. In the SCE settings profile, choose Model Maintenance .
3. Set the Include Objects to Ensure Model Consistency indicator if you want all dependent objects that are necessary for model consistency to be assigned
automatically. See table below.
4. Set one or more of the other indicators if you want to assign objects that are attached to the primary object but are not necessary to maintain model
consistency (for example, products at a location). See entries in table below:
Model Consistency and Dependent Objects
Primary Object

Dependent Object

Location

Loc. prod.

Resource

PPM

Location product

Location

Assign Objects to Ensure Model


Consistency

Delete Objects to Ensure Model


Consistency

Resource
PPM
Resource

Location

X
X

Loc. prod.

PPM

PPM

Location

Loc. prod.

Resource

Location of resource

For locations, you can also specify that the following objects are to be automatically assigned or deleted:
Location products
Resources
PPMs

!--a11y-->

1.1.6.3.5 Deleting Objects from Model


Procedure
1. Access your model in Change mode.
2. From the tree structure, choose the object you wish to delete from the model.
3. Open the context menu by clicking the right-hand mouse button and choose Delete Objects from Model or Model Objects All Object Types
Delete from Model .
If you are deleting products or locations, you must specify whether you want to delete the product, the location, or the location product.

If you delete a location for which dependent transportation lanes still exist, you get a warning message. When you delete the location, the
dependent transportation lanes are automatically deleted as well.
4. The selection screen appears. Adjust the selection if necessary.
5. When prompted, confirm deletion with Yes .

If you have set the indicator for the dependent objects in the SCE user settings, ALL dependent objects will be deleted along with the primary
object.
For more information, see:
SCE Settings Maintenance

PUBLIC
2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 21 of 120

!--a11y-->

Supply Chain Queries and Data Maintenance


Purpose
The SCE enables you to view data pertaining to the different elements in your chain, and also allows you to maintain the model objects at the same time. You can
submit queries for information on individual or combined elements in the chain. For example, you can query for a list of all products assigned to a specific location
in your model. At the same time, you can add products to that location or make changes to the location master or product master.

Procedures
Displaying and Maintaining Location Data
Displaying and Maintaining Product Data
Displaying and Maintaining Resource Data
Displaying and Maintaining PPM Data
Transportation Lane Data

!--a11y-->

Displaying and Maintaining Location Data


Use
In this step, you can view and change the data belonging to each location that you have maintained in your supply chain. You access the data by launching
queries.

Prerequisites
You have maintained the location data.

Procedure
1. Access your model via the SAP menu: Master Data Supply Chain E ngineer . Choose display mode if you want to view the object, and change mode
to maintain objects in the model.
2. Choose Location .
3. In the overview tree, there are two levels: location type and individual locations. Open the relevant context menu by clicking the right-hand mouse button.

Depending on the activity (for example, query for list of models), this screen appears, giving you the option to change your selection before
continuing.
4. You can perform the following activities for each level.
Location Type

Result

Add/delete objects to or from work area

Objects are added to or deleted from work area.

Individual Locations

Result

Display/Change

Location
Location product

The location master appears


The location master appears

Quota arrangements

All incoming or outgoing product quota arrangements maintained for a specific location in
the current model are displayed and can be changed.

Display RFQ process

RFQ option is displayed

Transportation lanes

Incoming or outgoing transportation lanes are displayed.

Incoming
Outgoing
Queries:
List of models

A list of all models that this location is assigned to.

Product list

A list of all products assigned to this location.

Resource list

A list of all products assigned to this location.

PUBLIC
2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 22 of 120

PPM list

A list of all PPMs assigned to this location

Transportation network (list or map)

The transportation network shows all the transportation lanes (starting with this location),
all the products assigned to this location and to the destination locations, as well as all
products assigned to the lanes.

Production network (list or map)

The production network shows all products assigned to this location and all its
transportation lanes.

Product list (model independent)

A list of all products assigned to this location.

Delete from work area

Use this context menu option to delete the objects from your work area.

Delete from work area

You can also perform these activities from the Supply Chain Engineer main menu. Choose

Model Objects

....

For more information, see Maintaining Objects in Model.

!--a11y-->

Displaying and Maintaining Location Product Data


Use
In this step, you can view and maintain data on each location product that you have maintained in your supply chain. You access the data by launching queries.

Prerequisites
You have maintained the location product data.

Procedure
1. Access your model via the SAP menu: Master Data Supply Chain E ngineer . Choose display mode if you want to view the object, and change mode
to maintain objects in the model.
2. Choose Location Product .
3. Expand the product list. Open the relevant context menu by clicking the right-hand mouse button.

Depending on the activity (for example, query for list of locations and lanes), the selection screen appears, giving you the option to change your
selection before continuing.
4. You can perform the following activities:
Location Product Header

Result

Master data

Access the product master. Maintenance is possible.

Products in model

List of all location products in model

Add objects to work area

Objects are added to work area.

Location Product

Result

Display/Change

Product
Location product

Product master appears


Product master appears

Queries:
List of models

List of all models that this product is assigned to

Location and lane list

A list of all locations and lanes that this product is assigned to

PPM list

A list of all PPMs maintained for a certain product/location combination

Transportation network (list or map)

The transportation network shows all transportation lanes and locations that this product
is assigned to.

Production network (list or map)

The production network shows all transportation lanes and locations that this product is
assigned to.

Location list (model-independent)

List of all models that this resource is assigned to

Delete from work area

Use this context menu option to delete the objects from your work area.

You can also perform these activities from the Supply Chain Engineer menu. Choose Model Objects

PUBLIC
2014 SAP SE or an SAP affiliate company. All rights reserved.

....

Page 23 of 120

For more information, see Maintaining Objects in Model.

!--a11y-->

Displaying and Maintaining Resource Data


Use
In this step, you can view or maintain data belonging to each resource that you have maintained in your supply chain. You access the data by launching queries.

Prerequisites
You have maintained the resources.

Procedure
1. Access your model via the SAP menu: Navigation Supply Chain E ngineer . Choose display mode if you want to view the object, and change mode to
maintain objects in the model.
2. Choose Resource .
3. There are two levels in the overview tree: resource type and the individual resources. Open the context menu by clicking the right-hand mouse button.

Depending on the activity (for example, query for list of models), this screen appears, giving you the option to change your selection before
continuing.
4. You can perform the following activities for each level.
Resource Type

Result

Add objects to work area

Objects are added to work area.

Individual Resources

Result

Display

Resource master appears

Queries:
List of models

A list of all models that this resource is assigned to appears

Delete from work area

Use this context menu option to delete the objects from your work area.

You can also perform these activities from the Supply Chain Engineer menu. Choose

Model Objects

....

For more information, see Maintaining Objects in Model.

!--a11y-->

Displaying and Maintaining PPM Data


Use
In this step you can view and maintain the data belonging to each PPM that you have maintained in your supply chain. You access the data by launching
queries.

Prerequisites
You have maintained the PPM.

Procedure
1. Access your model via the SAP menu: Navigation Supply Chain E ngineer . Choose display mode if you want to view the object, and change mode to
change objects in the model.
2. Choose Production .
3. There are two levels in the overview tree: the PPM header and the individual PPMs. Open the context menu by clicking the right-hand mouse button.
4. You can perform the following activities for each level.

PUBLIC
2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 24 of 120

PPM Header ...

Result

PPM master data

Access the PPM master. Maintenance is possible.

PPMs of model

List of all PPMs in model

Add objects to work area

Objects are added to work area.

PPMs

Result

Display

PPM master appears

Queries:
Model list

A list of all models that this PPM is assigned to

Delete from work area

Use this context menu option to delete the objects from your work area.

You can also perform these activities from the Supply Chain Engineer menu. Choose

Model Objects

....

For more information, see Maintaining Objects in Model.

!--a11y-->

Displaying and Maintaining Transportation Lane Data


Use
In this step, you can view and change the data on the transportation lanes that you have maintained for the location products in your supply chain. You access the
data by launching queries.

Prerequisites
You have maintained transportation lanes.

Procedure
1. Access your model via the SAP menu: Navigation Supply Chain E ngineer . Choose display mode if you want to view the object, and change mode to
change objects in the model.
2. Choose Transportation Lane.
3. There are two levels in the overview tree: the lane header and the individual lanes. Open the context menu by clicking the right-hand mouse button.

Depending on the activity (for example, query for list of locations and lanes), this screen appears, giving you the option to change your selection
before continuing.
4. You can perform the following activities for each level.
Transportation Lane Header Data

Result

Mass maintenance of lanes

Lane maintenance screen appears in change mode

Mass maintenance of lanes

Lane maintenance screen appears in change mode

Change lane parameters

Parameter maintenance screen appears in change mode

Transportation Lanes

Result

Display

Lane maintenance screen appears, populated with relevant information

Change
Lane
Mass maintenance
Parameters

Lane maintenance screen appears in change mode


Parameter maintenance screen appears in change mode

Delete from model

Delete lane from the model.

Queries:
List of products

A list of all products assigned to this lane

Location and lane list

A list of all products, lanes, and locations assigned to this lane

Transportation network (list or map)

The transportation network shows all locations, products, and lanes that are connected to
this lane

Production network (list or map)

PUBLIC
2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 25 of 120

You can also perform these activities from the Supply Chain Engineer menu. Choose

Model Objects

....

For more information, see Maintaining Objects in Model.

!--a11y-->

1.2 Location
Definition
A logical or physical place at which products or resources are managed on a quantity basis.
The following standard location types exist:
Production plant (1001)
Distribution center (1002)
Shipping point (1003)
Transportation zone (1005)
Stock transfer point (1006)
Storage location MRP area (1007)
Customer (1010)
Vendor (1011)
Subcontractor (1050)
Transportation service provider (1020)
Terminal (1030)
Geographical area (1031)
Store (1040)

Use
If you assign a location to a supply chain model, SAP APO takes the location into account in the planning. For more information, see Supply Chain Model,
Planning Version and Supply Chain Engineer.
For information enabling you to set up the location master data maintenance display on a user-specific basis by suppressing individual tab pages, see UserSpecific Display Profiles for Master Data Maintenance.
For information on logging changes for location master data, see Change Logging for Master Data.
For information on the where-used list for location master data, see Where-Used List for Master Data.

!--a11y-->

Displaying, Creating, and Changing a Location


Use
At this point, you can display, create, and change the master data for a location. For information on the deletion of a location, see Deleting Locations.

Procedure
1. From the SAP Easy Access menu, choose SAP APO Master Data Location . The Location Master Data: Initial Screen appears
2. Enter a location number and a location type. Location types are predefined.

When you first choose a location type, the input help for the Location field shows you all already existing locations of this location type.
Choose:
Display , to view an already created location
Change , to alter an already created location
Create , to create a new location
Set Planning Version , to set a planning version f or a location. The system sets the active planning version 000 by default.
Assign Model, to assign one or more supply chain models to a location.
3. The screen for the selected location appears.
4. Choose a tab page and enter the relevant data in the fields.

PUBLIC
2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 26 of 120

You can choose from the following tab pages:


Function

Tab page

Maintain General Data

General

Maintain Address

Address

Maintain Calendar Data

Calendar

Maintain Transportation Planning/Vehicle

TP/VS

What you should know

Scheduling (TP/VS) Data


Maintain Resource-Relevant Data

Resources

Maintain Supply Network Planning (SNP) Data

SNP

Maintain Additional Data

Additional Data

The fields on the Addit . tab page are fields that must
be released in Customizing before they become
available. In the APO Implementation Guide,
choose Advanced Planning and Optimization)
Master Data Define Free Attributes .

Maintain Vendor-Managed-Inventory (VMI) Data

VMI

Maintain Transportation Service Provider (TSP) Data

TSP

Maintain Available-to-Promise (ATP) data.

ATP

The VMI tab page only applies to location type 1010


Customer .
The TDL tab page applies only to location type
1020 Transportation Service Provider .

Input fields that do not exist for other location types are activated for the location type 1007 MRP Area .
5. On each tab page, w hen you have finished entering your data choose Save.

!--a11y-->

1.2.2 Deleting a Location


Use
If you wish to delete a location, first set the deletion flag before finally deleting the location in a second step. In this way you can schedule the actual deletion
process for a later point in time, not just for a single location but for several. You can carry out the delete operation in the background.

Prerequisites
The general prerequisites for the deletion of master data apply.
You have eliminated any still-existent dependencies involving this location. Possible dependent objects include ATP assignments or a product, model, or
resource assignment, for example.
For more information, refer to SAP Note 572579.
To clarify existing dependencies, you can generate a where-used list for the location that is to be deleted.

Procedure
1. On the Location Master: Initial screen, choose a location and then choose Location Deletion Flag .
On the following screen, set the deletion flag for the location and choose Save .

You can remove the deletion flag by unsetting the indicator for the relevant location.
Choose Extras Delete Locations, to finally delete one or more locations that have been flagged for deletion. You can either perform the deletion
immediately or schedule it for a later point in time.

!--a11y-->

1.2.3 Location Hierarchy


Definition
Locations can be displayed using hierarchy relationships. You can display distribution centers, cities and transportation zones in hierarchies, for example.
You can maintain hierarchies for locations and location products.
See also:
Hierarchy

PUBLIC
2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 27 of 120

See Implementation Guide documentation, under Advanced Planner and Optimizer Master Data Define Hierarchy Structure or Define Hierarchy .
!--a11y-->

1.2.4 Application Log for Location


Use
An application log for a location is a tool for collecting messages, exceptions, and errors. After being logged, this information is displayed in list form.

Features
The location application log shows you the messages issued by the following programs:
Deletion program for locations (program /SAPAPO/DLOC_DEL_JOB )
The application log for this program provides you with an overview of where references to the deleted location still exist. You can then remove these.
All programs capable of running in background mode.
Logs can be displayed, saved in the database, and deleted from the database.
You can call up the following information:
Basic header information (kind of log, who created it when and how, etc.)
Long text of message
Detailed information
Technical information

Activities
You can display logs from the SAP APO Easy Access menu via Master Data Location Application Log Display Application Log .
You can delete logs from the SAP APO Easy Access menu via Master Data Location Application Log Delete Application Log .
See also:
Application Log - Guide for End Users

!--a11y-->

1.2.5 Geocoding
Use
The term geocoding comes from the area of geographical data processing. It describes the process for determining the geographical coordinates (longitude and
latitude, altitude) from the address data given.
There are various commercial geocoding programs that determine the required data using the address attributes (country, region, postal code, city, street, and so
on). It is therefore possible in many ways to enhance the existing data basis of these programs gradually (per country, for example).
Within the SAP system, an interface has been created for such geocoding programs that is generally accessible for applications. Geocoding is a service that is
not firmly integrated into the central address management (CAM). Applications that do not use CAM can nevertheless implement geocoding. In addition, in a
further step, geocoding has been installed directly into the central address management (CAM) to simplify applications and their usage.
The coordinates determined can be used in various applications; for example, in the following applications:
Display of business objects on a map (localization of a business object on a map using address data)
Determination of the distance (distances can be calculated on the earths surface from the geocoordinates determined; for example, as a first approximation
as the crow flies or with the relevant map material on a street basis)
Routing (for example, in Transportation Planning, determining a route on a street basis)
Regional evaluation (for example, evaluating all customers within a radius of 50km or determining the nearest competitor)
The solution chosen by SAP guarantees a problem-free connection to various geocoding programs. A model has been selected that provides a single interface for
SAP applications. In Customizing it is possible to pass on these addresses, on a country-specific basis, to various geocoding programs. This distribution function
is carried out by the SAP geocoding framework. This function allows various geocoding programs (for example, a special geocoding program for North America,
another for Europe) to be used in the system. Depending on the country given in the address, the various geocoding programs are used. The geocoding programs
are called via an interface defined by SAP. Manufacturers of geocoding programs can be validated for use of this interface.
SAP SCM
Specifically in SAP SCM, you have the option of geocoding the locations that have an address, using the PTV eServer geocoding program. For more information,
see the Service Marketplace under service.sap.com/instguides mySAP Business Suite Solutions mySAP SCM Using SAP SCM 5.0 Server
Installation Guide - PTV eServer.

PUBLIC
2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 28 of 120

!--a11y-->

Calculation of Transportation Zone Coordinates


Use
You can use this program to convert the existing ERP data for a transportation zone into the geographical coordinates of a geolocation. A geolocation is defined by
the following data:

Latitude
Longitude
Time zone
Precision of the geolocation (for example, continent, country, region, postal code)

The system calculates the transportation zone coordinates by means of a geocoding program. The program determines the geographical latitude and longitude of
the transportation zone. You can use this data to calculate the distance between two business partners, for example.
The geocoding is carried out according to the required precision, which may be defined at the level of country, region, postal code, place, street, or house number
The SAP geocoding program supplied works at the country and region levels.

Prerequisites
You have made the basic settings for geocoding in Customizing for SAP Supply Chain Management (SAP SCM) under General Settings Set Up
Geocoding .
You have entered the necessary address data. The system calculates the transportation zone coordinates on the basis of this address data.

Activities
On the SAP Easy Access Menu mySAP Supply Chain Management screen, choose A dvanced Planning and Optimization
Location Calculate Transportation Coordinates .
On the initial screen, enter a supply chain model and choose Execute .

Master Data

If you set the Take Deletion Flag Into Account indicator on the initial screen, the customer and vendor locations that are assigned to the
transportation zone and for which the deletion flag has been set are not taken into consideration in the calculation of the transportation zone
coordinates.
Choose the transportation zones for which you wish to calculate the coordinates from the list of results and then choose Calculate Coordinates .
The system calculates the coordinates of the selected transportation zones. You will find the geographical data of the transportation zones on the General tab
page of the location master record.

!--a11y-->

Interface for Third-Party Geo-Coding


Use
SAP provides an interface for third-party vendors of geo-coding programs. This interface describes how a company developing geographical information systems
(GIS) can attach its geo-coding program to the SAP system. Thus, third-party vendors can offer a complete geo-coding package with regard to implementation,
delivery, and Customizing.

Prerequisites
The geo-coding interface is valid for SAP's basis releases 4.6C, 4.6D, and 6.10.

You are not required to set up a user interface. The dialog box for selecting an address is part of the SAP geo-coding framework.

Features
Internal Structure of Geo-Coding Framework
The SAP system uses a geo-coding framework that provides a dispatcher. The dispatcher enables you to choose between several geocoders for a given address
and an interface to ABAP applications. The application calls this dispatcher in order to pass one or more addresses. The dispatcher chooses the correct geocoder
(depending on the country where the address is located and on Customizing settings), and then calls it via the geo-coding interface.
The following figure shows the geo-coding framework from the left (application) to the right (geo-coding program). The relevant part for geo-coding program suppliers
can be found in the right-hand section of the figure (colored red), including the Interface to geo-coding programs.

PUBLIC
2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 29 of 120

Data Exchange Between the SAP Geo-Coding Framework and the Geo-Coding Program

Attachment of Geo-coding Programs to the SAP System


You can attach your geo-coding program to the SAP system using:
the ABAP IF_GEOCODING_TOOL interface or
the RFC interface.
For more information about the different parameters and data types used, see
Parameter Description
Data Types of the ABAP interface
Data Types of the RFC interface
ABAP IF_GEOCODING_TOOL Interface
To attach a geo-coding program to the SAP system via the IF_GEOCODING_TOOL interface, you must first implement a class in ABAP/OO. This class must
then implement the IF_GEOCODING_TOOL interface. This interface defines the GEOCODE method as follows:
method if_geocoding_tool~geocode
importing

exporting

changing

addresses

type

aes_addr_table

xinfo

type

geocdxinfo

results

type

geocd_res_table

choice

type

geocd_choice_table

relevant_fields

type

geocd_addr_relfields_sortedtab

corrected_addresses

type

aes_addr_sortedtable

messages

type

aes_msg_table

containers

type

aesc_sortedtable.

The interface always works with tables and is able to run mass transactions. Each address carries an identifier ( GUID16) for identification purposes. The geocoding program needs to assign the identifier to all calculated results. Within this documentation, only one address is passed to the method for simplification
purposes.

PUBLIC
2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 30 of 120

RFC Interface
To attach a geo-coding program to the SAP system via the RFC interface, you must implement an RFC server and use SAP's generic geocoder class to call it via
RFC. The RFC destination and geocoder function name can be maintained in the geo-coding customizing settings. The ABAP class (
CL_GEOCODER_GENERIC_RFC) simply maps the given parameters to RFC-safe structures and passes them to the RFC server, which you must implement.
We recommend that you use a function name such as RFCGEOCODER_pv_c, where pv is a product identifier and version number, and c your company
identifier. The maximum length of such a function name is restricted to 30 characters. For example, an SAP geocoder could use a name such as
RFCGEOCODER_GC10_SAP.
This interface is as follows:
RFC_FUNCTION name_is_up_to_you
importing

exporting

changing

addresses

type

aes_rfc_addr_table

xinfo

type

geocdxinfo

time_zone

type

timezone

results

type

geocd_res_table

choice

type

geocd_choice_rfc_table

relevant_fields

type

geocd_addr_relfields_sortedtab

messages

type

aes_msg_table

containers

type

aesc_rfc_sortedtable

container_lines

type

aesc_cont_sortedtable.

Differences Between IF_GEOCODING_TOOL and RFC Interfaces


A few arguments have changed in the RFC interface. These changes come from the fact that the address type has been changed from ADRC_STRUC in the OO
interface to GEOCD_ADDR in the RFC interface. Addresses occur in exactly these two arguments.
The argument time_zone has been added. This makes it easier for you to return the required time zone. Note that all addresses passed always come from the
same country. Thus we pass only one tzone, which is valid for all the addresses in the respective country. This method works fine for countries with just one time
zone and you only need to return this value. If you write a geocoder for a country with multiple time zones, such as the US or Russia, it is your job to determine the
correct time zone for a given address.
The argument corrected_addresses has been omitted because the SAP geo-coding framework corrects the addresses on its own.
The arguments choice and containers have been changed due to restrictions in RFC calls (no tables in tables). Argument container_lines has been added and is
now used in conjunction with choice and containers.

We recommend the RFC approach for the following reasons:


- There is no requirement to write ABAP coding.
- Certification and/or validation is easier.
Example for a result in container_lines
The address with ID=AF6C32 could have been geocoded (which can be seen by the zero in column COUNT), while the address with ID=FCA753 is ambiguous
(two entries with COUNT=1 and COUNT=2). Thus, address FCA753 has two corresponding entries in table CHOICE, while address AF6C32 has a corresponding
entry in table CONTAINERS.
ID

COUNT

SERVICE

FIELD

VALUE

FCA753

GEOCODING

LONGITUDE

1.234

FCA753

GEOCODING

LATITUDE

34.243

FCA753

GEOCODING

LONGITUDE

-53.987

FCA753

GEOCODING

LATITUDE

12.433

AF6C32

GEOCODING

LONGITUDE

38.432

AF6C32

GEOCODING

LATITUDE

-84.342

Activities
Customizing Settings
1. In Customizing for General Settings , register your geo-coding program in the SAP system by selecting Geo-Coding Register Geo-Coding Program in the
System .
Enter the value for SRCID that you received from SAP and the name of your class. When using an RFC interface, the third-party vendor can have his own
SRCIDs.
Save your entry. From now on, the SAP system only works with SRCID.
2. Set up a country for your geo-coding program in Customizing for General Settings by selecting Geo-Coding Assigning Geo-Coding Program to Countries .

PUBLIC
2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 31 of 120

Create a new line for the desired country, enter the value for SRCID that you received from SAP, and enter a value for the sequence. If there already is an existing
line entered for this specific country, select a number smaller than this one.
Set the exclusive flag.
3. Mark all fields of the ADRC_STRUC address structure that will be used to determine the geographical location in Customizing for General Settings by
selecting Geo-Coding Assign Relevant Address Fields for Geo-Coding for each attribute used in your geo-coding process. First enter the ID of your geocoding program, then enter a value in the address field (or press F4 for a list of possible attributes).

To test it, run the GEOCODING_FIRST program. It is a very simple program that lets you enter an address and prints out the values returned
from the geo-coding program. As this is only a test program, we recommend using it as an entry point for your test program. You can also use this
program for testing the SAP geo-coding program SAP0 that works on a country/region basis.
Keep in mind:
You are not required to write a geo-coding program for all countries at once.
It is possible to use more than one geo-coding program.
It is possible to set up the system for using specific geo-coding programs for specific countries.

Example
Fine-Tuning the Customizing Settings
A customer wants to use two different geo-coding programs for the same country (for example, France): a reasonable version that works on a regional basis in
France (for example, the SAP0 geo-coding program that is contained in the standard delivery) (Geocoder1), and one that works at street level for Paris as capital
of France (Geocoder2) for routing purposes.
You can set up Customizing in two different ways:
1. Run Geocoder1 to get a valid geographical location somewhere in France, and then improve it by trying Geocoder2, which may improve the location if it is in
Paris.
In Customizing for General Settings , select Geo-Coding Assign Geo-Coding Program to Countries . For France, Geocoder1 needs to get a value for the
Sequence column that is smaller than Geocoder2 to make the program run earlier. But although Geocoder1 may succeed, we need to run Geocoder2, which
may improve the result of Geocoder1. This requires that you remove the exclusive flag in Customizing.
This solution requires that you ALWAYS run both of the registered geo-coding programs, even for addresses in Paris.
2. Run Geocoder2. Only if the address is not located in Paris, start Geocoder1.
In Customizing for General Settings , select Geo-Coding Assign Geo-Coding Program to Countries . For France, Geocoder1 needs to get a value for the
Sequence column that is higher than Geocoder2 so that the program runs later. If Geocoder1 succeeds (because it found an address in Paris), Geocoder2 does
not need to be run because there is no chance for it to improve the location. For this set, the exclusive flag of Geocoder2, which means Do only continue if no
result (result=6 -> not responsible
class=Section2>
) was determined. If this flag is set once for a geo-coding program, all geo-coding programs for the same country with a higher value in the Sequence column are
implicitly set as exclusive.
This is the preferable solution because of its higher efficiency, but it requires the geo-coding program with the higher order value to be able to improve on an
already existing location.

!--a11y-->

1.2.5.2.1 Parameter Description


Use
The following table lists the parameters that can be used when attaching your geo-coding program to the SAP system via the ABAP IF_GEOCODING_TOOL
interface.
For more information about the differences between the parameters given to the IF_GEOCODING_TOOL interface and those passed via the RFC interface, go to
section Differences Between IF_GEOCODING_TOOL and RFC Interfaces in Interface for Third-Party Geo-Coding.
addresses

The interface passes all addresses in the table to the geo-coding program. Each entry consists of an ID and the address
data itself (ADRC_STRUC structure).

When implementing the geo-coding program via the RFC interface, the data type of the address is different. It is
GEOCD_ADDR which is a subset of ADRC_STRUC.
xinfo

This table is used to pass additional information:


SRCID
This attribute (SourceID) is an identifier for the geo-coding program. This value is set in Customizing and simply
needs to be returned in the geo-coding result container.
COUNTRY
All addresses passed in addresses are from this country.
LANGUAGE
This attribute displays the user language. Language code as defined in ISO 639.

PUBLIC
2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 32 of 120

results

This table is used to return the status from the geo-coding process. Each entry consists of the ID to identify the
corresponding address. For each address you need to return a result value ( RES attribute) with valid values (shown in
bold font):
0

Geo-coding was successful. The result is


unambiguous. The result has been returned in the
containers parameter.

No geo-coding was required because of non-relevant


address changes.
This value will be returned by the SAP geo-coding
framework and is not allowed as a result value by the geocoding program.

The result from geo-coding was ambiguous. The most


probable address has been selected.
This value will only be returned in batch processing and is
not allowed as a result value by the geo-coding program.

The result from geo-coding is ambiguous. Choices


are available (see also the CHOICE export
parameter).
This value should be returned if the user needs to
select one out of a few different addresses.

The result from geo-coding is ambiguous. There is no


choice available because the address data was not
clearly specified.
This value should be returned if the list of choices is
too big (too big is defined by you) or no match was
found. In interactive mode, the user will then be
asked to enter more data and geo-coding will be
continued.

Geo-coding was not successful.


This value should only be returned if serious
problems occurred within your program (program
errors, illegal states, ...).

The program was not responsible.


This value should only be returned if your program
was called for an address that cannot be geocoded.
Example: Your program is responsible for all
addresses in New York but the address given is
located in San Francisco. In this case, the SAP geocoding framework will dispatch the address to the
next program.

choice

This table is used to return a list of addresses the user can choose from. It will only be used if the return value in the
results parameter equals 3.
The structure of the table is as follows:
ID
RANKING
PERCENTAGE
ADDR_SHORT
ADDRESS
COUNT (CONTAINER in the ABAP interface, see argument CONTAINERS for details)
The table starts with the ID attribute.
The following RANKING and PERCENTAGE attributes will be used to put these addresses in order. RANKING is
used internally to determine the order. PERCENTAGE is only used for display purposes and does not have an impact
on the displayed order.
The addr_short attribute is mandatory and is used for displaying the address in the dialog box.
In the address attribute, you must store the complete modified address as it would be passed from an external source.

The addresses data type is different when using the RFC interface. For more information, see section Differences
Between IF_GEOCODING_TOOL and RFC Interfaces in Interface for Third-Party Geo-Coding.
RFC interface:
The final count attribute is used in conjunction with the container_lines attribute. container_lines holds all pairs of
service/key/value triples with results from geo-coding (for example GEOCODING/LONGITUDE/13.533). To identify
such an entry, each such line has ID/COUNT as access key. For more information, see the example in the Example
for a result in container_lines section in Interface for Third-Party Geo-Coding. (The address with ID FCA753 returns
a list of two addresses in choice and corresponding geographical data in container_lines ( count 1 & 2 in the table).
Please do only use count values greater than or equal to one. Zero is reserved for the unambiguous result of the geocoding process (see argument containers).
ABAP interface:
If you use the ABAP interface, container directly links to a table with corresponding container lines.
relevant_fields

Currently SAP displays the short form of the address ( addr_short attribute) in the selection dialog box. This table
contains the selection-relevant attributes of the returned addresses in the choice parameter. Only the attributes
mentioned in this table are displayed.
For example, if the user wants to geocode Frankfurt in Germany, he will encounter the problem that there are two cities
called Frankfurt in Germany (Frankfurt-upon-Oder and Frankfurt-upon-Main). The geo-coding program returns a choice
of addresses. Though these addresses also contain attributes like street name and house number, there is no need to
display these fields if the user first needs to select the correct town. So you may only return the attribute names
COUNTRY, POSTCODE and CITY1 in relevant_fields. A list is now displayed that shows only these three relevant
fields.

PUBLIC
2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 33 of 120

corrected_addresses

Do not change this attribute. Usually this attribute is used for internal purposes only.

messages

It is possible to create messages that are displayed to users or written to the application log. There are some predefined
messages in the SZGEOCODING development class. Simply append messages to this table. Do not modify or delete
a message.

containers

This is a table of AES containers. For each imported address, there will be an AES container to be exported. Again,
each AES container can be identified via the ID.

Note that for each address passed to the geo-coding program, there will also be an AES container passed with the
corresponding ID. So it is not required to create a new AES container entry in the table.
The attributes of each AES container structure are ID, CONTAINER, and CANCELLED in the ABAP interface, and ID
and CONTAINER in the RFC interface.
CANCELLED should not be set. This flag is set by the SAP geo-coding framework when users cancel the selection of
an address.
More details regarding the container are inside the AES container: One line of such a container consists of a SERVICE
field that describes which service created this line. For geo-coding purposes, use constant GEOCODING (upper case
is mandatory). The possible values for the FIELD attribute are LONGITUDE, LATITUDE, ALTITUDE, SRCID,
SRCTSTMP, PRECISID, and TZONE (upper case is mandatory). The VALUE attribute is used to store values for the
fields given in the FIELD attribute.
For a description of the container, see the graphic in section Data Exchange Between the SAP Geo-Coding Framework
and the Geo-Coding Program in Interface for Third-Party Geo-Coding.
For a description about the possible values and their data format, see Data Types of the ABAP interface.
RFC Interface:
For technical limitations, a direct link to the container table is not available in the RFC interface. Instead the ID is used
as link to the CONTAINER_LINES attribute, where the lines of the container are stored. Store container lines using
the address ID and COUNT=0 as key to table CONTAINER_LINES.

!--a11y-->

1.2.5.2.2 Data Types of the ABAP interface


Use
The following section describes the data types you can use when attaching your geo-coding program to the SAP system via the ABAP IF_GEOCODING_TOOL
interface. For more information about the data types passed via the RFC interface, see Data Types of the RFC interface.
Below, you will find the data types for the field values returned in the container (see the Data Exchange Between the SAP Geo-Coding Framework and the GeoCoding Program section in Interface for Third-Party Geo-Coding).
The data type of the VALUE attribute is char255. This data type enables you to store any kind of data. For the LONGITUDE, LATITUDE, ALTITUDE, SRCID,
SRCTSTMP, PRECISID, and TZONE attributes that are relevant for geo-coding, you need to convert your data to char255. Then, the SAP applications need to
convert these char255 strings back to real data types. These data types are defined in the GEOCODING structure.
GEOCODING structure

Type

Domain

GUIDLOC

geoguid

SYSUUID

LONGITUDE

geolon

GEOLONLAT

LATITUDE

geolat

GEOLONLAT

ALTITUDE

geoalt

GEOALT

SRCID

geosrcid

CHAR4

SRCTSTMP

timestamp

TZNTSTMPS

PRECISID

geoprecis

D_GEOPREC

TZONE

timezone

TZNZONE

The GUIDLOC attribute is for special use only. Do not create an entry with the GUIDLOC! field. The meaning of the LONGITUDE, LATITUDE, and ALTITUDE
attributes is self-explanatory. Longitude and latitude need to be passed in WGS84 data format. Altitude should be passed in meters above sea level and are set
to zero if unknown.
The SRCID attribute is an identifier for the program that determines the geographical data. The SRCID value is passed in the XINFO structure and can simply be
copied to your result.
The SRCTSTMP attribute holds a timestamp reflecting the time and date of data determination (this is not the date of geo-coding a specified address). A timestamp
always contains the time and date in the UTC time zone. The format of a timestamp is YYYYMMDDHHMMSS:
YYYY

Year

MM

Month

DD

Day

HH

Hour

MM

Minute

SS

Second

PUBLIC
2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 34 of 120

An example for a valid timestamp is 20001224121314, which is December 24th, 2000, 12:13:14, UTC time zone.
The PRECISID attribute describes how precisely a geographical location has been determined. The following values have been defined in the D_GEOPRECIS
domain.
0000

Information not available

0100

World

0200

Continent

0300

Country

0400

Region

0500

Borough

0600

Zip code

0700

Town

0800

District

0900

Center of street

1000

Center of interval of house numbers

1100

House number (interpolated)

1200

House number (exact)

1300

House number + additional information (for example Neurottstr. 7b)

The TZONE attribute describes the time zone in which the geographical location is located. The SAP table TTZZ lists the valid time zones. We need to determine
the time zone here because mapping from address to time zone is much easier than mapping a geographical location to time zone. You may use the
tzon_location_timezone function to determine the time zone for a given country or country + region. Determining the time zone is only difficult for bigger countries
with multiple time zones, like the US or Russia. If you do not use our framework, but start to implement an RFC server (using SAP's
CL_GEOCODER_GENERIC_RFC class for calling the geocoder via RFC), we additionally pass the time zone of the country used in the given addresses. This
makes it easier to develop geo-coding programs for countries that do not have different time zones. If you develop a geo-coding program for countries with multiple
time zones, you should ignore the given time zone.

!--a11y-->

1.2.5.2.3 Data Types of the RFC interface


Use
The following section describes the data types you can use when attaching your geo-coding program to the SAP system via the RFC interface.

Prerequisites
For more information about the data types passed via the ABAP IF_GEOCODING_TOOL interface, see Data Types of the ABAP interface.

Features
The data types of the RFC interface are as follows:
importing

exporting

changing

addresses

type

aes_rfc_addr_table

xinfo

type

xinfo

time_zone

type

timezone

results

type

geocd_res_table

choice

type

geocd_choice_rfc_table

relevant_fields

type

geocd_addr_relfields_sortedtab

messages

type

aes_msg_table

containers

type

aesc_sortedtable.

The data types will be defined using pseudo code:


aes_rfc_addr_table type standard table of aesaddrrfc;
aesaddrrfc type structure of {
id type byte[16],
address type geocd_addr
};

PUBLIC
2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 35 of 120

geocd_addr type structure of {


name_co type char[40],
city1 type char[40],
city2 type char[40],
city_code type char[12],
cityp_code type char[ 8],
home_city type char[40],
cityh_code type char[12],
regiogroup type char[ 8],
post_code1 type char[10],
post_code2 type char[10],
post_code3 type char[10],
pcode1_ext type char[10],
pcode2_ext type char[10],
pcode3_ext type char[10],
po_box type char[10],
po_box_num type char[ 1],
po_box_loc type char[40],
city_code2 type char[12],
po_box_reg type char[ 3],
po_box_cty type char[ 3],
postalarea type char[15],
transpzone type char[10],
street type char[60],
streetcode type char[12],
streetabbr type char[ 2],
house_num1 type char[10],
house_num2 type char[10],
house_num3 type char[10],
str_suppl1 type char[40],
str_suppl2 type char[40],
str_suppl3 type char[40],
location type char[40],
building type char[20],
floor type char[10],
roomnumber type char[10],
country type char[ 3],
langu type char[ 1],
region type char[ 3],
sort1 type char[20],
sort2 type char[20],
sort_phn type char[20],
addrorigin type char[ 4],
extension1 type char[40],
extension2 type char[40],
time_zone type char[ 6],
taxjurcode type char[15],
address_id type char[10],
remark type char[50],
langu_crea type char[ 1]
};
xinfo type structure of {
srcid type char[ 4],
country type char[ 3],
language type char[ 2]
}
time_zone type char[6];
geocd_res_table type standard table of geocd_ress;
geocd_ress type structure of {
id type byte[16],
res type int4,
info type char[128],
addit_info type char[64]
};
geocd_choice_rfc_table type standard table of aeschoirfc;
aeschoirfc type structure of {
id type byte[16],
ranking type int4,
percentage type numc[ 3],
addr_short type char[100],
address type geocd_addr,
container type aesc
};
geocd_addr_relfields_sortedtab
type sorted table of geocd_rlfl
with unique key id fieldname;
geocd_rlfl type structure of {
id type byte[16],

PUBLIC
2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 36 of 120

fieldname type char[30]


};
aes_msg_table type standard table of aes_msg;
aes_msg type structure of {
id type byte[16],
order_no type int4,
message type symsg
};
symsg type structure of {
msgty type char,
msgid type char[20],
msgno type numc[ 3],
msgv1 type char[50],
msgv2 type char[50],
msgv3 type char[50],
msgv4 type char[50]
};
aesc_sortedtable type sorted table of aesc_tabs;
aesc_tabs type structure of {
id type byte[16],
container type aesc,
cancelled type char
};
aesc. type standard table of aesc_struc;
aesc_struc type structure of {
service type char[16],
field type char[16],
value type char[255]
};

!--a11y-->

1.3 Product
Definition
A product is a tangible good or a service. It is the subject of business activity and is taken into account in the planning of the value chain.

Structure
Starting from the Product Master: Initial Screen , you can maintain both global and local product master data, set planning versions, assign models, and carry out
mass maintenance for products and penalty costs.
For more information, see:
Global Product Master Data
Location-Specific Product Master Data
For information enabling you to set up the product master data maintenance display on a user-specific basis by suppressing individual tab pages, see UserSpecific Display Profiles for Master Data Maintenance.
For information on logging changes for product master data, see Change Logging for Master Data.
For information on the where-used list for product master data, see Where-Used List for Master Data.

!--a11y-->

1.3.1 Global Product Master Data


Definition
Product global product master data is general master data for a product. This data is not location-dependent.
For further information, see
Location-Specific Product Master Data.
See also:

PUBLIC
2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 37 of 120

Maintaining Global Product Master Data


Carrying Out Mass Maintenance of Penalty Costs
!--a11y-->

1.3.1.1 Maintaining Global Product Master Data


Procedure
1. From the SAP Easy Access screen, choose mySAP Supply Chain Management, then Advanced Planning and Optimization Master Data
Product.
The Product Master: Initial screen appears. Here you have the following options:
View
To maintain global product master data, choose Global Data . Location-dependent product master data is not displayed in this view.
If you choose Location and enter a location, the location product master screen appears. In this view, you can also maintain global product master data.
Profile definition
On the initial screen of the product master, you can also maintain profiles, such as the lot size profile or the requirement/demand profile, independently
of the product. You can assign profiles to the product.
2. Enter a product number. The product number can be either alphanumeric or numeric. You can define the representation of the numeric product number in
SCM Customizing under Advanced Planning and Optimization Master Data Product Specify Output Format of Product Number .
The Create Product screen appears.
3. Enter the base unit of measure in which the product stock is to be measured.
4. Enter an identifier for the product. In doing so, take care not to use the special characters * (asterisk) and ; (semi-colon).
5. The following tab pages are available for global product master data.
Properties
Properties 2
On this tab page, you can specify alternative product numbers and product groups for a product.
Properties SPP
This tab page is displayed only if you are using Service Parts Planning (SPP). For more information, refer to the SAP Supply Chain Management (SAP
SCM) section of the SAP Library under Advanced Planning and Optimization Service Parts Planning (SPP).
Classification
Units of Measure
ATP
This tab page also contains location-specific product master data.
SNP1
This tab page also contains location-specific product master data.
Packaging Data
This data can be used for the packaging instructions.
Storage
This data is used in Extended Warehouse Management. Further information is available in the SAP SCM section of the SAP Library under SAP
Extended Warehouse Management.
6. Choose Save .
For more information on maintaining application-specific product master data, see:
Production Planning and Detailed Scheduling (PP/DS)
Master Data Maintenance
PP/DS Process with an SAP R/3 System
Demand Planning:
Lifecycle Planning
Like Profile.
Supply Network Planning
Master Data for Supply Network Planning
ATP
Global ATP Check
Product Allocation During Sales Order Entry

!--a11y-->

1.3.1.2 Maintaining Properties


Prerequisites
You are in the process of maintaining global product master data.

Procedure
The following fields are available on the Properties tab page:
Field

Use

PUBLIC
2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 38 of 120

Material Group

Information transferred from the OLTP or R/3 System

EAN/UPC

If you set this indicator, you specify that a European Article Number (EAN) exists for this
product. In the United States, the equivalent of the EAN is the Universal Product Code
(UPC).

Product Hierarchy

For more information, see Product Hierarchy.

Country of Origin

Country in which the product was originally manufactured.

Transportation Group

Products that can be combined in groups, because they have the same transportation
requirements.

Batch Management Requirement

If you set this indicator, you specify that the product is managed in batches.

Gross Weight

Weight of the product with the associated unit.

Volume

Cubic space occupied by the product expressed in a unit of volume. The unit of volume
must be specified.
The volume and its unit always relate to the base unit of measure.

Stacking Factor

Specifies whether and how often a pallet with this product can be stacked.

SDP Relevance

If you set this indicator, you specify that the product is relevant to Supply and Demand
Planning (SDP).

Additional Data

Additional fields are fields that are not available in the standard system and which you
must first release in Customizing. To do so, in Customizing, choose Advanced Planner
and Optimizer (APO) Master Data Maintain Freely-Definable Attributes .

Shelf Life (radio button)

If you choose this radio button, the specified use-by/expiration date is interpreted as the
final expiration date (maximum product shelf life).

Minimum Shelf Life

If you choose this radio button, the specified use-by/expiration date is interpreted as the
best-before date (minimum product shelf life).

Shelf Life (enterable field)

Overall period for which the product can be kept and/or used.

Planning with Shelf Life

Specifies whether the system is to take both the maturity and shelf life of product receipts
and the shelf-life demanded in requirements into account in the planning of this product.

Maturation Time

Period that a product needs after production before it can be used for further production or
by a customer.

Required Minimum Shelf Life

Minimum period that it is required to be possible to keep and/or use a product.

Required Maximum Shelf Life

Maximum period that it is required to be possible to keep and/or use a product.

Rounding Rule

The rounding rule facilitates the calculation of the shelf life.

1.

!--a11y-->

1.3.1.3 Maintaining Units of Measure


Use
Units of measure are maintained as part of the product master data.

Procedure
From the SAP Easy Access menu, choose SAP APO : Master Data Product . The Product Master: Initial Screen appears.
In this screen, you can display, create, or change products. You can also delete products from here, or assign them to a different model.
Enter a product number. Then choose:
Display
, to view an existing product.
Change
, to modify an existing product.
Create,
to maintain a new product.
3. Choose Enter . The screen for the selected product appears.
4. Enter the relevant data in the fields.
The following fields are provided on the Units of meas. tab page:
Units of measure

Use to Define...

Denominator

the denominator of the quotient that indicates the relationship between the
alternative unit of measure (AUn) and the base unit of measure (BUn)

Numerator

the counter of the quotient that indicates the relationship between the alternative
unit of measure and the base unit of measure

AUn

the unit of measure that can be used as an alternative to the base unit of

PUBLIC
2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 39 of 120

measure
BUn

the unit of measure in which the inventory of the product is managed

EAN/UPC code

the number that uniquely identifies a specific product

When you have entered the relevant data, choose Save.

!--a11y-->

1.3.1.4 Maintaining Classifications


Use
Classifications are maintained as part of the product master data.

Procedure
From the SAP Easy Access menu, choose SAP APO : Master Data Product . The Product Master: Initial Screen appears.
In this screen, you can display, create, or change products. You can also delete products from here, or assign them to a different model.
Enter a product number. Then choose:
Display
, to view an existing product.
Change
, to modify an existing product.
Create,
to maintain a new product.
3. Choose Enter . The screen for the selected product appears.
4. Enter the relevant data in the fields.
The following fields are provided on the Classification tab page:
Classification

Use to Define...

Reference product

a location-specific or cross-location product that is used as a reference product

Class

a product class

When you have entered the relevant data, choose Save.

!--a11y-->

1.3.1.5 Maintaining Product-Related Data for SNP1


Use
You maintain the data relevant for SNP1 as part of the product master data. Here, you can maintain data for both products and location products.

Procedure
From the SAP Easy Access menu, choose SAP APO : Master Data Product . The Product Master: Initial Screen appears.
In this screen, you can display, create, or change products and location products. You can also delete products for locations products from here, or assign
them to a different model.
Enter a product number or (for a location product) a product number and location number. Then choose:
Display
, to view an existing product/location product.
Change
, to modify an existing product/location product.
Create,
to maintain a new product/location product.
3. Choose Enter . The screen for the selected product/location product appears.
4. Enter the relevant data in the fields.

PUBLIC
2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 40 of 120

The following fields are provided on the SNP 1 tab page:


SNP1

Use to Define...

The following fields are dependent/independent of the location and are based on
Customer demand
Demand forecast
Demand forecasts that require correction
Penalty for ND

the daily penalty rate for nondelivery of the required product quantities

Delay penalty

the daily penalty rate that is used by the Optimizer to weight the delivery delay
of a product above and beyond the planned delivery date

Maximum delay

the maximum number of days that a product may be delayed

3. When you have entered the relevant data, choose Save.

!--a11y-->

1.3.1.6 Maintaining Product-Relevant Data for ATP


Use
You maintain the data relevant to ATP as part of product master data maintenance. Here you can maintain data for both products and location products.

Procedure
From the SAP Easy Access menu, choose SAP APO : Master Data Product .
The Product Master: Initial Screen appears.
On this screen, you can display, create, or change products and location products. You can also delete products or location products or assign them to a
model from here.
Enter either a product number only, or (if a location product is involved) a product number plus a location number. Choose:
Display
, to view an existing product/location product.
Change
, to change an already created product/location product.
Create,
to create a new product/location product.
3. Choose Continue .
The screen for the selected product/location product appears.
4. Enter the necessary data.
5. When you have finished entering your data, choose Save.
!--a11y-->

1.3.1.7 Product Group


Definition
Grouping of similar products. Product groups are defined for a product group type. The product group type specifies the criterion by which grouping takes place
(for example, size ). The product groups represent the instances of this grouping (for example, small , medium , large ). You define the product group type and
product groups in Customizing for the product master.

Use
Product groups are used in various processes, such as those in Service Parts Planning (SPP) . When defining product groups, you can also maintain
transportation lanes for product groups instead of for individual products, for example. For more information on maintaining transportation lanes for product groups,
see
To assign a product to an existing product group, choose Properties 2 in product master maintenance.
To assign a large number of products to an existing product group at one time, you can use the mass maintenance function. Here, the following cases exist:
You want to assign products for which an entry for a product group type already exists. To select these products, enter the following values:
Component
Product groups

Attribute
Product group

PUBLIC
2014 SAP SE or an SAP affiliate company. All rights reserved.

Value
Name of product group

Page 41 of 120

The system selects all products that are assigned to this product group. You can now also assign them to another product group, for example.
You want to assign products for which no entry for a product group type yet exists. To choose these products, enter the following values:
Component

Attribute

Value

Product groups

Product group

Initial

Product groups

Product group type

Identifier for product group type

The system selects all products fort this product group type that have not yet been assigned to a product group. You can now assign them to a product group.

Structure
Product groups consist of a product group type and a value assigned to this product group type.

Example
You want to group products according to size. For this purpose, you have defined a product group type Size . You assign the values small, medium, and large
to this product group type.

!--a11y-->

Alternative Product Number


Definition
Number under which a product is managed in the system in addition to the product number defined when it was created. An alternative product number (APN)
can be a manufacturer part number or an old material number, for example.

Use
You assign alternative product numbers to a product on the Properties 2 tab page in the products master record. Alternative product numbers are always
assigned to a type(APN type), which is defined in Customizing for the product master under Product Maintain 1.3.1.8 Alternative Product Number Type .
Alternative product numbers facilitate a more flexible search for a product, since you can conduct the search via not just one but several product numbers. To
search for an alternative product number, invoke the input help for the Product field on the initial screen of the product master and choose the Search with
Alternative Product Numbers tab page .
You can assign multipe alternative product numbers. The system does not perform a check of uniqueness.

Structure
Alternative product numbers comprise an APN type and an assigned value.

Integration
Alternative product numbers are not integrated with the ERP system via the APO Core Interface (CIF).

!--a11y-->

1.3.2 Location-Dependent Product Master Data


Definition
This master data is product master data which is assigned to a location.
See also:
Maintaining Location-Dependent Product Master Data
Carrying Out Mass Maintenance of Products
!--a11y-->

Maintaining Location-Dependent Product Master Data


PUBLIC
2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 42 of 120

Prerequisites
Your system administrator must maintain unique identifiers for valid planners. Only these planners can be assigned to a location product in master data
administration. To assign planners, in Customizing for SAP Advanced Planning and Optimization (SAP APO), choose Supply Chain Planning Specify
Person Responsible (Planner).

Procedure
1.
2.
3.
4.
5.

6.

7.
8.

9.

From the SAP Easy Access menu, choose SAP APO : Master Data Product. The Product Master initial screen appears.
Enter a product name.
Choose Location .
Choose a location.
To apply the specifications in the predefined profiles, enter the profile name for each of the following:
Lot size profile
Demand profile
SNP demand profile
SNP supply profile
Deployment profile
The relevant fields in the product master are populated with the data specified in the profiles you selected. If you modify this data, the product master cannot
be maintained globally via the profiles. Create and maintain master data profiles in Customizing. In Customizing for SAP APO Supply Chain Planning,
choose Supply Network Planning Profiles .
Choose Create . The Create Product for Location screen appears.
On this screen, you can see both the tab pages for global product master data (see also Maintaining Global Product Master Data) and those for location
product master data (described in the following).
Enter the unit of measure in which the product is measured. The system converts all the quantities you enter in alternative units of measure into the
corresponding quantities in the base unit of measure.
Enter the relevant data on the tab pages. Depending on how the master data is used, the following tab pages are now available:
Administration
ATP - both global and location-specific product master data
SNP 1 - both global and location-specific product master data
SNP 2
Requirements
Lot Size
PP/DS
Procurement
GR/GI
Additional
SPP Inventory Planning
SPP DRP
SPP Deployment
SPP Inventory Balancing/Inventory Surplus
Except for the SNP1 and ATP tab pages, which contain both global and location-specific data, these tabs contain location-specific product master data.
Unlike the global product view, the location product view also shows the tab pages containing the global product master data.
Save the entries.

More information on the maintenance of application-specific master data is available in the documentation for the relevant application. This applies, in particular, to
the following applications:
Production Planning and Detailed Scheduling (PP/DS)
Master Data Maintenance
Integration documentation:
Demand Planning:

PP/DS Process with an SAP R/3 System

Lifecycle Planning
Like Profile.
Supply Network Planning
Master Data Setup
ATP
Creating Product Allocation Procedures
Creating Sequences of Product Allocation Procedures
Maintaining Check Modes
Product Availability Check Using the Checking Horizon
Maintaining ATP Groups
Service Parts Planning (SPP)
For more information, refer to the SAP Library under Advanced Planning and Optimization Service Parts Planning (SPP) .

!--a11y-->

1.3.2.2 Maintaining Administration Data


Use
PUBLIC
2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 43 of 120

Administration data is maintained as part of the location product master data.

Prerequisites
The fields on the Administr . tab page are fields that must be released in Customizing before they become available. In Customizing, choose Advanced Planner
and Optimizer (APO) Master Data Maintain Freely-Definable Attributes .

Procedure
From the SAP Easy Access menu, choose SAP APO : Master Data Product . The Product Master: Initial Screen appears.
In this screen, you can display, create, or change location products. You can also delete location products from here, or assign them to a different model.
Enter the product number and a location number for a location product. Then choose:
Display
, to view an existing location product.
Change
, to modify an existing location product.
Create,
to maintain a new location product.
3. Choose Enter . The screen for the selected product appears.
4. Enter the relevant data in the fields.
The following fields are provided on the Administr. tab page:
Administration

Use to Define...

Production planner

the planner responsible for this area

SNP planner

the planner responsible for this area

Demand planner

the planner responsible for this area

Transportation planner

the planner responsible for this area

When you have entered the relevant data, choose Save.

!--a11y-->

1.3.2.3 Maintain Requirements Data


Use
The requirements data is maintained as part of the location product master data.

Prerequisites
The fields on the Addit . tab page are fields that must be released in Customizing before they become available. To do this, choose Advanced Planner and
Optimizer Master Data Maintain Freely-Definable Attributes.

Procedure
1. In the SAP menu choose Advanced Planning and Optimization Master Data
The Product Master: Initial Screen is displayed.

Product .

2. In this screen, you can display, create, or change location products. Enter a product and location number and choose
Create.
The screen for the selected product is displayed.

Display ,

You can also flag location products for deletion or assign them to a model. To do this, choose Product Flag for Deletion or
3. Choose the Demand tab page.
The Requirements Strategy , Pegging and Available Stock tab pages are now visible.
Enter the necessary data.

Change or

( Assign Model ).

Requirement Strategy
Fields/Area

Use to define...

Proposed Strategy

How quantities forecasted in APO Demand Planning are produced and how the demand
forecast is consumed with sales orders

PUBLIC
2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 44 of 120

Dependent Requirements
Always Coll. Requirement

That a collective dependent requirement is to be created

Possible Indiv. Cust. Reqt

That an individual dependent requirement is created, if possible

Consumption
Consumption Mode

Whether you want to use backward and/or forward consumption

Consumption Period

Number of calendar days for forward or backward consumption

Assembly Planning

Whether the system performs forecast consumption for the product's dependent demand
or transportation requirements when the dependent demand or transportation
requirements change

Pegging
Fields/Area

Use to define...

Dynamic Pegging
Pegging Strategy

How product requirements are covered

Maximum Earliness of a Receipt

The maximum time interval that could occur between an issue and a receipt element,
allowing the system to still set a pegging edge and thus create a pegging relationship
between the two in spite of the time interval

Maximum Lateness of a Receipt

The maximum duration for which a receipt element may exist before an issue element,
so that the system can still create a pegging relationship between both elements

Due Date/Time Alerts


Alert Threshold for Earliness

How far ahead an alert will be triggered if the date of a receipt element is before that of an
issue element and there is a pegging relationship between them
You also use the alert thresholds to define that early or late receipts are taken into
account to cover requirements or in the days' supply calculation.
See

Alert Threshold for Lateness

Calculation of the Days Supply

How far ahead an alert will be triggered if the date of a receipt element is after that of an
issue element and there is a pegging relationship between them

Individual Product Tolerance


Minus or Plus Product Tolerance

The maximum permitted shortage or surplus of the individual product tolerance in the
requirement element as a percentage.

Overall Delivery Tolerance


Underdelivery Tolerance

The amount, as a percentage, that specifies the amount by which the supply quantity
may fall below the order quantity

Overdelivery Tolerance

The amount, as a percentage, that specifies the amount by which an order quantity may
be exceeded

Use Quantity
Use total order quantity (Use Total Receipts)

That the total order quantity must be consumed

Consume quantity from total stock (Use Total Stock)

That the total stock quantity must be consumed

Available Stocks
Fields/Area

Use to define...

Blocked Stock, Stock in Transfer, Stock in Quality Inspection and so on

Which stocks are regarded as available in Production Planning and Detailed


Scheduling and in Capable-To-Match (CTM). This means that the system takes these
stocks into account when calculating the net requirements and in dynamic pegging

4. Save your entries.

!--a11y-->

1.3.2.4 Maintain Lot Sizes


Use
The lot size data is maintained as part of the location product master data.

Prerequisites
The fields on the Addit . tab page are fields that must be released in Customizing before they become available. In Customizing, choose Advanced Planner and
Optimizer (APO) Master Data Maintain Freely-Definable Attributes .

PUBLIC
2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 45 of 120

Procedure
1. From the SAP Easy Access menu, choose SAP APO : Master Data Product . The Product Master: Initial Screen is displayed.
2. Enter a product and a location.
Choose Display, Change or Create.
3. The screen for the selected product is displayed.
4. Choose the Lot Size tab page.
The Procedure and Quantity and Date Determination tab pages are displayed.
Enter the necessary data.

Procedure
Fields/Area

Use to define...

Lot Size DoS Prof.

The lot-sizing procedure that is to be used in production planning calculations

Lot-Size Unit

The valid unit of measure

Procedure
Lot-for-Lot

That the exact lot size is to be used in production planning calculations

Fixed Lot Size

That a fixed lot size is to be used in production planning calculations. It also specifies the
quantity that is to be ordered or produced if the available product quantity is not sufficient

By Period

That a period lot-sizing procedure is to be used with the associated period type (day,
week, and so on)

Reorder Point

That a reorder point procedure is to be used, with the corresponding type of procedure

Reorder Days' Supply

The number days for which the current stock and the planned receipts of a material
should last to cover the demand that exists at the time of planning

Planning Calendar

The planning calendar that is used for period lot-sizing procedures

Number of Periods

The number of periods in the short, medium, and long-term horizon

Quantity and Date Determination


Quantity Determination
Minimum Lot Size

Minimum procurement quantity

Maximum Lot Size

Maximum procurement quantity

TrgtStklLvl Method

The target stocks level is a value representing the available stock level that should be
reached through planning.

Assembly Scrap (%)

Scrap (as a percentage) that arises during production of the material (if the material is an
assembly)

Rounding Value

The value to which the system rounds up the procurement quantity

Rounding Profile

The key used by the system to adjust the order proposal quantity to deliverable units

Target days' supply

The number days for which the current stock and the planned receipts of a material
should last to cover the demand that exists at the time of planning

Date Determination
Safety Days' Supply

The number days for which the current stock and the planned receipts of a material
should last to cover the demand that exists at the time of planning

Use Period Factor

The indicator for determining the availability date. You can choose between requirements
date = availability date and the availability date from the period factor

Period Factor

At what point the time in a defined period the system is to create the availability dates of
receipt elements. This field only applies to period lot-sizing procedures

Stock Data
Safety Stock

The quantity that is to satisfy an unexpectedly high demand in the coverage period

Reorder Point

The quantity that is to satisfy an unexpectedly high demand in the coverage period

Maximum Stock Level

The quantity that is to satisfy an unexpectedly high demand in the coverage period

Stock

The quantity of available stock of this product in this location

SS method

The method used to calculate the safety stock

Service Level (%)

A percentage value that specifies the proportion of the requirements that is to be covered
by the warehouse stock

Demand Forecast Error (%)

Percentage depicting the mean deviation relationship between the forecast demand and
the actual demand at demand forecast level. The lower the percentage, the more accurate
the forecast is.

RLT Forecast Error (%)

Percentage depicting the mean deviation relationship between the replenishment lead
time (RLT) that was forecast and the real RLT at RLT forecast level. The lower the
percentage, the smaller the deviation between the forecast and the actual RLT.

5. Save your entries.

PUBLIC
2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 46 of 120

!--a11y-->

1.3.2.5 Maintaining Product-Related Data for SNP2


Use
Data for SNP2 is maintained as part of the location product master data.

Prerequisites
The fields on the Addit . tab page are fields that must be released in Customizing before they become available. In Customizing, choose Advanced Planner and
Optimizer (APO) Master Data Maintain Freely-Definable Attributes .

Procedure
From the SAP Easy Access menu, choose SAP APO : Master Data Product . The Product Master: Initial Screen appears.
In this screen, you can display, create, or change location products. You can also delete location products from here, or assign them to a different model.
Enter the product number and a location number for a location product. Then choose:
Display
, to view an existing location product.
Change
, to modify an existing location product.
Create,
to maintain a new location product.
3. Choose Enter . The screen for the selected product appears.
4. Enter the relevant data in the fields.
The following fields are provided on the SNP 2 tab page:
SNP2

Use to Define...

Demand profile

how the system calculates the demand

Forecast horizon

a horizon in calendar days in which the forecast is not regarded as part of the
overall demand

Pull deployment horizon

the number of days in which the distribution demand is taken into account for
calculating deployment

Period split

how the planning data is disaggregated by time when you release the demand
plan from Demand Planning to Supply Network Planning

VMI promotion lead time

Like the target days supply, which refers to the total demand without VMI
promotions, and is specified in the lot size profile, this lead time refers to the
number of days required to satisfy demand, specifically for VMI customer
promotions prior to their due date

SNP supply profile

how the system calculates supply, that is, key figures such as production and
distribution receipts

Production horizon

where Supply Network Planning stops and Production Planning & Detailed
Scheduling (PP/DS) begins

Stock transfer horizon

the number of days, beginning when the heuristic run is initiated, during which
the system does not plan transfers. The system does not generate planned
distribution receipts within this horizon but postpones them until the first day
after the stock transfer horizon

Push deployment horizon

the quantity available for distribution in the future. Receipts beyond this horizon
are too insecure to confirm by deployment

Deployment SS push horizon

the push horizon for deployment when using the safety stock

Firm production

that the production date is to be beyond the planning period

Fix transports

that the transports are to be beyond the planning period

Deployment profile

the logic that the system uses during deployment calculations to generate
distribution proposals

Fair share rule

If demand exceeds supply, the system can use fair share logic to calculate
deployment on the available to deploy (ATD) quantity. These rules allow for
alternative methods of allocating a restricted supply of a product to the demand
sources

Push distribution

push rules are used in Supply Network Planning to calculate deployment when
the available to deploy (ATD) quantity covers demand

Customer product

the material number used by the customer for this product

VMI purchasing group

the identifier for the purchase or purchaser group responsible for the purchasing
tasks associated with the VMI product

PUBLIC
2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 47 of 120

Purchasing group

the key for a purchaser or group of purchases responsible for certain


purchasing activities

Priority

the priority of the product

When you have entered the relevant data, choose Save.

!--a11y-->

1.3.2.6 Maintaining Procurement Data


Use
Procurement data is maintained as part of the location product master data.

Procedure
From the SAP Easy Access menu, choose SAP APO : Master Data Product . The Product Master: Initial Screen appears.
In this screen, you can display, create, or change location products. You can also delete location products from here, or assign them to a different model.
Enter the product number and a location number for a location product. Then choose:
Display
, to view an existing location product.
Change
, to modify an existing location product.
Create,
to maintain a new location product.
3. Choose Enter . The screen for the selected product appears.
4. Enter the relevant data in the fields.
The following fields are provided on the Procurement tab page:
Procurement

Use to Define...

Procurement type

how the product is procured (external procurement, in-house production,


external procurement or in-house production, external procurement planning)

Planned delivery time

the number of calendar days required to acquire the product or service via
external procurement

Cost function

used by the Optimizer to calculate the cost of procuring, producing, or


transporting varying quantities of products defined in intervals via the
Maintenance function

Procurement costs

all costs that are incurred in relation to procuring the product

Product storage costs

used by the heuristic and Optimizer to calculate how much it costs to store the
product in the associated storage resource (warehouse) per base unit of
measure

Safety stock penalty

the penalty costs incurred when the safety stock is violated

When you have entered the relevant data, choose Save.

!--a11y-->

1.3.2.7 Maintaining GR/GI Data


Use
The GR/GI data is maintained as part of the location product master data.

Procedure
From the SAP Easy Access menu, choose SAP APO : Master Data Product . The Product Master: Initial Screen appears.
In this screen, you can display, create, or change location products. You can also delete location products from here, or assign them to a different model.
Enter the product number and a location number for a location product. Then choose:

PUBLIC
2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 48 of 120

Display
, to view an existing location product.
Change
, to modify an existing location product.
Create,
to maintain a new location product.
3. Choose Enter . The screen for the selected product appears.
4. Enter the relevant data in the fields.
The following fields are provided on the GR/GI tab page:
Goods receipt/goods issue

Use to Define...

Goods receipt time

the time between the delivery or the production of a product and its availability
as stock

Goods issue time

the time between issuing the product from storage and transporting it

Loading group

groups of products that have the same loading requirements

Quantity propagation

quantity propagation by confirmations

Comp.adjust.confirm

component adjustment by confirmation

RemNetDrtnAdjustment

the remaining net duration adjustment by confirmation

Synchronous posting GI

whether the goods issue for this component is posted synchronously or


asynchronously in R/3

HandlCap consump. GR

how much handling resource capacity is used by the product for a particular
plan

HandlCap consump. GI

the handling capacity consumed in the goods issue

StorageCons per BUn

how much storage capacity is consumed by the product for a particular plan

GR costs

the unit of measure for a product that can be received

CostsGoodsIssue

the unit of measure for a product that can be issued

Del. time quota

the profile key for delivery time quota maintained in Customizing

Time in wareh./days

the average retention period (in days) of the location product in storage

When you have entered the relevant data, choose Save.


!--a11y-->

1.3.2.8 Maintaining Additional Data


Use
Additional data is maintained as part of the location product master data.

Prerequisites
The fields on the Addit . tab page are fields that must be released in Customizing before they become available. In Customizing, choose Advanced Planner and
Optimizer (APO) Master Data Maintain Freely-Definable Attributes .

Procedure
From the SAP Easy Access menu, choose SAP APO : Master Data Product . The Product Master: Initial Screen appears.
In this screen, you can display, create, or change location products. You can also delete location products from here, or assign them to a different model.
Enter the product number and a location number for a location product. Then choose:
Display
, to view an existing location product.
Change
, to modify an existing location product.
Create,
to maintain a new location product.
3. Choose Enter . The screen for the selected product appears.
4. On the Extra tab page, enter any additional information in the freely definable fields.
5. When you have entered the relevant data, choose Save.

!--a11y-->

1.3.3 Mass Maintenance of Location Products


PUBLIC
2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 49 of 120

Use
The mass maintenance of products refers to location-specific product master data (location products). It is possible to edit several location products in one
operation, which prevents you having to maintain them individually.

Procedure
In the Product Master Initial Screen choose Mass Maintenance of Products . You can select the records for mass maintenance via the product and location
numbers.
Set the indicator Detailed display to view all selected records and to restrict them if necessary. You can also choose the maximum number of hits to be
displayed.
When you have entered the relevant data, choose Save.
For further information on location products, see
Location-Specific Product Master Data.
!--a11y-->

1.3.4 Mass Maintenance of Penalty Costs for Products


Use
You can carry out parallel maintenance of penalty costs for several products, avoiding the need for individual maintenance.

Procedure
In the Product Master Initial Screen choose Extras Mass Maintenance Product Penalty Costs . You can maintain the penalty costs for products and
location products.
Enter the product number and description. When maintaining location products, you can also select Location, Production Planner, SNP Planner, Demand
Planner , and Transport Planner .
Set the indicator Detail display to view the number of products selected and to restrict this further if necessary.
For further information on master data maintenance for products, see
Global Product Master Data.
!--a11y-->

1.3.5 Mass Maintenance of Penalty Costs for Location


Products
Use
You can carry out parallel maintenance of penalty costs for several location products, avoiding the need for individual maintenance.

Procedure
In the Product Master Initial Screen choose Extras Mass Maintenance: Location Product Penalty Costs . You can maintain the penalty costs for products
and location products.
Enter the product number and description. When maintaining location products, you can also select Location, Production Planner, SNP Planner, Demand
Planner , and Transport Planner .
Set the indicator Detail display to view the number of products selected and to restrict this further if necessary.
For further information on master data maintenance for products, see
Global Product Master Data.

!--a11y-->

1.3.6 Setting the Planning Version


Use
PUBLIC
2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 50 of 120

You can assign location-specific product master data to a planning version to carry out planning with version-specific data.
If this data is not set, the version- in dependent data is used for a planning version.

Prerequisites
You have assigned the location product to a model. Using the F4 Help, you can choose a planning version from a list of planning versions assigned to the model.
You must create a planning version and a location product before you can make this assignment.

Procedure
1.
2.
3.
4.

You are on the Product Master: Initial Screen . Enter a product number and choose a location number for the Location view.
Choose the Set Planning Version button.
In the subsequent Set Planning Version dialog box , use F4 help to select a planning version.
Confirm the assignment with Enter. The Set Planning Version dialog box is closed and the selected planning version number is displayed in the Planning
Version field on the Product Master: Initial Screen .
5. Choose Create or Change . The Change Product for Location Version Specific screen then appears. This screen contains all the tab pages for
maintaining product master data and location product master data. You can now maintain version-specific data in all the active fields.
6. Maintain the relevant data on the tab pages for the set planning version. This data is specific location product data for a planning version.
7. Choose Save .

!--a11y-->

1.3.7 Deleting Planning Versions


Use
You can set a planning version for location-specific product master data and delete it again.

Prerequisites
You have set a planning version for a location product.

Procedure
You are in the Product Master: Initial Screen . Enter a product number and choose a location number for the Location view.
Choose the Delete planning version pushbutton.
In the subsequent Selection of Location Products with Planning Version screen, select the row containing the relevant planning version.
Confirm the assignment with Enter.

Result
The planning version assigned to the location product is deleted.

!--a11y-->

1.3.8 Assigning Models


Prerequisites
To assign a model to a product, you need to have created both a location product and a model.
You can only assign models to location products, not to the product itself.

Procedure
You are in the Product Master Initial Screen .
Use F4 help to select a product number and a location, then choose Assign model. The Assignment Location Product - Model appears.
Set the indicator for the model which is to be assigned to the location product.
Choose Save .
In the screen Assignment Location Product Model , it is possible to assign one or more models to a location product by setting the appropriate indicator. You
can also delete assignments in this screen by removing the indicator. When you have entered the relevant data, choose Save.
!--a11y-->

PUBLIC
2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 51 of 120

1.3.9 Deleting a Product


Use
To delete a product, you must first set the deletion flag before finally deleting the product in a second step. In this way, you can prepare several products for
deletion and perform the actual deletion at a later point in time perhaps in the background.
For information on how you can deactivate material master records in the Core Interface (CIF) and are then able to delete the relevant products in SAP APO, refer
to Logging Deactivated Material Master Records.

Prerequisites
The general prerequisites for the deletion of master data apply.
You have eliminated any still-existent dependencies involving this product. Dependent objects can be orders for the product or inclusion in production process
models (PPMs), for example. To clarify existing dependencies, you can generate a where-used list for the product that is to be deleted.
For more information, refer to SAP Note 571031.

Procedure
On the Product Master Data: Initial screen, choose a product, then choose Product Flag for Deletion.
1. On the following screen, set the deletion flag for the product and choose Save .

You can remove the deletion flag by unsetting the indicator for the relevant product.
2. Choose Extras Delete Products, to finally delete one or more products that have been flagged for deletion. You can either perform the deletion
immediately or schedule it for a later point in time.

!--a11y-->

1.3.10 Product Hierarchy


Definition
Products can be part of a hierarchical relationship, such as product families, product groups and products. Hierarchies can be formed for both products and
location products.
Product-relevant hierarchies are based on hierarchies (hierarchy, schema hierarchy) defined in Customizing. A distinction is made between planning products,
which are based on location product hierarchies, and configurable products, which are based on product hierarchies. Through the assignment, the hierarchies
acquire a special function (this applies exclusively to hierarchies and schema hierarchies, not to generated hierarchies).
See also:
Hierarchy
APO Implementation Guide documentation, under Advanced Planning and Optimization (APO) Master Data Product Maintain Product-Relevant
Hierarchy .

!--a11y-->

1.3.11 Defining Free Attributes


Definition
Free attributes are fields for global and location-specific product master data in which product attributes can be maintained. These fields are also used to maintain
location master data.

Use
These fields do not appear as default and must be released in Customizing. In Customizing, choose Advanced Planner and Optimizer (APO) Master Data
Maintain Freely-Definable Attributes .
For more information, see Displaying, Creating, and Changing a Location.

!--a11y-->

PUBLIC
2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 52 of 120

Inheritance of Product Master Attributes


Use
With the inheritance function, you can cause certain product master attributes to assume the same values for all the products of a location and a planning version.

Prerequisites
To set up the inheritance of product master attributes, you must extend the table structures of the attributes supplied by SAP. For more information, see Extending
Table Structures for Inheritance.
The attributes for which you set up the inheritance facility must be attributes of the location product master.

Features
Pass on values
In the standard system, the values of all attributes that are displayed in the maintenance transaction for inheritance can be passed on.
Display inherited values
Exclude attributes from inheritance
You can exclude individual attributes from inheritance by deselecting the relevant indicator in the product master menu under Edit Inheritance.

Activities
1.
2.
3.
4.
5.

From the SAP Easy Access menu, choose Advanced Planning and Optimization Master Data Product Maintain Values for Inheritance .
Enter the location and planning version for whose location products you wish to pass on values.
Enter the values of the attributes you wish to pass on in the relevant fields.
Choose Pass on Values .
The system populates the attributes of the products with the corresponding values provided that you have not explicitly excluded them from inheritance.

You cannot subsequently change inherited values manually in the product master. To be able to change the values, you must exclude the
relevant attributes from inheritance.

!--a11y-->

Extending Table Structures for Inheritance


Use
To set up the inheritance of product master attributes in a system, you must extend includes supplied by SAP in table /SAPAPO/MLREFLOC through append
structures in the customer namespace.

Procedure
1. Determine the location product fields for which you wish to use inheritance.

When choosing the fields, note that any inconsistencies arising through the passing on of the fields will not be picked up by consistency checks.
Such inconsistencies are liable to occur when quantity fields are passed on, for example.
2. Determine which of these fields belong to table /SAPAPO/MATLOC, which to table /SAPAPO/MATLSPP, and which belong to both tables.
3. Call up the table /SAPAPO/MLREFLOC.
4. Create append structures in the customer namespace for each of the following includes of this table supplied by SAP:
/SAPAPO/MLREF_I
/SAPAPO/MATLOC_R_I
/SAPAPO/MATL_SPP1_R_I

Extend just the include in each case, not under any circumstances the table.

Result
The system extends the selected fields in the tables /SAPAPO/MATLOC and /SAPAPO/MATLSPP by adding the inheritance indicator. Inheritance is now active
as standard for these fields. Values for these fields are used by the system as defaults in all products of location and planning version in question.

PUBLIC
2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 53 of 120

!--a11y-->

Creating an Append Structure for Include /SAPAPO/MLREF_I


Use
The append structure for the include /SAPAPO/MLREF_I is necessary to set up the inheritance facility in your system.

Prerequisites
You have determined the fields you wish to use for inheritance.

Procedure
1. Invoke the include /SAPAPO/MLREF_I in table /SAPAPO/MLREFLOC by double-clicking.
2. Create an append structure for this include in the customer namespace.
Choose a name for the append structure in the customer namespace in which the structures are to be stored.
Copy the field names into the append structure under Component . Copy the corresponding data elements into the structure nder Component Type . The
system supplies the values for the remaining columns automatically.
3. Save your entries and activate the append structure.

Example
1. You want to set up the inheritance facility for the fields SCOST and MAXEOQ_POD. The field SCOST comes from the table /SAPAPO/MATLOC and the
field MAXEOQ_POD from the table /SAPAPO/MATLSPP.
2. You enter ZMLREF_APPEND as the name of the append structure.
3. You copy the fields and data elements into the append structure as follows:
Example of Append Structure
Component

Component Type

SCOST

/SAPAPO/SCOST

MAXEOQ_POD

/SAPAPO/ MAXEOQ_PERIOD

!--a11y-->

Creating an Append Structure for Include /SAPAPO/MATLOC_R_I


Use
In this step, you include the fields originating from table /SAPAPO/MATLOC in an append structure.

Prerequisites
You have selected the fields you wish to use for inheritance.

Procedure
1. Invoke the include /SAPAPO/MATLOC_R_I in table /SAPAPO/MLREFLOC by double-clicking.
2. Create an append structure for this include.
Choose a unique name for the append structure in the customer namespace in which the structures are to be stored.
Copy the field names under Component . Under Component Type , specify the data element /SAPAPO/INH_FLAG for each field.
3. Save your entries and activate the append structure.

Result
The system creates the inheritance indicator for the selected fields in the product master.

PUBLIC
2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 54 of 120

Example
1. You have selected the fields SCOST and MAXEQR_POD. The field SCOST comes from the table /SAPAPO/MATLOC.
2. You enter ZMATLOC_R_APPEND as the name the append structure.
3. You copy the field name SCOST under Component and the data element /SAPAPO/INH_FLAG under Component Type as specified below .
Append Structure
Component

Component Type

SCOST

/SAPAPO/INH_FLAG

!--a11y-->

Creating an Append Structure for Include


/SAPAPO/MATL_SPP1_R_I
Use
In this step, you include the fields originating from table /SAPAPO/MATLSPP in an append structure.

Prerequisites
You have selected the fields you wish to use for inheritance.

Procedure
1. Invoke the include /SAPAPO/MATL_SPP1_R_I in table /SAPAPO/MLREFLOC by double-clicking.
2. Create an append structure for this include.
Choose a unique name for the append structure in the customer namespace in which the structures are to be stored.
Copy the field names under Component . Under Component Type , assign the data element /SAPAPO/INH_FLAG to each field.
3. Save and activate your entries.

Result
The system creates the inheritance indicator for the selected fields in the table /SAPAPO/MATLSPP.

Example
You have selected the fields SCOST and MAXEQR_POD. The field MAXEQR_POD comes from the table /SAPAPO/MATLSPP.
You enter ZMATLOC_R_APPEND as the name of the append structure.
You copy the field name MAXEOQ_POD under Component and the data element /SAPAPO/INH_FLAG under Component Type.
Append Structure
Component

Component Type

MAXEQR_POD

/SAPAPO/INH_FLAG

!--a11y-->

1.4 Resource
Definition
In the master data for resources, you define
Capacities of plant, machines, personnel, means of transport, warehouses
Resource-specific planning parameters for Supply Network Planning (SNP), Capable-to-Match (CTM) and Production Planning and Detailed Scheduling
(PP/DS)
Resource data is relevant to the planning of order dates taking working times and the available capacities of the resources into account.

PUBLIC
2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 55 of 120

The following table shows in which planning components the most important resource types are used:
Resource Type

Planning Component
PP/DS

SNP

CTM

Single-Activity Resource

Multi-activity resource

Single-Mixed Resources

Multimixed Resources

Bucket Resources

Use
Use in Routing
In SAP APO, the system saves routing data of a production data structure (PDS) or a production process model. The resource at which the activity is carried out,
is assigned to each activity in a PDS or PPM in the relevant mode. You can also define alternative resources here. The system uses the resource data to
schedule the activities.
Relationship to Supply Chain Model and Planning Version
You create a resource independently of a particular supply chain model or planning version. You assign all planning-relevant resources to a model. The system
also automatically copies the resources to all the planning versions that exist in this model.
When you are creating a planning version for a supply chain model, the system creates a copy specific to the planning version for each resource that you have
assigned to the model. If you want to change the planning data for the resource subsequently, you have to adjust these changes in each planning-version-specific
copy of the resource where necessary. (See Planning-Version-Dependent and Planning-Version-Independent Master Data.)

Integration
You can copy work centers from SAP R/3 to SAP APO by means of the SAP APO Core Interface (CIF). The capacities of a work center in SAP R/3 are
mapped to resources in SAP APO.
For more information, see Integration of Resources.
You can create a where-used list for resources. For more information, see Where-Used List for Master Data.

!--a11y-->

1.4.1 Resource Types


Definition
The resource type determines how the system plans the resource. There are several planning parameters for each resource type.
The following resource types are automatically created when transferring work centers from the R/3 system:
Single-Activity and Multiactivity Resource
Single-Mixed and Multimixed Resources
Line Resource (only through transfer of iPPE structures)
You can only manually create the following resource types in SAP APO.
Bucket Resource
Vehicle Resource
Transportation Resource

Integration
In the Customizing of the R/3 system, you can define which resource types are created when transferring work centers to SAP APO. In the R/3 system, choose
Integration with Other mySAP.com Components Advanced Planning and Optimization Application-Specific Settings and Enhancements Settings for
Resources Set the Transfer of Resources to SAP APO .

!--a11y-->

Single Activity and Multiactivity Resource


PUBLIC
2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 56 of 120

Definition
Only one activity can be carried out at a time in a single-activity resource.
Several activities can be carried out at once in a multiactivity resource.

Use
You can carry out to-the-second planning for both resource types in Production Planning and Detailed Scheduling (PP/DS) and Capable-to-Match
Planning (CTM) to determine exact production dates. You can also define planning parameters that allow you to carry out a
the CTP process and in block planning.

bucket-oriented capacity check in

Structure
Time-Continuous Capacity and PP/DS Bucket Capacity
Single and multiactivity resources have the following capacity categories:
Time-Continuous Capacity
The system can plan orders to the second using the time-continuous capacity. The system determines the available capacity of the time-continuous capacity
from the working time data.
PP/DS Bucket Capacity
The system uses the PP/DS bucket capacity to carry out a
bucket-oriented capacity check in the CTP process and in block planning. You can use this
procedure to check the capacity availability for incoming sales orders and reserve the required capacity.
The system determines the available capacity of the PP/DS bucket capacity from the productive time of the time-continuous capacities and the parameters
that you have defined on the PP/DS bucket capacity tab page. If you wish to use block planning with the bucket-oriented capacity check, then you must
define that the system uses the available capacity of the PP/DS bucket from block planning.
Working Time Data
The following working time data must be maintained for single-activity and multiactivity resources. This data is used by the system for scheduling activities:
Detailed working and break times
Rate of resource utilization
The rate of resource utilization is used to estimate the average periods when the resource is unavailable (due to technical and organizational failures) during
working times. The rate of resource utilization is defined as the percentage relationship between the productive time and the working time that remains once the
breaks have been subtracted.
The productive time of the resource is relevant for scheduling activities. It is calculated using the following working time data:
Productive time = (work end work start break duration) x rate of resource utilization / 100%
Productive time is the time that is actually available for carrying out an activity during working time. You should define the activity duration in the production
process model (PPM) for cases in which the resource is available without interruption and with 100% rate of resource utilization. During scheduling, the system
determines the actual duration of the activity. This is dependent on the productive time for the resource.
Capacity of Single-Activity Resources
A single-activity resource upon which only one activity can be executed at a time has a dimension-free capacity of one . For single-activity resources the
capacity value is fixed in the system. A single-activity resource can only have two different situations: Either it is loaded with an activity or it is not loaded at all. As
a result, only the working time data, in other words the time capacity is relevant for scheduling activities on such a resource.
Capacity of Multiactivity Resources
Multiactivity resources are used to map resources on which several activities can be carried out at a time. The maximum number of activities that can be
scheduled at the same time depends on the organizational or technical conditions for the resource. In order to model the multiple loading on the resource, you
define a multiactivity resource in addition to the working time data (time capacity), a capacity that reflects the technical and organizational requirements on the
resource:
If the multiactivity resource is, for example, a turnery with five lathes, you can schedule up to five parallel turning activities on the resource. The turnery has a
dimension-free capacity of five .
Another example of a multiactivity resource is a saw that can cut a slab/block up to three meters long into pieces. This block can also be formed from a
combination of several individual blocks of different lengths. These individual blocks can also come from different orders. You can schedule as many activities on
this resource at the same time as long as the total length of the individual blocks does not exceed three meters. The saw has the capacity three meters .
Each activity that is executed on the multiactivity resource consumes a certain proportion of this capacity. You can only schedule as many activities at the same
time as the available capacity allows for.
You define the resource consumption of an activity in the PPM. The resource consumption is the proportion of the multiactivity resource capacity that the activity
consumes.
Capacity Variants
Within a resource you can define various capacity variants with different working time data and capacities and select the variant of the resource to be used for
planning. See Capacity Variants for more information.

!--a11y-->

PUBLIC
2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 57 of 120

Single-Mixed and Multimixed Resources


Definition
You can use mixed resources for Production Planning and Detailed Scheduling (PP/DS), Capable-to-Match (CTM), and Supply Network Planning (SNP).
Single mixed resources correspond to single-activity resources in PP/DS, and multimixed resources correspond to multiactivity resources.

Structure
Mixed resources also have a SNP bucket capacity in addition to time-continuous and PP/DS bucket capacity .
You can derive the SNP bucket capacities of mixed resources from the time-continuous capacity or define these separately. You define the parameters for this on
the SNP bucket capacity tab page.
When the system calculates the SNP bucket capacity from the time-continuous capacity, the system proceeds as follows:
A bucket capacity with the dimension time is determined for a single mixed resource and this is calculated by multiplying the working time by the loss
factor.
In this case, you cannot assign a dimension or unit of measure to the time-continuous capacity of a multimixed resource. The SNP bucket capacity is
calculated from the time-continuous capacity with the dimension time according to the following formula:
(Resource working time) x (time-continuous capacity) x (loss factor).
You use the loss factor to balance out the fact that neither sequence-dependent setup activities nor relationships are taken into consideration in SNP.

If the SNP bucket capacity is determined from the time-continuous capacity, you cannot define any costs. If you define the SNP bucket capacity
directly, you can define costs in the capacity variant using the definition of the quantity or rate.

!--a11y-->

1.4.1.3 Bucket Resources


Definition
Resource in Supply Network Planning, which has a quantity-oriented capacity that you can plan on a daily basis (periods or "buckets").
You can define the capacity of bucket resources as a
Quantity (without reference to a period of time)
For example, you can use a quantity to define the transport capacity of a truck or the storage capacity of a warehouse.
Rate (quantity with reference to a period of time)
You use a rate to describe the consumption or production capacity of a resource, for instance the quantity that is consumed or produced by a resource in a
workday.
The bucket resource is identical to the transportation resource For more details on using this resource, please refer to the documentation APO Supply Network
Planning .

Structure
Capacity Variants
Within a resource you can define various capacity variants with different capacities and select the variant of the resource to be used for planning. See Capacity
Variants for more information.
Planning Parameters
You can define planning parameters in a resource in addition to those for working time data and capacity. These are taken into account when operations and
orders are scheduled for the resource. For more information, see SNP Bucket Capacity .

!--a11y-->

Resource with Storage Characteristics (Container Resource)


Definition
A container resource is a multi resource or multi-mixed resource with storage characteristics.

PUBLIC
2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 58 of 120

The container resource is not characterized by a separate resource type. Instead, it is a resource with additional storage characteristics (container
resource).

Use
A container resource is used in production for intermediate storage of different products. It may, however, only contain one product at a defined time. Several
activities may fill or empty products. From the point of view of planning, the container is a resource that is occupied for a certain period of time with a defined
product quantity. Along with production capacity, the container resource also has storage capacity.
The container characteristics are defined using the fill level description. The fill level is characterized by the minimum production quantity , the maximum stock
level and the remaining quantity allowed .

A container resource has a time dimension and a capacity dimension. The capacity dimension is not the fill level. Their units and values allow you
to distinguish between them.

Example
The following examples show the storage and assignments of container resources that are used in different ways.

Example 1
A container resource is first used for production, and then the product is filled from the resource at different times or all at once. The container must always be
completely emptied before it is used again.

Example 2
A container resource is used for intermediate storage. The product is filled into or emptied from the container resource at different times. The container must not be
completely emptied before being filled with another product.

Structure
The container resource is defined as follows:

Storage Characteristic Indicator


The Storage characteristic indicator is set for a multi-activity or multi-mixed resource on the General Data tab in resource maintenance. If you set the indicator,
then you can assign the following fill level descriptions to the resource.

Maximum stock level


The maximum stock level defines the maximum quantity of the product that can be stored in the container.

Minimum production quantity


The minimum production quantity defines the minimum quantity of the product that must be stored in a container. The minimum production quantity is only used
if the container resource is used for production.

You want to carry out a reaction in a container resource. For a complete conversion, the products used must be stirred. In order for the mixer blade

PUBLIC
2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 59 of 120

to be located within the product mixture, the container must be filled with the minimum production quantity .

Remaining quantity allowed


The remaining quantity allowed defines the maximum quantity of a product that can be stored in the container when a product is to be filled.

You want to display a container, which always has to be completely emptied before a new product can be filled in it again. In this case, you must
set the remaining quantity allowed to zero.

Integration
Fill Level
The material quantity in the container resource can be visually represented in the DS planning board. To do this, the profile of the DS planning board must be
adjusted accordingly.

Alerts
Violations to the storage characteristics of container resources can be displayed in the Alert Monitor . This is only possible if the Alert Monitor profile is defined
accordingly.
The following alerts can be displayed:
Stock < 0
The quantity of the product in the container resource is below zero.
Minimum Production Quantity Not Reached
The quantity of a product that was filled into the container is not enough. This alert is only triggered if the stock level is below the minimum production quantity
after the product has been filled into the container resource. No alert is triggered when the product is removed, even if the stock level in the container is below the
minimum production quantity .
Maximum Quantity Exceeded
The stock level in the resource is above the quantity defined as the maximum stock level .
Filling Violates Remaining Quantity Allowed
A product receipt takes place, even though the stock in the container exceeds the remaining quantity allowed.
Invalid Mixing
Different products were filled into a container resource.
The following graphic shows all of the alerts that can be displayed for a container resource.

Product Flow
The product flow is assigned in the production process model (PPM). The product flow describes whether a product is removed from or filled into a container
resource using an activity, as well as the time this occurs. The product flow is an additional dimension of a container resource.

!--a11y-->

PUBLIC
2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 60 of 120

1.4.1.4.1 Storage Characteristics


Definition
Storage characteristics can be assigned to a container resource (resource with storage characteristics). They can be assigned to multi-activity and multi-mixed
resources .

Use
Storage characteristics are maintained on the Storage characteristics tab on the Change Resources: Header Data - Model-Independent screen. The tab is only
available for multi-activity and multi-mixed resources if the Storage character . indicator has been set on the General Data tab.
You can choose from the following data:
Storage Characteristics

Use to define...

Storage dimension

Dimension of the storage capacity of the container resource

Stock level unit

Unit of measurement for the stock in a container

Minimum production quantity

Minimum quantity that must be filled for production at a container resource

Maximum stock level

Maximum quantity that can be contained in a container resource

Remaining quantity allowed

Quantity above which no further product may be added to the container

!--a11y-->

1.4.1.4.2 Creating a Container Resource


Prerequisites
You are on the screen for maintaining a multi-activity or multi-mixed resource .
resource.

You have already entered the general data and standard capacity for the

Procedure
1. On the General Data tab, choose the Storage Character. indicator. The system automatically branches to the Storage characteristics tab.

The characteristics of a resource may be dependent on the planning version. For resources with storage characteristics, you must set the Storage character.
indicator for both the model and all the associated versions. In the definition of the product flow in the PPM, container resources into which the product is filled
or from which the product is removed are assigned. A PPM is not version specific.
2. Enter the storage dimension and stock unit .
3. Define the fill level descriptions, such as the minimum production quantity , maximum stock level , and the remaining quantity allowed .
The maximum stock level is the maximum quantity of the product that can be stored in the container.
The minimum production quantity is the minimum quantity of the product that must be stored in a container.
The remaining quantity allowed is the quantity of a product up to which a further product can be added to the container.

You want to display a container, which always has to be emptied completely before products can be filled in it again. You do this by setting the remaining
quantity allowed to zero.
4. Save your entries.

!--a11y-->

1.4.1.5 Line Resource


Definition
Resource type that is especially designed for

takt-based scheduling, such as in model mix planning. The line resource determines the working times and the

rates of the line. A line resource is generated in SAP APO for each line you create in the DI system using the

iPPE line design.

Use
PUBLIC
2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 61 of 120

In SAP APO, you define an available capacity and the rates for the line resource.
The line resource determines the operating time capacity of the line.
The line resource determines the base rate and the production rates of the line for takt-based scheduling. For production rates, you can enter rates with different
validity periods in one rate model. You then assign the rate model to one or more line resources in a capacity variant.
In the line resource, you can also choose whether you want to connect the base rate for takt-based scheduling (rate-independent takt time).
If you want to produce specific materials with different rates, you can create product-dependent rates.
This data is the basis for production planning in SAP APO. See also: Defining Line Resource Data Relevant for Scheduling
Integration
When iPPE data is transferred from a DI system into SAP APO, the line resource is automatically generated from the line node. SAP APO adopts the name
you specified in the basic data for the line in the Line Resource field, as well as the plant that you also specified in the basic data.
In SAP APO, you complete the line resource with data that is relevant to planning, such as the shift sequence, the production rates, or the product-dependent
rates.
SAP APO generates an order activity with a start date/time and end date/time for each line resource on which an order is scheduled.

!--a11y-->

Calendar Resource and Calendar Mixed Resource


Definition
Resource whose capacity is not utilized during scheduling. The system only takes the calendar of the resource into consideration during scheduling.
In contrast to single resources, the following constraints exist for calendar resources and calendar mixed resources:
Since there is no capacity load for the calendar resource, it is not displayed in the

Detailed Scheduling planning board.

The capacity of a calendar resource is not taken into consideration during scheduling of activities, so it cannot be scheduled
You cannot define a capacity profile for a calendar resource.

finitely.

You can also specify downtimes for calendar resources.


No

setup time adjustment can be executed on a calendar resource.

Use
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 receipt processing time. If you use
another resource type, the system has to take the capacity into account when scheduling these activities, which may lead to performance problems.

!--a11y-->

1.4.1.7 Transportation Resource


Definition
Resource used in Supply Network Planning that is identical to the bucket resource. It has its own resource type in SAP liveCache.

Use
The transportation resource is used in the same way as the bucket resource. It differs from the bucket resource in the scheduling of requirements on the resource.
For more details on the use of this resource, refer to the documentation APO Supply Network Planning .

!--a11y-->

1.4.1.8 Vehicle Resource


Definition
Resource that is used in the Transportation Planning/Vehicle Scheduling (TP/VS) component.

PUBLIC
2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 62 of 120

Use
You use vehicle resources as planning objects in TP/ VS. Vehicle resources map the capacity and availability of vehicles that you want to use for transportation.

You cannot define the available capacity for this resource type dependent on time.
However, you can define a time-dependent availability using shift sequences.
You can choose up to eight dimensions and units of measurement to describe the capacity ( Weight and Volume are predefined by default). Only
if these correspond to the dimensions and units of measurement that you have defined in a

split rule can the optimizer take into account the

vehicle capacity. For more information, see


Dimensions and Units of Measurement.
If you want to check the capacity using the dimensions, set the Finite Planning indicator.
In manual planning, you can overload the capacity of a resource.

Integration
To be able to define vehicle resources, you must have defined means of transport and transportation modes. The following figure represents the relationship
between vehicle resources, means of transport, and transportation modes.

The vehicle resource is a concrete means of transport, for example, the ship Santa Maria. Means of transport are classes of vehicle resources, for example
container ship or cargo ship. You assign a means of transport to each vehicle resource. The transportation mode specifies how the goods are transported, for
example, as a sea shipment. You assign transportation modes to means of transport.

You define modes of transportation in Customizing. They must agree with the modes of transport that you have defined in the ERP system.

Schedule Vehicles
In TP/VS you can plan with schedule vehicles, in other words, vehicle resources with a schedule. To do this, you must set the Schedule indicator for the
means of transport that you want to assign to the vehicle resource. You can then assign this vehicle resource to a schedule. For more information about schedules,
see Definition of Schedules.

Only if you have assigned a means of transport suitable for schedules to a vehicle resource after creating a shipment, can this vehicle resource
also be used for other shipments for the duration of the transportation.
The optimizer does not take into account as a constraint opening times at the locations that the schedule vehicle visits.

Your Own Vehicle Resources


You define your own vehicle resources using the means of transport by specifying that it is your own means of transport. You then assign this means of transport
to your vehicle resource You can assign your own vehicle resource to a depot location.

!--a11y-->

1.4.2 Creating and Changing Resources


Use
You have the following options for creating and changing resources in SAP APO:
You can transfer the work centers that you created in the R/3 system to SAP APO using the APO Core Interface . The system creates a separate resource
for each capacity type of the work center (such as employee or machine) during the transfer to SAP APO. See also: Integration of Resources

PUBLIC
2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 63 of 120

After the transfer, you check the data adopted in the resources. If you are not managing the capacity data in the R/3 system and are working with multiple
shifts, you must manually maintain the data necessary to determine the available capacity in SAP APO (such as breaks and shifts). See also: Defining
Data for Multiple-Shift Operations
You can manage all capacity data in the R/3 system. You transfer the work centers to SAP APO. SAP APO uses external capacity when planning the
capacity data from the R/3 system.
You cannot create certain resource types in the R/3 system. You must create and change these resources manually in SAP APO

Prerequisites
You have defined a factory calendar containing workdays and non-workdays in Customizing for Master Data .
If you want to use the functions
resources, or

Determine Setup Time for Sequence-Dependent Setup Activities or

Optimize Setup Times and Setup Costs for single

Synchronize Activities on Multiresources, you must have defined setup matrixes that you assign to the resources.

Features
Logging Resource Changes
Planning-relevant changes to a resource are recorded in the planning log. In the planning log, the system lists all resources whose changes affect the liveCache
(such as changes in available capacity or changes in the planning indicator). Both the resources themselves and changed orders are logged.
1. From the SAP Easy Access screen, choose Advanced Planning and Optimization Reporting Logs Display Logs.
2. Choose Resource as the application.
3. Choose Execute .
4. You get an overview of all resources that have been changed by the specified user.
If orders are also affected by the changes, this is shown in a separate line.

You can also invoke the log from the initial screen for resource mainentance via Tools Planning Log .

!--a11y-->

1.4.2.1 Integration of Resources


Use
You can use the SAP APO Core Interface (SAP APO CIF) to transfer work centers from the R/3 system to SAP APO. In SAP APO, the system creates
resources for each capacity category of the work center (such as employee or machine).

Prerequisites
You can only transfer capacities that are assigned to a work center (or, for the process industry, to a resource) in SAP R/3. The Basic Data , Scheduling ,
and Capacity views must be defined in the master data of the work center and the work center must be contained in an active integration model.
You have checked the IMG activity for transferring resources. You can find this IMG activity in the R/3 Implementation Guide under Integration With Other
mySAP.com Components Advanced Planning and Optimization Application-Specific Settings and Enhancements Settings for Resources
Set the Transfer of Resources to SAP APO.

Features
SAP APO CIF creates a resource in SAP APO for each capacity. In SAP R/3, you can define parameters (such as the resource category ), which are not
available in SAP R/3 but which are required in SAP APO. You can also include them in the first capacity transfer. However, this is only possible when using a
Plug-In from 2003.1 in combination with SCM 4.0 or higher.

When the data is transferred, SAP APO CIF creates the resources in the database in SAP APO immediately (synchronously) but at a later point
in time in SAP liveCache (asynchronously). If a large number of resources are transferred at the same time, a resource might be displayed in
SAP APO that is not yet available for planning (for the creation of orders) because it does not yet exist in SAP liveCache .

The system transfers the following parameters unchanged:


Short text
In SAP APO, you can create texts in different languages. If a short text is not defined in SAP R/3, the system enters the name of the work center and
capacity category here (for example, AP1_001).
The active version from SAP R/3 is adopted as the active capacity variant.
The standard available capacity, determined through start, finish, break duration, rate of utilization, and operating time, or productive time.
If a reference available capacity is defined for a capacity in SAP R/3, the system creates another resource during the transfer and identifies this as the
reference resource.

The following parameters are converted into parameters specific to SAP APO:

PUBLIC
2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 64 of 120

The resource name is regenerated from the following data:


For a pool or reference capacity, the name of the capacity; or for an individual capacity W and the name of the work center (W stands for work
center).
The associated plant in SAP R/3.
The capacity category.
SAP R/3 source system with client number.

The personnel pool capacity POOL1 (capacity category 002) and the machine capacity (capacity category 001) of work center AP1 in plant
WERK1 in the SAP R/3 system xxxCLNTxxx are created in SAP APO as the resources POOL1_WERK1_003@xxxCLNTxxx and
WAP1_WERK1_001@xxxCLNTxxx.
As location, the location is used that corresponds to the plant in SAP R/3 (for example, plant 0001 in SAP R/3 corresponds to SAP APO location
PL0001@xxxCLNTxxx).
You can define the resource type that is assigned when transferring the resource in the IMG activity Set the Transfer of Resources to SAP APO in the R/3
system. You can choose between the following resource types:

Single-activity or multiactivity resources

Single mixed or multimixed resources

Line resources

Calendar resources or calendar mixed resources

You cannot create bucket, vehicle, and transportation resources in SAP APO through a transfer.
As standard, a pool capacity with several individual capacities, or one capacity that can be used by several operations , is mapped to a multiactivity
resource. Individual capacities without this indicator are mapped to single-activity resources. You cannot change the resource category in SAP APO.
If the capacity in SAP R/3 is relevant to finite scheduling , the resource is
finite in SAP APO, meaning that it can only be scheduled up to 100% utilization.
Information about which factory calendar is valid for the resource is taken from SAP R/3. You have to create the factory calendar manually in SAP APO or
by using a Customizing transport.

Creating and transferring APO resource data in R/3


You can create APO resource data directly in the R/3 work center and then transfer the work center.
You can use the APO Resource function key in the header data of the work center capacity. If you choose this function key, the system calls the following tab
pages for the APO resource.
General Data
Planning Parameters
Standard Capacity
Here, you can directly specify the resource type and resource category with which the capacity of the work center is created in SAP APO. You can also define
the capacity and planning parameters for the

time-continuous capacity, the

PP/DS bucket capacity, and the

SNP bucket capacity.

The following parameters are not transferred:

Intervals
Versions
Hierarchies
Definitions (shifts, break patterns, shift sequences)

You can choose if you want to manage the relevant data for determining the available capacity for each resource in SAP R/3 or in SAP APO. If
you want SAP APO to determine the resource capacity from SAP R/3, use the
external capacity for this resource.
Scheduling formulas are only taken into account during the transfer of a production process model (PPM) to determine the duration of activities.
The capacity category is also only taken into account when the PPM and PDS is generated. Capacity relevant to scheduling is assigned to the modes of the
associated activities as a primary resource. All other capacities are assigned as secondary resources.

Change Transfer
The system automatically transfer the CIF changes to the header data of the resources. In the IMG activity Define Settings for Resources in the R/3 system, you
define the resource copies for which the CIF changes are effective in SAP APO. You can choose between the following:
Planning-version-independent resource
Planning-version-independent copy of the resource, and the copy of the resource assigned to planning version 000
Planning-version-independent copy of the resource, and all copies of the resource assigned to a planning version of model 000

!--a11y-->

Tab Pages in Resource Maintenance

General Data
Time-Continuous Capacity
PP/DS Bucket Capacity
SNP Bucket Capacity
External Capacity
Downtimes
Block Planning

PUBLIC
2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 65 of 120

!--a11y-->

1.4.2.2.1 General Data


Use
On the General Data tab page, you can check and define the following parameters:
Basic Data
Capacity
Planning Parameters

Features
Basic Data

Resource category
Time zone
Location
Planner

Capacity
Parameter

Meaning

Resource Types

Factory calendar

Calendar that determines the work days

All resource types

Active variant

Available capacity for planning

All resource types

Reference resource

The reference resource determines the available capacity if All resource types
you are not working with the active variant or the external
capacity.

Planning Parameters
Planning Parameters

Meaning

Resource Types

Days -/ Days +

Relative validity period (in days) of the resource

All resource types

Sort string

String that can be used to sort the resources.

All resource types with the exception of vehicle resources

Bottleneck resource

Finite scheduling

All resource types with the exception of vehicle and


calendar resources
For resources with finite scheduling, the system takes the All resource types with the exception of calendar resources
capacity of the resource into consideration.

Finiteness level

If a resource can be scheduled by several applications,


Single, multi and line resources (with the relevant mixed
which, however, should not all schedule finitely or all
types)
infinitely, you can use the finiteness level and the strategy
settings for each application to control if scheduling should
be finite or infinite.

Storage characteristic

Defines a container resource

Only multiresources

!--a11y-->

Validity Period for Available Capacity


Definition
Defines the period of time for which the available capacity of a resource is generated in SAP liveCache.

Use
PUBLIC
2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 66 of 120

You specify the validity period of a resource in the master data on the General Data tab page in the Days +/ Days fields. The specified number of days lie
before and after the date on which the resource was saved in the SAP liveCache . Depending on the resource type, the system generates a continuous available
capacity or SNP bucket capacity.

For performance reasons, you should only generate the available capacity for the time period for which you want to schedule the resource.

Integration
In the following cases, the system automatically updates the available capacity of a resource in SAP liveCache:
When you create the resource
When you change and save planning-relevant master data for the resource
When you manually save the resource using the liveCache check function on the initial screen for resource master data.
If the available capacity is not updated for a long time, the capacity available for scheduling in the future reduces as time progresses; the system does not
automatically delete the capacity in the past. Using the report /SAPAPO/CRES_CAPACITY_LENGTHEN, you can update the available capacity of resources
relative to the time at which the report is executed, without having to save them again.

We recommend that you schedule this report periodically as a background job.


For more information, see the report documentation.

!--a11y-->

1.4.2.2.2 Time-Continuous Capacity


Use
You define the standard available capacity and the planning parameters for the time-continuous capacity on this tab page. This available capacity is valid for
an unlimited period. If you are not working in multiple-shift operations, and want to plan shifts, then you can define the data for the standard available capacity on
this tab page.
You can define data for the time-continuous capacity for the following resource types

Single-Activity and Multimixed Resources


Multi-Activity and Multimixed Resources
Line Resources
Vehicle Resources
Calendar Resources

Integration
If you want to transfer work centers from the R/3 system to SAP APO, the APO system can adopt the standard available capacity from the R/3 system:
If you have already maintained APO data for the header data of the scheduling-relevant capacity of the work center, the system adopts the standard available
capacity that you specified.
If you have not maintained any APO data, then the system adopts the available capacity of the scheduling-relevant capacity type of the work center.

Features
Capacity
You must maintain the following data to define the standard available capacity of the time-continuous capacity:

Start and end of daily working time


Break duration
Rate of resource utilization
For multiresources, you enter the capacity and the associated dimension, such as the number of individual capacities. Single resources always have the
dimension-free capacity 1.
In the case of line resources, you also specify the rates for takt-based scheduling.

Planning Parameters
The following parameters are provided for planning on time-continuous capacity (dependent on resource type):
Planning Parameters

Meaning

Setup Matrix

Setup matrix that the system uses to determine the setup


time and setup costs of sequence-dependent setup
activities on the resource.

Resource Types

Single resources
Line Resource

The setup matrix must be assigned to both the planningversion-independent and the planning-version-dependent

PUBLIC
2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 67 of 120

resource.
Synchronization Start

The system can synchronize the start dates/times of


activities with the same duration and classification.

Time buffer

Time interval in which the components have to be staged


at the resource before the planned operation begins.

Single resources
Multiresources

Maximum overlap

Maximum time (in seconds) by which 2 activities


processed at the resource may overlap, before the system
interprets the overlap as a capacity overload and generates
an alert if necessary.

Single resources
Multiresources
Line Resource

Campaign-relevant

Specifies if the resource can be used for planning

Single resources
Multiresources

production campaigns.

Multiresources

Activities
Calculating the Productive Time
The system determines the productive time in hours from the parameters that you defined for the available capacity according to the following formula:
Productive time = (Working time in hours Break duration) x Rate of Capacity Utilization
If you have only defined these data, then the productive time corresponds to the standard available capacity of the resource.
Displaying the Available Capacity of the Time-Continuous Capacity
You can display the available capacity of the time-continuous capacity by choosing the Capacity function key. The system creates a list that displays the
available capacity in hours for each day. In the Standard column, you can see if the standard available capacity is used for planning (marked with the indicator
X).
If you have defined an active capacity variant, the system evaluates the shift sequence and calculates the available capacity.
If you have specified a reference resource, the system calculates the available capacity of the resource from the reference resource data.
See also: Determining the Valid Capacity

!--a11y-->

PP/DS Bucket Capacity


Use
You define the parameters for the PP/DS bucket capacity on this tab page. You use the PP/DS bucket capacity to carry out a
bucket-oriented capacity check
in the CTP process and in block planning. You use the bucket-oriented capacity check when the available capacity for resources becomes critical.

Integration
You can also maintain the parameters for the PP/DS bucket capacity in the R/3 system for the APO data of the scheduling-relevant capacity for the work center.
You then transfer the work center to the SAP APO system using the APO Core Interface .

Prerequisites
You can only create the parameters for the PP/DS bucket capacity for the following resource types:
Single-Activity Resource
Single-Mixed Resources
Multi-activity resource (no dimensions)
Multimixed Resources (no dimensions)
You have set the Finite Planning indicator on the General Data tab page.
You have define the parameters for the time-continuous capacity.

Features
You create PP/DS buckets by defining the parameters for the PP/DS bucket capacity on the PP/DS Bucket Cap. tab page for the resource and then saving
your entries.
Bucket Definition

PUBLIC
2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 68 of 120

For the CTP check, choose the setting From Time-Continuous Capacity in the Bucket Definition field. The system derives the available capacity of the PP/DS
bucket from the available capacity of the time-continuous capacity of the resource.
For block planning, choose the setting From Block Planning in the Bucket Definition field. The system derives the available capacity of the PP/DS bucket from
the available capacity of the blocks. As long as you have not defined any blocks, the system will continue to derive the available capacity from the timecontinuous available capacity.
Bucket Schema
You can define the size and start time of a PP/DS bucket in the Bucket Schema field. The scope of a bucket is determined by the period that you define. If, for
example, you define the bucket scheme Day, then the available capacity of a bucket is one day. If, for example, you define Week, then the available bucket
capacity is one week. The individual buckets always have the same duration.
If you require user-defined periods, then you can change the predefined periods using BAdI /SAPAPO/CRESBUCKET.

For example, enter the period Day in resource maintenance. The duration of the bucket is then one day. You can use the BAdI to change the
predefined bucket by combining two days for a bucket, for example.
A suitable bucket size depends on the following factors:
Average order size
The bucket duration should be long enough for an operation of a large planned order to be produced within a bucket. Alternatively, you can define settings for
the maximum lot size in the product master that allow all operations to be produced within a bucket.
Required information quality
The quality of information is inversely proportional to the bucket size. This means that the quality of information becomes worse when the bucket duration
increases. For example, the quality of information is very bad if a sales order with a processing duration of one day is contained in a bucket with a duration of
one year.
Bucket Factor in %
The bucket fact is used to determine the relationship between the available capacity of the time-continuous capacity and the bucket capacity.
The bucket factor is used to determine the capacity reduction for the bucket capacity requirement of the sequence-dependent setup activity.
Finite Capacity
The Finite Capacity field determines if the bucket or the time-continuous capacity of a resource is scheduled finitely. The settings for the finite capacity in the
strategy profile override the settings for the resource.

Activities
The system calculates the available capacity of a PP/DS bucket based on the parameters you defined for the PP/DS bucket capacity according to the
following formulas:
Bucket capacity of single-activity resource = Productive time of resource x Bucket factor
Bucket capacity of multiactivity resource = Productive time of resource x Number of capacities x Bucket factor
You can display the available bucket capacity by choosing the Bucket Capacity function key. The system creates a list that displays the available capacity
for each bucket in hours.
You can check the PPM/PDS for the resource by choosing the Check Plans function key. The resource must be used as a primary resource in the
PPM/PDS and the Calendar Resource indicator must be set. After the PPM/PDS check has been carried out, the system outputs a list of plans in which
the resource is used as a secondary resource and/or for which the Calendar Resource indicator is not set.

Example
The maximum time-continuous available capacity for a resource is 22 hours per day. Enter 90% as the bucket factor . You have entered Day (Start: 00:00) as
the bucket schema . The system now calculates the available capacity of the PP/DS bucket according to the following formula:
Time-continuous available capacity per day x Bucket factor = 22h X 0.90 = 19.8 h
The available capacity of a PP/DS bucket is 19.8 hours.

!--a11y-->

1.4.2.2.4 SNP Bucket Capacity


Use
You define the capacity data and planning parameters for the bucket resources , vehicle resources , and mixed resources on this tab page. These data form
the basis for planning in Supply Network Planning (SNP).

Features
SNP Available Bucket Capacity
You can determine the available bucket capacity of mixed resources and vehicle resources from the time-continuous capacity , specify a loss factor , or

PUBLIC
2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 69 of 120

determine the capacity using certain parameters. You can only define the available bucket capacity for bucket resources using parameters.
You display the input fields of these capacity parameters by choosing the setting Maintain in the Bucket Definition field.
Dimensions in which the resource is planned (bucket-oriented), such as time.
Period type, such as day
Bucket capacity
Here you enter the number of days in the bucket, for example.
Rate of resource utilization
In the case of transportation resources, you specify the measurements or the volume of the resource.
Planning Parameters
Planning Parameters

Meaning

Overload (in %)

Percentage by which the resource load can exceed the


resource capacity. The system interprets any resource load

Resource Types

above this percentage as a resource overload and


generates an alert if necessary.

Single-Mixed Resources
Multimixed Resources
Bucket Resources
Transportation Resource

Minimum utilization (%)

Percentage by which the capacity load can fall below the


resource capacity.

Single-Mixed Resources
Multimixed Resources
Bucket Resources
Transportation Resource

Planning on grid

Activities must begin at the start of a bucket.

Single-Mixed Resources
Multimixed Resources
Bucket Resources
Transportation Resource

Cross-period
activities

Activities on the resource can start in one bucket (for


example, on one day) and end in another (for example, on
another day).

Single-Mixed Resources
Multimixed Resources
Bucket Resources
Transportation Resource

Cross-period
lot size

SNP optimization executes cross-period lot size planning


on this resource.

Single-Mixed Resources
Bucket Resources

Cross-period
You can display the available capacity of the SNP bucket capacity by choosing the Bucket Capacity function key. The system creates a list that displays
the available capacity for each bucket in hours.
You can display the source of the available capacity using the

function key.

!--a11y-->

1.4.2.2.5 External Capacity


Use
If you use SAP APO with SAP R/3, you can define that SAP APO directly uses the data defined in the external system to calculate the available time-continuous
capacity of single, multi, line, and calendar resources as well as the relevant mixed types.
If you are working with the capacity data from the R/3 system, SAP APO does not take into account any other settings when determining the valid available
capacity that affect the capacity with the exception of downtimes and the deviations defined in the capacity profile.

No capacity is available in downtimes.

Integration
The capacity can only be specified in SAP R/3 without a dimension, so the external capacity of multiresources is also always without a dimension.
In the case of mixed resources, the system generates the SNP bucket share of the capacity from the external capacity, if you specify for the resource that the
bucket capacity is generated from the time-continuous capacity.
You define the usage for the external capacity in the Implementation Guide in the R/3 system under Integration with Other mySAP.com Components
Advanced Planning and Optimization Application-Specific Settings and Enhancements Settings for Resources Set the Transfer of Resources to
SAP APO . In the Use Ext. Capacity field, you can choose from the following options:
The available capacity is usually generated in SAP APO and not in SAP R/3.
The available capacity is generated using the capacity data in the R/3 system for all resources that were transferred from this R/3 system.
The available capacity is generated only for specific resources using the capacity data in the R/3 system.
If you choose this option, you must set the External Capacity indicator for the APO data in the capacity header of the work center. This determines that
system generates the capacity of the work center in the R/3 system.
You also define the time period for which the external capacity is generated in SAP R/3 in this IMG activity.

PUBLIC
2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 70 of 120

Prerequisites
You have defined a capacity for a work center in SAP R/3 and transferred it to SAP APO by means of the SAP APO CIF.

Features
From the data in SAP R/3, an available capacity is generated in the database in SAP APO for each day within the validity period of a resource. The following
data is taken into consideration when the available capacity is generated in SAP R/3:

Header data for the capacity


Reference capacity
Intervals, shift sequences, shift definitions, and break schedules
Factory calendar

The APO Core Interface does not support any change transfers for shifts, shift sequences, and breaks that you change in the R/3 system. SAP APO adjusts
the available capacity of the resource to the data that was changed in the R/3 system. This means the available time is calculated again in SAP APO. SAP APO
automatically schedules all orders that are affected by the changes made to shifts or breaks, for example.

!--a11y-->

1.4.2.2.6 Downtimes
Definition
In the master data, you can define downtimes, in which the resource is not available for finite scheduling, for all resources (except vehicle resources). A distinction
should be made between the following types of downtimes:
Planned downtime
Time in which the resource cannot be used due to maintenance, for example. A planned downtime can be changed, added or deleted in interactive planning,
for instance in the detailed scheduling planning board. If you copy the simulation version into the planning version, the system also adopts the changed
downtimes.
Resource is inactive
Unexpected resource standstill. This downtime cannot be changed in a simulation version.
You define a downtime by specifying a start date/time and end date/time as well as the type. In addition, you can enter a language-dependent short text that
describes the downtime in more detail.

It does not make sense to define downtimes that are outside the validity period of the resource, since a capacity has not been defined for the
resource for these times. Downtimes outside the validity period are not taken into consideration during scheduling.

Integration
Activities cannot be interrupted by downtimes. This means the activities always come completely before or after a downtime. If you move an activity in the
planning board over a downtime, then the activity jumps behind the downtime.
If you implement the BAdI /SAPAPO/CRESDOWNTIME, you can define that the activities can be interrupted by downtimes. If an activity is moved onto a
downtime, the activity duration is increased by the duration of the downtime. The activity is then continued after the downtime. See also: SAP Note 448601

!--a11y-->

1.4.2.2.6.1 Downtimes for Maintenance Orders


Definition
Time segment in which a resource is not available.
Downtime differs from a regular scheduled non-working time based on the factory calendar or the shift sequence (for example, break or holiday).

Use
Maintenance orders may automatically create a downtime on a production resource in SAP APO.
To automatically create a downtime in SAP APO, the following prerequisites must be met:
In SAP R/3:
The order must contain a functional location or an equipment.
A work center must be entered on the Location tab in the functional location or equipment.

PUBLIC
2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 71 of 120

The System Condition in the order must be set to 0 or another value for which the Reservation indicator is set.
The order and the production resource must be contained in an active integration model.
In SAP APO, the downtime on the production resource is created from the start time to the end time of the maintenance order. However, you can change the
downtimes by implementing Business Add-In (BAdI) /SAPAPO/MNT_INBOUND , method CHANGE_DOWNTIMES . This method provides the default
downtimes from the start time to the end time of the orders, which you can then change.

For example, you can create downtimes per activity (see the sample implementation of the BAdI). You can also create downtimes only for certain
activities or not create downtimes for certain orders under certain conditions.
SAP APO does not create downtimes with zero duration.
When a downtime is created on a resource, SAP APO removes the activities that lie on that resource at the time for which the downtime is created from the
downtime.
You can use the

delta report to check the consistency of downtimes between SAP R/3 and SAP APO; downtimes are subobjects of maintenance orders.

Downtimes are stored on the SAP APO database, and correspond to an order that is stored in the live Cache. You can check and correct the consistency of
downtime data between the SAP APO database and the live Cache. To carry out the check, on the SAP Easy Access screen, choose Advanced Planning
and Optimization APO Administration liveCache/LCA Routines Consistency Checks liveCache Consistency Check (transaction code
/SAPAPO/OM17).
When displaying a maintenance order in the Process Order transaction (transaction code /SAPAPO/RRP2), you choose Downtimes to display the downtimes.
If the order does not have downtimes, an information message appears. If the order does have downtimes, the corresponding downtimes are listed in a dialog box.
By clicking on the resource, you navigate to the Resource display.
To find and display downtimes, you can use report /SAPAPO/MNT_DOWNTIMES_FIND . This report displays the resources, the start and end times of the
downtime, the downtime type, the order number (for downtime type 3), and some internal GUIDs. You can navigate to the display of the resource order by clicking
on the resource or the order number.
For more information about maintenance orders, see

Maintenance Orders in SAP APO.

!--a11y-->

Define Data for Multiple-Shift Operations


Purpose
If you are working with multiple-shift operations, plan shifts, and not manage these data using the external capacity in the R/3 system, then you can define one or
more capacity variants. You use capacity variants to define the available capacity based on different shift programs in SAP APO.

Process Flow
1. You create the required definitions for the resource that works in the multiple-shift operation.
a. If the resource does not work during breaks, then define the break times using the break pattern.
b. You can also define shift factors. A shift factor is the rate of capacity utilization for a specific shift; the rate of capacity utilization during the night shift is
lower than during the early shift.
c. You define the shifts and specify the start and end dates of the shifts including the break pattern and shift factors.
d. You define the shift sequence and assign the shifts, such as early and late shift, or early, late and night shift. You also specify how the shifts are
distributed weekly.
2. You define a capacity variant by defining a validity period.
3. You assign a time interval and a shift sequence to the capacity variant. This defines the available capacity of the capacity variant.
4. You enter the capacity variant in the Act. Variant field on the General Data tab page. The variant of the available capacity that you created is now valid.

!--a11y-->

Defining Capacity Variants


Use
If you work in a multiple-shift operation and want to plan using shifts, you can use capacity variants to define different available capacities for one or more
resources. See also: Define Data for Multiple-Shift Operations

Features
In the initial screen for the resources, you can define up to 99 capacity variants by choosing Current Settings Capacity Variants . Depending on where, as
standard, the system determines the resource capacity, the capacity variant is defined in different ways:
For resources with a standard available capacity, you can define intervals for these capacity variants, in which the valid available capacity is defined using
definitions. To define the intervals, go to the Change Resources screen and select the Capacity Variants pushbutton. You use different definitions,
depending on the capacity category of a resource:
You can define shift sequences with shifts, breaks, and shift factors for resources with time-continuous capacity (such as single and multiresources).
In the case of resources with SNP bucket capacity (such as mixed resources and bucket resources), you use quantity/rate definitions
You can also define define rate models for line resources.

PUBLIC
2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 72 of 120

You cannot define any intervals for resources with an external capacity that is determined directly from SAP R/3. The capacity variant is identical to the
available capacity determined from the external capacity, as long as you have not manually defined variances in the capacity profile.
If you define a capacity variant as the active variant in the General Data of a resource, the system uses the capacity variant instead of the standard
available capacity or the external capacity.
You can choose the Capacity Profile pushbutton to gain an overview of the available capacity that is determined from the active capacity variant for the validity
period of the resource, and to manually enter variances for individual data. (See Capacity Profile.)
For more information, see Determining the Valid Capacity.

For optimization in Supply Network Planning , you define capacity variants using minimum, normal and maximum capacity.

!--a11y-->

1.4.2.3.1.1 Definitions
Definition
Resource- and date-independent templates for defining the available capacities of the capacity variants of a resource.

Use
You use definitions to specify capacities in capacity variants for resources. You specify a valid to date for each definition . The definitions, their use and data are
summarized in the following table.

You can use the where-used list for definitions to check whether a definition is used in resources.
Definitions for Single-Activity and Single Mixed Resources or Multiactivity and Multimixed Resources
Definition

Use

Data

Shift sequence

In the shift sequence, you define the daily shifts for any
number of consecutive days (for example, for a week),
with working and break times, utilization rate and capacity
(in the case of multiactivity resources) for each shift.
You assign shift sequences to the time intervals of a

Day numbers
Zero to nine shifts per day
Processing of shifts that start or end on non-workdays
Planner group

Shift
Start/end of the shift
Break pattern
Shift factors
Planner group

capacity variant. In each interval, the shift sequence is


repeated periodically (every seven days, for example). You
also specify on which day of a shift sequence an interval
should start.
Shift

You define shift data in a shift definition.

Breaks

In a break pattern, you define the breaks for a shift.

Break pattern
Break number
Start and end of the breaks
or
Relative start of the break, in relation to the start of the
shift, and the total break duration
Planner group

Shift factors

Defining a shift factor means defining the rate of resource


utilization and capacity of a shift.

Shift factor definition


Validity
Rate of resource utilization
Capacity (multiactivity resources or multimixed

resources)
Planner group

Definitions for Bucket Resources (Quantity/Rate)


Quantity/rate definition

You define the capacity (quantity or the daily rate) of the


resource.

PUBLIC
2014 SAP SE or an SAP affiliate company. All rights reserved.

Validity
Capacity in two different units of measurement
Period reference (none or day)
Number of days
Planner group

Page 73 of 120

Costs

Definitions for Line Resources (Rate Model, Product-Dependent Rates)


Rate model

Production rate of the resource for different validity periods

Validity
Planner group
Units of time
Units of measure
Language-dependent short texts

Product-dependent rates

If you produce products with different rates, you define


product-dependent rates for specific line resources.

Validity
Planner group
Factor
Language-dependent short texts

Planning Version-Specific Definitions


You can create definitions that are dependent on or independent of planning versions. Definitions that are independent of planning versions are available for all
planning versions until a change that is specific to a planning version is made in the definition. This then counts as an object in its own right and is no longer
affected by changes in the associated planning version-independent definition.
Consequently, changes to a definition that is independent of planning versions immediately affect all planning versions that use this definition and do not already
contain this definition as a separate object.
For more information, see Planning-Version Dependent and Planning-Version-Independent Master Data.

Example
The following graphics are examples of how you can define the capacity of capacity variants for a resource using definitions .
Definition of Capacity Variants for Single-Activity and Multiactivity Resources or Single Mixed and Multimixed Resources

Definition of Capacity Variants for Bucket Resources

PUBLIC
2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 74 of 120

!--a11y-->

1.4.2.3.1.1.1 Creating Capacity Variants


Use
This section describes how you can combine capacity-relevant data such as different shifts and breaks in a capacity variant.

Prerequisites
You have created a resource.

Procedure
1. You are currently in the master data for the required resource (change mode). Choose Definitions. The Create/Change Definitions screen appears.
2. Choose the Breaks tab page.
3. Create the new break pattern (for example, lunch) and assign a break number (dependent on how many breaks you wish to define for the day).
There are two ways to define breaks:
You specify the start and end of the break.
You specify the number of hours after which a break should take place, and enter the duration of the break. The reference point is always the beginning of
the shift. However, this break is not a recurring break. If you want to define a break for resource 2 every 2 hours, you must define a break for 2 hours, 4
hours, 6 hours, and so on after shift begin (taking into account the duration of any previous breaks).
4. Choose the Shifts tab page.
5. Enter a description for the shift, a validity end, and a start and end for the shift. Assign your break pattern to this shift.

The system does not take account of any shift factors for vehicle resources.
6. Choose the Shift Sequences tab page.
7. Enter a description, the day number, and the validity end. In the Non-Workdays field, you can choose from the following options to define the start and end of
the shift:
Can Finish on a Non-Workday
Can Start on a Non-Workday
Can Only Start or Finish on a Workday
Can Start or Finish on a Non-Workday
8. Assign one or more shifts to the shift sequence. Save your entries.
9. Go back to the resource master data and choose Capacity Variants . To create a new variant, choose Interval .
10. Enter a number and a validity period. Assign the shift sequence to the capacity variant. Select the first day so that the first day of the time interval is the first
day of the shift sequence.

You have defined a four-day shift sequence. If you enter 2 as the first day, the first day of the time interval has the shifts from the second day of the
shift sequence.
There are three ways of defining workdays:

PUBLIC
2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 75 of 120

Workdays according to the factory calendar


No workdays (overwrites the factory calendar)
Workdays (overwrites the factory calendar)
11. Save the interval and go back to the resource master data.
12. On the General Data tab page, assign the capacity variant to the resource.
13. Save the resource and assign it to the required model.

!--a11y-->

Create and Change Resources Manually in SAP APO


Procedure
1. Select the tab for the resource type for which you wish to create a new resource. You cannot change the resource type later:
Single-Activity or Multiactivity Resource
Single Mixed or Multimixed Resource
Line Resource
Bucket Resource
Transportation Resource
Vehicle Resource
Calendar Resource and Calendar Mixed Resource
2. Enter the general data for the resource:
You have to define resource name, resource category, location or time zone, and factory calendar. In the case of multiresources, you also specify the capacity
(with dimension), and for bucket, vehicle and transportation resources, you specify the dimension. In addition, you can specify the relevant scheduler.

You can only create a resource independently of a model. As soon as you assign the resource to a model, the system automatically creates a
copy of the resource for each of the planning versions that belong to this model. If you create another planning version for this model later, the
system also automatically creates a copy that is specific to the planning version.
You can only process the original and the planning-version-dependent copy independently of each other (for example, change planning data,
delete resource).
3. Define the parameters for the time-continuous capacity if you want to use the resources in PP/DS.
4. Define the parameters for the SNP bucket capacity if you want to use the resources in SNP.
5. In addition, you can:
Define downtimes
Define language-dependent short texts
Define blocks for

block planning in Characteristics-Dependent Planning (CDP)

!--a11y-->

1.4.2.5 Copying Resources


Prerequisites
You must already have created a resource which is then to be copied.

Procedure
Start from the screen Change Resources: Header Data Independent of Model . Select the resource(s) that you want to copy.
Choose Copy resource .
In the Copy Resources dialog box, you can create one or more copies of a resource.
Single copy:
the data in the Copy individual resource From field group represents the template for the copy in the To field group. Here, you maintain the name of the copy,
its location, and a short description.
Replicate all selected resources
: enter the number with which the copied resources are to begin, and the number of resources that are to be created. This number will be added to the end of
the resource name as a counter value.
If you have selected more than one resource in the Change Resources: Header Data Model-Independent screen, the selected resources are called up
consecutively as a template in the Copy Resources screen.
Assume that the name of the template is Res_00. If you choose 1 as the start number and 10 as the number of resources, the list of existing
resources is extended to include the resources Res_001 to Res_0010.
4. Confirm the entries using Enter.

PUBLIC
2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 76 of 120

Result
You have created a copy of one or more resources. Each copy has its own name.
!--a11y-->

1.4.2.6 Deleting Resources


Prerequisites
You can only delete resources that do not exist in any model and are no longer used in a production process model. For that reason, check for existing
dependencies using the Where-Used List pushbutton and remove them before you delete the resources.

Procedure
Start from the screen Change Resources: Header Data Independent of Model . Select the resource to be deleted.
Choose Delete resource .
If there are no dependencies, the resource is deleted
If the resource has dependencies, the Where-Used List screen appears, in which there is a tab for each type of use. The different uses of the resource are
listed on these tab pages. You must remove all of these dependencies before you can delete the resource.
3. Choose Save in the screen Change Resources: Header Data Independent of Model to confirm deletion.

You delete planning-version-dependent copies of resources by removing them from the associated model.

!--a11y-->

Determining the Valid Available Capacity


Purpose
You can define different categories of capacity for a resource:
External capacity
Standard available capacity of the time-continuous capacity and the SNP bucket capacity
To call up an overview of the standard available capacity generated from the time-continuous capacity and SNP bucket capacity of a resource, choose the
relevant pushbuttons on the Time-continuous Capacity and SNP Bucket Capacity tab page.
Capacity variant
Capacity profile
By choosing the Capacity Profile pushbutton, you can call up an overview of the standard available capacity, the available capacity generated from the
capacity variants or the capacity defined externally.
Reference resource
To determine the capacity that is available at a specific point in time at a resource for scheduling, the system takes these different capacity categories into
consideration in a hierarchical sequence.

No capacity is available in downtimes.


This process describes how the system determines the valid capacity.

Process Flow
The system checks the resource at the current point in time in the following sequence. If the result of the check is negative, the system moves on to the next step:
1. If a downtime is defined for the resource for the current point in time, no capacity is available.
2. If it is specified in the resource that the capacity is determined in an external system,
a. And an active variant is also specified at the resource for which a capacity profile with different data exists, the system uses the data defined in this
capacity profile
b. And different data exists for the external capacity in a capacity profile for the current point in time, the system takes this variance into account
c. And no active variant is specified and no capacity profile is defined, the system uses the external capacity.
3. If an active capacity variant is specified in the resource, and different data is defined in a capacity profile for the current date, the system uses the
capacity defined in the capacity profile.
4. If an active capacity variant, for which a capacity profile does not exist, is specified in the resource,
a. And an interval with a capacity that is valid at the current time is defined in this variant, the system uses this capacity
b. And no interval is found with a capacity that is valid for the current time, the system checks if a reference resource is assigned to the resource
i. If the same (not necessarily active) capacity variant with a valid interval exists for the reference resource, the system uses the capacity of the
capacity variant for the reference resource.
ii. If a valid interval does not exist in the same capacity variant at the reference resource either, the system uses the standard capacity of the

PUBLIC
2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 77 of 120

reference resource.
5. If you have also created a capacity profile for the standard available capacity, the system uses the capacity defined in the capacity profile.
6. If a reference resource is specified at the resource, the system uses the standard capacity of the reference resource.

The capacity profile of the reference resource, should it exist, is ignored. If, on the other hand, another reference resource is specified at the
reference resource, the system determines the capacity as described here.
7. The system only uses the standard available capacity if it was not able to determine a valid resource capacity for the current point in time during one of
the previous checks.
8. If no standard available capacity is defined at the resource, the resource does not have any capacity.

Determination of the Valid Capacity for a Specific Time

!--a11y-->

1.4.3.1 Invoking the Capacity Profile


Use
The capacity profile is a list containing the manually adjusted capacity data of the standard available capacity or a capacity variant of the resource.

Features
The capacity profile provides you with an overview of the available capacity of a resource per day from the current date to the end of the validity period for the
following capacities:
Standard available capacity
Capacity variants
External capacity
Depending on the resource type, the overview shows the available time-continuous capacity (time capacity) or bucket-oriented capacity (quantity capacity).

Depending on the validity period defined for the resource and the number of shifts, the overview may contain a large number of entries.
You can manually change the available capacity for selected resources if, for example, the working time or the rate of resource utilization vary for individual days,
without having to define a new shift or a new interval in the capacity variant. The system saves these changes to the database in a capacity profile for the

PUBLIC
2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 78 of 120

standard available capacity, the selected capacity variant or for the external capacity.
If you change the basic available capacity by changing the shift, for example, the system adjusts all unchanged data in the capacity profile. All variances
entered manually are retained.
As soon as a capacity profile for the standard capacity, the capacity variant, or the external capacity exists in the database, the system takes the variances
defined there into consideration - instead of the corresponding capacity - when determining the valid capacity.

Activity
1. If you want to change the available capacity of a shift, choose Change Shift in the capacity profile .
A dialog box appears, in which you can specify the period and shift for which you want to change the available capacity.

You can also mark the period on the calendar. The system then automatically marks the corresponding shifts in the overview. The marked period
is also shown in the dialog box.
2. Enter the changed capacity in the Available Capacity area and confirm your input.
3. To save your changes, choose Back

and then save

on the Change Resource s screen.

!--a11y-->

1.4.3.2 Standard capacity


Definition
Available capacity that determines the basic resource availability.

Use
The standard available capacity of a resource has unlimited validity and is always the same. If you are not working with different shift sequences, then the
standard available capacity is sufficient for planning.

Structure
You define the parameters for the standard available capacity for resources (single, multi, line, vehicle, and calendar resources) you planned with PP/DS on
the time-continuous capacity tab page. Choose the Available Capacity pushbutton on this tab page to display the standard available capacity of the
resource for the entire validity period as a list.
You define the parameters for the standard available capacity on the SNP bucket capacity for resources to be planned with SNP. Choose the Available
Bucket Capacity pushbutton on this tab page to display the standard available capacity of the resource for the entire validity period as a list.

!--a11y-->

1.4.3.3 Reference Resource


Definition
Resource that you use to define the available capacity of other resources.

Use
You can use reference resources to create and change available capacities for several resources.
For example, in a resource, you can define the normal capacity of all resources in the plant or in a sector of the plant. You then specify this as a reference
resource in the individual resources and thus transfer the available capacity of the reference resource to these resources.
For the individual resources, you only define the exceptions to the normal available capacity, by defining an active
capacity variant for the time intervals in which another available capacity should be valid.
For more information, see
Determining the Valid Capacity
!--a11y-->

Production Process Model, Production Data Structure and iPPE

PUBLIC
2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 79 of 120

Definition
Structures containing production version information from SAP R/3 and SAP DIMP.

Use
The production process model (PPM) and the production data structure (PDS) are used as sources of supply for in-house production in SAP APO.
For more information, see:
Production Process Model
Production Data Structure (PDS)

Integrated Product and Process Engineering (iPPE)

You can create a where-used list for production process models and production data structures. For more information, see Where-Used List for Master Data.

!--a11y-->

1.5.1 Production Process Model


Definition
Source of supply for procuring a product produced in-house.

Use
Using a source of supply for in-house production, the planning applications in SAP APO can create a planned order within procurement planning that stages this
product. You can create a production process model (PPM) in SAP APO
By manually creating the PPM in SAP APO
By transferring relevant data from an OLTP system to SAP APO and then entering SAP APO specific planning data in the PPM, if required

A PPM corresponds to a production version in SAP R/3. You can transfer a SAP R/3 production version to SAP APO as a production process
model.

Structure
A PPM is based on the PPM plan. The PPM plan describes which process steps and components are required to manufacture the output products from the plan
on a non-order-specific basis. You define a PPM for each output product of a PPM plan. In the PPM, you define the validity conditions for the usage of the PPM
plan. The system may only use a PPM (and thus also the PPM plan) for a planned order if the order data fulfills the following conditions:
Lot Size Margin
The procurement quantity for the primary product of the planned order must be in the lot-size interval that you have defined in the PPM of the product.
Time Validity
The availability date/time of the planned order must be in the PPMs validity period. For the PPM, the system automatically uses the validity period that you
have entered in the plan for the output product.
Planning Location
The location in which you create the planned order must be entered in the PPM as planning location . A PPM is therefore always only valid for a specific
location. The system creates the receipt for the primary product in the planning location.
If you have entered a production location in the PPM that differs from the planning location, the system creates the dependent requirements for the
components and the receipts for the co-products in the production location. The production location is relevant for

production in another location.

In the case of planning with storage location MRP areas, the production location in the planned order may differ from the issuing location of the
components. The system automatically determines the issuing location from the storage location and the production location.
The resources used in the plan determine the locations in which the capacity requirements arise. The capacity requirements may therefore be
in different locations.
Procurement Priority
You can define several PPMs for an output product. You use the procurement priority to define the priority the system uses when taking a PPM into consideration
during

source determination.

!--a11y-->

1.5.1.1 PPM Plan

PUBLIC
2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 80 of 120

Describes the production process for manufacturing one or more products on a non-order-specific basis. A PPM plan consists of BOM and routing data from SAP
R/3.

Use
The following applications can use PPM plans:

Production Planning and Detailed Scheduling (PP/DS)


A PPM plan for PP/DS (PP/DS PPM) contains to-the-second information about the duration of the individual process steps. You can use resources here that
have a time-continuous capacity (single and multiresources). If you use mixed resources, which have both a time-continuous capacity and a bucket
capacity, you can enter a bucket consumption at the same time. You can generate a PPM plan for SNP (SNP PPM) from the PPM plan for PP/DS. (See
Generation of SNP PPMs from PP/DS PPMs.)

Supply Network Planning (SNP)


In a PPM plan for SNP (SNP PPM), you can only specify the duration of the activities in buckets. You can only assign one mode to each activity.

Demand Planning (DP)

A PPM plan for DP (DP PPM) corresponds to a BOM in SAP R/3 and does not contain any information on resources. (See
Forecast Using BOMs .)
You can use a template PPM (plan usage T) for the method CreateFromTemplate of the Business Application Programming Interface (BAPI)
ManufactOrderAPS. For more information, see the documentation for this BAPI.

Structure
In operations and related activities, you define the production flow in the PPM plan and assign the required components and resources. You define activity
relationships between the activities.
Possible Structure of a PPM Plan

Header Data
In the header data of the PPM plan, you define the costs incurred during production on the basis of this plan.
Single-level costs only contain the costs for the production steps defined in this plan.
Multilevel costs contain the costs incurred for staging the required components.
For

source determination in PP/DS, the system only takes the multilevel costs into consideration.

Operations
At the operation, you define which setup status is required for this operation on the primary resource. If the PPM plan has been created during the master data
transfer through the SAP APO Core Interface from SAP R/3, the operation also contains the following information:
Operation type (PP operation, PI operation, PI phase, or PP/PI suboperation)
The higher-level operation from SAP R/3

In SAP APO, an individual operation with one activity is created for each phase of a master recipe from SAP R/3 PP-PI. The activities of all
phases of a PP-PI operation have an end-start relationship.
Activities

PUBLIC
2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 81 of 120

For each activity, you define:


The activity type; for example, if it is a setup activity or a processing activity

In Customizing for Master Data you can define your own activity types under Production Process Model Maintain Activity Types .
The scrap as a percentage (if any results from the activity), if it is an activity with the type Produce or Maintain You can define scrap as time-dependent
and planning-version-dependent.
If a setup activity has a sequence-dependent duration
If activities on multiresources can be

synchronized

If the activity start and activity end are to lie within the
validity period of the order
Which products are consumed or manufactured by the activity
At each activity, you define which logical components are required or produced. Under the logical component , you specify the real input or output product,
which is defined in the system as product, as the alternative component . You can assign several alternative components, which can be distinguished by
their time validity or the material consumption. For each alternative component , you can also define the material consumption as time-dependent and
planning-version-dependent parameters.

In an activity, a finished product is manufactured from a raw mixture. The following components are used:
Logical component

Input/output indicator

Alternative components

Raw mixture

Input

ROH_01 (6/1/2003 12/31/2003)


ROH_02 (1/1/2004 5/31/2004)

Finished product

Output

FERT_01

The resources on which the activity is executed (modes)


You group together resources that are needed simultaneously for the activity in a mode, and assign this mode to the activity. You define a primary resource for
each mode and specify the required duration and the capacity consumption (in the case of multiresources). You can also define the duration for each mode
dependent on time and on planning version.
If you can use different resources for this activity, you define an individual mode for each possible combination. The system can then automatically switch to
an alternative mode (during optimization, for example), if a mode is not available. You use the
mode priority to define the sequence in which the modes
should be taken into consideration during planning.
You define the capacity consumption for each resource used (except for single resources that always have the capacity 1); you can also define them as
dependent on time and dependent on planning version.
The product flow
Activity Relationships
You define activity relationships (time relationships) between the activities, and specify the following:
The reference type of the activities; for example, if they start simultaneously ( start-start relationship ) or if the second activity begins as soon as the first is
completed ( end-start relationship ), and if the time buffers defined at the resource should be taken into consideration
Minimum or maximum intervals
Mode linkage ; in other words, if, for the following activity, only the mode with the same name as the previous mode, or with the same primary resource can be
selected
Continuous occupation of the resource between the activities (locked activity chain)
Further processing of the material which is processed in the first activity in the second activity ( material flow )
The material flow is relevant for calculating the activity scrap and the input quantity required in each case. If a material flow is defined at the activity
relationship, the system calculates the scrap of the linked activities cumulatively; otherwise, it does so for each activity individually.
Characteristic Propagation
If you use characteristics, you can define characteristic value assignments in the PPM plan. Activate the characteristic propagation under Plan
Characteristic Propagation Use .

Integration
You define the usage conditions (for example, validity period and lot-size interval) for a plan in the production process model.

!--a11y-->

1.5.1.1.1 Product Flow


Definition
You use the product flow to specify at an activity of the PPM plan that a product will be removed from or filled into a resource with storage characteristics
(container resource) during production.

The product flow should not be confused with the material flow . This is an attribute of the activity relationship and defines if the scrap of
activities, which are linked by the activity relationship, is calculated as cumulated or individually for each activity.

PUBLIC
2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 82 of 120

Structure
In the PPM plan, you assign the product flow to the activity that is on the container resource that is used for filling or removing products. You can define one or
more product flows for an activity, but you can only assign each logical component to one activity per PPM plan. If you want to assign the same logical component
several times, you have to use different PPM plans.
The product flow is characterized as follows:
The product flow ID, which you use to define if the product is removed or filled at the start or end of the activity or continuously
The logical component of the activity that is removed or filled.
The container resource into which the product is filled or from which it is removed

To assign a product flow to an activity, choose Product Flow .

Integration
You can define the product flow in SAP APO or in SAP R/3.
In SAP R/3 , you assign the product flow to operations or phases on the Material Component Assignment screen in the master recipe . The data is assigned to
the activity of each PPM plan during the transfer via the SAP APO Core Interface .

Example
A logical component (raw mixture) should be filled in a container, then processed further in two different ways, and removed from the container for this. Since three
activities with the same logical component have to be assigned a product flow, three different PPM plans have to be used. A PPM plan is defined for each of the
segments Fill , Remove for Further Processing A and Remove for Further Processing B . A product flow with the same logical component (for example, raw
mixture), but with a different product flow ID, is assigned to each activity of the PPM plan.

!--a11y-->

Production Process Model Plans for CDP and Block Planning


Use
You can display the BOM and routing of the R/3 system in production process model plans in SAP APO.

In Characteristics-Dependent Planning (CDP), components are all elements or parts of a PPM plan, for which you can define characteristics
propagation. Activities are also regarded as components.
If you are working with PPM plans, you use the characteristic propagation to define at which characteristics the values are copied from the configuration.
The object dependency in the ERP system at BOMs and routings is not transferred to the PPM plan. Therefore, you should not use an object dependency at
APO-relevant components or operations. If you wish to carry out preliminary costing, you must create a separate costing BOM/routing.

PUBLIC
2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 83 of 120

When transferring PPM plans for product variants, the object dependency is evaluated. Only the required components/operations are integrated in
SAP APO. In each case, you should check if processing with CDP is required.
If you delete or replace components in BOMs or operations in the routings in the ERP system and transfer these changes to SAP APO, dependent CDP data are
also deleted with the corresponding nodes in the PPM plan. The same applies to changed key dates in validities in BOMs and routings. In these cases, you must
subsequently maintain the CDP data in SAP APO. If you make frequent changes to the BOM or routing in the ERP system, you can also use production data
structures (PDS) instead of PPM plans.

Prerequisites
You have specified that you want to work with PPM in SAP APO when creating an integration model in the ERP system (plug-in).
The same prerequisites as described in Planning with CDP Characteristics are valid for characteristics-dependent planning.
The same prerequisites as described in Block Planning are valid for block planning.

Features
Define Characteristics Propagation
The class assignments for components and activities are displayed on the overview screen for characteristics propagation.
You define which characteristics are used for CDP for the output product. For logical components and the activities, you specify characteristics whose values are
copied from the configuration by the system.
You can define valuations and characteristic requirements for characteristic propagation:
For characteristics selected under Valuation , the system copies the values from the configuration and uses them for pegging or for creating orders.
For characteristics selected under Characteristic Requirements , you can define selection criteria that the system uses for pegging. The characteristics must
be defined as batch selection characteristics in a class of class type 023 in the ERP system (see Define Characteristic Requirements). If characteristic
requirements have been defined, the system will not consider any entries made under Valuations during pegging. The receipt requirements must be
compatible with the requirements valuation.
Define Rules
You use rules to control the selection of operations, activities, modes, and logical components that are required for the planned production step. These form the
actual items of the production order that was created by the PPM (without access to the live Cache).
In the PPM plan, rules replace the object dependency that is required in the PPM plan.
The system takes the rules into account during the plan explosion.
Overwrite Planning Parameters
You can overwrite certain planning parameters for operations, modes, activities and logical components. To do so, you must define the value and class
assignments of the next highest PPM level.
You can overwrite the following parameters:
PPM Level

Planning Parameters

Operation

Sequencing

Activity

Duration (must be entered in seconds for immediate transfer to the live Cache)
Scrap

Mode

Duration

Primary Resource (multi-activity resource)

Consumption of resources (capacity requirements)

Product

Material consumption for the respective product (component requirements)

!--a11y-->

1.5.1.2 Creating Production Process Models


Use
You can manually create a production process model in SAP APO.

Prerequisites
You have defined a PPM plan
You are in plan processing in the Change Plan Individual Display screen

Procedure
1. Choose
Product Plan Assignment.
The system shows the screen area Production Process Models . If you have not yet assigned any PPMs to the PPM plan, the table in the Production

PUBLIC
2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 84 of 120

Process Models area contains a row with the name of the output product, the associated logical component, and the validity period of the output product for
each output product of the plan. The validity period of a PPM is the same as the validity period of the output product.
2. Create a PPM for each output product.
Enter the required data for each output product. Do not use any special characters for the name and the description of the PPM.
3. Save your entries.
4. If you want to define an additional PPM for an output product, place the cursor on the PPM that you have already created for this product and choose
Copy .
The system creates a new row containing the data of the PPM you have copied. Modify this data as required by entering a different name and a different
planning location, for example.

Several PPMs for one output product of the plan are relevant for
production in another location and for planning with MRP areas. In these
applications, there may be several PPMs with different planning locations for an output product.

Result
You have created a PPM for each output product of the PPM plan. You have to assign a PPM to the supply chain model so that it is available in the model for
planning.

!--a11y-->

1.5.1.3 Generating SNP PPMs from PP/DS PPMs


Use
SAP APO allows you to generate SNP production process models (PPMs) based on existing PP/DS PPMs. For instance, this may be a good idea if you are
using both Production Planning and Detailed Scheduling (PP/DS) and Supply Network Planning and after the SNP planning want to convert SNP orders into
PP/DS orders. During order conversion, the system is then able to automatically determine the correct PP/DS PPM mode combination that is appropriate for the
SNP order. The following is a list of the generation options available:
SNP PPM generation with lot size margin:
You use this generation function to generate SNP PPMs from PP/DS PPMs for lot size margins and several
mode combinations of a PP/DS PPM. The system creates an SNP PPM per PP/DS PPM mode combination. For more information, see SNP PPM generation
with lot size margin.
As the number of mode combinations and therefore also the number of SNP PPMs will possibly become very large depending on the number of activities and
alternative PP/DS PPM modes, you can choose specific PP/DS PPM mode combinations for the SNP PPM before the function is run or enter specific
parameters to restrict the SNP PPMs generated. For more information, see
specifying mode combinations for SNP PPM generation.
SNP PPM generation without lot size margin:
You use this generation function to generate SNP PPMs from PP/DS PPMs for one individual lot size and exactly one PP/DS PPM mode combination.
Each generation report run can generate exactly one SNP PPM corresponding to one specific PP/DS PPM mode combination. For more information, see
SNP PPM generation without lot size margin.
For example, you can use this function when SNP PPM generation with lot size margins is not possible.
!--a11y-->

1.5.1.3.1 SNP PPM Generation With Lot Size Margin


Use
You use the SNP PPM Generation With Lot Size Margin function to generate SNP production process models (PPMs) from PP/DS PPMs for lot size margins
and multiple
mode combinations of a PP/DS PPM. Due to the fact that PP/DS PPMs can have multiple modes defined per activity whereas SNP PPMs can only have one
mode per activity, the system generates one SNP PPM per PP/DS PPM mode combination.

Integration
It is possible that the number of mode combinations and therefore also the number of SNP PPMs generated will become very large, depending on the number of
activities and alternative PP/DS PPM modes. For this reason, there is a different function available that you use before running this function to select certain
PP/DS PPM mode combinations or enter parameters in order to restrict the number of SNP PPMs generated. You then flag the chosen PPM plans so that they
are considered the next time this function is executed. For more information, see
Specifying Mode Combinations for SNP PPM Generation.
You can also run the function described here directly without first defining the mode combinations. Parameters are available on the selection screen for this
function, which you use to restrict the number of SNP PPMs generated. However, manual preselection of mode combinations is only possible in the function
mentioned above.

Prerequisites
PUBLIC
2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 85 of 120

In the system, you have created the appropriate PP/DS PPMs from which you want to generate the SNP PPMs. For more information, see the
PPM Plan section of the APO master data document.

During generation, the system only takes into account multi mixed resources or single mixed resources that have not been set with the indicator Not
SNP Rel. on the Planning Parameters tab page from resource master data. Also, the system only takes into account products with the activated
SDP relevance indicator on the Properties tab page within product master data.

Activities
You maintain the control parameters for executing the function. From the SAP APO Easy Access menu, choose Master Data Production Process Model
SNP PPM Generation With Lot Size Margin .

On the selection screen, if you leave the PP/DS plan number and SNP plan number fields blank, the flagged PPM plans and associated control
parameters are adopted from the transaction SNP PPM Generation: Determine Mode Combinations . On the selection screen, if you specify a
specific PP/DS plan number and SNP plan number, you must also enter the associated control parameters on the screen. If you do not enter any
values, the system uses the maximum values possible.
For example, you use the control parameters to specify how the operations, activities, and resource consumption from the PP/DS PPM are transferred to
the SNP PPM that has been setup for bucket-oriented SNP planning. You can also restrict the number of SNP PPMs generated by limiting the PP/DS
PPM mode combinations considered.
The following control parameters are available:
Parameter

Use

Start Date of Generation Period

You use this date to specify when bucket generation for the SNP PPM plan is
to start. The
temporary PP/DS order created by the system, from which the SNP plan is to
be generated, is also scheduled from this start date on.
If possible, you should choose the start date so that the PPM generation horizon
corresponds to a typical horizon for your work processes (based on leave
periods, public holidays, and so on).
For generation, it is not possible to shift the start date into the past.

Bucket Size

You use bucket size (period length) to specify which PP/DS plan activities are
to become an SNP plan activity during SNP plan generation. To do this, a
temporary PP/DS order over a certain lot size (typical order lot size, see below)
is created by forward scheduling from the Start Date of the Generation Period
specified. All activities from the planned order that fall within a bucket of the
pre-specified size, then become one production activity in the generated SNP
plan. This means that the longer the bucket is, the more PP/DS plan activities
can be included within one SNP plan activity. This production activity is one
day long. If necessary, the remaining time from the bucket is occupied by a
wait activity.
You should choose the bucket size so that it corresponds to the period length for
SNP planning (that is, the period length specified in the planning buckets
profile).

Lowest Mode Priority

You use lowest mode priority to specify which PP/DS plan modes are to be
considered for the mode combination, that is, how many SNP plans are
generated. Modes with a lower priority than the one specified here are not
considered for SNP plan generation.

Consumption Calculation

You use the consumption calculation parameter to specify how the variables
and fixed bucket resource consumptions from SNP plan activities are to be
calculated, which means how the corresponding PP/DS plan consumptions are
to be transferred to the SNP plan. There are the following two types of
calculation:
1. Consumption is calculated on a one to one basis, so that one PP/DS
order corresponds to one SNP order (generation variant without PP/DS
campaign):
The system uses the fixed duration and fixed resource consumption from
the PP/DS plan plus the duration of sequence-dependent setup
activities to calculate the fixed bucket consumption of the SNP plan. The
duration of these activities is calculated as the setup duration of an initial
setup group/setup key (as specified in the setup matrix) to the setup
group/setup key of the operation considered. Variable bucket
consumption is determined from the PP/DS plan variable duration and
variable resource consumption.
2. Consumption is calculated on a many to one basis, so that n PP/DS
orders correspond to one SNP order (generation variant with PP/DS
campaign):
The system calculates fixed bucket consumption from the duration of
sequence-dependent setup activities only (see above). The fixed PP/DS
plan durations are made linear and go into the variable bucket
consumptions from the SNP plan. Variable durations and resource
consumptions are also used to determine the variable bucket
consumption.

Typical Order Lot Size

This is the lot size over which the system creates a temporary PP/DS order.

PUBLIC
2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 86 of 120

The system uses the temporary PP/DS order to assign PP/DS PPM operations
to the respective SNP buckets (periods) using normal scheduling rules.
As the order length is usually based on the lot size, you should enter the typical
order lot size in this field. When choosing this lot size, it should correspond to the
typical SNP lead time, because all orders that you create from the generated
SNP PPM receive the duration derived from the temporary PP/DS order.
As a rule, the larger the typical order lot size, the longer the duration of activities
in the generated SNP PPM. Note that if you choose an order lot size that is too
large, the duration of activities may exceed the bucket size, and the system will
not be able to generate an SNP PPM. Because of this, there are several
options available for determining the typical order lot size (see the selection
help).
Maximum Number

You use this parameter to specify an upper limit on the number of SNP plans
to be generated.
If this number is exceeded, the system terminates generation.

2. You run the function.


3. The system generates SNP PPMs from the specified PP/DS PPMs according to the parameters you defined.
4. It is possible to view the results of the function and messages in a log. From the SAP APO Easy Access menu, choose Master Data Production
Process Model SNP PPM Generation: Display Log .
!--a11y-->

1.5.1.3.1.1 Specifying Mode Combinations for SNP PPM


Generation
Use
You use this function before running
SNP PPM Generation with Lot Size Margin to choose certain PP/DS PPM mode combinations for the SNP-PPMs or to enter specific parameters in order to
restrict the number of SNP PPMs generated. Because the automatic generation function generates exactly one SNP PPM per PP/DS PPM mode combination, it
is possible that the number of SNP PPMs generated will become very large, depending on the number of activities and alternative PP/DS PPM modes. After you
have made your selection, you can flag the PPM plans so that they are part of the next run of SNP Generation with Lot Size Margin .
This function can also be used to change the mode combinations and parameters for SNP PPM plans that have already been generated by the SNP PPM
Generation with Lot Size Margin function (for example, you can choose new mode combinations), and then flag the plans for a new generation report run.

Prerequisites
In the system, you have created the appropriate PP/DS PPMs from which you want to generate the SNP PPMs. For more information, see the
PPM Plan section of the APO master data document.

During generation, the system only takes into account multi mixed resources or single mixed resources that have not been set with the indicator Not
SNP Rel. on the planning parameters tab page from resource master data. Also, the system only takes into account products with the activated
SDP relevance indicator on the Properties tab page within product master data.

Procedure
From the SAP APO easy access menu, choose Master Data Production Process Model SNP PPM Generation: Determine Mode Combinations . The
Select Worklist screen appears.
In the upper part of the screen, specify a PP/DS PPM plan or range of PP/DS plans that you want to convert into SNP PPM plans using the SNP
Generation with Lot Size Margin function (you can also choose PP/DS plans by entering one or more products or location products). Alternatively, in the lower
part of the screen, you specify SNP plans that have already been generated with the SNP PPM Generation with Lot Size Margin function, which you want to
change and flag to be run in a new generation report run.
Choose
. The Mode Combinations for Generation of SNP Plans screen appears.
The PPM plans you selected in the selection screen are displayed in the upper table.
You first specify a name in the SNP Plan field. If you give a name without a placeholder, the system provides the appropriate SNP plan number at the end of
this name (such as SNP Plan01 and SNP Plan02) when generating multiple SNP plans for one PP/DS plans (one SNP plan is generated per PP/DS plan mode
combination). However, you can also add the placeholder # at the end of the name or insert it at any point in the name. If you choose this option, the system
replaces the placeholder with the relevant number. You can also leave the field blank and use the
SNP Name button to have the name automatically
generated by the system. It is formed like this: Name of PP/DS Plan_SNP (if required +_Number ) .
In the Generated field, you are shown whether the SNP plan has already been generated from the PP/DS plan manually or automatically (which means with or
without manual mode combination determination) using the SNP PPM Generation with Lot Size Margin function.
In the other fields from the upper table, you specify parameters to control SNP PPM Generation that can be maintained both in this function and in the SNP PPM
Generation with Lot Size Margin function. If you enter values in the corresponding fields in this function, these values overwrite the corresponding entry in the
generation report selection screen, if you leave the report fields PP/DS plan number and SNP plan number blank. For more information on these parameters,
see
SNP PPM Generation with Lot Size Margin or the corresponding F1 help.
If you double click on a PP/DS plan, the operations and activities of this plan are displayed in the lower table. It is now possible to use the selection help to
choose a specific mode for each activity. You can only choose one mode per activity as only one mode is valid per activity in an SNP PPM. When the SNP

PUBLIC
2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 87 of 120

PPM Generation with Lot Size Margin function is run at a later point, exactly one SNP PPM is generated for the PP/DS PPM mode combination chosen.
If you choose just one mode combination, the other parameters for restricting the number of SNP PPMs generated (such as lowest mode priority) are
ignored.
6. You can run checks on the validity of mode combinations and the maximum number of SNP plans generated.
If you choose

, the system checks whether valid mode combinations exist and whether all the mode combinations chosen are valid. Negative check results

(displayed in the table in the form of the


icon and an error message), can be caused by the fact that the mode combinations are now no longer valid due to a
subsequent change to the PP/DS mode combinations or that no valid mode combinations exist because a lowest mode priority has been specified.
If you choose
Maximum Number , a check is made to see whether the number of SNP plans to be generated exceeds the value entered in the Maximum
Number field (the generation report does not terminate if this value is exceeded). If the value is exceeded, you can restrict the number by choosing the lowest
mode priority, for example, or by specifying a specific mode combination.
7. After you have entered the mode combinations, choose Adopt . The system saves your selection and generates a name for the corresponding SNP plan
(for rules, see above). If you choose Cancel , your changes are undone.
8. Set the Flag indicator for the PP/DS plan. If you set the indicator, the PP/DS plan will be taken into account in the next run of the generation report. By
pressing the
Flags button, you can set or delete all flags automatically.
9. Save your entries.

Result
The PPM plans you flagged are taken into account within the next run of the SNP PPM Generation with Lot Size Margin function.
!--a11y-->

1.5.1.3.2 SNP PPM Generation Without Lot Size Margin


Use
This involves generating an SNP production process model (PPM) from an existing PP/DS PPM. Note that this concerns this PPM constellation only. In this
process, all SNP-relevant product and resource consumptions from the existing PP/DS PPM are determined for a lot size and grouped together into SNP
operations and activities. If you wish to generate SNP PPMs from PP/DS PPMs for lot size margins and several
mode combinations of a PP/DS PPM, use the generation report SNP PPM Generation With Lot Size Margin.
To call up the SNP PPM Generation Without Lot Size Margin generation report , choose Master Data Production Process Model SNP PPM Generation
Without Lot Size Margin from the SAP APO Easy Access menu .

Prerequisites
To be able to generate and to use the transaction, you must note the following points:
You have an active PP/DS PPM.
The SNP PPM is generated exclusively for the specified lot size, since no variable durations or consumptions can be taken into account.
In the generation process, only single or multi-mixed resources for which the Not SNP Rel. indicator has not been set on the Planning Parameters tab
page are taken into account. In addition, only those products for which the SDPrelevance indicator has been activated on the Properties tab page of the
product master data are taken into account.
Operations and activities in the SNP PPM do not necessarily match those of the PP/DS PPM from which they were generated. The reason for this is that
activities and operations that are contained in non-relevant resources or components are omitted, or are grouped together with other activities in a time
bucket because of short duration.

Activities
Using the plan or PPM entered and the lot size, an order is dispatched infinitely to liveCache (without taking into account resource schedules that possibly
exist).
Using a time bucket, consumption of the SNP-relevant resources and components can be determined per SNP bucket and grouped together into SNP
operations or SNP activities.

Only the valid components and the mode, which is selected automatically via the order explosion, are relevant for generating the SNP PPM.
Consecutive consumptions of the same type are consolidated into one activity, while bucket durations and material consumptions are added together.
If a new component or resource is added to, or removed from a bucket in an SNP PPM, a new activity is generated in this SNP PPM.
If there is a change of primary resource, the system generates a new operation. If several PP/DS activities with different primary resources lie within an
SNP bucket, the system checks the resources to see whether the dimensions are the same. The primary resource for the SNP mode is then determined
from the PP/DS activity with the highest resource consumption.
Data from the setup matrix is only relevant if the Setup indicator has been set for a setup activity.
Only fixed consumptions and durations can be generated within the SNP plan, because the consumptions arising are determined via a dummy order (fixed
lot size). However, if the SNP PPMs generated are also to be valid for lot size margins, the variable portions must likewise be manually calculated out of the
fixed portions (see also
SNP PPM Generation With Lot Size Margin).
In calculating the bucket consumption, the planned delivery time is also considered. If, for example, a planned delivery time of one day has been specified,
the system generates a wait activity for this time. If a PPM is generated in the past, the days up to the generation date are consolidated to form a wait
activity.
After generation, you must manually maintain the following texts:

PUBLIC
2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 88 of 120

Plan
Product plan assignment
Operation
Activity
This manual maintenance is necessary because the texts cannot be adopted from the PP/DS PPM automatically.

!--a11y-->

1.5.2 Production Data Structure (PDS)


Definition
A structure generated in SAP APO from a production version or bill of material in SAP R/3, or a production version in SAP DIMP. The structure contains
information about the production cycle and the component assignment for the production of a product.

Use
You can use the PDS as well as the PPM as a source of supply for in-house production in SAP APO.

Structure
Production data structures are differentiated as follows:
Source of master data
R/3
Production data structures that are generated from R/3 master data contain data from:
Bill of material
Routing
Master recipe
iPPE
Production data structures that are generated from iPPE master data contain data from:
Product structure
Process structure
Factory layout
By planning application in SAP APO
PP/DS
SNP
CTM
DP

Integration
The production version provides the basis for generating the PDS from both R/3 and iPPE master data.
Exception: Integration model for phantom assemblies
If you are creating integration models for phantom assemblies from R/3 (option Bill of Material ), no production versions must exist for the phantom assembly.
See Create Integration Model for Transferring R/3 Data
PDS from iPPE master data must be generated in APO; the data is then active in SAP APO and can be used for planning. This applies to iPPE master data
that were transferred using the CIF in SAP APO as well as iPPE master data that were created in SAP APO.
PDS from R/3 master data are generated during the transfer to SAP APO via the CIF; the data is then active and can be used for planning.

!--a11y-->

Production Data Structure Generated from iPPE Data


Definition
The production data structure (PDS) contains active master data from Integrated Product and Process Engineering (iPPE) and provides the basis for planning in
SAP APO. The PDS is generated from a production version in SAP APO.

Structure
Production data structures that are generated from iPPE data contain different data depending on the application.

PUBLIC
2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 89 of 120

PP/DS Production Data Structures (PP/DS PDS):


PP/DS PDS for line-oriented manufacturing (RPM and single explosion) contain:
Product structures
Line routings
Line structures
PP/DS PDS for shop-floor-oriented manufacturing contain:
Product structures
Routings
PP/DS PDS for characteristics-based forecasting contain:
Product structures
SNP production data structures (SNP PDS) contain:
Product structures
SNP routings
CTM uses SNP or PP/DS production data structures:
SNP production data structures (SNP PDS) for CTM contain:
Product structures
SNP routings
PP/DS production data structures for CTM contain:
Product structures
Routings

You must set the Use in CTM Planning indicator in the routing header on the Basic Data tab page for Capable-to-Match planning (CTM) to use
the data of a PP/DS PDS.
DP production data structures (DP PDS) are generated from SNP or PP/DS production data structures, or contain iPPE product structures with the usage
Demand Planning (DPB) at the access.
To generate DP production data structures from SNP and PP/DS PDS, you must use the transaction Generate DP Production Data Structures . On the
SAP Easy Access screen, choose Advanced Planning and Optimization Master Data Production Data Structure (PDS) Generate DP
Production Data Structure.
iPPE product structures with the usage Demand Planning (DPB) in the access are generated with the transaction Generate Production Data Structure from
iPPE Data .

!--a11y-->

Generating Production Data Structures (PDS) from iPPE Data


Purpose
So that you can use master data from Integrated Product and Process Engineering (iPPE) for planning in SAP APO, you must generate production data structures
(PDS) from the relevant production versions. This applies to data that are transferred from a DIMP system, and data that was created in SAP APO.
After transferring data from a DIMP system and creating data in iPPE in SAP APO, the data are at first inactive. This means that the data cannot be used
immediately in planning and that possible maintenance errors do not affect planning.
When you have checked the data, you can generate the production data structure, thereby activating the data for planning.

Prerequisites
You have transferred the iPPE data from the DIMP system via the Core Interface in SAP APO, or created iPPE master data in SAP APO and maintained
production versions.
You have checked the data in the DIMP system with the iPPE consistency check.

Process Flow
1. You can check the data using the iPPE consistency check in SAP APO.
See:

iPPE Consistency Check

The system always executes the iPPE consistency check automatically as soon as you have generated a check PDS in an inactive planning
version, and have generated the production data structures for all models.
2. You can use the check production data structure (check PDS) to check data you are using in PP/DS. You also generate a check PDS in an inactive
planning version.
See Checking Master Data in Inactive Planning Versions.
3. You generate the production data structures from production versions for all models.
4. You check the results in the generation log.

Result
The data can now be used in planning.

!--a11y-->

PUBLIC
2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 90 of 120

Checking Master Data in Inactive Planning Versions


Use
You can generate iPPE master data in an inactive SAP APO planning version for PP/DS planning without affecting operational data. You can use the check PDS
function to do so.
You can create orders for the check PDS which check requirements and execute your processes with the new and changed master data. However, you cannot
execute a backflush in an inactive planning version. You can then decide if you want to generate the PDS for all models, thereby providing the data for planning.

Integration

You can generate the check PDS from changed and new master data from production versions.
The current status of the master data is generated as the check PDS in the selected planning version.
The check PDS in the inactive planning version, and the data that you created cannot be transferred from the inactive planning version to the active one.
If the data are correct, and you generate the PDS for all models, then this status applies to all model planning versions that are assigned to the production
version. All previous statuses of the check PDS are inactive; this means you can no longer create any orders.
You cannot execute a backflush in an inactive planning version.
You can check the data for CTM with the check PDS as the application CTM can also use the PP/DS production data structures.
The check PDS cannot be used for SNP and DP data.

Actions
1. Choose Advanced Planning and Optimization Master Data Production Data Structure (PDS) Generate Check Production Data Structure from
iPPE Data.
The screen Generate Check Production Data Structures from iPPE Data appears.
2. Specify the planning version in which you wish to generate the check PDS and choose if
You only want to generate production versions whose master data have changed since the last generation are generated in the inactive planning version
( Generate Changed Production Versions Only ).
Or
You want to generate production data structures whose master data have not changed since the last generation in addition to the PDS that were changed
( Generate Current Production Data Structures Also ). Only use this option after having upgraded.
3. Choose Execute .

!--a11y-->

Generating Production Data Structures (PDS) from iPPE Data for All
Models
Use
You use this procedure to generate production data structures (PDS) for all models. The PDS can be displayed in all planning versions of the models that are
assigned to the production versions. The master data are active and can be used for planning.
The system executes the iPPE consistency check when generating the production data structure. See:

iPPE Consistency Check

Procedure
1. On the SAP Easy Access screen, choose Advanced Planning and Optimization Master Data Production Data Structure (PDS) Generate
Production Data Structure from iPPE Data.
The screen Generate Production Data Structure from iPPE Data appears.
2. Enter the data for the production version from which you wish to generate the production data structure(s) for all models, the usage, and choose if
You only want to generate production versions whose master data have changed since the last generation ( Generate Changed Production Versions
Only ).
Or
You want to generate production data structures whose master data have not changed since the last generation in addition to the PDS that were changed
( Generate Current Production Data Structures Also ). Only use this option after having upgraded.
3. Choose Execute .
The Logs screen appears. Here, the system lists all messages related to the generation.
You can also call up logs related to generating the production data structures separately. On the SAP Easy Access screen, choose Advanced Planning
and Optimization Master Data Production Data Structure Display PDS Generation Log.

!--a11y-->

PUBLIC
2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 91 of 120

Production Data Structure Generated from R/3 Master Data


Definition
A structure generated from a production version or a bill of material in SAP R/3 that contains information about the production cycle and the component assignment
for the production of a product; the production data structure can be used in SAP APO as a source of supply for in-house production. The production data
structure (PDS) is generated when transferring master data from SAP R/3 via the SAP APO Core Interface to SAP APO.

Structure
The production data structure consists of the following:
List of components with the following information:
Consumed total quantity
Type of consumption
Assignment to activities.
List of available capacities with reference to resources
List of activities with data for setup
List of modes with data for duration and assignment to activities
Relationships

Use
You can use the PDS generated from R/3 data, the PDS generated from iPPE data, and the production process model (PPM) as a
house production in
Production Planning and Detailed Scheduling
Demand Planning (DP).

source of supply for in-

(PP/DS), in Supply Network Planning (SNP), in Capable-to-Match Planning (CTM), and

Integration
The production data structure (PDS) is generated during the transfer of master data from the connected SAP R/3 System using the SAP APO Core Interface
in SAP APO. The production data structure can be generated from the following master data in SAP R/3:
Production version with routing and bill of material
Production version based on a master recipe
Bill of material (for phantom assemblies)
In SAP APO, you cannot change the data that are contained in the production data structure. You can display the data. See Display Production Data
Structures
On the SAP Easy Access screen, choose Advanced Planning and Optimization
Master Data Production Data Structures (PDS) Display
Production Data Structures .
If you wish to change the PDS data, you must change the data in SAP R/3 and then generate the production data structure again using the SAP APO CIF.
When transferring via the SAP APO CIF, the production data structure is created in the model 000 and the active planning version 000. On the SAP Easy
Access screen in SAP R/3, choose Logistics Central Functions Supply Chain Planning Interface Core Interface Advanced Planner and
Optimizer Integration Model Change Transfer Production Data Structure (PDS)
Transfer Production Data Structure (PDS) to assign a
different planning version to the production data structure (PDS).

If you are using the production data structure, you can implement the following Business Add-Ins (BAdIs) in SAP APO that can be applied to the
generation and explosion:
/SAPAPO/CURTO_CREATE Enhancement When Creating a PP/DS PDS (R/3) (Generation)
/SAPAPO/CURTO_SNP ) Enhancements When Creating an SNP PDS (R/3) (Generation)
/SAPAPO/CULLRTOSNP ) Change SNP/CTM Production Data Structure Data (Generation)
/SAPAPO/CULLRTOEXPL Enhancements for PP/DS PDS (Explosion)
So that the system uses the PDS generated from R/3 data during planning in PP/DS, SNP, CTM, and DP in SAP APO, you must set plan explosion 5
Production Data Structure Generated from R/3 in the location product master of the product.
For more information, see Integration of PP/DS Production Data Structures.

If you are using Integrated Product and Process Engineering (iPPE) in SAP APO, you must generate the production data structure from iPPE
data in SAP APO. For more information, see Generating Production Data Structures (PDS) from iPPE Data.
See also:
Comparison of PP/DS Production Data Structure

!--a11y-->

Create Integration Model for Transferring R/3 Data


Use
PUBLIC
2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 92 of 120

You create an integration model for R/3 master data (BOM, routing, and master recipe) to transfer data to the SAP APO. During the transfer, the system generates
a production data structure (PDS) that provides the basis for planning in SAP APO. You use the integration model to define what type of PDS is generated in SAP
APO.
You can implement BAdIs that influence the results in SAP APO.

Prerequisites
You have created the master data in SAP R/3 (BOM, routing, master recipe).
You have created a production version in SAP R/3 for each product that you wish to plan in SAP APO.
Do not create a production version if you wish to create an integration model for a phantom assembly (option Bill of Material ).

Create Integration Model for Transferring BOMs, Routing, and Master Recipes
1. On the SAP Easy Access screen in SAP R/3, choose Logistics Central Functions Supply Chain Planning Interface Core Interface Advanced
Planner and Optimizer Integration Model Create .
The Create Integration Model screen appears.
2. At the top of the screen:
Enter a unique name in the Model Name field.
Enter the RFC destination you have defined for SAP APO in the Logical System field.
Enter a description in the APO Application field. This is for information only.
3. Choose the option PDS (R/3) and then
Further Restrictions in the Material-Dependent Objects group box.
4. In the General Selection Options for Materials group box, enter the materials, plant, and additional data for the product that you wish to transfer to SAP APO.
5. Depending on the data you require for planning in SAP APO, enter the following information in the Production Data Structure group box:
PDS Type :
Determines what type of PDS is generated in SAP APO. You can implement BAdIs that can be applied to the generation.
Production Version :
Determines which data is transferred.
Routing Select. :
Determines which routing and master recipe is copied from the production version to the integration model.
The relevant PDS is generated in SAP APO based on the information provided in the Production Data Structure group box.
6. Choose
Execute .
The Create Integration Model screen appears.
7. Save your data.

Create Integration Model for Transferring Phantom Assemblies


1. On the SAP Easy Access screen in SAP R/3, choose Logistics Central Functions Supply Chain Planning Interface Core Interface Advanced
Planner and Optimizer Integration Model Create .
The Create Integration Model screen appears.
2. At the top of the screen:
Enter a unique name in the Model Name field.
Enter the RFC destination you have defined for SAP APO in the Logical System field.
Enter a description in the APO Application field. This is for information only.
3. Choose the option BOM and then
Further Restrictions in the Material-Dependent Objects group box.
4. In the General Selection Options for Materials group box, enter the materials, plant, and additional data for the product that you wish to transfer to SAP APO.
5. Depending on the data you require for planning in SAP APO, enter the following information in the Material BOM group box:
PDS Type :
Determines what type of PDS is generated in SAP APO. You can implement BAdIs that can be applied to the generation.
Usage
Determines which data is transferred.
Alternative :
Determines which routing and master recipe is copied from the production version to the integration model.
The relevant PDS is generated in SAP APO based on the information provided in the Production Data Structure group box.
6. Choose
Execute .
The Create Integration Model screen appears.
7. Save your data.
The following table shows the correlation between the master data in SAP R/3, data in the integration model, and the PDS as result in SAP APO.
Master Data in R/3

Prod. Version Available

PDS Type

Possible Planning
Selection

BadI in SAP APO

Result: PDS in SAP APO

Bill of Material
Routing
Master Recipe

Yes

PP/DS

Detailed Scheduling
Rate-Based Planning

/SAPAPO/ CURTO_
CREATE

PP/DS PDS

Bill of Material

Yes

PP/DS with Subcontracting

Detailed Scheduling

/SAPAPO/ CURTO_

PP/DS PDS in Suppliers /

Rate-Based Planning

CREATE

Subcontractor Locations

Routing
Master Recipe
Bill of Material
Routing
Master Recipe

Yes

SNP

Detailed Scheduling
Rate-Based Planning
Sales and Operations
Planning

/SAPAPO/ CURTO_SNP

SNP PDS

Bill of Material
Routing
Master Recipe

Yes

SNP with Subcontracting

Detailed Scheduling
Rate-Based Planning
Sales and Operations

/SAPAPO/ CURTO_
CREATE

PP/DS PDS in Suppliers /


Subcontractor Locations

PUBLIC
2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 93 of 120

Planning
Bill of Material
Routing
Master Recipe

Yes

PP/DS

Detailed Scheduling
Rate-Based Planning

Bill of Material
(for Phantom Assembly)

No

PP/DS
SNP

No Influence on Generated
PDS

/SAPAPO/ CURTO_
CREATE
Method:
CREATE_CTM_PDS

CTM PDS

PP/DS PDS
Without Routing

If no routing has been specified in the production version, the system:


Generates an activity with the duration of the planned delivery time from the purchasing info record for a PDS with subcontracting in SAP APO.
Generates an activity with the duration of the planned delivery time from the product master for a PDS without subcontracting.

!--a11y-->

Comparison of PP/DS Production Data Structure


Use
You use this function to compare R/3 master data with the PP/DS production data structure (PDS) that is generated from it in SAP APO.
This means that you can check whether R/3 master data has been correctly transferred to SAP APO.
You use this report (/SAPAPO/CURTO_ORDER_EXPLODE) to carry out a simple or more detailed comparison and to retransfer master data:
1. Comparison of the change date
With this simple comparison, you can check whether R/3 master data or changes to it have already been transferred to SAP APO, on the basis of the date of
the last change to the BOM, routing, master recipe and production version.
The comparison only takes into account the date on which this R/3 master data was last changed. The date of the last change in SAP R/3 is compared with
the time at which the PP/DS production data structure was generated in SAP APO.
2. Comparison of the explosion results
You can use this comparison to carry out a more detailed check of the master data on the basis of the explosions results. It is not necessary to have carried
out the first comparison in order to carry out this comparison.
In the comparison, the explosion result of the R/3 manufacturing order (production and process order) is simulated and compared with the simulated explosion
result of the PDS in SAP APO.
Only the operations, phases, input and output products, and activity relationships of the manufacturing orders are compared.
3. Retransfer of the master data
You can carry out an automatic retransfer of the PDS from SAP R/3 to SAP APO for deviating master data in the background.

Prerequisites
System Prerequisites
The following system and releases are required:
SAP SCM 4.1
PI 2004.1

SAP R/3
Required master data
The report compares only data that is relevant in APO (routing, master recipe, production version, work center, components) and fields in the active integration
model.
Therefore, the following steps are necessary:
1. The master data that is necessary for the creation of a production order or a process order must be entered in SAP R/3.
Materials
Production version
Work center or master recipe
BOM
2. You must create and activate an integration model with the master data required for the PDS (materials, plant, work center, production version).
For more information on initial and change transfer of PP/DS production data structures, see Integration of PP/DS Production Data Structures.
Required settings in the material master
Because a temporary order is created in SAP R/3 during the comparison of the explosion results, you must have maintained the production scheduling profile,
production scheduler, or MRP group in the material master ( MRP 1 view, Work Scheduling ). The system uses this information to determine the order type of
the manufacturing order (production or process order). This information is necessary for the manufacturing order explosion.

Customer-Exits and Business Add-Ins (BAdIs)


If you use Customer Exits or BAdIs to modify the explosion data then it is no longer possible for the explosion results from SAP R/3 and SAP APO to be
compared correctly.

PUBLIC
2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 94 of 120

You can use parameters in the following Customer Exits and BAdIs to control whether your modification is taken into account in the comparison function.
The following enhancements are executed during the order explosion:
In SAP R/3:
During the explosion of the R/3 manufacturing order the following Customer-Exits are called in the enhancement CIFORD02 ( Transfer of Customer-Specific
Order Fields ):
EXIT_SAPLCOVA_001
EXIT_SAPLCORD_004
In SAP APO:
During the explosion of the PDS, the BAdI /SAPAPO/CULLRTOEXPL ( Enhancement for Exploding a PP/DS Production Data Structure ) is called.

The parameter IV_ORDERTRIGGER (= EC) specifies that the function module is called from the comparison function.
In other words, you can program that the comparison skips your modifications if the parameter is EC.

Features
The report comprises the following functions:
Comparison of the change date
Compare Last R/3 Change Date with PP/DS PDS Generation Date
Comparison of the explosion results
Compare Explosion Result in R/3 and APO
Retransfer of the master data
Automatic retransfer of the PP/DS production data structure in the background
The report can be carried out in the dialog or in the background.
To avoid a long runtime, you must enter an R/3 partner system, product and location.

Comparison of the Change Date


If you choose Compare Last R/3 Change Date with PP/DS PDS Generation Date , the system carries out a simple comparison that is exact to the day.
This means that it compares the date on which the PDS was generated (the generation date) with the date of the last change to the routing, BOM, production
version and master recipe (the change date in SAP R/3) in the UTC time zone.
If the date of the last master data change in SAP R/3 is greater than the PDS generation date in SAP APO the system regards this as a
deviation or data inconsistency.
If the R/3 change date and the APO generation date are identical, no comparison is carried out. In contrast, the system always checks the
explosion results, regardless of the date of the last master data change.
The time is not compared, due to the possible delay between the systems.
Because only the date of the R/3 change pointer in the table CIF_PPM_CHANGED is compared with the generation date of the PDS, the
performance of this comparison is better than that of the detailed comparison.
Result
The report informs you of the number of selected products and the number of products for which deviating master data has been found.
The following results are possible:
Deviating master data found
These products are displayed in the results list with the status
You can choose:

( Variance found ).

Transfer again
The PDS is retransferred.
New comparison
The new comparison can be carried out after the function Transfer again.
Display log
The log can be displayed for both successful and failed new transfers of the PDS.
In the log, the incorrect products that have not yet been transferred are displayed first, then the incorrect products that have been transferred and finally
the correct products that have been transferred.
No deviating master data found
If there is no data to be compared, for example because products are contained in the active integration model or the production version is missing, you go
directly to the application log. When you leave the application log, a dialog box is displayed, asking if you want to save the application log.
Transfer again
If you select products with variances and choose
Transfer PP/DS Production Data Structure .

Transfer again , the PDS is transferred again (and synchronously) in the same way as the R/3 function

During the retransfer, the system checks whether master data, such as work center or component, are contained in an active integration model, that is, whether
they are relevant for APO.
The existing PDS is overwritten.
Correctly transferred products have the status
.
The report changes the PDS generation date to the current date and displays the number of correct retransfers.
You can call the log in order to view correctly transferred products.
Incorrectly transferred products have the status
.
You can call a log for incorrectly transferred products.
In the
Log, you see detailed information on products with deviating master data.
For example, if a work center has been changed in a BOM and the new work center is not contained in an active integration model, you see a message
telling you that no resource is available. You must transfer the work center to SAP APO before you carry out the comparison again.

PUBLIC
2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 95 of 120

These messages are also saved in the application log ( APO Administration Integration Monitor Application Log ).
The user can select relevant messages via the object CIF, subobject IPRT.
See Application Log

If you carry out the Transfer again function more than once, only the products with the status
( Variance found ) are taken into account.
Products for which the new transfer has failed are always added to the log, this means that the logs of previous new transfers are not overwritten.
New comparison
If you choose

New comparison, after the new transfer, the products are selected and compared according to the selection criteria:

Products with the status

are no longer displayed.

Products with the status

are displayed with the status

, if the error has not been removed.

Comparison of the Explosion Results


If you choose Compare Explosion Result in R/3 and APO, the validity of the PDS is checked on the basis of the explosion date and the order quantity.
In other words, the simulated explosion result of the R/3 manufacturing order is compared with the simulated explosion result of the PDS.
For the comparison, temporary production or process orders are generated in SAP R/3 from the selection data in SAP APO.

SAP R/3
When a manufacturing order is created or changed in SAP R/3 the BOM and routing are exploded for the selected date. (The explosion date is the
date on which the BOM and routing are determined.)
The explosion date must lie within the validity of the production version.
SAP APO
The explosion date of the PDS for a receipt element for in-house production (planned or manufacturing order), corresponds to the order start date.
The explosion date can, for example, be the start date of the first activity.
Selection
You must also enter the following criteria, which are necessary for the explosion of the R/3 manufacturing order:
Interval
Order quantity
Explosion date
During the comparison of the explosion result in R/3 and APO, performance problems may occur if you try to compare a large number of
explosion results. For example, if you enter a large date range and also specify an interval of one day.
If necessary, you can
Specify tolerances in percent for the operation duration and for components
Select an automatic retransfer for background processing
Result
The system displays a list of master data in which deviations were found. The list displays the product, location, production version, status and explosion date.
Master data with deviations is displayed in the results list with the status

( Variance found ).

You can choose:

Transfer again
The PDS is retransferred.
See Transfer Again

New comparison
It makes sense to carry out a new comparison after the function Transfer again .

Display log
The log can be displayed for both successful and failed new transfers of the PDS.
For example, the system displays a message if no comparison has taken place for a product because there is no production version for the explosion date,
or no valid production version in SAP R/3.
See Transfer Again

Display comparison
If you select deviating master data and choose
Display comparison you see a detailed overview of the deviating data.
The APO and R/3 explosion results, including the operations, phases, input and output products, and relationships are displayed in a tree.
The status
indicates where the comparison function found deviating data. In this way you can see, for example, whether operations have been deleted in
SAP R/3 and are therefore missing in SAP APO, or if the duration of an activity in SAP APO exceeds the calculated permitted tolerance.
Choose

or

, to display the details of more comparisons.

Execute Comparison in the Background


You can define for the background processing of both comparisons that production data structures should be transferred again, if deviating data is found during the
comparison.
You can choose:
Automatic retransfer
If you select Automatic Retransfer of the Deviating PP/DS PDS , the production data structures are automatically transferred to SAP APO in the
background.
The following messages about the PDS comparison are displayed In the application log: Messages about successful and failed new transfers, and success
messages.
Do not retransfer
If you do not use automatic retransfer, no retransfer takes place. The deviating production data structures with their product, location and production version are
recorded in the application log.

PUBLIC
2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 96 of 120

Display messages about the comparison


Choose APO Administration Integration Monitor Application Log
You can select messages about the PP/DS PDS Comparison via o bject CIF, subobject IPRT, transaction /SAPAPO/RTO_ORD_COMP and your user name.
In addition, you see a message in the

Job Log of the background job telling you to check the application log. ( Tools CCMS Jobs )

By double clicking on the message you see the long text and can go to the application log.

Activities
Choose Master Data PP/DS Production Data Structure 1.5.2.2.2 Comparison of PP/DS Production Data Structure or APO-Administration
Integration Comparison of Master Data Comparison of PP/DS Production Data Structure (/SAPAPO/RTO_ORD_COMP).

System Behavior During Comparison of Explosion Results


The following sections describes which checks the system carries out before the comparison and which steps are executed as part of the comparison of the
explosion results.
Prerequisites
Before a manufacturing order is simulated for the comparison of the explosion in SAP R/3, the system checks that:

The header material is contained in an active PDS integration model


The header material exists or whether a deletion flag is set for the header material
Production versions are not locked or deleted
The explosion date entered lies within the valid from and valid to dates of the production version
The explosion quantity lies within the from and to lot size of the production version
If R/3 work centers (resources) are not relevant for APO, (in other words, not in an active integration model) the R/3 operations for these resources
are filtered during the comparison. The comparison is still carried out, but the operation is not displayed in the R/3 explosion result. If a
corresponding operation exists in the APO explosion result, these operations are marked as deviating.
If R/3 components (input products) are not relevant for APO, then they are also filtered.

If these conditions are met the system carries out the comparison.
Process Flow
The following steps are carried out:
1. Simulated manufacturing order is created in SAP R/3
Effect of the criteria entered on manufacturing order explosion:
Explosion date (from to)
You can enter dates for which an explosion should be simulated.
The system:
Checks the validity of the production version on the explosion date
SAP R/3 checks whether the explosion date lies within the validity of the production version, in other words, whether the production version is valid
at the time of order creation.
If the system does not find a valid production version, because production versions have been deleted, changed or locked, then no comparison
takes place.
Carries out a BOM explosion with the explosion date ( from )
Therefore, only components that are valid at the time of the explosion are compared.
Interval
The number of days or weeks entered is used to calculate additional key dates on which master data should be exploded and compared.

For example, to compare explosion results for more than one point in time in November you could enter the explosion date 01.11. to 30.11.and
choose the interval 1 and Week .
The system would then simulate the explosion result for every week (every 7 days) and therefore carry out four comparisons.
Order quantity
The order quantity is always used for the order explosion. If you select Use Fixed Lot Size of Product and the fixed lot size is greater than zero (R/3
material master, MRP 1 view), the fixed lot size is used as the order quantity.
Tolerance in % for operation duration
The duration of an operation is calculated using the scheduling formula from the routing (work center).
To settle rounding differences you can specify a percentage tolerance for operation durations. The tolerance is always calculated on the basis of the R/3
operation duration.
If the difference between the operation durations exceeds the calculated admissible tolerance, the operation is regarded as deviating.

Operation duration in SAP R/3: 120 mins


10 % admissible tolerance 12 mins
Operation duration in SAP APO: 130 mins
Difference in operation duration 130 120 = 10 mins OK
Tolerance in % for components
The component quantity can be calculated in the manufacturing order using the material quantity calculation.
To settle rounding differences, you can specify a percentage tolerance for input products (components) and for output products (co-product, by-product).
The admissible tolerance is always calculated on the basis of the R/3 quantity.
This comparison checks whether, for example, quantities in the BOM have been changed.

PUBLIC
2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 97 of 120

If the difference between the APO quantity and the R/3 quantity exceeds the admissible tolerance the quantity is marked as incorrect.

Component quantity in SAP R/3 42 pieces


10 % admissible tolerance 4.2 pieces
Quantity in SAP APO 50 pieces
Quantity difference 50 42 = 8 pieces not OK
2. Comparison of the explosion results from simulated manufacturing order (SAP R/3) and from simulated PDS explosion (SAP APO)
Which master data is compared?
Only the operations, phases, input and output products, and activity relationships of the manufacturing orders are compared.
Operations and phases
Number of operations or phases
Operation number, phase number
Duration
The durations of dynamic setup (setup group, setup key) are not compared because they are calculated in SAP APO.
Operation quantity
Operation scrap in %
Number of activities (setup time, processing time, teardown time)
Number of resources
Resources have been changed in SAP R/3
Number of capacities of the resources
Capacities of the resources have been changed in SAP R/3
Input and output products
Number of components
Input components have been changed
Component quantity
Activity relationship
Number of activity relationships
Process-related minimum interval
Planning-related minimum interval
Maximum interval
Scheduling of relationships (SPACE = not scheduled, 1 = scheduled via predecessor, 2 = scheduled via successor)
The following restrictions apply:
Suboperations and secondary resources are not compared.
The configuration of the input and output products is not compared.
Setup groups and setup keys are not compared.
3. List of variances is output
See also:
Integration of PP/DS Production Data Structures
Production Data Structure

!--a11y-->

Generating DP Production Data Structures (DP PDS)


Use
You can use this function to generate DP production data structures. You can use these in Demand Planning.

Integration
DP PDS that were generated from iPPE master data with the usage Demand Planning in the access are already available for Demand Planning.

Prerequisites
If you are working with master data from SAP R/3, you have transferred the data via the CIF; and can use one of the following PDS in SAP APO:
PP/DS PDS from R/3
SNP PDS from R/3

PUBLIC
2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 98 of 120

If you are working with iPPE master data, you have generated one of the following PDS and the data are already active in SAP APO:
PP/DS PDS from iPPE
SNP PDS from iPPE
See Generate Production Data Structures (PDS) for All Models

Features

You can generate PDS from iPPE and R/3 master data , and update existing DP PDS.
You can use the SNP PDS and the PP/DS PDS for generating a DP PDS.
You can specify if the system determines the source of supply according to procurement priority or costs.
You can enter a name for the DP PDS manually, or use a name generated by the system.

Activities
1. On the SAP Easy Access screen , choose Advanced Planning and Optimization Master Data Production Data Structure (PDS) Generate
DP Production Data Structure .
The Generate or Update DP Production Data Structures screen appears.
2. Decide if you want to generate a new DP PDS or update an existing one.
3. Enter the data for the product.
4. Choose the PDS type that provides the basis for generating the DP PDS.
5. Define how the system selects the source of supply.
6. Enter the remaining data.
7. Choose Execute .
8. The DP PDS Generation screen appears, where you can view messages regarding the DP PDS generation.

!--a11y-->

1.5.2.4 Display Production Data Structures


Use
Display Production Data Structures can display many types of production data structures (PDS), each generated from either an R/3 BOM/routing or recipe, or
from iPPE. Display Production Data Structures can display structures generated from the following sources:
Sources of Production Data Structures
R/3 BOM/routings or recipes for:

iPPE data for:

PP/DS (production planning / detailed scheduling)

PP/DS
Shop floor scenario
Line scenario with single explosion
Line scenario with matrix explosion

SNP (supply network planning)

SNP

CTM (capable to match planning)

CTM

DP (demand planning)

DP

Integration
Display Production Data Structures can be accessed directly, or it can be called by several other functions. For example, Display Production Data
Structures is accessed by the following functions (among others):

iPPE Workbench Professional

Planned Order Management


Display Production Data Structures is also called by other functions such as iPPE. Depending on the choices you make in the calling function, the system
either finds
the PDS corresponding to the objects you choose (production versions or production orders, for example) and presents the results list
or presents the selection screen

Prerequisites
You must have generated production data structures from either of the following:
SAP R/3 data using the CIF (Core Interface) in R/3
iPPE data in SAP APO using the generation report/transaction.

For more information see Generating PDS for all models.

Activities
PUBLIC
2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 99 of 120

1. In the SAP Easy Access menu, choose Advanced Planning and Optimization Master Data Production Data Structures Display Production Data
Structures.
The Load Production Data Structure dialog box appears.
2. Enter your search criteria.
Alternatively, if you frequently use the same search criteria, you may define and save variants that you access using

Get Variant . To begin the

search, choose
Execute .
The Display Production Data Structures screen appears. The system displays a results list with the production data structures matching your search
criteria.
3. You select an individual PDS from the results list and the system displays the first level of detail for this PDS in several tabs below. If only one PDS is
found, the system automatically displays the first level of detail for that PDS.

You can change the columns that display on the Display Production Data Structure screen by choosing
Select Layout . This ability
applies to all levels of detail and to the results list. The initial (unexpanded) results list has hidden columns, but subsequent detail lists do not.

By choosing different Valid From and Valid To dates, you get different results in the results list.

First Level of Detail


When you select a PDS from the results list and choose
( Display Production Data Structure) , the system displays details for an individual PDS within one or
more tabs. The following tabs are presented on the tab strip of the first level of detail for a PDS (assuming the PDS has all the relevant data). Once the details are
displayed, the icon in the Detail column changes to ( PDS Displayed).
Tab Strip for First Level of Detail
Tab

Comment

Components
Activities

Not applicable to DP or line scenarios

Operations

Not applicable to DP

Activities (Line)

Line scenarios only

Activities (Routing)

Line scenarios only

Activity Relationships

Not applicable to DP or line scenarios

Activities Relationships (Line)

Line scenarios only

Activities Relationships (Routing)

Line scenarios only

Reporting Points

Only applicable to iPPE.

Reporting Point Relationships

Only applicable to iPPE

Subsequent Levels of Detail


You can drill down from the first level of detail displayed by selecting one or several rows within a tab and choosing

(Open Detail Level) in the toolbar. If you

only want to explode one row, you click on a hotspot ( ), or double click the row. The system displays the tab strip one level below. For example, you could
choose the Activities tab, then the Modes tab within Activities , and then Capacity/Requirements within Modes.

The first level of detail always shows all available data for the PDS, but the dependent tap strips in subsequent levels show only data that is
related to the row or rows selected in the tab above .
Certain hotspots, such as
valuation assignments.

(Open object dependency) and

(Open valuation) , open the relevant tabs to display, for example, object dependencies or

Dependent Tab Strips


The tables below list the various dependent tab strips and the tabs within each one.
Dependent Tabs for Components Tab Strip
Tab

Comment

Mode dependent data (such as production supply areas)

PP/DS and iPPE only

Selection conditions

PP/DS only

Procedures

PP/DS only

Valuation Assignment

PP/DS only

Dependent Tabs for Operations Tab Strip


Tab

Comment

Activities

Not applicable to line scenarios

Activities (Line)

Line scenarios only

Activities (Routing)

Line scenarios only

PUBLIC
2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 100 of 120

Dependent Tabs for Activities, Line Activities, and Routing Activities Tab Strips (Single Explosion)
Tab

Comment

Modes
Components
Activity relationships

Normal/line/routing depending on activity type above and only if tab above is not a
relationships tab

Selection conditions

PP/DS only

Procedures

PP/DS only

Block planning valuations

PP/DS only

Dependent Tabs for Routing Activities Tab Strip (Matrix Explosion )


Tab

Comment

Line assignments
Capacity requirements

Dependent Tabs for Routing Activities Tab Strip (Matrix Explosion)


Tab

Comment

Activities

Same kind as the relationship

Dependent Tab for Reporting Point Relationship Tab


Tab

Comment

Reporting points

Dependent Tabs for Modes Tab Strip


Tab

Comment

Capacity requirements
Reporting points
Selection conditions

Only applies to PP/DS, but not to matrix explosion

Procedures

Only applies to PP/DS, but not to matrix explosion

Time dependent parameters for modes

iPPE only

Dependent Tabs for Capacity Requirements Tab Strip [except if tab above is routing activities / matrix explosion)
Tab

Comment

Time dependent parameters for capacity requirements

iPPE only
If the drill-down path to the capacity requirements starts at the operations or activity
relationships, the paths are as follows:
Operations Activities Modes Capacity Requirements .
Activity Relationships Activities Modes Capacity Requirements
In this case, all four tab strip levels are used up and it is not possible to drill into the time
dependent parameters. (It is possible, if the path starts with the Activities tab.)

Icons
Display Production Data Structures uses certain icons in a unique manner. Those instances are explained below.
Functions of PDS Icons>
Icon

Use
Denotes one of the following functions, depending on where it is used:
Display production data structure
Open next detail level
Show sub-operations/secondary resources
Show component (phantom assemblies)

PUBLIC
2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 101 of 120

T o choose more than one row in detail levels of the screen, you must first select the
rows, then use
the information.

(Open next detail level)

on the left side of toolbar to expand

Denotes one of two possible functions, depending on where it is used:


PDS displayed
Row displayed
Show all obsolete statuses.
The system loads obsolete status(es) into the results list below the line on which you
click the hotspot.
Show simulated PDS.
If the simulation succeeds, the system loads the simulated PDS into the results list
below the line on which you click the hotspot, and explodes it.
Simulated status
Several entries - see next detail level
Open valuation
Open object dependency
Open time-dependent parameters
Denotes one of two possible functions, depending on where it is used:
Hide sub-operations/secondary resources
Hide component (phantom)
Loads the selected PDS into the result list

The icons below are used to specify configuration statuses.


Icons for Configuration Status
Icon

Use
The PDS is configured with this configuration.
The characteristics have changed since the last configuration.
Configuration is not yet applied to the PDS.

The icons below apply to the Configuration tab.


Icons for Configuration Tab
Icon

Use
Apply configuration
Reject configuration
Load configuration

The icons below apply to the o bject dependency tabs (selection conditions / procedures).
Icons for Object Dependency Tabs
Icon

Use
Page forward (either to the next object dependency within a component, an operation, an
activity, or a mode; or to the object dependency of the next component, operation, activity,
or mode)
Page backward (either to the prior object dependency within a component, an object, an
activity, or a mode; or to the object dependency of the prior component, operation, activity,
or mode)

The icons below allow you to manipulate the size of the various screen areas.
Screen Sizing Icons
Icon

Use
Increase Gradually
Allows you to expand the adjacent screen area by clicking the button repeatedly.
Decrease Gradually
Allows you to shrink the adjacent screen area by clicking the button repeatedly. You can
cause the screen to disappear entirely by repeatedly clicking the button.
Focus on area

PUBLIC
2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 102 of 120

Expands the adjacent screen area to consume most of the screen. It also shrinks screen
areas above the focus area to minimal size, and drops screen areas below the focus area
entirely.
Size Adjustment-Off
System automatically resizes screen areas (resizing is turned on.) By selecting
button, you turn resizing to off.
Size Adjustment-On
Screen areas are not resized automatically (resizing is turned off). By selecting button,
you turn resizing to on.

See also
Simulating a Production Data Structure
Selecting a Production Data Structure
!--a11y-->

1.5.2.4.1 Simulating a Production Data Structure


Use
Display Production Data Structures may be used in simulation mode allowing you to simulate a new status, a configuration, and an explosion date. You define
what if criteria to simulate different production data structure (PDS) scenarios, or statuses . You might wish to simulate a PDS if, for example, the underlying
data has changed since the PDS was created. To do so, you would generate a status of a PDS that does not exist for current data (although there may be a PDS
for old data). You could then see what the PDS would look like based on current data.

Simulated production data structures cannot be saved.

Prerequisites
If you want to simulate a configuration, the PDS to be simulated must contain a configurable material.
If you want to simulate a new status, your iPPE data must have changed since the original PDS was created.

Activities
Initiating a Simulation
There are two ways to initiate a status simulation:
1. Chose an existing PDS on the results list and then choose
2. Initiate the simulation from iPPE.

( Simulate).

Before you can simulate using Display Production Data Structures, a PDS must exist for the relevant iPPE data.
You simulate statuses of a PDS based on variations in explosion date,. configuration, or new iPPE data. Your procedure varies slightly depending on the
basis of your simulation.
If you are performing a simulation for a specific explosion date, enter the date in the Explosion Date column of the results list and choose

( Enter).

If you are performing a simulation for a specific configuration, select the Configuration tab, change or enter the new values, and choose
Configuration) .

(Apply

If you are performing a simulation for new iPPE data, choose

(Simulate) in the desired row of the results list, or simulate a production version from iPPE.

If you initiate the simulation from iPPE, the system searches for the original PDS in addition to simulating a new PDS based on current iPPE data.
It then displays both the original and the simulated PDS in the results list and automatically explodes the simulated PDS.

Configuration
Configuration allows you to assign values to certain characteristics of configurable materials.
You may wish to simulate a PDS based on different configurations (sets of values assigned to your configurable materials). You can do this simulation using an
existing PDS, or using a simulated PDS. This capability allows you to test and troubleshoot the configuration of a product.
To maintain configuration in Display Production Data Structures , you access the functionality on the Configuration tab of the first level of detail for your PDS.
When you change configuration, you use the icons in the table below.
Configuration Icons
Icon

Use
Use Apply Configuration to activate the new configuration for your PDS when you enter
a new configuration, or change an existing configuration.
Use Reject Configuration to reset the data in the configuration table to whatever it
started with, and to remove the configuration from the PDS.

PUBLIC
2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 103 of 120

Use Configuration from Order to retrieve a configuration from an order and load those
values into your configuration table. Configuration from Order does not apply the
retrieved configuration. After the configuration is retrieved, you must change it and apply
it or apply it as is for the configuration to take effect.

Explosion Date
The explosion date allows you to look at the PDS at a point in time. It controls which components, activities, and so on are selected based on their validity
periods.
You enter an explosion date for a PDS to restrict the display for the components, modes, activities, and so on that are valid for this day. You can enter the
explosion date in the selection screen, or enter or change it in the results list. Normally, the field is blank unless you enter a value, or unless a value is transferred
from the selection screen or from an order.
See Selecting a Production Data Structure for examples of using the explosion date.
See Also
Display Production Data Structures

!--a11y-->

1.5.2.4.2 Selecting a Production Data Structure


Using the Selection Screen
Here, we provide details and examples about how the selection criteria on the selection screen work.
The screen is divided into three sections: General Selection Criteria , Production Data Structure for Order, and Production Data Structure for Account
Assignment Object . Below are rules about how these sections work.
If you only supply General Selection Criteria parameters, Display Production Data Structures selects any PDS that matches the criteria.
If you only enter an Order, Display Production Data Structures searches for orders with the order number that you specify (it could be more than one order, as
order numbers are not unique) and then displays the PDS for each order.
If you enter data in both General Selection Criteria and Production Data Structure for Order sections, the system first evaluates the order number, and then
restricts the displayed results to match the General Selection Criteria . However, this combination of criteria is rarely necessary, since APO orders have only
one item and not many orders have the same number.
If you only enter an Account Assignment Object , the system displays all production data structures associated with this account assignment object. This
may result in many production data structures being displayed.
If you enter a combination of General Selection Criteria and Account Assignment Object: the system searches using all the selection criteria.
You may not combine the selection areas Production Data Structure for Order and Account Assignment Object.

Examples Using Explosion Date


When you access Display Production Data Structures , you specify explosion dates for the production data structure(s) you want to see. The choices that you
make control which production data structure(s) appear in the results list. The examples below illustrate how your choices in explosion dates influence which
production data structure(s) are displayed.

All the examples below assume a PDS with iPPE data. PDSs generated from R/3 data do not have statuses, however, the validity dates still
apply.
The figures in the cases below illustrate an example where you have a database containing four validity periods for one PDS ( 1.x, 2.x, 3.x, and 4.x). In addition
to having a validity period, every PDS can have one or more statuses, identified here by the number after the decimal point. For example. validity period 1 has
status 1.1, 1.2, and 1.3. Each status is a different iteration of the PDS using data from different dates (1/15, 1/23, 2/8, and so on).

Case 1: You do not specify an explosion date.


In Case 1, you have specified your PDS but no explosion dates on your selection screen. The shaded boxes represent a combination of status/validity periods
that would be displayed in your results list. Below the figure, the results list table shows what you would see in the results list on your screen.
Box 1.3 (see first row of results table below), shows the newest PDS status for the validity period Jan. 15, 2004 Jun. 15, 2004. This status was created on Feb.
17, 2004 and it has two obsolete statues (1.1 and 1.2, created on Jan. 15, 2004 and Jan. 23, 2004 respectively).

PUBLIC
2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 104 of 120

Results List
Reference box in graph

Valid from

Valid to

Explosion Date

Created on

Obsolete Status

1.3

Jan. 15, 2004

Jun. 15, 2004

Feb. 17, 2004

1.2, 1.1

2.2

Jun. 15, 2004

Apr 1, 2005

Feb. 8, 2004

2.1

3.1

Apr. 1, 2002

Nov. 27, 2006

Jan. 23, 2004

4.1

Nov. 27, 2006

Dec. 31, 9999

Jan. 23, 2004

Case 2: User Enters an Explosion Date Range.


In Case 2, you have specified a PDS, and also an explosion date range on the selection screen. The shaded boxes represent combinations of validity period/
status that would be displayed in your results list. The large colored area represents the date range that you selected, in this case May 1, 2004 May 1, 2005.
Below the figure, the results list table shows what you would see in the results list on your screen.
The system searches for any PDS whose validity overlaps your date range. So, in this case, the system selects 1.3, 2.2, and 3.1. It also selects the obsolete
statuses of 1.1, 1.2, and 2.1, but it hides these statuses behind

Obsolete Status.

Results List
Reference box in graph

Valid from

Valid to

Explosion Date

Created on

Obsolete Status

1.3

Jan. 15, 2004

Jun. 15, 2004

Feb. 17, 2004

1.2, 1.1

2.2

Jun. 15, 2004

Apr. 1, 2005

Feb. 8, 2004

2.1

3.1

Apr. 1, 2002

Nov. 27, 2006

Jan. 23, 2004

Case 3: User Enters a Specific Explosion Date


In Case 3, you have specified a PDS, and also a specific explosion date on the selection screen. The shaded boxes represent the validity period / status that
would be displayed in your results list. The colored arrow represents the date that you selected, in this case Jan. 1, 2005. Below the figure, the results list table
shows what you would see in the results list on your screen.
The system searches for any PDS whose validity range contains your date. So, in this case, the system only selects 2.2 (2.1 is selected, but hidden behind
Obsolete Status).

PUBLIC
2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 105 of 120

Results List
Reference box in graph

Valid from

Valid to

Explosion Date

Created on

2.2

Jun. 15, 2004

Apr. 1, 2005

Jan. 1, 2005
Feb. 8, 2004
This date is transferred from
the selection and used to
explode the PDS.

Obsolete Status
2.1

Case 4: User Specifies an Order


In Case 4, you have specified an order number on the selection screen. The order creation date determines which validity period and which status is selected.
The shaded boxes represent the validity period and the status that would be displayed in the results list. The colored line represents the order date, in this case
Feb. 1, 2004. Below the figure, the results list table shows what you would see in the results list on your screen.
The system searches for any PDS whose validity range contains the order (creation) date. It also discards any status that is newer than the order date. So, in this
case, the system only selects 1.2 (1.1 is selected, but hidden behind
created, this status did not exist, making it irrelevant for this case.

Obsolete Status). Status 1.3 is not selected because at the time the order was

Since you are using an order in this example, the system shows you the status that is automatically used for backflushing. There maybe newer
statuses of that PDS that do not display on the screen. If we were not using an order, the system would show us the newest status, which is not
necessarily the one used for backflushing. In this case, you could manually search for the correct status.
This concern might arise, for example, if you are troubleshooting the backflushing of an order.

Results List
Reference box in graph

Valid from

Valid to

Explosion Date

Created on

1.2

Jan. 15, 2004

Jun. 15, 2004

Feb. 1, 2004
Jan. 23, 1004
This date is transferred from
the order and used to
explode the PDS.

Obsolete Status
1.1

Case 5: How the Explosion Date Affects the Detail Screen


Assume that PDS 2.2 is exploded, and that the explosion date in the result list is empty. In the modes tab, you would see something like the table below:

PUBLIC
2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 106 of 120

Modes Tab
Mode

Duration

Valid from

Valid to

30 min

Jan. 15, 2004

Mar. 7, 2005

25 min

Mar. 7, 2005

Dec. 31, 9999

If you entered an explosion date of Feb. 1, 2004 you would only see one line, as illustrated below:
Modes Tab
Mode

Duration

Valid from

Valid to

Mode

Duration

30 min

Jan. 15, 2004

Mar. 7, 2005

30 min

See also
Display Production Data Structures
Simulating a Production Data Structure

!--a11y-->

Deleting Production Data Structures (PDS) in SAP SCM


Use
You can use this function to delete all types of production data structures (PDS) in SAP APO.

Features
You can define for which applications (Demand Planning, Supply Network Planning, Production Planning and Detailed Scheduling) you wish to delete the
selected PDS.
You can define if the selected PDS is deleted for all models or only in specific planning versions.
You can further restrict the type of PDS that is deleted depending on where the PDS master data originated from (iPPE master data or R/3 master data).
You can also simulate deletion for a PDS generated from iPPE data to check if the PDS is still being used in orders. To do this, set the Simulate indicator.
If the PDS is still being used in orders, it is not deleted. If the PDS is still being used in orders, you may delete it by setting the Delete PDS Despite Usage
indicator.

Activities
1. On the SAP Easy Access screen, choose Advanced Planning and Optimization Master Data Production Data Structure (PDS) Delete
Production Data Structure .
The Delete Production Data Structures screen appears.
2. Enter the product and the location, and specify the name of the production version in the Source of Supply field in SAP APO.
3. Select the usage for which you want to delete the PDS.
4. Specify if the PDS is deleted for all models or only in specific planning versions.
5. Under Mast. Data Type , specify the type of master data for the PDS that is to be deleted; further restrict the selection under Options iPPE and Options
R/3 .
6. Choose Execute .
The Logs screen appears. Here, the system lists the messages that were output when deleting the PDS.

If you wish to delete production versions that originate from SAP R/3, proceed as follows:
Delete the production version in SAP R/3. Start the change transfer for the PDS.
The source of supply in SAP APO and the relevant PDS are deleted.
If orders exist in SAP APO, then the production version in SAP R/3 is deleted. However, the source of supply and relevant PDS are not deleted
in SAP APO.

!--a11y-->

Integrated Product and Process Engineering (iPPE)


Purpose
This component enables you to collect all the data for an entire product life cycle in one integrated model. It is particularly suited to products with many variants.

PUBLIC
2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 107 of 120

You can use iPPE to document data, and later re-use and update it, from early phases of the research and development process for a product. You can represent
a complete production model because Integrated Product and Process Engineering allows you to keep the master data for BOMs, routings, and line design in one
model. It is particularly suited to repetitive manufacturing.
You maintain the data in a functional structure, which you fill with more data at later stages in the product development, thus representing the whole product life
cycle.
There is an interface for connecting time analysis products to the iPPE routing (process structure). You can determine processing times and transfer these times to
Integrated Product and Process Engineering.

Integration
You require the following mySAP.com components to use Integrated Product and Process Engineering:
Engineering Change Management (ECM)
Classification System
Variant Configuration
You must install the iPPE component and maintain the data in order to plan material requirements with the Rapid Planning Matrix (RPM). For further information on
the above-mentioned components, see Variant Configuration, Classification System, and Engineering Change Management.

Features

The product variant structure and assemblies can be used to maintain BOM data for configurable and non-configurable materials.
You can use the process structure to maintain routing data.
Line design can be used to maintain the structure and setup of your production lines.
You can use Engineering Change Management to edit PVS variants and modes. When you use ECM, the system can make operational use of different
change statuses. When you do not use ECM, there is exactly one valid status for each object in the system.
Material requirements planning with the RPM in the SAP Advanced Planner and Optimizer (SAP APO) is based on the master data from iPPE.
The product variant structure and the iPPE routing can be maintained as functional structures when you begin to develop a product. It is not necessary to
assign precise materials or activities, for example, at this stage. They can be added to the model at a later phase in product development.
You can use the network graphic to display a model from Integrated Product and Process Engineering as a graphic.

!--a11y-->

1.6 Hierarchy
Definition
Hierarchies serve to depict hierarchical relationships between the master data objects of an object type. Hierarchies are based on hierarchy structures and can
be created, changed, and deleted in the course of hierarchy maintenance.
Hierarchies can be formed from the following master data object types:
Location
You can define a
transportation zone hierarchy for locations, for example.
Product
A hierarchy of this master data type might consist of product family, product group, and product, for example.
Location product
Hierarchies for location products can be generated from location hierarchies and product hierarchies (generated hierarchy). Manually maintained location
product hierarchies can be set up on a cross-location basis.
Resource
Similar resources can be combined to form a resource group. The resources can be planned individually but can be used as a resource group in the
production process model (PPM). This facilitates a rough capacity check in the entire supply chain.
Production process model (PPM)/product data structure (PDS)
A hierarchy for a PPM or a PDS might consist of a PPM for a product group and a PPM for a product, for instance.
A master data object can occur in different hierarchies.
For more information, see Hierarchy Structure and Maintain Hierarchy.

!--a11y-->

1.6.1 Hierarchy Structure


Definition
A structure, defined in Customizing, that forms the basis of a hierarchy. The hierarchy structure determines the following properties of each hierarchy whose basis
it forms:
Master data object type from which the hierarchy is built (for example, location).
Maximum number of levels the hierarchy can have.
Each hierarchy structure belongs to one of the following four hierarchy structure categories:

PUBLIC
2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 108 of 120

Hierarchy
Generated hierarchy
Schema hierarchy
Extended Hierarchy

Use
Hierarchy structures are necessary prerequisites for the creation of hierarchies. Each hierarchy is based on a hierarchy structure.
You define hierarchy structures in the mySAP SCM Implementation Guide under Advanced Planning and Optimization Master Data Hierarchy
Define Hierarchy Structure . For more information, see the documentation on this IMG activity.

!--a11y-->

1.6.2 Maintain Hierarchy


Use
Hierarchies serve to depict hierarchical relationships between master data objects. Hierarchies can be used in different applications, such as
(Aggregated) Planning in Supply Network Planning (SNP) or in Transportation Planning/Vehicle Scheduling (TP/VS).
In Service Parts Planning (SPP), location hierarchies are used to represent
region patterns also via hierarchy maintenance.

bills of distribution and

Hierarchical

region patterns. You create bills of distribution and

You can create hierarchies for the following master data objects:
Product
A hierarchy of this master data type might consist of product family product group product.
Location product
Hierarchies of this master data type combine location hierarchies with product hierarchies. Location product hierarchies can be cross-location.
Location
For this master data type, you could define a customer hierarchy containing customer groups with different customers. This could obviate the need for singleitem planning.
Resource
Similar resources can be combined to form a resource group. The resources can be planned individually but can be used as a resource group in the
production process model (PPM). This facilitates a rough capacity check in the entire supply chain.
Production process model (PPM)/production data structure (PDS)
A hierarchy for a PPM or a PDS might consist of a PPM for a product group and a PPM for a product, for instance.
A master data object can occur in different hierarchies.

Prerequisites
You have created a hierarchy structure in Customizing.

Procedure
Create and Change Hierarchies
1. From the SAP APO Easy Access Men, choose Master Data Hierarchy Maintain Hierarchy .
2. Enter the name of the hierarchy you wish to create or change. You are now in hierarchy maintenance mode.
3. Create a new hierarchy by adding additional subnodes (i.e. master data objects) to the uppermost node. The number of hierarchy levels available depends
on the hierarchy structure used.
You can change already existing hierarchies by adding, changing, or deleting nodes.

You can also transfer the nodes of a hierarchy in the fast entry facility by double-clicking. Here you can change, insert, or delete the master data
objects of the next lower level and adopt these changes in the hierarchy via the Transfer button.
Copy Hierarchies
You can copy an existing hierarchy. However, the subnodes are not copied at the same time. In hierarchy maintenance mode, choose Change and enter the
relevant data in the Copy Hierarchy dialog box.
Delete Hierarchy
To delete an existing hierarchy, choose Delete Hierarchy in the same menu path.

!--a11y-->

1.6.3 Schema Hierarchy


PUBLIC
2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 109 of 120

Definition
The schema hierarchy is a hierarchy structure category that differs from the structure category hierarchy in the assignment of the level numbers.

Use
Level number in the case of the structure category hierarchy
The levels are pulled in numerical order. The number itself has a meaning.
Level number in the case of the structure category schema hierarchy
The level number in case of these hierarchies is a designation that does not contain the numerical order of the levels but has significance as a number per se.
The specified value of the level number stands for the number of characters that defines the object of the level:
Level number

Number of characters

Object

Level 1: 3

3 characters

AAA

Level 2: 5

5 characters

AAA BB

Level 3: 9

9 characters

AAA BB CCCC

Note that the characters of the object at the upper level must be replicated at a subordinate level so that the assignment can be recognized. Level 2 objects with
the designation AA1 BB, for example, cannot be assigned here to a higher level.
Unlike hierarchy structures, the digit here has both a classification and semantic significance.

!--a11y-->

1.6.4 Extended Hierarchy


Definition
Hierarchy structure category with respect to which, in contrast to the hierarchy structure category 'hierarchy', a child hierarchy node can be assigned to several
parent nodes.

Use
You can use an extended hierarchy if a hierarchy node is to be assigned to several parent nodes. However, the node that is assigned multiple times must always
be assigned at the same hierarchy level.
An extended hierarchy can make sense in processes of transportation planning/vehicle scheduling (TP/VS), for example, in which a plant delivers materials to a
customer and several alternative itineraries involving different transshipment locations (such as ports) are available. In this case, you can use an extended
hierarchy to assign a plant (hierarchy level 2) to several transshipment locations (hierarchy level 1), for example.

!--a11y-->

1.7 Transportation Lane


Use
You need transportation lanes when planning distribution and procurement between different locations. Products can only be procured if transportation lanes exist
between the possible locations.
For information on change logging for transportation lanes, see Change Logging for Master Data.
For information on the where-used list for transportation lanes, see Where-Used List for Master Data.
Transferring Stock from one Location to Another
In SAP APO, you can use transportation lanes to plan stock transfers between locations. You can:
Create a transportation lane manually in SAP APO
Store a special procurement type in the material master record in SAP R/3
When a material master record is transferred with one of these special procurement types via CIF, the corresponding transportation lane between the
supplying plant and the receiving plant can be created the SAP APO system automatically.
For more information, see Automatic Creation of Transportation Lanes.
External Procurement Relationships
In the SAP R/3 system, the business relationship between a supplier and a plant (customer) is stored as a purchasing info record or outline agreement (contract
or scheduling agreement). When you transfer this purchasing data to SAP APO, the system automatically generates external procurement relationships. At the
same time, the system creates a transportation lane from the supplier to the plant. The external procurement relationship and transportation lane are assigned to

PUBLIC
2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 110 of 120

each other.
For more information, see External Procurement Relationship.
You can also assign an external procurement relationship to a transportation lane manually. For example, for subcontracting with components provided by a third
party, you have to manually create the transportation lane from the supplier to the subcontractor in SAP APO.
See also:

Subcontracting with Third-Party Provision of Components in PP/DS

Sales Scheduling Agreements


In the SAP R/3 system, the business relationship between a plant (supplier) and a customer is stored as a sales scheduling agreement. If you have transferred
these sales scheduling agreement from Sales and Distribution (SD) to SAP APO, the system automatically generates sales scheduling agreements there. At the
same time, the system creates a transportation lane from the plant to the customer. The sales scheduling agreement and transportation lane are assigned to each
other.
For more information, see:
Release Management for Sales Scheduling Agreements
Collaboration via Procurement and Sales Scheduling Agreements

Structure
A transportation lane is specified more exactly by the following:
The products that can be procured via this transportation lane
The means of transport that can be used for transporting the products being procured
You can create a transportation lane as follows:
For a specific product
For a product group
This option is displayed only if you have defined at least one product group in Customizing for the product master.
For all products
For a specific mass selection
Note that you can only use mass selection for products that exist at both the start and destination locations.
Product Procurement Parameters
The parameters for product procurement enable the system to find the valid sources of supply in the source determination process, for example.
Means of Transport
Means of transport are used to move goods between the locations of a transportation lane. The term covers trucks, ships, aircraft etc. You assign means of
transport to a transportation lane and specify the associated parameters such as the transportation duration, transportation distance, and transportation costs. The
system can also calculate the straight line distance (as the crow flies) from the geographical coordinates of the location. If multiple means of transport are assigned
to a transportation lane, the SNP optimizer can decide which one to choose on the basis of the transportation duration, transportation costs, and penalty costs for
delays.
Product-Specific Transportation
You can assign a product-specific means of transport to one or more products. You must have already defined this means of transport in the means of transport
list.
You can assign the means of transport as follows:
You can assign a specific means of transport or all available means of transport to a product.
To do so, you select a product from the Product Procurement list and choose the Create button in the Product-specific Means of Transport list.
You can assign one product or all existing products to a means of transport.
To do so, you select a means of transport from the Means of Transport list and choose the Create icon in the Product-specific Means of Transport list.

!--a11y-->

Automatic Creation of Transportation Lanes


Use
Transportation lanes can be created automatically as well as manually.
Transportation lanes are created automatically in the SAP APO system if you have transferred the following data from the SAP R/3 system into the SAP
APO system using the SAP APO Core Interface (CIF):
Purchasing data, such as purchasing info records, contracts, or scheduling agreements
Sales scheduling agreements
Material masters with a special form of procurement consisting of a procurement type F: External procurement and a special procurement U: Stock
transfer .

Prerequisites
You have transferred the following data from the SAP R/3 system using CIF:
For transportation lanes with reference to R/3 purchasing data:

PUBLIC
2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 111 of 120

Purchasing info records


Scheduling agreements
Contracts
To be able to transfer purchasing data, you also have to transfer plants, material master records, and vendor master records.
For more information, see Processing an External Procurement Relationship.
For transportation lanes with reference to R/3 sales scheduling agreements:
Sales scheduling agreements
To be able to transfer sales scheduling agreements, you also have to transfer plants, material master records, and customer master records.
For transportation lanes with reference to the special procurement type of the R/3 material master record:
Material master records
To be able to transfer material master records, you also have to transfer plants.

Features
Transportation Lanes with Reference to R/3 Purchasing Data
If you have transferred purchasing data from the SAP R/3 system, the SAP APO system automatically creates external procurement relationships for the
products concerned.
For more information, see Processing an External Procurement Relationship.
For example, if the external procurement relationship contains an info record that has a vendor as the source location and a plant as the destination location, the
system creates a corresponding transportation lane running from the vendor location to the plant location.
The system links the external procurement relationship with the transportation lane. This transportation lane contains the following product procurement data:

Validity period
Form of procurement
Source of supply type
Purchasing document number
Purchasing document item
Purchasing organization
Planned delivery time
Goods receipt time

Transportation Lanes with Reference to Sales Scheduling Agreements


If you have transferred sales scheduling agreements from the SAP R/3 system, the SAP APO system automatically creates APO sales scheduling agreements
for the products concerned.
If the APO sales scheduling agreement contains items that have a plant as a source location and a customer location as a destination location, the system
creates a corresponding transportation lane running from the plant location to the customer location.
The system links the APO sales scheduling agreement with the transportation lane. This transportation lane contains the following external procurement data:
Sales document number
Sales item
Sales organization

Transportation Lanes with Reference to R/3 Material Master Record


Storing a special procurement type with procurement type F: External Procurement and special procurement U: Stock Transfer (in the MRP 2 view of the R/3
material master record), means that the material has to be procured externally from another plant (supplying plant) or transferred from another plant.
To also be able to perform stock transfers for this material in the SAP APO system, there has to be a transportation lane from the supplying plant to the receiving
plant. If you have transferred a material with this special procurement type from the SAP R/3 system, the SAP APO system automatically creates a
corresponding transportation lane from the supplying plant to the receiving plant for the supplying plant (from the special procurement type) and material/plant
combination. The transportation lane is given the creation indicator S for special procurement.

When the material master record is transferred from the SAP R/3 system to the SAP APO system, if there is already a manually created
transportation lane with exactly the same supplying plant and receiving plant combination, this is kept and no new transportation lane is created.
Change of Supplying Plant in the Special Procurement Type
In the SAP R/3 system, if you have changed the supplying plant in the special procurement type, the SAP APO system creates a new transportation lane for the
new supplying plant (from special procurement type) and material/plant combination. The already existing transportation lane and now invalid combination
between supplying plant and receiving plant in the R/3 system is locked for orders in the SAP APO system. This can be recognized by the lock indicator X that
is set by the system.
Removal of Special Procurement Type from the Material Master Record
If you have removed the special procurement type from the material master record in the SAP R/3 system, the SAP APO system locks the already created
transportation lane so that it cannot be used in orders.
Inclusion in Source Determination
If transportation lanes (that were generated or manually created when purchasing data was transferred from the SAP R/3 system) already exist in the SAP APO
system, the SAP APO system takes these transportation lanes into account when determining sources of supply. In this instance, the transportation lanes that
were automatically generated from the SAP R/3 material master are not taken into account.

PUBLIC
2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 112 of 120

Activities
You can display and edit automatically created transportation lanes by choosing this SAP Easy Access menu path: Master Data -> Transportation Lanes .
You can go directly from the transportation lane to its associated external procurement relationship by choosing Goto -> External Procurement Rel.
You can go directly from the transportation lane to its associated sales scheduling agreement by choosing Goto -> Sales Scheduling Agreements.

!--a11y-->

Creating Transportation Lanes


Use
A transportation lane is a direct link between two locations. You use transportation lanes to source and transport products between the two locations. Each lane is
defined by its source and destination locations, depending on the direction of traffic, and is assigned products to be transported along the route. Each lane is also
assigned available means of transport.

Prerequisites
Create and assign locations to the model.

Procedure
To create a lane directly on the map in the Supply Chain Engineer, follow this procedure:
1.
2.
3.
4.

Go to the SAP Easy Access menu and access your supply chain model in Change mode.
From the map menu bar, select the Transportation Lane toggle.
Select the source location on the map.
Position your mouse over the source location, choose the left-hand mouse button, hold, and go to the destination location. Release the mouse button.
The Create transportation lane screen is displayed.
5. Choose the Header Data button. The detail view appears on the right. The General data section is populated with the names of the source and destination
locations.
6. Enter a description and transportation planner (optional).
7. Maintain the procurement options and means of transport for the lane as described in the Maintaining Transportation Lanes topic.
To create a lane as a stand-alone transaction:
1.
2.
3.
4.
5.

From the SAP Easy Access menu, choose Master Data Transportation Lanes .
Enter the model name.
Enter the source and destination locations.
Choose the Create icon.
Continue as described in steps 5 and 6 above.

!--a11y-->

1.7.3 Transportation Lane Maintenance Screen


Use
In this screen you can:
define product procurement for a transportation lane
define transportation methods for a transportation lane
define product-specific assignment of transportation methods
assign carriers to a transportation method
launch a query to view all assignments valid for a specific lane

Structure
The Transportation lane maintenance screen consists of a header control and several tables, plus an optional detail view for maintenance.

PUBLIC
2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 113 of 120

Transportation Lane Maintenance Screen


Header controls

Tables

Header data
Product-specific transportation methods
External carrier assignment
Lane overview
Transportation lane maintenance consists of 4 parts. The details are displayed
in the tables that appear in this screen. Each table has its own controls with
standard functionality. The tables include:
product procurement
transportation methods
product-specific transportation methods OR external carrier assignment
To save space, these two tables replace each other. You can toggle back and forth
between them using the header icons.

lane overview (appears only when icon is activated)


Detail view

You can open the detail view of a table in the following ways:
click on the Create icon in the table control header
double click on a selected row in the table
select a row and click on the Detail icon in the table control header
Close the detail view using one of the icons at the top of the screen:
close screen (without copying data)
copy data (copy data into the maintenance table on the left)
copy and close (copy data into the maintenance table on the left and
close the parameter maintenance screen)

!--a11y-->

1.7.4 Defining Product Procurement


Use
Use this procedure to define the parameters for the procurement of products. The procurement parameters include:

Validity period
Minimum and maximum lot sizes
Purchase costs of a unit
Priorities
Cost function
Procurement method

Prerequisite
Create transportation lanes
Maintain product master data
Assign products to location

PUBLIC
2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 114 of 120

Procedure
1. From the SAP Easy Access menu, choose Master Data Transportation Lanes . Enter the model name, the source location, and the destination location of
the transportation lane for which you want to maintain product procurement. OR choose a lane in the map display of the Supply Chain Engineer in Change
mode and open (or double-click on) the context menu.
2. Choose Edit.
The Change Transportation Lane screen appears.
3. Choose the Create icon in the Product Procurement table header for new product procurements OR choose the line containing the product you want to
maintain, and double-click on it.
The Product Procurement detail view appears on the right.
4. Maintain the following parameters:

When you choose the Create icon, you have three options in the right-hand screen:

Choose a single product via the standard selection view.


Select a product group
This option is displayed only if you have defined at least one product group in
Customizing for the product master.

Select all products


Mass selection for multiple entries
Validity

Enter the start and end date of the period for this product procurement

Lot sizes

Enter the minimum and maximum lot sizes. If you do not make an entry here, the
product procurement covers all lot sizes.

Procurement costs

Enter the product procurement costs per base unit at the procurement point.

Priority

Define the procurement and distribution priorities.

Cost function

Choose a cost function from the input help .

Lock indicator

Set this indicator if you want to lock (block) the source for orders.

Form of procurement

Choose the form of procurement :

Standard
Subcontracting
Consignment
Assign procurement relationship

This optional activity is possible only in the active model. It allows you to assign R/3
orders to products. Procurement relationships are maintained in the procurement
master data.

5. Use one of the icons at the top of the detail view to end this transaction:
Close (without copying data)
Adopt (the data is copied into the maintenance table on the left)
Adopt and close (the data is copied into the left-hand table and parameter maintenance is closed)
6. To delete an entry from the Product Procurement table, select the product and choose Delete .
7. To open the detail view, choose the Detail icon.

Result
If you chose a copy option in step 7, you can now maintain the product procurement attributes in the Product Procurement table.

!--a11y-->

Transportation Lanes for Product Groups


Use
You can define a transportation lane for one or more product groups of a product group type. This accelerates and simplifies the maintenance of transportation
lanes.

Prerequisites
You have defined at least one product group type in Customizing for the product master under Product Groups Define Product Group Types .
You have defined at least one product group for this product group type in Customizing for the product master under Product Groups Define Product
Groups .
You have set the Relevant to Transportation Lanes indicator for a product group type in Customizing for the product master under Product Groups Define
Product Group Types . This product group type is displayed on the maintenance screen for transportation lanes.
If you have not set this indicator, the system does not show the Product Group Type and Product Group fields on the maintenance screen for transportation
lanes.

PUBLIC
2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 115 of 120

Activities
Maintain a product group for a transportation lane on the maintenance screen for transportation lanes. The transportation lane is automatically valid for all the
products of this product group.

!--a11y-->

1.7.5 Defining Means of Transport


Use
Use this procedure to define the parameters for means of transport.

Prerequisite
You created transportation lanes.
You have maintained the product master data.
You have created a means of transport in Customizing for the APO master data under Transportation Lane Create Means of Transport .

Procedure
1. From the SAP Easy Access menu, choose Master Data Transportation Lanes .
2. Enter a model name for the source and destination location of the transportation lane for which you want to maintain a means of transport.
3. Choose Edit.
The Change Transportation Lane screen appears.
4. In the Means of Transport table, choose Create OR choose the line containing the means of transport that you want to maintain by double-clicking on it.
The means of transport maintenance screen appears.
Maintain the following settings:
Validity

Enter the start and end date of the period to which this parameter relates.

Control Indicator

Set this indicator ...

All products

If you want this means of transport for which procurement has been defined to apply. If
this indicator is not set, the means of transport applies only to those products that have
been explicitly assigned to the means of transport.
For more information on the effects of setting this indicator, see also: Validity of Product
Procurement and Means of Transport

Aggregated planning

If the means of transport is valid for aggregated planning. For example, for Network
Design or Supply Network Planning

Detailed planning

For detailed planning in Transportation Planning and Vehicle Scheduling (TP/VS)

Fixed transportation duration

If you do not want this setting to be overwritten by automatic calculation (when


maintaining new transportation lanes, for instance)

Fixed transportation distance

If you do not want this setting to be overwritten by an automatic calculation of distance


factors when maintaining new transportation lanes.

Discrete means of transport

For means of transport optimization calculated in whole numbers (i.e. no half-loads on a


truck). Relevant to SNP only

Parameters

Maintain the following parameters:

Transportation calendar (APO customizing)


Duration of transportation
Additional retention period
Transportation costs per unit of measure

Resource
Means of transport costs
TLB profile
Transportation time rounding

Cost function

Note
The duration of transportation is specified in hours and minutes (for example: 12:22) and
refers to the net duration (i.e. the actual time in motion). Bucket-oriented planning
applications such as SNP calculate the gross duration using the following formula:
Net duration divided by average working time, or time in motion, for example the
number of hours driven in one day.
Gross duration of transportation refers to the time between arrival and departure.
Short text

Text describing the assignment of a means of transport to a transportation lane

Use one of the icons at the top of the maintenance view to exit this transaction:
Close (without copying data)
Adopt (the data is copied into the maintenance table on the left)
Adopt and Close (the data is copied into the left-hand table and parameter maintenance is closed)
5. To delete an entry from the Means of Transport table, select the means of transport and choose Delete .

PUBLIC
2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 116 of 120

Result
If you chose the Adopt option in step 5, you can now maintain the attributes directly in the Means of Transport table.

!--a11y-->

Duration Time and Distance Determination for Means of Transport


Purpose
It is now possible to exactly calculate duration times and distances for means of transport within transportation lanes. Until now, the system used a straight line to
calculate the distance (that is, not taking roads or other transportation lanes into account) and an average speed to calculate the duration time.
By connecting the Geographic Information System (GIS) to the Internet Graphic Server (IGS), you can, depending on the GIS tool provider, calculate the duration
time and distance for each means of transport within a transportation lane (with exact road detail).

Prerequisites
You have installed the GIS tool and connected it to the IGS (see also:

Internet Graphics Service).

In Customizing, you have set usage of the GIS tool for these clients. For more information, see the my SAP SCM Implementation Guide (IMG), following this menu
path: Advanced Planning and Optimization Master Data Transportation Lane Set Usage of GIS Tool .
In Customizing, you have activated the IGS connection for the relevant means of transport. You have made the following entries: A low speed (for traveling in
towns, for instance), a medium speed (on country roads, for instance), and a high speed (on a highway, for instance). For more information, see the SAP APO
implementation guide (IMG), following this menu path: SAP Advanced Planner and Optimizer (SAP APO) Supply Chain Engineer (SCE) Maintain Means
of Transport .

The different speeds are transferred to the GIS tool automatically during the calculation. Note that if you have not entered anything in these fields,
the system will not be able to also calculate a duration time for you or will use a standard value for the duration time. When selecting the GIS tool,
you should make sure that it is also capable of managing three speeds.
To access the GIS data quickly when using generated transportation lanes (transportation zones), you have to make a preselection of this data in background
processing. To make this preselection, choose the following SAP menu path: Advanced Planning and Optimization Master Data Transportation Lane
Preselection of GIS Data . For more information, see transportation zones (below):

Process Flow
The system processes the general search sequence as follows:
1. If something has been selected already, that is processed.
2. For individual maintenance, if nothing has yet been selected, connection to the IGS is set up and the data is recalculated.
3. If the IGS does not exist or no duration time or distance has been calculated, the straight line distance is calculated (as the bird flies).
You can determine duration times and transportation lane distances as follows:
When individually maintaining a lane
By using mass maintenance
By maintaining transportation zones

Individual Lane Maintenance


1. Create a transportation lane or edit an existing transportation lane (see also: Creating Transportation Lanes).
2. Choose a means of transport in the transportation lane.
3. Choose Generate proposal .
If the GIS is connected and available, and you have activated the IGS for the means of transport concerned, the duration time and distance is recalculated. The
status in the Precision field changes to 0100 IGS Accuracy.

Mass Maintenance
It would be advisable to use mass maintenance if you want to calculate the duration time and distance of multiple transportation lanes between multiple locations.
1. Create multiple transportation lanes (see also: Creating Multiple Lanes).
2. When running mass maintenance, the system starts job SAP_TRM_UPD_TRDIDUPS.
The job then attempts to get the IGS to calculate the distances and duration times for all means of transport in the transportation lane.

Note that if the IGS connection fails, an error message is displayed in the job log and the system calculates the straight line distance.
If background processing is canceled, you can restart posting for the non-posted data. To do this, choose the following SAP menu path: Advanced
Planning and Optimization Master Data Transportation Lane Post GIS Data Retroactively .

Transportation Zones

PUBLIC
2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 117 of 120

Using the IGS to determine distances and duration times is very time-consuming. Therefore, if you are performing this type of calculation, you should be sure of
the following information:
Which transportation zones you want to process.
The locations between which you want to interactively create transportation lanes.
For more information about transportation zones, see Defining Transportation Zone Hierarchies.
1. Choose the following SAP menu path: Advanced Planning and Optimization Master Data Transportation Lane Preselection of GIS Data .
2. Enter the job name.
3. Use the following areas to restrict the values for the transportation lane:
Model/work area
Location
Hierarchy
4. Choose whether you want the selection to be performed with the following setting:
Existing transportation lane
Generated transportation lane

For this selection, restrict the value range exactly to connections for transportation lanes that are used interactively. Otherwise, the quantity
calculated could be too large.
5. Select the means of transport
6. Define the start date and time.
7. The system then generates the job.
You can find this job again using the start date and time that you specified.
If you wish to delete the preselected data again; because you have connected a different GIS tool for instance, choose the following SAP menu path: Advanced
Planning and Optimization Master Data Transportation Lane Reorganize Preselection .

!--a11y-->

Assigning Products to Means of Transport


Use
In this step you assign product(s) to a means of transport that has already been assigned to a transportation lane.

Prerequisites

You have created a transportation lane


You have assigned the product to both the source and destination locations
You have maintained the product procurement settings
You have maintained the means of transport settings

Procedure
1. Access the Transportation Lane Maintenance screen in Change mode.
2. Choose the Product Procurement table. In the Product Procurement table, select the product you want to assign to a means of transport by clicking in the
selection box at the beginning of the line. The entire row is highlighted.

3.
4.
5.
6.

Products can only be assigned individually or using the mass selection button. It is not possible to assign a means of transport to an All products
entry.
From the Product Procurement table header, choose the icon : Assign Transportation method to Product .
OR select a means of transport from the Means of Transport table and choose the Assign product to means of transport icon .
Choose the Create icon. The detail view for assigning products to means of transport appears on the right.
Maintain as described in the table below.
Use one of the icons at the top of the Quota Items maintenance screen to end this transaction:
Close the screen (without copying data)
Copy
Copy and close (the data is copied and the maintenance screen is closed)

Maintain the detail view


If you selected Product

Use the selection icon in the detail screen to choose a valid means of transport.

If you selected Means of Transport

Use the selection icon in the detail screen to choose a valid source for transportation.

Validity of product-specific means of transport

Results from the overlap between the validity dates for the product and the means of
transport

Restriction indicator for the means of transport

Set this indicator if the means of transport is not authorized for this product.
For more information about the effects of setting this indicator, see the topic: Validity of
Product Procurement and Means of Transport

Parameters

Set the following parameters:

Transportation costs for each base unit of measure


Consumption: To determine which part of a transportation resource is

PUBLIC
2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 118 of 120

reserved for a specific base unit of measure


Lot size profile
Stacking factor: To indicate how many pallets of this product can be stacked
on top of each other. If you make no entry, the system assumes the product
cannot be stacked.

Result
If you chose a copy option in step 6, the product or means of transport assignment appears in the table.

!--a11y-->

Assigning External Transportation Service Providers


Use
In this step, you assign external transportation service providers to means of transport assigned to a lane. For example, you could assign Logistics Company A
and Logistics Company B to the means of transport Truck.

Prerequisites
You have maintained transportation service providers in the location master.

Procedure
1. Access the Transportation Lane Maintenance screen in Change mode.
2. In the Means of Transpor t table, choose the means of transport to which you want to assign external transportation service providers. The entire row is
highlighted.
3. Choose the Assignment of Transportation Service Provider icon
The External Transportation Service Provider Assignment screen is displayed and replaces the lower table.
4. Choose the Create icon in the External Transportation Service Provider Assignment screen.
The detail screen for assigning transportation service providers is displayed on the right.
5. Maintain as described in the table below.
6. Use one of the icons at the top of the Quota Items maintenance screen to end this transaction:
Close the screen (without copying data)
Copy data (copy to the right-hand side of the external transportation service provider assignment screen)
Copy and close (the data is copied and the maintenance screen is closed)

Transportation service provider

Choose a transportation service provider or select one from the input help .

Parameters

Set the following parameters:

Transportation costs for each unit of measure


Transportation service provider costs per measure of distance
Priority
Business share (for example, 50%)

Result
If you chose a copy option in step 6, the transportation service provider assignment appears in the table.

!--a11y-->

1.7.9 Creating Multiple Lanes


Use
Mass maintenance of multiple transportation lanes allows you maintain large quantities of supply chain transportation data. This function is particularly useful if you
want to create lanes between multiple source and destination locations; for example, between selected plants and customers.

Prerequisites

PUBLIC
2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 119 of 120

Existing lanes to copy

Procedure
To create multiple lanes in the Supply Chain Engineer, you simply copy an existing lane to use as a template for the new ones.
1. Access your model in the Supply Chain Engineer in Change mode. Open the Transportation Lane tab page in the left-hand panel.
2. Use the right-hand mouse button on the tree header and choose: Transportation lanes
3. From the context menu, choose Mass Generation .
The Mass Creation of Transportation Lanes screen is displayed.
To create multiple lanes as a stand-alone transaction, from the SAP Easy Access menu, choose Master Data Mass Creation of Transportation Lanes.
1.
2.
3.
4.

Enter the source location and destination locations of the lane you want to use as a template.
Enter the source and destination locations for the new lanes. You can also enter a range of locations. See example below.
Maintain any other applicable selection criteria such as location type, maximum distance, or minimum distance.
Choose Execute.

Result
The system creates new lanes between all the specified locations. Each new lane is an exact copy of the template, thus individual maintenance may be required.
However, product procurement entries are only copied if the product exists at both locations. In order to maintain the settings for product procurement and means of
transport, see Transportation Lane Maintenance.

If the lanes are created in the stand-alone transaction, they are saved directly to the database and appear in the model the next time the Supply
Chain Engineer is accessed. If the lanes are created in the Supply Chain Engineer, they are only saved to the database when the model itself is
saved.

Existing lanes are NOT overwritten.

Example
Creating Multiple Lanes
Model name:

Model X

Copy from:

Source location A
Destination location B

Create lanes for:


Source locations

All plants

Destination locations:

All distribution centers

Minimum distance:

100 km

Maximum distance:

1000 km

The system creates lanes between all the plants in the specified region and all distribution centers that are more than 100 km and less than 1000 km away. The
new lanes are replicas of transportation lane AB in model X.

PUBLIC
2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 120 of 120