Supply Network Planning

Advanced Planning and optimizer Supply Network Planning
Supply Network Planning

APO Supply Network Planning (SNP) integrates purchasing, manufacturing, distribution, and transportation so that
comprehensive tactical planning and sourcing decisions can be simulated and implemented on the basis of a single, global
consistent model Supply Network Planning uses advanced optimi!ation techni"ues, based on constraints and penalties, to
plan product flow along the supply chain #he result is optimal purchasing, production, and distribution decisions$ reduced
order fulfillment times and inventory levels$ and improved customer service
Starting from a demand plan, Supply Network Planning determines a permissible short% to medium%term plan for fulfilling the
estimated sales volumes #his plan covers both the "uantities that must be transported between two locations (for e&ample,
distribution centre to customer or production plant to distribution center), and the "uantities to be produced and procured
'hen making a recommendation, Supply Network Planning compares all logistical activities to the available capacity
#he (eployment function determines how and when inventory should be deployed to distribution centers, customers, and
vendor%managed inventory accounts )t produces optimi!ed distribution plans based on constraints (such as transportation
capacities) and business rules (such as minimum cost approach, or replenishment strategies)
#he #ransport *oad +uilder (#*+) function ma&imi!es transport capacities by optimi!ing load building
)n addition, the seamless integration with APO (emand Planning supports an efficient S,OP process
Integration with Other APO Applications
To... Do this... Other Information
Set up the Supply -hain
.odel
/se the Supply -hain
0ngineer (S-0)
)n the S-0, you assign the locations, products, resources, and
PP.s to a model 1ou then add transportation lanes to link supply
to demand locations, allocate products to the transportation lanes,
and maintain "uota arrangements
.ake the unconstrained
forecast available in
2elease the (emand
Plan to Supply
Network Planning and
vice versa
#he supply chain planner can then plan resources based on a full
and reliable picture of demand, and, likewise, the demand planner
can later monitor where ad3ustments to the demand plan have
been necessary due to production, distribution and other
constraints
.ake the Supply Network
Plan available to PP4(S
-onvert the SNP
orders into PP4(S
orders
)n PP4(S, production planning is synchroni!ed with e&ecution to
resolve all constraints and bottlenecks and create a viable
production plan
Features
Supply Network Planning is used to calculate "uantities to be delivered to a location in order to match customer demand and
maintain the desired service level Supply Network Planning includes both heuristics and mathematical optimi!ation methods
to ensure that demand is covered and transportation, production, and warehousing resources are operating within the
specified capacities
#he interactive planning desktop makes it possible to visuali!e and interactively modify planning figures 1ou can present all
key indicators graphically #he system processes any changes directly via live -ache
Supply Network Planning Process
1ou use Supply Network Planning (SNP) to model your entire supply network including all associated constraints 1ou can
use this model to synchroni!e activities and plan the flow of material along the supply chain #his allows you to create
feasible plans for purchasing, manufacturing, inventory, and transportation, and to closely match supply and demand
Process
#he following diagram shows the SNP cycle and the integration of SNP with the other components of SAP APO
#he se"uence of the process steps described here is generally the se"uence in which you should carry out the cycle
5owever, you may need to repeat certain steps or to proceed in a different order Also, not all activities are mandatory
Page 1 of 251
Planning Area Administration
#ake all the necessary steps to set up your planning area #he planning area is the basis for all activities in SNP )t is a
collection of parameters that define the scope of all planning tasks
SAP APO aster Data Setup
.aster data is a crucial aspect of the SNP component in SAP APO 1ou have to configure this master data very
carefully to achieve satisfactory results SNP master data includes information about locations, products, resources,
production process models (PP.s) or production data structures (P(S), and transportation lanes
odel!"ersion #reation
+efore you set up the model in the Supply -hain 0ngineer (S-0), you have to create a model name and assign the
model to at least one version 1ou can assign the model to several different versions for simulation purposes #he
version is also used for releasing the demand plan (final forecast) to SNP and for releasing the supply network plan to
(emand Planning
Supply #hain odel Setup
1ou set up the supply chain model for SNP in S-0 #here you assign the locations, products, resources, and PP.s or
P(S to a model 1ou then add transportation lanes to link supply locations to demand locations, allocate products to the
transportation lanes, and define "uota arrangements
$elease Forecast Data to SNP
1ou release forecast data to SNP by first loading the data in a planning area in demand planning ((P) and then
releasing it, or by directly releasing it from an )nfo Provider #he data is often unconstrained by any production or
distribution restrictions 0ither the demand planner or the SNP planner can e&ecute this step
Page 2 of 251
Definition of Planning ethod and Profile Settings
1ou choose whether you want to use optimi!ation%based planning, heuristic%based planning, or supply and demand
propagation as your planning method 1ou also decide if you want to perform safety stock planning before the Supply
Network Planning run 1ou then make the settings in the appropriate profiles for each of the methods re"uiring settings
1ou can still change these profiles during planning for simulation purposes 1ou may need to define additional master
data specifically for the method you are using
Supply Network Planning $un
1ou perform the planning run once you have chosen the method and carried out the prere"uisite steps
#he result of a Supply Network Planning run using the heuristic, the optimi!er, supply and demand propagation, or
-apable%to%.atch is a medium%term production and distribution plan
Interacti%e Planning
After the SNP run, you review the plan in the interactive planning desktop )f you run heuristic%based planning, you can
also level capacities from the interactive planning table
$elease SNP Plan to DP
1ou release the final supply network plan back to (emand Planning ((P) to compare the demand plan (without
constraints) with the constraint%based supply network plan .a3or discrepancies between these two plans could trigger
re%forecasting, and, ultimately, re%planning 6or e&ample, you may want to release the supply network plan back to (P if
the capacity situation is not sufficient to fulfill demand created by a promotion and you need to make ad3ustments to the
promotion planning strategy
#on%erting SNP Orders into PP!DS Orders
#his is not part of the SNP process since it can only be done in Production Planning and (etailed Scheduling (PP4(S)
5owever, it is included in the cycle because this step is usually performed before running deployment and the #ransport
*oad +uilder
)n PP4(S, you convert SNP orders into PP4(S orders to make them available for Production Planning and (etailed
Scheduling
Production Planning and Detailed Scheduling &PP!DS'
#his is not part of the SNP process because it can only be run in PP4(S 5owever, it is included in the cycle because
Production Planning and (etailed Scheduling is usually run before deployment and the #ransport *oad +uilder, which
are both part of the Supply Network Planning application component
)n PP4(S, you create a viable production plan based on the planned orders generated in SNP
Deployment $un
After production planning is complete and the system knows what will actually be produced (this information is saved
automatically in live-ache), the deployment run generates deployment stock transfers
Transport (oad )uilding
#he #ransport *oad +uilding (#*+) run groups the deployment stock transfers resulting from the deployment run into
#*+ shipments 1ou can also manually create #*+ shipments for stock transfers that could not be taken into account
during the #*+ run due to specified constraints
Planning Area Administration
#he set up of the Supply Network Planning (SNP) system environment is integral to successful planning Planning area
administration is the first step in this setting%up process7
Prere*uisites
1ou have understood the differences between the different storage methods in Supply Network Planning and (emand
Planning, and know which functions are supported by which storage methods 6or more information, see (ata Storage in
Supply Network Planning and (emand Planning
1ou have understood the role and purpose of the following8
Key Figure
Characteristic
Master Planning Object Structure
Storage Buckets Profile
Planning Area
Planning +ook
Page 3 of 251
Note that the attribute ob3ect (navigation attribute for instance) is only used in (emand Planning 1ou cannot create
aggregate ob3ects yourself, as opposed to (emand Planning, where you can do this )f you create and activate your own
master planning ob3ect structure (see step five below), SNP aggregates are generated automatically
Process
1. 6or Supply Network Planning, SAP delivers pre%defined standard key figures and characteristics, which mean you,
do not have to create your own key figures and characteristics #he characteristics in master planning ob3ect structure
9ASNP+AS and key figures in the planning areas 9ASNP:;, 9ASNP:<, 9ASNP:=, or 9ASNP:> are displayed in
Administration of (emand Planning and Supply Network Planning (APO 0asy Access menu Supply Network
Planning 0nvironment -urrent Settings Administration of (emand Planning and Supply Network Planning) )f
you do not see these key figures and characteristics there, go to the A+AP 0ditor to create them in your system (APO
0asy Access .enu #ools A+AP4> 'orkbench (evelopment A+AP 0ditor) and run the program
4sapapo4ts?d?ob3ects?copy
)f the key figures that are delivered with the system are not sufficient for your purposes, you can create additional key
figures in the Administrator 'orkbench (from Administration of (emand Planning and Supply Network Planning, choose
Administrator 'orkbench and then #ools @ 0dit )nfo Ob3ects). )f the system asks you to choose between an APO key
figure and a +' key figure, choose APO key figure 'hen creating a key figure for "uantities, select Auantity and enter
the data type A/AN and the unit :+AS0?/O. or :/nit
2. 1ou create storage +ucket profiles from SNP -urrent Settings by choosing Periodicities for Planning Area 6or more
information, see Storage +uckets Profile
3. 1ou create planning +ucket profiles in -ustomi!ing from Supply Network Planning by choosing (efine planning
bucket profiles 6or more information, see Planning +uckets Profile
4. 1ou create the planning %ersions that you want to use for SNP and assign them to a supply chain model 6or more
information, see .odel4Bersion -reation
5. SNP comes with the standard master planning o+,ect structures 9ASNP+AS and 9ASNPSA (for scheduling
agreement processing) 1ou also have the option of creating your own master planning ob3ect structure 5owever, this
does not have any advantages over using the standard master planning ob3ect structures #o create a new master
planning ob3ect structure, from the SAP 0asy Access screen, choose Supply Network Planning 0nvironment
-urrent Settings @ Administration of (emand Planning and Supply Network Planning #hen, from the top left pull%down
menu Administration, choose Planning Ob3ect Structures, right%click the Planning Ob3ect Structures folder, and choose
-reate Planning Ob3ect Structure )f you select the SNP Planning indicator, the SNP standard characteristics are
adopted into the master planning ob3ect structure automatically
)t is not possible to use additional characteristics in SNP #he delivered standard characteristics mentioned above
should not be changed either )n particular, you are not permitted to add navigation attributes to characteristics, as SNP
does not support them (apart from the standard navigation attributes), which means that using navigation attributes
leads to problems
'hen you activate the master planning ob3ect structure, you are asked whether you want the SNP standard planning
level to be created -onfirm this to trigger generation of the SNP aggregates (that is, master data ob3ects such as
location product or resource) 1ou also still have the option of creating the SNP standard planning level at a later point in
Administration of (emand Planning and Supply Network Planning using the conte&t menu function from the master
planning ob3ect structure
6or more information, see .aster Planning Ob3ect Structure and ).C
6. SAP delivers the following standard planning areas for SNP8
9ASNP:; (time series%based)
9ASNP:< (order%based)
9ASNP:= (for scheduling agreement processing)
9ASNP:> (for optimi!ation%based planning with time%dependent restrictions)
9ASNP:D (for safety stock planning)
9AB.):= (for deployment heuristic with consideration of demands in the source location)
1ou can also create your own planning areas8 6rom the SAP 0asy Access screen, choose Supply Network Planning
0nvironment -urrent Settings @ Administration of (emand Planning and Supply Network Planning, and choose
Planning Areas from the pull%down menu Administration on the top left
#o create an order%based SNP planning area, you should copy an order%based SNP standard planning area #hat way
you can ensure that your own planning area contains the entire key figures with their necessary attributes re"uired in
SNP #o create a time%series%based SNP planning area, you should choose menu function 0dit @ SNP #ime Series
Ob3ect, which adds the standard SNP time series key figures to the planning area 1ou can also assign additional key
figures to your planning area to store data that is calculated by a macro, for e&ample Note that you should not make any
Page 4 of 251
settings for the additional key figures in the key figure details since these key figures would then be created in live-ache
time series ob3ects
6or more information, see Planning Area and ).C
7. 1ou set up your master data for SNP 6or more information, see .aster (ata for Supply Network Planning
8. 1ou initiali!e the planning area by right%clicking the planning area and choosing )nitiali!e Planning Bersion Note that
the conte&t menu function for initiali!ing is only called )nitiali!e Planning Bersion if no time series key figures are
included in the planning area )f at least one of these key figures e&ists in the planning area, the conte&t menu function is
called -reate time series ob3ects
)f you need to re%initiali!e a planning area after updating your master data or in order to e&tend the planning hori!on, you
do not need to de%initiali!e it first or delete the time series ob3ects #he system recogni!es new and deleted planning
ob3ects and updates accordingly
6. -reate planning +ooks and planning %iews 1ou can assign the planning books and planning views to individual
users 6or more information, see Planning +ook
SNP provides the following standard planning books and data views for the different types of planning 6or SNP, we
recommend that you use these standard%planning books )f you need to create additional planning books, you should
use the standard books as templates
9ASNP9> ()nteractive Supply Network Planning and Transport Load Builder (TLB)) - #his planning book offers the
standard functions for running interactive Supply Netork Planning and the interactive !ransport "oa# Buil#er
9ASOP (Sales , Operations Planning (SOP)) % 1ou use this planning book to run SNP planning method supply
an# #e$an# propagation
9A(2P ((istribution 2esource Planning ((2P)) E #his user interface is almost identical to the interactive Supply
Network Planning interface, the only difference being that here it is also possible to display distribution receipts and
issues
9AB.) ()nteractive B.)) % )n addition to the typical SNP data that you can display, you can also display the values
for your B.) receipts and demands (planned, confirmed, and #*+%confirmed)
9ASA (interactive scheduling agreements) E 1ou use this planning book to display and change all data that is
relevant for sche#uling agree$ent processing
9ASNPACC2 (Aggregated Planning) E 1ou use this planning book to perform aggregate# planning and
planning ith aggregate# resources
9ASNP?PS (product interchangeability) E 1ou use this planning book if you want to consider pro#uct
interchangeability when planning
9A#SOP# E 1ou use this planning book to define ti$e%base# constraints for optimi!ation%based planning
9ASNP?SSP E 1ou must use this planning book (or one based on it) if you want to apply certain stan#ar# safety
stock planning methods 1ou can also use this book for e&ten#e# safety stock planning
9(2P?6SS E 1ou can use this planning book (or one based on it) if you want the deployment heuristic to also
consider customer demands or planned independent demands in the source location 6or more information, see
-onsideration of (emands in the Source *ocation
aster Planning O+,ect Structure
Definition
A master planning ob3ect structure contains plannable characteristics for one or more planning areas )n (emand Planning,
the characteristics can be either standard characteristics and4or ones that you have created yourself in the Administrator
'orkbench -haracteristics determine the levels on which you can plan and save data Specific characteristics are re"uired
for Supply Network Planning, -haracteristics%+ased 6orecasting and forecasting of dependent demand$ these characteristics
can be included on demand in the master planning ob3ect structure
#he use of additional characteristics for Supply Network Planning is not supported 6or an e&ample of a master planning
ob3ect structure with the correct characteristics for Supply Network Planning, see 9ASNP+AS
#he master planning ob3ects structure is the structure on which all other planning ob3ect structures are based Other planning
ob3ect structures are aggregates and standard SNP planning levels
A master planning ob3ect structure forms part of the definition of a planning area #he e&istence of a master planning ob3ect
structure is therefore a prere"uisite for being able to create a planning area
Integration
Page 5 of 251
+efore you can start planning, that is entering data for key figures$ you must have created characteristic combinations 1ou
do this for each master planning ob3ect structure
-orking with aster Planning O+,ect Structures
.aster planning ob3ect structures are prere"uisites for creating planning areas in Supply and (emand Planning
)n (emand planning you can assign any characteristics that e&ist in the system to the master planning ob3ect structure
#he following applications have fi&ed sets of standard characteristics8
-haracteristic%based forecasting
6orecasting with bills of material
Prere*uisites
1ou have created the characteristics with which you wish to work
Procedure
#o edit master planning ob3ect structures you work in Supply and (emand Planning Administration, which you access by
choosing (emand Planning4Supply Network Planning 0nvironment -urrent Settings Administration of (emand
Planning and Supply Network Planning
)n S,(P Administration you can edit8
Planning areas
.aster planning ob3ect structures
#o edit master planning ob3ect structures choose Planning ob3ect structures on the selection button (top left of the
screen)
#reating aster Planning O+,ect Structures
'( -hoose -reate master planning ob3ect structure from the conte&t menu
)( On the dialog bo& that appears enter a name for the new master planning ob3ect structure and choose #he
-onfigure Planning Ob3ect Structure screen appears
= 0nter a descriptive te&t for the master planning ob3ect structure
> 1ou now assign characteristics from the table on the right of the screen )f the master planning ob3ect structure is for
use in one of the applications listed above in the /se section, simply select the relevant indicator #he standard
characteristics are transferred automatically Otherwise select the characteristics that you want to use and then choose
Similarly you can choose to remove characteristics from the master planning ob3ect structure
*( 1ou can also assign dimensions to the characteristics in your master planning ob3ect structure (imensions here are
similar to dimensions in )nfo-ubes and are used to improve performance #o assign dimensions use the pull%down bo&
in the dimension ( ) column of the left hand table 1ou can add further dimensions by choosing the Add button at
the bottom of the screen
F )f you want to use other characteristics for product and location than 9A.A#N2 and 9A*O-NO, you must specify these
characteristics in the master planning ob3ect structure )n general you should use the two SAP characteristics as the
basis for the new characteristics #he main reason for changing these characteristics is to be able to use navigational
attributes in (emand Planning without causing problems afterwards in SNP (SNP does not support navigational
attributes) #o assign the product 4 location characteristics in the master planning ob3ect structure choose 0dit Assign
prod 4loc 0nter the relevant characteristics in the dialog bo& that appears
G Save your master planning ob3ect structure
#hanging Planning O+,ect Structures
SAP recommends that you do not change master planning ob3ect structures that have been activated and that are in use
in planning books
#o remove a characteristic from a master planning ob3ect structure you must first deactivate the structure
'hen you deactivate a master planning ob3ect structure, all characteristic value combinations are deleted and the
e&isting live-ache time series ob3ects become inconsistent
Acti%ating!Deacti%ating aster Planning O+,ect Structures
+efore you can work with a master planning ob3ect structure (for e&ample create characteristics combinations or assign them
to a planning area) you must activate it
1ou can do this either8
Page 6 of 251
6rom the planning ob3ect structure workspace in S,(P Administration by selecting the master planning ob3ect structure
and then choosing Activate or (eactivate from the conte&t menu
On the -onfigure Planning Ob3ect Structure screen by choosing to activate or to deactivate
2ead the cautions above before deactivating master planning ob3ect structures
Storage )uckets Profile
#here are two kinds of time bucket profiles8 one is used for storing data (the storage buckets profile), and the other for
planning the data (the planning buckets profile)
A storage buckets profile defines the time buckets in which data based on a given planning area is saved in (emand
Planning or Supply Network Planning
)n a storage buckets profile, you specify8
One or more periodicities in which you wish the data to be saved
#he hori!on during which the profile is valid
1ou can also include a time stream in storage bucket profile 1ou use time streams to incorporate factory calendars and
other planning calendars in (emand Planning 1ou can thus specify which days are workdays and which days are holidays
1ou define time streams in -ustomi!ing under APO H .aster (ata -alendar .aintain Planning -alendar (#ime
Stream) 2efer to the implementation guide ().C) before editing time streams
1ou assign the time stream to the storage bucket profile in the relevant field at the bottom of the screen
1ou select the periodicities month and week in the storage buckets profile 1ou do not enter a time stream (ata for the
months of Iune and Iuly <::; is stored in the following buckets, also known as technical periods

Time span Num+er of days
6riday through Sunday, Iune ;%= = days
.onday through Sunday, Iune >%;: G days
.onday through Sunday, Iune ;;%;G G days
.onday through Sunday, Iune ;J%<> G days
.onday through Saturday, Iune <D%=: F days
Sunday, Iuly ; ; days
.onday through Sunday, Iuly <%J G days
.onday through Sunday, Iuly 9%;D G days
.onday through Sunday, Iuly ;F%<< G days
.onday through Sunday, Iuly <=%<9 G days
.onday and #uesday, Iuly =:%=; < days
#he definition procedure for storage bucket profiles is the same for (emand Planning and Supply Network Planning
)nclude in the storage buckets profile only the periodicities you need because the technical periods take up storage space
On the other hand, you must include all the periodicities in which you intend to plan 6or e&ample, if you intend to plan in
months, you must include the periodicity month in the storage buckets profile
1ou need a storage buckets profile before you can create a planning area
#he storage buckets profile can be used for the release to SNP 6or more information, see +elease of the ,e$an# Plan to
SNP
#he way data is saved is further defined by the way you customi!e the #alculation type and Time.+ased disaggregation
in the planning area 6or more information, see Aggregation an# ,isaggregation and the 6; 5elp for these fields
#o define the buckets in which data is displayed and planned in interactive planning, create a planning buckets profile 6or
more information, see Planning +uckets Profile
1ou maintain storage bucket profiles in -ustomi!ing under Supply -hain Planning (emand Planning +asic Settings
(efine Storage +ucket Profile
Once a storage buckets profile is in use, it is not possible to change it )t is therefore sensible to specify a relatively long
hori!on Since the storage bucket profile does not take up any room in live-ache, this does not affect performance
Page 7 of 251
Planning )uckets Profile
)nformation, which is incorporated into the definition of the past or future time hori!on of demand planning #he planning
buckets profile defines the following8
'hich time buckets are used for planning
5ow many periods of the individual time units are used
#he se"uence in which the time periods with the various time units appear in the planning table
/se
1ou can plan in monthly, weekly, daily or (combined with fiscal year variants) self%defined periods
'hen you create a planning buckets profile, only use the periodicities or a subset of the periodicities that are also
defined in the storage buckets profiles (see storage buckets profiles) on which the planning area is based )n a planning
buckets profile, do not include a periodicity that is not in the storage buckets profile
1ou can have multiple planning buckets profiles, and therefore multiple planning hori!ons, for one planning book #he
planning buckets profile is attached to the data view within the planning book 1ou could have three data views for three
users, for e&ample, where a different planning buckets profile is valid for each view8 .arketing plans in months, sales
plans in months and weeks, and logistics plans in weeks and days
#o switch to a different planning buckets profile in interactive planning, you open the planning book wi!ard by changing
to (esign mode and choosing the -hange Planning +ook button On the (ata Biew tab page, enter a name and
description for the new view as well as the re"uired time bucket profiles and any other necessary data
)f you specify a historical planning hori!on in the data view, the first historical time bucket starts on the day before the
future planning hori!on start date #he second historical period begins further back in the past, and so on )f you plan in
weeks, the first day of the week is always .onday
)f you plan in weeks and the planning hori!on start date as specified in the data view of the planning book is not a
.onday, the first week of the planning hori!on is predated to the previous .onday 6or e&ample, if the planning hori!on
starts date as specified in the planning book is November ;, <::; (a #hursday), the first week of the planning hori!on
begins on October <9, <::; (a .onday)
)f the planning buckets profile contains smaller and larger time buckets, for e&ample weeks and months, the smaller time
buckets take precedence if any conflict arises )f, for instance, you have specified that the first month is to be planned in
weeks and the month does not start or end on a .onday, the system creates D time buckets of a weekKs duration 6or
e&ample, you start planning on Ianuary :;, <::; and specify that the first month (Ianuary) is to be planned in weeks
#he first D time buckets from Ianuary ; to 6ebruary > are in weeks #he first month bucket is shortened and is from
6ebruary D through 6ebruary <J
)f you forecast using mass processing 3obs, the length of the planning hori!on is a vital prere"uisite for being able to
save corrected history and the corrected forecast #he historical planning hori!on in the planning book must include the
historical forecast hori!on in the master forecast profile )t may also go further back into the past than the historical
forecast hori!on in the master forecast profile )t must not be shorter than in the master forecast profile Similarly, the
future%planning hori!on in the planning book must include the future forecast hori!on that is defined in the master
forecast profile )t may also e&tend further into the future than the future forecast hori!on in the master forecast profile )t
must not be shorter than in the master forecast profile #his restriction is necessary for performance reasons )t does not
apply if you forecast in interactive demand planning
#o read the data for the online release of the demand plan to SNP, you can use a planning buckets profile 6or more
information, see 2elease of the (emand Plan to SNP
#o release the demand plan to Supply Network Planning in daily buckets, you use a daily buckets profile, that is a
planning buckets profile containing daily buckets only #he use of a time buckets profile to release data to Supply
Network Planning is optional See also 2elease of the (emand Plan to SNP and 2elease from an )nfo Provider to
SNP
#o see the start and end dates of a period in a planning book or in the demand%planning table, double%click with the right
mouse button on the column heading )n this dialog bo&, you can also configure what information you want to see in the
column heading
#he buckets in which the data is stored in the system are known as storage +uckets or technical periods 1ou define
these technical periods when you create a storage buckets profile 6or information on how technical periods affect
disaggregation and rounding, see -&a$ple of ,isaggregation an# +oun#ing
Structure
After you have created the planning buckets profile, use it for the definition of the future planning hori!on and of the past
hori!on by entering them in a planning book8 one hori!on as future planning hori!on and one as past hori!on #he system
displays the hori!ons in interactive demand and supply planning starting with the smallest time bucket and finishing with the
Page 8 of 251
largest time bucket #he future hori!on starts with the smallest time bucket$ on the planning hori!on start date, and works
forwards, finishing with the largest time bucket #he past hori!on starts with the smallest time bucket the day before the start
of the future hori!on and works backwards, finishing with the largest time bucket8
01ample
Num+er of
periods
)asic
periodicit
y
Fiscal year %ariant of +asic
periodicity &optional'
Display
periodicity
Fiscal year %ariant of display
periodicity &optional'
< 1
; 1 .
< . '
)n the above e&ample, the time hori!on spans two years Of these two years, the first year is displayed in months #he first
two months of this year are displayed in weeks
#he first row defines the entire length of the time hori!on #he following rows define the different sections of the hori!on 1ou
make entries in the columns Number and (isplay periodicity #he content of the other columns is displayed automatically
when you press 0nter #o see e&actly which buckets will be displayed, choose Period list
2ey Figure
-ontains data that is represented as a numerical values either a "uantity or a monetary value 0&amples of key figures used
in (emand Planning are planned demand and actual sales history 0&amples of key figures used in Supply Network
Planning are production receipts and distribution receipts
1ou create key figures in the Administration 'orkbench, even if you only intend to use the key figures in *ive-ache -hoose
#ools, 0dit )nfo Ob3ects
)n APO, create APO key figures (not +' key figures)
#here are three types of key figure that are of interest for demand planning8
Auantity% /se this type for physical "uantities
Amount % #his type is amounts of money
Number % /se this type for numbers that do not have units of measure or currencies, such as factors
#he unit of measure and currency are always taken from the planning area
#here are different places in which a key figure can be stored 6or detailed information, see ,ata Storage in ,e$an# Planning
an# Supply Netork Planning
#haracteristic
A planning ob3ect such as a product, location, brand or region
#he master data of (emand Planning or Supply Network Planning encompasses the permitted values of the characteristics,
the characteristic values -haracteristic values are discrete names or numbers 6or e&ample, the characteristic KlocationK
could have the values *ondon, (elhi and New 1ork
#he characteristics used in (emand Planning are the same as those used in the SAP +usiness )nformation 'arehouse 1ou
create and edit characteristics in the Administration 'orkbench 6or more information, see )nfoOb3ect and -reating
)nfoOb3ect8 -haracteristics
SAP delivers several characteristics for use in SAP APO as +usiness -ontent #hese characteristics have the prefi& 3A as
opposed to 4 for other +' characteristics As SAP reserves the right to change these characteristics without notice, we
strongly recommend that you do not change them
-ompared to +' characteristics there are the following restrictions for the use of characteristics in (emand Planning
(ata types (A#S E (ate and #).S E #ime are not permissible
Similarly lowercase characteristic names are not permissible (1ou can of course use lowercase in the description fields
'e recommend that you do not use compound characteristics
Page 9 of 251
Planning Area
Planning areas are the central data structures for (emand Planning and Supply Network Planning
#he planning area is created as part of the (emand Planning4Supply Network Planning setup A planning book is based on a
planning area #he end user is aware of the planning book, not the planning area #he live-ache ob3ects in which data is
saved are based on the planning area, not the planning book
#he planning area specifies the following8
/nit of measure in which data is planned
-urrency in which data is planned (optional)
-urrency conversion type for viewing planning data in other currencies (optional)
Storage buckets profile that determines the buckets in which data is stored in this planning area
Aggregate levels on which data can be stored in addition to the lowest level of detail in order to enhance performance
Ley figures that are used in this planning area
Settings that determine how each key figure is disaggregated, aggregated, and saved
#he assignment of key figures to aggregates
Supply Network Planning comes with predefined planning areas 1ou can also define your own planning areas
1ou define planning areas in S,(P Administration
Structure
1ou assign a planning area to a master planning ob3ect structure, which in turn is assigned characteristics and aggregates,
which in turn are assigned characteristics and aggregates
1ou assign the key figures with which you want to work directly to the planning area

ass aintenance of Time Series 2ey Figures
)n Supply Network Planning (SNP), planning is generally based on order key figures 5owever, in some areas, you can also
use time series key figures, for defining time%dependent restrictions for optimi!ation%based planning, for instance
1ou can use this function to carry out mass maintenance of time series key figures, that is, you can select several key figures
and planning ob3ects, and either define the key figure values for individual periods, or for all periods
1ou can also use this function to process time series key figures for (emand Planning ((P)
Features
Selection of 2ey Figures
1ou can select the key figures for a particular planning area and planning time period, as well as for particular planning
ob3ects As when defining a planning book, you determine the planning time period and the period schedule lines, by
entering a planning buckets profile and a planning start date 1ou can also shorten the planning time period further by
entering a time period for maintenance
1ou select the planning ob3ects with the shuffler, as in interactive planning )n addition to the standard planning ob3ects,
in this function, you can also use the SNP aggregate APO E Product #ransport (a product on a transportation lane) #he
APO E PP.4P(S aggregate also includes the header product for the production process model (PP.) or the production
data structure (P(S) )f you select (isplay Selected Ob3ects,
Definition of 2ey Figure "alues
1ou can define key figure values for individual periods or for all periods #he options available are8
Set Ley 6igure Balues8 1ou can define the values for the individual periods 1ou can use the distribution function to
distribute values over periods, as in interactive planning
-hange Ley 6igures8 1ou can define or change the values for all periods in the planning time period 1ou can also
determine, for e&ample, that you want the system to add or subtract specific values or percentages to (or from) e&isting
values
Note that values saved earlier or in live-ache are not displayed, but are overwritten by the new values
Acti%ities
1. Select Advanced Planning and Optimi!ation @ Supply Network Planning @ 0nvironment @ .ass .aintenance of #ime
Series Ley 6igures from the SAP 0asy Access screen
2. Select the key figures as detailed above, and then select Set Ley 6igures or -hange Ley 6igures
Page 10 of 251
3. After entering the values, select (with tool tip Save) or (in the +ackground) )f you select the latter option, you
carry out the saving procedure as a background 3ob
Data Storage in Demand Planning and Supply Network Planning
)n (emand Planning and Supply Network Planning, you can store data in three ways8
)n live-ache time series ob3ects
)n live-ache orders
)n an )nfo-ube
0ach key figure in a planning area has its own storage method
Integration
Since planning areas for Supply Network Planning can contain only the standard SNP characteristics, you can only use a
3oint planning area for (emand Planning and Supply Network Planning, if demand planning in your company is done at
product level or at product and location level )f you want to do demand planning at other levels, such as brand or regional
level, you must have separate planning areas
Features
(i%e#ache Time Series O+,ects
#he data is stored in buckets, with no reference to orders #his storage method is suitable for tactical, aggregated planning )t
is the usual method for saving current (emand Planning data )t also supports the Sales , Operations Planning process )f
you save a key figure to live-ache time series ob3ects, you can use the following functions8
-onstraint propagation up and down stream (material constraints, capacity constraints, stock level constraints)
Aggregation and disaggregation
6reely definable macros
Product allocation checks
-haracteristics%+ased 6orecasting (-+6)
Single% and multilevel infinite heuristics
-apacity leveling
.)*P Optimi!er
-apable%to%.atch
(eployment
Bendor%.anaged )nventory (B.))
#here are a number of standard key figures that are saved to live-ache time series ob3ects which you can include in an SNP
planning area by choosing 0dit M SNP time series ob3ects
#he prere"uisites for saving a key figure to live-ache time series ob3ects are that8
1ou have created time series ob3ects for the planning area
'hen creating the planning area, you made no entries for the key figure in the fields )nfo-ube, -ategory or -ategory
Croup
'hen creating the planning area, any entry you made in the field Ley figure semantics is prefi&ed with #S (an entry in
this field is optional)
6or an e&ample of Sales , Operations Planning using the time series storage method, see planning book 3ASOP, planning
area 3ASNP45 (transaction 4SAPAPO4SNPSOP) in the standard APO system
(i%e#ache Orders
#he data is stored with reference to orders #his storage method is suitable for operative planning, such as in a classical
SNP setup )f you save a key figure to live-ache orders, you can use the following functions8
2eal%time integration with 24=
6ull pegging
6reely definable macros
Single% and multilevel infinite heuristics
-apacity leveling
.)*P Optimi!er
Page 11 of 251
-apable%to%.atch (-#.)
(eployment
One%step deployment
#ransport *oad +uilder (#*+)
Bendor%.anaged )nventory (B.))
#here are a number of standard key figures that are saved to live-ache orders which you can include in an SNP planning
area by choosing 0dit M SNP standard
#he prere"uisites for saving a key figure to live-ache orders are that8
1ou have created time series ob3ects for the planning area (even though you are saving to orders)
'hen creating the planning area, you either specified a -ategory or -ategory Croup or entered a Ley figure semantic
prefi&ed with *-
'hen creating the planning area, you made no entry for the key figure in the field )nfo-ube
6or an e&ample of Supply Network Planning using the orders storage method, see planning book 3ASNP36, planning area
3ASNP47 (transaction 4SAPAPO4SNP9>) in the standard APO system
Info#u+es
#he data is stored in an )nfo-ube in the Administrator 'orkbench #his storage method is suitable for data backups, old
planning data, and actual sales history )n (emand Planning, actual sales history is used to generate master data and as the
basis for forecasting
)n APO (emand Planning you can only read from )nfo-ubes if you have specified the )nfo-ube in planning area
configuration 6or details of how to save data to )nfo-ubes see 0&change of (ata +etween )nfo-ubes and Planning Areas
#o specify an )nfo-ube from which the key figure is read in all versions8
5. Select the planning area in S,(P Administration
7. -hoose -hange in the conte&t menu
8. On the Ley figs tab page choose (etails
6. Select the relevant key figure and enter the )nfo-ube in the relevant field
)t is possible to use different )nfo-ube for different versions -ontinue as above up to step = )n Step > do not enter an
)nfo-ube -hoose A dialog bo& appears, in which you enter the )nfo-ube for each version After you entered the
necessary information, choose to save the data and return to the previous screen 1ou can see that such data has been
entered by the icon
01tracting Data from a Planning Area
#here are two purposes for which you might follow this procedure8
6or ad hoc reporting for planning area data
#o save data persistently to the database
Procedure
5. Cenerate an e&port (ata Source for the planning area #o do so, proceed as follows8
a. On the SAP 0asy Access screen, choose (emand Planning 0nvironment Administration of (emand Planning
and Supply Network Planning
+. Select the planning area and, in the conte&t menu, choose -hange4(isplay
c. )n planning area maintenance, choose 0&tras Cenerate (ata Source
A dialog bo& appears in which you enter a name for the data source
d. -hoose 0&ecute
A screen with details for the data source appears
e. Specify the fields that you want to be able to select later for reporting purposes #his step enables you to limit a
"uery to specific ob3ects or ranges of ob3ects 1our selection here does not influence the fields that are included in
the e&port structure Select the Suppress field indicator for the fields ()nfoOb3ects) that you do not want to transfer
#he number of fields that you transfer directly affects performance #herefore, we recommend that you only
transfer those fields that you re"uire for reporting purposes in the )nfo-ube
Page 12 of 251
#he field for the planning version is selected by default$ you cannot deselect it #his means that you must enter
a planning version in the )nfoPackage later
f. .ake a note of the (ataSource name
g. -hoose Save
7. 2eplicate the (ataSource #o do so, right mouse click the source system and choose 2eplicate (ataSources in the
(ata 'arehousing 'orkbench )n this case, the source system is the system in which you are performing (emand
Planning 6or e&ample, if you are planning in the SAP S-. system, client ::<, the technical name of the source
system is APO-*N#::<
'hen the system messages at the bottom of your screen cease, a background 3ob is triggered -heck in the 3ob
overview that this 3ob has finished before proceeding to the ne&t step
8. )n the (ata 'arehousing 'orkbench, you are still in the source system view 2ight%click the source system and choose
(ataSources Overview in the conte&t menu
6. Assign an )nfoSource to the (ataSource8 #o do so, proceed as follows8
a. )n the (ataSource overview under (ata .arts, select the (ataSource and choose Assign )nfoSource from the
conte&t menu
+. )n the dialog bo&, choose -reate
c. )n the ne&t dialog bo&, enter a name and a short description for the )nfoSource
d. 'hen the )nfoSource has been created, choose 0nter
e. Answer the system prompt with 1es
#his saves the )nfoSource4(ataSource assignment
)f the above procedure is unsuccessful, use the following alternative8
Switch to the )nfoSource view
-reate an )nfoSource (right%click a suitable )nfoArea and choose -reate )nfoSource)
2ight%click the )nfoSource and choose Assign (ataSource from the conte&t menu
A dialog bo& appears with an overview of all (ataSources in the (ata .art, including the e&port (ataSources
you have generated yourself
Select the (ataSource you created in step ;
9. )n the (ata 'arehousing 'orkbench, branch to the )nfoSource view
:. 2ight%click the )nfoSource that you have 3ust created and choose -hange
#he screen in which you can specify the assignment of the communication structure to the transfer structure appears
1ou see the communication structure in the upper half of the screen and the transfer structure in the lower half Some
of the assignment information is proposed by the system 1ou must fill in the missing information
#his is another opportunity to remove superfluous )nfoOb3ects from the communication structure See also step ;
;. (efine the assignment of the communication structure to the transfer structure #o do so, proceed as follows8
a. )n the lower half of the screen, enter the source system and the (ataSource for the transfer structure
+. On the #ransfer Structure tab page, copy the ob3ects from the (ataSource to the transfer structure (from right to
left)
c. -lick the #ransfer 2ule tab page
d. -heck where the assignment of transfer structure fields to communication structure )nfoOb3ects is not proposed by
the system
e. 'here the assignment has not been proposed8
)nclude new )nfoOb3ects in the communication structure in the upper half of the screen
)n the lower half of the screen, select the new )nfoOb3ects in the communication structure on the left and copy
the )nfoOb3ects to the appropriate fields in the transfer structure on the right
f. -hoose Activate
<. )f you need an )nfo-ube to carry out reporting with a +) front end, create an SAP 2emote )nfo-ube, specifying the
)nfoSource that you created in step > as the )nfoSource, Otherwise, see the note below
3. Activate the SAP 2emote )nfo-ube
$esult
)n the SAP +usiness 0&plorer +rowser, you can now create "ueries based on this SAP 2emote )nfo-ube See also A#
.oc +eporting on ,ata in a Planning Area
Page 13 of 251
)f you want to copy planning area data to an )nfo-ube for backup purposes or to save old planning data, create a basic
)nfo-ube during step J (for e&ample, by running program 4SAPAPO4#S?PA20A?#O?)-/+0) and proceed as you would
when uploading data from an 02P system or a flat file
Tools for 01traction from Planning Areas
SAP provides a group of tools for checking and working with (ataSources and other ob3ects used in con3unction with
planning areas
.ost of the functions available here are also available in other transactions, in particular in the (ata 'arehousing
'orkbench and in Administration of (emand Planning and Supply Network Planning #he data e&traction functions
described here has been bundled together for ease of use
DataSource anagement
=enerate DataSource
1ou use this function to generate a (ataSource #his is the e&isting SAP APO function that you can also access from the
conte&t menu for a planning area under Cenerate 0&port (ataSource
1ou can only create one (ataSource for each basis planning ob3ect structure and each aggregate assigned to a planning
area
1ou can choose any characteristic to be used for selection purposes #he characteristic 9AB02S)ON for the planning
version is always used for selection and cannot therefore be changed here 1ou cannot use key figures or units for selection
purposes
1ou must enter the version in the selection when you call up the (ataSource Otherwise, the system issues an error
message
1ou use the Suppress field indicator to e&clude key figures from a (ataSource #hese key figures are not e&tracted
#his reduces the amount of data to be handled, and thus improves performance
6or performance reasons, we recommend that you only use e&port (ataSources for e&tracting data from live-ache 1ou can
e&tract key figures from an )nfo-ube directly by creating an e&port (ataSource in the (ata 'arehousing 'orkbench
6or technical reasons, e&tracting data from planning areas to )nfo-ubes using (ataSources is only possible with full uploads
5owever, you can use (ata Store ob3ects to simply update the changes 6or more information, see /p#ating 0nfoCubes /sing
,ata Store Objects
#hange!Display DataSource
#his function allows you to change or display a (ataSource using the same screen as above
#heck DataSource
#his function runs a consistency check on the selected (ataSource and displays a log if errors are found
$epair DataSource
#his function attempts to repair errors found in the above checks
Test DataSource
1ou can use this function to test data e&traction using the selected (ataSource
$estrictions
(o not use 6> help
#he system uses the internal representation of characteristic values #his means8
'hen entering numeric characteristic values, use leading !eros, if necessary
0nter dates in internal formal, that is, 1111..((, 1111.., 1111'', for e&ample
Assigning DataSources to InfoSource
#he system automatically suggests a name for the )nfoSource when you make the assignment in the (ata 'arehousing
'orkbench #he )nfoOb3ects from the (ataSource are then automatically assigned to the )nfoSource per default On the
dialog bo& that appears, the name is in the Applicant Proposal field and the corresponding indicator is selected by default )f
you want to use another name for the )nfoSource, choose others and then )n this case, some )nfoOb3ects may not be
transferred automatically from the (ataSource
#his function is only available for (ataSources that were created in release >: or after release =: SP <<, or after release
=; SP 9 )f the (ataSources were created before these releases, e&ecute the function -heck (ataSource and then the
function 2epair (ataSource as described above
"irtual Pro%ider anagement
1ou use these functions (ad hoc reporting) to check and test Birtual Providers
Page 14 of 251
Information A+out "irtual Pro%ider
#his function provides information about the selected Birtual Provider, such as the names of the ob3ects involved
((ataSource, )nfoSource, planning area, for e&ample), the initiali!ed versions, and the number of characteristic
combinations
"irtual Pro%ider #onsistency #heck
1ou can use this function to run a consistency check on the selected Birtual Provider #he system displays a log if errors are
found 6or e&ample, the system checks if the same )nfoOb3ects e&ist in the planning area and the Birtual Provider
Test "irtual Pro%ider Automatically
#his function chooses an e&isting characteristic combination and reads it from the planning area )t then checks for the same
characteristic combination in the Birtual Provider )f the characteristic combination e&ists in both ob3ects, it reads the data for
all key figures in one period from the planning area and the Birtual Provider )f the values of the individual key figures are the
same in the planning area and the Birtual Provider, the system completes the test successfully
A log is produced in which the various steps are documented 1ou can find details of most steps in the long te&ts
Start the $eport onitor
#his starts a +o& "uery in the SAP APO environment (does not use .icrosoft 0&cel) 1ou can use it to test "ueries for basic
)nfo-ubes and Birtual Providers Other functions are also available for testing "ueries
)asic #u+e anagement
1ou use this function to generate a +asic -ube based on a planning area 1ou can use +asic -ubes for backing up data and
for reporting purposes
#his function only generates the )nfo-ube )t does not generate other ob3ects re"uired for data e&traction, such as
(ataSources or )nfoSource Similarly, it does make any assignments
Acti%ities
#o access the tools described here, call the planning area maintenance #here, choose 0&tras @ (ata 0&traction #ools and
then one of the following functions8
#o call (ata Source management, choose (ataSource management
#o call Birtual Provider management, choose Ad%5oc reporting
!o generate a basic 0nfo Cube1 choose (ata backup
/pdating Info#u+es Directly
1ou can update an e&isting )nfo-ube directly from the planning area without (ata Store ob3ects #his results in better
performance
)f you use this procedure, the system deletes the contents of the )nfo-ube before it creates a backup of the planning
area
Prere*uisites
#he )nfo-ube, (ataSource, )nfoSource, and update rules already e&ist 6or information about how to create these ob3ects,
see -&tracting ,ata fro$ a Planning Area, ,P ,ata Mart, and the subordinate topics
Procedure
5. -reate an )nfoPackage for the )nfoSource #o do this, select the )nfoSource for the source system on the )nfoSource
screen of the (ata 'arehousing 'orkbench
7. Co to the (ata #argets tab page 5ere, the following methods are available for deleting data while adding new
information to the )nfo-ube8
#o delete all the data in the data target before uploading the current data, select the relevant data target and set
the (elete entire content of data target indicator
Since the system does not check the e&isting data before deleting, this is the "uicker method 5owever, data can
be lost if problems occur during the update
#o delete data selectively, click the icon in the Automatic loading ofNcolumn (#his icon is either or
depending on whether entries have already been made or not)
A dialog bo& appears in which you can restrict the selection conditions
8. Proceed with the update as usual
#he settings that you make in the )nfoPackage can be critical for performance 6or more information, see SAP
Note >J<>9>
Page 15 of 251
After your update process has run smoothly, update the data directly in the data target without using the Persistent
Staging Area (PSA) #his improves performance
/pdating Info#u+es /sing Data Store O+,ects
0&tracting data directly has the disadvantage that the complete data set is copied to the )nfo-ube at each update #he
following procedure allows you to update the data in an )nfo-ube without adding superfluous data
1ou can also use this procedure for uploading data from flat files
#he procedure that is described here using (ata Store ob3ects can be time consuming #herefore, we only recommend
that you use it if you re"uire delta functionality 6or most purposes, it is sufficient to delete the contents of the )nfo-ube
before conducting a full update 6or more information, see /p#ating 0nfoCubes ,irectly
Prere*uisites
1ou have generated an e&port (ataSource for the planning area (see -&tracting ,ata fro$ a Planning Area)
(o not create any update rules for an )nfo-ube that has an )nfoSource as the data source
Procedure
5. )f necessary, replicate the (ataSource #o do so, you can use the following options in the (ata 'arehousing
'orkbench8
Select the source system in the source system overview and choose 2eplicate (ataSources in the conte&t menu
#his replicates all data sources in the source system
Select the data source in the (ataSource overview and choose 2eplicate .etadata in the conte&t menu #his
replicates 3ust the one (ataSource
7. -reate an )nfoSource and assign the data source to it #o do so, choose your application component on the )nfoSource
page of the (ata 'arehousing 'orkbench )n the conte&t menu, choose -reate )nfoSource On the ne&t dialog bo&,
select #ransactional (ata Another dialog bo& appears 0nter a name and description for the new )nfoSource and
choose 0nter )n the tree, select the new )nfoSource )n the conte&t menu, choose Assign (ataSource On the dialog
bo& that appears, enter the source system A list of (ataSources appears Select the re"uired (ataSource -hoose
0nter
Alternatively you can remain in the (ataSource overview An icon indicates that no )nfoSource has been assigned
yet 0ither click the icon or choose Assign )nfoSource in the conte&t menu On the dialog bo& that appears, enter a
name for the )nfoSource -hoose On the ne&t dialog bo&, enter a description and choose -onfirm the following
dialog bo& 1ou can now maintain the )nfoSource
1ou can assign a (ataSource to one )nfoSource only
8. -reate a (ata Store ob3ect in the )nfoProvider overview of the (ata 'arehousing 'orkbench
a. 0nter a name and a short description )f re"uired, you can also specify a (ataStore ob3ect to use as a template
-hoose #he 0dit (ataStore Ob3ect dialog bo& appears
+. On the left%hand side of the screen, you can select )nfoOb3ects, for e&ample, )nfo-ubes or )nfoOb3ect-atalogs 1ou
can copy characteristics or key figures from these )nfoOb3ects to the (ataStore ob3ect 'e suggest that you select
either the )nfo-ube to which you want to copy the data, or the )nfoSource
c. -opy the characteristics to the key fields in the right%hand tree in the (ataStore ob3ect and copy the key figures to
the data fields )n both cases, use drag and drop 1ou might have to transfer the :20-O2(.O(0 )nfoOb3ect from
the +usiness -ontent
d. )n the Settings branch of the (ataStore tree, set the following indicators8
Set "uality status to KOLK automatically
Activate ,ataStore object #ata auto$atically
/pdate data targets from (ataStore ob3ect automatically
e. Activate the (ataStore ob3ect
For $ore infor$ation1 see ,ataStore Object(
6. -reate update rules for the (ataStore ob3ect
a. Select the (ataStore ob3ect in the data targets page ((ata 'arehousing 'orkbench)
+. -hoose Create up#ate rules from the conte&t menu #he Create /p#ate +ules screen appears
c. 0nter the )nfoSource that you created in step < -hoose 0dit the update rules as necessary
Activate the update rules by choosing
9. -reate update rules for the )nfo-ube as above, but with the (ataStore ob3ect as the data source
Page 16 of 251
:. -reate an )nfoPackage for the )nfoSource )n contrast to the normal procedure, on the Processing tab page1 set the
Only PSA an# /pdate subse"uently in data targetsin#icators( Start or sche#ule the #ata loa#( For $ore infor$ation1 see
/ploa# Process(
Planning )ook
A planning book determines the content and layout of the interactive planning screen
/se
1ou use planning books in Supply Network Planning (SNP) and (emand Planning ((P) #hey allow you to design the screen
to suit individual usersO planning tasks A planning book is based on a planning area #here is no restriction on the number of
planning books you can have for a planning area
'ithin a planning book, you can also define one or more views Biews allow you, for instance, to tailor the information
displayed to various users (for e&ample, displaying different key figures for different users)
Supply Network Planning comes with the following standard planning books8
9ASNP9> for traditional Supply Network Planning
9ASOP for Sales , Operations Planning (SOP)
9A(2P for (istribution 2esource Planning ((2P)
9AB.) for Bendor%.anaged )nventory
9ASA for scheduling agreement processing
9ASNPACC2 for aggregated planning and planning with aggregated resources
9ASNP?PS for planning that takes into account product interchangeability
9A#SOP# for optimi!ation%based planning that takes into account time%based constraints
9ASNP?SSP for safety stock planning
9A(2P?6SS for planning with the deployment heuristic with consideration of demands in the source location
'e recommend that you use the standard planning books for Supply Network Planning )f you need to create additional
planning books, you should use standard books as templates #o create your own planning books, from the SAP 0asy
Access menu, choose Supply Network Planning @ Planning @ )nteractive Supply Network Planning #hen choose the (esign
icon and -reate new planning book
)f you create additional planning books, you can define the following elements8
-haracteristics
Ley figures and other rows
6unctions and applications that can be accessed directly from this planning book
/ser%specific views for the planning book, including initial column, number of grids and accessibility of the view for other
users (there is no limit on the number of views you can have within one planning book)
1ou can use conte&t menus in interactive design mode to configure these and additional elements of the interactive planning
screen (such as the position of columns and rows, the use of colors and icons in rows, the visibility or not of the rows, the
appearance of the graphic, and macros)
Planning )ook aintenance
Supply Network Planning (SNP) offers a variety of stan#ar# planning books 2an# planning vies3 for the different planning
methods 5owever, you can also create your own planning books 'e recommend that you use the standard planning books
as templates when you create your own planning books
Prere*uisites
1ou have created a planning area
1ou have created a planning buckets profile
Process Flow
1. On the SAP APO -asy Access screen, choose ,e$an# Planning Planning 0nteractive ,e$an# Planning( On the
interactive desktop, choose ,esign and Planning Book
2. 1ou then work through the tab pages guided by the planning book wi!ard and choose -ontinue after entering the
relevant data on each tab page
a. Planning +ook tab page
Page 17 of 251
On the Planning +ook tab page, you give a longer description for the planning book, the planning area on which
the planning book is based, the SNP functions (for e&ample, Supply Network Planning, -apacity Planning, and so
on) to be included in your planning book, and, if you are also using (emand Planning, the views to which you can
navigate
+. Ley 6igures tab page
On the Ley 6igures tab page, you specify which key figures you want to use in this planning book #o add all key
figures from the planning area to the planning book, choose the Add all key figures icon below the planning area
window
#he planning areas you are using (such as 9ASNP:; or 9ASNP:<) determine which key figures are
transferred to your planning book
c. -haracteristics tab page
On the -haracteristics tab page, you specify which characteristics you want to use in this planning book 1ou can
add all characteristics to your planning book or choose individual characteristics only
d. Ley 6igure Attributes tab page
On the Ley 6igure Attribute stab page, you define the attributes of specific rows in the planning book 'hen you
create a planning book, this tab page is available in (isplay mode #he tab page is available in -hange mode
when you edit a planning book
On this tab page, you can also create au&iliary key figures that are not stored in the database but that can be
displayed in interactive planning 1ou can use au&iliary key figures with macros, for e&ample
1ou can also define that a key figure refers to a specific planning version #he implication of this is that you can
work with different versions of a key figure in the same planning book )f you carry out SNP planning with different
planning versions, you can compare the results in interactive SNP planning
)f you specify that the key figure refers to a variable planning version, you can select the planning version for the
key figure in interactive SNP planning
e. (ata Biew tab page
On the (ata Biew tab page, you create one or more data views for the planning book 1ou need at least one view
to use the planning book 1ou can have multiple views for multiple users within one planning book )n the data
view, you specify the planning hori!on
f. Ley 6igures tab page (after (ata Biew)
On the Ley figures tab page (after (ata Biew), you specify which key figures in the planning book the users of this
particular data view use
3. 'hen you have finished working through the tab pages and wish to save the planning book, choose Co$plete and
confirm any messages that may appear
Ad%anced acros
/se advanced macros to perform comple& calculations "uickly and easily
.acros are e&ecuted either directly by the user in interactive planning or automatically at a predefined point in time during a
background 3ob
#he definition of macros is optional
1ou do not have to write macros yourself Some stock level and daysK supply macros are also delivered with the standard
SNP planning books 1ou can create your own planning book for SNP using one of the e&isting books as a template, and
copy the standard macros to the new book
Integration
1ou create an advanced macro either when creating or chaning a planning book in -ustomi!ing, or in design mode of
interactive planning 1ou can define a macro either for an entire planning book or for a specific data view
Prere*uisites
1. 1ou have created a planning area
2. 1ou have created a planning buckets profile
3. 1ou have created a planning book with at least one data view
Features
1ou can8
-ontrol how macro steps are processed through control instructions and conditions
+uild a macro consisting of one or more steps
Page 18 of 251
-ontrol how macro results are calculated through control instructions and conditions
/se a wide range of functions and operators (see Operators and 6unctions in .acros)
(efine offsets so that, for e&ample, the result in one period is determined by a value in the previous period
2estrict the hori!on in which the macro is e&ecuted to a specific period or periods
'rite macro results to either a row, or a column, or a cell
'rite the results of one macro step to a row, column, cell or variable, and use them only in subse"uent iterations, macro
steps or macros
#rigger an alert in the Alert .onitor showing the outcome of a macro e&ecution
#o create authori!ations for the creation and e&ecution of macros, choose #ools Administration /ser .aintenance
2oles from the SAP 0asy Access menu 6or more details see Authori!ation in Supply Network and (emand Planning
acro )uilder Screen
'hen defining advanced macros, you work in a special desktop environment known as the .acro+uilder
#here are two methods of accessing the .acro+uilder8
6rom the SAP 0asy Access screen, choose (emand Planning @ 0nvironment @ -urrent Settings @ .acro 'orkbench 6or
more details, see .acro 'orkbench
6rom design mode of interactive demand planning, choose .acro+uilder PQ Planning +ook or .acro+uilder PQ (ata
Biew
Structure
#he .acro +uilder consists of the several screen areas8
Macro ele$ents in a tree on the top left
(epot with parked macros on the bottom left
Leep all macros that you are not currently editing in the depot #his improves the performance when starting the .acro
+uilder
(emand planning table (grid) in the top center
Processing area where you edit macros
.acro tree with the macro tools in the bottom center
Page 19 of 251
#o see the attributes of any item in the tree, double%click on the item
Standard macros on the top right
-lipboard on the bottom right
2esults area for semantic checks
Au&iliary table
#he last two screen areas are hidden when you open the .acro +uilder 1ou can make them visible by dragging the lower
edge of the processing area upwards Similarly you then drag the lower edge of the semantic check area upwards
6or more information on how to edit macros, see (efinition of .acros in the .acro +uilder
Ad%anced acro Structures
An advanced macro consists of one or more macro steps #o define the conditions under which individual macro steps are
carried out, you use control structures 0ach macro step consists of one or more calculations #o define these calculations in
the macro tree, you use calculation structures
Structure
A macro can comprise of up to > levels #he following figure shows a simple
0&ample8
5. .acro level
#his is the top level and consists of the macro name only
7. Step level
At this level you can enter either a step or a control structure A macro must contain at least one step A step contains a
calculation or series of calculation A step is also an iteration loop #he calculation or operation is repeated over a
predefined period, if you work with rows
8. 2esult level
At this level you specify the macro ob3ect to which the results of a calculation or operation is written #his can be a key
figure in the planning book, or an element in the au&iliary table that you use to store an intermediate result temporarily
At this level you can also enter control structures, action bo&es, documents, procedural messages, or alerts
6. Argument level
At this level you enter the calculations or operations Similarly conditions are defined at argument level, if the control
structure is entered at result level
#he following figure is a concrete e&ample of the structure above #he macro calculates the ad3usted forecast by adding
the manual ad3ustment to the sales forecast #his is done for the period of one year in the future
Page 20 of 251
#ontrol Structures
As mentioned above, you use control structures at either step level or result level )n the first case you can control structures
to decide which step to e&ecute depending on which conditions are satisfied
#he statements that are available here are based on the corresponding A+AP statements, such as )6, (O, -AS0, '5)*0
and are similar in most programming languages 6or further information see -ontrolling the Program 6low Not all A+AP
statements are supported in macro control structures
#here are more options when working at the step level than the result level 6or instance, you can use -AS0 '50N
structures to branch to different steps depending on the value of a variable or key figure
#he following is an e&ample of a macro that makes e&tensive use of control structures Note the level of the various
ob3ects 6or information on the functions used, see Functions for 0nfo Objects an# Planning Book
#alculation Structures
1ou use calculation structures not only to e&ecute calculations but also to carry out other actions in which a value is not
directly assigned to a key figure or variable 0&amples of such actions are8
#riggering an alert
(isplaying a message or dialog bo&
Sending an e%mail
-alculation structures always consist of at least one step
)n general a calculation step consists of a macro element at the result level followed by one or more elements at the
argument level A simple e&ample is the second graphic above
Page 21 of 251
/sing acro 0lements
#o define macros, use macro elements in combination with macro tools (see /sing Macro !ools) and drag,drop techni"ues
(see ,efinition of Macros in the MacroBuil#er)
Features
Icon 0lement Description
.acro
/sed in (emand Planning or Supply Network Planning (SNP) to carry out comple& or
fre"uent planning tasks "uickly and easily 1ou can e&ecute a macro in interactive
planning or as part of mass processing
+Ad)4/ser 0&it
.acro
A comple& macro used in (emand Planning or SNP and that you implement in A+AP
yourself 1ou can use this +usiness Add%)n (+Ad)) in a collective macro
Step
A macro step consists of one or more macro calculations or macro activities 6or each
macro step, you define how much iteration of the macro calculations or macro activities
are to be performed$ that is, the area of the table to which the macro
calculations4activities apply
#he se"uence of the macro calculations4activities in a step is not significant$ that is, a
calculation4activity cannot use the results of another calculation4activity within the same
iteration
-ontrol statement /sed together with a condition (see below) to control macro steps and calculations
-ondition
/sed for the definition of a logical condition that, together with a control instruction, is
used for macro steps and calculations
2ow
2ow in the table 1ou can assign the results of a calculation to a row (a results row) A
row can be used as an argument in a calculation A row can also be an argument in a
logical condition (an argument row) #he calculation is repeated for all the cells that lie
within the period defined for the step
-olumn
-olumn in the table 1ou can assign the results of a calculation to a column (a results
column) A column can be used as an argument in a calculation A column can also be
an argument in a logical condition (an argument column) As for rows, calculations are
repeated for all the cells in the column
-ell
-ell in the table 1ou can assign the results of a calculation to a cell (a results cell) A
cell can be used as an argument in a calculation A cell can also be an argument in a
logical condition (an argument cell)
Area
Several ad3acent cells in the table 1ou can assign the results of a calculation to an
area /se an area if the function of a macro step changes several cells in one iteration
6or e&ample, the function -P1 copies values from one area to another area, such as to
the au&iliary table )n the Rcopy toR area, you select only the top left cell of the area
before pasting Another use of areas is in mathematical operations, for e&ample where
a sum is formed over a range of cells or a ma&imum value is found
Au&iliary table
5olds data that is used subse"uently as part of the macro e&ecution /se the au&iliary
table to retain intermediary results for subse"uent calculations, or to collect data for
calculations
#he same elements are available in the au&iliary table as in the planning book table
#he system differentiates between a local au&iliary table and a global au&iliary table A
global au&iliary table is available in every macro book )f you do not set the (o Not
)nitiali!e Au&iliary #able indicator, the system uses a local au&iliary table for this macro
and you cannot access the global au&iliary table 1ou can use the global au&iliary table
if you set the indicator (o Not )nitiali!e Au&iliary #able
Balues in an au&iliary table cannot be saved #o save them, you must assign the
values to elements in the planning book table
Operator4function
Symboli!es8
; -omparative operators such as S or Q
< Arithmetic operators such as T or %
= A wide range of comple& functions that enable you to manipulate data in your
planning book #hese functions include several useful (P and SNP tools
See also Operators an# Functions in Macros
Page 22 of 251
Icon 0lement Description
6unction
1ou define functions for a rectangular section of the table #he section borders either
are fi&ed or move with each iteration
)f an RUR appears ne&t to a function in the macro tree, this means that the coordinates of
the section are fi&ed and are not relative to the iterations
Alert4status
1ou can use this element to send an alert to the Alert .onitor8 6or e&ample, you can
define an alert that is triggered if a specific condition is met (such as demand Q ;,:::
bo&es)
A status alert displays the status after the e&ecution of the macro Any previous
statuses are deleted from the Alert .onitor )f you run a macro twice, you see only the
latest alert
A message alert displays the current status after the e&ecution of the macro, and also
any previous statuses )f you run a macro twice, you see two alerts
1ou assign one of the following priorities to an alert8
; 0rror
< 'arning
= )nformation
1ou also assign a te&t to an alert #his is the te&t that appears in the Alert .onitor$ for
e&ample, .AP0 is too big8 , )n the Alert .onitor, the actual value of .AP0 appears in
place of the ,
1ou can assign the alerts that are generated in a planning book4 data view to another
planning book4data view #his is particularly useful when working with background
3obs
Process message
/sing this element, you can have the system issue a message 1ou define the
message te&t yourself )n interactive forecasting, an information message appears in a
dialog bo&, while warning, success and error messages appear at the bottom of the
screen )n mass processing, the messages are shown in the 3ob log
Note that if the system issues a procedural message with type V'arningO or V0rrorO, it
also terminates the macro #he background 3ob is not terminated Any changes that the
macro has already made are revoked
Action bo&
/se an action bo& if a macro function does not return a result or if you do not want to
assign the result of a macro function to an element of the planning table or au&iliary
table Always use the following functions in an action bo&8
; 50*P#A+?-*0A2
< O/#P/#?POP/P()
= 20PO2#?S/+.)#()
(ocument
/sing this element, you can have the system send an email #he recipients can be a
single internal user, a distribution list, or an e&ternal user #here are options for sending
to )nternet addresses, for sending regular or e&press mails, and for including the
demand planning table as an attachment to the email
)f you do not enter a recipient, a dialog bo& re"uesting the details appears when the
macro is run
1ou can also use a variable to create the address at runtime 0nter
*A1O/#BA2)A+*0 (Vvariable nameO) in the recipient field
/sing acro Tools
/se macro tools in combination with macro elements and drag,drop techni"ues to define macros 6or more information
about macro elements, see /sing Macro !ools and for more information about drag,drop techni"ues, see ,efinition of Macros
in the MacroBuil#er
Features
Sym+o
l
Tool /se
Attributes
(isplay or change an elementKs attributes
Select the element, whose attributes you want to change or display -lick on the icon
Page 23 of 251
Sym+o
l
Tool /se

A dialog bo& with the attributes of the selected element appears
#his has the same effect as double%clicking on the element or selecting it and choosing
Attributes from the conte&t menu
See also Macro Attributes
(elete
(elete an element in the macro tree #he deleted element is automatically copied to
the macro clipboard
-heck -heck the synta& of one macro or of all macros in the tree
Cenerate
Cenerate one macro or all macros 1ou must generate a macro before it can be
e&ecuted

Active4inactive
Activate4deactivate an element in the macro tree 6or e&ample, use this tool to check
individual sections of comple& macros by deactivating some sections and then
checking the remaining section(s)
-opy to macro
clipboard
-opy an element in the macro tree to the clipboard
Paste Paste the contents of the clipboard to the macro tree
/ndo /ndo the previous step 1ou can undo up to <: steps
2edo 2edo the step you have 3ust undone 1ou can redo up to <: undone steps
0&pand all 0&pand all nodes in the macro tree
-ollapse all -ollapse all nodes in the macro tree
Save layout settings
Save the .acro+uilderKs new layout after you have ad3usted the si!e of some of the
screen areas #he new screen layout is then retained and appears the ne&t time you
open the .acro+uilder
Definition of acros in the acro )uilder
#here are two basic methods of working in the .acro +uilder8
#he conte&t menu
(rag,(rop techni"ues
1ou define macros in planning books in combination with $acro ele$ents and $acro tools
Acti%ities
#onte1t enu
1ou use the conte&t menu primarily in the macro tree section )f you select an e&isting macro element (this can even be at
the .acro level), the system displays a menu with all the available options for this element at the current position in the
macro 0ach macro element is listed separately
Terminology
)nsert E 0nter the new element before the selected element
Attach E 0nter the new element after the last element at the same level
Add E 0nter the new element after the selected element at the ne&t level
#he conte&t menu offers two options that are not available with (rag,(rop8
Active4inactive
Activate4deactivate an element in the macro tree as in the macro toolbar
+reakpoint On4Off
Sets a breakpoint #his means that during e&ecution of the macro the macro stops at this element A dialog bo& appears in
which the value of the element is displayed 1ou continue processing by choosing
#hese two options are for use when creating macros, particularly for debugging comple& macros
Page 24 of 251
Drag > Drop
/se (rag , (rop to do any of the following8
Add or insert any macro element in the macro tree
'hen you drop the element, the system offers you a choice of options if more than one option is available
.ove elements within the macro tree
(rag a macro from the macro tree to the standard macros screen area
-hange the se"uence of the standard macros
-opy a part of the macro tree to the clipboard
)f the icon appears, you cannot carry out the action for this element )f the ? icon appears, you can carry out the action
for this element )n this case, you can release the left mouse button
6or more information on the different areas of the .acro +uilder screen, see .acro +uilder Screen

enu Functions in the acro )uilder
/se
#o be able to use some of the .acro+uilder menu functions, you need some additional information, which you can find
below #he functions described here are available to you if you access the .acro+uilder as a stand%alone application
((emand Planning or Supply Network Planning @ 0nvironment @ -urrent Settings @ .acro 'orkbench) as opposed to
through interactive planning
Features
enu Option Function
0dit )mport
.acro(s)
)mports either all macros or one macro from another planning book
After the import, check the macros in the target book #his is especially necessary if the source
book contains key figures that are not in the target book )f re"uired, make the appropriate
ad3ustments #hen activate the macros in the target book
0dit 0dit /ser
6unctionN
Adds a function that you have programmed in your own system to the list of possible
operators4functions in the .acro+uilder
1ou have programmed the function and defined the corresponding interface in transaction S0=G
)n the dialog bo&, which appears after choosing the menu entry, enter the technical name of the
user function -hoose 0nter Another screen appears in which you select the interface
parameters of the function 1ou must select the e&act same interface parameters that you used
when defining the interfaces of the user function
Note that the parameters C2)(?*)N0S, C2)(?-O*S, C2)(?-0**S, C2)(?6)W0(?*)N0S$
C2)(?6)W0(?-O*S and C2)(?6)W0(?#A+ are obsolete and should no longer be used )f you
use one of these parameters in a user function, the performance may suffer when a macro is
e&ecuted that uses this user function
Settings 0&pert
.ode On4Off
)f you turn the e&port mode off, certain fields are not visible on the attribute screens of macro
elements
/tilities Bersions
See Macro Book 4ersions
/tilities #est
.acros
A new screen appears with an empty test planning book 1ou can enter test data in the grid and
select a macro that has been generated -hoose 0&ecute .acro to test the macro Similarly you
can test the default macros by choosing the (efault button
6or more information, see SAP Note J9=F9;

Operators and Functions in acros
1ou enter functions in the following manner8
1. (rag and drop the operator4function icon to the relevant line in the macro work area A dialog bo& appears
2. On the bottom line choose the function you want to insert by using the pull%down bo& or 6> help #he function
automatically appears in both lines On the top line you can add alphanumeric arguments to the functions
6or more details of individual function see the following topics according to the type of function you want to use8
Mathe$atical Operators an# Functions
Page 25 of 251
Statistical Functions
"ogical 2Boolean3 Functions
Functions for 0nfo Objects an# Planning Books
,ate Functions
5eneral an# Planning !able Functions
SNP 6unctions
3. )f you want to add another macro element (an icon) to your macro, do not close the parentheses (in other words delete
the right%hand parenthesis) and choose 0nter the macro element as usual After you have made all the necessary
entries, finish the function by adding ) as the last line
1ou can nest macro functions within each other )n the following e&ample the macro step converts the value of row ;
from the internal unit of the current resource to the e&ternal unit contained in the resource master
1ou can also define and use your own functions 6or more information, see R/ser functionR in Menu Functions in the Macro
Buil#er
0ntry #on%entions
An argument is an input parameter, an independent variable, in a function 0nter character%based values of an argument in
"uotation marks and numerical values of an argument without "uotation marks -haracter strings inside "uotation marks
cannot have any blanks
/se a semicolon as a separator between the arguments of a function *eave no space between a function operator and a
parenthesis, but insert blanks before and after arguments in the parentheses$ for e&ample,
o 2O/N(( W $ 1 )
o 2O/N(( S/. ( W $ X ) $ 1 )
U represents a fi&ed coordinate
#hanging Attri+utes
.ost of the functions available are value functions, controlling the numbers or values stored within APO 5owever, SAP APO
also delivers a further category of functions that is the attribute%based functions #hese functions do not control the stored
values but rather the properties of the data views 6or instance, these functions change the color of a cell, row, or column,
hide or unhide rows or columns, or change the ready%for%input status
)f you want to use one of these functions, you must change the -hange scope field on the attributes of the result (row,
column, or element) to Attributes
#he results of attribute functions are not persistent in APO )n other words, if you turn a rowOs background color green, this
change is not stored permanently by the system So when you make a new selection in interactive planning or leave and
reenter the planning view, that green color change will be lost #herefore, if you want to see the results of the attribute
change ne&t time you enter the selection, you will need to rerun the relevant macros again )n some circumstances you may
also need an additional key figure to save the results of actions from previous sessions or selections
)t is not possible to modify the same result row with two or more attribute functions at the same time #he e&ample below
would lead to an error during the check 1ou must repeat the results row for each attribute function
Similarly if you wish to use the attribute of a cell, column, or row in a calculation, you must change the (ata Source field in
the attributes of the argument to 2ow attributes or -olumn attributes
Page 26 of 251
athematical Operators and Functions
athematical Operators
Operator 01planation
( Opening bracket
) -losing bracket
Y .ultiplication
YY Power (eg < Y Y = P < Y < Y <)
T Addition
% Subtraction
4 (ivision
$
Separator between arguments An argument is an input parameter 6or e&ample, in function f, e&pressed
as f& @5 A @7 ', the arguments are W; and W<
S Smaller than
SP Smaller than or e"ual to
Q *arger than
QP *arger than or e"ual to
athematical Functions
2efer to the following table to find the function of your choice #he functions are listed in alphabetical order
Function 01planation
A+S()
A+S( W ) returns the absolute value ZWZ for W #he argument can be either a number that you enter in an
Operator!function dialog bo& or one of the macro elements cell, row or column from the planning
table or au&iliary table
A-OS()
Arccos( W ) where W is between E; and ;, so that the function has values in the range [%4<, 4<\ #he
argument can be either a number that you enter in an Operator!function dialog bo&, or one of the
macro elements cell, row, or column from the planning table or the au&iliary table
AS)N()
Arc sin( W ) where W is between E; and ;, so that the function has values in the range [%4<, 4<\ #he
A#AN()
Arc tan( W ) has values in the range [%4<, 4<\ #he argument can be either a number that you enter in
an Operator!function dialog bo&, or one of the macro elements cell, row, or column from the planning
table or the au&iliary table
+0#'00N
Operator8 6or e&ample, W +0#'00N : AN( ;: returns the value ; if W falls within the range : through
;:
-OS()
-OS( W ) returns the cosine of an angle measured in radians #he argument can be either a number
that you enter in an Operator!function dialog bo&, or one of the macro elements cell, row, or column
from the planning table or the au&iliary table
-OS5()
-OS5 ( W ) returns the hyperbolic cosine #he argument can be either a number that you enter in an
Operator!function dialog bo&, or one of the macro elements cell, row, or column from the planning
()B 'hole number divisions ("uotient) operator8 6or e&ample, F ()B > returns ;
0WP()
0WP( W ) is the e&ponential function #he argument can be either a number that you enter in an
6A-()
6A-( n ) returns the factor of n, that is, the result of multiplying the integers from ; through n, e&pressed
as n] )f n P =, then =] P = Y < Y ; P F #he argument can be either a number that you enter in an
6*OO2() 6*OO2( W ) returns the largest integer value that is not greater than W #he argument can be either a
number that you enter in an Operator!function dialog bo&, or one of the macro elements cell, row or
Page 27 of 251
column from the planning table or the au&iliary table
62A-()
62A-( W ) returns the decimal part of W #he argument can be either a number that you enter in an
Operator!function dialog bo&, or one of the macro elements cell, row or column from the planning
*OC()
*OC( W ) returns the natural logarithm of W #he argument can be either a number that you enter in an
*OC;:()
*OC;:( W ) returns the power to which the basis of ;: must be raised to get the number W #he
.O( Operator for whole number divisions (remainder)8 6or e&ample, F .O( > returns :D
PA2#)A*S/.(
)
PA2#)A*S/.( W $ 1; $ $ 1n ) allows you to sum a variable number of values in a time series where W
specifies the number of values and 1; through 1n specify the time series
2O/N(()
2O/N(( W $ 1 ) rounds W to 1 decimal places #he arguments can be numbers that you enter in
Operator!function dialog bo&es, as well as cell&s', row&s' or column&s' from the planning table or the
au&iliary table
S)CN()
S)CN( W ) returns
the value of ; if W Q :
the value of : if W P :
the value of %; if W S :
#he argument can be either a number that you enter in an Operator!function dialog bo&, or one of the
macro elements cell, row or column from the planning table or the
au&iliary table
S)N()
S)N( W ) returns the sine of angle W measured in radians #he argument can be either a number that
you enter in an Operator!function dialog bo&, or one of the macro elements cell, row, or column from
the planning table or the au&iliary table
SA2#()
SA2#( W ) returns the s"uare root of a non%negative number #he argument can be either a number
S/.() S/. ( W; $ W<$ Wn ) returns the sum of the specified numbers
#AN()
#AN( W ) returns the tangent of angle W measured in radians #he argument can be either a number
#AN5()
#AN5( W ) returns the hyperbolic tangent of W #he argument can be either a number that you enter in
an Operator!function dialog bo&, or one of the macro elements cell, row or column from the planning
#2/N-()
#2/N-( W ) returns the integer part of W #he argument can be either a number that you enter in an
"ector operators
Bector operators are operators whose operands are areas 'ithin the macro the operation is only performed once Since the
respective function module is only called once, performance is in general improved with respect to operators that have rows
or cells as operands #he areas involved in such operations must be mutually compatible
B0-?()B()
B0-?()B( area; $ area< ) carries out real division of the two areas #he ith member of area; is divided
by the ith member of area<
B0-?./*#()
B0-?./*#(area; $ area< ) multiplies area; by area< #he ith member of area; is multiplies by the ith
member of area<
B0-?S/+()
B0-?S/+(area; $ area< ) subtracts area< from area; #he ith member of area< is subtracted from the
ith member of area;
B0-?S/.()
B0-?S/.(area; $ area< ) adds area< to area; #he ith member of area< is added to the ith member of
area;
Page 28 of 251
Statistical Functions
ABC()
ABC( W; $$ Wn ) returns the mean average of W; through Wn #he arguments can be numbers that you
enter in Operator!function dialog bo&es, as well as rows, columns, cells or areas from the planning
+)NO.()
+)NO.( n $ k ) calculates the binomial coefficient based on the formula n] 4 k](n%k)] /se this function to
determine the total number of possible combinations without repetition of k items in a set of n items #he
arguments can be numbers that you enter in Operator!function dialog bo&es, as well as rows, columns
or cells from the planning table or au&iliary table
-(6+()
-(6+( W $ n $ p ) returns the probability that the value of a binomial ( n $ p ) distributed variable (see
(6+() ) is less than or e"ual to W$ thus, the cumulative probability function of the binomial distribution in a
sample of si!e n where p is the probability that a faulty item is drawn #he arguments can be numbers
that you enter in Operator!function dialog bo&es, as well as rows, columns or cells from the planning
-(65()
-(65( W $ n $ . $ N ) returns the probability that the value of a distributed variable (see (65() ) is less
than or e"ual to W$ thus, the cumulative probability function of the hypergeometric distribution, where n is
the si!e of the sample, . is the number of faulty items in the sample, and N is the si!e of the population
#he arguments can be numbers that you enter in Operator!function dialog bo&es, as well as rows,
columns or cells from the planning table or au&iliary table
-(6N()
-(6N( W ) returns the probability that the value of a standard normal distributed variable is less than W$
thus, the cumulative function of the standard normal distribution #he argument can be either a number
that you enter in an Operator!function dialog bo&, or one of the macro elements row, column or cell
from the planning table or au&iliary table
-(6#()
-(6#( W $ n ) returns the probability that the value of a standard normal distributed variable is less than
W$ thus, the cumulative density function of StudentKs t distribution where n is the degrees of freedom (n
QP >) #he arguments can be numbers that you enter in Operator!function dialog bo&es, as well as
rows, columns or cells from the planning table or au&iliary table
-ONS#AN#()
-ONS#AN#( W; $ $ Wn $ 1; $ $ 1n ) returns the constant A of a linear regression line 1 P A T +W for a
series of observed values W; through Wn gives the values of the e&planatory variable 1; through 1n
gives the values of the dependent variable #he number of the values Wi and 1i must be the same #he
arguments of the function can be number(s) that you enter in Operator!function dialog bo&es as well as
cell&s', row&s', column&s' or area&s' from the planning table or the au&iliary table
-O2()
-O2( W; $ $ Wn $ 1; $ $ 1n ) returns the correlation coefficient for a two%dimensional random variable
for which the values W; through Wn and 1; through 1n are observed #his allows you to e&amine the
relationship between two random variables #he number of the values Wi and 1i must be the same #he
arguments of the function can be number(s) that you enter in Operator!function dialog bo&es as well as
-OB()
-OB( W; $ $ Wn $ 1; $ $ 1n ) returns the covariance for the two data sets W; through Wn and 1;
through 1n #he arguments of the function can be number(s) that you enter in Operator!function dialog
bo&es as well as cell&s', row&s', column&s' or area&s' from the planning table or the au&iliary table
(6+()
(6+( m $ n $ p ) returns the probability of the binomial distribution where m is the number of faulty items in
a sample of si!e n, and p is the probability that a faulty item will be drawn #he arguments can be
numbers that you enter in Operator!function dialog bo&es, as well as rows, columns or cells from the
planning table or au&iliary table
(65()
(65( m $ n $ . $ N ) returns the probability of the hypergeometric distribution, that is, the probability of
finding m faulty items in a sample of si!e n where . is the number of faulty items in the population and N
is the si!e of the population #he arguments can be numbers that you enter in Operator!function dialog
bo&es, as well as rows, columns or cells from the planning table or au&iliary table
0?S#(0B()
0?S#(0B( W; $ $ Wn ) returns the estimated value for the standard deviation of a random variable
based on the observed values W; through Wn, ie SA2#( 0?BA2( W; $ $ Wn ) ) #he arguments can be
number(s) that that you enter in Operator!function dialog bo&es, as well as row&s', column&s', cell&s',
or area&s' from the planning table or au&iliary table
0?BA2()
0?BA2( W; $ $ Wn ) returns the unbiased estimated value for the variance of a random variable based
on the observed values W; through Wn #he arguments can be number(s) that that you enter in
Operator!function dialog bo&es, as well as row&s', column&s', cell&s', or area&s' from the planning
table or au&iliary table #he correction factor n 4 n%; is the difference between the functions 0?BA2() and
BA2()
Page 29 of 251
CA..A()
CA..A( W ) returns the gamma function for W #he argument can be either a number that you enter in
an Operator!function dialog bo&, or one of the macro elements cell, row or column from the planning
.A(()
.A(( W; $ $ Wn ) returns the mean absolute deviation of the values of the values W; through Wn #he
arguments can be numbers that you enter in Operator!function dialog bo&es, as well as cell&s', row&s',
column&s' or area&s' from the planning table or the au&iliary table
.AP0()
.AP0( W; $ $ Wn $ 1; $ $ 1n ) returns the mean absolute percentage error for the values W;, 1;
through Wn, 1n #he arguments can be numbers that you enter in Operator!function dialog bo&es, as
well as cell&s', row&s', column&s' or area&s' from the planning table or the au&iliary table
.AW()
.AW( W; $ $ Wn ) returns the greatest value in the range W; through Wn #he arguments can be either
numbers that you enter in Operator!function dialog bo&es, or cell&s', row&s', column&s' or area&s' from
.0AN()
.0AN( W; $ $ Wn ) returns the mean of the values W; through Wn #he arguments can be numbers that
you enter in Operator!function dialog bo&es, as well as cell&s', row&s', column&s' or area&s' from the
planning table or the au&iliary table
.0()AN()
.0()AN( W; $ $ Wn ) returns the median of the values W; through Wn #he arguments can be numbers
that you enter in Operator!function dialog bo&es, as well as cell&s', row&s', column&s' or area&s' from
.)N()
.)N( W; $ $ Wn ) returns the smallest value of the values W; through Wn #he arguments can be
numbers that you enter in Operator!function dialog bo&es, as well as cell&s', row&s', column&s' or
area&s' from the planning table or the au&iliary table
.P0()
.P0( W; $ $ Wn $ 1; $ $ 1n) returns the mean percentage error for the values W;, 1; through Wn, 1n
#he arguments can be numbers that you enter in Operator!function dialog bo&es, as well as cell&s',
row&s', column&s' or area&s' from the planning table or the au&iliary table
.S0()
.S0( W; $ $ Wn $ 1; $ $ 1n ) returns the mean s"uare error for the values W;, 1; through Wn, 1n #he
P02./#()
P02./#( W $ 1 ) returns the number of possible permutations when W ob3ects are selected from a set of
1 ob3ects where 1 Q W or 1 P W P02./# (W $ 1 ) P W] 4(W % 1)] #he arguments can be numbers that you
enter in an Operator!function dialog bo&, as well as cell&s', row&s' or column&s' from the planning
2.S0()
2.S0( W; $ $ Wn $ 1; $ $ 1n ) returns the root of the mean s"uare error for the values W;, 1; through
Wn, 1n #he arguments can be numbers that you enter in Operator!function dialog bo&es, as well as
S#(0B()
S#(0B( W; $ $ Wn ) returns the standard deviation of the values W; through Wn #he arguments can be
numbers that you enter in Operator!function dialog bo&es, as well as cell&s', row&s', column&s' or
#20N(()
#20N(( W; $ $ Wn $ 1; $ $ 1n ) returns the trend + in a linear regression line 1 P A T +W for a series
of observed pairs of values W; through Wn gives the values of the e&planatory variable 1; through 1n
gives the values of the dependent variable #he number of the values Wi and 1i must be the same #he
BA2()
BA2( W; $ $ Wn ) returns the variance of the values W; through Wn #he arguments can be numbers
that you enter in Operator!function dialog bo&es, as well as cell&s', row&s', column&s' or area&s' from
BW()
BW( W; $ $ Wn ) returns the coefficient of variation for the values W; through Wn, calculated as the
standard deviation S#(0B( W; $ $ Wn ) divided by the mean .0AN ( W; $ $ Wn ) #he arguments can
be numbers that you enter in Operator!function dialog bo&es, as well as cell&s', row&s', column&s' or
(ogical &)oolean' Functions
AN( +oolean operator for conditions8 true only if both conditions are true
NO# +oolean operator for conditions8 logical negation
O2 *ogical operator8 true if either one or both conditions are true
Page 30 of 251
SNP Functions
2efer to the following table to find the function of your choice #he functions are listed in alphabetical order 1ou can find
e&amples of macros that use some of these functions in the standard planning book 9ASNP9>, view SNP9>(;)
A-#?*O-A#)ON?P2O(/-#S or
A-#?*O-A#)ON ?P2O(/-#S()
A-#?*O-A#)ON?P2O(/-#S provides all the product%location combinations that
are in the current selection VC2)(P<O is an optional parameter )f you enter this
parameter, the system returns the location products of the selection in the second
grid
-OB02?-A*-()
-OB02?-A*-(rows for stock on hand $ area for demand from the ne&t period to the
end of the time period $ area containing the number of workdays $ demand from the
ne&t period to the end of the time period) returns the daysO supply of a product by
considering the current stock on hand, the total demand of subse"uent time periods,
and the number of workdays in this time period
6or e&ample8
#ime span w;; w;< w;= m:> m:D
#otal demand8 : <:,: : <D,: <G,D
Stock level FJ,G >J,G >J,G <=,G :
(aysO supply G: F= DG <F :
'orkdays G G G =: =;
2esult at the end of m:>8
#otal demand is <=G
#otal demand in the future is <GD
#otal number of work days in the ne&t period is =;
#hus, (<=G4<GD) & =; ^ <F (only <F days can be covered)
/sing the above value (<F)
for w;<8 (aysO supply is F= P G (from w;=) T =: (from m:>) T <F (from m:D)
for w;;8 (aysO supply is G: P G (from w;<) T =: (from m;=) T <F (from m:>) T <F
(from m:D)
-OB02AC0?S/.()

-OB02AC0?S/. (necessary daysO supply $ area containing "uantity $ area
containing days in the period) returns the total "uantity that corresponds to the daysK
supply re"uired )nstead of the area, you can also enter two se"uences with the
same number of entries
6or e&ample8
-OB02AC0?S/. ( ;: $
<: $ =: $ >: $ D:
; $ < $ G $ ;: )
provides the sum of the values <:, =:, >: P 9:, since the sum of days in the first
three periods corresponds to the necessary daysO supply
(0.AN(?-A*- ()
(0.AN(?-A*-( KproductK , K locationK , KversionK , KperiodK , key figure for demand ,
forecast key figure ) returns the demand of a period taking the settings in the master
record for the location product (re"uirements strategy, forecast hori!on) into account
#he arguments for the key figures can be rows or areas
(0P?*O-A#)ON?P2O(/-#S()
(0P?*O-A#)ON?P2O(/-#S(KlocationsO $ KproductO $ VversionO $ VdirectionO $ Vlocation
typeO $) returns all product%location combinations that are connected to the given
location product using the transportation land in the given direction (A P all, 6 P
forwards, + P backwards) 1ou can enter several location types
6O2'A2(?-A*-() 6O2'A2(?-A*-( number of days $ area containing the values $ area containing
the number of working days in a period) returns the sum of the values in the area
over the number of days specified )f the number of days does not coincide with the
end of the period, the value for this last period is calculated proportionally
Period ; < = > D F
(emand ;:: ;<: ;=: ;<: ;::
Page 31 of 251
'orking <: << <; << <:
days
)n the above e&ample for period ;, 6O2'A2(?-A*- ( F=$ ) returns the value =D:
(;:: T ;<: T ;=:) 6O2'A2(?-A*- ( G>$) returns >;: (;:: T ;<: T ;=: T ;<:
;;Y<<)
)N)#)A*?S#O-L()
)N)#)A*?S#O-L( KversionK ) returns the initial stock for the version #he system
determines the parameters (stock category group from the location master) from the
current selection
)N#0C02?-A*-()
)N#0C02?-A*-( 2ow(nattribute) ) provides the integral sum of values from the
detailed level of a key figure 6or e&ample8
L6; total ;:<D
(etail ; =GD
(etail < FD:
)N#0C02?-A*- (L6; as attribute) provides ;:
)t must be e&ecuted on the _all planning ob3ects` level, or on _specific level(s)`, but
not on detail level
.A#*O-?)N-()
Synta1
.A#*O-?)N-( Field name ; Product ; Location ; <Version> ;
Date )
Field name8 *iteral in "uotation marks containing the name of the field from the
master data for product interchangeability #he following are valid names8
"A(IDF$8 Balid from
"A(IDTO8 Balid to
/S0/PDAT08 /se up date
Product: Product ID
(ocation: Location ID
"ersion: Version ID (optional)
1ou can enter the product, the location, and the version with other operators or
functions, such as A-#?P2O(/-#, A-#?*O-A#)ON and A-#?B02S)ON, or as a
literal in "uotation marks )f you do not enter a version, the system uses the active
version
Date8 1ou can enter the date with operators or functions, such as
+/-L0#?0(A#0() for instance
Description
.A#*O-?)N-() provides the content of the numerical master data fields for product
interchangeability e&ecuted above
.A#*O-?)N-?-() Synta1
.A#*O-?)N-?-( VField name ; Product ; Location ; <Version> ;
Date )
Field name8 *iteral in "uotation marks containing the name of the field from the
master data for product interchangeability #he following are valid names8
P$OD/#TID8 )nternal product )( (C/)()
P$OD/#T: External product ID
S/#0P$ODID: Internal product ID of the successor product
(GUID).
S/#0P$OD: External product ID of the successor product.
/S0/PF(=: Use-up strateg
I#TBP0: !pe of interchangea"ilit group
Page 32 of 251
Product: Product ID
(ocation: Location ID
"ersion: Version ID (optional)
1ou can enter the product, the location, and the version with other operators or
literal in "uotation marks )f you do not enter a version, the system uses the active
version
Date8 1ou can enter the date with other operators or functions, such as
+/-L0#?0(A#0() for instance
DescriptionC .A#*O-?)N-?-() provides the content of the alphanumeric master
data fields for product interchangeability e&ecuted above
.AW?S#O-L()
.AW?S#O-L( KversionK ) returns the storage capacity for the location product #he
system uses the current selection to find this information in the product master
./*#)*0B0*?(0.AN(?.0AN()
./*#)*0B0*?(0.AN(?.0AN( forecast key figure, actual key figure, product,
location, version, SperiodQ) returns the sum of demands from all locations in the
supply chain Balues for the future are taken from the forecast key figure, for the past
from the actual key figure, in both cases for the given product, location (here for
instance the plant or distribution center for which you are planning), and version #he
entries actual key figure and period are not strictly necessary but improve
performance, if you use ./*#)*0B0*?(0.AN(?BA2 in the same macro 6or more
information, see Multilevel Functions in the Supply Chain Netork
./*#)*0B0*?(0.AN(?BA2()

./*#)*0B0*?(0.AN(?BA2( forecast key figure, actual key figure, product,
location, version, SperiodQ ) returns the error variance between the forecast demand
and actual demand for all locations in the supply chain #his value is determined for
the whole historical period or the period specified As above you also enter the
product, location, and version of interest, for e&ample A-#?P2O(/-#,
A-#?*O-A#)ON, and A-#?B02S)ON 6or more information, see Multilevel
Functions in the Supply Chain Netork
./*#)*0B0*?*0A(?.0AN()

./*#)*0B0*?*0A(?.0AN( forecast key figure, actual key figure, product, location,
version, SperiodQ) is similar to ./*#)*0B0*?(0.AN(?.0AN() 6rom a customer
view it calculates the lead time for a product in a location 6or more information, see
Multilevel Functions in the Supply Chain Netork
./*#)*0B0*?*0A(?BA2()

./*#)*0B0*?*0A(?BA2( forecast key figure, actual key figure, product, location,
version, SperiodQ ) returns the error variance between the forecast lead time and
actual lead time for the specified product and location #his value is determined for
the whole historical period or the period specified As above you also enter the
product, location, and version of interest, for e&ample A-#?P2O(/-#,
A-#?*O-A#)ON, and A-#?B02S)ON 6or more information, see Multilevel
Functions in the Supply Chain Netork
N0#?(0.AN(() Synta1
N0#?(0.AN(( Stock ; reorder point ; target stock level ; net
demand ; method ; material A DlocationE A D%ersionE )
Stock8 -urrent period stock
Net demand8 Net demand of previous period
ethod8 ;, <, = or >
Description
N0#?(0.AN(() calculates the net demand using various methods 6or methods ;
and <, the system cumulates the net demand 6or methods = and >, the system only
considers the Net (emand parameter
)f you have defined the reorder point method for the product .aterial at location
*ocation, the system calculates the net demand according to the following formula,
irrespective of the method selected8 Net demand P #arget stock level E current stock
level #he following applies8 -urrent stock level P stock T (cumulative) Net demand
(of previous periods) A negative net demand is set to :
)f you have not defined a reorder point method in the location product master, the
Page 33 of 251
system calculates the net demand depending on the method selected8
.ethods ; and =8 )f the current stock level is lower than the reorder point, the
system calculates the net demand using the following formula8 Net demand P
#arget stock level E current stock level )n other cases, the following formula is
used8 Net demand P 2eorder point E current stock level
.ethods < and >8 )f the current stock level is lower than the reorder point, the
system calculates the net demand using the following formula8 Net demand P
#arget stock level E reorder point )n other cases, the following formula is used8
Net demand P 2eorder point E current stock level
O2(02?(A#A?*O-P2O(S()
O2(02?(A#A?*O-P2O(S( Vbuffering (y4n)O $ Vcategory groupO $ VversionO $ from%
date $ to%date $ Vlocation ;O $ Vproduct ;O $ Vlocation <O $N) provides the cumulated
order "uantities of any number of location products in the specified time series and in
the specified category group
P51S)-A*?S#O-L()
P51S)-A*?S#O-L( VproductO $ VlocationO $ version $ VcategoryO $ VcategoryO $ N)
returns the stock of a location product of one or more categories
P51?S#O-L?*O-P2O(S()
P51?S#O-L?*O-P2O(S( Vcategory groupO $ VversionO $ Vlocation ;O $ Vproduct ;O $
Vlocation <O $N) returns the cumulated stock of multiple location products from the
specified category group
P2O(/-#)ON?-OS#()
P2O(/-#)ON?-OS#( KproductK $ KlocationK $ date in period $ SKversionKQ ) returns the
production costs for the product in the location for the period specified using the
PP.
20O2(02?-A*-()
20O2(02?-A*-( KproductK $ KlocationK $ KversionK $ reorder days $ reorder pointK $
offset $ key figure for planned demand $ row for number of workings days per period )
returns the reorder point for the location product referring to the parameters saved in
the location production master data 6or instance if the reorder point process in the
master data re"uires a manual entry for the reorder point, you must enter a value,
otherwise enter :
20O2(02?(A1S()
20O2(02?(A1S(KproductK $ KlocationK $ KversionK $ daysK supply ) returns the daysK
supply referring to the parameters saved in the location production master data )f
these parameters re"uire a manual entry for the daysK supply, enter a value ,
otherwise enter :
SA60#1?-A*-()
SA60#1?-A*-( KproductK $ KlocationK $ KversionK $ safety daysO supply $ KSname of key
figure for safety daysO supplyQO $ safety stock $ KSname of key figure for safety
stockQK $ key figure for planned demand $ key figure for number of workdays per
period ) returns the safety stock for the location product while taking the parameters
defined in the location product master data into account )f these parameters re"uire
a manual entry for the safety daysK supply or the safety stock, enter a value ,
otherwise enter :
1ou can use the optional parameters name of key figure for safety daysK supply and
name of key figure for safety stock in aggregate# planning (see SAP note JDJG9>)
SA60#1?(A1S()
SA60#1?(A1S(KproductK $ KlocationK $ KversionK $ safety daysK supply $ VSname of key
figure for safety daysO supplyQO) returns the safety daysO supply for the location
product while taking the parameters defined in the location production master data
into account )f these parameters re"uire a manual entry for the safety daysK supply
enter a value , otherwise enter :
1ou can use the optional parameter name of key figure for safety daysO supply in
aggregated planning (see above)
S+?A*P5A?-1-*0()
S+?A*P5A?-1-*0( service level $ demand forecast $ forecast error demand (a) $
replenishment lead time $ forecast error replenishment lead time (a) $ daysK supply )
returns the safety stock level for the Alpha service level according to the cycle
method
#he demand forecast is a "uantity per day #he replenishment lead time and the
daysO supply are measured in seconds
6or more information, see Safety Stock Planning
Page 34 of 251
S+?A*P5A?PO)N#()
S+?A*P5A?PO)N#( service level $ demand forecast $ forecast error demand (a) $
replenishment lead time $ forecast error replenishment lead time (a)) returns the
safety stock level for the Alpha service level according to the point method
S+?+0#A?-1-*0()
S+?+0#A?-1-*0( service level $ demand forecast $ forecast error demand (a) $
returns the safety stock level for the +eta service level according to the cycle
method
S+?+0#A?PO)N#()
S+?+0#A?PO)N#( service level $ demand forecast $ forecast error demand (a) $
returns the safety stock level for the +eta service level according to the point method
SOS?-50-L?./*#)()
Synta1
SOS?-50-L?./*#)( procurement indicator ; version ; product ;
location ; resource )
Procurement indicator8 (in%house production) or F (e&ternal procurement)
Description
SOS?-50-L?./*#)() provides the value W, if there are multiple sources of supply
in the planning time period for the location product, or combination of location and
product )n other cases the value SPA-0 (no value) is returned
S#O-L?+A*AN-0?OP#()
Synta1
S#O-L?+A*AN-0?OP#( Version ; location ; product ; ma!imum
dela" ; return value ; demand area ; total demand area; total
receipt area )
"ersion8 Bersion )(
(ocation8 *ocation )(
Product8 Product )(
1ou can enter the version, the location, and the product with other operators or
literal in "uotation marks
a1imum Delay8 .a&imum delay in days
$eturn %alue8 *iteral in "uotation marks for defining the return value of the macro
function )f you enter SE as the return value, the macro function provides the stock
on hand )f you enter PE, the function provides the demand not covered due to
capacity restrictions
Demand area8 #he system uses the planned independent demand available in this
area as the input data for the macro function
Total demand area8 #he system uses the total demand available in this area as the
input data for the macro function
Total receipts area8 #he system uses the total receipts available in this area as the
input data for the macro function
Description
S#O-L?+A*AN-0?OP#() calculates the stock on hand for a location product by
considering a ma&imum delay for the demand
6or more information on using this macro function, see SAP note G:;99<
S#O-L?-A*-()
S#O-L?-A*-( total demand key figure $ total receipts key figure $ stock level of the
previous period ) returns the stock level
#A2C0#?-A*-()
#A2C0#?-A*-( KproductK $ KlocationK $ KversionK $ target daysO supply $ target stock
level $ offset (such as safety stock)$ key figure for planned demand $ key figure for
number of workings days per period ) returns the target stock level referring to the
parameters saved in the location production master data )f these parameters re"uire
a manual entry for the target daysK supply or the target stock level, enter a value ,
otherwise enter :
#A2C0#?(A1S() #A2C0#?(A1S( KproductK $ KlocationK $ KversionK $ target daysK supply ) returns the
Page 35 of 251
target daysK supply referring to the parameters saved in the location production
master data )f these parameters re"uire a manual entry for the target daysK supply,
enter a value , otherwise enter :
#2ANSPO2#?-OS#()
#2ANSPO2#?-OS#( KproductK $ Ksource locationK $ Kdestination locationK $ Kmeans of
transportK $ date $ SKversionKQ ) returns the transport costs incurred transporting the
product from source location to destination location using the means of transport on
the given date #he system uses the information stored in the relevant transportation
lane
B0-?-OB02?-A*-()
B0-?-OB02?-A*-(area for stock on hand $ area for demand from the ne&t period
to the end of the time period $ area containing the number of workdays $ demand
from the ne&t period to the end of the time period) returns the daysO supply of a
product by considering the current stock on hand, the total demand of subse"uent
time periods, and the number of workdays in this time period
#he vector functions correspond to the largest possible e&tent to the functions with
the same names, but without the B0- prefi& (in this case -OB02?-A*-) 1ou are,
however, working using vectors, so the operands are areas and not rows #his
means that there are no loops within the step and performance is better
B0-?C2)(?P20A?A/AN#)#1
B0-?C2)(?P20A?A/AN#)#1 provides the part "uantities in the distribution receipt
for the SNP key figure procured e&ternally
B0-?20O2(02?-A*-()
B0-?20O2(02?-A*-( KproductK $ KlocationK $ KversionK $ reorder days $ reorder
pointK $ offset $ key figure (area) for planned demand $ area for number of workings
days per period ) returns the reorder point for the location product referring to the
parameters saved in the location production master data )f the reorder point method
in the master data re"uires a manual entry for the reorder point, for instance, you
must enter a value, otherwise enter : #his is the vector version of
20O2(02?-A*-
#he result is an area
B0-?SA60#1?-A*-()
B0-?SA60#1?-A*-(KproductK $ KlocationK $ KversionK $ safety daysK supply $ safety
stock , key figure for planned demand ) returns the safety stock for the location
product referring to the parameters saved in the location production master data )f
these parameters re"uire a manual entry for the safety daysK supply or the safety
stock, enter a value , otherwise enter :
#he arguments for the key figures are areas, as for the result
#his is the vector version of SA60#1?-A*-
B0-?S#O-L?-ONS/.P#)ON() B0-?S#O-L?-ONS/.P#)ON() is a vector function that carries out consumption
using stock and demand values
6unction arguments8
;8 Strategy (-haracteristics values8 6)6O, +)6O, *)6O)
<8 #ime (days) for backwards consumption
=8 #ime (days) for forwards consumption
>8 Number of decimal places for consumption
D8 )nitial stock on hand
F % nTF Bector with n storage values
nTG % <nTF Bector with n stock values
<nTG % =nTF Bector with n period lengths (days)
6or e&ample8
B0-?S#O-L?-ONS/.P#)ON( K*)6OK $ = $ 999 $ : $ : $ Area8 Sum of receipts (;) $
sum of receipts (n) $ area8 Sum of demand (;) $ sum of demand (n) $ area8 'orkdays
(;) $ workdays (n) ) provides a vector with n values that display the result of
consumption #he resulting values can be interpreted as follows8
Negative values8 #he demand of the corresponding periods cannot be covered
completely #he amount indicates the "uantity of demand not covered
Positive values8 )n the period concerned, stock is still available after
consumption #his can then be used for covering further demand #he amount
Page 36 of 251
indicates the stock "uantity
B0-?#A2C0#?-A*-()
B0-?#A2C0#?-A*-( KproductK $ KlocationK $ KversionK $ target daysK supply $ target
stock level $ offset ( safety stock) ) returns the target stock level referring to the
parameters saved in the location production master data )f these parameters re"uire
a manual entry for the target daysK supply or the target stock level, enter a value ,
otherwise enter :
#his is the vector version of #A2C0#?-A*- #he result and all key figures are
areas
B.)?*0A(#).0()
B.)?*0A(#).0( KversionK ) returns the procurement time for B.) #he system uses
the information from the current selection (product and location) to find the data in
the master data

Functions for Scheduling Agreements
#he field +XA)( is referred to in several functions #his field is the internal number of an item in a scheduling agreement, and
can be determined by using function A-#?S-50(?AC200.0N#?)( (see below)
A-#?*OCS1
A-#?*OCS1 returns the name of the current logical system that is being used for
planning (9A*OCS1)
A-#?S-50(?AC200.0N#
A-#?S-50(?AC200.0N# returns the name (document number) of the current
scheduling agreement that is being used for planning (9A(O-NO)
A-#?S-50(?AC200.0N#?)(()
A-#?S-50(?AC200.0N#?)( returns the internal number (field +XA)() of the
current scheduling agreement item )t is determined from the logical system name,
scheduling agreement name, and the item number
A-#?S-50(?AC200.0N#?PS(
)
A-#?S-50(?AC200.0N#?PS returns the item number that is currently being
processed
SA()
SA ( +XA)( $ Vfield?nameV returns the value of any nunerical field (field?name) in a
scheduling agreement item (+XA)() #his function is particularly useful for user
fields
SA?-()
SA?- ( +XA)( $ Vfield?nameV returns the value of any character field (field?name) in
a scheduling agreement item (+XA)() #his function is particularly useful for user
fields
SA?-A**O66?5)S#()
SA?-A**O66?5)S#( +XA)( $ from?date $ VtypeV $ N $ SO24)OQ) returns the release
history for a scheduling agreement item (+XA)() from the from?date date )n VtypeV
you specify whether the scheduling agreement is relevant to delivery (S) or a
forecast (6) )n N you specify which version is read #he default is the last version
(;)$ the last but one has n P < etc )n the last field you can specify whether the
system views receipts (2) or issues ()) #he default is )
SA?-ON6?5)S#()
SA?-A**O66?5)S#( +XA)( $ from?date $ VtypeV $ N $ SO24)OQ) returns the
confirmation history for a scheduling agreement item (+XA)() from the from?date
date )n VtypeV you specify whether the scheduling agreement is relevant to delivery
(S) or a forecast (6) )n N you specify which version is read #he default is the last
version (;)$ the last but one has n P < etc )n the last field you can specify whether
the system views receipts (2) or issues ()) #he default is )
SA?*AS#?(0*?(A#0()
SA?*AS#?(0*?(A#0 ( +XA)( ) returns the date of the last delivery in a scheduling
agreement (+XA/)()
SA?*AS#?(0*?A/AN#)#1()
SA?*AS#?(0*? A/AN#)#1 ( +XA)( ) returns the "uantity of the last delivery in a
scheduling agreement (+XA/)() #his field is only used in the case of stock
transfer
SA?*AS#?C)?A/AN#)#1()
SA?*AS#?C)? A/AN#)#1 ( +XA)( ) returns the last goods issue "uantity in a
scheduling agreement (+XA/)()
SA?*AS#?C2?(A#0()
SA?*AS#?C2?(A#0 ( +XA)( ) returns the date of the last goods receipt in a
scheduling agreement (+XA/)()
SA?*AS#?C2? A/AN#)#1() SA?*AS#?C2? A/AN#)#1 ( +XA)( ) returns the "uantity of the last goods receipt
Page 37 of 251
in a scheduling agreement (+XA/)()
SA?*AS#?S5)P?A/AN#)#1()
SA?*AS#?S5)P?A/AN#)#1 ( +XA)( ) returns the notified "uantity of the last
delivery in a scheduling agreement (+XA/)()
SA?N0W#?620*0AS0?(A#0()
SA?N0W#?620*0AS0?(A#0 ( +XA)( ) returns the date of the ne&t forecast
release in a scheduling agreement (+XA/)()
SA?N0W#?20*0AS0?(A#0()
SA?N0W#?20*0AS0?(A#0 ( +XA)( ) returns the date of the ne&t delivery%relevant
release in a scheduling agreement (+XA/)()
SA?P*)6X()
SA?P*)6X ( +XA)( ) returns the planned delivery time of a scheduling agreement
item (+XA)()
SA?P*NC?-A#0CO21()
SA?P*NC?-A#0CO21 ( +XA)( ) returns VAPOO if the scheduling agreement
( +XA)( ) is an APO scheduling agreement and VO*#PO if it was created in the O*#P
system
SA?P2O-0SS?#1P0()
SA?P2O-0SS?#1P0 ( +XA)( ) returns the process type for the scheduling
agreement (+XA)()
SA?#O#A*?(0*?A/AN#)#1()
SA?#O#A*?(0*?A/AN#)#1 ( +XA)( ) returns the total delivery "uantity in the
complete scheduling agreement that contains item (+XA)()
SA?#O#A*?C)?A/AN#)#1()
SA?#O#A*?C)?A/AN#)#1 ( +XA)( ) returns the total goods issue "uantity in the
SA?#O#A*?C2?A/AN#)#1()
SA?#O#A*?C2?A/AN#)#1 ( +XA)( ) returns the total notified "uantity in the
SA?#O#A*?S5)P?A/AN#)#1()
SA?#O#A*?S5)P?A/AN#)#1 ( +XA)( ) returns the total goods receipt "uantity in
the complete scheduling agreement that contains item (+XA)()

Functions for Info O+,ects and Planning )ooks
2efer to the following table to find the macro function of your choice #he functions are listed in alphabetical order
A-#?-O*/.N A-#?-O*/.N returns the number of the column that is currently being processed
A-#?)O+IN.?BA*/0()
A-#?)O+IN.?BA*/0( K)O+IN.K$ SC2)(P<KQ ) returns the value of the )nfoOb3ect
that is currently being planned VC2)(P<O is an optional parameter )f you specify this
parameter, the value of the specified )nfoOb3ect in the second grid at the time of the
calculation is returned 6or e&ample, the result of
A-#?)O+IN.?BA*/0( KSA*O2CK) might be KnorthK
A-#?*0B0* or A-#?*0B0*()
A-#?*0B0* returns the level of the ob3ect you are planning VC2)(P<O is an optional
parameter )f you specify this parameter, the level of the planning ob3ect in the
second grid is returned 6or e&ample, the result of A-#?*0B0* ( KC2)(P<K ) is <, if
the planning ob3ect at the time of the calculation is the result of the second drilldown
in grid <
A-#?*O-A#)ON or
A-#?*O-A#)ON()
A-#?*O-A#)ON returns the name of the location that is currently being planned
where the )nfoOb3ect for the location is 9A*O-NO 6or e&ample, the result of
A-#?*O-A#)ON might be (-%+02*)N VC2)(P<O is an optional parameter )f you
specify this parameter, the name of the location being calculated in the second grid
is returned
A-#?*O-A#)ON ?P2O(/-#S or
A-#?*O-A#)ON ?P2O(/-#S()
A-#?*O-A#)ON?P2O(/-#S provides all the product%location combinations that
are in the current selection VC2)(P<O is an optional parameter )f you specify this
parameter, the system returns the location products in the selection in the second
grid
A-#?P*O+
A-#?P*O+ returns the internal number of the planning ob3ect for which the macro is
currently being processed #he internal number of a planning ob3ect is often needed
in other macro functions
A-#?P*O+?C2)(<
A-#?P*O+?C2)(< returns the internal number of the planning ob3ect in grid < for
which the macro is currently being processed #he internal number of a planning
ob3ect is often needed in other macro functions
A-#?P2O(/-# or
A-#?P2O(/-#()
A-#?P2O(/-# returns the name of the product that is currently being calculated
where the )nfoOb3ect for the product is 9A.A#N2 6or e&ample, the result of
A-#?P2O(/-# might be _>G;;_ VC2)(P<O is an optional parameter )f you specify
this parameter, the name of the product being calculated in the second grid is
Page 38 of 251
returned
A-#?20SO/2-0 or
A-#?20SO/2-0()
A-#?20SO/2-0 returns the name of the resource that is currently being planned
where the )nfoOb3ect name of the resource is 9A2NA.0 6or e&ample, the result of
A-#?20SO/2-0 might be 20S%<:?;:::?::; VC2)(P<O is an optional parameter
)f you specify this parameter, the name of the resource being calculated in the
second grid is returned
A-#?/S02 A-#?/S02 returns the user name of the current planner
A-#?B02S)ON or
A-#?B02S)ON()
A-#?B02S)ON returns the version that is currently being planned where the
)nfoOb3ect name of the version is 9AB02S)ON KC2)(P<K is an optional argument )f
you specify this argument, the version being planned in the second grid is returned
6or e&ample, the result of A-#?B02S)ON( KC2)(P<K ) might be ::;
ACC?*0B0*()
Synta1
ACC?*0B0*(#characteristic# $% E&'LUDE(I)P* $G+ID,-* )
-haracteristic P #echnical name of the characteristic that is to be analy!ed
0W-*/(0?).P8 )f you set this optional indicator (KWK), implicitly strong characteristics
are not taken into account in the analysis
C2)(P<8 )f you set this optional parameter, the analysis is applied to the planning
ob3ect of the second grid
Description
#he ACC?*0B0*() function analy!es whether the planning ob3ect being currently
processed is detailed or aggregated with regards to the characteristic characteristic
)f detailed, the return value is V:O$ if aggregated, the value is V;O
#he return value of the ACC?*0B0*() function is complementary to the return value
of the (0#?*0B0*() function
A*02#?+(A#0()
A*02#?+(A#0( A*02# ) returns the start date of the earliest valid alert4status of
the alert4status type specified by A*02# for the current selection #he argument of
this function is an alert!status element 6or more information about macro
elements, see the Application 5elp for (emand Planning
A*02#?0(A#0()
A*02#?0(A#0( A*02# ) returns the finish date of the latest valid alert4status of the
alert4status type specified by A*02# for the current selection #he argument of this
function is an alert!status element
A*02#?0W)S#()
A*02#?0W)S#( A*02# ) returns the number of alerts4statuses that e&ist for
alert4status type A*02# for the current selection #he argument of this function is an
alert!status element
A*02#?P2O6)*0?#520S5()
A*02#?P2O6)*0?#520S5( VprofileO $ Valert typeO $ Valert priorityO $ SOalert ob3ect
typeOQ $ SOapplicationOQ) returns the threshold value for a particular alert type and
priority (information, warning, error) in an alert profile
A**O-()
A**O-( n $ m $ W; $ $ Wn T m T ; $ 1; $ $ 1n T m T ; ) returns the open
allocation "uantity that is available for satisfying sales orders, where n is the number
of allocation periods before the current period, m is the number of allocation periods
after the current period, Wi is the allocation "uantity for period i ( i P ; n T m T ; ),
and 1i is the incoming orders "uantity for period i #he arguments can be numbers
that you enter in Operator!function dialog bo&es as well as rows, columns, cells,
or areas from the planning table or au&iliary table
A**O-?.)SA#1()
A**O-?.)SA#1( n $ m $ W; $ $ Wn T m T ; $ 1; $ $ 1n T m T ; ) returns the
amount by which the customer has already e&hausted their allocation, where n is
the number of allocation periods before the current period, m is the number of
allocation periods after the current period, Wi is the allocation "uantity for period i ( i
P ; n T m T ; ), and 1i is the incoming orders "uantity for period i #he arguments
can be numbers that you enter in Operator!function dialog bo&es as well as rows,
columns, cells, or areas from the planning table or au&iliary table
+/-L0#?+(A#0()
+/-L0#?+(A#0( W; $ $ Wn ) returns the earliest start date of the periods given
by the cell&s', row&s', and4or column&s' (not areas) W; through Wn of the planning
table or the au&iliary table #his date is e&pressed in whole numbers with reference
to the date :;:;:::; )n the attributes of the argument elements, you must specify
Period data as the data source
Page 39 of 251
+/-L0#?(A#0?)N()
+/-L0#?(A#0?)N( W $ 1; $ $ 1n ) returns ; if date W falls within the periods
given by the cell&s', row&s', and4or column&s' (not areas) 1; through 1n
Otherwise, : is returned #he date W (for e&ample, the function #O(A1 or (A#0())
is e&pressed in whole numbers with reference to the date :;:;:::; #he argument
can be either a number that you enter in an Operator!function dialog bo&, or one of
the macro elements cell, row, or column from the planning table or the au&iliary
table )n the attributes of the argument elements 1; through 1n, you must specify
Period data as the data source
+/-L0#?(A1S()
+/-L0#?(A1S( W; $ $ Wn ) returns the number of Cregorian calendar days of the
periods given by the cell&s', row&s', and4or column&s' (not areas) W; through Wn )n
the attributes of the argument elements, you must specify Period data as the data
source
+/-L0#?(0S-2)P#)ON()
+/-L0#?(0S-2)P#)ON( W ) returns for the specified column W the te&t that
appears in the column of that period in the planning table
+/-L0#?0(A#0()
+/-L0#?0(A#0( W; $ $ Wn ) returns the latest finish date of the periods given by
the cell&s', row&s' and4or column&s' (not areas) W; through Wn #his date is
e&pressed in whole numbers with reference to the date :;:;:::; )n the attributes
of the argument elements, you must specify Period data as the data source
+/-L0#?'(A1S()
+/-L0#?'(A1S( ScalendarQ $ W; $ $ Wn) returns the number of workdays in the
periods given by the cell&s', row&s', and4or column&s' (not areas) W; through Wn )n
the attributes of the argument elements, you must specify Period data as the data
source #he specification of a calendar as the first argument is optional )f you do not
specify a calendar, the system reads the calendar given by the time stream in the
storage buckets profile )f no time stream is defined, the system uses calendar days
-A*-?022O2
-A*-?022O2 returns the value W if an error has occurred during e&ecution of the
macro
-A*0N(A2()
-A*0N(A2( KlocationK $ Kcalendar typeK $ SversionQ ) returns the calendar of the
specified type that is used by the specified location in the specified version #he
specification of a version as the third argument is optional
-A*0N(A2( A-#?*O-A#)ON $ KPPK ) would return the production planning
calendar of the location you are currently planning
-A*0N(A2?'(A1S()
-A*0N(A2?'(A1S( VcalendarO $ from date $ Sto dateQ ) returns the number of
workdays between the from%date and the to%date in the calendar specified
-+6?()SP*A1?#O?)N#()
-+6?()SP*A1?#O?)N#( row ; $ Nrow n ) writes the displayed values in a -+6
planning book into the internal memory
-+6
-+P?S0#?)N()-A#O2()
-+P?S0#?)N()-A#O2 (KmodeK) switches the display of the -+P progress indicator
on or off #he argument is either KONK or KO66K #he default value is KONK
-+P?S0#?2O/N()NC()
-+P?S0#?2O/N()NC (KmodeK) switches rounding on or off for -+P #he argument
is either KONK or KO66K #he default value is KONK
-O**A+O2A#)ON()
-O**A+O2A#)ON ( NA.0 ) returns a value of ; if you are currently planning
collaboration NA.0$ otherwise, : 1ou enter the name NA.0 of the collaboration as
an argument in an Operator!function dialog bo&
(0*#A?S/.()
(0*#A?S/.( key figure, drilldown level) runs the (0*#A?S/. function for the
specified key figure at the specified drilldown level 6or more information, see SAP
Note F;:D;G #his macro function can only be used at detail level
(0#?*0B0*() Synta1
(0#?*0B0*(#characteristic# $% E&'LUDE(I)P* $G+ID,-* )
-haracteristic P #echnical name of the characteristic that is to be analy!ed
0W-*/(0?).P8 )f you set this optional indicator (KWK), implicitly strong characteristics
are not taken into account in the analysis
C2)(P<8 )f you set this optional parameter, the analysis is applied to the planning
ob3ect of the second grid
Description
#he (0#?*0B0*() function analy!es whether the planning ob3ect being currently
Page 40 of 251
processed is detailed or aggregated with regards to the characteristic
characteristic )f detailed, the return value is V;O$ if aggregated, the value is V:O
01amples
0&ample ;8
1ou have selected the products P; and P< (characteristic 9A.A#N2) DE!(LEVEL(
#./)/!0+# ) will provide the return value K:K for this planning ob3ect because you
are at aggregated level with regards to the characteristic 9A.A#N2
0&ample <8
#he products P; and P< are only in location *; (characteristic 9A*O-NO) due to the
characteristics combinations maintained (in (P) or location products (in SNP) 1ou
have selected the products P; and P< (characteristic 9A.A#N2)
DE!(LEVEL( #./L1'01# ) will provide the return value K;K for this planning ob3ect
because you are at detailed level with regards to the characteristic 9A*O-NO #he
9A*O-NO characteristic is implicitly strong in this case (namely location *;) due to
the selection of products P; and P< and it is used in the analysis
DE!(LEVEL( #./L1'01# % #&# ) will deliver the return value K:K for this
planning ob3ect because implicitly strong characteristics are not used for the
analysis A drilldown to the characteristic VlocationO would characteri!e it e&plicitly
(2)**?(O'N()
(2)**?(O'N( KcharacteristicO , SKinternalKQ, SO-+6OQ ) carries out a drilldown using
the specified characteristic (technical name) #he display is as for (etails (all) in the
planning table )f you set the optional argument Kinternal,K the display is not changed
#his option improves performance if you intend to drill%up in the same macro
subse"uently
Set the V-+6O argument if you are working in a -+6 planning book and the
characteristic is a -+6 characteristic )f you want to drill down on a non%-+6
characteristic, do not set this argument
(2)**?)O+IN.()
(2)**?)O+IN.( drill%down level ) returns the technical name of the characteristic
that was drilled down on at a particular #rill%#on level #he drill%down level can be a
number ;, <, and so on or A-#?*0B0* as the current level
#his function is only available if you have drilled down in the grid using the header or
by using the (2)**%(O'N macro function
(2)**?/P()
(2)**?/P( KcharacteristicO , SKinternalKQ, SO-+6OQ carries out a drill%up using the
specified characteristic (technical name) )f you set the optional argument Kinternal,K
the display is not changed #his option improves performance if you intend to drill%up
in the same macro subse"uently
Set the V-+6O argument if you are working in a -+6 planning book and the
characteristic is a -+6 characteristic )f you want to drill up on a non%-+6
characteristic, do not set this argument
#he same rules for drill%down and drill%up apply as in interactive planning
6)W?-A*-()
6)W?-A*-( W;$ W<8 Sinput checkQ ) performs fi&ing calculation with W; as the row
containing the key figure with the value to be fi&ed and W< the key figure for the fi&ed
values )f the input check indicator is set (for instance W), the system tries to correct
any inconsistencies that may occur due to changes being made on the detail level
6or e&ample, a key figure has, at aggregate level, the value ;:: and at detail level it
has three values (D:, =:, and <:) 1ou then change the last value to >:$ the system
reduces the amounts of the remaining levels so that the total is still ;:: .acros that
use this function should not be used at detail le%el
6O2-ONS?*OC)-() Synta1
6O2-ONS?*OC)-( product $ location )
Product8 Product )(
*ocation 8 -ustomer location )(
#hese arguments can be entered using other operators4functions such as
A-#?P2O(/-#, A-#?*O-A#)ON or as literals in single inverted commas
Description
6O2-ONS?*OC)- returns the value ; if the following conditions are fulfilled8
Page 41 of 251
)n the customer location, the standard consumption logic has been chosen
#he location product has been assigned a re"uirements strategy for which the
assignment mode is Assign customer re"uirements to planning with assembly, for
e&ample, in the standard re"uirements strategy <: E Planning with 6inal Assembly
Otherwise, the function returns the value :
#his function is intended for use with the B.) scenario
6O20-AS#?-ONS/.P#)ON()
Synta1
6O20-AS#?-ONS/.P#)ON( product $ location )
Product8 Product )(
*ocation 8 -ustomer location )(
#hese arguments can be entered using other operators4functions such as
A-#?P2O(/-#, A-#?*O-A#)ON or as literals in single inverted commas
Description
6O20-AS#?-ONS/.P#)ON e&ecutes consumption of the B.) forecast by
customer re"uirements for the given customer location and product
6O20-AS#?P2O6)*0?S0#()
6O20-AS#?P2O6)*0?S0#(KprofileK$ Kprofile typeK$ KversionK$S key figure K)O+IN.KQ )
sets the forecast profile KprofileK for the forecasting type Kprofile typeK (S % univariate,
. % .*2, - % composite) and the version KversionK An optional entry is the key figure
for which the profile is valid, for e&ample, 9A6-S# for the standard forecast key
figure
)O+IN.?BA*/0()
)O+IN.?BA*/0( K)O+IN.K $ KBA*/0K ) determines whether the current selection
contains only data for the specified characteristic value BA*/0 of the )nfoOb3ect
)O+IN. )f yes, the system returns the value ;$ otherwise, : 0nter the arguments in
a dialog bo& of the Operator!function element /se this function to find out, for
e&ample, if the current selection contains data for product BA*/0
)N#02NA*?20SO/2-0?/N)#()
)N#02NA*?20SO/2-0?/N)#( KresourceK $ KversionK ) returns the unit of measure in
which a resource is saved in live-ache
)NB0N#O21?-OS#()
)NB0N#O21?-OS#( KproductK $ KlocationK $ SKversionKQ ) returns the inventory cost of
the specified product at a specified location in the specified version #he third
argument for the version is optional )NB0N#O21?-OS#( A-#?P2O(/-# $
A-#?*O-A#)ON ) returns the inventory cost of the currently planned product in the
currently planned location
)#02A#)ON?-O/N#02
)#02A#)ON?-O/N#02 returns the number of iterations that have been carried out
in the current step
L016S?P*O+()
L016S?P*O+(W) returns the internal number of planning ob3ect in row W )n the
attributes of the argument row, the value in the Data field must be $ow attri+utes.
1ou can use this function as an argument in other macro functions
L016S?B02S)ON()
L016S?B02S)ON( W ) returns the version of the key figure values in row W )n the
attributes of the argument row, the value in the Data field must be $ow attri+utes
*A1O/#BA2?BA*/0()
Synta1
*A1O/#BA2?BA*/0( Kmy?BariableK )
my?Bariable P Name of variables
Description
*A1O/#BA2?BA*/0 () returns the value of the numeric variables 2(Varia"le
1ou must assign this value to the variables first with the function
*A1O/#BA2)A+*0?S0# ()
*A1O/#BA2)A+*0() Synta1
*A1O/#BA2)A+*0( Kmy?BariableK )
Description
*A1O/#BA2)A+*0 () returns the character string of the alphanumeric variables
2(Varia"le 1ou must assign this character string to the variables first with the
Page 42 of 251
function *A1O/#BA2)A+*0?S0# ()
*A1O/#BA2)A+*0?S0#()
Synta1
*A1O/#BA2)A+*0?S0#( Kmy?BariableK $ value)
Balue P numeric value
KBalueK P alphanumeric character string
Description
*A1O/#BA2)A+*0?S0#() assigns the numeric value or the alphanumeric
character string #3alue# to the variable 2(Varia"le )f you want to assign an
alphanumeric character string, you set the argument in single inverted commas, that
is, #3alue# )f you want to assign a numeric value, you use the argument without
single inverted commas 1ou can access the variable 2(Varia"le with the
functions *A1O/#BA2?BA*/0 () and *A1O/#BA2)A+*0 () in other macros of the
same planning book #he content of the variables is deleted when new data is
loaded into interactive planning #he declaration of the type of variables (numeric or
alphanumeric) takes place automatically when setting the variables with
*A1O/#BA2)A+*0?S0# ()
*O-()
*O-( K6)0*(?NA.0K $ SKlocationKQ $ SKversionKQ ) returns the content of a numeric
field in the location master record of the specified location #he arguments for the
location and version are optional )f you do not specify an argument for the location,
the system uses the currently planned location 5owever, it is better for performance
reasons to use the A-#?*O-A#)ON function 6or e&ample, *O-( K(/2A#K $
A-#?*O-A#)ON ) returns the ma&imum duration during continuous move of the
current location
*O-?-()
*O-?-( K6)0*(?NA.0K $ SKlocationKQ $ SKversionKQ ) returns the content of a
character field in the location master record of the specified location #he arguments
for the location and version are optional )f you do not specify an argument for the
location, the system uses the currently planned location 5owever, it is better for
performance reasons to use the A-#?*O-A#)ON function 6or e&ample,
*O-?-( KPA2#N02K $ A-#?*O-A#)ON ) returns the partner for the current location
*O-?0W#2A()
*OC?0W#2A( n $ SKlocationKQ $ SKversionKQ ) gets the value of an e&tra field in the
location master record for the specified location in the specified version, where n
represents the number of the e&tra field 6or e&ample, *O-?0W#2A( ; $
A-#?*O-A#)ON ) gets the value in e&tra field ; for the currently planned location
#he arguments for the location and version are optional )f you do not specify an
argument for the location, the system uses the currently planned location 5owever,
it is better for performance reasons to use the A-#?*O-A#)ON function /se this
function for numeric fields
*O-?0W#2A?-()
*OC?0W#2A?-( n $ SKlocationKQ $ SKversionKQ ) gets the value of an e&tra character
field in the location master record for the specified location in the specified version,
where n represents the number of the e&tra field 6or e&ample, *O-?0W#2A?-( ; $
A-#?*O-A#)ON ) gets the value in e&tra field ; for the currently planned location, if
this field is of type character #he arguments for location and version are optional )f
you do not specify an argument for the location, the system uses the currently
planned location 5owever, it is better for performance reasons to use the
A-#?*O-A#)ON function
*O-?0W#2A?S0#()
*OC?0W#2A?S0#( n $ Kfield?valueK $ SKlocationKQ $ KSversionQK ) sets the value of an
e&tra field in the location master record for the specified location in the specified
version, where n represents the number of the e&tra field and Kfield?valueK
represents the character or numerical value you want to give the field 0nter a
numerical value without single inverted commas #he arguments for location and
version are optional )f you do not specify an argument for the location, the system
uses the currently planned location 5owever, it is better for performance reasons to
use the A-#?*O-A#)ON function
*O-?S0#() *O-?S0#( Vfield nameO $ Kfield?valueK $ SKlocationKQ $ KSversionQK ) sets the value of
the specified field in the location master record for the specified location in the
specified version #he arguments for location and version are optional )f you do not
specify an argument for the location, the system uses the currently planned location
Page 43 of 251
5owever, it is better for performance reasons to use the A-#?*O-A#)ON function
*O-A#)ON?#1P0()
*O-A#)ON?#1P0 ( KlocationK ) returns the location type of the location in the
argument, for e&ample A-#?*O-A#)ON
.A#()
.A#( K6)0*(?NA.0K $ SKproductKQ $ SKversionKQ ) returns the content of a numerical
field in the product master record of the specified product .A#( K+2C0'K $
A-#?P2O(/-# ) returns the gross weight of the current product #he arguments
for product and version are optional )f you do not specify an argument for the
product, the system uses the currently planned product 5owever, it is better for
performance reasons to use the A-#?*O-A#)ON function
.A#?-()
.A#?-( K6)0*(?NA.0K $ SKproductKQ $ SKversionKQ ) returns the content of a
character field in the product master record of the specified product #he arguments
for product and version are optional )f you do not specify an argument for the
product, the system uses the currently planned product 5owever, it is better for
performance reasons to use the function A-#?P2O(/-# 6or e&ample,
.A#?-( KLOS-5K $ A-#?P2O(/-# ) returns the product allocation procedure for
the current product
.A#?0W#2A()
.A#?0W#2A( n $ SKproductKQ $ SKversionKQ ) gets the value of an e&tra field in the
product master record for the specified product in the specified version, where n
represents the number of the e&tra field #he arguments for product and version are
optional )f you do not specify an argument for the product, the system uses the
currently planned product 5owever, it is better for performance reasons to use the
function A-#?P2O(/-# 6or e&ample, .A#?0W#2A( ; $ A-#?P2O(/-# ) gets
the value in e&tra field ; for the currently planned product
.A#?0W#2A?-()
.A#?0W#2A?-( n $ SKproductKQ $ SKversionKQ ) gets the value of an e&tra character
field in the product master record for the specified product in the specified version,
where n represents the number of the e&tra character field #he arguments for
product and version are optional )f you do not specify an argument for the product,
the system uses the currently planned product 5owever, it is better for performance
reasons to use the function A-#?P2O(/-# 6or e&ample, .A#?0W#2A( ; $
A-#?P2O(/-# ) gets the value in e&tra character field ; for the currently planned
product
.A#?0W#2A?S0#()
.A#?0W#2A?S0#( n $ Kfield?valueK $ SKproductKQ $ KSversionQK ) sets the value of an
e&tra field in the product master record for the specified product in the specified
version, where n represents the number of the e&tra field and Kfield?valueK
represents the character or numerical value you want to give the field 0nter a
numerical value without single inverted commas #he arguments for product and
version are optional )f you do not specify an argument for the product, the system
uses the currently planned product 5owever, it is better for performance reasons to
use the function A-#?P2O(/-#
.A#?S0#()
.A#?S0# ( Vfield nameO $ field?valueK $ SKproductKQ $ KSversionQK ) sets the value of
the specified field in the product master record for the specified product in the
specified version #he arguments for product and version are optional )f you do not
specify an argument for the product, the system uses the currently planned product
5owever, it is better for performance reasons to use the function A-#?P2O(/-#
.A#*O-()
.A#*O-( K6)0*(?NA.0K $ SKproductKQ $ SKlocationKQ $ SKversionKQ ) returns the
content of a numerical field in the location4product master record of the specified
product and location #he arguments for product, location, and version are optional
)f you do not specify an argument for the product and4or location, the system uses
the current product4location 5owever, it is better for performance reasons to use the
functions A-#?*O-A#)ON and A-#?P2O(/-# 6or e&ample,
.A#*O-( K+S#.AK $ A-#?P2O(/-# $ A-#?*O-A#)ON ) returns the ma&imum lot
si!e for this location product
.A#*O-?-() .A#*O-?-( K6)0*(?NA.0K $ SKproductKQ $ SKlocationKQ $ SKversionKQ ) returns the
content of a character field in the location4product master record of the specified
product and location #he arguments for product, location, and version are optional
)f you do not specify an argument for the product and4or location, the system uses
the current product4location 5owever, it is better for performance reasons to use the
functions A-#?*O-A#)ON and A-#?P2O(/-# 6or e&ample, .A#*O-( K+0SLXK $
A-#?P2O(/-# $ A-#?*O-A#)ON ) returns the procurement type for this location
Page 44 of 251
product
.A#*O-?0W#2A()
.A#*O-?0W#2A( n $ SKproductKQ $ SKlocationKQ $ SKversionKQ ) gets the value of an
e&tra field in the product4location master record for the specified product and
location in the specified version, where n represents the number of the e&tra field
#he arguments for product, location, and version are optional )f you do not specify
an argument for the product and4or location, the system uses the current
product4location 5owever, it is better for performance reasons to use the functions
A-#?*O-A#)ON and A-#?P2O(/-# 6or e&ample, .A#*O-?0W#2A( ; $
A-#?P2O(/-# $ A-#?*O-A#)ON ) gets the value in e&tra field ; for the currently
planned location product /se this function for numeric fields
.A#*O-?0W#2A?-()
.A#*O-?0W#2A( n $ SKproductKQ $ SKlocationKQ $ SKversionKQ ) gets the value of an
e&tra character field in the product4location master record for the specified product
and location in the specified version, where n represents the number of the e&tra
character field #he arguments for product, location, and version are optional )f you
do not specify an argument for the product and4or location, the system uses the
current product4location 5owever, it is better for performance reasons to use the
functions A-#?*O-A#)ON and A-#?P2O(/-# 6or e&ample,
.A#*O-?0W#2A( ; $ A-#?P2O(/-# $ A-#?*O-A#)ON ) gets the value in e&tra
character field ; for the currently planned location product
.A#*O-?0W#2A?S0#()
.A#*O-?0W#2A?S0#( n $ Kfield?valueK $ SKproductKQ $ SKlocationKQ $ KSversionQK )
sets the value of an e&tra field in the location product master record for the specified
product and location in the specified version, where n represents the number of the
e&tra field and Kfield?valueK represents the character or numerical value you want to
give the field 0nter a numerical value without single inverted commas #he
arguments for product, location, and version are optional )f you do not specify an
argument for the product and4or location, the system uses the current
product4location 5owever, it is better for performance reasons to use the functions
A-#?*O-A#)ON and A-#?P2O(/-#
.A#*O-?S0#()
.A#*O-?S0#(( Vfield nameO $ $ Kfield?valueK $ SKproductKQ $ SKlocationKQ $
KSversionQK ) sets the value of the specified field in the location product master
record for the specified product and location in the specified version #he arguments
for product, location, and version are optional )f you do not specify an argument for
the product and4or location, the system uses the current product4location 5owever,
it is better for performance reasons to use the functions A-#?*O-A#)ON and
A-#?P2O(/-#
PA2#N02()
PA2#N02( NA.0 ) returns the value ; if planning is currently being done by partner
NA.0$ otherwise, : 1ou enter the name NA.0 of the partner as an argument in an
Operator!function dialog bo& /se this function in -ollaborative Planning
P*O+S?6O2?*0B0*()
P*O+S?6O2?*0B0*( W ) returns the number of planning ob3ects on the specified
level where W represents the planning level 6or e&ample, P*O+S?6O2?*0B0*( ; )
returns the number of products in the product group selection if you have first
selected a product group and then drilled down to product level
P2O(/-#?*)60()
P2O(/-#?*)60( W $ SKproductKQ ) returns the value ; if data is selected for e&actly
one product and if the specified date W comes after the phase%in time span and
before the phase%out time span of the product Otherwise, : is returned 6or
e&ample, P2O(/-#?*)60 ( (A#0 ( <::;:<<: ) ) returns the value ; if the product
is in its growth or maturity phrase on 6ebruary <:, <::; #he argument can be either
a number that you enter in an Operator!function dialog bo&, or one of the macro
elements cell, row, or column from the planning table or the au&iliary table #he
argument for product is optional
P2O(/-#?P5)N?0N( or
P2O(/-#?P5)N?0N(()
P2O(/-#?P5)N?0N(( SKC2)(P<KQ $ SKproductKQ ) returns the end date of the
specified productKs launch phase as maintained for the phase%in profile in the
product master record #he arguments for grid < and product are optional )f you do
not specify a product, the system returns the end date of the phase%in time span of
the currently planned product 5owever, for performance reasons, we recommend
that you use the function A-#?P2O(/-# to represent the current product
P2O(/-#?P5)N?S#A2# or
P2O(/-#?P5)N?S#A2#()
P2O(/-#?P5)N?S#A2#( SKC2)(P<KQ $ SKproductKQ ) returns the start date of the
specified productKs launch phase as maintained for the phase%in profile in the
not specify a product, the system returns the start date of the phase%in time span of
Page 45 of 251
P2O(/-#?P5O/#?0N( or
P2O(/-#?P5O/#?0N(()
P2O(/-#?P5O/#?0N(( SKC2)(P<KQ $ SKproductKQ ) returns the end date of the
specified productKs decline phase as maintained for the phase%out profile in the
not specify a product, the system returns the end date of the phase%out time span of
P2O(/-#?P5O/#?S#A2# or
P2O(/-#?P5O/#?S#A2#()
P2O(/-#?P5O/#?S#A2#( SKC2)(P<KQ $ SKproductKQ ) returns the start date of
the specified productKs decline phase as maintained for the phase%out profile in the
not specify a product, the system returns the start date of the phase%out time span of
20SO/2-0?-OS#()
20SO/2-0?-OS#( KresourceK $ Kresource variantK $ (A#0 ) returns the cost of the
specified resource for the specified capacity variant on the specified date
20SO/2-0?0()#()
20SO/2-0?0()#( KresourceK $ KversionK ) returns the value K W K if the resource can
be edited in the specified version, K K if it cannot
20SO/2-0?OB02*OA(()
20SO/2-0?OB02*OA(( KresourceK $ KversionK ) returns the resource overload for
the specified resource in the specified version 6or e&ample,
20SO/2-0?OB02*OA( ( A-#?20SO/2-0 $ A-#?B02S)ON ) might return
;:a
20SO/2-0?20S#1P0()
20SO/2-0?20S#1P0( KresourceK $ KversionK ) returns the resource type of the
specified resource in the specified version 6or e&ample,
20SO/2-0?20S#1P0( A-#?20SO/2-0 $ A-#?B02S)ON ) returns resource
type KPK, K#K, KS,K or K5K (production, transportation, storage or handling) for the current
resource in the current version
20SO/2-0?/N(02*OA(()
20SO/2-0?/N(02*OA(( KresourceK $ KversionK ) returns the resource underload
for the specified resource in the specified version 6or e&ample,
20SO/2-0?/N(02*OA( ( A-#?20SO/2-0 $ A-#?B02S)ON ) might return
;:a
20SO/2-0?/N)#()
20SO/2-0?/N)# ( KresourceK $ KversionK ) returns the unit for the resource that is
contained in the resource master record in the specified version
20SO/2-0?BA2)AN#()
20SO/2-0?BA2)AN#( KversionK $ Kresource?variantK $ Kfrom?dateK $ Kto?dateK )
returns the available capacity for the specified resource variant in the specified time
span
S/.?-A*-()
S/.?-A*-( key figure ) calculates the sum of all detail levels of the specified key
figure
S#(B?(0.AN(?C0#()
Synta1
S#(B?(0.AN(?C0#([ke figure\)
Ley figure P 0nter the name of the combined key figure here (that is, the result key
figure)
Description
#his function combines the values of one or more forecast key figures to form a
single key figure, the combined key figure #he prere"uisite for this function is that
you have maintained the $aster #ata for #e$an# co$bination
S#(B?'2)#0?A*02#S()
Synta1
S#(B?'2)#0?A*02#S()
Description
#his function generates data base alerts for #e$an# co$bination, which the Alert
.onitor displays 1ou must call the function S#(B?(0.AN(?C0#() in the same
macro before the alerts can be generated
#).0S5)6#?+A-L'A2(S()

#).0S5)6#?+A-L'A2(S( W; $ $ Wn $ 1; $ $ 1n ) shifts the values of time
series W; through Wn backward in time by the number of periods given in time series
Page 46 of 251

1; through 1n 6or e&ample8
#he time series look like this8
W ;: <: =: >: D:
1 ; < ; = ;
#he result looks like this8
=: >: =: % D: %
#he value ;: is shifted back one period in time, the value <: is shifted back two
periods in time, and so on
#).0S5)6#?6O2'A2(S()

#).0S5)6#?6O2'A2(S( W; $ $ Wn $ 1; $ $ 1n ) shifts the values of time
series W; through Wn forward in time by the number of periods given in time series
1; through 1n 0&ample8 #he time series look like this8
W ;: <: =: >: D:
1 ; = ; < ;
#he result looks like this8
;: % =: <: 9:
#he value ;: is shifted forward one period in time, the value <: is shifted forward
three periods in time, and so on

#S?C0#()
#S?C0#( K#S?#1P0K $ Kkey?value?;K $ Kkey?value?<K $ Kkey?value?=K $
Svalue?fromQ $ Svalue?toQ ) reads the values of a database time series where
K#S?#1P0K defines the time series type, the second, third and fourth arguments
represent the values from the three possible key fields of the time series, and the
fifth and si&th arguments (which are optional) define the value range that you want
to read
#he mandatory fields have the following types8
#S#1P0 P -5A2 <:
key?value; P -5A2 F:
key?value< P -5A2 F:
key?value= P -5A2 F:
0&ample8 A time series with )( K)KK, KAK$ K+K$ K-K is
)tem ; < = > D F G J 9
Balue ;: ;: <: =: D: D: F: 9: ;<:
#SC0# ( KK)KK, KAK $ K+K $ K-K $ < $ 9 ) returns
;: <: =: D: D: F: 9: ;<:
/se an area as the macro result element
#S?S0#()
#S?S0#( K#S?#1P0K $ Kkey?value?;K $ Kkey?value?<K $ Kkey?value?=K $ from?value $
1; $ $ 1n ) writes values to a database time series where K#S?#1P0K defines the
time series type, the second, third and fourth arguments represent the values from
the three possible key fields of the time series #hese fields are defined for
#S?C0#() #he fifth argument specifies at which bucket the system should start to
write the data (for e&ample, D P start at bucket D) #he value of this argument must
be a whole number ; 1; through 1n are the values to be written #hese values
can be numbers or other functions that define these values
BA*/0?-ON#A)N0(()
BA*/0?-ON#A)N0(( value $ range ) returns the value ; if the value is contained in
the specified range
B0-?*A1O/#BA2)A+*0() Synta1
B0-?*A1O/#BA2)A+*0( Kmy?vectorK [$ from?inde& [$ to?inde& \ \ )
my?vector P Name of vector
from?inde& P )nde& that specifies the start of the interval to be read
to?inde& P )nde& that specifies the end of the interval to be read
Description
#he contents of the vector 2(3ector are assigned to a results area (tableau
element area) Optionally, you can specify an inde& fro2(index so that the
contents of the vector 2(3ector are assigned as of the inde& fro2(index )f you
have specified an inde& fro2(index, you can also specify the inde& to(index so
Page 47 of 251
that the contents of the vector are only assigned to the results area up to the inde&
to(index
B0-?*A1O/#BA2)A+*0?S0#()
Synta1
B0-?*A1O/#BA2)A+*0?S0# ( Vmy?vectorO $ table?element )
my?vector F Name of vector variable
table?element F 2ow, column, cell, or area
Description
B0-?*A1O/#BA2)A+*0?S0#() assigns the numerical values in ta"le(ele2ent
to the vector variable 2(3ector
B0-?*A1O/#BA2)A+*0?APP()
Synta1
B0-?*A1O/#BA2)A+*0?APP ( Vmy?vectorO $ table?element )
my?vector P Name of vector variable
table?element P 2ow, column, cell, or area
Description
B0-?*A1O/#BA2)A+*0?APP() assigns the values in table?element to the vector
variable my?vector
'?ABC?-A*-()
'?ABC?-A*- (key figure with values$ key figure with weighting factors) calculates
the weighted average of the first key figure using the weighting factors given in the
second key figure
ultile%el Functions in the Supply #hain Network
#hese four functions enable you to determine statistical values for use with multilevel scenarios
)n the above graphic e&ample, the figures represent the planned consumption of a product at different levels in the supply
chain for one particular period As well as aggregating the demand from the lower levels the locations also have their own
consumption
#he function ./*#)*0B0*?(0.AN(?.0AN forms the sum of these planned demands, in this case ;:: T ;D: T ;=: T >: T
<: P >>:

#he function ./*#)*0B0*?(0.AN(?BA2 determines the error variance between the planned and actual values for the
whole specified period or if you have not specified a period, the complete past
(0rror variance P where and are the planned and actual values respectively)
Page 48 of 251
#he function ./*#)*0B0*?*0A(?.0AN calculates the planned lead%time for a customer to a receive a product in the
period #he system always uses the longest lead%time that is the values from the critical path #he system considers the time
from the customer back to the ne&t location that has safety stock )n the above graphic the value would be F days
#he function ./*#)*0B0*?*0A(?BA2 determines the error variance between the planned and actual values for the whole
specified period or if you have not specified a period, the complete past
(0rror variance P where and are the planned and actual values respectively)
Date Functions
A*02#?+(A#0()
A*02#?+(A#0( A*02# ) returns the start date of the earliest valid alert4status of the
A*02#?0(A#0()
A*02#?0(A#0( A*02# ) returns the finish date of the latest valid alert4status of the
+/-L0#?+(A#0()
+/-L0#?+(A#0( W; $ $ Wn ) returns the earliest start date of the periods given by the
cell&s', row&s', and4or column&s' (not areas) W; through Wn of the planning table or the
au&iliary table #his date is e&pressed in whole numbers with reference to the date
:::;4:;4:; )n the attributes of the argument elements, you must specify Period data as
the data source
+/-L0#?(A#0?)N()
+/-L0#?(A#0?)N( W $ 1; $ $ 1n ) returns ; if date W falls within the periods given by
the cell&s', row&s', and4or column&s' (not areas) 1; through 1n Otherwise, : is
returned #he date W (for e&ample, the function #O(A1 or (A#0()) is e&pressed in whole
numbers with reference to the date :::;4:;4:; #he argument can be either a number
that you enter in an Operator!function dialog bo&, or one of the macro elements cell,
row, or column from the planning table or the au&iliary table )n the attributes of the
argument elements 1; through 1n, you must specify Period data as the data source
+/-L0#?(A1S()
+/-L0#?(A1S( W; $ $ Wn ) returns the number of Cregorian calendar days of the
periods given by the cell&s', row&s', and4or column&s' (not areas) W; through Wn )n the
attributes of the argument elements, you must specify Period data as the data source
+/-L0#?0(A#0()
+/-L0#?0(A#0( W; $ $ Wn ) returns the latest finish date of the periods given by the
cell&s', row&s' and4or column&s' (not areas) W; through Wn #his date is e&pressed in
whole numbers with reference to the date :::;4:;4:; )n the attributes of the argument
elements, you must specify Period data as the data source
+/-L0#?6)S-A*?P02)O(() see 6)S-A*?P02)O(()
+/-L0#?'(A1S() +/-L0#?'(A1S( ScalendarQ $ W; $ $ Wn) returns the number of workdays in the
periods given by the cell&s', row&s', and4or column&s' (not areas) W; through Wn )n the
attributes of the argument elements, you must specify Period data as the data source
#he specification of a calendar as the first argument is optional )f you do not specify a
calendar, the system reads the calendar given by the time stream in the storage buckets
Page 49 of 251
profile )f no time stream is defined, the system uses calendar days
-A*0N(A2?'(A1S()
-A*0N(A2?'(A1S (VcalendarO$ from date$ Sto dateQ ) returns the number of workdays
between the from%date and the to%date in the calendar specified #he calendar is the
timestream )(
(A#0()
(A#0 (1111..(( ) returns the integer value which corresponds to the number of days
between :::;4:;4:; and the specified date 1ou enter the date 1111..(( in the
format 1111..(( in an Operator!function dialog bo& 6or e&ample, (A#0
(;999:;:;) P G<9GDF /se this function in order to include a fi&ed, known date in a
macro
(A#0?#O?-5A2 ()
Synta1
(A#0?#O?-5A2 (Number o# da"s)
Num+er of days8 Number of days since :::;4:;4:;
Description
(A#0?#O?-5A2 () returns the date as a string #he function calculates the date starting
at :::;4:;4:; and adding the $um%er o# da"s #he system uses the date format that
is saved in user master data
(A1()
(A1( W ) returns the day in a date that is e&pressed in whole numbers with reference to
the date :::;4:;4:; 0&ample8 (A1( (A#0( ;999:<<:)) P <: #he argument can either
be a number you enter in an Operator!Function dialog bo& or one of the macro
elements cell, row, or column from the planning table or au&iliary table
6)S-A*?+(A#0()
6)S-A*?+(A#0( W, Kfiscal year variantK ) returns the start of the posting period that
contains the date W (e&pressed in whole numbers with reference to the date :::;4:;4:;)
1ou can enter the date as (A#0 ( ;999:;:; ) or use other date functions such as
+/-L0#?0(A#0() #he second argument specifies the fiscal year variant
6)S-A*?0(A#0()
6)S-A*?0(A#0( W, Kfiscal year variantK ) returns the end of the posting period that
contains the date W (e&pressed in whole numbers with reference to the date :::;4:;4:;)
1ou can enter the date as (A#0 ( ;999:;:; ) or use other date functions such as
+/-L0#?0(A#0() #he second argument specifies the fiscal year variant
6)S-A*?P02)O(() 6)S-A*?P02)O((W) returns the number of the posting period specified by column W
6)S-A*?10A2 6)S-A*?10A2 (W) returns the fiscal year of the period specified by column W
.ON#5()
.ON#5( W ) returns the month in a date that is e&pressed in whole numbers with
reference to the date :;4:;4:::; 0&ample8 .ON#5( (A#0( ;999:<<: )) P < #he
argument can either be a number you enter in an Operator!Function dialog bo& or one
of the macro elements cell, row, or column from the planning table or au&iliary table
.ON#5?+(A#0()
.ON#5?+(A#0( W ) returns the start date of the month given in the argument in integer
format with reference to the date :::;4:;4:;
.ON#5?0(A#0()
.ON#5?0(A#0( W ) returns the finish date of the month given in the argument in integer
format with reference to the date :::;4:;4:;
P2O(/-#?P5)N?0N( or
P2O(/-#?P5)N?0N(()
P2O(/-#?P5)N?0N(( SKC2)(P<KQ $ SKproductKQ ) returns the end date of the specified
productKs launch phase as maintained for the phase%in profile in the product master
record #he arguments for grid < and product are optional )f you do not specify a product,
the system returns the end date of the phase%in time span of the currently planned
product 5owever, for performance reasons, we recommend that you use the function
A-#?P2O(/-# to represent the current product
P2O(/-#?P5)N?S#A2# or
P2O(/-#?P5)N?S#A2#()
P2O(/-#?P5)N?S#A2#( SKC2)(P<KQ $ SKproductKQ ) returns the start date of the
specified productKs launch phase as maintained for the phase%in profile in the product
master record #he arguments for grid < and product are optional )f you do not specify a
product, the system returns the start date of the phase%in time span of the currently
planned product 5owever, for performance reasons, we recommend that you use the
function A-#?P2O(/-# to represent the current product
P2O(/-#?P5O/#?0N( or
P2O(/-#?P5O/#?0N(()
P2O(/-#?P5O/#?0N(( SKC2)(P<KQ $ SKproductKQ ) returns the end date of the
specified productKs decline phase as maintained for the phase%out profile in the product
product, the system returns the end date of the phase%out time span of the currently
Page 50 of 251
P2O(/-#?P5O/#?S#A2#
or
P2O(/-#?P5O/#?S#A2#(
)
P2O(/-#?P5O/#?S#A2#( SKC2)(P<KQ $ SKproductKQ ) returns the start date of the
specified productKs decline phase as maintained for the phase%out profile in the product
product, the system returns the start date of the phase%out time span of the currently
A/A2#02()
Synta1
A/A2#02 ( $um%er o# da"s )
Description
A/A2#02() returns the "uarter (as a number ; to >) in which the date, e&pressed as the
number of days since :::;4:;4:;, lies 1ou can convert a date in the normal format to
the number of days format by using functions (A#0 or #O(A1
A/A2#02?+(A#0()
Synta1
A/A2#02?+(A#0 ( $um%er o# da"s )
Description
A/A2#02?+(A#0() returns the first date of the "uarter in which the date, e&pressed as
the number of days since :::;4:;4:;, lies 1ou can convert a date in the normal format
to the number of days format by using functions (A#0 or #O(A1
A/A2#02?0(A#0()
Synta1
A/A2#02?0(A#0 ( $um%er o# da"s )
Description
A/A2#02?0(A#0() returns the last date of the "uarter in which the date, e&pressed as
the number of days since :::;4:;4:;, lies 1ou can convert a date in the normal format
to the number of days format by using functions (A#0 or #O(A1
S0ASON?+(A#0
Synta1
S0ASON?+(A#0 ( 'olu2n )
-olumn8 2ow, column, or cell element (data source P column attributes)
Description
#he S0ASON?+(A#0 function determines the start date of a season if all the
characteristic values combinations selected for the planning ob3ect have the same start
date
S0ASON?0(A#0
Synta1
S0ASON?0(A#0 ( 'olu2n )
-olumn8 2ow, column, or cell element (data source P column attributes)
Description
#he S0ASON?0(A#0 function determines the end date of a season if all the
characteristic values combinations selected for the planning ob3ect have the same end
date
#).0S5)6#?+A-L'A2(S() Synta1
#).0S5)6#?+A-L'A2(S( SO0O$Q &rea ' $ &rea ( )
K0K8 optional parameter for controlling the behavior at the end of the period
Area 58 Name of the area that contains the data to be moved
Area 78Name of the area that contains the offsets
#he two areas should have the same length and consist of only one line
Description
#).0S5)6#?+A-L'A2(S() moves the values of the time series in area ' back by the
Page 51 of 251
number of periods specified in area ( )f you set the optional parameter K0K, values that
are moved back beyond the first period in area ;, are either lost or are added to the first
period
6or e&ample8
the time series look like this8
Area ; ;: <: =: >: D:
Area < ; < ; = ;
#he result looks like this if parameter 0 was set8
2esults >: =: : D: :
)f 0 is not set, the result is as follows8
2esult G: =: : D: :
#).0S5)6#?6O2'A2(S()
Synta1
#).0S5)6#? 6O2'A2(S ( SO0O$Q &rea ' $ &rea ( )
K0K8 optional parameter for controlling the behavior at the end of the period
Area 58 Name of the area that contains the data to be moved
Area 78Name of the area that contains the offsets
#he two areas should have the same length and consist of only one line
Description
#).0S5)6#?6O2'A2(S() moves the values of the time series in area ' forward by
the number of periods specified in area ( )f you set the optional parameter K0K, values
that are moved forward beyond the last period in area ;, are either lost or are added to
the last period
#O(A1
#O(A1 returns todayKs date in integer format with reference to the date :::;4:;4:; 6or
e&ample, you can use this function as the argument of another function8
(A1 ( #O(A1 )
'00L ( #O(A1 )
.ON#5 ( #O(A1 )
P2O(/-#?*)60 ( #O(A1 )
'00L(A1 ( #O(A1 )
'00L?+(A#0( #O(A1 )
'00L?0(A#0( #O(A1 )
10A2 ( #O(A1 )
10A2?+(A#0( #O(A1 )
10A2?0(A#0( #O(A1 )
+/-L0#?(A#0?)N ( #O(A1 $ )
'00L()
'00L( W ) returns the week in a date W that is e&pressed in whole numbers with
reference to the date :::;4:;4:; 0&ample8 '00L( (A#0( <:::;<<:)) P D; #he
argument can either be a number you enter in an Operator!Function dialog bo& or one
of the macro elements cell, row, or column from the planning table or au&iliary table
'00L?+(A#0()
'00L?+(A#0( W ) returns the start date of the week in which the specified day W falls
6or e&ample, if todayKs date is 'ednesday, (ecember <:th in the year <:::,
'00L?+(A#0( #O(A1 ) returns <:::;<;J
'00L?0(A#0()
'00L?0(A#0( W ) returns the end date of the week in which the specified day W falls
'00L?0(A#0( #O(A1 ) returns <:::;<<>
10A2?+(A#0()
10A2?+(A#0( W ) returns the start date of the year in which the specified day W falls
10A2?+(A#0( #O(A1 ) returns <::::;:;
10A2?0(A#0() 10A2?0(A#0( W ) returns the end date of the year in which the specified day W falls 6or
e&ample, if todayKs date is 'ednesday, (ecember <:th in the year <:::, 10A2?0(A#0(
Page 52 of 251
#O(A1 ) returns <:::;<=;
'00L(A1()
'00L(A1( W ) returns as a number between ; and G the weekday of a date that is
e&pressed in integer format with reference to the date :::;4:;4:;, where ; P .onday
and G P Sunday 6or e&ample, for Ianuary <:th ;999 '00L(A1( (A#0( ;999:;<: ) )
returns = #he argument can be either a number that you enter in an Operator!function
dialog bo&, or one of the macro elements cell, row or column from the planning table or
the au&iliary table
10A2()
10A2( W ) returns the year of a date that is in whole numbers with reference to the date
:::;4:;4:; 0&ample8 6or Ianuary <:th ;999 10A2( (A#0( ;999:;<: ) ) returns ;999
#he argument can be either a number that you enter in an Operator!function dialog bo&,
or one of the macro elements cell, row or column from the planning table or the au&iliary
table
=eneral and Planning Ta+le Functions
2efer to the following table to find the macro function of your choice #he functions are listed in alphabetical order
-0**?+C()
Synta1
-0**?+C( -olor [$ #ool#ip\ )
-olor8 'hole number color code between : and F>
#ool#ip8 String displayed as a #ool#ip of the cell (optional)
Description
-0**?+C sets the background color of a cell
-0**?6C()
Synta1
-0**?6C( -olor [$ #ool#ip\ )
#ool#ip8 String displayed as a #ool#ip of the cell (optional)
Description
-0**?6C sets the foreground color of a cell
-0**?)NP/#()
Synta1
-0**?)NP/#( +ead(onl(2ode )
2ead?only?mode8 'hole number value :, ;, or <
Description
#he -0**?)NP/# function sets the ready for input status of a cell #he +ead(onl(2ode
parameter determines the status #he value : sets the cellKs status to Not ready for input
#he value ; sets the cellKs status to 2eady for input #he value < determines that the cell
adapts the status of the corresponding row )f no status has been set for the row, the value <
determines that the cell adapts the status of the corresponding column
-0**?*)-ON()
Synta1
-0**?*)-ON( )con [$ #ool#ip\ )
)con8 'hole number icon code between : and <9
#ool#ip8 String displayed as a #ool#ip of the icon (optional)
Description
-0**?*)-ON sets an icon left%aligned in a cell
-0**?2)-ON()
Synta1
-0**?2)-ON( )con [$ #ool#ip\ )
Description
-0**?2)-ON sets an icon right%aligned in a cell
Page 53 of 251
-0**?#OO*#)P()
Synta1
-0**?#OO*#)P( #ool#ip )
#ool#ip8 String displayed as a #ool#ip of the cell
Description
-0**?#OO*#)P sets a #ool#ip for a cell #he #ool#ip can be entered directly as a string or
can be determined using the macro function C0#?#0W# (language%dependent), for e&ample
-5A2?BA*/0S?)NP/#()
-5A2?BA*/0S?)NP/# ( Kdialog?bo&?descriptionK $ Kfield?label?;K $ $ Kfield?label?nK )
prompts the user to enter n character strings in a dialog bo& that appears automatically when
this function is e&ecuted A ma&imum of ;: character strings can be entered #hus, you can
have a ma&imum of ;; arguments for this function As the first argument you specify the te&t
that will appear in the title bar of the dialog bo& 'rite this te&t in single inverted commas with
underscores between each word As the other arguments, you specify the field labels for the
fields in which the user will enter the character strings
-O*?+C()
Synta1
-O*?+C( -olor [$ #ool#ip\ )
-olor8 'hole number color code between : and F>, ;:: and ;F>, or <:: and <F>
#ool#ip8 String displayed as a #ool#ip of the column (optional)
Description
-O*?+C sets the background color of a column
-O*?6C()
Synta1
-O*?6C( -olor [$ #ool#ip\ )
-olor8 'hole number color code between : and F>, ;:: and ;F>, or <:: and <F>
#ool#ip8 String displayed as a #ool#ip of the column (optional)
Description
-O*?6C sets the foreground color of a column
-O*?)NP/#()
-O*?)NP/#( W ) sets the input status of a column )f W P ;, the status of the column is ready
for input )f W P :, the status of the column is read%only #he argument can be either a
number that you enter in an Operator!function dialog bo&, or one of the macro elements
cell, row, or column from the planning table or the au&iliary table 1ou can apply this
function to a column or cell of the planning table )n the attributes of the column or cell, set
the Scope of change to Attri+utes #his applies to Crid ; #o refer to Crid < use W P <: for
read%only, and W P <; for ready for input Similarly W P ;: and W P ;; to refer 3ust to C2)( ;
-O*?*)-ON()
Synta1
-O*?*)-ON( )con [$ #ool#ip\ )
Description
-O*?*)-ON sets an icon left%aligned in a column
-O*?2)-ON()
Synta1
-O*?2)-ON( )con [$ #ool#ip\ )
Description
-O*?2)-ON sets an icon right%aligned in a column
-O*?#OO*#)P() Synta1
-O*?#OO*#)P( #ool#ip )
#ool#ip8 String displayed as a #ool#ip of the column
Description
-O*?#OO*#)P sets a #ool#ip for a column #he #ool#ip can be entered directly as a string
or can be determined using the macro function C0#?#0W# (language%dependent), for
Page 54 of 251
e&ample
-O*?B)S)+*0()
-O*?B)S)+*0( W ) sets the visibility of a column )f W P ;, the column is visible )f W P :, the
column is not visible #he argument can be either a number that you enter in an
Operator!function dialog bo&, or one of the macro elements cell, row, or column from the
planning table or the au&iliary table 1ou can apply this function to a column or cell of the
planning table )n the attributes of the column or cell, set the Data source to Attri+utes #his
applies to Crid ; #o refer to Crid < use W P <: for read%only, and W P <; for ready for input
Similarly W P ;: and W P ;; to refer 3ust to C2)( ;
-O*/.N?62O.
Synta1
-O*/.N?62O.
Description
#he -O*/.N?62O. function provides the inde& of the first column of a macro step interval
(compare A-#?-O*/.N and -O*/.N?#O)
-O*/.N?.A2L0(()
-O*/.N?.A2L0( returns the value ; if the column specified in the argument has been
selected Otherwise the value is : )n the attributes of the row or cell, set the Data source to
$ow Attri+utes
-O*/.N?#O
Synta1
-O*/.N?#O
Description
#he -O*/.N?#O function provides the inde& of the last column of a macro step interval
(compare A-#?-O*/.N and -O*/.N?62O.)
-/22?-ONB?6A-()
-/22?-ONB?6A-( Ksource currencyK $ Ktarget currencyK $ Ke&change rate typeK $ (A#0 )
returns the currency conversion factor for the specified source currency, target currency and
e&change rate type on the specified date #his date can be #O(A1 (that is, the system date)
or another (see the functions (A#0() and #O(A1) #O(A1 is a function, so you do not need
to put it in inverted commas 0&ample8 -/22?-ONB?6A-( K/S(K $ K0/2K $ K.K $ #O(A1 )
(A#A?)S?*O-L0(
(A#A?)S?*O-L0( returns the value ;, if the data is locked for the current user, meaning
they can edit the data )t returns the value :, if the data is locked by another user, meaning
the current user cannot edit the data
()SP*A1?-ONB?6A-#O
2()
()SP*A1?-ONB?6A-#O2 (2ow) returns the conversion factor between the unit in which
the data is stored internally and the unit in which it is displayed for the row 6or e&ample, time
data may be stored in *ive-ache in seconds but it is displayed in the planning table in hours
()SP*A1?-ONB?6A-#O2 would then return =F:: )n the attributes of the row or cell, set the
Data source to $ow Attri+utes
0BA*()
0BA*() is an au&iliary function for constructing more complicated functions 0BA*()
evaluates the arithmetic e&pression in the argument so that this result can be used in another
function #he argument can be either a number that you enter in an Operator!function
dialog bo&, or one of the macro elements cell, row, or column from the planning table or the
au&iliary table
/se this function to calculate the argument of other functions at runtime
6or e&ample 0BA* ( ( ; T < ) Y = ) P 9
C0#?#0W#() Synta1
C0#?#0W#( #e&t)( [$ *anguage\ )
#e&t)(8 #e&t )( for identifying the te&t element to be read
*anguage8 Parameter for specifying the language (optional)
Description
C0#?#0W# returns the language%dependent te&t of the te&t element !extID #he te&t
element !extID must e&ist as a macro te&t in at least one language
)f you do not specify the language parameter, the te&t element is read in the logon
language )f the te&t element is not available in the logon language, it is returned in 0nglish or
in whatever language is available
)f you specify the language parameter, the system first looks for the te&t element in that
language )f the te&t element is not available in this language, it is returned in 0nglish or in
Page 55 of 251
whatever language is available
50*P#A+?-*0A2
50*P#A+?-*0A2 initiali!es the values in the au&iliary table 1ou can use this function
anywhere in a macro )f you wish to initiali!e the values in the au&iliary table at the beginning
of a macro, leave unchecked the macro attribute Do not initialiGe au&iliary table
)S?6)W0(()
Synta1
)S?6)W0(( 4e 5igure )
Ley 6igure8 2ow, column, or cell element (data source P row attributes)
Description
#he )S?6)W0( function returns the value ; if the cell is completely fi&ed (#he column results
from the current step iteration$ the row is determined by the 4e 5igure parameter) )f the
cell is not fi&ed or partially fi&ed, the return value is : #he function is not available if the
compatibility mode is activated for the macro book
)S?)N)#)A*()
Synta1
)S?)N)#)A*( 4e 5igure )
Description
#he )S?)N)#)A* function returns the value ; if the cell is initial (#he column results from the
current step iteration$ the row is determined by the 4e 5igure parameter) Apply this
function for key figures that can distinguish between !ero values and initial values #his
function is not available if the compatibility mode is activated for the macro book
)S?PA2#*1?6)W0(()
Synta1
)S?PA2#*1?6)W0(( 4e 5igure )
Description
#he )S?PA2#*1?6)W0( function returns the value ; if the cell is partially fi&ed (#he column
results from the current step iteration$ the row is determined by the 4e 5igure parameter)
)f the cell is not fi&ed or is completely fi&ed, the return value is : #he function is not available
if the compatibility mode is activated for the macro book
.A2L0(?-O*/.N() or
.A2L0(?-O*/.N
.A2L0(?-O*/.N(SK6)2S#4*AS#KQ) returns the column numbers of all marked columns )f
K6)2S#K or K*AS#K is included as an argument, the function returns the first or last marked
column in the time series K6)2S#K and K*AS#K are the only possible arguments
.A2L0(?P*O+
.A2L0(?P*O+ returns the internal planning ob3ect number of the marked rows /sing this
number has the advantage in comparison to the row number that this number remains
constant irrespective of where the ob3ect appears in the grid
.A2L0(?2O'() or
.A2L0(?2O'
.A2L0(?2O'(SK6)2S#4*AS#KQ) returns the row numbers of all marked rows )f K6)2S#K or
K*AS#K is included as an argument, the function returns the first or last marked row K6)2S#K
and K*AS#K are the only possible arguments
N/.?BA*/0S?)NP/#()
N/.?BA*/0S?)NP/# ( Kdialog?bo&?descriptionK $ Kfield?label?;K $ $ Kfield?label?nK )
prompts the user to enter n numerical values in a dialog bo& that appears automatically when
this function is e&ecuted As the first argument you specify the te&t that will appear in the title
bar of the dialog bo& 'rite this te&t in single inverted commas with underscores between
each word or use the function S#2)NC?-ON-A#0NA#0 () As the other arguments, you
specify the field labels for the fields in which the user will enter the numerical values A
ma&imum of ;: numerical values can be entered #hus, you can have a ma&imum of ;;
arguments for this function
N/.+02()
N/.+02( 0; $ $ 0n ) returns the total number of cells in the macro elements 0; through
0n 0; through 0n can be cell&s', row&s', column&s' and4or area&s' from either the planning
6or instance, you can use this function to determine the number of time buckets in the
current grid
O/#P/#?POP/P
O/#P/#?POP/P(Kdialog?bo&?descriptionK $ Kfield?label?;K $ value in field ; $ $
Kfield?label?;:K $ value in field ;: ) opens a dialog bo& that shows the alphanumeric or
numerical values of e&tra fields in the product and4or location master record A ma&imum of
;: field values can be displayed in this bo&
Page 56 of 251
P*O+?(A#A?B)S)+*0()
P*O+?(A#A?B)S)+*0( W$ Kplanning ob3ectKKplanning ob3ect nK ) sets the visibility of the
specified planning ob3ect(s) 1ou use this function if you are working with drill%down in the
(etails (all) view )f W P; the planning ob3ects are displayed )f WP: the planning ob3ects are
hidden /se functions A-#?P*O+, .A2L0(?P*O+, or L016S?P*O+ to specify the
planning ob3ects
P*O+?.A2L0(()
P*O+?.A2L0( returns the value ; if the planning ob3ect specified in the argument has
been selected Otherwise the value is : /se functions A-#?P*O+, .A2L0(?P*O+, or
L016S?P*O+ to specify the planning ob3ects
20PO2#?S/+.)#()
20PO2#?S/+.)#( Kprogram?nameK $ SK3ob?nameKQ $ SK3ob?numberKQ$ SKnewmodeKQ)
causes the specified program to be e&ecuted /se the optional arguments, 3ob name and 3ob
number, if you wish the program to run in the background )f you set the argument
KnewmodeK, the results are displayed in a new window
2O'?+C()
Synta1
2O'?+C( -olor [$ #ool#ip\ )
#ool#ip8 String displayed as a #ool#ip of the row (optional)
Description
#he function 2O'?+C set the background color of a row
2O'?-*0A2()
Synta1
2O'?-*0A2( ke" #igure)
2ey figure8 2ows of the key figure of the planning area 1ou can enter the key figure two
ways8
b As the internal number of the key figure #his is the position of the key figure in the table
on the Ley 6igure tab page of planning area maintenance
b +y including the row as the argument )n this case you must the data source to 2ow
Attributes in the .acro 'orkbench
Description
2O'?-*0A2() deletes all values of the key figure at aggregate (total) level #he value : is
then disaggregated to all detail levels #hus it is sufficient to e&ecute the macro only at
aggregate level Similarly it is sufficient to include the function in a step with only one
iteration

2O'?6C()
Synta1
2O'?6C( -olor [$ #ool#ip\ )
#ool#ip8 String displayed as a #ool#ip of the row (optional)
Description
#he function 2O'?6C set the foreground color of a row
2O'?)NP/#()
2O'?)NP/#( W ) sets the input status of a row )f W P ;, the status of the cell is set to ready%
for%input )f W P :, the status of the cell is set to read%only #he argument can be either a
number that you enter in an Operator!function dialog bo&, or one of the macro elements
cell, row, or column from the planning table or the au&iliary table 1ou can apply this
function to a row or cell )n the attributes of the row or cell, set the Scope of change to
Attri+utes
Note8 )t is not possible to use this function in con3unction with key figure%specific locking and
the (o not lock read%only key figures option 6or more information, see Key Figure Specific
"ocking
2O'?*)-ON() Synta1
2O'?*)-ON( )con [$ #ool#ip\ )
Page 57 of 251
Description
#he function 2O'?*)-ON sets an icon left%aligned in a row
2O'?.A2L0(()
2O'?.A2L0( returns the value ; if the row specified in the argument has been selected
Otherwise the value is :
2O'?2)-ON()
Synta1
2O'?2)-ON( )con [$ #ool#ip\ )
Description
#he function 2O'?2)-ON sets an icon right%aligned in a row
2O'?#OO*#)P()
Synta1
2O'?#OO*#)P( #ool#ip )
#ool#ip8 String displayed as a #ool#ip of the row
Description
#he function 2O'?#OO*#)P sets a #ool#ip for a row
2O'?BA*/0S?-5ANC
0(()
2O'?BA*/0S?-5ANC0(( W ) returns ; if the user has changed one or more values in row
W in the current planning session since last pressing 0nter )n the attributes of the row, enter
$ow Attri+utes as the data source
Note8 Since you generally choose 0nter when entering values, SAP recommends that you
use macros with this functions as default macros
2O'?B)S)+*0()
2O'?B)S)+*0( W ) sets the visibility of a row )f W P ;, the row is visible )f W P :, the row is
not visible #he argument can be either a number that you enter in an Operator!function
dialog bo&, or one of the macro elements cell, row, or column from the planning table or the
au&iliary table 1ou can apply this function to a row or cell )n the attributes of the row or cell,
set the Scope of change to Attri+utes
S#0P?A20A?S0#()
Synta1
S#0P?A20A?S0#( 6rom%-olumn $ #o%-olumn )
6rom%column8 -olumn inde&
#o%column8 -olumn inde&
Description
#he S#0P?A20A?S0# function sets the step interval of all the following macro steps to
from%column to to%column #his way, the macro step interval that you defined in the
.acro+uilder is overridden 5owever, the step interval of the macro step in which the
S#0P?A20A?S0# function is called is not changed
#he step interval set by the S#0P?A20A?S0# function is valid until the end of the macro
e&ecution or can be cancelled by calling 6!EP(/+E/(6E!( 7 % 7 )
S#0P?-A*-?S#OP
Synta1
S#0P?-A*-?S#OP
Description
#he S#0P?-A*-?S#OP function leaves a macro step after carrying out the current step
iteration Any assignments and macro functions that e&ist after calling S#0P?-A*-?S#OP
will still be e&ecuted
S#2)NCS?-ON-A#0NA
#0()
S#2)NCS?-ON-A#0NA#0(Kstring;KKstringnK) inserts blanks between several character
strings to produce one string
/N)#?-ONB?6A-()
/N)#?-ONB?6A-( NA.0; $ NA.0< ) returns the conversion factor for conversion from unit
NA.0; to unit NA.0< 1ou enter the names of the units in Operator!function dialog bo&es$
for e&ample, /N)#?-ONB?6A- ( LC $ #O ) P ;:::
/S02()
/S02( NA.0 ) P ; if the user name of the person who logged on is NA.0$ for e&ample,
/S02( S/-5AN0L ) P ; if the logon name of the planner is Suchanek Otherwise,
/S02( S/-5AN0L ) P : 1ou enter the argument in an Operator!function dialog bo&
BA*/0?O6?2O'?-5AN BA*/0?O6?2O'?-5ANC0(( W $ 1; $ 1n ) returns ; if the user has changed one or
Page 58 of 251
C0(()
more key figure values in columns 1; through 1n of row W in the current planning session
since last pressing 0nter )n the attributes of the row, enter $ow Attri+utes as the data
source
Attri+utes of acro 0lements
1ou can change the attributes of the various macro elements (macros, steps, conditions, and so on) #he attributes that can
be edited vary with the element type and include the periods for which the element is valid and additional functions
Features
6or each macro element, you can change the name in the attributes
acro
5ere you specify8
'hether the macro can be e&ecuted directly
'hether a confirmation prompt appears when you e&ecute the macro
'hether the au&iliary table is initiali!ed when you call the macro
)f the au&iliary table is not initiali!ed when you call the macro, any values that are in the table from the e&ecution of
previous macros remain in the table and can be used in the current macro All entries in the au&iliary table are lost when
you leave the planning book
'hich change mode is to be performed, for e&ample, a value change or an attribute change (see -hange .ode for
Ley 6igures)
#he level on which the macro is used
#he level is defined by the current drill%down situation #his means in interactive planning that the aggregate level is the
level at which you enter the planning book by making a selection )f you drill down on characteristic A, this is level ; )f
you then drill down on another characteristic (characteristic +), this is level <
'hether cells that have no entries (initial) are left blank or are given the value R:R
#o improve performance, we recommend that you set this indicator
#his indicator does not have any effect on key figures that differentiate between initial values and !ero values
1ou can also assign an icon to the macro that appears in the planning table 1ou can then e&ecute the macro by clicking this
icon
1ou also see if the macro is used as a stan#ar# $acro and if so, which type and at which position the macro appears in the
list for the relevant type (start, e&it, level change, or default)
1ou can also define collective macros #hese consist of other macros in the planning book #hese macros are then e&ecuted
automatically in the given order
1ou define a macro as a collective macro when you create it, by setting the .acro type field to -ollective macro )f you have
already assigned other elements (steps, conditions, and so on) to it, you can no longer define the macro as a collective
macro
Step
)n the step attributes, you primarily define the time period for which the step applies 1ou can specify that it applies to8
#he whole period
#he past
#he future
6reely definable
5ere you can enter e&isting time buckets or columns #his means that the position of the column in the table remains
constant, but that the dates might move 6or e&ample, the macro applies to the second time bucket in the future to the
tenth time bucket in the future
(ate%dependent
5ere the time buckets are selected that contain the specified dates #he dates remain constant, but the time bucket
might change 0&ample8 #he macro is valid from Ianuary :;, <::; to Iune =:, <::; 1ou can specify whether only
those periods are taken into account that is entirely in the specified time frame
'hether the columns at the start and end are ad3usted automatically
Page 59 of 251
#his function is only available if the start column or end column contains the first or last past period or the first or last
future period (see SAP Note FG><=9)
Acti%ities
'hen you create a new macro element, the attribute dialog bo& appears automatically 1ou can access it later via the
conte&t menu, or by double%clicking the element in the workspace
Several of these functions are only available in e&pert mode 1ou can switch the e&port on or off by choosing Settings
0&pert .ode On4Off #his reverts to the default the ne&t time you enter the .acro +uilder #o save the setting in a user%
specific way, choose Settings Save .ode Setting
Standard acros
A standard macro is a macro that is e&ecuted automatically$ the planner does not trigger its e&ecution manually
A standard macro is one of the following types8
(efault
A default macro is e&ecuted when the planner opens the planning desktop and loads data, regenerates the screen (for
e&ample, by choosing 0nter or #ab), or saves the plan )f other types of standard macros can be e&ecuted, these are
e&ecuted before the default macros
*evel change
A level change macro is e&ecuted when the planner drills up or down in interactive planning
Start
A start macro is e&ecuted when the system loads data #his is for instance when a planner selects characteristic values
in the shuffler and loads the data
#he systems always reload data after the user saves the data #his means that start macros are also carried out after
saving
0&it
An e&it macro is e&ecuted when the planner saves the plan
/se
#o define a macro as a standard macro8
1. (rag and drop the macro from the macro tree to the appropriate standard macro icon in the 0vents section of the
.acro+uilder (top right corner)
2. Set the attribute No direct e&ecution for the macro$ as re"uired Since these macros are automatically e&ecuted, it often
makes sense to prevent users from e&ecuting them manually
One possible use of standard macros is to calculate the difference between forecasts of different periods #his is part of the
process for Statistical -rror Analysis
acro Se*uence
1ou can specify in which se"uence the standard macros are e&ecuted #his is the order in which the macros are listed under
the re"uisite heading in the 0vents screen section #his se"uence is also displayed in the .acros screen section of the
.acro 'orkbench #o change the order use drag , drop
01ample
1ou have defined start, end and default macros 1ou have entered or changed data in interactive and now save the planning
book #he system first e&ecutes the end macro and saves the data in live-ache Since it reloads the data, the start macro is
e&ecuted followed by the default macro Note that the data changed by the start and default macros have not been saved
aster Data for Supply Network Planning
.aster data is the essential data (about products, locations, resources, production process models (PP.s), and so on) that
is necessary to build a supply chain model and e&ecute planning
)n addition to the general data mentioned, you also have to create specific master data for each of the planning methods
used in Supply Network Planning (SNP) 6or e&ample, to e&ecute e&tended safety stock planning, you have to enter specific
data on the *ot Si!e tab page in the product master #his specific data includes information about safety stock, safety stock
method, service level, and so on 6or information about the master data considered by the different planning methods, see
the topics listed below
Page 60 of 251
Process
1. 1ou create the general master data for Supply Network Planning
2. 1ou decide which method to use in Supply Network Planning and create the master data specifically for it

#onfiguring aster Data for the OptimiGer
#his section lists all the master data that must be created to successfully run the optimi!er in Supply Network Planning )t
also lists all the re"uired entry fields and other data that the optimi!er takes into account /se this information as a checklist
before you run the optimi!er to make sure you have maintained all the master data for your supply chain model
6or detailed information, see the field%level help (6; help) 6or more information, see the SAP APO master data
documentation
)f you want to work with local time !ones, you have to set the *ocal #ime Xone indicator in .odel and Bersion .anagement
)f you do not set this indicator, we recommend that you use the /T# time !one 'hen using local time !ones, we also
recommend that you use the same time !one for both the location and the planning calendar or for the location and the
resource
Process
1. Bou create locations &that are not product.dependent'.
*ocation type
Storage resource
5andling resource
-alendar
#ime !one
2. Bou create products.
Ta+ Page!Screen Field
5eader (ata +ase /nit of .easure
Attributes
Cross 'eight and /nit
Bolume and /nit
Shelf *ife
/nits of .easure
(efine a conversion from the volume unit into the base unit of measure (based on the unit of
measure of the planning area)
SNP ;
6or customer demand, demand forecast, and the corrected demand forecast *ocation%dependent
penalty costs are also available
No delivery penalty
(elay penalty
.a&imum lateness
SNP <
SNP production hori!on
SNP stock transfer hori!on
#hese two hori!ons are also relevant if you are using Production Planning and (etailed Scheduling
(PP4(S)
#he SNP optimi!er does not consider the forecast hori!on )t calculates total demand as a total of
the forecast plus sales orders )f you want the SNP optimi!er to consider the forecast hori!on, you
can set this by making changes in -ustomi!ing and to the source code #o do this, see SAP Note
>;<DD;
Procurement
Procurement type
Planned delivery time (with e&ternal procurement)
-ost function (with e&ternal procurement)
Procurement costs
Production storage costs
Penalty costs for shortfall of safety stock
C24C) 5andling capacity consumption % if not specified, the optimi!er uses the Bolume specified on
Page 61 of 251
the Attributes tab page as the default value
Storage consumption % if not specified, the optimi!er uses the Bolume specified on the
Attributes tab page as the default value
3. Bou create resources.
1ou have the option of creating the following resource types for Supply Network Planning8
Single%mi&ed resource
.ulti%mi&ed resource
+ucket resources
#ransportation resource
/se single%mi&ed resources or multi%mi&ed resources if the resources are to be used for both Supply Network Planning and
Production Planning and (etailed Scheduling (PP4(S) A bucket resource can only be used for SNP 'e recommend that
you create mi&ed resources if possible Note however that bucket%oriented block planning is possible in PP4(S in con3unction
with SNP only if you are using different resources for block planning in PP4(S and Supply Network Planning 1ou ensure this
by setting the Not SNP%2elevant indicator for the resource used in PP4(S
#o create transportation resources, use the same procedure as for creating bucket resources
6or more information about creating resources, see the resource section in the SAP APO master data documentation
+elow is a list of the data that must be defined for optimi!ation%based planning in SNP
Single.i1ed $esources ! ulti.mi1ed $esources
Standard -apacity
1ou must define the available bucket capacity8
+uckets E )f you choose +uckets from -onti, the PP4(S available capacity is used to generate
the available bucket 1ou can also define a loss factor (for maintenance or setup times, for
e&ample,) here )f you choose .aintain +uckets, you must enter the following additional data8
Period type
Number of periods
+ucket capacity
/tili!ation rate for bucket%oriented capacity (a)
1ou can use the Available +ucket -apacity button to display the defined available bucket capacity
for the individual buckets
1ou can also still define an available capacity profile and capacity variants, and change the
periodicity and capacity of individual buckets 6or more information about this, see the SAP APO
master data documentation
1ou can define costs for the SNP optimi!er in the capacity profile or in the "uantity4rate definition for
the individual capacity variants (for details, see the -apacity variants button section below)
Planning
Parameters
-ross%period lot si!es (only valid for single%mi&ed resources]) % set this indicator if you want to run
SNP optimi!er cross%period lot si!e planning on this resource
)ucket $esources
Ta+
Page!Screen
Field
Ceneral (ata 2esource
2esource category
*ocation E when you define a location, the system refers to the time !one from the location
master data, otherwise you have to enter the time !one
#ime !one
Planner
6actory calendar
Active variant E information about the active variant of a resource is re"uired for live-ache
purposes only )f you have defined multiple capacity variants, you should specify the ma&imum
capacity variant as the active variant or, if this has not been defined, the normal capacity variant
Page 62 of 251
Ta+
Page!Screen
Field
(uring the capacity check in interactive planning, the system considers the active variant 6or
more information, see the e&planation of the -apacity Bariants button
Planning
Parameters
(ay %4(ay T % #he resource capacityOs validity period
-apacity overload (a)
.inimum load (a)
-ross%period lot si!e planning % Activate this indicator if you want to run an SNP optimi!er cross%
period lot si!e planning on this resource
Standard
-apacity
Period type
Number of periods
+ucket capacity
/tili!ation rate for bucket%oriented capacity (a)
-apacity
Bariants +utton

-apacity variant
Balid from4to
-apacity utili!ation
Aty4rate definition
1ou can define multiple capacity variants and use a status indicator to label the available capacity of
this variant as normal capacity, ma&imum capacity, or minimum capacity 1ou can define costs for
using the normal or ma&imum capacity and for falling below the minimum capacity in the "uantity4rate
definition or the capacity profile of the resource #he SNP optimi!er then takes these costs into
account during planning 5owever, the SNP optimi!er only takes into account the minimum available
capacity and the costs you defined for a capacity variant with the status Normal -apacity for
production resources
1ou define the status indicator globally for all resources that have been assigned with the capacity
variant 6rom the resource initial screen, choose -urrent Settings @ -apacity Bariants #he default
value is a ma&imum capacity (blank field) )f you have defined multiple capacity variants with the same
status, the system uses the smallest numbered variant
'e recommend that on the Ceneral (ata tab page you always define the ma&imum capacity variant
as the active variant or, if this has not been defined, the normal capacity variant
#he system includes the default available capacity for periods for which you have not created a
capacity variant )f the normal capacity is below the minimum capacity, the system uses the normal
capacity as the minimum capacity )f the normal capacity e&ceeds the ma&imum capacity, the system
uses the normal capacity as the ma&imum capacity
#he SNP optimi!er does not consider the 'orkdays field for planning #he optimi!er considers the
entries within this field when calculating the available capacity of the capacity variant but always uses
the factory calendar for planning
(efinitions
+utton % the
Auantities42ates
#ab Page
1ou use the Aty42ate (efinition to define the available capacity for the capacity variant
Aty4rate definition (name)
Balid to
Planner
Number of periods
Period type
+ucket capacity
/nit
-osts E 1ou define costs for falling below a minimum capacity or for using a normal or ma&imum
capacity (you define costs for a capacity variant that you assign with status .inimum -apacity,
Normal -apacity, or blank ( P ma&imum capacity) 6or more information, see the -apacity
Bariants +utton section above #he optimi!er only takes into account costs you define for a
capacity variant with status Normal -apacity if the resource is a production resource)
4. Bou assign resources to locations in the location master data.
Page 63 of 251
5. Bou create PP
Ta+
Page!Scree
n
Field
)nitial screen
Plan number
/se of a plan8 S (for SNP)
Operations
(escription of PP.
Single level costs
-ost function (cost profile)
Operation
(escription (of operation)
Activities
)n Supply Network Planning, each activity must be at least one day long or a multiple of one day 0ach
operation can also contain only one activity
Activity number
(escription (of activity)
Activity category
Scrap a
-omponents
Product
)nput4output indicator
6rom date
#o date
/nit of measurement
.aterial consumption (variable)
#ime%dependent data
.odes
.ode % you can specify only one mode per activity
/nit of measure (must be Day)
(uration (fi&ed)
Primary resource (re"uired only if resources are connected to this PP.)
*ocation (re"uired only if resources are connected to this PP.)
2esource consumption (rate) and unit (re"uired only if resources are connected to this PP.)
2esources
2esource (can enter several, but re"uired only if resources are connected to this PP.)
/nit of measure (re"uired only if resources are connected to this PP.)
-alendar resource (for the entire PP.)
Bariable and fi&ed bucket consumption (re"uired only if resources are connected to this PP.)
#ime%dependent data
Activity
relationships
Predecessor4
successor
#ab Pages
Operation name
Activity number
Product plan
assignment
button
PP. and description
Balidity (date4time)
*ocation
(iscreti!ation
+ucket offset
.inimum and ma&imum lot si!e
Page 64 of 251
$esults
After you have configured the master data, you must set up the supply chain $o#el in the Supply -hain 0ngineer, including
the creation and maintenance of transportation lanes, before you can perform any planning runs
aster Data Setup for the Heuristic
#his section lists all the master data you have to create to run the heuristic successfully in Supply Network Planning )t lists
all of the re"uired fields and other data considered by the heuristic /se this information as a checklist before you run the
heuristic to make sure you have created all the master data for your supply chain model
6or detailed information, see the field%level help (6; help) 6or more information, see the APO master data document
resource
Process Flow
1. #reate (ocations &that are not product.dependent'
*ocation type
Storage resource
5andling resource
-alendar (production, shipping)
A#( category groups (for deployment, #*+)
#ime !one
2. #reate products
Ta+
page!screen
Field
)nitial screen and
header data
*ot si!e profile
(emand profile
SNP demand profile
SNP supply profile
(eployment profile
+ase unit
Attributes
Cross weight
Bolume
/nits of .eas
(efine a conversion from the volume unit into the base unit of measure (based on the unit of measure
of the planning area)
*ot si!e
Procedure (lot%for%lot, fi&ed lot si!e etc)
Safety stock method
SNP <
SNP production hori!on
#hese two hori!ons are also relevant if you are using Production Planning and (etailed Scheduling
(PP4(S)
Procurement
Procurement type
C24C)
5andling capacity consumption
Storage consumption
3. #reate $esources &optional'.
1ou have the option of creating the following resource types for Supply Network Planning8
Page 65 of 251
+ucket resource
/se single%mi&ed or multi%mi&ed resources if you want to use the resources for both Supply Network Planning and
Production Planning and (etailed Scheduling (PP4(S) +ucket resources can only be used for SNP 'e recommend that
you create mi&ed resources if possible Note however that bucket%oriented block planning is possible in PP4(S in con3unction
with SNP only if you are using different resources for block planning in PP4(S and Supply Network Planning 1ou ensure this
by setting the Not SNP%2elevant indicator for the resource used in PP4(S
6or general information about creating resources, see the resource section in the APO master data document +elow is a
list of the e&act data you have to define for heuristic%based planning in SNP
Single ! ulti.mi1ed $esources
Ta+
page!screen
Field
Standard
-apacity
1ou must define the available bucket capacity8
+ucket definiton % if you choose 6rom -ont -apacity, the PP4(S available capacity is used to
generate the available bucket capacity 1ou can also define a loss factor here (for maintenance or
setup times for e&ample) )f you choose .aintain, you must enter the following additional data8
Period type
Number of periods
+ucket capacity
2ate of bucket%oriented capacity utili!ation (a)
1ou can use the +ucket -apacity button to display the available bucket capacity that was defined for the
individual buckets
1ou can also still define an available capacity profile and capacity variants, and change the periodicity and
capacity of individual buckets 6or more information, see the APO master data document
)ucket $esources
Ta+
page!screen
Field
Ceneral (ata
2esource
2esource category
*ocation E if you define a location, the system adopts the time !one from the location master data$ if
not, you have to enter the time !one
#ime !one
Planner group
6actory calendar
Active variant
2eference resource
Planning
Parameters
(ay %4(ay T % validity period for the resource capacity
Overload (a)
.inimum load (a)
Standard
-apacity
Period type
Number of periods
+ucket capacity
-apacity
variants
button
1ou can define up to 99 capacity variants in order to define the available capacity for specific validity
periods
-apacity variant
Page 66 of 251
Balid from4to
Auantity4rate definition
#he system takes into account the default available capacity for periods without a capacity variant
(efinitions
button
1ou use the "uantities4rates definition to define the available capacity for the capacity variant
Balid to
Planner group
Number of periods
Period type
+ucket capacity
/nit
4. Bou assign resources to locations in location master data
5. Bou create PP
Ta+
page!screen
Field
)nitial screen
Plan number
/se of a plan8 S (for SNP)
Operations
(escription of PP.
Operation
(escription (of operation)
Activities
)n Supply Network Planning, each activity must be at least one day long or a multiple of one day 0ach
operation can contain only one activity
Activity number
(escription (of activity)
Activity type
Scrap a
-omponents
Product
)nput4output indicator
6rom date
#o date
/nit of measure
.aterial consumption (variable)
#ime%dependent data, if re"uired
.odes
.ode % you can specify only one mode per activity
/nit of measure (must be Day)
6i&ed duration
Primary resource (re"uired only if resources are connected to this PP.)
*ocation (re"uired only if resources are connected to this PP.)
2esource consumption (rate) and /nit (re"uired only if resources are connected to this PP.)
2esources 2esource (can enter several, but re"uired only if resources are connected to this PP.)
/nit of measure (re"uired only if resources are connected to this PP.)
-alendar resource (for the entire PP.)
Bariable and fi&ed bucket consumption (re"uired only if resources are connected to this PP.)
Page 67 of 251
#ime%dependent data, if re"uired
Activity
relationships %
Predecessor4suc
cessor tab pages
Operation name
Activity number
Product plan
assignment
button
PP. and description
Output product
Balidity (date4time)
*ocation
Procurement priority
Period factor
.inimum and ma&imum lot si!e
6. Bou create transportation lanes in the Supply #hain 0ngineer or in master data.
.eans of transport (using the Aggr Planning key figure)
#ransportation calendar
Procurement priority
6or more information, see Supply Chain Mo#el Set /p
7. Bou ha%e the option of creating *uota arrangements in the Supply #hain 0ngineer or in master data.
Auota arrangement at location, e&ternal procurement relationship, or in%house production (PP.)
Auota arrangement (percentage)
)f you do not define any "uota arrangements, you must determine a procurement priority on the transportation lane, or in the
PP. for automatic source determination )f both "uota arrangements and procurement priorities have been defined, the
heuristic includes the "uota arrangements
$esult
Once you have set up the master data, you have to set up the supply chain $o#el in the Supply -hain 0ngineer before you
can perform any planning runs
See alsoC
#he APO master data documentation
#he APO Supply -hain 0ngineer documentation

aster Data Setup for Supply > Demand Propagation
#he master data fields that are supported by Supply , (emand Propagation are listed below
Process Flow
1. 1ou must enter the products and locations and assign the location products to a model
2. 1ou can enter the data, which should be taken into account during Supply , (emand Propagation, in the fields listed
below8
Product aster
Ta+ Field
Attributes
Cross weight and unit
Bolume and unit
S(P relevance &Optional field'
Product (ocation aster
Ta+ Field
Procurement Procurement type
#he procurement type in the location product master is essential for Supply , (emand Propagation +y
choosing a procurement type, you prioriti!e the various procurement options used in propagation #he
options available are8
Page 68 of 251
0 and no PP8 -heck inventory first
0 and PP8 -heck storage location first, then produce
F and no incoming transportation lanes8 -heck storage location first, then create e&ternal
procurement
F and incoming transportation lanes8 -heck storage location first, then create stock transfer
receipts
@ and PP and incoming transportation lanes8 -heck storage location first, then produce, then
use stock transfer receipts
Other com+inations using @8 Analogous to 0 and 6.
P8 -heck storage location first
C24C)
Optional FieldsC
Coods rcpt time
Coods issue time
5and l -ap consumption C2 and unit
5and l -ap consumption C) and unit
aster Data Setup for Aggregated Planning
)n aggregate# planning, you e&ecute the SNP heuristic or the SNP optimi!er at header location product level of a location
product hierarchy #o do so, you must first have made the general master data settings for running the SNP heuristic or the
SNP optimi!er 6or more information, see Master ,ata Setup for the .euristic and Master ,ata Setup for the Opti$i6er #here
are also some distinct features for aggregated planning described below that you must remember when defining the master
data
1ou must define all the master data at sub product level as well as at header product level #hat means that the system
cannot automatically generate the master data from sub product level
)n the following setting recommendations, the use of the word _should` means that planning can otherwise lead to incorrect
or une&pected results
Settings
#reate Products and (ocations
#he following distinct features apply to aggregated planning8
1ou e&ecute aggregated planning at header location product level A header location product is the header product of a
location product hierarchy that you have generated from a location hierarchy and a product hierarchy (see -reate
5ierarchies section) 1ou create all the levels of these two%level hierarchies as standalone products and locations in the
product and location master data
)f you want to plan multiple levels (locations) of your network, the same header products should be defined in all
locations #here should not be any cycles in your network
SNP disaggregation takes into account the rounding values and lot si!e parameters defined for the individual header
and sub products )f you want to ensure that during SNP disaggregation there are no remainders at header product
level, the rounding values defined at sub product level must be the same within a location product hierarchy #he
rounding value of the header product must be a multiple of the value at sub product level )n addition, the minimum lot
si!e at header level should be larger than or e"ual to the minimum lot si!e defined at sublevel
#he procurement type defined at header product level should also be supported at sub product level
#he same SNP production hori!on, e&tended SNP production hori!on, and SNP stock transfer hori!on should be
defined for all products of the location product hierarchy (including the header product)
#reate $esourcesI PP ! PDS and Transportation (anes
#he following distinct features apply to aggregated planning8
)f you carry out optimi!ation%based planning with resources, you must also always create a resource at header product
level #he SNP optimi!er uses the resource and costs defined at header product level for aggregated planning -reating
resources is optional for the SNP heuristic
#o ensure that the resource consumption of fi&ed orders at sub product level is correctly taken into account during
planning, you should note the following restrictions for creating resources8
1ou should use the same resources at header and sub product level )f you use a resource hierarchy, this restriction
does not apply
Page 69 of 251
#he resource consumption of the production process models (PP.s) or production data structures (P(Ss), and
transportation lanes at header and sub product level should be similar
#he total of the resource capacities defined at header product level should form the resource capacity at sub product
level )f you are using several PP.s4P(Ss at sub product level, the resource consumption of the PP.4P(S at header
product level should form the resource consumption of the different PP.4P(SOs at sub product level
6or e&ternal procurement, the same transportation lanes must apply for the header and sub products, since SNP
aggregation and disaggregation use the source determination decisions from header product level
#reate Hierarchies
Standard hierarchy structures are already assigned to the standard planning area 9ASNP:< 1ou can create hierarchies for
location products, resources, and PP.s based on these structures )n SNP -ustomi!ing, you can also create your own
hierarchy structures and assign them to your planning area A standard hierarchy structure is also predefined for a P(S
hierarchy 5owever, it is not assigned to the standard planning area 9ASNP:<, so you have to assign it to your own planning
area
6or more information, see the )mplementation Cuide ().C) under Advanced Planning and Optimi!ation .aster (ata
5ierarchy (efine 5ierarchy Structure
(ocation Product Hierarchy
#o create a location product hierarchy re"uired for the standard aggregated planning process, first create a product hierarchy
and a location hierarchy in the SAP%APO master data 1ou then generate a location product hierarchy from the product
hierarchy and the location hierarchy #he header location product is at the top of a hierarchy tree of this hierarchy #he sub
location products are at the second level A hierarchy can consist of several hierarchy trees
1ou can create the location product hierarchy as a location hierarchy for a product or as a product hierarchy for a location,
for e&ample )n the first instance, you must create a location hierarchy with one header location and multiple child locations
as well as a product hierarchy )n this instance, the product hierarchy can only consist of one hierarchy level and must
contain a sub product )n the second instance (in which you create a product hierarchy for a location), you have to do the
opposite )n addition, when you define the hierarchy structure (see above), you must specify in the 5ierPos field the position
in which the hierarchies will be in the generated location product hierarchy
01ample for #reating a (ocation Product Hierarchy
#he figure shows the different possible combinations when you create a location product hierarchy )n this e&ample, the
product hierarchy consists of header product A with sub products + and - #he location hierarchy consists of header location
; with sub location < )n addition, there are location products A4;, A4<, -4<, and +4=, and location =
#he generated location product hierarchy consists of the following levels8 5eader product4sub location level (level ;) and sub
product4 sub location level (level <) A4< is located on level ; and -4< on level < -4< is subordinate to A4< A4; is not a
component of the generated location product hierarchy since the header product4header location level was not defined in the
generated hierarchy +4= is not a component of the hierarchy since location = is not a component of the location hierarchy
and nor are there any header product4sub location nodes for +4= (which would then have to be called A4=)
PP ! PDS Hierarchy
6or in%house production, you must also create a PP. or P(S hierarchy that contains its own hierarchy tree for each PP. or
P(S at header product level, since SNP aggregation and disaggregation use the source determination decisions of the
header product level #he PP. or P(S hierarchy should be consistent with the location product hierarchy
Page 70 of 251
6or more information about creating hierarchies, see the hierarchy section in the SAP APO master data documentation
$esource Hierarchy
)f you want to display the resource consumption at header level and you are not using the same resources at header and sub
level in the PP.s or P(S, you should create a resource hierarchy so that the resource consumption is displayed correctly
#his hierarchy should be consistent with the PP.4P(S hierarchy used
aster Data Setup for Safety Stock Planning
#his document describes which specific master data you must define for safety stock planning in Supply Network Planning
(SNP) 6or more information, see the associated 6; 5elp
Process
1. (etermine whether you want to use standard or e&tended safety stock planning
2. )f you use standard safety stock planning, enter the relevant data in the following fields on the *ot Si!e tab page in the
location product master8
Safety Stock .ethod E .ethods S+, SX, S. for time%independent determination and methods .+, .X, .. for
time%dependent determination
Safety Stock % is considered by the system during safety stock methods S+ and S.
Safety (aysO Supply % -onsidered by the system during safety stock methods SX and S.
3. )f you use e1tended safety stock planning, enter the relevant data in the following fields on the *ot Si!e tab page in
the location product master8
Safety Stock .ethod E .ethods A#, AS, +# and +S
Service *evel (a)
(emand 6orecast 0rr (a) E -an also be calculated by the system using historical data
2*# 6orecast 0rror (a)E -an also be calculated by the system using historical data
#arget (aysO Supply E (uring safety stock methods A# and +# the system interprets this value as an order cycle
(uring safety stock method +S the system uses this value to calculate the purchase order "uantity
2eplens *ead #ime E -an also be calculated by the system using historical data
.in S6#
.a& S6#
aster Data Setup for the Deployment Heuristic
#his section lists the master data you have to create to run the deployment heuristic successfully in Supply Network Planning
(SNP) )t lists all of the re"uired fields and other data considered by deployment /se this information as a checklist before
you run deployment to make sure you have maintained all the master data for your supply chain model
6or more information, see the SAP APO master data documentation
Process Flow
1. #reate locations (choose the SNP tab page in the location master)
A#( receipt
A#( issue
1ou can define these fields in the location master as well as the location product master (uring the deployment run, the
system first checks whether the category group is specified for the location product )f not, the system checks the entry
at location level )f no category group is defined for the location either, the system uses the standard category groups
AT$ or ATI
1ou define category groups in the -ustomi!ing for SNP under +asic Settings .aintain -ategory Croups
Push not allowed
1ou set this indicator to restrict the locations to which the system distributes the supply available during deployment 6or
e&ample, you may not wish to push supply to a location that has low demand
2. #reate products
(eployment profile
)f you choose fair share rule - or push rule A, the system uses the "uota arrangements defined in the Supply -hain
0ngineer (S-0)$ therefore, you must also define the "uota arrangements when you set up the supply chain model
Page 71 of 251
SNP supply profile
SNP demand profile
SNP < tab page
A#( receipt
A#( issue % (see above)
*ot Si!e tab page
.a&imum lot si!e
2ounding value
)f you have assigned an SNP lot si!e profile for transportation lanes to the relevant transportation lane, the system first takes
into account the rounding data that you have defined in this profile
#he deployment heuristic does not consider the minimum lot si!e or the rounding profile, which you can define on the *ot
Si!e tab page in the location product master data, as well as in the SNP lot si!e profile for transportation lanes
Note in addition that deployment heuristic values generally round down
$esult
After you have set up the master data, you must set up the supply chain $o#el in the Supply -hain 0ngineer before you can
e&ecute a planning run #his includes creating and maintaining transportation lanes
See alsoC
#he SAP APO master data documentation
Supply -hain .odel Setup
aster Data Setup for the Deployment OptimiGer
#his section lists all the master data you have to create to successfully run the deployment optimi!er in Supply Network
Planning )t lists all of the re"uired entry fields and other data that the deployment optimi!er considers /se this information
as a checklist before you run the deployment optimi!er to make sure you have maintained all the master data for your supply
chain model
6or more information, see the SAP APO master data documentation
resource
Process Flow
1. #reate (ocations &that are not product.dependent'
*ocation type
Storage resource
5andling resource
-alendar
A#( category groups (for deployment and the #*+)$ if you do not make any entries, the optimi!er uses default
values
#ime !one
2. #reate products
5eader data +ase unit
Properties
Cross weight and unit
Bolume and unit
Shelf life
/nits of .eas
(efine a conversion from the volume unit into the base unit of measure (based on the unit of
measure of the planning area)
SNP ; Penalty costs for customer demand, the demand forecast, and the corrected demand forecast
(re"uired only for products that fulfill demand$ not re"uired for components)8
Page 72 of 251
No delivery penalty
(elay penalty
.a&imum delay
SNP <
#his hori!on is relevant if you are using Production Planning and (etailed Scheduling (PP4(S)
#he deployment optimi!er does not consider the forecast hori!on )t calculates total demand as a
total of the forecast plus sales orders )f you want the deployment optimi!er to consider the forecast
hori!on, you can set it up by making changes in -ustomi!ing #o do this, see SAP note >;<DD;
*ot Si!e
6i&ed lot si!e
.inimum lot si!e
2ounding value
Procurement
Procurement type
-ost function (with e&ternal procurement)
Procurement costs
Product%dependent storage costs
Safety stock penalty
C24C)
5andling capacity consumption )f not specified, the deployment optimi!er uses the Bolume
specified on the Attributes tab page as the default value
Storage consumption )f not specified, the deployment optimi!er uses the Bolume specified on
the Attributes tab page as the default value
3. #reate $esources
1ou have the option of creating the following resource types for the deployment optimi!er8
+ucket resource
6or general information about creating resources, see the resource section in the APO master data document +elow is a
list of the data that you must specify for deployment optimi!er planning in SNP
)ucket resources
Ceneral (ata
2esource
2esource category
*ocation E if you specify a location, the system refers to the time !one from the location master
data$ if not, you have to enter the time !one
#ime !one
Planner group
6actory calendar
Active variant E information about the active variant of a resource is re"uired for live-ache
purposes only )f you have defined multiple capacity variants, you should specify the ma&imum
capacity variant as the active variant or, if this has not been defined, the normal capacity variant
#he system considers the active variant during the capacity check in interactive planning 6or
more information, see the -apacity variants button section below
Planning
Parameters
(ay %4(ay T % validity period for the resource capacity
Overload (a)
Page 73 of 251
.inimum load (a)
6inite scheduling E is used for lot si!e planning, that is, the set up status from Production
Planning and (etailed Scheduling
Standard
-apacity
Period type
Number of periods
+ucket capacity
-apacity variants
button
-apacity variant
Balid from4to
Auantity4rate definition
1ou can define multiple capacity variants and use a status indicator to label the available capacity of
this variant as normal capacity, ma&imum capacity, or minimum capacity 1ou can define costs for
using the normal or ma&imum capacity and for falling below the minimum capacity in the "uantity4rate
definition or the capacity profile of the resource #he deployment optimi!er then takes these costs into
account during planning 5owever, the optimi!er only takes into account the minimum available
capacity and the costs you defined for a capacity variant with the status Normal -apacity for
production resources
1ou define the status indicator globally for all resources that have been assigned with the capacity
variant 6rom the resource initial screen, choose8 -urrent Settings @ -apacity Bariants #he default
value is a ma&imum capacity (blank field) )f you have defined multiple capacity variants with the same
status, the system uses the smallest numbered variant
'e recommend that on the Ceneral (ata tab page you always define the ma&imum capacity variant
as the active variant or, if this has not been defined, the normal capacity variant
#he system includes the default available capacity for periods that you have not created a capacity
variant for )f the normal capacity is below the minimum capacity, the system uses the normal capacity
as the minimum capacity )f the normal capacity e&ceeds the ma&imum capacity, the system uses the
normal capacity as the ma&imum capacity
#he deployment optimi!er does not consider the 'orkdays field for planning #he optimi!er does
consider the entries within this field when calculating the available capacity of the capacity variant but
always uses the factory calendar for planning
(efinitions button
E the
Auantities42ates
tab page
1ou use the Aty42ate (efinition to define the available capacity for the capacity variant
Balid to
Planner group
Number of periods
Period type
+ucket capacity
/nit
-osts E 1ou define costs for falling below a minimum capacity or for using a normal or ma&imum
capacity (you define costs for a capacity variant that you assign with status8 .inimum -apacity,
Normal -apacity, or blank ( P ma&imum capacity) E for details, see the -apacity variants button
section above #he optimi!er only takes into account costs you define for a capacity variant with
status Normal -apacity if the resource is a production resource)
4. Assign resources to locations in location master data
$esult
After you have set up the master data, you must set up the supply chain $o#el in the Supply -hain 0ngineer before you can
e&ecute a planning run #his includes creating and maintaining transportation lanes
Page 74 of 251
aster Data Setup for the Transport (oad )uilder
)n addition to the general master data settings for planning in Supply Network Planning (SNP), or in the SAP )nventory
-ollaboration 5ub (SAP )-5), you can also make additional settings for the #ransport *oad +uilder (#*+) #he following is
intended to provide an overview of the #*+ settings 6or more information, see the 6; 5elp for the individual fields
6or more information on the master data settings that you can make for the additional #*+ settings in SAP )-5, see
Additional #*+ 6unctions in SAP )-5
Settings
Product aster Data
1ou make the following settings in the product, or location product, master data8
Ta+ Field
Properties
Stacking 6actor
#his fields is relevant if you want to use the Pallet Positions #*+ parameter in the #*+ profile
#he stacking factor indicates how many pallets of a product can be stacked on top of each other
6or mi&ed pallets, the system uses the smallest stacking factor of all products
/nits of .eas
6or the parameters, weight, volume, and pallet positions (only SNP #*+) that you use in the #*+
profile, you must determine conversion of the parameter unit of measure into the base unit of measure
for the product
SNP <
B.) Purchasing Croup
#he #*+ can divide the #*+ shipments into individual orders according to the purchasing group of
the B.) customer
A#( 2eceipt and A#( )ssue
#hese fields are only considered by the SNP #*+ 1ou can enter the category groups that you
have defined in the SNP -ustomi!ing under +asic Settings @ .aintain -ategory Croups /sing
the category groups, you define which order categories are included in the "uantity that is
available for transport load building
)f you do not enter a value here, the system uses the value from the location master data or the
standard category groups AT$ and ATI
*ot Si!e4Auantity
and (ate
(etermination
2ounding value
#he #*+ uses the rounding value for building transport loads 5owever, the #*+ first uses the value
that you have defined in the transportation lane, that is, in the lot si!e profile (SNP) or transportation
guideline set (SAP )-5) )f no value is assigned, the #*+ then uses the value specified here or 5
So that the SNP #*+ can use this rounding value, you must set the relevant indicator in the SNP
-ustomi!ing under +asic Settings @ .aintain Clobal SNP Settings Otherwise, the SNP #*+ uses the
rounding value from the transportation lane
C24C)
5andling unit C
#he #*+ can only pack products with the same handling unit group together in the same han#ling
unit 2./3 )n the SNP #*+, which does not use handling units, this field applies to pallets
.a& -overage
#he #*+ considers the ma&imum coverage time during ship$ent upsi6ing #he system only brings
forward as many #eploy$ent stock transfers as are necessary to cover demand within this time
period
Shipment /psi!ing
6or the location product, you specify whether shipment upsi!ing is allowed and whether is is
permitted beyond the ma&imum coverage time period
*oading Croup
#he #*+ considers the loading group for the straight loa#ing method
Not Palletable
1ou specify whether the location product may be stacked on pallets )f you set this indicator, the
#*+ considers no pallet positions for this product
(ocation aster Data
1ou make the following settings in the location master data8
Page 75 of 251
)nitial screen
*oc #ype
#his field is relevant if you want to use transportation !ones 6or more information, see /se of
!ransportation 7ones
SNP
A#( 2eceipt and A#( )ssue
)f you have not defined category groups for the location product (see above), the SNP #*+
considers the category groups defined here
Transportation (ane aster Data
1ou make the following settings for the means of transport in the transportation lane master data8
Section Field
.eans of
#ransport
#*+ Profile
1ou must assign a !"B profile that you created previously
*oading .ethod
1ou specify whether you want the #*+ to consider the straight loa#ing oder loa# balancing loading
method
Pull%)n 5ori!on
)f the #*+ carries out a shipment upsi!ing, it considers the pull%in hori6on
Si!(esn and Shpmt #hrBal
)n the Si!(ecsn field, you determine how the #*+ calculates the value it uses to decide about
shipment si!ing #he system compares the base value calculated with the value you have entered
in the Shpmt #hrBal field, and then carries out ship$ent upsi6ing or #onsi6ing
Product%specific
transportation
# *ot Prfl
#he SNP #*+ only considers this field 1ou can enter a profile here that you created in the SNP
-ustomi!ing under +asic Settings @ Profiles @ SNP%*ot Si!e Profile (#ransportation *ane) #he
#*+ considers the value defined in this profile (see above)

odel!"ersion #reation
)n this process, you create a model name and assign the model to a planning version so that you can you can model the
supply chain in the Supply -hain 0ngineer in the ne&t step 1ou must define the model name before you can set up the
supply chain model
-reating multiple versions of the model allows you to perform simulative planning and what%if scenarios without corrupting
the supply chain model
Only the active version receives data from 24= via -)6
Process Flow
1. -reate a model name and give it a description
2. Assign the model to at least one planning version
Planning version name and description
SNP8 -hange planning active (set flag to active)
PP4(S8 -hange planning active (set flag to active)
)f you use PP4(S, you must set the PP4(S8 -hange planning active and SNP8 -hange planning active indicators to enable
automatic planning to be triggered or planning file entries to be created when changes relevant to planning occur #hese
indicators are important when converting Supply Network Planning orders into PP4(S orders and vice%versa 1ou must set
these indicators for the target%planning version$ otherwise you will have to plan all orders manually
Planning "ersion erge
1ou use this function to copy selected Supply Network Planning (SNP) key figures that you planned in an APO planning
version (copy of the active version) back into the active version 1ou can limit your selection to location products and SNP
planners
Page 76 of 251
.ultiple SNP planners can first make copies of the active versionOs master data and transaction data8
#he SNP planners then revise these copies within their individual planning environments 0ach SNP planner has his or her
own planning section (product and location)8
#he SNP planners then copy the revised planning versions back into the active version8
1ou have to ensure that the plans of the various SNP planners do not overlap since, when the individual planning versions
are copied back into the active version, the version that is copied back last overwrites the data from all the previously copied
versions
Prere*uisites
1ou have created one or more copies of the active version (:::) as planning versions
An SNP planner has been assigned to all the location products in master data
Page 77 of 251
1ou have authori!ation for the relevant locations and products to copy the data from the planning version back into the
active version (authori!ation ob3ect -?APO?P*N2) #he SNP planner controls authori!ation
Features
1ou can use this function to copy four SNP key figures from a planning version back into the active version PP4(S order
data cannot be copied #he following is a list of the SNP key figures8
Planned Production (key figure 9APP2O(, key figure function <::;)
SNP (istribution 2eceipt (key figure 9APS5)P, key figure function >::;)
(eployment (istribution 2eceipt (key figure 9A6S5)P, key figure function >::D)
Safety Stock (key figure function =::=)
Selection of SNP 2ey Figures
1ou choose the SNP key figures that you want to copy back into the active version in transaction 4SAPAPO4B02.028
Planning area8 )ndicates the SNP planning area that key figures are to be copied from into the active version
Ley figures8 )ndicates the SNP key figures that are to be copied back
Planning version (source)8 Name of the planning version to be copied back
Planning version (target)8 Name of the active version 1ou cannot modify this entry
Product8 Name of one or more location products whose previously chosen key figures are to be copied back #his entry
is optional )f you do not make an entry here, the key figures of all the location products that you are authori!ed to use
and that belong to the underlying model are copied back
*ocation8 *imits you to specific locations whose location products the key figures are to be copied back from #his entry
is optional )f you do not make an entry here, the key figures of the location products you are authori!ed to use are
copied back from all locations belonging to the underlying model
Planner8 *imits you to specific SNP planners whose assigned location products the key figures are to be copied back
from #his entry is optional )f you do not make an entry here, the key figures of the assigned location products you are
authori!ed to use are copied back for all SNP planners belonging to the underlying model
#he copying of planning versions back to the active version is not a copy process in the strict sense of the word )n fact, the
SNP key figures concerned are first deleted from the active version and then recreated in it from the planning versions
(og File #reation
#he system generates a log file for storing messages about the copy process )f you run this process online, the log file is
displayed automatically once the copying is complete
)f you run the process in the background, the log file is created but not displayed 1ou can then call it up using the
identification numbers from the 3ob log
*og file creation is activated by the system and cannot be deactivated
Do Not Permit 0rrors
)f this option is set, copying can only proceed if all ob3ects can be copied without errors )f you do not set this option, it is
possible that not all of the ob3ects will be copied
Test $un
#he system runs the entire copy process as a simulation without actually copying the data into the active version )t runs
through all stages of the copy process (authori!ation checks, log file creation, and so on) apart from the final copy into the
active version #o then start the actual copy process, remove the #est 2un indicator
Stop #IF Jueues
)f this option is set, the system stops all data transfers from 24= systems into the SAP APO system through the -ore
)nterface before starting the copy process Only inbound "ueues in the same system are stopped 1ou have to stop
outbound "ueues in the source system
(uring the copy process, stop -ore )nterface (-)6) using either this function, the monitor, or a background 3ob in order to
prevent lock problems from occurring
#o stop -)6 "ueues, you need authori!ation ob3ect S?A(.)?6-(
#onstraints
SNP orders are not permitted to be published directly into the SAP 24= system -ommunication with the SAP 24= system is
only permitted to take place using the Production Planning and (etailed Scheduling (PP4(S) component #he system
performs a technical check of the corresponding -ustomi!ing for this
Page 78 of 251
)t is not permitted for any releases to be made into or out of SNP until all the planning versions that came from an active
version have been copied back into this active version )n particular, no order is permitted to be converted for PP4(S and no
data can be transferred into the active version from (emand Planning
An authori!ation check is made during the copy process 1ou can only copy key figures for location products whose SNP
planner is assigned to your user
#he copy process ignores scheduling agreement schedule lines
Acti%ities
1. Start transaction8 Supply Network Planning 0nvironment Planning Bersion .erge (4SAPAPO4B02.02)
2. 0nter the necessary SNP key figures, planning version, and re"uired restrictions (product, location, SNP planner)
3. )f re"uired, set the following options8
(o Not Permit 0rrors
#est 2un
Stop -)6 Aueues
-hoose 0&ecute to start the function
4. -hoose Supply Network Planning 0nvironment Planning Bersion .erge8 .essage *og to display the log file
1ou can also call up the log file directly from transaction 4SAPAPO4B02.2.

Supply #hain odel Setup
#he supply chain model consists of individual nodes (locations) and links (transportation lanes) 1ou can assign several
different planning versions to a model )t is also possible to create multiple models for simulation purposes
Only the active version receives data from the 24= system through the -ore )nterface (-)6)
Prere*uisites
1ou have to set up the master data for planning in accordance with how you are using this model8
*ocations
2esources
Products
PP.s
6or more information, see the corresponding SNP documentation sections on setting up master data for the individual
planning methods (the heuristic, the optimi!er, and so on)
Process Flow
1. 1ou create a model and assign ob3ects to it that you want in your model8
*ocations
2esources
Products
PP.
6or more information, see APO .odel .aintenance
2. Add transportation lanes to the model 6or general information about creating transportation lanes, see
#ransportation *ane .aintenance #he SNP%relevant fields are listed below8
5eader data8
#ransportation planner
#he product procurement area8
Procurement priority (heuristic and deployment only)
(istribution priority (deployment only)
6rom and to lot si!es (heuristic only)
0&ternal procurement relationship data (transferred using -)6 E this is relevant when working with scheduling
agreements)
#he means of transport area8
Page 79 of 251
Aggregated planning (indicator must be set)
#ransportation calendar
#ransportation duration
Additional retention period
#ransportation distance
#ransportation costs (optimi!er only)
-ost function (optimi!er only)
#*+ profile (for the #ransport *oad +uilder)
+ucket offset (optimi!er only)
Period factor (heuristic only)
(iscrete means of transport (optimi!er only)
#he product%specific means of transport section8
#ransportation costs (optimi!er only)
-onsumption (of transportation resource)
SNP lot si!e profile for transportation lanes
Stacking factor (for the #ransport *oad +uilder)
3. 1ou maintain "uota arrangements, if re"uired 6or more information about the role of "uota arrangements in supply
source determination within the SNP heuristic, see Source ,eter$ination 2.euristic3 #he optimi!er creates "uota
arrangements automatically during the planning run 6or more information about creating "uota arrangements, see
8uota Arrange$ent Maintenance
Production Data Structure in SNP
Structure containing the master data for planning in SAP APO Production data structures vary in the following ways8
Origin8
Cenerated from iPP0 data (product structure, process structure, factory structure)
Cenerated from SAP 24= data, that is, classical master data, such as bill of materials, phantom assembly, work plan,
and master recipe
)n both cases, the production version serves as the basis for generating the production data structure
Application8
(emand Planning ((P)
Supply Network Planning (SNP)
-apable%to%.atch Planning (-#.)
Production Planning and (etailed Scheduling (PP4(S)
)n SAP APO, the production data structure is used as a source of supply
/se
)n Supply Network Planning, you can use the production data structure as an alternative to the pro#uction process $o#el
2PPM3 Similar to the PP., the P(S is a combination of the work plan and the bill of materials -ompared to the PP., the
P(S offers more fle&ible ways of combining and reusing data from individual work plans and bills of materials
#he SNP P(S is supported by all SNP planning processes, e&cept for demand and stock propagation #here is a further
restriction for the (elete #ransaction (ata function 'ith this function, you cannot select or delete according to specific
P(Ss
#he following options are available for creating an SNP production data structure8
=eneration of an SNP Production Data Structure from iPP0 Data
1ou can either create the iPP0 data in a connected ().P system, and then transfer it to an SAP S-. system using the
APO -ore )nterface (-)6), or you can create the data directly in the SAP S-. system Note that, for SNP, you must use
an SNP work plan in the iPP0 data 1ou then create a product version for the iPP0 data, and generate an SNP
production data structure from there
Page 80 of 251
1ou determine the validity of a product and a location in the production version, as in a PP. or an SAP 24= production
version 1ou can also define costs and enter co%products )f necessary, you can also specify a PP4(S production version
in the production version, which is considered by PP4(S when converting SNP orders into PP4(S orders
=eneration of an SNP Production Data Structure from SAP $!8 Data
1ou can generate the SNP P(S directly from work plan, bill of materials, and production version data in SAP 24= #o do
this, you must select SNP or SNP Subcontracting as the P(S type in the -)6 integration model #he relevant SAP 24=
data is then transferred to the SAP S-. system automatically, and an SNP P(S is then generated from it in the SAP
S-. system
)f you select SNP Subcontracting, the master data (also for components) is automatically created at the subcontractor
location #he transportation lane between plant and subcontractor is also generated automatically (this is not possible
when using SNP PP.)
1ou can also influence the generation of a SNP P(S from SAP 24= data with the following +usiness Add%)ns (+Ad)s)
4SAPAPO4-/2#O?SNP8 1ou can calculate bucket consumption of resources with the
-A*-?+/-L0#?-ONS/.P#)ON method of this +Ad) #his method, which e&ecutes standard calculation of bucket
consumption, is active automatically5owever, you can change the calculation
4SAPAPO4-/**2#OSNP8 )f you want to carry out optimi!ation%based SNP planning, you can use the
6)**?-OS#?6)0*(S method of this +Ad) to fill the SNP P(S cost fields
1ou can use both +Ad)s to change the SNP P(S data to be generated
Once an SNP P(S has been generated, you can only display that source of supply 1ou can make changes in the iPP0 or
SAP 24= 1ou must then, however, regenerate the P(S
#he SNP P(S is used in SNP like the SNP PP. #he source #eter$ination considers all e&isting sources of supply,
irrespective of whether it concerns an SNP PP. or an SNP P(S
Note that most SNP PP. procedures also apply for the SNP P(S #his is not always e&plicitly mentioned in SNP
documentation
1ou cannot generate an SNP P(S from Production Planning and (etailed Scheduling structures (PP4(S P(S)
#he SNP P(S can also be used in -#. planning
See alsoC
6or more information, see the SAP APO master data documentation entitled Production (ata Structure and )ntegrated
Product and Process 0ngineering (iPP0)
=enerating SNP PPs from PP!DS PPs
SAP APO allows you to generate SNP production process models (PP.s) based on e&isting PP4(S PP.s 6or instance,
this may be a good idea if you are using both Production Planning and (etailed Scheduling (PP4(S) and Supply Network
Planning and after the SNP planning want to convert SNP orders into PP4(S orders (uring order conversion, the system is
then able to automatically determine the correct PP4(S PP. mode combination that is appropriate for the SNP order #he
following is a list of the generation options available8
SNP PP. generation with lot si!e margin8
1ou use this generation function to generate SNP PP.s from PP4(S PP.s for lot si!e margins and several mode
combinations of a PP4(S PP. #he system creates an SNP PP. per PP4(S PP. mode combination 6or more information,
see SNP PP. generation with lot si!e margin
As the number of mode combinations and therefore also the number of SNP PP.s will possibly become very large
depending on the number of activities and alternative PP4(S PP. modes, you can choose specific PP4(S PP. mode
combinations for the SNP PP. before the function is run or enter specific parameters to restrict the SNP PP.s generated
6or more information, see specifying mode combinations for SNP PP. generation
SNP PP. generation without lot si!e margin8
1ou use this generation function to generate SNP PP.s from PP4(S PP.s for one individual lot si!e and e&actly one PP4(S
PP. mode combination 0ach generation report run can generate e&actly one SNP PP. corresponding to one specific
PP4(S PP. mode combination 6or more information, see SNP PP. generation without lot si!e margin
6or e&ample, you can use this function when SNP PP. generation with lot si!e margins is not possible
SNP PP =eneration -ith (ot SiGe argin
1ou use the SNP PP. Ceneration 'ith *ot Si!e .argin function to generate SNP production process models (PP.s) from
PP4(S PP.s for lot si!e margins and multiple $o#e co$binations of a PP4(S PP. (ue to the fact that PP4(S PP.s can
Page 81 of 251
have multiple modes defined per activity whereas SNP PP.s can only have one mode per activity, the system generates
one SNP PP. per PP4(S PP. mode combination
Integration
)t is possible that the number of mode combinations and therefore also the number of SNP PP.s generated will become
very large, depending on the number of activities and alternative PP4(S PP. modes 6or this reason, there is a different
function available that you use before running this function to select certain PP4(S PP. mode combinations or enter
parameters in order to restrict the number of SNP PP.s generated 1ou then flag the chosen PP. plans so that they are
considered the ne&t time this function is e&ecuted 6or more information, see Specifying .ode -ombinations for SNP PP.
Ceneration
1ou 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 PP.s generated 5owever, manual
preselection of mode combinations is only possible in the function mentioned above
Prere*uisites
)n the system, you have created the appropriate PP4(S PP.s from which you want to generate the SNP PP.s 6or more
information, see the PP. Plan section of the APO master data document
(uring generation, the system only takes into account multi mi&ed resources or single mi&ed resources that have not been
set with the indicator Not SNP 2el on the Planning Parameters tab page from resource master data Also, the system only
takes into account products with the activated S(P relevance indicator on the Properties tab page within product master
data
Acti%ities
1. 1ou maintain the control parameters for e&ecuting the function 6rom the SAP APO 0asy Access menu, choose .aster
(ata c Production Process .odel c SNP PP. Ceneration 'ith *ot Si!e .argin
On the selection screen, if you leave the PP4(S plan number and SNP plan number fields blank, the flagged PP. plans and
associated control parameters are adopted from the transaction SNP PP. Ceneration8 (etermine .ode -ombinations On
the selection screen, if you specify a specific PP4(S plan number and SNP plan number, you must also enter the associated
control parameters on the screen )f you do not enter any values, the system uses the ma&imum values possible
6or e&ample, you use the control parameters to specify how the operations, activities, and resource consumption from the
PP4(S PP. are transferred to the SNP PP. that has been setup for bucket%oriented SNP planning 1ou can also restrict the
number of SNP PP.s generated by limiting the PP4(S PP. mode combinations considered
#he following control parameters are available8
Parameter /se
Start (ate of
Ceneration
Period
1ou use this date to specify when bucket generation for the SNP PP. plan is to start #he temporary
PP4(S order created by the system, from which the SNP plan is to be generated, is also scheduled from
this start date on
)f possible, you should choose the start date so that the PP. generation hori!on corresponds to a
typical hori!on for your work processes (based on leave periods, public holidays, and so on)
6or generation, it is not possible to shift the start date into the past
+ucket Si!e
1ou use bucket si!e (period length) to specify which PP4(S plan activities are to become an SNP plan
activity during SNP plan generation #o do this, a temporary PP4(S order over a certain lot si!e (typical
order lot si!e, see below) is created by forward scheduling from the Start (ate of the Ceneration Period
specified All activities from the planned order that fall within a bucket of the pre%specified si!e, then
become one production activity in the generated SNP plan #his means that the longer the bucket is, the
more PP4(S plan activities can be included within one SNP plan activity #his production activity is one
day long )f necessary, the remaining time from the bucket is occupied by a wait activity
1ou should choose the bucket si!e so that it corresponds to the period length for SNP planning (that is,
the period length specified in the planning buckets profile)
*owest .ode
Priority
1ou use lowest mode priority to specify which PP4(S plan modes are to be considered for the mode
combination, that is, how many SNP plans are generated .odes with a lower priority than the one
specified here are not considered for SNP plan generation
-onsumption
-alculation
1ou use the consumption calculation parameter to specify how the variables and fi&ed bucket resource
consumptions from SNP plan activities are to be calculated, which means how the corresponding PP4(S
plan consumptions are to be transferred to the SNP plan #here are the following two types of
calculation8
1. -onsumption is calculated on a one to one basis, so that one PP4(S order corresponds to one SNP
order (generation variant without PP4(S campaign)8
#he system uses the fi&ed duration and fi&ed resource consumption from the PP4(S plan plus the
Page 82 of 251
Parameter /se
duration of se"uence%dependent setup activities to calculate the fi&ed bucket consumption of the
SNP plan #he duration of these activities is calculated as the setup duration of an initial setup
group4setup key (as specified in the setup matri&) to the setup group4setup key of the operation
considered Bariable bucket consumption is determined from the PP4(S plan variable duration and
variable resource consumption
2. -onsumption is calculated on a many to one basis, so that n PP4(S orders correspond to one SNP
order (generation variant with PP4(S campaign)8
#he system calculates fi&ed bucket consumption from the duration of se"uence%dependent setup
activities only (see above) #he fi&ed PP4(S plan durations are made linear and go into the variable
bucket consumptions from the SNP plan Bariable durations and resource consumptions are also
used to determine the variable bucket consumption
#ypical Order
*ot Si!e
#his is the lot si!e over which the system creates a temporary PP4(S order #he system uses the
temporary PP4(S order to assign PP4(S PP. operations to the respective SNP buckets (periods) using
normal scheduling rules
As the order length is usually based on the lot si!e, you should enter the typical order lot si!e in this
field 'hen choosing this lot si!e, it should correspond to the typical SNP lead time, because all orders
that you create from the generated SNP PP. receive the duration derived from the temporary PP4(S
order
As a rule, the larger the typical order lot si!e, the longer the duration of activities in the generated SNP
PP. Note that if you choose an order lot si!e that is too large, the duration of activities may e&ceed the
bucket si!e, and the system will not be able to generate an SNP PP. +ecause of this, there are
several options available for determining the typical order lot si!e (see the selection help)
.a&imum
Number
1ou use this parameter to specify an upper limit on the number of SNP plans to be generated
)f this number is e&ceeded, the system terminates generation
2. 1ou run the function
3. #he system generates SNP PP.s from the specified PP4(S PP.s according to the parameters you defined
4. )t is possible to view the results of the function and messages in a log 6rom the SAP APO 0asy Access menu, choose
.aster (ata c Production Process .odel c SNP PP. Ceneration8 (isplay *og
Specifying ode #om+inations for SNP PP =eneration
1ou use this function before running SNP PP. Ceneration with *ot Si!e .argin to choose certain PP4(S PP. mode
combinations for the SNP%PP.s or to enter specific parameters in order to restrict the number of SNP PP.s generated
+ecause the automatic generation function generates e&actly one SNP PP. per PP4(S PP. mode combination, it is
possible that the number of SNP PP.s generated will become very large, depending on the number of activities and
alternative PP4(S PP. modes After you have made your selection, you can flag the PP. plans so that they are part of the
ne&t run of SNP Ceneration with *ot Si!e .argin
#his function can also be used to change the mode combinations and parameters for SNP PP. plans that have already
been generated by the SNP PP. Ceneration with *ot Si!e .argin function (for e&ample, you can choose new mode
combinations), and then flag the plans for a new generation report run
Prere*uisites
)n the system, you have created the appropriate PP4(S PP.s from which you want to generate the SNP PP.s 6or more
information, see the PP. Plan section of the APO master data document
(uring generation, the system only takes into account multi mi&ed resources or single mi&ed resources that have not been
set with the indicator Not SNP 2el on the planning parameters tab page from resource master data Also, the system only
takes into account products with the activated S(P relevance indicator on the Properties tab page within product master
data
Procedure
1. 6rom the SAP APO easy access menu, choose .aster (ata c Production Process .odel c SNP PP. Ceneration8
(etermine .ode -ombinations #he Select 'orklist screen appears
2. )n the upper part of the screen, specify a PP4(S PP. plan or range of PP4(S plans that you want to convert into SNP
PP. plans using the SNP Ceneration with *ot Si!e .argin function (you can also choose PP4(S 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 PP. Ceneration with *ot Si!e .argin function, which you want to change and flag
to be run in a new generation report run
Page 83 of 251
3. -hoose #he .ode -ombinations for Ceneration of SNP Plans screen appears
4. #he PP. plans you selected in the selection screen are displayed in the upper table
1ou first specify a name in the SNP Plan field )f you give a name without a placeholder, the system provides the
appropriate SNP plan number at the end of this name (such as SNP Plan:; and SNP Plan:<) when generating multiple
SNP plans for one PP4(S plans (one SNP plan is generated per PP4(S plan mode combination) 5owever, you can also
add the placeholder d at the end of the name or insert it at any point in the name )f you choose this option, the system
replaces the placeholder with the relevant number 1ou can also leave the field blank and use the SNP Name button
to have the name automatically generated by the system )t is formed like this8 Name of PP4(S Plan?SNP (if re"uired
T?Number )
)n the Cenerated field, you are shown whether the SNP plan has already been generated from the PP4(S plan manually
or automatically (which means with or without manual mode combination determination) using the SNP PP. Ceneration
with *ot Si!e .argin function
)n the other fields from the upper table, you specify parameters to control SNP PP. Ceneration that can be maintained
both in this function and in the SNP PP. Ceneration with *ot Si!e .argin function )f 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 PP4(S plan number and SNP plan number blank 6or more information on these
parameters, see SNP PP. Ceneration with *ot Si!e .argin or the corresponding 6; help
5. )f you double click on a PP4(S plan, the operations and activities of this plan are displayed in the lower table )t is now
possible to use the selection help to choose a specific mode for each activity 1ou can only choose one mode per
activity as only one mode is valid per activity in an SNP PP. 'hen the SNP PP. Ceneration with *ot Si!e .argin
function is run at a later point, e&actly one SNP PP. is generated for the PP4(S PP. mode combination chosen
)f you choose 3ust one mode combination, the other parameters for restricting the number of SNP PP.s generated
(such as lowest mode priority) are ignored
6. 1ou can run checks on the validity of mode combinations and the ma&imum number of SNP plans generated
)f you choose , the system checks whether valid mode combinations e&ist 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 subse"uent change to the PP4(S mode
combinations or that no valid mode combinations e&ist because a lowest mode priority has been specified
)f you choose .a&imum Number, a check is made to see whether the number of SNP plans to be generated e&ceeds
the value entered in the .a&imum Number field (the generation report does not terminate if this value is e&ceeded) )f
the value is e&ceeded, you can restrict the number by choosing the lowest mode priority, for e&ample, or by specifying a
specific mode combination
7. After you have entered the mode combinations, choose Adopt #he system saves your selection and generates a name
for the corresponding SNP plan (for rules, see above) )f you choose -ancel, your changes are undone
8. Set the 6lag indicator for the PP4(S plan )f you set the indicator, the PP4(S plan will be taken into account in the ne&t
run of the generation report +y pressing the 6lags button, you can set or delete all flags automatically
9. Save your entries
$esult
#he PP. plans you flagged are taken into account within the ne&t run of the SNP PP. Ceneration with *ot Si!e .argin
function
SNP PP =eneration -ithout (ot SiGe argin
#his involves generating an SNP production process model (PP.) from an e&isting PP4(S PP. Note that this concerns this
PP. constellation only )n this process, all SNP%relevant product and resource consumptions from the e&isting PP4(S PP.
are determined for a lot si!e and grouped together into SNP operations and activities )f you wish to generate SNP PP.s
from PP4(S PP.s for lot si!e margins and several mode combinations of a PP4(S PP., use the generation report SNP
PP. Ceneration 'ith *ot Si!e .argin
#o call up the SNP PP. Ceneration 'ithout *ot Si!e .argin generation report, choose .aster (ata c Production Process
.odel c SNP PP. Ceneration 'ithout *ot Si!e .argin from the SAP APO 0asy Access menu
Prere*uisites
#o be able to generate and to use the transaction, you must note the following points8
1ou have an active PP4(S PP.
#he SNP PP. is generated e&clusively for the specified lot si!e, since no variable durations or consumptions can be
taken into account
Page 84 of 251
)n the generation process, only single or multi%mi&ed resources for which the Not SNP 2el indicator has not been set on
the Planning Parameters tab page are taken into account )n addition, only those products for which the S(Prelevance
indicator has been activated on the Properties tab page of the product master data are taken into account
Operations and activities in the SNP PP. do not necessarily match those of the PP4(S PP. from which they were
generated #he 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
Acti%ities
/sing the plan or PP. entered and the lot si!e, an order is dispatched infinitely to live-ache (without taking into account
resource schedules that possibly e&ist)
/sing 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 e&plosion, are relevant for
generating the SNP PP.
-onsecutive consumptions of the same type are consolidated into one activity, while bucket durations and material
consumptions are added together
)f a new component or resource is added to, or removed from a bucket in an SNP PP., a new activity is generated in
this SNP PP.
)f there is a change of primary resource, the system generates a new operation )f several PP4(S activities with different
primary resources lie within an SNP bucket, the system checks the resources to see whether the dimensions are the
same #he primary resource for the SNP mode is then determined from the PP4(S activity with the highest resource
consumption
(ata from the setup matri& is only relevant if the Setup indicator has been set for a setup activity
Only fi&ed consumptions and durations can be generated within the SNP plan, because the consumptions arising are
determined via a dummy order (fi&ed lot si!e) 5owever, if the SNP PP.s generated are also to be valid for lot si!e
margins, the variable portions must likewise be manually calculated out of the fi&ed portions (see also SNP PP.
Ceneration 'ith *ot Si!e .argin)
)n calculating the bucket consumption, the planned delivery time is also considered )f, for e&ample, a planned delivery
time of one day has been specified, the system generates a wait activity for this time )f a PP. 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 te&ts8
Plan
Product plan assignment
Operation
Activity
#his manual maintenance is necessary because the te&ts cannot be adopted from the PP4(S PP. automatically
$elease of Forecast Data
1ou can release forecast data to Supply Network Planning (SNP) (epending on your approach, you can choose between
the following release methods8
1ou load data into a (emand Planning planning area and then release the data 6or more information, see 2elease of
the (emand Plan to Supply Network Planning
1ou release the data directly from an )nfoProvider 6or more information, see 2elease from an )nfoProvider to SNP
$elease of the Demand Plan to SNP
#his process makes the demand plan available to the supply chain planner if the supply chain planner performs Supply
Network Planning using live-ache orders #he process also makes the data available in Production Planning and (etailed
Scheduling (PP4(S), depending on the hori!ons that have been maintained for the products involved (6or more information,
see the input help for the SNP Prod 5or field of the location product master E SNP < tab) )n SNP, the supply chain planner
can then use the demand plan as a basis for making sourcing, deployment, and transportation decisions #he actual
production is then planned in PP4(S
6rom a technical point of view, you are copying data from live-ache time series ob3ects to a forecast category in the
live-ache orders
Page 85 of 251
)f Supply Network Planning is performed in live-ache time series, see Copy Manage$ent
)n a separate process, the supply chain planner releases the SNP plan to (emand Planning #he data of particular
categories in the SNP plan, which has been created or changed by the supply chain planner, is thereby copied to a
predefined key figure in a (P planning book 5ere, you can perform reporting on the released data and, in particular,
compare the original RunconstrainedR demand plan with the RconstrainedR SNP plan 6or more information, see !ransfer of the
SNP Planning +esults
Prere*uisites
1ou have created product master records for your products
1ou have created location master records for your locations
1ou have set up your supply chain models
)f you are using #escriptive characteristics, you need to have previously created a consu$ption group and assigned
it to the relevant products
)f applicable, you have defined the location split for the release to Supply Network Planning 6or more information, see
*ocation Split
)f applicable, you have defined a product split 6or more information, see Pro#uct Split
Process Flow
#here are two methods for releasing data to SNP8
Online
1ou can release small amounts of data using an online transaction 6or more information, see 2eleasing the (emand Plan
Online
)n the background
1ou plan mass releases as background 3obs that can then be e&ecuted when there is little system activity 6or more
information, see +eleasing the ,e$an# Plan ith Mass Processing
$esult
01ample 5
1ou create a demand plan in months in (emand Planning #he storage buckets profile contains weeks and months #he
technical periods in which the data is stored are as follows8
Time Span of Technical Period
Num+er of Days
in Technical Period
Planned Demand
Juantity
.onday and #uesday, 6ebruary <J and <9 < >:
'ednesday, .arch ; through Sunday, .arch D D ;::
.onday, .arch F through Sunday, .arch ;< G G:
.onday, .arch ;= through Sunday, .arch ;9 G G:
.onday, .arch <: through Sunday, .arch <F G G:
.onday, .arch <G through Sunday, .arch =; D D:
Saturday and Sunday, April ; and < < <:
6or the release to Supply Network Planning, you do not specify a planning buckets profile or a daily buckets profile. 1ou
specify a release hori!on from .arch ; through .arch =; #he system reads the following data and releases it in the same
periods to Supply Network Planning #he shipping calendar of the location determines which days are workdays in Supply
Network Planning )n this e&ample, all days from .onday through Sunday are workdays
From.Date To.Date Planned Demand Juantity
.arch ; .arch D ;::
.arch F .arch ;< G:
.arch ;= .arch ;9 G:
.arch <: .arch <F G:
.arch <G .arch =; D:
Page 86 of 251
01ample 7
1ou create a demand plan in months in (emand Planning #he storage buckets profile contains weeks and months #he
technical periods in which the data is stored are as in e&ample ; above
6or the release to Supply Network Planning, you do not specify a planning buckets profile$ you specify a daily buckets profile
with ;< days 1ou specify a release hori!on from .arch ; through .arch =; #he system reads the following data8
.arch ; .arch D ;::
.arch F .arch ;< G:
.arch ;= .arch ;9 G:
.arch <: .arch <F G:
.arch <G .arch =; D:
#he following demands are released to Supply Network Planning #he shipping calendar of the location determines which
days are workdays in Supply Network Planning )n this e&ample, all days from .onday through Sunday are workdays
Period Planned Demand Juantity
.arch ; <:
.arch < <:
.arch = <:
.arch > <:
.arch D <:
.arch F ;:
.arch G ;:
.arch J ;:
.arch 9 ;:
.arch ;: ;:
.arch ;; ;:
.arch ;< ;:
.arch ;= through ;9 G:
.arch <: through <F G:
.arch <G through =; D:
01ample 8
1ou create a demand plan in months in (emand Planning
For the release to Supply Network PlanningI you specify a planning +uckets profile containing months only +ut no
daily +uckets profile. 1ou can specify a planning buckets profile only when releasing data online 1ou specify a release
hori!on from .arch ; through .arch =; #he system reads the following data and releases it in the same period to Supply
Network Planning
.arch ; .arch =; =F:
01ample 6
1ou create a demand plan in months in (emand Planning
For the release to Supply Network PlanningI you specify a planning +uckets profile containing months onlyI as well
as a daily +uckets profile containing 57 days. 1ou can specify a planning buckets profile only when releasing data online
1ou specify a release hori!on from .arch ; through .arch =; #he system reads the following data8
.arch ; .arch =; =F:
#he following demands are released to Supply Network Planning #he shipping calendar of the location determines which
days are workdays in Supply Network Planning )n this e&ample, all days from .onday through Sunday are workdays
Period Planned Demand Juantity
Page 87 of 251
.arch ; =F:4=; P ;;F
.arch < =F:4=; P ;;F
.arch = =F:4=; P ;;F
.arch > =F:4=; P ;;F
.arch D =F:4=; P ;;F
.arch F =F:4=; P ;;F
.arch G =F:4=; P ;;F
.arch J =F:4=; P ;;F
.arch 9 =F:4=; P ;;F
.arch ;: =F:4=; P ;;F
.arch ;; =F:4=; P ;;F
.arch ;< =F:4=; P ;;F
.arch ;= through =; =F: % (;< Y ;;F) P <<:J
#he number of decimal places to which the system rounds depends on the number of decimal places defined for the unit of
measure in -ustomi!ing
)n mass processing, the release hori!on is given by the hori!on attached to the data view that you specify in the mass
processing activity and 3ob
#he Period Split on the SNP< tab page of the product master record also determines the results of the release to SNP 6or
more information, see the input help for this field
)f you plan in weeks in Supply Network Planning, the system aggregates the daily "uantities into weekly buckets
)f you re"uire a time split other than the ones illustrated above, use functional enhancement APO(.:;G (transaction
-.O()$ for e&ample, if you want to create demand "uantities in Supply Network Planning on day one and day ;D of every
month
#wo +usiness Add%)ns (+Ad)s) are also available for the release function8
-hange (ata (uring 2elease to SNP
Set 2e"uirements Strategy (uring 2elease
6or more information, see the )mplementation Cuide ().C) for (emand Planning under +usiness Add%)ns 2elease to
SNP
$eleasing the Demand Plan Online
/se this procedure to release a limited amount of data (a few product 4 location combinations only) from (emand Planning to
Supply Network Planning (o not use it for mass releases, for e&ample large planning books
)f you try to release too much data with this transaction, memory problems are likely, since the system tries to read all the
data simultaneously 6or mass processing, use the procedure described in +eleasing the ,e$an# Plan ith Mass Processing
Prere*uisites
See +elease of the ,e$an# Plan to SNP
Procedure
1. On the SAP 0asy Access screen, choose (emand Planning Planning 2elease 2elease to Supply Network
Planning
Field 0ntry
(ata Source8
Planning Area
#he planning area from which you want to release the demand plan$ that is, the source planning area
(ata Source8
Planning Bersion
#he version from which you want to release the demand plan
(ata Source8
Ley 6igure
#he key figure that represents the demand plan
#arget8 #he version to which you want to release the demand plan
Page 88 of 251
Planning Bersion
#arget8 -ategory
#he order category
-ategories serve to group orders according to different kinds of stocks, goods receipts, goods issues
and order types 0nter a category that represents orders or forecasts such as 6A or 6+ #he system
creates demand orders with reference to the category in the live-ache order area (also called Order
live-ache) #he category is determined during the release to SNP as follows8
1. 5as a category been entered in the release profile7 )f yes, this category is used
2. )f no, has a category been set in the definition of the re"uirements strategy in -ustomi!ing7 (1ou
define the productOs strategy in the Proposed strategy field on the (emand tab page of the
product master record) )f yes, this category is used
3. )f no, the category 6A (forecasts) is used
Add data
)f you set this indicator, new order "uantities are created in SNP when you release the demand plan
from (emand Planning to SNP #he system ignores e&isting orders in the same SNP version for the
same product, location and periods #his means that if you release to SNP twenty times, twenty
separate orders are created in SNP
)f you do not set this indicator, e&isting order "uantities in the same SNP version for the same product,
location and periods are overwritten
Set this indicator only in e&ceptional circumstances
6rom%(ate
A date that defines the beginning of the release hori!on
An entry in this field is compulsory
#o%(ate
A date that defines the end of the release hori!on
An entry in this field is compulsory
Planning
+uckets Profile
A planning buckets profile that determines how the demand plan is read from live-ache time series for
the release to Supply Network Planning
#he use of a planning buckets profile for the release from (P to SNP is optional )f you use a planning
buckets profile, the system releases the demand plan in the buckets in which data was planned #he
planning buckets profile must be as big as or bigger than the release hori!on specified by the 6rom
and #o dates
)f you do not enter a planning buckets profile, the data is read in technical periods #he storage
buckets profile determines what the technical periods are #echnical periods are not visible to the
demand planner
#he period split also determines how the demand plan is released to SNP 1ou set the period split in
the product master record (the SNP< tab)
See also the e&amples in +elease of the ,e$an# Plan to SNP
(aily +uckets
Profile
A planning buckets profile containing days if you wish demand orders to be created in Supply Network
Planning in daily buckets
#he use of a daily buckets profile containing days to release the demand plan to SNP is optional )f
you use a daily buckets profile, it must contain days only
(uring the release, the system works forward in time 6or e&ample, if your daily buckets profile
contains >: days, the system releases data to8
#he >: workdays starting on and following the 6rom date if you are releasing the data online
#he first >: workdays of the planning hori!on if you perform the release using mass processing
#he planning hori!on that is used is the planning hori!on of the data view you specify in the mass
processing activity and 3ob .ake sure the planning hori!on begins in the future, unless you want
to release data in the past
#he factory calendar determining which days are workdays is the shipping calendar that you enter in
the location master record
#he period split also determines how the demand plan is released to SNP 1ou set the period split in
the product master record (the SNP< tab)
See also the e&amples in +elease of the ,e$an# Plan to SNP
Period Split
Profile
See !i$e%Base# ,e$an# ,istribution
Product Product or range(s) of products for which you wish to release the demand plan
Page 89 of 251
*ocation *ocation or range(s) of locations for which you wish to release the demand plan
0&tended
)f the )nfoOb3ects in the source planning area that represent products and locations are not 9A.A#N2
and 9A*O-NO, click here to specify the correct )nfoOb3ects
)f you are working with ,escriptive Characteristics, you must enter a consumption group Only then
are the descriptive characteristics transferred to order live-ache 1ou can also specify whether
forecasts are generated in order *ive-ache for all values of the descriptive characteristics or 3ust for
specified values )f you select this option, a button appears with which you can access a selection bo&
2esults *og
#o see the results of the release, check this bo& 6or e&ample, you may wish to do this if the demand
plan was created in months but you are releasing to SNP in days Any errors that occurred during the
release are shown in the log
2. -hoose Program 0&ecute
$esults
See the e&amples in 2elease of the (emand Plan to SNP
$eleasing the Demand Plan with ass Processing
1ou can use this procedure for releasing any amount of data from (emand Planning to Supply Network Planning in the
background 1ou must use it for large amounts of data, for e&ample whole planning books
Prere*uisites
5. 1ou have created a data view for this task #he use of a separate data view to release a mass demand plan has
performance benefits #he data view contains8
A future planning hori!on only (no historical hori!on, unless you want to release data in the past)
#he start date for which data is released is the first day of the planning hori!on #he planning hori!on is defined in
the data view you specify in the planning 3ob
Only the key figure(s) that you want to release to Supply Network Planning
No actual data rows
7. See also +elease of the ,e$an# Plan to SNP
Procedure
5. Create a release profile
7. Create an activity
8. Create a planning job
6. Sche#ule the planning job
9. 2eview the results in the 3ob log, and take any necessary action
$elease from an Info Pro%ider to SNP
1ou can use this function to release forecast data from the 0nfoProvi#er to Supply Network Planning (SNP) #he release
takes place directly to SNP )n other words, you do not need to load the forecast data first into a planning area in (emand
Planning and thus into the time series live-ache
Features
1ou can use the categories for forecast orders (6A, 6+, 6-, and 6() for the release to SNP 1ou can release the forecast
data from the following ob3ects of the SAP +usiness )nformation 'arehouse (+')8
0nfoCube
4irtualProvi#er
,ataStore Object
MultiProvi#er
Selection of Data Source
As data sources for the release, you choose an )nfoProvider and a planning version and key figure contained in the
)nfoProvider )f you do not specify any characteristics for product and location under (ata Source8 0&tended Settings, the
system uses the characteristics 9A.A#N2 and 9A*O-NO
Page 90 of 251
)f you are working with #escriptive characteristics for the release, you must specify a consu$ption group 1ou must also
create at least one planning ob3ect structure and a planning area in (emand Planning #his planning area is only re"uired so
that you can generate consumption groups 1ou do not need to create a characteristics combination or store any planning
data in live-ache
$estriction to the Data Source
#he standard settings for the grouping condition are product and location, since the release to SNP always takes place at
location product level SNP can only evaluate additional characteristics if you are working with descriptive characteristics #o
do so, you must specify a consumption group for the release that contains these characteristics 1ou must also specify these
characteristics in the grouping condition
)f you are working with location splits, you restrict the characteristics e&clusively to the location #he system does not
evaluate any other characteristics during the release
/sage of Periodicities
6or the release, you can use all periodicities that are available in the )nfoProvider )f the selected )nfoProvider contains
months and weeks, for e&ample, you can select precisely these periodicities, but you cannot select days 6or a release of the
periodicity month or week or day, the system reads the data from the )nfoProvider aggregated to week, month, or day level,
and releases the data in the same periodicity to SNP )f you choose more than one periodicity (for e&ample, month and
week), the system performs the release with technical periods )f the )nfoProvider contains the week and day periodicities
and you choose both periodicities for the release, the system also reads the data here from the )nfoProvider in technical
periods )n this case, the technical periods are identical to the day periodicity
)f you use fiscal year as the periodicity, the selected )nfoProvider must only contain one single fiscal year variant
)f you want to release the data aggregated at the level of a periodicity, but this periodicity is not available in the )nfoProvider,
you can either use a daily buckets profile or a period split profile 6or more information about daily buckets profiles, see
Planning Buckets Profile 6or information about period split profiles, see !i$e%Base# ,e$an# ,istribution
)f you use a period split profile, select e&actly one periodicity in the )nfoProvider
Determining the Num+er of Hits in the InfoPro%ider
+efore the release, you can find out how large the data "uantity is that you transfer to SNP #o do so, use Number of 5its in
)nfoProvider #he system then determines the amount of data for the planning version in the )nfoProvider in the specified
period
#he system ad3usts the specified period automatically to the smallest periodicity available in the )nfoProvider 6or e&ample, if
only the periodicity _month` is available in the )nfoProvider, and you enter Ianuary ;D, <::D to (ecember ;D, <::D as the
period, the system determines the data in the period Ianuary :;, <::D to (ecember =;, <::D
Acti%ities
)f you want to release forecast data from the )nfoProvider to SNP, on the SAP 0asy Access screen, choose (emand
Planning Planning 2elease 2elease from )nfoProvider to SNP
01ample
)n the selected )nfoProvider, the data is available in the month and week periodicities 1ou have chosen both periodicities for
the release #he following figure shows how the system determines the technical periods8
#he period displayed in the figure comprises the months Ianuary to .arch A technical period corresponds to the smallest
unit of the periodicity you have chosen, that is, a week Ianuary starts in the middle of the first week of the year, whereby the
start of the following months can also be within one week As a result, technical periods, which are shorter than a week,
occur at the start and end of the affected months
Safety Stock Planning
Safety stock planning in Supply Network Planning (SNP) allows you to attain a specific service level by creating safety stock
for all intermediate and finished products at various locations throughout the entire supply chain
Safety stock is used to safeguard stock in the supply chain against uncertain influencing factors Supply chain planning is
susceptible to a number of influencing factors that cannot be predicted with certainty in advance 6or e&ample, when
forecasting customer demand, the "uantity re"uired is usually uncertain )n addition to this, disruptions in production or
transportation time fluctuations lead to discrepancies in planned replenishment lead times #o safeguard yourself against
such uncertainties when planning, you can take one or more of the following measures8
Page 91 of 251
Overestimate customer demand
/nderestimate production output "uantity
Overestimate procurement lead times
/se safety stock
'hile overestimating customer demand is a (emand Planning tool for safeguarding against forecasting errors, you can
model an underestimation of production output "uantity and an overestimation of procurement lead times using production
process models (PP.s) and transportation lanes
9ou have to a##ress the folloing :uestions as part of safety stock planning;(
5. At which locations within the supply chain do you want to have safety stock7
7. 5ow much safety stock do you want to hold at a particular location7
01ample
'ith the aid of this simple supply chain, it immediately becomes clear that the "uestion about where to hold safety stock is a
highly comple& problem due to the variety of possible combinations (calculated as < to the power n E in this e&ample, there
are already F> possibilities) (ue to this wide range of possibilities, it is advisable to make use of the plannerOs e&perience
and allow the planner to simulate selected planning scenarios
Safety Stock ethods
Since safety stock is usually necessary for products at different locations, you can select a safety stock method in the
product master for every location product #he different methods are split into standard and e1tended methods here
Standard ethods
#he standard methods differ from one another in their observance of time 6or these methods, the planner enters the safety
stock information directly into the system8
Not time.+ased &static' Time.+ased &dynamic'
Safety Stock S+ .+
Safety daysK supply SX .X
.a& eSafety stock, safety daysO supplyf S. ..
6or e&ample, you might want to define safety stock directly as a safety daysO supply or as the ma&imum of the safety stock
and safety daysO supply 'ith the ma&imum option, safety stock can be ad3usted dynamically to meet the demand flow, and
not fall below the defined safety stock 1ou specify safety stock that is not time%based on the *ot Si!e tab page in the
product master, but define safety stock that is time%based in interactive Supply Network Planning
Note that for safety stock method .., the SNP optimi!er only considers independent re"uirements as well as dependent
and distributed demands caused by fi&ed orders, since these demands and the demand locations are already known before
the optimi!ation run
01tended ethods
'hile the standard methods are based e&clusively on the plannerOs e&perience, the proposed safety stock levels of the
e&tended methods are determined by the system based on scientific safety stock planning algorithms #he starting point is a
ser%ice le%el that you want to attain through observance of the calculated safety stock 1ou can define this service level in
the *ot Si!e tab page in the product master )t can be interpreted as follows (based on the business process)8
Page 92 of 251
Shortfall%event%oriented (alpha service level)8 #he service level in percentage means that no shortfall is e&pected in &
percent of the buckets within the planning period
Shortfall%"uantity%oriented (beta service level)8 #he service level in percentage means that & percent of the e&pected
total customer demand can be fulfilled within the planning period
01ample
)ucket 5 7 8 6 9 : ; < 3 54
0&pected demand ;:: ;:: ;:: ;:: ;:: ;:: ;:: ;:: ;:: ;::
Shortfall "uantity : : : : : ;: : : : ;:
Shortfall event % % % % % & % % % &
#otal of shortfall "uantities8 <: %Q beta service level8 ; E (<: 4 ;:::) P 9Ja
#otal of shortfall events8 < %Q alpha service level8 ; E (< 4 ;:) P J:a
#o decide which service level to use, answer this "uestion8 Are the costs for subse"uently delivering a shortfall "uantity
dependent on the shortfall "uantity or not7 )f these costs are not dependent on the shortfall "uantity (fi&ed costs), we
recommend that you use an alpha service level$ if they are dependent on the shortfall "uantity (variable costs), a beta
service level would be more appropriate
#he stockholding method used by SNP when planning demands has a ma3or influence on the algorithm for calculating
safety stock #he following two different stockholding methods e&ist8
2eorder cycle method8 'ith this method, the system makes a purchase order decision on a time basis, which means
that procurement can only be triggered for all t buckets
2eorder point method8 'ith this method, the system makes a purchase order decision on the basis of stock, which
means that procurement can be triggered if stocks fall below a certain level s (the reorder point)
Stockholding ethod
#he two service levels result in these four model%supported safety stock methods8
$eorder cycle method $eorder point method
Alpha service level A# AS
+eta service level +# +S
#he prere"uisite for using this method is that shortfall "uantities are delivered subse"uently (_back order case` as opposed to
_lost sales case`) )f this prere"uisite is met, the system can calculate the safety stock on any step of the supply chain and for
each bucket in the planning period
Forecast 0rror Determination
'hen calculating the safety stock, the system can take into account a forecast error in both demand and procurement #he
following key figures form the starting point for the forecast error calculations8
Demand Procurement
Planned demand "uantity key figure Planned replenishment lead time key figure
2eali!ed demand "uantity key figure 2eali!ed replenishment lead time key figure
Page 93 of 251
#he system calculates the forecast error by determining the planned actual deviation of the relevant key figures #he
standard deviation of the planned actual deviations is interpreted as the forecast error A forecast error is thus determined
from the historical data and the future forecast is based on this forecast error #o more accurately support the future forecast,
it is a good idea to interpret this forecast error as a relative forecast error, so that instead of keeping the forecast error itself,
you keep the relationship between forecast error and forecast (variation coefficient) #his is clarified in the following e&ample8
01ample
.ean value of the planned demand "uantity8 ;::
Standard deviation of the planned actual deviations8 ;:
)ucket 5 7 8 6 9
(emand 6orecast ;:: ;::: ;::: ;:: ;::
6orecast error if the standard deviation is constant ;: ;: ;: ;: ;:
6orecast error if the variation coefficient is constant ;: ;:: ;:: ;: ;:
)f the forecast error is not dependent on the forecast, an incremental forecast une&pectedly causes the safety stock to fall
because the forecast error decreases in relation to the forecast 6or this reason, it is more advisable to use relative forecast
errors in a dynamic environment than constant forecast errors
)f there is a forecast error in procurement (a replenishment lead time forecast error), the demand forecast error is ad3usted
based on the assumption that the two forecast errors are independent of each other
1ou can also enter the demand forecast error and replenishment lead time forecast error directly in the location product
master 'e recommend that you do this in the following circumstances8
)f there is no historical data (because the product is new for instance)
)f the amount of historical data is so small that it is impossible to calculate a statistically relevant forecast error
)f the forecast error can be considered constant
)n the safety stock planning profile, you can specify if the system is to calculate the forecast error during e&tended safety
stock planning from the historical data or from the location product master data
odifying the Parameters
.ultilevel safety stock planning is a very comple& issue for any supply chain structure )t is therefore a good idea to
implement high%performance heuristics Algorithms are thus the focus of attention for single%level, non%time%based safety
stock planning that is then incorporated within a multilevel, time%based supply chain planning by ad3usting the input
parameters
#his makes it necessary for the system to ad3ust the forecast and forecast error for demand and procurement
6or demand, the system first determines all the location products supplied by the safety stock location product )t then
pro3ects all the forecasts and forecast errors onto the safety stock location product (considering all the "uantity and time
relationships) to calculate the safety stock
6or procurement, the system first determines all the location products that are to supply the safety stock location product )t
will do this until it finds a safety stock location product, or until it finds e&ternal supply for the supply chain )t then determines
the critical supply path by calculating the ma&imum replenishment lead time All forecasts and forecast errors along this
critical path are then pro3ected onto the safety stock location product for safety stock planning
See alsoC
Stan#ar# Safety Stock Planning, -&ten#e# Safety Stock Planning, Master ,ata Setup for Safety Stock Planning
Standard Safety Stock Planning
1ou use standard safety stock planning in Supply Network Planning (SNP) to build up safety stock for location products
according to values that match past e&perience 1ou can define these values as time%independent in the location product
master data or time%dependent in interactive SNP planning 'hen doing so, you can choose from si& different safety stock
methods with which you define the safety stock directly using the safety daysO supply or as a ma&imum of safety stock and
safety daysO supply
#he values you have defined are then considered during heuristic or optimi!ation%based SNP planning
Prere*uisites
1ou have defined the specific master data for standard safety stock planning 6or more information see .aster (ata
Setup for Safety Stock Planning
Page 94 of 251
)f you wish to use safety stock methods .X, .+, or .., you have to use standard SNP planning area 9ASNP:D and
standard planning book 9ASNP?SSP (or a planning area and planning book based on these) that contain the following
key figures8 9ASA60#1 E Safety Stock (Planned) and 9ASB##1 E Safety (aysO Supply
Note that for safety stock method .., the SNP optimi!er only considers independent demands as well as dependent and
distributed demands caused by fi&ed orders, since these demands and the demand locations are already known before the
optimi!ation run
Acti%ities
#he safety stock values you defined are shown in interactive SNP planning and the system considers them during the SNP
planning runs
01tended Safety Stock Planning
0&tended safety stock planning in Supply Network Planning (SNP) automatically calculates the safety stock using data that
you specified as mandatory in the system #his includes, for e&ample, a service level that you want to attain through
observance of the calculated safety stock 1ou also specify the current demand forecast and the historical data using the
demand forecast and the replenishment lead time (2*#) as key figures #he system uses the historical data to calculate the
forecast error for the demand forecast and the 2*#
Prere*uisites
1ou have assessed your supply chain and determined at which stages you want to plan safety stock
1ou have determined the special master data for safety stock planning ne&t to the basic SNP planning master data
(including "uota arrangements) #his includes, for e&ample, the service level and the safety stock methods in the
location product master data 6or more information see .aster (ata Setup for Safety Stock Planning
1ou have created a safety stock planning profile (S6# planning profile) )n this profile you can, for e&ample, determine
how the system calculates the forecast error (from historical or master data), and specify the demand type (regular or
sporadic) 6or more information, see Safety Stock Planning Profile
Features
#he system considers the following factors when calculating the safety stock8
(emand forecast and demand forecast error
2eplenishment lead time (2*#) and 2*# forecast error
Service level
Safety stock method
(emand type
#he reorder point method that you determined in the location product master data does not influence safety stock planning
#he system determines these factors as follows8
Demand Forecast Determination
#he forecasted demand for a product at a location is the sum of the independent and dependent demands at the
location and all downstream locations 1ou specify the independent demands in the system as a key figure for the
demand forecast #he system determines the dependent demands using transportation lanes and production process
models (PP.) or production data structures (P(S) #he system also takes into account inbound "uota arrangements
#he system determines the demands forecast error from the historical data or location product master data that you
specified as mandatory (settings in S6# planning profile)
$eplenishment (ead Time Determination
#he 2*# for a product at a location is the total time for the in%house production or the e&ternal procurement of a product
(including its components) #he system determines the 2*# using the supply chain model or from location product
master data (settings in S6# planning profile)
)f the system determines the 2*# using the supply chain model, it adds up the respective production times, good issue
processing times, transportation times, goods receipt processing times, and planned delivery times )f there are
alternative procurement options, the system always considers the option that takes the longest time #he system does
not consider restrictions on capacity si!e, lot si!e, or warehouse stock Procurement from upstream safety stock is not
restricted
#he system determines the 2*# forecast error from the historical data or location product master data that you specified
as mandatory (settings in S6# planning profile)
Ser%ice (e%el Determination and Safety Stock ethod Determination
Page 95 of 251
#he system determines the service level and the safety stock method from the location product master data ( *ot Si!e
tab page) 'ith the safety stock method you determine the combination of service level and order policy that the system
is to consider
(uring the reorder cycle methods A# and +# the system interprets the target daysO supply from the location product
master data as an order cycle
(uring the reorder point method +S the system uses the target daysO supply from the location product master data to
calculate the purchase order "uantity
(uring the reorder point methods AS and +S the system accepts a monitoring interval (period of time between
successive reviews of the warehouse stock) from one period
Demand Type Determination
1ou can use safety stock planning both for products with regular demand and also for products with sporadic demand
6or the former, the formulas used assume normal distribution, for the latter they use gamma distribution
#he system determines the demand type from the settings you made in the S6# planning profile 1ou can determine
whether it is regular or sporadic demand, or whether the system is to automatically determine the demand type using
historical data
Acti%ities
On the SAP 0asy Access screen, choose Advanced Planning and Optimi!ation Supply Network Planning Planning
Safety Stock Planning On the Safety Stock Planning screen, you then enter the data described below8
Section Input data
Planning
(ata
)n this section you then specify the planning area where the planning ob3ects and key figures are 1ou can
use, for e&ample, the SNP standard planning area 9ASNP:D (or a planning area based on it) that contains
the key figures 9A(6-S#, forecasting, and 9ASA60#1, safety stock (planned)
1ou can also specify the key figure for the demand forecast, based on which the system calculates the safety
stock (for e&ample, 9A(6-S#) 1ou can also specify the key figure in which the system saves the safety
stock (for e&ample, 9ASA60#1) and the S6# planning profile the system uses
Ob3ect
Selection
)n this section you specify the location products for e&tended safety stock planning #he system plans the
safety stock for those location products for which you have determined an e&tended safety stock method in
the master data
5istorical
(ata
)n this section you specify the key figures for the demand forecast historical data which the system uses to
calculate the forecast error 1ou can, however, determine the forecast error in the location product master
data yourself
Application
*og
)n this section you specify how the system creates the application log (level of detail, immediate display,
length of storage)
1ou can display the calculated safety stock as a key figure in interactive Supply Network Planning and, if re"uired, manually
change it or copy it into another planning version 1ou can also use the calculated safety stock in Production Planning ,
(etailed Scheduling (PP4(S) and -apable%to%.atch (-#.)
Safety Stock Planning Profile
#his profile contains settings for e&ten#e# safety stock planning in Supply Network Planning (SNP)
)f you e&ecute e&tended safety stock planning in SNP, you must specify a safety stock planning profile (S6# planning profile)
)n this profile you determine settings for safety stock planning that rarely have to be changed #his includes, for e&ample,
how the system calculates the replenishment lead time (2*#) forecast and the 2*# forecast error
Structure
#he profile consists of the following sections8
Profile
)n this section you give the profile a name and a description
Demand
)n this section you determine how the system calculates the demand forecast error (from historical data or location
product master data) 1ou can also correct the level of the demand forecast and the demand forecast error up or down
$eplenishment (ead Time
)n this section you determine how the system calculates the replenishment lead time forecast (from the supply chain
structure or location product master data)
Page 96 of 251
1ou also determine how the system calculates the forecast error (from historical data or location product master data)
1ou can also correct the level of the 2*# forecast and the 2*# forecast error up or down
Safety Stock #alculation
)n this section you determine the re"uirements category that the e&tended safety stock planning is to use as the basis
for its calculation (regularly, sporadically, or automatically)
1ou can also specify that the system takes into account the location product fi&ed lot si!e, defined in the location product
master data, while calculating the procurement "ualities
Further settings
)n this section you determine the block si!e with which the e&tended safety stock planning saves the result in the
live-ache 1ou can also specify that the system checks the supply chain in cycles to avoid endless loops during the
planning
)f you want to carry out aggregate# safety stock planning, you can specify the level at which the system is to consider the
sources of supply8 sub location product level, header location product level, or at both levels (default value)
'hen you specify a new profile, the system offers you default values 1ou can also use the SNP standard profile
SAP(06A/*# that also contains default values
Supply Network Planning $un
1ou can use any of the following planning methods to perform the planning run in Supply Network Planning (SNP)8
Opti$i6ation%Base# Planning
.euristic%Base# Planning
Supply an# ,e$an# Propagation
1ou can run optimi!ation%based and heuristic%based planning interactively from the interactive planning #esktop in Supply
Network Planning or you can run them in the background 1ou run supply and demand propagation in a dedicated planning
book in interactive Supply Network Planning
+ased on these planning methods, SNP supports special planning processes, such as8
Aggregate# Planning
Planning ith Aggregate# +esources
Pro#uct 0nterchangeability
Procure$ent Sche#uling Agree$ent in .euristic%Base# SNP Planning
Subcontracting ith Source "ocation in SNP
Subcontracting ith !hir#%Party Provision of Co$ponents in SNP
,irect ,elivery fro$ Pro#uction Plant to Custo$er
6or detailed information about the individual planning methods and processes, see the related sections of this
documentation
1our individual planning environment influences which planning method would be the most suitable for your re"uirements
6or a comparison of the heuristic and optimi!ation planning methods with -apable%to%.atch (see below), see Co$parison of
the Planning Metho#s
See also
-apable%to%.atch planning (-#.) is an alternative to the optimi!ation%based or heuristic%based planning methods from
Supply Network Planning 6or more information, see the .ultilevel Supply and (emand .atching section of the SAP APO
documentation
#omparison of the Planning ethods
Opti$i6ation%base# planning and heuristic%base# planning are the two main planning methods of Supply Network Planning
(SNP) #his topic compares these two planning methods with the Capable%to%Match 2C!M3 planning method
'e recommend that you use optimi!ation%based planning or -#. planning if one of the following conditions applies to you8
1our business environment is sub3ect to strict constraints (for e&ample, you must take into account production
capacities, transportation capacities, storage capacities, and4or handling capacities)
1ou have alternative production locations and sources of supply (locations, production process models, and e&ternal
procurement relationships)
1ou can decide between early production and late production
Page 97 of 251
1ou share resources, meaning that multiple products are produced simultaneously on the one resource
'e recommend that you use heuristic%based planning or -#. planning if any of the following conditions apply8
1ou wish to plan on an infinite basis (meaning that you do not wish to consider capacities) for the medium to long%term
hori!on (heuristic)
1ou wish to take into account predefined "uota arrangements$ for sources of supply, for instance (heuristic or -#.)
1ou wish to plan or fulfill demands on the basis of priorities (-#.)
#he following table describes the main features of each planning method8
)usiness 0n%ironment
Area
Heuristic and #apacity
(e%eling
#apa+le.to.atch OptimiGer
+usiness Ob3ective
#o create a feasible plan
with few bottleneck
resources
#o create a feasible
plan by fulfilling the
highest priority demand
first
#o create a feasible plan
with minimum costs
#o ma&imi!e profits
(emand #ype Not relevant
Prioriti!ed demand and
demand%specific supply
strategies
(emand can be
aggregated for three
demand classes or by
customer locations
-apacity
5euristic run8 +ased on
the assumption that
capacity is infinite (infinite
capacity planning)
-apacity leveling8 #his is a
step following on from the
heuristic run to level
capacities
6inite capacity planning
(taking capacity
constraints into
account) or a simulation
of infinite planning
6inite or infinite capacity
planning
Planning Approach
+ucketed (period%based)
planning
+ucketed or continuous
planning
+ucketed planning
#onstraints and )usiness Scenarios
Area
(e%eling
2esources
Production
#ransportation
5andling (heuristic
only)
Production
Production
#ransportation
Storage
5andling
#arget Stock *evels
6le&ible definitions for
the heuristic but
capacity levelling does
not consider the target
stock level method
specified
-an use absolute target
stock levels or target daysO
supply for planning
-an use absolute target
stock levels or target
daysO supply for planning
#he optimi!er calculates
the target daysO supply
before the actual
optimi!ation run
*ot Si!es
-onsiders lot si!es for
production,
transportation, and
procurement
production, transportation,
and procurement
production and
transportation
-onsiders cross%period lot
si!es for production
#ransportation lot si!es
have to be used to map
lot si!es for procurement
Source (etermination
(sourcing)
+ased on "uota
arrangements and
+ased on costs (PP.4P(S
and transportation),
-ost%based sourcing
decisions
Page 98 of 251
Area
(e%eling
priorities
priority, or "uota
arrangements ("uota
arrangement does not split
orders unless necessary to
fulfill demands on time)
(oes not take "uota
arrangements into
account but can be used
to modify "uota
arrangements
#ime%+ased
Production Parameters
-onsidered -onsidered -onsidered
.aterial -onstraints
.aterial staging is not
a constraint A backlog
is created for e&ternally
planned products
-onsiders material
constraints$ e&ternal
products are not planned
and do not represent a
material constraint
-an consider material
constraints for e&ternally
planned products or by
setting a high
procurement cost for
procured products
Supply -ategori!ation Not supported
1ou can define supply
categories
Not supported
Supersession and
(iscontinuation of
Products
;8; % Supports
supersession
(supersession chains
and form%fit%function
classes)
;8; % Supports
supersession (forward
interchangeable
supersession chains only)
;8; % Supports
supersession
(supersession chains and
form%fit%function classes)
5ierarchical Planning
Supports aggregation
planning and
disaggregation
(oes not support
aggregation based on
hierarchies but you can
choose to aggregate
demands and supply on a
time basis or by order
types for product
Supports aggregation
planning and
disaggregation
.a&imum Stock *evels
by Product
Not considered Not considered
-onsidered as a
constraint
Push (istribution Stock
to (ownstream
*ocations
Not supported (but is
supported by
deployment)
Not supported (but is
supported by deployment
and by supply distribution
in -#.)
-an be controlled using
storage costs
.inimum 2esource
/tili!ation
Not supported Not supported
1ou can define a
minimum available
capacity for a resource
and assign costs for
falling below this
minimum level (this only
applies to production
resources)
2esource -apacity
(oes not make a
distinction between
standard and e&tended
capacity
(oes not make a
distinction between
standard and e&tended
capacity
-an make a distinction
between standard and
e&tended capacity
(emand Prioriti!ation
-apacity leveling does
not recogni!e demand
priorities
(emand can be sorted by
different sort criteria
(emand can be
aggregated for three
demand classes or by
customer locations
Shelf life Not considered Not considered
-an consider shelf life
constraints in a restricted
way (see SAP note
DG9DDF)
+atches are not
recogni!ed
Page 99 of 251
Area
(e%eling
Subcontracting
Supported (the
subcontractor has to
be modeled as a
location)
Supported (the
subcontractor has to be
modeled as a location)
Supported (the
subcontractor has to be
modeled as a location)
Scheduling Agreement
Processing
Supported Not supported Not supported
#onfiguration
Area
(e%eling
2elevant .aster (ata
*ocations
Products
2esources (single%
mi&ed, multi%mi&ed,
and bucket resources)
PP.s and P(Ss
(SNP)
#ransportation lanes

*ocations
Products
2esources (single%mi&ed or
multi%mi&ed, and bucket
resources)
PP.s and P(Ss (SNP and
PP4(S, but some
restrictions)
-#. profile (supply
profiles, demand profiles,
and so on)
*ocations
Products
2esources (single%mi&ed
or multi%mi&ed, and
bucket resources)
PP.s and P(Ss (SNP)
SNP optimi!er profile
Optimi!er costs
6le&ibility of Algorithm
.acros can be used to
modify heuristic values
that are entered
1ou can modify aspects of
the calculation by changing
profile settings and
maintaining parameters
5as a user function for
modifying the optimi!er
input log
.acros can be used to
modify optimi!er values
that are entered
Average 0ffort .inimal
.edium to large,
depending on the
comple&ity of the supply
chain
.edium to large,
depending on the
comple&ity of the supply
chain
-ost fine%tuning is the
ma3or effort
-urrent Application
-apacity leveling only
considers one
resource at a time
After the parameters have
been configured, -#. can
be run automatically
After costs are fine%tuned,
the optimi!er can be run
automatically
-omprehensibility #ransparent results
#ransparent results based
on priorities #he analysis
comple&ity is governed by
the supply chain
comple&ity
Order tracking by pegging
Craphical representation of
results
2e"uires some
understanding of cost
tradeoffs
-ost summaries are
available after the
optimi!ation run
)ntegration with PP4(S
+ucketed plans need
to be converted into
continuous plans
+ucketed plans need to be
converted into continuous
plans
-ontinuous plans can be
created
+ucketed plans need to
be converted into
continuous plans
2ecogni!es material flow,
capacity consumption,
and setup statuses from
PP4(S
Net -hange Planning Supported Supported % with options
for dynamic and fi&ed
5ave to replan all
Page 100 of 251
pegging
demands
-an use the SNP
optimi!ation bound profile
to restrict replanning
OptimiGation.)ased Planning
#he SNP optimi!er offers cost%based planning #his means that it searches through all feasible plans in an attempt to find the
most cost%effective (in terms of total costs) #otal costs refers to the following8
Production, procurement, storage, and transportation costs
-osts for increasing the production capacity, storage capacity, transportation capacity, and handling capacity
-osts for violating (falling below) the safety stock level
-osts for late delivery
Stock out costs
1ou use the SNP cost profile to fine%tune the relative importance of different cost types
)n the optimi!er view, a plan is feasible when it satisfies all the Supply -hain .odel constraints that you set in the SNP
opti$i6er profile A feasible solution might involve due date or safety stock constraint violations (ue dates and safety stocks
are Soft -onstraints (constraints to which you assign violation costs) #he optimi!er only proposes a plan that will violate soft
constraints if, according to the costs specified in the system, it is the most cost%effective plan
#he optimi!er makes sourcing decisions within optimi!ation%based planning #his means that it uses costs as a basis for
deciding the following8
'hich products are to be produced, transported, procured, stored, and delivered and in which "uantities (product mi&)
'hich resources and which production process models (PP.s) or production data structures (P(Ss) to use (technology
mi&)
#he dates and times for production, transportation, procurement, storage, and delivery
#he locations for production, procurement, storage, delivery, and the source and destination locations for transportation
Since you can enter PP.s or P(Ss with fi&ed resource consumption in master data, you can also include setup operations
in Supply Network Planning #herefore, you can also use the SNP optimi!er for lot si6e planning #he optimi!er also supports
cross%perio# lot si6e planning where orders are grouped into large lots due to high set up costs
#he optimi!er uses the linear programming method to take account of all planning%problem%related factors simultaneously
within one optimal solution As more constraints are activated, the optimi!ation problem becomes more comple&, which
usually increases the time re"uired to solve the problem As a rule, you should run optimi!ation as a background 3ob
#he optimi!er makes a distinction between continuous linear optimi!ation problems and discrete optimi!ation problems
(inear OptimiGation
1ou can choose one of the three following methods in the SNP optimi!er profile to solve continuous linear optimi!ation
problems8
Primal simple& method
(ual simple& method
)nterior point method
All three methods arrive at an optimal solution 2untime could be the main influencing factor when deciding which of these
methods to use 5owever, there is no general rule for selecting the best method for a given problem (apart from to test each
method individually) A good way of assessing the application is to do a benchmarking based on a test scenario #his is
because the optimal choice of method depends more on the structure of the supply chain and less on the input data
#herefore, in a productive environment, daily benchmarking is not necessary
Discrete OptimiGation
A problem is not continuous (and is therefore discrete) in Supply Network Planning, when the model contains8
(iscrete (integer%value) lot si!es for transportation or PP.s4P(Ss
(iscrete means of transport
(iscrete increase of production capacity
.inimum lot si!es for transportation or PP.s4P(Ss
Piecewise linear cost functions for transportation, production, or procurement
Page 101 of 251
6i&ed PP.4P(S resource consumption
6i&ed PP.4P(S material consumption
-ross%period lot si!e planning
)f you want the optimi!er to consider any of the above constraints, you must use one of the discrete optimi!ation methods
from the SNP optimi!er profile
#he piecewise linear cost function that you can define in master data makes a distinction between the conve& cost function
(cost per unit increases for higher volumes$ for modelling overtime or night shifts for instance) and the concave cost function
(cost per unit decreases for higher volumes$ for modelling freight rates for instance)
-onve& cost functions do not complicate the planning problem and can be solved efficiently 5owever, they can also be
modelled using alternative modes without using piecewise linear cost functions
.ode ; with UD: per unit and a limited capacity of eight models
.ode < with U;:: per unit and a limited capacity of si& models
-onve& functions of labour cost per day, assuming eight normal working hours and a ma&imum of si& hours of overtime
paid at double time
)n contrast, concave piecewise linear cost functions cannot be solved by an *P solver but only by using discreti!ation
methods (mi&ed integer linear programming) )f piecewise linear functions are modelled but the optimi!er is run without
discreti!ation or the discreti!ation hori!on is smaller than the planning hori!on, the optimi!er takes into account the linear
cost function defined in addition to the piecewise linear cost function
#he discrete optimi!ation method cannot be used with strict prioriti!ation (see below)
/sing the discrete optimi!ation method can significantly increase runtime re"uirements Note that Supply Network Planning
is a medium%term planning function and its focus should not be on solving integer problems (that is, using the discrete
optimi!ation method)
PrioritiGation
#he optimi!er can differentiate between the priority of sales orders and forecast demand 'ith strict prioriti!ation, sales
orders always have priority ;, the corrected demand forecast priority D, and the demand forecast priority F 'ithin every
priority class, the system uses all available cost information to determine the final solution 'hen cost%based prioriti!ation is
used, the optimi!er uses penalty cost information from the product master data (the SNP; tab page) to determine the optimal
solution
Decomposition
1ou can use the decomposition methods, defined in the SNP optimi!er profile, to reduce runtime and memory re"uirements
for optimi!ation (ecomposition may also represent the only way for the optimi!er to find a feasible solution in the event of
large discrete problems 6or more information, see ,eco$position
Aggregated Planning . "ertical
#o reduce the si!e of the model to be optimi!ed, the optimi!er can restrict planning to location product group level (assuming
you have defined the demands at the lower level) Plans are distributed to lower level products based on demand for the
lower level products #o plan at product group level, you must define hierarchies for products and locations in the hierarchy
master #his data is used to generate the location product hierarchy 1ou also must define the PP.s or P(Ss for the product
groups and create the PP. or P(S hierarchy in the hierarchy master )n the SNP optimi!er profile, if you set the Aggregated
Planning % Bertical indicator, the products are automatically aggregated to the relevant groups for planning and after planning
is complete, they are disaggregated again
Aggregated Planning . HoriGontal
#his function allows you to plan a subset of your supply chain 1ou can limit the products or locations to be taken into
account during the optimi!ation run 6or e&ample, if optimi!ation is only run to plant level but forecasts are at customer level,
the optimi!er can sum (aggregate) the demands to plant level and use this value during the optimi!ation run #he
transportation times, for e&ample, from the plant to the distribution center and to the customer, as well as the duration of the
PP.s or P(Ss, are also taken into account
Incremental OptimiGation
)ncremental optimi!ation is the name given to optimi!ation%based planning that is run for only part of the model or on the
basis of an already e&isting plan #he plan might be infeasible with this type of optimi!ation since the optimi!er cannot plan
receipts for shortages that are the result of fi&ed orders from previous planning runs )t is also possible that the optimi!er will
ignore input products (and associated stock) that are defined in PP.s 4 P(Ss or products that are available for procurement
at a source location using a transportation lane (source location products)
#o prevent this, you can specify in the SNP optimi!er profile that the optimi!er is to take into account the stocks of non%
selected input products or source locations products 1ou can also specify that the dependent demand and distribution
demand of fi&ed orders is to be treated as an independent re"uirement, meaning that the optimi!er will permit shortages
sub3ect to the calculation of penalty costs for not delivering 1ou define penalty costs for not delivering for customer demand,
Page 102 of 251
the demand forecast, and corrected demand forecast in the product master data 1ou can also set that the optimi!er is to
consider the dependent demand and distribution demand of fi&ed orders, and the stocks of non%selected input products or
source location products as a pseudo%hard constraint #his means that shortages are possible but are sub3ect to the
calculation of infinitely high penalty costs that are internally defined in the optimi!er Setting this ensures that the optimi!er
will only permit shortages if it cannot find any other feasible solution
Process Flow
1. 1ou run the optimi!er
2. 1ou run deployment
3. 1ou run the #*+
The OptimiGation $un
NoteC #he optimi!er plans all distribution demands for all locations in the distribution network before e&ploding the +O. and
processing dependent demand at the production locations
Factors #onsidered During the $un
Balid transportation lanes
*ead times
#ransportation capacity
#ransportation costs
5andling capacity
5andling costs
Production capacity
Production costs
Storage capacity
Storage costs
#ime stream (location master data)
*ot si!e (minimum, ma&imum, and rounding value)
Scrap
Application 01amples for the SNP OptimiGer
+elow is a list of e&amples showing where you can use the SNP optimi!er within production planning and distribution
resource planning and what you should keep in mind8
Page 103 of 251
1. Finite #apacity Planning
)t is particularly advisable to use the SNP optimi!er to plan capacities as finite if you have limited business resource
capacities and these limited capacities have an impact on your production planning and distribution resource planning
+y already planning capacities as finite in Supply Network Planning (SNP), you can take capacities into account and
make it easier for the subse"uent detailed scheduling (such as SAP APO Production Planning and (etailed Scheduling,
PP4(S) to create feasible plans
6urthermore, by using the SNP optimi!er to plan finite capacities, you can include a possible e&tension of your
capacities into your plan, sub3ect to the calculation of additional costs
1ou can use the SNP optimi!er to plan the following resource categories and types as finite8
2esource categories8
Production resources
#ransportation resources
5andling resources
Storage resources
2esource types8
Single%mi&ed and multi%mi&ed resources
+ucket resources
Integration
#he SNP optimi!er takes into account the net available capacity only, meaning that it checks whether the capacity
available in SNP is already being used by other system application areas (PP4(S, deployment, or the #ransport *oad
+uilder, for e&ample) or by fi&ed SNP orders
6or single%mi&ed and multi%mi&ed resources, the SNP optimi!er subtracts the capacity consumed by PP4(S, for
instance, from the capacity available in SNP )f the capacity consumed by PP4(S e&ceeds the aggregated available
capacity in a bucket in SNP, the optimi!er assumes that there is an available capacity of 4 in the corresponding bucket
and plans no further capacity consumption in this bucket
Prere*uisites
#he prere"uisites for finite capacity planning are the same as those for general optimi!ation%based planning8
Planning Area A#$inistration
Master ,ata Setup for the Opti$i6er
Mo#el<4ersion Creation
Supply Chain Mo#el Setup
+elease of the ,e$an# Plan to SNP
Features of Finite #apacity Planning
=eneral Information
Cenerally, the SNP optimi!er takes into account all model constraints simultaneously #his means that the optimi!er
takes into account the available capacity of all resources at the same time #hus, during multilevel production, for
e&ample, all the manufacturing levels are incorporated simultaneously into planning
)n the SNP optimi!er profile, you can set which capacity constraints (production capacity, transportation capacity,
handling capacity, or storage capacity) you want the optimi!er to take into account
#he optimi!er determines the available capacity based on the defined factory calendar, meaning that it only uses days
defined as workdays to determine the bucket capacity
1ou can define multiple capacity variants for resources and label these as the minimum, normal, or ma&imum
available capacity #hus, you can let the optimi!er decide to increase capacity or fall below the minimum capacity
sub3ect to the calculation of additional costs Since the optimi!er generally chooses the solution with the lowest
costs, it will only increase capacity or fall below the minimum if this course of action is the most cost%effective total
solution despite the additional costs
1ou define the costs for the capacity variants with minimum, normal, or ma&imum capacity in the "uantities4rate
definition or the capacity profile of the resource master data #o set the status indicator, go to the resource initial screen
and choose8 -urrent Settings %Q -apacity Bariants (see also, .aster (ata Setup for the Optimi!er)
Page 104 of 251
Note that the optimi!er takes into account the minimum available capacity and the costs you defined for a capacity
variant with the status Normal -apacity only for production resources
Production $esources
#apacity #onsumption
#he SNP optimi!er takes into account the capacity consumption of a production resource, which you define in the
production process model (PP.) mode One PP. can load several resources and one resource can be loaded by
several PP.s #he duration of an SNP PP. (that is, the sum of the duration of all PP. activities) is fi&ed )t has no
influence on resource consumption and instead is used only for scheduling within the PP.
#he resource consumption defined per activity is distributed evenly over the length of the activities #his means that
the optimi!er ignores the consumption type defined for the activity and always assumes that consumption is
continuous (consumption type #)
)f you use the linear optimi!ation method, the optimi!er only takes into account the variable resource consumption
defined in the PP. )f you want the optimi!er to also take into account fi&ed resource consumption, you have to
choose discrete optimi!ation in the SNP optimi!er profile and define a discreti!ation hori!on for the 6i&ed .aterial
and 2esource -onsumption #his is necessary if, for instance, you want to use fi&ed resource consumption to
model setup times during lot si!e planning with the SNP optimi!er (see also, *ot Si!e Planning)
Note that the optimi!er ignores the fi&ed resource consumption defined in the PP. if you choose the linear
optimi!ation method in the SNP optimi!er profile Howe%erI fi1ed resource consumption is taken into account if
orders are created in li%e#ache during planning. #his can cause a resource overload to be displayed in the
capacity view of interactive Supply Network Planning #herefore, if you want the optimi!er to take into account the
fi&ed resource consumption, choose discrete optimi!ation or do not define a fi&ed resource consumption in the
PP.
)f you are running an integrated SNP and PP4(S planning and set the *ot Si!e Planning8 Not -ross%Period indicator
in the SNP optimi!er profile (the )ntegration tab page), fi&ed resource consumption is not taken into account when
creating SNP orders in live-ache if there is already an e&isting PP4(S order for the associated PP4(S PP. (see
also the 6; help at the indicator) #his also applies for Cross%Perio# "ot Si6e Planning if you set the accompanying
-ross%Period *ot Si!e Planning indicator
#he optimi!er also takes into account time%based resource consumption that you defined in the PP. 1ou can use
time%based consumption to model varying consumption levels over the course of the bucket 6or e&ample, you
could include the following information in your plan8 A machine consumes more lubricant at the beginning of
production than it does towards the end
A%aila+le #apacity
6or the ma&imum available capacity variant of production resources (see above), you can define that the optimi!er is
permitted to either increase the capacity by this variantOs entire available capacity (an entire layer, for e&ample), or
not increase it at all )n this instance, the optimi!er either takes into account the entire costs of the increase or no
costs at all )n the SNP optimi!er profile, choose the discrete optimi!ation method and define a discreti!ation
hori!on in the (iscrete Production -apacity )ncrease field
#apacity #osts
1ou can also define time%based costs for increasing the capacity of production resources 6or a daily planning
buckets profile, you can define that the increase costs more on a .onday than it does on a #uesday, for e&ample
1ou also have the option of defining costs for the normal capacity variant (standard capacity) for production
resources 1ou can specify these costs (also on a time basis) per capacity unit and bucket #he costs incurred are
proportional to the resource usage
)f you wish to define a minimum available capacity (see the Ceneral )nformation section), you have to define costs for
falling below it 1ou can also specify these costs for each capacity unit and bucket #he costs incurred are
proportional to the amount fallen below the minimum available capacity
#onstraints
Since you can only create one mode per activity in the SNP PP., you cannot define any alternative resources for a
production activity #o define alternative resources, you must create one PP. per mode combination 1ou can use
the SNP PPM 5eneration =ith "ot Si6e Margin function to generate SNP PP.s automatically for multiple PP4(S
PP. mode combinations
Transportation $esources
#he SNP optimi!er only takes into account the means of transportOs variable capacity consumption (per day) that you
specified in the -onsumption field of the Product%Specific .eans of #ransport section 1ou specify consumption for
the product that is defined in this section -onsumption is dependent on the transportation duration )f the
transportation duration is :, no resource consumption e&ists
Page 105 of 251
)f you do not enter a value in the -onsumption field or do not define any data for the Product%Specific .eans of
#ransport, the optimi!er calculates consumption using the conversion factor for units of measure that you specified
on the /nits of .easure tab page in product master data
A%aila+le #apacity
1ou can assign transportation resources to multiple transportation lanes and so limit the transportation capacity on
these transportation lanes #o do this, specify a transportation resource in the 2esource field of the .eans of
#ransport section in the transportation lane
)n the SNP optimi!er profile, you can set that you want the available means of transport to be treated as discrete (in
non%divisible integer numbers) )f you do this, the means of transport is treated as discrete for each transportation
lane 1ou define the capacity of the means of transport in the #ransp2esSi!e field of the resource master data
1ou can use this option to model the means of transport that are available in your company (a truck, for e&ample)
5owever, if you commission e&ternal transportation service providers, considering means of transport as discrete is
not relevant for you
#apacity #osts
#he transportation costs considered by the optimi!er consist of the product%specific transportation costs (that is, the
transportation costs you entered in the Product%Specific .eans of #ransport section in the transportation lane) and
the transportation costs for the means of transport (that is, the transportation costs entered in the .eans of
#ransport section) #he means of transport costs are dependent on the transportation resource consumption of all
the products transported on the transportation lane and the distance that was defined for the transportation lane
between the start location and destination location
1ou can define the means of transport costs either as costs per transportation resource unit or as costs per means of
transport 6or the costs per transportation resource unit, you do not define a si!e for the transportation resource
5owever, for the costs per means of transport, you do define a si!e (D t, for e&ample) and set the )ntegral .eans of
#ransport indicator in the SNP optimi!er profile, if re"uired (when activating this indicator, you must also choose the
discrete optimi!ation method in the SNP optimi!er profile)
)f, for instance, you want to model discount scales for the costs per transportation resource unit option, you can use
cost functions -ost functions are most appropriate when you are working together with e&ternal transportation
service providers
Handling $esources
1ou can assign handling units to a location (on the 2esources tab page) as handling%in resources or handling%out
resources in location master data #he handling%in resource is loaded by inbound shipments (SNP stock transfers)
and e&ternal procurement during the goods receipt processing time and the handling%out resource is loaded by
outbound shipments during the goods issue processing time
1ou can define the capacity consumption of the handling%in and handling%out resources for the respective location
product in location product master data (on the C24C) tab page) 2esource consumption refers to the handling
operation and is therefore proportional to "uantity but not time
#onstraints
1ou can define a ma&imum of one handling%in resource and one handling%out resource per location
Storage $esources
#he optimi!er takes into account the capacity consumption of the storage resource that you define for the respective
location product in location product master data (on the C24C) tab page)
A%aila+le #apacity
#he optimi!er considers the storage capacity constraint as a soft constraint that can be violated by the optimi!er,
sub3ect to the calculation of penalty costs #hese penalty costs are assigned by the optimi!er, which means that you
cannot set them in the master data
Storage capacity is a soft constraint due to the integration between Supply Network Planning, PP4(S, and SAP 24=
#here might be initial on%hand stocks or fi&ed material receipts (from PP4(S, for e&ample) because of this
integration that cannot be reduced within a bucket and e&ceed the storage capacity #o be able to find a solution,
the optimi!er must be allowed to violate the storage capacity and incur penalty costs 5owever, due to the high
penalty costs incurred, the optimi!er will always try not to e&ceed the storage capacity
)n contrast to other resource categories, the available capacity of the storage resource is not aggregated by bucket
#he optimi!er always takes into account the capacity that is available on the final day of a bucket
Page 106 of 251
6or the storage resource, we recommend that you choose a factory calendar with no non%working days )f the final
day of a bucket were a non%working day, the optimi!er would assume an available capacity of 4
)n addition to the storage resource capacity, you can define a product%specific upper bound for on%hand stock in the
location product master #he optimi!er takes this upper bound into account if you set the .a&imum Product%Specific
Auantity Stored indicator in the SNP optimi!er profile #he optimi!er considers this a soft constraint, meaning that it
can be violated sub3ect to the calculation of penalty costs #hese penalty costs are assigned by the optimi!er, which
means that you cannot set them in the master data
1ou can also define a time%based upper bound for stock 6or more information about this, see ,efinition of !i$e%
Base# Constraints in 0nteractive Planning
#onstraints
1ou can assign a ma&imum of one storage resource to each location
2. Source Determination &OptimiGer'
)f your company has alternative source of supply options with different costs, you can use the optimi!er in Supply
Network Planning (SNP) to solve the following issues8
'here to produce, procure, store, and deliver (for e&ample, it can decide whether to use in%house production or
e&ternal procurement)
'hich products and product "uantities to produce, transport, procure, store, and deliver (product mi&)
'hich resources and which production process models (PP.s) or production data structures (P(Ss) to use
(technology mi&)
'hich locations to transport from and to (for e&ample, production plant%Q distribution center or distribution center %Q
customer)
/nlike heuristic%base# planning and Capable%to%Match planning (-#.), the SNP optimi!er does not base its sourcing
decisions on predefined :uota arrange$ents or rules but instead bases its decisions on costs #he optimi!er uses the
following as possible sources8
PP.s 4 P(Ss
#he main purpose of optimi!ed source determination using the SNP optimi!er is to define the production locations in
such a way as to reduce the number of stock transfers and associated stock transfer costs
#onstraints
#he SNP optimi!er does not take into account "uota arrangements or procurement priorities 5owever, it can be used
to create "uota arrangements for subse"uent heuristic%based planning runs 6or e&ample, after a longer term
optimi!ation%based planning (monthly, for instance) you can run shorter term heuristic planning runs using the "uota
arrangements created in the optimi!ation planning run as a basis for the heuristic planning runs 6or this, set the
.odify "uota arrangements indicator when you run the optimi!er in the background (see also the 6; help)
Since the optimi!er does not take into account "uota arrangements, it does not support an even distribution of
production over various locations either (regarding resource utili!ation or "uantity%based "uota arrangement) Nor
does it support single sourcing (procuring a product from only one preferred source)
#he optimi!er does not take into account e&ternal procurement relationships as sources of supply$ that is, no
scheduling agreements, contracts, nor purchasing info records )f you have assigned a means of transport to the
transportation lane generated from the e&ternal procurement relationship, the optimi!er takes this transportation
lane into account 5owever, the optimi!er does not create any orders for scheduling agreements or contracts during
planning (it only takes into account e&isting orders as fi&ed orders)
Prere*uisites
#he prere"uisites for source determination are the same as those for general optimi!ation%based planning8
Set /p of Planning Area
Set up of Master ,ata for the Opti$i6er
Creation of Mo#el Na$e an# 4ersion
Set /p of Supply Chain Mo#el
+elease of ,e$an# Plan to Supply Netork Planning
Page 107 of 251
/sing #osts to #ontrol Source Determination
Since the SNP optimi!er simultaneously takes into account all the conditions of a model to determine an optimal (most
cost%effective) solution, it is generally only possible to influence its choice of sources by using costs 6or e&ample, you
can use costs to prioriti!e sources by reducing the production costs at your preferred location 5owever, remember that
the optimi!er always takes all influencing factors into account8
/sing Production #osts to PrioritiGe Production $esources
1ou can influence the optimi!erOs decision regarding which location and resources to use for production by defining
corresponding production costs in the PP.4P(S 6or e&ample, if you want to define priorities for three different
PP.s4P(Ss, you can specify the lowest production costs for your highest priority PP.4P(S, higher costs for the
PP.4P(S with medium priority, and the highest costs for the PP.4P(S with lowest priority #o do this, define single%
level production costs or a cost function in the PP.4P(S
Note however that in addition to taking into account production costs when making its decision, the optimi!er considers
the costs for storing the PP.4P(S products and the available capacity of the resources re"uired for the PP.4P(S
/sing Transportation #osts to PrioritiGe the Procurement (ocation
1ou can influence the optimi!erOs decision regarding which locations to procure from, by defining corresponding costs in
the transportation lane 6or e&ample, if you want to define the priorities of two different procurement locations, enter
lower transportation costs for the transportation lane of your preferred location than those for the other transportation
lane #ransportation costs consist of the means of transport costs (costs from the .eans of #ransport section of the
transportation lane) and the product%specific means of transport costs (from the Product%Specific .eans of #ransport
section)
Note however that in addition to taking into account transportation costs when making its decision, the optimi!er also
considers other influencing factors, such as the storage costs and production costs of the location
System Action if Source #annot )e Found
)f there is no valid transportation lane for procurement type 6 (e&ternal procurement), the system creates an SNP stock
transfer with no reference to a source of supply )f there is no valid PP.4P(S for procurement type 0 (in%house
production), the systemOs behavior is governed by whether or not the SNP8 No Planned Order indicator has been set in
the planning version )f this indicator is set, the SNP optimi!er does not create any planned orders$ if it is not set, the
SNP optimi!er creates planned orders with no reference to a PP.4P(S
3. (ot SiGe Planning
1ou use lot si!e planning to specify which demand "uantities are to be made available in which buckets (periods) 1ou
can choose to do one of the following8
#o procure or produce the e&act demand "uantities of a product #he order si!e corresponds to the demand "uantity
#he main advantage of this method is the low storage costs )ts disadvantages include high costs for procurement
and setup
#o group several product demand "uantities from consecutive buckets into larger procurement lots or production lots
'ith this method, procurement or production is done in advance and you can make use of the economy of scale
cost savings
#he advantages of this method include low procurement and setup costs )ts main disadvantage is the high storage
costs
#he SNP optimi!er uses all the costs to determine the optimal (most cost%effective) procurement lot si!es,
production lot si!es, and transportation lot si!es 6or Finite Capacity Planning with the SNP optimi!er, both costs and
available capacities are relevant for lot si!e planning
)ncreased setup consumption and4or higher setup costs can be taken into account during planning or rough%cut
planning in Supply Network Planning (SNP) to facilitate integration with subse"uent Production Planning and
(etailed Scheduling (SAP APO PP4(S) #his makes it easier for Production Planning and (etailed Scheduling to
create feasible plans
Prere*uisites
#he prere"uisites for lot si!e planning are the same as those for general optimi!ation%based planning8
Page 108 of 251
(ot SiGe Planning for Production
'hen using the SNP optimi!er for lot si!e planning in production, you can model both setup consumption and setup
costs in the system 1ou can also influence lot si!e planning by defining minimum lot si!es, ma&imum lot si!es, and
discrete (integer value) lot si!es
Setup #onsumption
1ou can choose any of the following three options for modeling setup consumption in the system8
1. )f the past setup consumption amount per you know bucket, you can model setup consumption by reducing the
available capacity of the production resource accordingly )f the setup consumption remains the same across all
buckets, you can reduce the rate of the resource utili!ation in resource master data 6or e&ample, for a setup
consumption of <:a, enter a bucket capacity utili!ation rate of J:a
)f setup consumption varies across the different buckets, you can reduce the standard capacity for individual
buckets accordingly
)n this instance, you can choose the linear optimi!ation method for the optimi!ation run, meaning that discreti!ation
is not re"uired
2. )f the setup consumption level is not known but setup consumption is relatively low in comparison to bucket capacity,
you can define setup consumption in the PP. as a fi&ed bucket resource consumption
)n order for the optimi!er to be able to take into account the fi&ed resource consumption defined in the PP., you
must define a discreti!ation hori!on in the 6i&ed .aterial and 2esource -onsumption field of the SNP optimi!er
profile 1ou also have to choose the discrete optimi!ation method in this profile
3. )f the setup consumption level is not known and setup consumption is relatively high in comparison to bucket capacity,
you can run cross%period lot si!e planning 6or more information, see Cross%Perio# "ot Si6e Planning
Setup #osts
#he optimi!er primarily uses setup and storage costs as a basis for determining optimal lot si!es and lot numbers )f
setup costs are high and storage costs low, the optimi!er is most likely to plan large lots whereas if setup costs are low
and storage costs high, it will plan small lots
1ou can define the setup costs as fi&ed costs within the PP. cost function (choose the .aintenance pushbutton near
the -ost Profile field and enter the setup costs in the 6i&ed costs field) 1ou also have to choose the discrete
optimi!ation method in the SNP optimi!er profile and enter a discreti!ation hori!on in the PP. 0&ecution field on the
(iscrete -onstraints tab page
Integration
)f you have integrated SNP and PP4(S planning (the SNP PP. and PP4(S PP. are linked), the optimi!er takes into
account setup statuses from PP4(S #his means that the optimi!er does not take into account setup consumption and
setup costs if a PP4(S order for the associated PP4(S PP. already e&ists in the corresponding bucket 6or this, you
have to set the -ross%Period *ot Si!e Planning indicator (for Cross%Perio# "ot Si6e Planning) or the *ot Si!e Planning8
Not -ross%Period indicator (if your lot si!e planning is not cross%period) on the )ntegration tab page
inimum and a1imum (ot SiGes
)f, due to technical constraints for instance, a minimum or ma&imum lot si!e is re"uired for your production (for e&ample,
at least one entire tank of active ingredient must be produced), you can define minimum and ma&imum lot si!es 1ou
can choose one of the following two options for defining these minimum and ma&imum lot si!es8
1. 1ou define the minimum and ma&imum lot si!e in the PP.
2. 1ou define the minimum lot si!e on the *ot Si!e tab page in location product master data in con3unction with the 6i&ed
*ot Si!e or *ot%for%*ot lot%si!ing procedure #he SNP optimi!er takes these settings into account for integration
purposes (with PP4(S, for e&ample) #he minimum lot si!e defined in the product master applies to all the PP.s
that use this product as the header material )f the minimum lot si!e in the product master is larger than the
minimum lot si!e in the PP., the optimi!er takes into account the value from the product master #he ma&imum lot
si!e defined in the product master has no relevance for the SNP optimi!er
6i&ed lot si!e8 #he SNP optimi!er considers the value you specified for the fi&ed lot si!e as the minimum lot
si!e 0very time the PP. is e&ecuted, the PP. output "uantity (the output component "uantity) corresponds to
this fi&ed lot si!e
*ot%for%lot8 #he optimi!er takes into account the minimum lot si!e defined in the location product master as the
minimum lot si!e
)n order for the SNP optimi!er to be able to take into account the minimum lot si!es defined in the PP. or location
product master, you also have to choose the discrete optimi!ation method in the SNP optimi!er profile and enter a
discreti!ation hori!on in the .inimum PP. *ot Si!e field on the (iscrete -onstraints tab page #he optimi!er also takes
into account the ma&imum PP. lot si!e defined in the PP. when the linear optimi!ation method has been chosen 6or
this, you must set the .a&imum PP. *ot Si!e indicator from the Ceneral -onstraints tab page of the SNP optimi!er
profile
Page 109 of 251
Discrete &Integer "alue' (ot SiGes
)f, due to technical constraints for instance, you can only produce integer multiples of a lot (for e&ample, you can only
produce entire tanks of active ingredient and not ;D tanks), you can set the (iscreti!ation indicator in the PP. )n order
for the optimi!er to be able to consider this indicator, you must also choose the discrete optimi!ation method in the SNP
optimi!er profile and enter a discreti!ation hori!on in the )ntegral PP.s field on the (iscrete -onstraints tab page )f you
do this, the optimi!er always plans production in integer multiples of the output component "uantity
(efining a fi&ed lot si!e or lot%for%lot on the *ot Si!e tab page of the location product master data for integration purposes
(with PP4(S, for instance) has the following implications8
6i&ed lot si!e8 0very time the PP. is e&ecuted, the SNP optimi!er sets the output "uantity in the PP. to the value
you entered for the fi&ed lot si!e
*ot%for%lot8 0very time the PP. is e&ecuted, the SNP optimi!er sets the output "uantity in the PP. to the value you
entered in the 2ounding Balue field (on the *ot Si!e tab page) of the location product master
#he "uantity of input components and amount of resource consumption are ad3usted accordingly Since you can also
use the lot si!es defined in the location product master when creating PP4(S orders, you can plan with greater
precision
(ot SiGe Planning for Transportation
Fi1ed eans of Transport #osts
As with setup costs for production, the SNP optimi!er primarily uses fi&ed means of transport costs as a basis for
determining optimal transportation lot si!es )f these costs are high, the optimi!er is most likely to plan larger
transportation lots (meaning less shipments$ once every two weeks, for e&ample)
1ou can define these fi&ed means of transport costs in the .eans of #ransport section of the transportation lane )n the
-ost 6unction field, enter a transportation cost function for which you have defined fi&ed costs 1ou also have to choose
the discrete optimi!ation method in the SNP optimi!er profile and enter a discreti!ation hori!on in the .eans of
#ransport field on the (iscrete -onstraints tab page
inimum and a1imum (ot SiGes
1ou can define minimum and ma&imum lot si!es for transportation in the SNP lot si!e profile (transportation lanes) 1ou
then specify this lot si!e profile for a particular product in the Product%Specific .eans of #ransport section of the
transportation lane 1ou can thus define minimum and ma&imum transportation lot si!es for specific products
)n order for the optimi!er to be able to consider the minimum lot si!e that has been defined, you must choose the
discrete optimi!ation method in the SNP optimi!er profile and enter a discreti!ation hori!on in the .inimum
#ransportation *ot Si!e field on the (iscrete -onstraints tab page )f you set the .a&imum #ransportation *ot Si!e
indicator of the Ceneral -onstraints tab page in the SNP optimi!er profile, the SNP optimi!er also takes the ma&imum
transportation lot si!e into account when the linear optimi!ation method is chosen
Discrete &Integer "alue' Transportation (ots and eans of Transport
)f you only want to transport integer multiples of a transportation lot si!e (only entire pallets of a product, for e&ample),
you can define that you want the optimi!er to take this into account during planning by choosing the discrete
optimi!ation method in the SNP optimi!er profile and by entering a discreti!ation hori!on in the )ntegral #ransportation
*ots field of the (iscrete -onstraints tab page 1ou usually define the transportation lot si!e as a rounding value in the
SNP lot si!e profile (transportation lanes) Alternatively however, you can set in the .aintain Clobal SNP Settings
activity in -ustomi!ing for SNP that the optimi!er is to use the rounding value defined in the destination locationOs
location product master as the transportation lot si!e
Similarly, you can define that you want the optimi!er to plan means of transport only in integer values, by only
scheduling whole trucks for a shipment, for e&ample #o do this, enter a discreti!ation hori!on in the )ntegral .eans of
#ransport field
(ot SiGe Planning for Procurement
Fi1ed Procurement #osts
As with setup costs for production and fi&ed means of transport costs for transportation, the SNP optimi!er primarily
uses fi&ed procurement costs as a basis for determining optimal lot si!es for procurement )f these costs are high, the
optimi!er is most likely to plan large procurement lots (meaning less procurement operations$ once every two weeks, for
e&ample)
1ou can define these fi&ed procurement costs on the Procurement tab page of the location product master )n the -ost
function field, specify a procurement cost function, for which you have defined fi&ed costs 1ou must also choose the
discrete optimi!ation method in the SNP optimi!er profile and enter a discreti!ation hori!on in the Procurement Auantity
field on the (iscrete -onstraints tab page
inimumI a1imumI and Integral (ot SiGes
At present, the SNP optimi!er cannot take into account minimum, ma&imum, and integer value procurement lot si!es
during lot si!e planning 5owever, there is a workaround for modeling these lot si!e constraints8
Page 110 of 251
a. 6irst create your supplier as a location in your model

+. -reate a transportation lane between the supplier and the demand location
c. 1ou can now model the procurement lot si!e constraints as transportation lot si!e constraints (see the section on *ot
Si!e Planning for #ransportation)
4. Stock Planning
-ompanies have stock on hand to safeguard against uncertainties and fluctuations in demand 5owever, holding an
e&cessive amount of stock ties up too much capital and generates high storage costs )f there is insufficient on%hand
stock, there is a danger that une&pected demand might arise that cannot be fulfilled
#herefore, the SNP optimi!erOs main purpose in stock planning is to keep the on%hand stock between specific upper and
lower bounds
Prere*uisites
#he prere"uisites for stock planning using the SNP optimi!er are the same as those for general optimi!ation%based
planning8
Integration
'hen planning the on%hand stock, the SNP optimi!er takes into account goods receipts and issues that were caused by
other system application areas (PP4(S, deployment, or #ransport *oad +uilder, for e&ample) or fi&ed SNP orders
)f these orders involve goods issues that cannot be balanced by the optimi!er within the relevant bucket (period), the
optimi!er has an infeasible problem #o avoid this, you can specify in the SNP optimi!er profile (in the )ntegration tab)
that goods issues caused by stock transfers or planned orders are to be treated the same as the customer demand,
demand forecast, or corrected demand forecast, meaning that these demands do not have to be fulfilled )n the product
master on the SNP; tab page, you define penalty costs for non%fulfillment of these demands, which the SNP optimi!er
takes into account #his makes the problem feasible for the optimi!er 5owever, the solution provided may contain
shortfall "uantities
Storage costs
6irst, you can set for the storage cost calculation whether you want the SNP optimi!er to interpret the on%hand stock
per bucket as the average stock on hand per bucket or as the stock on hand at the end of the bucket8
Average stock on hand8 #he optimi!er calculates the storage costs by multiplying together the on%hand stock, the
storage costs defined in the location product master (see below), and the number of days in the bucket #his option
is most appropriate when receipts and issues are evenly distributed over a bucket
Stock on hand at end of period8 #he optimi!er calculates the storage costs by multiplying the stock on hand with the
storage costs defined in the location product master #his option is most appropriate when receipts and issues are
unevenly distributed over a bucket
1ou define storage costs for a specific product at a specific location in the Prod Storage -osts field on the
Procurement tab page of location product master data
1ou should always define storage costs since this is how you ensure that the SNP optimi!er does not plan any
unnecessary production /sing storage costs helps you to ensure that production, procurement, and transportation
always match demand as near to the time as possible
Since storage costs are defined on a product%specific basis, you can use them to control where (in which locations) a
product is stored
Storage costs are independent of storage resource consumption, which means you can define storage costs without
creating a corresponding storage resource
Adhering to a (ower )ound for Stock
Safety Stock Planning
#he SNP optimi!er decides whether safety stock is to be created for a product in specific locations, and if so, how it is
to be created
Page 111 of 251
1ou have to provide the optimi!er with the information about the level of safety stock that is re"uired 1ou can either
enter this level directly in the location product master based on past e&perience or use e&tended safety stock
planning to allow the system to determine it #he optimi!er automatically includes the results of e&tended safety
stock planning in a key figure 6or more information, see Safety Stock Planning
#he optimi!er considers safety stock as a soft constraint that can be violated with incurring penalty costs )n order for
the optimi!er to take safety stock into account, you have to either define penalty costs for violating safety stock in
the Safety Stock Penalty field on the Procurement tab page of the location product master, or define them as a
time%based key figure in interactive planning (planning book 9A#SOP# for instance)$ see also (efinition of #ime%
+ased -onstraints in )nteractive Planning #hese costs must be higher than the storage costs )f not, the optimi!er
would never plan safety stock
)n the SNP optimi!er profile (on the Ceneral -onstraints tab page), you can define whether you want the optimi!er
to take into account safety stock at all, and if so, whether you want it to use the absolute deviation value or the
relative deviation value when calculating the penalty costs for falling below the safety stock level 6or absolute
deviation, the optimi!er multiplies the absolute value fallen below with the penalty costs defined in the product
master (per day) 6or relative deviation, the optimi!er multiplies the percentage fallen below with the penalty costs
defined in the product master (per day)
#he safety stock level is not permitted to e&ceed the product%specific upper bound for storage defined in the location
product master (the .a&imum Stock *evel field of the *ot Si!e tab page)
DaysE Supply Planning
1ou can also use safety stock for static daysO supply planning with the SNP optimi!er 'hen using static daysO supply
planning, it should be ensured that there is at all times at least as much on%hand stock of a product as is re"uired within
the daysO supply hori!on
#o do this, define a safety stock method for the appropriate product on the *ot Si!e tab page in the location product
master (SX, .X, S., or ..) and enter either a safety daysO supply that is not period%dependent in the location product
master or a safety daysO supply that is period%dependent in the interactive planning table Note that for safety stock
methods S. and .., the SNP optimi!er only considers independent re"uirements as well as dependent and distributed
demands caused by fi&ed orders, since these demands and the demand locations are already known before the
optimi!ation run
#he optimi!er uses the daysO supply planning results as a basis for creating the safety stock
Adhering to an /pper )ound for Stock
Static /pper )ound for Stock
1ou can define a product%specific stock upper bound for a location product in the location product master data #o do
this, enter a value in the .a&imum Stock *evel field of the *ot Si!e tab page #he SNP optimi!er takes this upper bound
into account when planning if you set the .a&imum Product%Specific Auantity Stored indicator of the Ceneral
-onstraints tab page in the SNP optimi!er profile #he optimi!er considers the upper bound for stock as a soft
constraint, meaning that it can be violated sub3ect to the calculation of penalty costs #hese penalty costs are assigned
by the optimi!er, which means that you cannot set them in master data
1ou can also define a time%based upper bound for stock in interactive Supply Network Planning 6or more information
about this, see ,efinition of !i$e%Base# Constraints in 0nteractive Planning
1ou can specify a multi%product stock upper bound by defining the available capacity of a storage resource in the
resource master data #he SNP optimi!er takes this upper bound into account when planning if you set the Storage
-apacity indicator on the Ceneral -onstraints tab page in the SNP optimi!er profile (see also, Finite Capacity Planning)
Dynamic /pper )ound for Stock
1ou can use the shelf life functionality to define a dynamic stock upper bound for optimi!ation%based planning )n
product master data, if you set the Plng with Shelf *ife indicator of the Attributes tab page and enter a hori!on in the
associated Shelf *ife field, the optimi!er ensures when planning that at no time is there more stock on hand than
re"uired in the specified hori!on
6or e&ample, if you enter a shelf life hori!on of a week, you are specifying that you do not want any goods receipts to be
planned for the demand that e&ists in the week before this hori!on, which means that no stock should be kept on hand
for longer than a week prior to the demand
)n order for the SNP optimi!er to be able to take into account the productOs shelf life that you defined in the product
master, you must set shelf life as a soft constraint in the SNP optimi!er profile #o do this, go to the Ceneral -onstraints
tab and select the -ontinue /sing 0&pired Product radio button #he optimi!er then plans to continue using products
that have passed their e&piration date, but calculates penalty costs for doing so 'e also recommend that you set the
Product%)ndep Ley figure /se Penalty -osts )f you do this, the optimi!er does not use the procurement costs of the
location product to calculate penalty costs (the default setting) but instead uses penalty costs that are not product%
dependent, which you set yourself in the accompanying field
Page 112 of 251
Product Shelf (ife
#he SNP optimi!er can also take into account the shelf life of a product but in a restricted way At no point in time does it
try to plan more on%hand stock of this product than is re"uired in the corresponding bucket 5owever, if a larger product
"uantity has to be stored than the "uantity to be used in the bucket, the optimi!er considers the surplus as "uantities
that are to be disposed of as waste and calculates corresponding penalty costs
6or this, first set the Plng with Shelf *ife indicator of the Attributes tab page in the product master data (as previously
mentioned) and enter a hori!on in the associated Shelf *ife field #hen, in the SNP optimi!er profile, define shelf life as a
hard constraint by selecting the (ispose of 0&pired Product radio button on the Ceneral -onstraints tab page'e do not
recommend that you set the Product%)ndep Ley figure /se Penalty -osts )n this case, the optimi!er calculates the
costs for procuring the location product (defined in the product master) as penalty costs
#onstraints
'hen creating orders at the end of the optimi!ation run, the system does not distinguish between the "uantities the
optimi!er considers as waste and the other planned "uantities #his means that the sum from both "uantities is
displayed as the planning results (in interactive planning, for e&ample)
#he product shelf life defined in the product master data is not passed onto all the manufacturing levels, which means
for instance that the shelf life of an input component has no effect on the shelf life of an output component 6or
e&ample, if you define the shelf life of an active ingredient, the system does not transfer this shelf life to the
subse"uent pills containing this ingredient or their packaging
As with production, the product shelf life defined in the product master is not passed onto multiple locations during
transportation #his means that if a product is transported from one location to another, the shelf life hori!on starts
anew
#he conse"uence of this is that when there are cycles in the distribution network (transporting a product from one
location through another and then back to the start location), products lose their shelf life upon return arrival )n this
instance, the optimi!er would be able to continue using a product that, in fact, needed disposing as waste
OptimiGation Profiles
#he following table describes the profiles used by the SNP optimi!er #o access each profile individually, choose Supply
Network Planning @ 0nvironment @ -urrent Settings @ Profiles from the SAP 0asy Access screen 1ou can also define the
profiles in the -ustomi!ing for Supply Network Planning (SNP) 6or more information, see the )mplementation Cuide ().C)
or the field%level help (6; help)
Profile /sed in OptimiGation Planning $un
SNP optimi!er
profile
)n this profile, you choose which optimi!ation method you want to use during the optimi!ation run
(linear optimi!ation or discrete optimi!ation) and which constraints you want the system to take into
account
SNP cost profile
)n this profile, you assign a weighting to different cost elements in the ob3ective function (thus
determining how the costs relate to one another)
'e recommend that you only change the standard settings for test purposes when modeling #o
avoid undesired side%effects, you should not change the default setting of ;: in the production
system if possible #his setting corresponds to the costs entered in cost maintenance
SNP lot si!e
profile
(transportation
lanes)
)n this profile, you define minimum and ma&imum lot si!es for the shipment 1ou then specify this
profile for one specific product in the Product%Specific .eans of #ransport section of the
transportation lane 1ou can thus define minimum and ma&imum transportation lot si!es for specific
products
)f you wish to make shipments in integer multiples of a transportation lot si!e only, you can also
define the transportation lot si!e as a rounding value in this profile
#o enable the optimi!er to take into account the minimum lot si!es and rounding values defined, you
have to choose the discrete optimi!ation method in the SNP optimi!er profile
SNP optimi!ation
bound profile
)f you want to perform a new planning run after an SNP optimi!er planning run, you use this profile
to improve planning stability by restricting possible decision variable deviations from the previous
optimi!ation plan 6or e&ample, you can permit smaller deviations at the start of the planning hori!on
and then increase these towards the end of the hori!on to avoid too many last%minute planning
changes
1our new plan does not have to be based on the directly preceding optimi!ation run, you can also
choose earlier runs
SNP Priority
Profile
1ou can use the SNP priority profile to define priorities for pro#uct #eco$position and resource
#eco$position , that is, you can change the se"uence in which the optimi!er groups and plans
Page 113 of 251
Profile /sed in OptimiGation Planning $un
products and resources in partial problems 6or more information, see ,eco$position
SNP planning
profile
)n this profile, you can make basic settings for the various SNP planning procedures, such as
heuristic, optimi!er, deployment heuristic, deployment optimi!er, and #ransport *oad +uilder (#*+)
#he SNP planning profile that you activate in the SNP -ustomi!ing under .aintain Clobal SNP
Settings applies globally for all SNP planning procedures 6or some planning procedures, you can
overwrite the settings of the active profile by entering another SNP planning profile during e&ecution
of planning in the background
Parallel
processing profile
1ou use this profile to define how background 3obs are divided in parallel processes 1ou can
specify the number of concurrent parallel processes, the number of ob3ects per processing block,
and the server group )n each case, you define the profile for one specific application function, such
as the SNP optimi!er
1ou can also maintain the SNP optimi!er profile, the SNP cost profile, and the SNP optimi!ation bound profile in the
interactive planning desktop of Supply Network Planning
Decomposition
/sing the decomposition methods can reduce optimi!ation runtime and memory re"uirements in Supply Network Planning
(SNP) (ecomposition may also represent the only way for the SNP optimi!er to find a feasible solution in the event of large
discrete problems
(ecomposition is a fle&ible tool for balancing the tradeoff between optimi!ation "uality and re"uired runtime 'hen runtime is
unrestricted, the SNP optimi!er usually provides a better (optimal) solution without decomposition$ however, when a fi&ed
runtime has been specified, using decomposition could assist the optimi!er to find a better or, in fact, feasible solution
Features
Decomposition ethods
#he following decomposition methods are available8 #ime decomposition, product decomposition, and resource
decomposition 1ou can use time decomposition as well as product decomposition in con3unction with the linear and discrete
optimi!ation methods )t is only advisable to use resource decomposition in con3unction with discrete optimi!ation
#ime decomposition speeds up the solution process by dividing the source problem into a series of partial problems
#he system then solves these partial problems se"uentially
Product decomposition speeds up the solution process by forming product groups #he system solves the complete
model for one product group at a time according to the window si!e selected #he rule of thumb is as follows8 #he
smaller the window si!e, the less time it will take the system to find a solution, but the larger the window si!e, the better
the "uality of the solution found
2esource decomposition speeds up the solution process by analy!ing the material flow and basic optimi!er decisions
about production, procurement, and transportation to determine a resource se"uence #he optimi!er can then create
sub%problems for the individual resources, which are solved in se"uence #he optimi!er makes decisions in every sub%
problem that cause the resource to be loaded
)t is particularly advisable to use resource decomposition if the production processes always load the resources in a similar
se"uence 2esource decomposition does not reduce memory re"uirements )f you would like to reduce memory
re"uirements, you could use time decomposition alongside this decomposition method 1ou cannot use resource
decomposition in con3unction with strict prioriti!ation )f you want to use product and resource decomposition together, the
system carries out the resource decomposition first #he product decomposition then tries to improve upon the results of the
resource decomposition
SNP Priority Profile
1ou can use the SNP priority profile to define priorities for product and resource decomposition, that is, you can change the
se"uence in which the optimi!er groups and plans products and resources in partial problems
6or product decomposition, the se"uence of planning is normally based on the costs for non%delivery and the total demand
"uantity of the product 1ou can use the priority profile to assign priorities for important products and, thus, control the
se"uence for planning #he following rules apply8
#he system groups the products into partial problems according to their priorities and their dependencies defined in the
bill of materials )f a partial problem contains products with different priorities, due to product dependencies, the partial
problem takes on the priority of the product with the highest priority (that is, the priority with the lowest number)
#he system plans partial problems with different priorities separately, so no overlapping occurs
)f many products have the same or no priority, division into partial problems and the se"uence of planning are also
based on the costs of non%delivery and the product "uantity
Page 114 of 251
6or product decomposition, you can also control division into partial problems using window si!e, which you can specify for
the decomposition methods in the SNP optimi!er profile )f you select a small window si!e, the optimi!er plans products with
the same priority separately, since the partial problems are very small ()* P separate planning) )f you select a larger
window si!e, the optimi!er plans products with the same priority together in one partial problem (++* P planning together in
one partial problem)
Note that, due to prioriti!ation, the optimi!er no longer e&clusively considers the defined costs when covering demand
)nstead, the system plans the products with the highest priority first #he system only considers costs when solving the
individual partial problems
6or resource decomposition, the planning se"uence is generally predetermined by the production process models (PP.s) or
production data structures (P(Ss) )f the se"uence is not clear, or if you want another se"uence, you can change it by
assigning priorities to resources )n this way, you can reverse the standard order that the system uses to plan the assembly
and then the end products, or you can plan important resources that must be utili!ed for cost reasons first
Acti%ities
1. 1ou specify a decomposition method in the SNP optimi!er profile #o do this, select SNP Optimi!er Profile in the SNP
-ustomi!ing or in the current settings, and then select the Solution .ethods tab page
2. )f necessary, specify a priority profile in the current settings of SNP, under (efine SNP Priority Profiles, and assign it to
the decomposition methods on the Solution .ethods tab page
$unning the OptimiGer from the Interacti%e Planning Desktop
#he optimi!er proposes a plan for multiple products simultaneously based on the minimum procurement costs, storage
costs, transportation costs, and production costs without overloading resources
Prere*uisites
1ou have set up the planning area and planning book
.aster (ata Setup for the Optimi!er
1ou have maintained opti$i6ation profiles
Procedure
1. Select Advanced Planning and Optimi!ation @ Supply Network Planning @ Planning @ )nteractive Supply Network
Planning from the SAP 0asy Access screen #he Planning +ook8 SNP )nteractive Planning 4 SNP Plan (*ive) screen
appears
2. -hoose to display the shuffler 1ou then choose the location products you want to be used in the optimi!ation run
from here
3. 6rom the dropdown bo& in the first sort statement (Show), choose8 APO location product 1ou can also choose
specific location products to be used by choosing the icon to the right of this dropdown bo& )n addition, you can perform
a consistency check for this data by choosing -heck 0ntry
4. )f re"uired, limit the range of location products to be planned by making selections from the dropdown bo&es under the
second sort statement (that fulfill the following conditions) 6or e&ample, you can choose different planning versions
5. -hoose #he location products are now displayed in the selector
6. (ouble%click on a location product to display the current situation in the workspace to the right of the selector, or place
your cursor on a location product and choose the *oad data icon
7. Select the location products to be planned 1ou can choose either all the location products displayed (choose Select all),
or particular location products by placing your cursor on a location product, clicking and holding down the left mouse
button while dragging the cursor until all desired location products have been highlighted (alternatively, use the Shiftand
Arrow keys on your keyboard)
8. -hoose Optimi!er, to call the optimi!er #he SNP Optimi!er window appears
#he Optimi!er icon is displayed on the interactive desktop automatically if you are using the standard SNP planning
book SNP9> 5owever, )f you create your own planning books and wish to use the optimi!er in interactive planning, you
must specify that you want this icon to be displayed 1ou do this in the (esign mode of the interactive planning desktop
9. On the Optimi!ation tab page in the SNP Optimi!er window, you choose one of your predefined optimi!ation profiles,
cost profiles, and optimi!ation bound profiles +y choosing the icons , , and , you branch to the maintenance
Page 115 of 251
screens for the SNP optimi!er profiles, cost profiles, and optimi!ation bound profiles to make changes to e&isting
profiles, for e&ample
10. -hoose to start the optimi!ation run
#he current solution resulting costs determined by the optimi!er are displayed in the -urrent Solution area of the
Optimi!ation tab page #he individual steps of the optimi!ation process are displayed in the Status area during the
optimi!ation run and information about intermediary solutions is displayed in the Solution 2un area )n addition to this,
messages about the current optimi!ation run are displayed in the .essages area
1ou can also display the products that were selected for this optimi!ation run by choosing -hoose to branch to
the Supply Network Planning8 Optimi!er log file screen 6rom there, you can decide which type4form of log to display
(the message log, input log, or results in a te&t file for e&ample)
11. -hoose the Solutions tab page to view information about the previous optimi!ation runs )f you select a solution in the
right%hand screen area, the data corresponding to that solution appears in the left%hand area
12. -hoose the .essages tab page to view messages about the previous optimi!ation runs )f you select an optimi!ation
run in the left%hand screen area, the messages corresponding to that optimi!ation run appear in the right%hand area
Definition of Time.)ased #onstraints in Interacti%e Planning
A number of constraints are taken into account during the SNP optimi!ation run, including capacity constraints that have
been defined for resources 1ou usually use the SNP opti$i6er profile to specify which constraints you want the optimi!er to
consider during the optimi!ation run 5owever, in certain circumstances, it might be necessary to define constraints that are
time%based$ for e&ample, if a supplier provides varying "uantities of a product from bucket to bucket 1ou can define these
time%based constraints in interactive planning 1ou can set the following bounds8
An upper bound for e&ternal procurement (at product%location level)
An upper bound for stock on hand (at product%location level)
An upper bound for production (at product%PP. level)
An upper bound for transportation (at product%transportation lane level)
1ou cannot define any time%based lower bounds because this could prevent the optimi!er from finding a feasible solution
Stock on hand is an e&ception here since a time%based lower bound can be defined using safety stock
Prere*uisites
1ou have not set the )gnore #ime%+ased -onstraints indicator in the SNP optimi!er profile
Features
#here is a table available on the lower part of the screen in standard SNP planning book 9A#SOP# (planning area
9ASNP:>, data view OP#?#S+($ go to the SAP 0asy Access screen and choose Supply Network Planning @
)nteractive Supply Network Planning (All +ooks)) that, in addition to the standard interactive Supply Network Planning
functionality, has the following four key figures available8 /pper Procurement +ound, /pper +ounds for Stock,
Production /pper +ound, and #ransportation /pper +ound 1ou can define upper bounds for the individual key figures
in specific periods #he system takes these upper bounds into account when you run SNP optimi!ation (see 2unning the
Optimi!er from the )nteractive Planning (esktop)
1ou can use the (isplay (ependent Ob3ects function to define the upper bound for production for specific PP.s and the
upper bound for transportation for specific transportation lanes 1ou define the upper bounds for e&ternal procurement
and stock on hand at location product level
Only the relevant upper bounds are displayed on screen, based on your selection #hus, if you choose a location
product, only the upper bounds for e&ternal procurement and stock on hand are displayed
Note that when entering the upper bound for production, you do not enter the production "uantity, instead enter the
number of times the PP. concerned is to be e&ecuted #o do this, you set how often you want PP. e&ecution to be
started within a period #he duration of the PP. then determines the period in which product "uantities are available
6or e&ample, if you wish to define a "uantity of =: pieces as the upper bound on the third workday and the associated
PP. produces ;: pieces each time it is e&ecuted (taking = days), on the first workday you have to specify that you want
the PP. to be e&ecuted for a ma&imum of three times % and therefore enter = as the value for the first workday
)n an additional key figure for the individual upper bounds, you can show that an upper bound value of 4 is to be
interpreted as an actual upper bound by specifying not e"ual to 4 Otherwise, a value of 4 signifies that there is no upper
bound
)n the SNP optimi!er profile, you can also specify whether you want the optimi!er to consider the upper bounds for stock
as a soft constraint or a pseudo%hard constraint (on the 0&tended Settings tab page, activate or deactivate the -onsider
/pper +ounds for Stock as a Soft -onstraint indicator) #he optimi!er can violate soft constraints by calculating penalty
costs 1ou can define these penalty costs in a time%based key figure in planning book 9A#SOP#
Page 116 of 251
Pseudo%hard constraints can be violated but only by calculating infinitely high penalty costs, which means that the
optimi!er only violates this type of constraint if it cannot find any other feasible solution #he optimi!er considers all the
other time%based upper bounds that you define as pseudo%hard constraints
Safety stock is a time%based lower bound for stock on hand that you can define #he optimi!er always considers safety
stock to be a soft constraint that can be violated sub3ect to the calculation of penalty costs #here is another time%based
key figure in planning book 9A#SOP# that you use to define penalty costs for falling below the safety stock level
6urthermore, you can specify in the SNP optimi!er profile that you would like the system to ignore the time%based
constraints in the optimi!ation run (by going to the 0&tended Settings tab page and setting the )gnore #ime%+ased
-onstraints indicator) #his can be a good idea if you want to use an SNP optimi!ation bound profile for the optimi!ation
run, for e&ample )f you use time%based constraints in con3unction with the bounds from the optimi!ation bound profile,
the constraints might cancel each other out )f this occurs, the optimi!er will not be able to find a feasible solution
5owever, if you do use the SNP optimi!ation bound profile in con3unction with the time%based constraints, the optimi!er
takes into account the smaller of the upper bound values that have been defined Note that you can also define lower
bounds in the optimi!ation bound profile )f the lower bound defined here is higher than the upper bound defined in
interactive planning, the optimi!er will not be able to find a feasible solution
1ou can also define values for key figures using mass processing #o do this, select the Mass Maintenance of !i$e
Series Key Figures (Advanced Planning and Optimi!ation @ Supply Network Planning @ 0nvironment @ .ass
.aintenance of #ime Series Ley 6igures from the SAP 0asy Access screen)
$unning the OptimiGer in the )ackground
#he optimi!er proposes a plan for multiple products simultaneously based on the minimum procurement costs, storage
costs, transportation costs, and production costs without overloading resources
Prere*uisites
1ou have set up the master data for the optimi!er
1ou have maintained optimi!ation profiles
1ou have created a model name and version
1ou have set up the supply chain model
1ou have released the demand plan to Supply Network Planning
1ou have locked any inbound or outbound "ueues in the 02P system during the time of the optimi!ation run8
)f you cannot rule out that data will be transferred from an 02P system to the SAP S-. system (or from SAP S-. to
02P) using the -ore )nterface (-)6) during the optimi!ation run, you can lock inbound or outbound "ueues in the 02P
system from the SAP S-. system #his should prevent plan inconsistencies due to transaction data that is transferred
from the 02P system to SAP S-. during the optimi!ation run, which the optimi!er then ignores (uring the -)6
transfer, you can also prevent planning ob3ects from being locked for -)6 or the optimi!er
#o lock outbound "ueues, you can use the 4SAPAPO4-)6S#OPA/0/0S and 4SAPAPO4-)6S#A2#A/0/0S reports in
SAP S-. 2eports 2S#26-); and 2S#26-)= are available for locking inbound "ueues (see also, OSS note >JG<F;)
Procedure
1. 6rom the SAP 0asy Access screen, choose Advanced Planning and Optimi!ation @ Supply Network Planning
Planning Supply Network Planning in the +ackground Supply Network Optimi!ation
2. 0nter the planning book and data view
3. 0nter an SNP planning profile that you may have defined in -ustomi!ing for SNP #his contains basis settings for the
SNP planning procedures )f you do not specify a profile, the system uses the default profile activated in -ustomi!ing
4. 0nter a parallel processing profile that you may have defined in -ustomi!ing for SNP #his determines how the
background 3obs are divided into parallel processes
5. 0nter a selection profile in which you stored your selections in interactive Supply Network Planning or manually select
data for planning #o enter data manually, follow this procedure8
a. 0nter the planning version
+. 0nter the products and locations you wish to plan )f you intend to plan all the products and locations of the planning
version, you can leave these fields blank
6. )f you also want to plan all the products of a supersession chain as part of product interchangeability in SNP, make the
relevant setting6or more information, see Pro#uct 0nterchangeability in Supply Netork Planning
Page 117 of 251
7. )n the Source ,eter$ination field, select the level of a source of supply hierarchy at which you want the system to
consider sources of supply for in%house production #he default value is All *evels
1ou can use this field in the planning with aggregated resources process, for e&ample
8. Specify the start and end date that you want the system to consider for planning #his entry is optional )f you do not
enter a start and end date, the system uses the planning buckets profile that was specified in the data view
9. 0nter the name of the optimi!er profile that you want to use for this optimi!ation run
10. 0nter the name of the cost profile that you want to use for this optimi!ation run
11. 0nter the identifier for the optimi!ation bound profile you want to use for this optimi!ation run #his entry is optional
12. )f re"uired, set the .odify Auota Arrangements indicator
#he results of the optimi!ation run can be used to calculate "uota arrangements for use in the heuristic (inbound "uota
arrangements) and the deployment heuristic (outbound "uota arrangements) )f you set the .odify Auota Arrangements
indicator, the system automatically creates optimal "uota arrangements, which means that you do not need to maintain
them manually in the Supply -hain 0ngineer
1ou use the )nbound, Outbound, and +oth indicators to set whether the optimi!er is to modify and create inbound "uota
arrangements, outbound "uota arrangements, or both )n the Start (ate for .odification and 0nd (ate for .odification
fields, you can specify the hori!on within which the system is to modify and create "uota arrangements )f you leave
these fields blank, the system modifies "uota arrangements over the entire planning hori!on 1ou can also specify the
smallest period si!e for which the system is to modify and create "uota arrangements #hese options can help you to
improve performance
1ou should use this feature with caution since there is no back%up of the original "uota arrangements
)f you define a subset of the model for the optimi!ation run (for e&ample, some of the locations), then the "uota
arrangements will only be changed for the locations that are part of the subset #he "uota arrangements for the other
locations remain unchanged
'e recommend that you either optimi!e for the whole model or check the "uota arrangements for the remaining
locations and manually change them if necessary Only use this function if the planning situation for the optimi!ation run
can be viewed as a representative planning situation and the overall planning environment is fairly stable Otherwise the
results of optimi!ation will not lead to ade"uate "uota arrangements
13. -hoose 0&ecute
$esults
At the end of the optimi!ation run, you access the results by choosing Supply Network Planning @ Reporting @ Optimi!er *og
(ata Alternatively, you can display the results in interactive SNP planning (Supply Network Planning @ Planning @
)nteractive Supply Network Planning)
Automatic #ost =eneration
-osts play an essential role for optimi!ation%based planning in Supply Network Planning (SNP) #he optimi!er selects the
plan with the lowest total costs from all the permitted production and distribution plans #his means that the optimi!er also
makes business decisions based on the costs involved for covering a demand at a certain point in time, for e&ample
1ou can provide the optimi!er with the costs for planning by specifying your actual costs such as production and
transportation costs in the system 1ou can also define control costs that are in accordance with your business goals 6or the
planner, however, the conversion of business goals into control costs is not easy
'ith the automatic cost generation function, you can easily generate all the control costs relevant to the optimi!er (that is,
the cost model) #hesystem generates these costs automatically based on the business goals you have defined #he system
re"uires the main goal to be the ma&imi!ation of the service level 1ou can also define the following goals8
-onsideration of demand and product priorities
-onsideration of procurement priorities
)n addition, you can use this function to "uickly and easily create an optimi!ation%based production plan #o create a finite
(capacity%based) production plan, you only have to make a few additional settings (such as the consideration of capacities)
Features
=enerating the #ost odel
#he system generates the following control costs8
Storage costs
Production costs, that is, costs of the production model (PP.) or of the production data structure (P(S)
Product%specific transportation costs
Page 118 of 251
Procurement costs
Penalty costs for non%delivery
Penalty costs for late delivery
)n order for the system to be able to calculate the costs for a late delivery, you must define a ma&imum delay in the product
master data on the SNP ; tab page
#he system ignores all the costs you may have defined in the master data #hey remain unchanged in the system even after
cost generation, however
#he system does not generate the following costs, because it would re"uire additional information from the planner or
because the costs are only relevant to comple& scenarios8
-ost functions (production, shipment, procurement)
-osts for means of transport
-osts for the use of the available capacity of resources (costs for using the normal and ma&imum available capacities or
for falling short of the minimum available capacity)
)n addition, the system does not consider the cost profile for weighting costs that you can define for optimi!ation%based
planning
Properties of the =enerated #ost odel
#he system ensures the following properties of the generated cost model8
#he model has no anomalies
#he system defines the costs such that undesired effects do not arise, such as8
a. Not covering a demand due to too low penalties costs for non%delivery
+. Planning a shipment due to too low costs at the destination location
c. Planning a shipment to save storage costs
#he system also covers the demands as timely as possible
#he model is stable
#he costs are, for e&ample, independent of period length and transaction data
#he model is coherent
6or e&ample, the transportation costs increase proportionally to the shipment length and the product value increases
with the depth of production
#he system automatically uses the value ; for the value of raw products (products without input products) )f you want
the system to base the calculation of the product value on the actual storage costs, you can make this setting in the SNP
or #eploy$ent opti$i6er profiles on the Automatic -ost Ceneration tab page
#he system cannot guarantee this model property, because the first two properties have higher priority and it is not
always possible to guarantee all three
#he generated cost model is independent from the costs defined in the master data (e&cept for possible consideration of
storage costs) #he system does not support a combination of these two cost models (for e&ample, completion of the master
data cost model)
Definition of the )usiness =oals
#he system calculates the costs based on the business goals you have defined 6or further information see ,efinition of the
Business 5oals
Actions
1. (efine your goals for optimi!ation%based planning as described
2. )f, for e&ample, you want to create a finite (capacity%based) plan, set the corresponding indicator for the consideration of
capacity restrictions on the Ceneral 2estrictions tab page of the SNP or deployment optimi!er profile
3. Set the Automatic -ost Ceneration indicator in the SNP or deployment optimi!er profile
4. 0&ecute an SNP or deployment optimi!ation run 6or more information, see 2unning the Optimi!er in the +ackground,
2unning the Optimi!er from the )nteractive Planning (esktop, or 2unning (eployment Optimi!ation
5. (isplay the application log that is in the 2esults *og section and contains information about the generated costs 6or
more information about optimi!ation logs, see Application *ogs for Optimi!ers
Page 119 of 251
)f you want to create an optimi!ation%based production plan with the auto$atic cost generation function, first define your
business goals for planning #he system then uses these goals to automatically generate the corresponding control costs,
based on which the optimi!er makes planning decisions
#he main goal of planning is to ma&imi!e the service level 1ou can also define the following additional goals8
1ou define these goals in the SNP or #eploy$ent opti$i6er profile on the Automatic -ost Ceneration tab page
Features
#onsideration of demand and product priorities
1ou can define priorities for three different priority classes of the #e$an# and the safety stock8
-ustomer demand
-orrected demand forecast
(emand forecast
Safety stock
#he standard setting is that all priority classes and the safety stock have the same priority
)n addition, you can define that the system also considers the priority of products 1ou can enter this priority in the master
data of the location product on the SNP < tab page #he system considers the product priority in combination with the
demand priority 1ou can define which priority is more important and is to be considered by the system first
#o simplify this combination of both priority types, you must also subdivide the product priorities into three classes of A, +,
and - products
#he following figure shows e&actly how the system proceeds if the demand priority is more important than the product priority
or vice versa8
)f the demand priority is more important than the product priority, the system covers all the demand with priority class ; (such
as customer demand) for all location products first )t then covers all the demand with priority class <, and so on )f the
product priority is more important, the system covers all the demand of all priority classes for the location products with class
A first, then all the demand for the location products with class +, and so on
#onsideration of procurement priorities
1ou can define that the system considers the procurement priorities of production process models (PP.s) or production data
structures (P(S) as well as transportation lanes 1ou define this priority in the master data of the PP.s4P(S and
transportation lanes (specific to the product) #he procurement priority of sources of supply for in%house production is always
more important than the priority of sources of supply for e&ternal procurement (same as the SNP heuristic procedure)
#he system always tries to first cover all the demand of a period with receipts from all the sources of supply available in this
period (in the se"uence of the procurement priority of these sources of supply) Only after this does it try to cover the
demand with receipts from sources of supply from an earlier period )f the system has to switch to an earlier or later period, it
may not be able to follow this principle in this period
Page 120 of 251
#osts aintenance
plan with the lowest total costs from all the permitted production plans
/se this function to define all costs used by the optimi!er and assigned to the master data from a single point of access #he
master data is then automatically updated for the selected planning version
#o call the function, on the SAP 0asy Access screen, choose Advanced Planning and Optimi!ation .aster (ata @
Application%Specific .aster (ata@ Supply Network Planning @ .aintain -osts((irectory) or .aintain -osts (#able)
Features
1ou can define the following costs8
Production costs
Storage costs
5andling costs
Procurement costs
-osts for non%delivery
-osts for using the available capacity of resources
-ost functions
#ross.Period (ot SiGe Planning
)n some industry sectors (such as the process industry), setup activities have a great influence on lot si!e planning )f the
setup costs are relatively high in comparison to the storage costs, orders are grouped into large lots to save on set up costs
6or this reason, it is possible to run a cross%period lot si6e planning as part of opti$i6ation%base# planning within Supply
Network Planning 5ere, the optimi!er takes into account the setup statuses from the previous bucket if the same production
process model (PP.) is being used to produce a product in that bucket #his means that the optimi!er only schedules one
setup operation per lot si!e 6or this setup operation, the system then calculates the setup costs and setup consumptions
(fi&ed resource consumption and material consumption) that were defined in the PP. for the resource set with the -ross%
Period *ot Si!e indicator
#he SNP optimi!er does not support multi%level cross%period lot si!e planning, meaning that lot si!e planning can only be
done at production level
Integration
1. 'ithin the campaign planning business process, cross%period lot si!e planning represents the preliminary stage of the
actual campaign creation that is done in Production Planning and (etailed Scheduling (PP4(S) (uring planning, the
SNP optimi!er creates SNP planned orders that correspond to a production campaign that is created at a later point in
PP4(S 1ou can convert these SNP planned orders into PP4(S orders 6or more information, see -onverting SNP
and -#. Orders into PP4(S Orders
2. #he optimi!er is also able to consider setup statuses resulting from already planned PP4(S orders 'hen doing this, it is
possible to run an SNP PP. in a bucket (period) without taking into account setup e&penses, if there is a PP4(S order
with the associated PP4(S PP., or if the corresponding setup e&penses can be adopted from the previous bucket
Prere*uisites
#he steps listed below are general prere"uisites for running the SNP optimi!er8
#he following are special prere"uisites for cross%period lot si!e planning8
$esource master data
Page 121 of 251
#he optimi!er only takes into account the setup statuses from previous buckets for the resource for which the cross%
period lot si!e indicator has been set
Production process model (PP.)
'( #he PP. is permitted to use a ma&imum of one resource only for which the cross%period lot si!eindicator has been
set
< #he PP. is not permitted to use any other resources that have been specified with a fi&ed resource consumption
= #he PP. duration must be less than or e"ual to the smallest bucket from the planning buckets profile used
> #he minimum PP. lot si!es and the discrete (integer value) lot si!es refer to the cross%period lot "uantity
D #he optimi!er plans a ma&imum of one setup operation per bucket
Profiles
)n Supply Network Planning, you have also maintained the relevant profiles for SNP optimi!ation, in particular the SNP
optimi!er profile (from the )mplementation Cuide ().C), choose SAP Advanced Planner and optimi!er (SAP APO) @ Supply
-hain Planning @ Supply Network Planning @ Profiles @ (efine SNP Optimi!er Profiles) 6or more information, see
Optimi!ation Profiles and the corresponding )mplementation Cuide ().C) documentation
)n particular, you have made the following settings for cross%period lot si!e planning in the SNP optimi!er profile8
1ou have chosen (iscrete Optimi!ation as your optimi!ation method
1ou have entered the hori!on over which you want the optimi!er to take into account the setup statuses from this
previous bucket in the -ross%Period *ot Si!e field from the (iscrete -onstraints tab page #he optimi!er can only do this
if the PP. from the previous bucket is used to produce a product
)f you want the optimi!er to take account of setup statuses resulting from already planned PP4(S orders, you must have
activated the indicator -ross%Period *ot Si!e Planning on the )ntegration tab page A prere"uisite for this is that the
corresponding PP4(S PP. must be assigned to the SNP PP.
Acti%ities
1ou run the optimi!er from the interactive planning desktop or in the background 6or more information, see 2unning the
Optimi!er from the )nteractive Planning (esktop and 2unning the Optimi!er in the +ackground 6or general information
on the SNP optimi!er, see Optimi!ation%+ased Planning
#he optimi!er determines the most cost%effective solution to fulfil the demands 6or e&ample, to decide about lot si!es,
the optimi!er uses storage costs and setup costs 5aving larger lot si!es and only one setup operation per lot si!e saves
on setup costs but results in higher storage costs 'ith smaller lot si!es, multiple setups mean that more capacity is
re"uired and this results in higher setup costs
1ou display the individual stages and final results of the optimi!ation run in interactive planning on the Optimi!ation tab
page within the optimi!er window 1ou also receive a list of the costs determined by the optimi!er
Application (ogs for OptimiGers
'hen you e&ecute an optimi!ation%based planning function in Supply Network Planning (SNP) in the background (mass
processing), the system automatically generates an application log Amongst other things, this log contains planning results,
Page 122 of 251
such as planned orders and stock transfers created, as well as error, warning, and information messages #he input data for
the optimi!ation run and the costs of the solution determined by the optimi!er are also displayed, for e&ample
#he central Optimi!er *og (ata function is available for accessing optimi!ation run logs 6rom the SAP 0asy Access screen,
choose Advanced Planning and Optimi!ation @ Supply Network Planning @ 2eporting @Optimi!er *og (ata 1ou can use
this function to access the following SNP planning functions8
SNP Optimi!er
(eployment Optimi!er
-apacity *eveling (optimi!ation%based method)
Sourcing of 6orecast
Features
The OptimiGer (og Data function pro%ides an o%er%iew of the generated logs. Amongst other thingsI the list of logs
contains the following data8
*og status
A traffic light or flag indicates whether the optimi!ation run is still in progress, has already ended, or was terminated
with a message (see 6; help)
*og creator
Optimi!er profile used
Start and finish time of the run
2untimes of the individual optimi!ation steps
An optimi!ation run has three steps (data reading, model consistency check, and solution calculation, as well as
order creation)
#otal costs of solution
*og e&piration date
1ou specify the log e&piration date globally for all optimi!ation logs in -ustomi!ing for Advanced Planning and
Optimi!ation (APO) under +asis Settings Optimi!ation @ +asic 6unctions @ .aintain Clobal Settings 5owever,
you can also change this date for one specific optimi!ation run by choosing -hange 0&piration (ate #he log is
automatically deleted after the e&piration date if you e&ecute the 4SAPAPO4O.?20O2C?(A)*1 report
1ou can also delete the log from the list, set filters and sort entries
If you dou+le click a log or choose Display (ogI you recei%e the following data and su+.logs for the log.
Input Parameter
-ontains the settings that you made on the initial screen for the planning function
(ocation Products
-ontains the location products selected for the optimi!ation run
Deletion Time Period
Specifies a time period in which the system deletes e&isting planned orders and stock transfers before actual
optimi!ation
Input (og
-ontains the input data considered by the system during the optimi!ation run (that is, master data and transaction data)
#he data is divided into a number of tables (such as 0#?*O-.A#) 1ou can display the content of these tables on the
right%hand side of the screen 6or more information, see Opti$i6ation 0nput "og
$esults (og
-ontains all results of the optimi!ation run, such as planned orders, stock transfers, resource consumption, costs, and
penalty costs #he data is divided into a number of tables (such as 0#?P2O.O) 1ou can display the content of these
tables on the right%hand side of the screen
$esult Indicators
-ontains indicators that display the "uality of the optimi!ation solution, such as service level and shortfall of safety stock
6or more information, see +esult 0n#icators
01planations
-ontains the results of an e&planation tool run (see below)
01tended $esults (og
Page 123 of 251
)n this log, you can display the results of the optimi!ation run in the interactive SNP planning form
essage (og
-ontains error messages, warning messages, and information messages generated by the system during the
optimi!ation run #hey are ordered according to meaning, that is, whether they refer to the optimi!ation run settings or to
the three main steps of the run
Trace File
All individual optimi!ation run steps are logged in this te&t file )t is saved on the optimi!ation server, but you can also
download it to your own computer
#osts
-ontains detailed information about the costs of the solution determined by the optimi!er 6or more information, see
+esulting Costs of Opti$i6ation
Solution Juality
-ontains the costs of the best solution determined by the optimi!er up to the time displayed )f you used a
decomposition method, you can also relate the costs the partial problem solved up to this time
1ou can use the log to determine whether you can reduce the optimi!er runtime without effecting solution "uality
Note that the input log and the results log, as well as the deletion time period, are only displayed if you have set the
'rite All *og (ata indicator in the optimi!er profile being used 0ven if an error occurred in the first step of the
optimi!ation run (data reading), the log may not be available
Bou can also download the input log and the results log to your own computer. To do thisI choose Download
Input (og or Download $esults (og. The logs are then sa%ed in $0(ATIO te1t format.
If you select a log and choose 01plainI you go to the 01planations of SNP OptimiGation $esultsscreen. From this
screen you can e1ecute the e1planation tool which e1plains two important e1ceptional situations of an optimiGation
runC non.deli%eries and shortfall of safety stock.
OptimiGation Input (og
*og generated during an optimi!ation run in Supply Network Planning (SNP) )t contains all input data considered by the
system during the optimi!ation run (that is, master data and transaction data) #he data is utili!ed in numerous tables (such
as 0#?*O-.A#)
/se
#he input log is part of the application log that you can access by selecting Advanced Planning and Optimi!ation @ Supply
Network Planning @ 2eporting @ Optimi!er *og (ata from the SAP 0asy Access screen 6or more information, see
Application "ogs for Opti$i6er
1ou can download the log and give it to SAP support as a te&t file for analysis
Structure
#he individual sections of the log are detailed below
(egend
6lag8 W P Active, K K P )nactive
Prof8 SNP optimi!er profile
/nits8 +#ime P +ase unit of time (days)
+-urr P +ase currency
+Prod P +ase unit of measure of the product
5an/n P 5andling unit
Sto/n P Storage unit
+2es P +ase unit of measure of the resource
0SK#T$(
#hese entries describe the general properties of the model #he entries are determined from the SNP optimi!er profile or
directly from the model (iscrete (integer value) transportation lots are displayed in the history of the optimi!ation runs (the
Vtrace fileO)$ choose #ools APO Administration Optimi!ation *og (isplay
N+/-L Number of buckets
NP2O( Number of products
Page 124 of 251
N*O-S Number of locations
NS/+* Number of sublocations
NP2O. Number of production process models
N20SO Number of resources
N206A Number of resource families
NA2-S Number of arcs
N6*00 Number of fleets
N(0.- Actual number of demand classes
N(0.A Number of demand vectors
()S26 Prof8 0nd bucket for increasing production resource discretely
()S2X Prof8 0nd bucket for using fi&ed production resource consumption
()S#2 Prof8 0nd bucket for using discrete fleet on transportation lanes
()SP2 Prof8 0nd bucket for using integral PP.
LA.PA Prof8 0nd bucket for campaign T (>;F planning
#2*OS Prof8 0nd bucket for using minimum transportation lot si!e
P2*OS Prof8 0nd bucket for using minimum production lot si!e
-OS#2 Prof8 0nd bucket for using transportation cost function
-OSP( Prof8 0nd bucket for using production cost function
-OSP- Prof8 0nd bucket for using procurement cost function
0TKIN0@20B
#hese entries are the e&ternal keys for internal ob3ect keys )n particular, there is a list of calendar data for the day numbers,
and a list of product and location numbers for the C/)(s
)NL01 C/)( (uni"ue internal key)
0WL01 -orresponding e&ternal key
0TK)/#2DF
#hese entries show the bucket definition (time intervals) upon which all optimi!er planning is based #he source of this
information is either the selected planning buckets profile or the planning start and end date
+/-L0Y +ucket no
BA*#O 0nd date of the bucket (day no, ;
st
day is ;4;4;9G:) +#ime
BA*62 +egin date of the bucket (day no, ;
st
day is ;4;4;9G:) +#ime
0TKAT0$IA(
#he validity period of all products selected for optimi!ation is stored here At present, this always encompasses the entire
planning hori!on
.A#)(Y Product C/)(
+-L#O Balid to bucket no
+-L62 Balid from bucket no
0TK(O#
)nformation about the e&istence or non%e&istence of a defined handling capacity (handling resource) is stored here for
locations
*O-)(Y *ocation C/)(
20S)N 5andling%in resource C/)( or dummy resource, if no handling%in resource is maintained
.AW)N Prof8 6lag8 5andling%in resource active (not activated, if dummy resource is used)
20SO/ 5andling%out resource C/)( or dummy resource, if no handling%out resource is maintained
.AWO/ Prof8 6lag8 5andling%out resource active (not activated, if dummy resource is used)
Page 125 of 251
0TKS/)(O#
A storage resource is defined here with information about whether it can be e&tended S/+)( is currently the resource )(
#he source of this information is the location master and, if in e&istence, storage resource maintenance 0&tension is allowed
if the resource has two capacity variants
S/+)(Y Storage resource C/)( or dummy resource, if no storage resource is maintained
.AW6* Prof8 6lag8 Storage resource active (not activated, if dummy resource is used)
0TK(O#AT
#he properties of location%dependent products are shown here 2esource consumption is listed, in particular #he source for
this is the location product master
.A#)(Y Product C/)(
S/+)( Storage C/)(
5-OS# Storage cost +-urr4+Prod
+/-6* Prof8 6lag8 Storage cost8 .ultiply by bucket length
SSP0N Penalty for not covering safety stock +-urr4+Prod
.AWS# .a&imum stock level of the product
.AW6* 6lag8 .a&imum stock level active
S#O-L )nitial stock +Prod
-ON)N -onsumption of input handling capacity 5an/n4+Prod
-OS)N 5andling%in cost +-urr4+Prod
-ONO/ -onsumption of output handling capacity 5an/n4+Prod
-OSO/ 5andling%out cost +-urr4+Prod
20-#) Coods receipt processing time in days +#ime
)SS#) Coods issue processing time in days +#ime
-A-ON Storage capacity consumption Sto/n4+Prod
'AS6* 6lag8 Shelf life penalty is active
'AS#0 Shelf life8 Penalty for wasted "uantity +-urr4+Prod
S#O(/ Shelf life8 Storage duration +#ime
6-OS# *inear procurement cost +-urr4+Prod
6P026 Procurement permitted and4or product sub3ect to incremental optimi!ation
SS.#5 Safety stock method
0TK$0SO/$#0
Production resources that are used in the production process models are listed here (see the 0#?P2O20S section below)
/N)BO is currently always e"ual to ;
20S)(Y 2esource C/)(
26A)( 2esource family C/)( (currently the same as resource)
/N)BO /nitary volume +2es
LA.PA 6lag8 2esource is a campaign resource
0TK$0SFA
Production resources are allowed to be e&tended here if a second capacity variant has been defined in the resource master
#he resource family is currently always the same as the production resources (one%to%one)
26A)(Y 2esource family )(
.AW6* 6lag8 2esource has a capacity constraint
()S-2 Prof8 6lag8 (iscrete increase of resource family
0TKF(00T
6leet refers to the transportation resource that has been specified for a transportation lane A possible e&tension and the
costs related to it are determined from the resourceOs second capacity variant
6*0)(Y 6leet C/)(
Page 126 of 251
.AW6* 6lag8 -onsider ma&imum fleet capacity
#/N)A -apacity ; of one truck #ra/n;
#/N)+ -apacity < of one truck (not used) #ra/n<
#/N)- -apacity = of one truck (not used) #ra/n=
0TKA$#
All the transportation lanes that have been defined for the model in the Supply -hain 0ngineer are listed here A2- refers to
a transportation lane4means of transport combination
A2-)(Y Arc C/)(
6*0)( 6leet C/)(
*O-62 *ocation from C/)(
*O-#O *ocation to C/)(
##1P0 )( for means of transport
(/2A# (uration of shipment (base time unit) +#ime
2N(#2 +ucket offset (rounding limit for transportation times)
#-#1P Bariable transportation cost for the fleet +-urr4#ra/n;
()S-2 6lag8 /sing discrete transportation fleets
2*(/2 2esource load duration +#ime
0TKA$#AT
Product%dependent properties for the transportation lane are shown here (ata is taken from the Supply -hain 0ngineer
Standard entries are generated if the product has not been assigned to the transportation lane and the All Products indicator
has been set at the transportation lane #he lot si!e information is taken from the lot si!e profile (transportation lanes)
defined at the transportation lane
A2-)(Y Arc C/)(
.A#)(Y Product C/)(
BA*#O Balid to date (base unit of time) +#ime
BA*62 Balid from date (base unit of time) +#ime
.)N*O .inimum number of lots #2BO*
.AW*O .a&imum number of lots #2BO*
.AW6* 6lag8 .AW*O active
#2BO* *ot si!e in product units +Prod
#-ONA -apacity consumption for <> hours #ra/n;4+Prod
#-ON+ -apacity consumption for the transportation time that is less than <> hours #ra/n;4+Prod
#-ON- -apacity consumption (not used)
#-OS# Bariable transportation cost for Rarc productR +-urr4+Prod
S/+-O 6lag8 VWO Product will be subcontracted
0TK(O##
#he handling resourceOs available capacity is listed here 6igures are determined from the resourceOs first capacity variant
Caps in the intervals are defined by the resource calendar or shipping calendar of the location
20S)(Y 5andling resource C/)(
BA*#OY Balid to date (base unit of time) +#ime
.AW5A 5andling capacity 5an/n4+#ime
-O/N( .inimum resource consumption
/NP0N Penalty per unitary volume dropping minimum capacity +-urr4/nivo
Page 127 of 251
0TK(O#/#
A possible e&tension of the handling resourceOs available capacity is listed here 6igures are determined from the resourceOs
second capacity variant by subtracting the first capacity variant values Caps in the intervals are defined by the resource
calendar or shipping calendar of the location
20S)(Y 5andling resource C/)(
)N-5A /pper bound for increasing handling capacity 5an/n4+#ime
)NP0N Penalty per unitary volume for increasing capacity +-urr4/nivo
0TKS/)(O##
#he storage resourceOs available capacity is listed here 6igures are determined from the resourceOs first capacity variant
#he interval gaps are defined by the resource calendar
S/+)(Y Sublocation C/)(
.AWS* -apacity volume of storage (sublocation) Sto/n
0TKS/)(O#/#
A possible e&tension of the storage resourceOs available capacity at a location is listed here 6igures are determined from the
resourceOs second capacity variant by subtracting the first capacity variant values #he interval gaps are defined by the
resource calendar
S/+)(Y Sublocation (storage) C/)(
)N-S* /pper bound for increasing storage capacity Sto/n
0TK$0S#
#he production resourceOs available capacity is listed here 6igures are determined from the resourceOs first capacity variant
#he interval gaps are defined by the resource calendar
.AW20 Production resource capacity +2es4+#ime
--OS# -ost per unitary volume for capacity +-urr4/nivo
0TK$0SFA#
A possible e&tension of the production resourceOs available capacity is listed here 6igures are determined from the
resource calendar
26A)(Y 2esource family C/)(
)N-26 /pper bound for increasing production resource /nivo4+#ime
Page 128 of 251
0TKF(00T#
#he transportation resourceOs available capacity is listed here 6igures are determined from the resourceOs first capacity
variant #he interval gaps are defined by the resource calendar
6*0)(Y 6leet C/)(
.AW6* -apacity measured in trucks #ruck4+#ime
/NP0N Penalty per unitary volume dropping minimum capacity +-urr4#ruck
0TKF(00T/#
A possible e&tension of the transportation resourceOs available capacity is listed here 6igures are determined from the
resource calendar
6*0)(Y 6leet C/)(
)N-6* /pper bound for increasing fleet capacity #ruck4+#ime
)NP0N Penalty per unitary volume for increasing capacity +-urr4#ruck
0TKP$OO
#he properties of the production process model (plan or PP.) are stored here 5owever, the PP. needs to have been
assigned to the model in the Supply -hain 0ngineer #his information is defined in master data maintenance for the PP.
#ime%dependent PP.s are converted into multiple entries for the optimi!er, and the validity period of each one is set
accordingly #he master resource is the PP. calendar resource
P2O)(Y Production process model C/)(
*O-)( *ocation C/)(
.A#)( Product C/)(
*O#SX 6i&ed lot si!e of the location product +Prod
+-L#O Balid to date in buckets
+-L62 Balid from date in buckets
P.)NA .inimum production lot si!e Pro.od
P.AWA .a&imum production lot si!e Pro.od
.AW6* 6lag8 P.AWA active
(/2A# (uration8 : P one day, ; P two days +#ime
()S-2 6lag for using discrete production
P-OS# Bariable cost of PP. +-urr4Pro.od
2N(P2 +ucket offset
20S)( 2esource C/)( for calendar
0TKP$O$0S
-onsumption of production resources for the PP. is listed here, as defined in the production process model master data in
.ode -apacity -onsumption
O6S#OY -onsumption time offset +#ime
+-L#OY Balid to date of bucket interval
B-ONS Bariable consumption of the resource +2es
6-ONS 6i&ed consumption of the resource +2es
Page 129 of 251
0TKP$OAT
#he product flow for the PP., as defined in the Products section of production process model master data, is listed here )t
represents the bill of materials (+O.) structure, where finished products have a plus sign and input products a minus sign
.A#)(Y Product C/)(
O6S#OY )nput4output time offset +#ime
+-L#OY Balid to date of bucket interval
O/#)N Output(T) or input(%) "uantity +Prod
6-ONS 6i&ed input(%) "uantity +Prod
0TK$0SINI
-ontains the initial setup statuses of the resources for cross%period lot si!e planning (set up or not set up)
0(A#0Y 0nd date +#ime
+(A#0Y Start date +#ime
A/AN# Output "uantity for master product +Prod
APP*) Application8 P%QPP4(S S%QSNP
S0#/P 6lag8 Order with setup
0TK(O#P$OD
#he re"uired safety stock (target stock levels), fi&ed demands (6P2O( with minus sign), and receipts for the products are
defined in this table #he latter entries result from planned orders and stock transfers that had been fi&ed before the optimi!er
was run #his fi&ing is done both manually and when orders are transferred to the PP4(S application 2eceipts and issues
are also fi&ed when the optimi!er has been run incrementally (for a subset of products from the model)
.A#)(Y Product C/)(
+/-L0Y (ate bucket of safety stock and 6P2O(
SA6#1 Safety stock (not a demand]) +Prod
.AWS# .a&imum stock level of the product +Prod
SAP0N Penalty for not covering safety stock +-urr4+Prod
S#P0N Penalty for violating the ma&imum stock level +-urr4+Prod
6P2O( -onfirmed production, includes intransit "uantities +Prod
SB##1 Safety daysO supply
0TKD0#(TI
#he ma&imum delay that is to be allowed for finished products is defined here #he values are taken from the product master
(the SNP ; tab page) #here are currently only three categories8 ; for customer demands, < for corrected demand forecasts,
and = for demand forecasts -osts for delivering the finished products late, or for not delivering them at all are also defined
#he values are taken from the product master (the SNP ; tab page) #he values are not defined as time%dependent in SAP
APO, meaning that +-L#O is the same as the planning end date
(0.-*Y (emand class (highest priority P ;)
.A#)(Y Product C/)(
+-L#OY Balid to bucket
*AP0N Penalty for lateness +-urr4(+#imeY+Prod)
.AW*A .a&imum lateness +#ime
N(P0N Penalty for not delivering +-urr4+Prod
0TKD0AND
#his table contains all the customer demands and forecast demands that have been read for the model from live-ache
Page 130 of 251
.A#)(Y Product C/)(
+/-L0Y (emand date given in bucket
(0.AN Auantity of demand +Prod
0TKP$O#)ND
#arget procurement corridor
.A#)(Y Product C/)(
+/-L0Y +ucket
*O'+N *ower bound +Prod
/PP+N /pper bound +Prod
)N)#B )nitial value (result of previous run) +Prod
+N(6* 6lag8 /pper bounds are active
0TKP$OD)ND
#arget production corridor
+/-L0Y +ucket
*O'+N *ower bound Pro.od
/PP+N /pper bound Pro.od
)N)#B )nitial value (result of previous run) Pro.od
0TKT$AN)ND
#arget stock transfer corridor
A2-)(Y Arc C/)(
.A#)(Y Product C/)(
+/-L0Y +ucket
0TKST#2)ND
#arget stock level corridor
.A#)(Y Product C/)(
+/-L0Y +ucket
0TKD0(I)ND
#arget demand fulfillment corridor
.A#)(Y Product C/)(
(0*A1Y *ateness measured in buckets
Page 131 of 251
+/-L0Y +ucket
0TKT$AN#OS
Stock transfer cost functions are defined here #hese functions are analy!ed on the basis of this formula8 -ost P 6)W-O T
BA2-OY (W E O2)CN) #he cost function is assigned to the product%dependent transportation lane in the Supply -hain
0ngineer
A2-)(Y Arc C/)(
O2)CNY Smallest value #ra/n;
6)W-O 6i&ed cost +-urr
BA2-O Bariable cost +-urr4#ra/n;
0TKP$OD#OS
Production cost functions are defined here #hese functions are analy!ed on the basis of this formula8 -ost P 6)W-O T
BA2-OY (W E O2)CN) #he cost function is assigned to the plan in master data maintenance for the production process
model
O2)CNY Smallest value Pro.od
BA2-O Bariable cost +-urr4Pro.od
0TKP$O##OS
Procurement cost functions are defined here #hese functions are analy!ed on the basis of this formula8 -ost P 6)W-O T
BA2-OY (W E O2)CN) #his cost function is assigned to the product in the location product master
.A#)(Y Product C/)(
O2)CNY Smallest value +Prod
BA2-O Bariable cost +-urr4+Prod

$esulting #osts of OptimiGation
*og generated during an optimi!ation run in Supply Network Planning (SNP) )t contains detailed information about the costs
of the solution determined by the optimi!er
/se
#he log is part of the application log that you can access by selecting Advanced Planning and Optimi!ation @ Supply
Network Planning @ 2eporting @ Optimi!er *og (ata from the SAP 0asy Access screen 6or more information, see
Application "ogs for Opti$i6ers
Structure
#he individual fields of the log are detailed below
Field Information displayed
/ser #he plannerKs name
-urrent date #he date the Optimi!ation run was e&ecuted
#ime #he time when the Optimi!ation run was e&ecuted
version #he planning version used for the optimi!ation run
Optimi!er profile #he optimi!er profile used for optimi!ation run
-ost profile #he cost profile used for optimi!ation run
+ound profile #he SNP optimi!ation bound profile used for optimi!ation run
Page 132 of 251
Field Information displayed
#otal costs #he total costs associated with the solution proposed by the system #he cost categories
are displayed in total values for all ob3ects throughout the supply chain #he total costs are
made up of all the cost categories displayed in this log
Production costs #he total production costs for this plan based on the pieces produced using the production
process models PP.s with the associated cost data, displayed in total values for all
ob3ects throughout the supply chain
Procurement costs #he total procurement costs for this plan
Storage costs #he total storage costs for this plan based on the capacity consumption of products stored
at the storage resource, displayed in total values for all ob3ects throughout the supply
chain
Storage e&pansion #he total costs incurred as a result of a re"uirement to e&pand storage capacity for this
plan displayed in total values for all ob3ects throughout the supply chain
Penalty costs for safety
stock deficit
#he total penalty costs incurred because the safety stock level falls below the specified
re"uirement for safety stock for this plan displayed in total values for all ob3ects throughout
the supply chain
#ransportation costs #he total transportation costs for this plan displayed in total values for all ob3ects
throughout the supply chain
5andling capacity
e&pansion
#he total costs incurred as a result of a re"uirement to e&pand the handling capacity of
one or more resources for this plan displayed in total values for all ob3ects throughout the
supply chain
#ransportation capacity
e&pansion
#he total costs incurred as a result of a re"uirement to e&pand the transportation resource
capacity for this plan displayed in total values for all ob3ects throughout the supply chain
Production resource
e&pansion
#he total costs incurred as a result of a re"uirement to e&pand the production resource
capacity for this plan displayed in total values for all ob3ects throughout the supply chain
(elay penalty #he total penalty costs incurred as a result of all deliveries that are late displayed in total
values for all ob3ects throughout the supply chain
Shortfall penalty #he total penalty costs incurred as a result of all deliveries of all products that are less than
the "uantity ordered displayed in total values for all ob3ects throughout the supply chain
Penalty costs for e&ceeding
ma&imum stock on hand
#he total penalty costs incurred for e&ceeding ma&imum stock on hand
Penalty costs for falling
short of minimum resource
utili!ation
#he total penalty costs incurred for falling short of the minimum resource utili!ation defined
in the resource master data

$esult Indicators
)ndicators that show the "uality of an optimi!ation solution
/se
)f you have successfully e&ecuted an optimi!ation run and have created a log for this run, the log contains a series of result
indicators #hey show the "uality of the optimi!ation solution with reference to the following factors8
(emand 6ulfillment
Stock *evel
2esource /tili!ation
6rom the SAP 0asy Access screen, you choose Advanced Planning and Optimi!ation Supply Network Planning
2eporting Optimi!er *og (ata 1ou then select an optimi!ation run with a double%click #he tree structure of the logs
contains the entry 2esult )ndicatorswith the two aggregation levels .odel%(ependent )ndicators and *ocation Product%
(ependent )ndicators
Structure
#he system calculates the following indicators for the "uality of an optimi!ation solution8
Demand Fulfillment
Service level (in percent)
(elayed demand fulfillment (in percent)
Page 133 of 251
Average delay (in days)
#he system also calculates these indicators separately for the following priority classes8
-ustomer re"uirement
(emand forecast
_Pseudo%hard` demand (if you have made the setting in the optimi!er profile that the system considers the dependent
demand and4or distribution demand of fi&ed orders as a pseudo%hard constraint #hat means that the system may allow
shortages for which it calculates penalty costs)
Stock (e%el
6ulfillment of safety stock demand in percent
Average stock level
/tiliGation
#he system calculates the resource consumption for the following resource types
Storage resources
5andling resources
1ou can also display the resource utili!ation for each period in the capacity view of interactive SNP planning #he capacity
view always shows the current resource utili!ation based on the data saved in live-ache 5owever, the data calculated by
the e&planation tool is available for as long as the output log of the optimi!ation run is available
#he system calculates the result indicators at the level of the model and each location product or resource, and displays this
data directly in the optimi!ation run log or under the 2esult )ndicators entry #he indicators for the utili!ation of the individual
resources are displayed in the result log
#o aggregate the data of each location product at different levels (such as location level or product level), you can transfer
the data to the SAP Net'eaver /sage #ype +usiness )ntelligence (+)) using the (ataSource :APO?SNP?)N()-A#O2 6or
more information, see the documentation for component SAP Net'eaver under +) -ontent Supply -hain .anagement
Planning 1ou can also simulate a simple aggregation with the SAP *ist Biewer (A*B)
The following ta+le shows the aggregation le%els at which the result indicators are displayed in the optimiGation logC
Ser%ic
e (e%el
Delay
in
Percen
t
A%erag
e Delay
Ser%ice
(e%el
per
Deman
d #lass
Delay in
Percent
per
Demand
#lass
A%erage
Delay per
Demand
#lass
A%erag
e Stock
(e%el
Safety
Stock
Shortfal
l
/tiliGation
per
$esource
odel & & & & & & & &
(ocation
Product
& & & & & & & &
$esourc
e
&

01planation of the OptimiGation $esults
Optimi!ation%based planning in Supply Network Planning (SNP) pursues a global solution approach by considering all
restrictions and costs simultaneously and across the entire model )t therefore fre"uently finds a better solution than is
possible with other planning methods 5owever, the results of the optimi!ation run are not always easy to understand
1ou can use the e&planation tool to have the system e&plain two significant e&ceptional situations of an optimi!ation run8
Non%delivery
Shortfall of safety stock
#his function shows you the possible causes for the e&ceptional situations in the optimi!ation run log 1ou can use the
causes shown to check whether you can solve the problem by increasing capacities or e&tending hori!ons, for e&ample #he
system also suggests additional orders that you could use to remedy the missing "uantities
Among other things, you can specify the location products for which you want the e&planation, and how detailed it should be
Page 134 of 251
Prere*uisites
1ou have e&ecuted an optimi!ation run and created a log for this run (that is, you have set the 'rite All *og (ata
indicator in the SNP or deployment optimi!er profile) #he e&planation tool refers to the result of the optimi!ation run as
you see it in the log
+etween the optimi!ation run and e&planation run, you have not changed the SNP or deployment optimi!er profile you
used for the optimi!ation run 1ou have also not changed the optimi!ation%relevant settings in planning version
management
)n the case of a deployment optimi!ation run, you have chosen an optimal cost allocation #he e&planation tool does not
support fair share or push distribution
Features
Non%deliveries and lack of safety stock can have the following five causes8
-apacity -onstraints
#ime%+ased -onstraints and .a&imum *ot Si!es
Product Availability
*ead #ime
-osts
#he e&planation tool displays these causes, but does not e&plain why the optimi!er fulfills the demand of one product but not
of another when there is a lack of capacity
#apacity #onstraints
)n the SNP or deployment optimi!er profile, you have defined that the optimi!er is to consider certain capacity constraints
#he optimi!er considers the resource capacity defined in the resource master data
A possible cause for non%deliveries is that the system cannot fulfill the demand with the available resource capacity
#he system shows you the following data of the capacity problem8
2esource with the capacity problem
Number of the period (bucket) where the capacity problem occurs
.issing capacity of the resource
)f your planning buckets profile also includes daily periods, the system cannot determine any capacity problems caused by
calendar problems within the time frame covered by daily periods 6or e&ample, the system cannot suggest working on a
holiday could make up capacity
Time.)ased #onstraints and a1imum (ot SiGes
)n interactive SNP planning, you have defined time%based constraints (upper limits) for the capacity of specific sources of
supply (such as for production or transportation) 6or more information, see ,efinition of !i$e%Base# Constraints in 0nteractive
Planning )n the SNP or deployment optimi!er profile, you have also or alternatively defined that the optimi!er is to consider
ma&imum lot si!es
#he system displays the following data8
Name of the source of supply for which you have set the upper limit or ma&imum lot si!e
Name of the product for which you have set the upper limit or ma&imum lot si!e
Procurement type of the location product (in%house production, e&ternal procurement, and so on)
Number of the period where the capacity problem occurs
Auantity by which you must raise the upper limit to solve the problem )n the case of the production upper limit, the
system does not show the "uantity but rather the number of e&ecutions of the production model (PP.) or production
data structure (P(S) An e&ecution of the PP. or P(S corresponds to the output "uantity you specified in the
PP.4P(S
Product A%aila+ility
A possible cause for non%delivery can be that products are not available because a source of supply does not e&ist (for
e&ample, because the bill of material has not been completely defined)
#he system shows you the following data of the product availability8
Name of the product and location
Number of the period in which the product "uantity is missing
.issing "uantity of the product
Page 135 of 251
#he system does not check the validity of PP.s4P(Ss or transportation lanes )t also does not check the validity of time%
dependent parameters of PP.s4P(S (such as material consumption)
)f you have defined a PP.4P(S that is not valid until the middle of the planning hori!on, for e&ample, the system does not
determine any availability problems in the first half of the planning hori!on
(ead Time
(ue to a long duration of shipment and production, the lead time it takes for a product to be available in a specific period can
stretch over several periods #he system therefore fre"uently cannot fulfill demands because the lead time stretches into the
production or stock transfer hori!on, or the planned delivery time #he lead time can even stretch back into the past (before
the planning period)
#he system shows you the following data of the lead%time8
Name of the product and location
Name of the source of supply
Procurement type of the location product
)f the lead%time stretches into the past, the procurement type is S (initial stock level)
.issing "uantity of the product
Start and finish time of the order
Number of days by which the corresponding hori!on (production or stock transfer hori!on) or the planned delivery time
has been violated
#osts
#he fulfillment of the demand and the safety stock re"uirement is called a soft constraint for the SNP or deployment
optimi!er #hat means there are penalty costs for not fulfilling the demand )f you have set the penalty costs for non%delivery
and safety stock shortfall too low in the location product master data, the optimi!er may decide not to fulfill the demand #his
may be the case if the total costs are lower when demand is not fulfilled
#he system displays this possible cause in a message
)f you have not defined penalty costs for safety stock shortfall, the optimi!er cannot determine the cause )f you run a model
consistency check, you will, however, see a corresponding message
Order Suggestions
#he system suggests additional orders that you could use to remedy the missing "uantities
)f you use the suggested orders or try to solve the e&ceptional situations another way depending on the displayed causes, a
new optimi!ation run can however still lead to similar or different problems due to the dependencies
6or e&ample, if you increase the capacity of a resource to remedy the missing "uantities of a specific product, the system
can use the additional capacity to cover the missing "uantities of another product with higher priority
Further Information
#he e&planation tool only generates one possible e&planation for each e&ceptional situation 5owever, there may be other
e&planations as well 6or e&ample, if the system finds a capacity bottle%neck for a resource and suggests increasing the
capacity of this resource, another solution might be to increase the capacity of an alternative resource
)f the results of the e&planation tool are incorrect, this might be because the optimi!ation solution on which they are based
was not optimal (for e&ample, due to runtime restrictions)
Acti%ities
#o e&ecute the e&planation tool, from the SAP 0asy Access screen, choose Advanced Planning and Optimi!ation @ Supply
Network Planning @ 2eporting @ Optimi!er *og (ata #hen select an optimi!ation run and choose 0&plain #he
0&planations of the SNP Optimi!ation 2esults screen appears 5ere you make settings such as the target and level of detail
of the e&planation, and choose 0&ecute 6or more information, see Configuration of the -&planation !ool
After you have e&ecuted the e&planation run, you see the Optimi!ation 2un W screen that displays the logs for the selected
optimi!ation run #he tree structure contains the entry 0&planations with the subentries -onfiguration and 0&planation
2esults )f you double%click on these entries, you see your entry data and4or the results of the e&planation run on tab pages
on the right side of the screen )f the upper table on the right side of the screen contains several entries, you can double%click
on an entry in the lower table to see its detailed data
1ou can also e&ecute the e&planation tool from the Optimi!ation 2un W screen by choosing 0&plain
)f you want to e&ecute the e&planation tool in the background, choose Advanced Planning and Optimi!ation @ Supply
Network Planning @ 2eporting @ 0&planation of Optimi!ation 2esults
Page 136 of 251
#onfiguration of the 01planation Tool
1ou can configure the e&planation tool for an optimi!ation log in Supply Network Planning (SNP) according to your
re"uirements #his means you can choose which e&ceptional situations you want e&plained and how detailed you want the
e&planation to be #his affects, for e&ample, the comple&ity of the calculation and thus the runtime as well
ProcessC
1. Selection of the OptimiGation $un
1ou can select a specific optimi!ation run directly or you can specify which run of a specific user is to be e&plained
(going backward8 the fourth to last run is run no >, for e&ample)
2. Target of the 01planation
1ou can specify whether you want an e&planation for the causes for non%delivery only, or for the causes for safety stock
shortfall only, or both )n addition, you can specify the priority classes of the demand for which you want the system to
determine these causes (demand forecast, customer demand, and so on)
1ou also have to show the system how your model is structured +y doing so, you are giving the system information
about the se"uence in which it is to check the possible causes for an e&ceptional situation (epending on whether your
model is based on control costs or actual costs or whether it is in the structure phase, other causes for the e&ceptional
situation could be possible Since the causes are dependent on one another, the check se"uence of these causes is
crucial for the analysis
#he following table shows the se"uence of the analysis depending on the model8
odel +ased on control costs
(Such as high non%delivery costs
with the goal of ma&imi!ing the
service level)
odel +ased on +usiness &actual'
costs
(Such as prices as costs for non%
delivery)
odel in the structure phase
(master data is in the structure
phase and might not yet be
complete)
-osts
#ime%based constraints and
ma&imum lot si!es
-apacity restrictions
5ori!ons (such as production
hori!on)
Product availability
Planning hori!on
#ime%based constraints and ma&imum
lot si!es
5ori!ons
-osts
Planning hori!on
-osts
#ime%based constraints and
ma&imum lot si!es
5ori!ons
Planning hori!on
)n the e&planation results, the analysis phase displayed is the one in which the system has determined the cause
1ou have defined high penalty costs for non%delivery in the location product master data to ensure that the system
covers as many demands as possible Since your model is therefore based on control costs, you set this as the target of
the e&planation
5owever, the e&planation tool ascertains that a demand was not covered A probable cause is that you have not set the
penalty costs for non%delivery high enough to prevent non%deliveries According to your setting, the system first checks
whether or not the penalty costs are the cause for the non%delivery )f so, the system does not have to check for any
other causes (such as lack of capacity)
3. O+,ect Selection
)n many cases, e&planations are only useful and necessary for a subgroup of the location products in an optimi!ation
run 6or e&ample, you can choose to see the e&planations only for the non%deliveries for the most important products
and4or customer locations
1ou can select the location products with a selection you have created in interactive SNP planning or you can enter
them directly
4. (e%el of Detail of the 01planation
1ou can specify how detailed you want the systemOs e&planations to be 6or e&ample, the most detailed e&planation
would e&plain the non%delivery for each location product, period, and priority class #he least detailed e&planation level
would e&plain the non%delivery for all location products in the entire e&planation hori!on
1ou can specify the following parameters8
(e%el of detail8 1ou specify how detailed you want the e&planations to be #he options available are8
Aggregated e&planations for all selected location products
Aggregated e&planations for all products in a location
Aggregated e&planations for a product in all locations
Page 137 of 251
0&planations for each location product
1ou have defined that you want the system to generate aggregated e&planations for all selected location products 1ou
see the e&planation that a total of J hours of production capacity are missing for all selected location products
)n this case, you cannot tell how much production capacity is necessary to remedy the missing "uantity of a specific
location product #o see this information, you must specify that you want the system to generate e&planations for each
location product
01planation horiGon8 1ou can enter a time frame for which you want the system to generate e&planations
01planation for each period!priority class8 1ou can specify whether you want the system to generate the e&planation
for each period and each priority class, or for the entire e&planation hori!on and not separately according to priority
classes
Discrete restrictions8 1ou can specify whether or not you want the system to consider the discrete restrictions defined
in the SNP optimi!er profile or deployment optimi!er profile when it runs a cause analysis
$untime8 1ou can restrict the runtime of the e&planation tool )f you have defined that the system also considers
discrete restrictions (see above), we recommend that you restrict the runtime
OptimiGation $un Termination
1ou can use this function to terminate optimi!ation runs in a VgentleO fashion, without interrupting current processes )t is
particularly suited to runs that were started interactively but can also be used for background runs )f you start an
optimi!ation run interactively, you might want to use this function in the following circumstances8
)f you discover that you have defined a runtime that is too long and would like to perform a new optimi!er run with a
shorter runtime
)f you can conclude from the messages or graphics displayed during the optimi!ation run that the system has already
found a solution but the optimi!er continues the run, trying to improve on this solution, and you want to accept the
solution that has already been found and terminate the run
Prere*uisites
1ou can only terminate optimi!ation runs that you have started yourself #o terminate runs started by other users, you need
system administrator authori!ation (authori!ation ob3ect S?2X*?A(. that must include authori!ation field A-#B# E activity)
Features
)f you terminate an optimi!ation run, the system brings the run to a proper conclusion, which means that it saves all the
data that has been determined by this point in time and creates a complete log Any solutions found by this time are also
saved and recorded in the log
#he system makes regular checks to see if the user has terminated the optimi!ation run 5owever, it might take some
time before the system receives this information and terminates all the current processes )t is not possible to VgentlyO
terminate the optimi!ation run during its initial data collection (data reading) period)f it takes too long to terminate the
optimi!ation run with this function, you can also terminate the run immediately )f you do this, the system does not save
any data from the current run and also terminates log creation immediately, which means that the log generated might
be incomplete 1ou need system administrator authori!ation to perform this abrupt optimi!ation run termination (see the
Prere"uisites)
Acti%ities
Terminating an OptimiGation $un =ently
1. 6ollow this SAP APO 0asy Access menu path8 APO Administration @ Optimi!ation @ System .onitoring @ #erminate
Optimi!ation 2uns
2. Select the optimi!ation run you wish to terminate and choose with the "uick info, 6inish Optimi!ation 2un
3. #he system completes the data collection period if necessary, saves the data, and generates a complete log
Terminating an OptimiGation $un A+ruptly
1. 6ollow this SAP APO 0asy Access menu path8 APO Administration @ Optimi!ation @ System .onitoring @ Process
Overview
2. -hoose with "uick info, (isplay Optimi!er Processes
3. Select the optimi!ation run you wish to terminate and choose 6inish Process
4. #he system terminates the optimi!ation run and log generation immediately )t does not save any data
Page 138 of 251
Heuristic.)ased Planning
#he heuristic is used as part of a repair%based planning process consisting of the heuristic, capacity leveling, and
#eploy$ent #he heuristic run processes each planning location se"uentially and determines sourcing re"uirements #he
heuristic processing groups all demands for a given product at a location into one demand for the bucket #he heuristic run
determines valid sources of supply and corresponding "uantity based on pre%defined percentages for each source of
supply ("uota arrangements), or procurement priorities for transportation lanes and production process models (PP.s) or
production data structures (P(S) #he demands are then passed through the supply chain to calculate a plan 5owever, this
plan is not necessarily feasible #he planner can then use capacity leveling to ad3ust the plan and formulate a feasible plan
+oth the key figures upon which the heuristic is based and the planning hori!on are determined by the planning book
.acros can also be used to define how you want to calculate general key figures such as #otal (emand and Stock on 5and,
or product%specific key figures such as Safety Stock, 2eorder Point, and #arget Stock *evel (for more information, see
A#vance# Macros and SNP Functions)
Process
1. 1ou run the heuristic
2. 1ou run capacity leveling
3. 1ou run deployment
4. 1ou run the #ransport *oad +uilder (#*+)
The Heuristic $un Process Flow
#he heuristic plans all distribution demands for all locations within the distribution network before e&ploding the +O. and
processing dependent demand at the production locations #he system e&plodes the +O. only when you choose a
multilevel heuristic run
Factors #onsidered in Processing
*ocation products
*ow%level codes of the location products
Balid production process models (PP.s)
Balid transportation lanes
Auota arrangements or procurement priorities
*ead times
-alendars
*ot si!e rules
Scrap
-omponent availability
SNP demand profile
Page 139 of 251
SNP supply profile
(emand profile
Other #onsiderations
#he heuristic run considers all demand for a given product4location combination within one period as one demand
#he heuristic planning se"uence is governed by the low%level codes of the location products 6or more information, see
*ow%*evel -ode (etermination
#he initial solution produced by the heuristic run may not be feasible because the system assumes that capacity is
infinite #he planner must then ad3ust the plan by leveling resource capacity 6or more information, see -apacity
*eveling
#he heuristic run results do not include pegging orders back to the original individual re"uirement because re"uirements
are bucketed
Heuristic Profiles
#he following table describes the profiles used by the SNP heuristic 1ou can define these profiles partly in the location
product master and partly in the -ustomi!ing or in the current settings for Supply Network Planning (SNP) 6or more
information, see the )mplementation Cuide ().C) or the field%level help (6; help)
Profile /se in Heuristic Planning $un
Planning calendar
(time streams)
Specifies the planning calendars the system uses to determine when you can produce, transport, and
so on
SNP demand profile
(product master)
Specifies how the system calculates demand
SNP supply profile
(product master)
Specifies how the system calculates supply, that is, key figures such as production, and distribution
receipts
SNP rounding
profile
Specifies how the system is to round order proposal "uantities to create deliverable units
*ot si!e profile
(product master)
Specifies which lot%si!ing procedure is to be used during planning )n this profile, you can also define
additional constraints, such as minimum or ma&imum lot si!es, or a rounding value
SNP lot si!e profile
(transportation
lanes)
)n this profile, you define minimum and ma&imum lot si!es for the shipment 1ou then specify this
profile for one specific product in the Product%Specific .eans of #ransport section of the transportation
lane 1ou can thus define minimum and ma&imum transportation lot si!es for specific products
)f you wish to make shipments in integer multiples of a transportation lot si!e only, you can also define
the transportation lot si!e as a rounding value in this profile
SNP re"uirements
strategy
Specifies how "uantities forecasted in (emand Planning are to be produced and how the demand
forecast is consumed by sales orders
SNP planning
profile
heuristic, optimi!er, deployment heuristic, deployment optimi!er, and #ransport *oad +uilder (#*+)
Settings applies globally for all SNP planning procedures 6or some planning procedures, you can
overwrite the settings of the active profile by entering another SNP planning profile during e&ecution of
planning in the background
Parallel processing
profile
1ou use this profile to define how background 3obs are divided in parallel processes 1ou can specify
the number of concurrent parallel processes, the number of ob3ects per processing block, and the
server group )n each case, you define the profile for one specific application function, such as the
SNP heuristic

(ow.(e%el #ode Determination
1ou use this function to determine the low%level codes of location products before running heuristic%base# planning in Supply
Network Planning (SNP) #he low%level code specifies the bill of material (+O.) level and supply chain location at which a
location product is situated #he SNP heuristic needs this information to be able to determine the correct planning se"uence
for the location products, thus ensuring that demands are fulfilled correctly )t is important to maintain the planning se"uence
if you are running the SNP heuristic for only a part of your supply chain model
'e recommend that you always e&ecute this function before an SNP heuristic run if changes have been made to the
production process model (PP.) or transportation lane master data that are relevant to low%level code determination and
thus for the SNP heuristic planning se"uence
Page 140 of 251
Features
#he system determines the low%level codes for a given planning version$ that is, for an entire model 1ou cannot restrict
it to individual products and locations of the model since there would be no way of ensuring that the low%level codes for
the supply chain were determined correctly
#he system takes into account all SNP%relevant sources of supply, such as PP.s and transportation lanes, for the
individual products that are valid from any date within the planning hori!on #here cannot be any cycles in the
transportation lanes
#he system uses the productOs position in the bill of material and the location assigned to the product to determine the
low%level code #he highest low%level code (a code of :) is attributed to the finished product assigned to the final location
in the supply chain (a customer location for instance) #he second highest low%level code (;) is attributed to the finished
product at the penultimate location (a distribution center for instance), and so on #he system assigns low%level codes to
the individual components at the different +O. levels in the same way
#he SNP heuristic then plans the location products in the low%level code se"uence, first planning the location product
with low%level code : and so on
After running this function, a list of location products with assigned low%level codes is generated for the specified
planning version 1ou display this list by choosing (isplay 2esults
Acti%ities
1. #o access the low%level code determination function, follow this SAP APO 0asy Access menu path8 Supply Network
Planning @ Planning @ Supply Network Planning in the +ackground @ (etermine *ow%*evel -ode
2. 0nter the planning version and e&ecute the function
3. )f re"uired, display the results (see above)
4. 2un the SNP heuristic in the background or from interactive Supply Network Planning #he heuristic uses the low%level
codes to determine the correct planning se"uence for location products 6or more information, see 2unning the
5euristic in the +ackground
1ou can also restrict planning to specific low%level codes on the initial screen for running the SNP heuristic
$unning the Heuristic in the )ackground
#he heuristic in Supply Network Planning (SNP) is used to create a mid%term procurement, production, and transportation
plan
Prere*uisites
1ou have maintained the heuristic profiles (optional)
1ou have set up the master data for the heuristic
1ou have created a model name and version
1ou have set up the supply chain model
1ou have released the demand plan to Supply Network Planning
1ou have determined the low%level codes
1ou have locked any inbound or outbound "ueues in the 02P system during the time of the heuristic run8
)f you cannot rule out that data will be transferred from an 02P system to the SAP S-. system (or from SAP S-. to
02P) using the -ore )nterface (-)6) during the heuristic run, you can lock inbound or outbound "ueues in the 02P
system from the SAP S-. system #his should prevent plan inconsistencies due to transaction data that is transferred
from the 02P system to SAP S-. during the heuristic run, which the heuristic then ignores (uring the -)6 transfer, you
can also prevent planning ob3ects being locked for either -)6 or the heuristic
#o lock outbound "ueues, you can use the 4SAPAPO4-)6S#OPA/0/0S and 4SAPAPO4-)6S#A2#A/0/0S reports in
SAP S-. 2eports 2S#26-); and 2S#26-)= are available for locking inbound "ueues (see also, OSS note >JG<F;)
Procedure
5. 6rom the SAP 0asy Access screen, choose Supply Network Planning @ Planning @ Supply Network Planning in the
+ackground @ Supply Network Planning in the +ackground #he Supply Network Planning8 Planning 2un screen
appears
8. 0nter an SNP planning profile that you may have defined in -ustomi!ing for SNP #his contains basis settings for the
SNP planning procedures )f you do not specify a profile, the system uses the default profile activated in -ustomi!ing
Page 141 of 251
6. 0nter a parallel processing profile that you may have defined in -ustomi!ing for SNP #his determines how the
background 3obs are divided into parallel processes
9. Specify that you want to use the hori!on you defined as the planning buckets profile in the planning book for planning
(select 0ntire Planning 5ori!on) or specify a shorter planning hori!on
:. 0nter the planning version and the product or range of products that you want to be planned during this planning run )f
you choose the location heuristic (see step G), you also have to enter the location or range of locations for which you
want the heuristic to be run )f you leave this field blank, the system plans all eligible locations
Alternatively, you can specify a selection profile that you saved in interactive Supply Network Planning
)f you choose the location heuristic, you also have the option of restricting planning to specific low%level code, see step G
;. (efine the scope of the planning run8
)f you select Network (5euristic), the system plans the specified products at all locations of the supply chain model
where these products are assigned
)f you select *ocation (5euristic), the system plans the specified products at the specified locations 1ou can thus
choose to plan only a part of the model for instance
'ith both heuristic options, you can specify whether you want the system to take into account all the bill of material
(+O.) components of the chosen products during planning #o do this, set this indicator8 Take into account found
components in planning run #he system then also plans the dependent demand of the products 5owever, with the
location heuristic, the system plans only those components that have been assigned to the specified locations
#he planning se"uence is governed by the low%level codes of the location products 1ou use the etermine Low-Le!el
"ode function to determine these low%level codes before running the heuristic (see also8 "o%"evel Co#e ,eter$ination)
#he heuristic first plans the product with the highest low%level code : (such as a finished product at a customer location),
then the one with the second highest low%level code ; (such as a finished product at a distribution center), and so on
#his guarantees correct demand coverage even when a part model is selected
)f you wish to run the heuristic in interactive Supply Network Planning, you have the option of running a network
heuristic, a location heuristic, or a multilevel heuristic #he multilevel heuristic is a network heuristic that also takes into
account +O. components )nteractive Supply Network Planning does not have a location heuristic that takes into
account +O. components
6urthermore, you can specify that you also want to plan all the products of a supersession chain as part of product
interchangeability in SNP 6or more information, see Pro#uct 0nterchangeability in Supply Netork Planning
<. )f you wish to run net change planning, select Net -hange Planning #his means that the heuristic run plans only those
location products for which a planning file entry has been set #he system sets this planning file entry if a planning%
relevant change has been made to the location product since the last heuristic run$ for instance, if the demand situation
of the location product has changed
Net change planning can be performed only if you set the SNP8 -hange Planning Active indicator beforehand in the
planning version #he active planning version is the only version to support net change planning
3. )n the Source (etermination field, select the level of a source of supply hierarchy at which you want the system to
consider sources of supply for in%house production #he default value is All *evels
1ou can use this field in the planning with aggregated resources process, for e&ample
54. -hoose whether you want the heuristic to also consider a ma&imum vendor capacity (that may have been specified for
scheduling agreements) when taking into account scheduling agreements as supply sources #he options available to
you are listed below8
)f you select /nrestricted -apacity, the system does not take into account vendor capacities
)f you select #ransportation *ne SA -apacity, the heuristic, during planning, takes into account the vendor capacity
specified in the Ley 6igure8 .a&imum -apacity field for the transportation lanes of a scheduling agreement item
'hen working with scheduling agreements, you use this option, for e&ample, if you want to restrict the capacity of
means of transport that have been maintained for transportation lanes
)f you select *ocation Product SA -apacity, the heuristic, during planning, takes into account the vendor capacity for
the entire scheduling agreement item that you specified in the key figure entered in the Ley 6igure8 .a&imum
-apacity field
55. )f necessary, enter the appropriate key figures for determining ma&imum vendor capacity, plus the planning book and
data view that you want the system to use to derive these key figures
57. .ake settings for the application log generated in the planning run )n the *og Availability field, enter the number of days
you want the log to be saved for #he default value is =: days
5. 1ou can also define whether the log contains detailed information, such as data for SNP planned orders
and stock transfers created, and whether this is displayed directly at the end of the planning run 1ou can
also display the log after the heuristic run by choosing (isplay *ogs
Page 142 of 251
58. -hoose 0&ecute
#apacity (e%eling
#he capacity leveling function is an e&tension of heuristic%base# planning in Supply Network Planning (SNP) #he SNP
heuristic run is an infinite form of planning that does not take into account capacities and can thus cause resource overloads
1ou can use SNP capacity leveling to clear resource overloads by moving orders or partial order "uantities into previous or
subse"uent periods using forward or backward scheduling )n addition, you can transfer orders to alternative resources in the
same period
SNP capacity leveling is used to level specific bottleneck resources )t is run locally on a resource in a specified hori!on,
which means that dependencies with other resources are ignored *eveling capacity for the entire supply chain would, in
effect, be the same as performing a new planning run and is not within the scope of this function
1ou can run capacity leveling in both interactive Supply Network Planning and in the background )nteractive planning has
the advantage that you can display the resource load directly before and after leveling )f you run capacity leveling in the
background, you can select several resources for leveling (which can then be processed in se"uence) 1ou can also use a
selection profile 2unning capacity leveling in the background is especially suited to large data volumes and comple& models
A detailed log is displayed whether you run capacity leveling in interactive planning or in the background
Prere*uisites
1ou have run the SNP heuristic before capacity leveling Although it is possible to run capacity leveling after an SNP
optimi!ation run or -apable%to%.atch (-#.) run, in most cases it is not advisable to do so
)n addition, the same prere"uisites apply for running capacity leveling as for heuristic%based planning in general 6or more
information, see +unning the .euristic in the Backgroun#
Features
Supported $esource #ategories and Order Types
#apacity le%eling supports the following resource categoriesC
)t does not support storage or handling resources
#apacity le%eling supports all the resource types supported +y SNP in general. It supports the following
resource types in particular8
+ucket resource
)t does not support any other resource types
#apacity le%eling only takes into account SNP planned orders and SNP stock transfers. Deployment stock
transfersI T! s"#pmentsI and Production Planning and Detailed Planning orders &PP!DS orders' are not le%eledA
howe%erI the system does take into account the resource load caused +y these orders.
-apacity leveling does not take dependent demands into account Since leveling is only performed locally on a resource, it
can lead to other resources being overloaded, additional on%hand stocks being created, or shortfall "uantities being
generated
6or more information about which master data the system considers, such as lot si!es and rounding values, see
Consi#eration of "ot Si6es an# Other Master ,ata
#apacity (e%eling Profile
1ou can control capacity leveling using various parameters 1ou define these parameters in a profile that you specify when
running capacity leveling in interactive planning or in the background 5owever, you can also specify the parameters
manually or overwrite individual profile parameters before each capacity leveling run 1ou define the capacity leveling profile
in -ustomi!ing for SNP under Profiles @ (efine SNP -apacity *eveling Profiles or in the SAP 0asy Access screen under
Supply Network Planning @ 0nvironment @ -urrent Settings @ Profiles @ (efine SNP -apacity *eveling Profiles
1ou use the profile to define the following specific parameters8
#he capacity leveling method (heuristic, optimi!er, or +Ad))
#he scheduling direction (forward, backward, or combined)
Order prioriti!ation (that is, which orders you want capacity leveling to process first)
Page 143 of 251
5andling of fi&ed orders and order fi&ing during capacity leveling
#he ma&imum resource utili!ation
#he ma&imum runtime for capacity leveling
6or more information, see Capacity "eveling Profile
#onsideration of Alternati%e $esources
1ou can specify that capacity leveling also considers alternative resources #his means that the system considers production
process models (PP.s) or production data structures (P(S) that produce the same location product with alternative
resources
6or more information, see Consi#eration of Alternative +esources
(og and Alerts
#he system generates a detailed log for capacity leveling that is displayed automatically after the planning run both in
interactive planning and when e&ecuted in the background )t includes the following information8
Auantities in each period before and after capacity leveling
2esource utili!ation before and after capacity leveling
Surplus or shortage in the supply of output products
0rror and warning messages (that e&cessively large lot si!es will cause leveling problems, for instance)
Parameters selected by the user
)f you run capacity leveling in the background, you can hide the "uantities in each period and the resource capacity load in
the log #his helps you improve performance and reduce data volume 1ou can also specify for how long you want the log to
be saved and display logs from previous capacity leveling runs
-apacity leveling does not generate alerts directly 5owever, you can run a background 3ob for a macro to generate alerts
(for e&ample, the SNP standard macro for database ((+) alerts) 1ou can then view these alerts in the Alert .onitor 6or
more information, see the following (emand Planning documentation under (emand Planning Process @ -reation of the
(emand 6orecast @ Macro -&ecution ith Mass Processing (see also the subordinate topics)
Acti%ities
#apacity (e%eling in Interacti%e Supply Network Planning
1. On the SAP 0asy Access screen, choose Advanced Planning and Optimi!ation Supply Network Planning @
Planning @ )nteractive Supply Network Planning and go to the capacity view (-apacity -heck data view)
2. Select a resource
3. )f the resource is overloaded, choose -apacity *eveling
1ou can choose the planning hori!on in the planning table by selecting one or more periods #o select several periods,
select the first and last period of the hori!on (by choosing the left%hand mouse button and the control key) 1ou can also
choose individual products for capacity leveling by drilling down for products and selecting the products you re"uire
-apacities are then only leveled for the selected products within the chosen hori!on
4. A dialog bo& appears where you can choose a capacity leveling profile or manually specify the parameters
5. 1ou run capacity leveling and, if re"uired, view the log
6. 1ou display the new load situation in the capacity view
#apacity (e%eling in the )ackground
On the SAP 0asy Access screen, choose Advanced Planning and Optimi!ation Supply Network Planning @ Planning @
Supply Network Planning in the +ackground @ -apacity *eveling
1. 1ou select one or more resources for capacity leveling #o do this, you can also specify a selection profile that you
previously saved in interactive planning
2. 1ou select a capacity leveling profile or manually specify the parameters
3. 1ou run capacity leveling in the background and, if re"uired, view the log
4. 1ou display the new load situation in the capacity view of interactive Supply Network Planning
See alsoC
.euristic%Base# Planning
+unning the .euristic in the Backgroun#
0nteractive Planning ,esktop
Page 144 of 251
#onsideration of (ot SiGes and Other aster Data
Capacity leveling that you e&ecute after an SNP heuristic run considers E like the heuristic run % the master data created for it
5owever, there are some special features, which are e&plained below
Features
-apacity leveling takes into account lot si!e data that is defined in the master data, that is, it takes into account fi&ed lot
si!es, ma&imum lot si!es, and minimum lot si!es #he system does not take period lot si!es or lot si!es from production
process models (PP.s) or production data structures (P(S) into account
#he capacity leveling method that you choose governs the way in which the system takes into account lot si!es )f you
choose heuristic%based capacity leveling, the system uses the same rules as for the SNP heuristic when taking lot si!es
into account$ if you choose optimi!ation%based capacity leveling, the system uses the same rules as for the SNP
optimi!er
-apacity leveling takes into account the rounding value defined in the location product master #he system does not
consider the SNP rounding profile
-apacity leveling does not take into account the target daysO supply defined in the location product master
-apacity leveling (like SNP in general) does not support local time !ones for transportation resources (which means you
can only use the /T# time !one)
-apacity leveling ignores the minimum available capacity of a resource
#he following details are specific to optimi!ation%based capacity leveling8
#he optimi!er does not support transportation lanes that have different source locations but the same destination
location
#he optimi!er does not support cyclical transportation lanes
PP. or P(S se"uences, where the output products of one PP. or P(S are also used as the input products of
another and only the last PP. or P(S of this se"uence is run (with procurement indicator P), are not valid if the
resource that is to be leveled is being used in at least two of the PP.s or P(S involved
PP.s or P(S, in which the output product is completed in an activity other than the last activity, are not valid (this
applies to SNP optimi!ation in general)
#apacity (e%eling Profile
Profile, with which you can specify parameters for controlling capacity leveling in Supply Network Planning
(SNP)Parameters include scheduling direction, leveling method, and consideration of priorities 1ou can enter the profile
when you run capacity leveling in the background and in interactive planning
Structure
#apacity (e%eling ethod
1ou can choose one of the following three leveling methods8
5euristic8 #he heuristic processes the individual orders on a period basis #hat means, when a resource is overloaded,
the system moves order "uantities into subse"uent or previous periods depending on the direction of scheduling
(forward or backward) until the desired ma&imum load for the resource is reached #he total order "uantities in the
planning hori!on are not changed )n contrast to the optimi!er, the heuristic does not always find optimal resource
utili!ation results
Optimi!er8 #he optimi!er considers the "uantities per period$ that is, not the individual orders At the start of processing,
it deletes all e&isting orders that are not fi&ed (based on the setting) and then creates new orders As with the heuristic,
the total order "uantities in the planning hori!on are not changed 1ou can achieve a more even utili!ation of resources
than you can using the heuristic
Optimi!ation%based capacity leveling uses the SNP optimi!er to level resources 5owever, in contrast to the SNP
optimi!er, the constraints and costs taken into account are defined automatically and cannot be influenced by the user
#he costs are only used to control capacity leveling #hey have no business significance
+Ad)8 #he +usiness Add%)n 4SAPAPO4SNP?-AP provides an interface that you can use to connect your own method to
capacity leveling 1ou can choose it here once you have activated the +Ad)
6or more information, see -omparison of the -apacity *eveling .ethods and 5euristic%+ased -apacity *eveling8 0&amples
Scheduling Direction
1ou can define the direction in which the system e&ecutes capacity leveling$ that is, the direction in which the system moves
order "uantities from the order availability date when a resource is overloaded
Page 145 of 251
#he "uantities are moved within the planning hori!on 6or the planning hori!on, the system uses either the planning buckets
profile defined in the planning book or the planning buckets profile you specified in the capacity leveling profile 1ou can also
define the planning hori!on in interactive Supply Network Planning by selecting the start and end time period or by entering a
VfromO and VtoO date in the function for running capacity leveling in the background
#he options available are8
6orward scheduling8 #he order "uantities are moved from the availability date into the future
+ackward scheduling8 #he order "uantities are moved from the availability date into the past (until todayKs date at the
latest, minus the defined hori!ons)
-ombined forward and backward scheduling8 #he order "uantities are moved both into the future and the past
PrioritiGing Orders
1ou can specify which orders are to be considered first during heuristic%based capacity leveling for a resource, meaning
which orders will be the first to be moved to a different period 6or instance, during forward scheduling, the orders are moved
to a later period first and during backward scheduling, they are moved to an earlier period
#he options available are8
No priority8 'ith this option, capacity leveling does not take into account any product or order priorities 'e recommend
that you use this setting if you want to have optimal resource utili!ation Specifying a priority can have a negative effect
on the capacity leveling results for optimal resource utili!ation
Order si!e8 'ith this option, capacity leveling takes into account orders according to their si!e 6or e&ample, you can
specify that during backward scheduling, large orders are moved to the earlier periods first
Product priority8 'ith this option, capacity leveling takes into account the orders according to the priority specified for
products in the location product master 6or e&ample, you can specify that, during forward scheduling, unimportant
products are first moved to later periods
1ou can also choose whether you want the priorities defined to be sorted in ascending or descending order
Ascending8 'hen you choose the Product Priority option, the capacity leveling function moves orders for highest priority
products first (priority ;), then orders for second highest priority products (priority <), and so on 'hen you choose the
Order Si!e option, capacity leveling moves the small orders first
(escending8 'hen you choose the Product Priority option, the capacity leveling function moves orders for lowest priority
products first (priority <DD or :), then orders for second highest priority products (priority <D>), and so on 'hen you
choose the Order Si!e option, capacity leveling moves the large orders first
1ou define the product priority on the SNP < tab page of the location product master Optimi!ation%based capacity leveling
does not consider priorities
Handling of fi1ed orders and order fi1ing during capacity le%eling
1ou can specify that the system also levels fi&ed orders #his means that the system also moves, changes, and deletes
orders that were fi&ed in earlier planning runs Note that this can cause orders that were fi&ed for subse"uent planning runs
to be lost since, for e&ample, optimi!ation%based capacity leveling first deletes all e&isting orders and then creates new ones
1ou can also specify that all orders for subse"uent planning runs are to be fi&ed during capacity leveling$ that is, they can no
longer be edited after leveling
a1imum (oad and a1imum $untime
1ou can specify the ma&imum load for a resource (as a percentage) that you want the system to take into account during
capacity leveling #his value does not represent an absolute upper bound Since the total "uantity of all the orders that e&ist
in the planning hori!on has to remain the same, resource overloads might occur if the re"uired capacity is not available
1ou can also define the ma&imum runtime (in minutes) for capacity leveling Once this runtime has been e&ceeded, the
system terminates planning #he following details apply to the #euristic and optimi$er capacity leveling methods8
5euristic8 #he heuristic processes the orders on a period basis Once the runtime has been e&ceeded, the system
completely terminates processing for the current period Solutions e&ist for the periods that had already been processed
Optimi!er8 Since the optimi!er attempts to determine an optimal solution, it might already have found a solution for the
entire planning hori!on$ however, this solution might not represent the best possible solution
6or the planning results found before termination, refer to the log
#onsideration of Alternati%e $esources
'ith capacity leveling in Supply Network Planning (SNP) you can not only level the resource load by moving orders to
preceding or subse"uent periods, but also transfer the orders to alternative resources #he system moves the orders to
Page 146 of 251
production process models (PP.s) or production data structures (P(S) that have been defined for the same location product
but use different resources
#he system uses only the free capacity of the alternative resources and does not generate any new capacity overloads )t
does not e&ecute capacity leveling for the alternative resources and does not change any orders that already e&ist for these
resources
#he se"uence in which the system uses the PP.s or P(S with alternative resources is based on the procurement priority of
the PP.s or P(S
#he system only considers alternative production resources, that is, it does not consider transportation resources
Features
All three capacity leveling $etho#s, that is, the heuristic, optimi!ation, and the +Ad)%based methods, consider alternative
resources #he heuristic% and optimi!ation%based methods have the following special features8
Heuristic.)ased #apacity (e%eling
)f the system finds that a resource to be leveled is overloaded, it first partially or completely moves the orders causing
the capacity overload to alternative PP.s or P(S in the same period )f the free capacity of the alternative resources is
used up and yet there is still a capacity overload, the system moves the orders for the remaining "uantities back to the
original PP.4P(S #hen the system moves the orders to a previous or later period, depending on the selected
scheduling )f there is another capacity overload, the system again determines alternative PP.s4P(S in this period
#he system moves remaining "uantities that still e&ist after processing all periods of the planning hori!on to the first or
last period of the planning hori!on #here they cause a capacity overload of the original resource 'hether the
remaining "uantities are moved to the first or to the last period depends on the scheduling direction selected
OptimiGation.)ased #apacity (e%eling
#he system considers the alternative resources according to the procurement priority of the PP.s or P(S #he system
automatically converts this priority into costs, so that PP.s or P(S with higher priorities are considered first #he costs
of the original resource are defined by the system as lower than the costs of the alternative resources, so that this
resource always has the highest priority for the optimi!er and so that the system uses it completely first
#onsideration of a $esource Hierarchy
)f you use a resource hierarchy, you can set the level of this hierarchy at which the system considers alternative resources
6or e&ample, you can specify that the system considers only header resources or only subresources as follows8
Sublevel8 1ou e&ecute capacity leveling for subresources, for e&ample, and specify a header resource during the
selection of alternative resources #he system then only selects the subresources of this header resource as alternative
resources #his allows you to restrict the consideration of alternative resources to a specific group of resources
5eader level8 1ou e&ecute capacity leveling for header resources, for e&ample, and specify subresources during the
selection of alternative resources #he system then only selects the header resources belonging to the subresources as
alternative resources
Note that the system does not consider any subresources of the resource to be leveled as alternative resources )f you
define a header resource and its subresource as alternative resources at the same time, the system does not consider the
header resource as an alternative resource
1ou must have created the resource hierarchy based on a hierarchy structure that you have assigned to your planning area
#here is already a standard resource hierarchy structure assigned to the standard planning area 9ASNP:< 1ou must also
have assigned the hierarchy to your supply chain model 6or more information, see the SAP APO master data
documentation under .ierarchy
Acti%ities
)f you want capacity leveling to consider alternative resources, enter these resources on the screen for running capacity
leveling in the background or in the dialog bo& for interactively running capacity leveling 6irst, set the Alternative 2esources
indicator #hen you will see the following options8
All 2elevant 2esources8 #he system automatically determines the resources that can be used
2esource8 0nter specific resources
Selection Profile8 0nter a selection profile you have created for resources
*evel of Source (etermination8 Select a source determination level if you want the system to consider a resource
hierarchy
)f you select more than one resource for capacity leveling, the system considers the alternative resources for each resource
to be leveled #he system automatically filters out the resources that are not related to the resource the system is leveling at
the time 1ou can therefore select a resource as a resource to be leveled and as an alternative resource
Note that the alternative PP.s or P(S cannot use the resources of the original PP.s or P(S )n this case, there is the
danger that the system could generate cyclical capacity overloads of the original or alternative resources
Page 147 of 251
#he alternative resources you have entered are displayed with the other parameters in the application log of capacity
leveling )n addition, all the orders created by the system are listed for the alternative resources #he utili!ation of the
alternative resources is displayed 3ust like that of the original resources
#omparison of the #apacity (e%eling ethods
#he following three main capacity methods are available in Supply Network Planning (SNP)8
5euristic%based capacity leveling
Optimi!ation%based capacity leveling
1our own method connected using the +usiness Add%)n 4SAPAPO4SNP?-AP
'hich method you should choose depends on the individual circumstances 5owever, the main features of the two methods
provided by SAP are described below to assist you in deciding which to use
Heuristic.)ased #apacity (e%eling
Features
5euristic%based capacity leveling starts from the start or end of the planning hori!on depending on the scheduling direction
you chose (forward or backward), and compares the resource capacity load in each period with the re"uired load that you
defined )f the system detects a resource overload, it first selects all the activities or orders that are causing the overload in
the period concerned #he system then sorts these orders according to the priority you specified and, in turn, moves orders
or partial order "uantities into later or earlier periods until the ma&imum resource capacity level has been achieved (uring
forward scheduling, the system moves the orders into the future so that the first activity that uses the resource to be leveled
starts after the period with the overload (uring backward scheduling, the system moves the orders into the past so that the
final activity that uses the resource to be leveled is completed before the start of the period with the overload
'hen moving orders, the system takes into account the lot si!e values and rounding values defined in master data (for
information about constraints, see Consi#eration of "ot Si6es an# Other Master ,ata)
Performance
#he runtime of heuristic%based capacity leveling depends on the number of orders to be processed and the number of
periods 2untime is influenced by the following factors in particular8
Number of products at the resource
2atio of the lot si!e to the total "uantity
0&tent of the resource overload
-hoice of periods (day, week, month)
*ength of the planning hori!on
OptimiGation.)ased #apacity (e%eling
Features
Optimi!ation%based capacity leveling uses the SNP optimi!er to clear resource overloads #he system actions are as follows8
1. #he optimi!er first determines all the production process models (PP.s) or production data structures (P(S) and
transportation lanes that use the resource to be leveled )t then determines all the location products that belong to this
master data plus the relevant master data and transaction data for these products
2. #he optimi!er generates a special optimi!ation problem for capacity leveling based on the data determined and the
settings made by the user (scheduling direction, for instance) #he optimi!er automatically sets the costs that are taken
into account for this problem (costs for storage, delay, or non%delivery for instance) )t ignores any costs defined by the
user #he costs are only used to control capacity leveling #hey have no business significance
3. #he optimi!er solves the optimi!ation problem generated #o do this, it first deletes all orders and stock transfers for the
resource to be leveled and then completely replans it )f alternative PP.s, P(S, or transportation lanes are available, it
bases its selection on procurement priority, if possible
#he optimi!er makes sure that the resource to be leveled is not overloaded and takes care not to move the planned
orders and stock transfers too far beyond or prior to the original receipt due dates )t prefers to create receipts that are
too early (resulting in the creation of stock on hand) rather than too late (resulting in the creation of shortfall "uantities), if
possible
4. #he optimi!er creates new orders and stock transfers )t then also creates the orders and stock transfers that it was
initially unable to schedule due to the limited resource capacity )n backward scheduling, it creates the orders and stock
transfers for the original receipt due date$ in forward scheduling, it creates them in the last possible period of the
planning hori!on
Page 148 of 251
Performance
#he following factors have a significant influence on the runtime of optimi!ation%based capacity leveling8
#he length of the planning hori!on and the number of periods within it
#he number of alternative transportation lanes and PP.s or P(S
#he number of products for which there are planned orders or stock transfers
#he following factors do not have a significant influence on the runtime of optimi!ation%based capacity leveling8
#he number of planned orders or stock transfers for a product within a period
*ot si!es
0&tent of the resource overload
#omparison of the ethods
#he features of the two methods are compared in the following table8
Heuristic OptimiGer
Type of processing
Order.+ased processingC
Only orders that are moved are changed
(live-ache, 24=)
#his is beneficial if there are many
orders but only a few that are
overloading the resource
Period.+ased and *uantity.+ased
processingC
All e&isting orders are deleted and
recreated after capacity leveling
$esource capacity le%el
Not always optimal in configurations such as
that described in 5euristic%+ased -apacity
*eveling8 0&amples
Almost always optimal
#hanges to plan 6ew -ompletely new plan
Priority rule o+ser%ance
Order si!e
Product priority
(sorting in ascending or descending order)
No
O%erloads mo%ed during
+ackward scheduling
Always
Only if there is sufficient capacity free in the
target period
(ocation of receipt and
issue
#he receipt has to be within the planning
hori!on and outside of the SNP production
hori!on or stock transfer hori!on
#he receipt and issue have to be within the
planning hori!on and outside of the SNP
production or stock transfer hori!on
)ucket offset )s ignored (see period factor)
#he bucket offset for PP.s or P(S is
always ;
#he bucket offset for transportation lanes
is always ;
Period factor
#he period factor of the PP.4P(S or
transportation lane is taken into account (if
not defined, the period factor of the location
product is taken into account)
)s ignored (see bucket offset)
Heuristic.)ased #apacity (e%elingC 01amples
#his topic includes a few e&amples of heuristic%based capacity leveling #he following parameters have been chosen for the
e&amples8
6orward scheduling
2esource capacity level8 ;::a
*eveling method8 5euristic
No consideration of priorities
01ample 5C (e%eling the #apacity of a Production $esource
Step 5
Page 149 of 251
An order for <> pieces of product P2O(; is loading resource 20S; #he product is available on day = #he production
process model (PP.) activities are loading the resource on day ;, <, and = #he PP. has the following activities8
Activity ;8 (uration P ; day, resource P 20S;, variable bucket consumption P ;h
Activity <8 (uration P ; day, resource P 20S;, variable bucket consumption P <h
Activity =8 (uration P ; day, resource P 20S;, variable bucket consumption P <h, Output product P P2O(;,
consumption P ; P-
Step 7
5euristic%based capacity leveling reduced the resource load on day < to ;::a by reducing the "uantity of the original order
by D:a and creating a new order for the remaining D:a of the order "uantity #herefore, the system moved D:a of the
original order into the future so its activities were outside of the period concerned (day <)
Step 8
#o level the resource load on day =, the system moved the new order from day D to day F
01ample 7C (e%eling the #apacity of a Transportation $esource
Step 5
An order with a "uantity of =: pieces is to be transferred to a different location #he time of receipt at the destination location
is day = at ;<8::8:: h #he shipment duration is <> h #herefore, the activity loads the resource from day <, ;<8::8:: h until
day =, ;<8::8:: h
#he following data was defined for the transportation lane8
2esource8 #20S;
Shipment duration8 <> h
2esource consumption ; P- P ;: #O
Step 7
Page 150 of 251
5euristic%based capacity leveling leveled the resource load on day < by moving ;: pieces to day >
Step 8
#o level the resource load on day =, the system moved another ;: pieces to day D
Procurement Scheduling Agreements in Heuristic.)ased SNP
Scheduling agreements are considered when procuring products as part of heuristic%based planning within Supply Network
Planning Scheduling agreements can help you to improve collaboration with your vendors or suppliers Since they are better
informed of demand times and demand "uantities, you can reduce processing time 1ou can also include vendor%confirmed
"uantities within your planning as ma&imum vendor capacities
#he SNP heuristic takes into account procurement scheduling agreements that were created in an O*#P system and
transferred to the SAP APO system through an appropriate interface (24= system8 APO -ore )nterface, -)6), as possible
sources of supply
#he SNP heuristic does not take into account scheduling agreements for the subcontracting form of procurement -ontracts
are not included in SNP planning either (whereas purchasing info records are taken into account) )n addition to this,
scheduling agreements in SNP are only included in active model versions
Prere*uisites
1ou have configured the integration process for all the scheduling agreements and purchasing info records that are to
be transferred to SAP APO #his means that you have entered all the data that is to be transferred in the -)6 integration
model for an SAP 24= system #his master data is transferred to the SAP APO system in an initial data transfer Any
changes that are made to this master data in the O*#P system after this point are saved for the ne&t change transfer
6or more information, see Cenerating )ntegration .odels
1ou have made the relevant settings for APO scheduling agreements 6or more information, see Prere"uisites for the
APO Scheduling Agreement
1ou have released demands to Supply Network Planning in the form of a demand plan from (emand Planning (see
2elease of the (emand Plan to SNP)
1ou have made the general settings for running the SNP heuristic 6or more information, see +unning the .euristic in the
Backgroun#
Process Flow
Process Options
#here are four different scheduling agreement%processing options to choose from 1ou configure these processes for APO
scheduling agreements in the e&ternal procurement relationship (see below)8
Process with 0&pected -onfirmations,
Process 'ithout -onfirmations,
Process with -onfirmations in 0&ceptional -ases
Process 'ithout 2eleases
#he e&ample process described below is the Process with 0&pected -onfirmations #he below list also applies, in the main,
to the other options, Process 'ithout -onfirmations or Process with -onfirmations in 0&ceptional -ases, e&cept that
scheduling agreement release creation in SAP APO automatically generates schedule lines in the O*#P system
Page 151 of 251
#he Process 'ithout 2eleases is a simplified version of the process described below )t is particularly suited to scenarios
whereby the supplier uses collaborative supply planning to make confirmations over the )nternet )t does not do step >$
that is, creation of scheduling agreement releases 'ith this process, the supplier sees only the schedule lines on the
)nternet and confirms these directly Alternatively, the manufacturer can enter the confirmations in interactive Supply Network
Planning
#he following prere"uisites apply to this simplified process8
)f you are using Clobal Available%#o%Promise (Clobal A#P), you must set in -ustomi!ing for this application component
that confirmations are A#P%relevant (choose Product Availability -heck .aintain -heck -ontrol)
1ou should choose a confirmation profile with tolerance check, in order to be informed by alert about serious deviations
between the re"uired and confirmed "uantities (in -ustomi!ing for supply chain planning, choose8 -ollaborative
Procurement c Procurement Scheduling Agreement -onfirmation 2eceipt .aintain -onfirmation Profiles for
-onfirmation 2eceipt)
01ample Process &Process with 01pected #onfirmations'
An e&ample of a scheduling agreement process from Supply Network Planning is given below #he process described is the
Process with 0&pected -onfirmations #his process refers to heuristic%based SNP planning, taking into account APO
sche#uling agree$ents
#he SNP heuristic also takes into account O*#P scheduling agreements )n contrast to the process described, when
planning O*#P scheduling agreements, the SNP heuristic generates SNP stock transfers that reference O*#P scheduling
agreements, which are then transferred automatically to the O*#P system through an interface Scheduling agreement
schedule lines and releases are generated in the O*#P system 5owever, it is possible to display these schedule lines and
releases in interactive Supply Network Planning
SNP Scheduling Agreement Processing 01ample
1. #he SAP APO system generates e&ternal procurement relationships
'hen you transfer scheduling agreements and purchasing info records from an O*#P system to SAP APO through an
interface, this data is generated in the SAP APO system as e&ternal procurement relationships 5ere, an e&ternal
procurement relationship is created for each individual scheduling agreement item An e&ternal procurement relationship
is product%specific and assigned to a transportation lane #ransportation lanes are generated in SAP APO automatically
when you transfer data from the O*#P system #his means that the e&ternal procurement relationship contains the
contractual details of the relationship between a source location (supplier or supplying plant) and destination location
(plant) 1ou still have to assign a means of transport to the transportation lane
6or more information, see 0&ternal Procurement 2elationship
2. )n Supply Network Planning, you e&ecute heuristic%base# planning at location product level #he SNP heuristic takes into
account the scheduling agreements transferred from the O*#P system as possible sources of supply #o do this, the
system applies the normal source #eter$ination rules from the SNP heuristic, which means that it takes into account
the scheduling agreements according to either procurement priority or "uota arrangement, depending on specifications
made
Page 152 of 251

1ou can first run the heuristic without capacities (infinitely), meaning that supplier capacity is not considered (to do this,
choose No capacity on the initial screen for Supply Network Planning in the background) )f you do this, you may want to
include the supplier capacity in a later planning run after receiving confirmations for your scheduling agreement releases
from the supplier (see step D) 5owever, even at this early stage, you also have the option of including the supplier
capacity in your schedule, if the supplier has already informed you of these capacities (through collaborative supply
planning, for e&ample) 1our supplier can enter the "uantities he or she is capable of delivering in the -onfirmation key
figure in the 9ASAS planning book (choose SAP 0asy Access @ Supply Network Planning @ Planning @ -ollaborative
Supply Planning) )n the -apacity key figure, the supplier can also specify his or her entire capacity, which alternatively
can be derived from the confirmation "uantities (using macros, for instance) #he supplier can also specify the
capacity of transportation lanes for a scheduling agreement item, in order to restrict the capacity of means of transport
)f you have already received the appropriate capacity data from the supplier, specify the corresponding planning book
and capacity key figures on the Supply Network Planning initial screen 6or performance reasons, you should choose a
planning book that only includes key figures that are actually re"uired, if possible 1ou also choose whether you want to
consider during planning the capacity specified for the transportation lanes of a scheduling agreement item, or the
capacity specified for the entire scheduling agreement item
3. (uring the planning run, the SNP heuristic generates schedule lines for the scheduling agreements being considered as
supply sources A schedule line is a partial "uantity of the total scheduling agreement item "uantity with associated
delivery dates Schedule lines, like the entire planning results, can be displayed in interactive planning (planning book
9ASA, choose the APO 0asy Access menu @ Supply Network Planning @ Planning @ Scheduling Agreements
(Procurement) @ )nteractive Scheduling Agreements)
4. 1ou manually (in the product view) or automatically (using the release creation profile) create scheduling agreement
releases that you use to notify the supplier that he or she should deliver the products on the dates listed in the schedule
lines 6or more information, see Scheduling Agreement 2elease -reation
5. #he supplier notifies you of his or her capacities, using collaborative supply planning for instance (see step <) 1our
supplier can display the schedule lines and scheduling agreement releases in the 9ASAS planning book and can specify
the "uantities he or she is capable of delivering in the -onfirmation key figure )n the -apacity key figure, the supplier
can also specify his or her entire capacity, which alternatively can be derived from the confirmation "uantities (using
macros, for instance) )n interactive planning you also have the option of entering capacities that your supplier notified
you about in an email (planning book 9ASA or 9ASAS)
Page 153 of 251
#he system automatically transfers the confirmations to the O*#P system as scheduling agreement schedule lines
6. )f the confirmation "uantity is less than the release "uantity, you can run SNP planning once more in the background to
plan the demand "uantities still to be fulfilled 'ith this planning, you can consider the capacity confirmed by the supplier
(see step D) as the ma&imum supplier capacity Also enter the corresponding planning book and key figures, as
described in step <
01ternal Procurement $elationship
0&ternal procurement relationships belong to the $aster #ata in the Advanced Planner and Optimi!er (APO) #hey represent
purchasing info recor#s, contracts and sche#uling agree$ents from your O"!P syste$ (for e&ample, an SAP 24= system) in
your SAP APO system and make available all the data necessary for the planning of product procurement
0&ternal procurement relationships enable you to do the following8
Cenerate delivery schedule lines for a scheduling agreement item (APO scheduling agreement) directly within the SAP
APO system
Cenerate purchase re"uisitions with reference to a purchasing info record, a contract, or a scheduling agreement item
(O"!P sche#uling agree$ent) in your O*#P system from within the SAP APO system
#he e&ternal procurement relationship links the transportation lane with information from your O*#P system8
#he transportation lane represents the business relationship between a source location (for e&ample, a vendor) and a
destination location (for e&ample, a plant) #his is created automatically in SAP APO when you have transferred data from
the SAP 24= system
#he e1ternal procurement relationship supplements the information about the transportation lane by creating a link to a
specific contract that e&ists in your O*#P system for the source and destination locations
0&ternal procurement relationships can e&ist for the following forms of procurement8
Standard
Subcontracting
Consign$ent
Stock transfer for stock transport scheduling agreements
#he product Steel bolt :; can be procured by your 5ouston plant from the vendor Armstrong -o #he product is to be
procured via a scheduling agreement that already e&ists in your 24= system
)n your APO system, the link between the vendor Armstrong -o (source location) and your 5ouston plant (destination
location) for the product Steel bolt :; is represented by a transportation lane 6urthermore, an e&ternal procurement
relationship e&ists, creating a link between this transportation lane and the scheduling agreement in your SAP 24= system
Page 154 of 251
/se
/p to 2elease <:+, the source determination process in SAP APO system only proposed vendors for e&ternal procurement
As of 2elease =:A, the system can also propose purchasing info records and contract or scheduling agreement items in the
source determination process if you are working with e&ternal procurement relationships in SAP APO
1ou create an e&ternal procurement order in the product view and the system shows you all the possible sources of supply
)f you choose a contract item at this point, a purchase re"uisition referencing this item is created in your O*#P system
Structure
An e&ternal procurement relationship contains the following data8
=eneral data
#he Ceneral data includes information on the purchasing info record, contract, or scheduling agreement (for e&ample,
the procurement category, the logical system, the document number, the vendor and so on)
Settings
/nder Settings, you can see the planned delivery time of a material and whether the e&ternal procurement relationship
is active or inactive
Planned deli%ery time
#he planned delivery time is copied from the 24= outline agreement 5owever, you can change it
)n the source determination process, the system uses the planned delivery time to calculate the scheduling of
e&ternal procurement orders )f there is no entry in the e&ternal procurement relationship, or the entry is !ero, the
system uses the planned delivery time from the product master
)f you want the planned delivery time of !ero from the e&ternal procurement relationship to be taken into account in
source determination, you must also set the #ake )nto Account indicator
Planned delivery times greater than !ero are generally taken into account, even if the #ake )nto Account indicator
has not been set
Deacti%ation of e1ternal procurement relationship
An e&ternal procurement relationship is usually deactivated if the purchasing info record, contract, or scheduling
agreement is deleted in the O*#P system )f the e&ternal procurement relationship is inactive, it is no longer taken
into account in the source determination process and no new transportation lanes can be created for it
Data on the transportation lane
On the Assigned #ransportation *anes tab page, you can display data on the transportation lanes and maintain the
priority 1ou can also block and unblock the assigned transportation lanes on this tab page
Scheduling agreement data (only in the case of APO scheduling agreements)
1ou can display, and in some cases maintain, the following data on the Scheduling Agreement tab page8
Settings
.ovement data
(elivery data
Partners (only in the case of APO scheduling agreements)
On the Partners tab page, you can specify8
#he address (for e&ample, postal address, e%mail address) to which scheduling agreement releases are to be sent
#he medium (for e&ample, fa&, e%mail) via which scheduling agreement releases are to be output
'hich partner role your vendor taken on (here8 source location)
)f you have not maintained an address here, the SA release will be sent to the address maintained in the master data for the
source location #he medium and the partner role are then determined from the default values maintained in -ustomi!ing for
Supply -hain Planning under -ollaborative Procurement Set .essage #riggers
1ou can also call up additional information by clicking one of the following buttons8
#osts
#his gives you more precise information on the product costs (for e&ample, scale prices and their validity periods)
2elease -reation Profile (only in the case of APO scheduling agreements)
#his takes you to -ustomi!ing, where you can display the release creation profile
SA releases (only in the case of APO scheduling agreements)
Page 155 of 251
5ere you can display the scheduling agreement releases that have already been generated for a scheduling agreement
item
PO history (only in the case of APO scheduling agreements)
5ere you can view all the transactions and events that have been recorded for an item of a scheduling agreement (for
e&ample, receipts of goods and invoices)
Display last deli%eries (only in the case of APO scheduling agreements)
5ere you can display an overview of the last inbound deliveries against a scheduling agreement item #he inbound
delivery data is transferred from the O*#P system to the APO system
Accessi+le Functions
1ou can also branch to the following functions (0nvironment SQ)8
(ocation
Product
Transportation (ane
Juota arrangement
Tolerance profile, checking procedures und confirmation profile for the receipt of confirmations (only in the case of
APO scheduling agreements)
)n -ustomi!ing, you can display the profiles and procedures for the receipt of confirmations
0nter confirmations (only in the case of APO scheduling agreements)
1ou go to the function for entering confirmations
Integration
#he e&ternal procurement relationship is directly linked to the relevant transportation lane and provides additional information
about it 6rom the e&ternal procurement relationship, you can also branch directly to the transportation lane in order to
maintain relevant data
)f your O*#P system is an SAP 24= system, you can transfer purchasing info records, contracts, and scheduling agreements
(and changes to them) to your SAP APO system via the -)6
Processing 01ternal Procurement $elationships
#he 0&ternal Procurement 2elationship function enables you to check (and, if necessary, ad3ust) data relating to your
e&ternal procurement relationships
0&ternal procurement relationships constitute master data in the Advanced Planner and Optimi!er (APO) #hey provide the
SAP APO system with data from purchasing info records, contracts, and scheduling agreements for the purpose of planning
materials procurement activities )n this way, you can not only reference a vendor from an e&ternal procurement order, you
can also directly reference a specific item in an e&isting contract
'hen you transfer purchasing info records, contracts, or scheduling agreements from your O"!P Syste$ to your SAP APO
system via the -ore )nterface (-)6), e&ternal procurement relationships and the associated transportation lanes are
automatically created in the SAP APO system for this data )n the process, a separate e&ternal procurement relationship is
created for each contract item or scheduling agreement item
Integration
#he e&ternal procurement relationship is directly linked to the relevant transportation lane and provides it with data from the
purchasing info record, contract, and scheduling agreement 6rom the e&ternal procurement relationship, you can also
branch directly to the transportation lane in order to maintain transportation lane data
)f your O*#P system is an SAP 24= system, you can transfer purchasing info records, contracts, and scheduling agreements
(and changes to them) to your SAP APO system via the -)6
Prere*uisites
+efore you can work with e&ternal procurement relationships in SAP APO, you must transfer the following data to it from your
O*#P system via the -)68
Plants
.aterial master records
Bendor master records
Purchasing info records
Scheduling agreements
Page 156 of 251
-ontracts
)n SAP APO, you can work with the forms of procurement Standard, Subcontracting, and Consign$ent 6or scheduling
agreements, you can also use the form of procurement Stock !ransfer
Transferring master data for the first time
1. -reate an integration model in your O*#P system, in which you specify which data is to be transferred to the SAP APO
system (transaction -)6$ )ntegration .odel c Cenerate c -reate)
2. #hen activate the integration model ()ntegration .odel c Activate)
Transferring changed master data
)f purchasing document or master data has changed, you can carry out a transfer of the changed data
#o do this, choose -hange #ransfer c .aster (ata in the transaction -)6 )ntegration .odel and select the Sources indicator
to transfer changes involving purchasing info records, contracts, and scheduling agreements
#he transfer of changes may result in data that you have changed in your SAP APO system being overwritten
)n your APO system, you have an e&ternal procurement relationship for item ;: of scheduling agreement no DD:::::::;
from your O*#P system )n the APO system, you change the planned delivery time for this e&ternal procurement relationship
from VD daysO to V= daysO
)n the O*#P system, the original planned delivery time is then changed from VD daysO to VF daysO #he changed planned
delivery time is now transferred from the O*#P system to the APO system #he planned delivery time, which was = days in
the SAP APO system, is overwritten by the planned delivery time, which was changed to VF daysO in the O*#P system
)n an 24= system, you can use contracts (-entrally Agreed -ontracts) and purchasing info records on a cross%plant basis
simply by not assigning any plants to them
)f you transfer such a centrally agreed contract or cross%plant purchasing info record to your APO system, an e&ternal
procurement relationship will be created for each plant of the relevant purchasing organi!ation that e&ists in your APO
system
Features
#he 0&ternal Procurement 2elationship function enables you to display and change e&ternal procurement relationships that
e&ist in the APO system and to restrict how they are used, by blocking the transportation lane, for e&ample
On the initial screen for this function you define which e&ternal procurement relationships are displayed 6or e&ample8 all
e&ternal procurement relationships for a destination location (for e&ample, plant :::;), all those for a source location (vendor
.eyer -orp), or all those with a certain e&ternal procurement category (`contract`)
#he e&ternal procurement relationships are displayed in an overview tree in the left%hand part of the screen, listed by e&ternal
procurement category (purchasing info record, contract, O*#P scheduling agreement, APO scheduling agreement) and the
logical system from which the data originates
)f you choose an e&ternal procurement relationship from the overview tree, the following data will be displayed in the right%
hand part of the screen8
=eneral information on the e&ternal procurement relationship (such as the source and target location, the product, and
the validity of the e&ternal procurement relationship)
Status of the e1ternal procurement relationship (active or inactive)
Associated transportation lanes
Scheduling agreement dataI for e&ample, the release creation profile (only in the case of APO scheduling agreements)
#hanging an 01ternal Procurement $elationship
Only the certain data in an e&ternal procurement relationship can be changed8
-hange planned delivery time
Activate, deactivate, and delete e&ternal procurement relationship
-hange transportation lane (0nvironment c #ransportation *ane c .aintain)
-reate new transportation lane (0nvironment c #ransportation *ane c -reate)
1ou can process a transportation lane in an e&ternal procurement relationship as follows8
-hange priority
+lock transportation lane
)f you block an e&ternal procurement relationship then it can no longer be selected in the source determination process
)f the e&ternal procurement relationship contains a reference to an APO scheduling agreement, you can also maintain the
following data8
Page 157 of 251
$elease creation profile
#he release creation profile for the scheduling agreement is not transferred from the O*#P system 1ou must create a
separate release creation profile in the APO system and assign it to the e&ternal procurement relationship 1ou define
the release creation profile in -ustomi!ing for Supply -hain Planning under -ollaborative Procurement c .aintain
2elease -reation Profile
#onfirmation profile
1ou define the confirmation profile in -ustomi!ing for Supply -hain Planning under -ollaborative Procurement c
.aintain 2elease -onfirmation Profiles
Process
5ere you can specify how confirmations are to be integrated in the scheduling agreement process
/pdate li%e#ache
'hen an e&ternal procurement relationship is created, the field /pdate live-ache is automatically filled with the value ;:
E At time of release creation
Scheduling agreement with forecast
1ou use this indicator to specify whether forecast4planning delivery schedules are to be generated in addition to
operative schedules )n the standard system, this indicator is not preset when an e&ternal procurement relationship is
created
)f you want to work principally with forecast4planning delivery schedules, you can specify that the indicator is
automatically preset when an e&ternal procurement relationship is created by using the +usiness Add%)n (+Ad))
4SAPAPO4P'+?#PS2-?)N /sing this +Ad), you can also influence other data of the e&ternal procurement relationship
or transportation lane
1ou can also specify in the release creation profile whether forecast4planning delivery schedules are to be generated in
addition to operative schedules 6or this reason, the settings in the release creation profile and the Scheduling
Agreement with 6orecast field must be harmoni!ed
Internet release
1ou can use this indicator to specify whether or not the scheduling agreement release is an 0nternet +elease and
whether it has to be acknowledged by the vendor
Address data
Address data is not transferred from the O*#P system )f you do not maintain any address data on the Partners tab
page, the address data of the source location is used
/se the button to maintain your own address data for an e&ternal procurement relationship
1ou can only influence other data by changing it in the O*#P system (for e&ample, a change to the scheduling agreement)
Deacti%ating an 01ternal Procurement $elationship
)f a purchasing info record, a contract, or a scheduling agreement is deleted in your O*#P system, the relevant e&ternal
procurement relationship is deactivated in the SAP APO system
#his procurement alternative can no longer be used in the source determination process #he log for the source
determination process draws your attention to the fact that the relevant procurement alternative has been deactivated
6urthermore, no new transportation lanes can be created for deactivated e&ternal procurement relationships
Deleting an 01ternal Procurement $elationship
)f you no longer need an e&ternal procurement relationship in the APO system, you can delete it
)n order for you to be able to do this, the e&ternal procurement relationship must have been deactivated 6urthermore, no
e&ternal procurement orders or "uota arrangements may e&ist in the SAP APO system for this e&ternal procurement
relationship
1ou can delete e&ternal procurement relationships as follows8
)n the e&ternal procurement relationship
(isplay the relevant e&ternal procurement relationship (.aster (ata Procurement .aster (ata Procurement
2elationships) and choose
/sing the report (elete Procurement 2elationships
-hoose .aster (ata Procurement .aster (ata (elete Procurement 2elationships and select the e&ternal
procurement relationships that you want to delete -hoose (elete All e&ternal procurement relationships marked
with are deleted
Page 158 of 251
ass aintenance
1ou can use mass maintenance to change data that can also be changed in master data maintenance
Procurement Scheduling Agreement &S#.APO.#P$.S#H'
Outline Agree$ent against which materials are procured at predefined points in time over a certain period
Structure
A scheduling agreement consists of a number of items, for each of which a certain form of procurement is defined #he
following forms of procurement e&ist8
Standard
-onsignment
Stock transfer
Subcontracting
Procurement scheduling agreements with account assignment can also be planned in SAP APO (See APO Sche#uling
Agree$ents ith Account Assign$ent3
)n the schedule lines, the total "uantity of the material specified in the scheduling agreement item can be split up into
different "uantities with delivery dates4times
1ou send scheduling agreement (SA) releases (specific types of delivery schedule) to the vendor, which inform the vendor of
the "uantities you want and when they should be delivered (See -reating Scheduling Agreement 2eleases and Outputting
Scheduling Agreement 2eleases)
)n the 2elease -reation Profile you can define the conditions under which releases are generated against a scheduling
agreement 1ou assign a release creation profile to a scheduling agreement item in the e&ternal procurement relationship
See also 2elease -reation Profile (APO Scheduling Agreement)
1ou can display the releases transmitted to a vendor at any time (See also Processing Sche#uling Agree$ent +eleases)
Scheduling agreements from the O"!P syste$ (which is usually an SAP 24= system) are represented in the SAP Advanced
Planner and Optimi!er (SAP APO) by _e&ternal procurement relationships`
#he O*#P system can be an SAP 24= system or another system #he following processes and functions relate to the use of
an SAP 24= system with an SAP APO system 6or this reason the following section refers to an SAP 24= system, rather than
an O*#P system
0&ternal procurement relationships belong to the Master ,ata in SAP APO #hey represent Purchasing 0nfo +ecor#s,
Contracts and Sche#uling Agree$ents from your SAP 24= system in your SAP APO system and make available all the data
necessary for material procurement planning (See also -&ternal Procure$ent +elationship)
)n SAP APO, a distinction is made between two forms of scheduling agreement8
O(TP Scheduling Agreement
#he delivery schedule lines for and releases against O*#P scheduling agreements are generated in the O*#P system
1ou specify this in the additional data for the scheduling agreement item by choosing the setting =enerate and output
SA release in $!8 for the 0&ternal Planning indicator
#he O*#P scheduling agreement in the SAP 24= system is usually a scheduling agreement with the document type
(PA, for which the 2elease (ocu indicator has been set under Scheduling Agreement (efine (ocument #ypes in
-ustomi!ing for Purchasing
6or more information see Procure$ent /sing an O"!P Sche#uling Agree$ent and Prere:uisites for the O"!P Sche#uling
Agree$ent
#he schedule lines and releases for APO scheduling agreements are generated in the SAP APO system 1ou specify
this in the additional data for the scheduling agreement item by choosing the setting =enerate and output SA release
in APO for the 0&ternal Planning indicator
As a rule, the APO scheduling agreement in the SAP 24= system is a scheduling agreement with the document type (P.
6or more information see Procure$ent /sing an APO Sche#uling Agree$ent and Prere:uisites for the APO Sche#uling
Agree$ent
1ou should note that you must not have any items with different 0&ternal Planning settings in a scheduling agreement
because this leads to problems in the message determination process )n other words, all items of a scheduling
agreement must be planned either in the SAP APO system or in the O*#P system
Page 159 of 251
Prere*uisites for the APO Scheduling Agreement
)f you use APO sche#uling agree$ents (with planning and release creation in the SAP APO system) then you should ensure
that the following prere"uisites are met in the SAP 24= system and SAP APO system8
SAP APO System
1ou must transfer your procurement scheduling agreements to the SAP APO system 1ou can transfer the procurement
scheduling agreements from the SAP 24= system to the SAP APO system over the -ore )nterface (-)6) (See SAP 24=
System)
Procurement scheduling agreements are created as e&ternal procurement relationships in the SAP APO system
)n the e&ternal procurement relationship you must8
2eassign the release creation profile (release creation profile)
Select which schedule types (operative #elivery sche#ules and forecast<planning #elivery sche#ules) you want to use
(Scheduling Agreement with 6orecast)
)f you want to work mainly with forecast4planning delivery schedules then you can use the +usiness Add%)n (+Ad))
4SAPAPO4P'+?#PS2-?)N to define that the indicator is automatically selected when the e&ternal procurement
relationship is created /sing this +Ad) you can also influence other data relating to the e&ternal procurement
relationship or the transportation lane
(efine at what time the schedule lines should be transferred to the SAP 24= system (update live-ache)
(efine whether you want to send )nternet releases ()nternet release)
(efine whether you want to receive confirmations from your vendors (Process)
Assign the confirmation profile (-onfirmation profile)
#ustomiGing L =eneral Settings
)n -ustomi!ing for Advanced Planning and Optimi!ation (SAP APO), set e&ternal procurement for the destination location
(for e&ample, the plant) in the Publ#ype field under +asis Settings )ntegration Publication .aintain (istribution
(efinition
AuthoriGations
1ou can use the authori!ation ob3ect -?APO?0WP2 to define which activities a user is allowed to carry out 6or e&ample,
you can control whether a user can create releases, enter confirmations, or change master data
aintaining the $elease #reation Profile
(efine the release creation profile in -ustomi!ing for Advanced Planning and Optimi!ation (SAP APO), under Supply -hain
Planning -ollaborative Procurement Procurement Scheduling Agreement .aintain 2elease -reation Profile
6or e&ample, you can define that schedule lines that lie in the past and have already been sent to the vendor are totaled and
displayed as backlog in the operative delivery schedule (+acklog is only transmitted in the operative delivery schedule)
1ou can also define whether the re"uirements date sent is the pickup date or the delivery date
1ou then assign this release creation profile in the e&ternal procurement relationship to the scheduling agreement item on
the Scheduling Agreement tab page
)f you have maintained tolerances for the release creation in the release creation profile, then these are only taken into
account if you use a constant planning calendar (for e&ample, without weekends)
Stopping and $eleasing Scheduling Agreement $eleases
)f you want to stop scheduling agreement releases, you must define the relevant criteria in -ustomi!ing for Advanced
Planning and Optimi!ation (SAP APO) under Supply -hain Planning -ollaborative Procurement Procurement
Scheduling Agreement .aintain SA 2elease -reation Profile on the (ynamic Stopping tab page
#he SAP APO system can only stop releases against APO scheduling agreements, because in the SAP APO system,
releases are generated against this type of scheduling agreement only
#he SAP APO system can only stop SA releases generated by the release creation program (transaction
4SAPAPO4P'+S-5;)
SA releases generated manually in the product view are not stopped
1ou can release stopped SA releases in the function for processing SA releases
)f you are using an SAP 24= system (Automotive), you can also stop releases against O*#P scheduling agreements
Page 160 of 251
1ou can specify whether an SA release is to be stopped either in the additional data for the SA item (static stopping, that is,
always), or in the SA release creation profile (dynamic stopping, that is, on the basis of certain criteria) 1ou can specify this
for each release type
6or more information see the SAP *ibrary for SAP for (iscrete )ndustries under SAP for Automotive Scheduling
Agreement Automotive8 0nhancements for Scheduling Agreement 2eleases (62- or I)# (elivery Schedules) @
Stopping and 2eleasing SA 2eleases
Settings for Scheduling Agreement $eleases Output &SAP APO System'
1ou must define the output of scheduling agreement releases in the SAP APO system
6or more information on the settings for outputting scheduling agreement releases, see Setting Message Actions 2Sche#uling
Agree$ent +elease3
In+ound Deli%ery
)f an inbound delivery is registered during parking with multi%level automotive goods receipt, it is given the status )n Plant
#his status is transferred from the SAP 24= system to the SAP APO system over the APO -ore )nterface (APO%-)6) at the
same time as the inbound delivery
#he system can take inbound deliveries with this status into account as category )' when calculating the daysO supply or the
receipt daysO supply
.ake the necessary settings in -ustomi!ing for Advanced Planning and Optimi!ation (SAP APO), under Supply -hain
Planning Production Planning and (etailed Scheduling (PP4(S) Product Planning #able (efine (aysO Supply #ypes
Display (ast Deli%eries
)f you want to use this function, you must8
In the $!8 system
Assign a confirmation control key with the internal confirmation category < (inbound delivery) to the APO scheduling
agreement
#ransfer the data on the deliveries from the O*#P system to the APO system over the -)6
#o do so, set the POs42e"uisitions indicator in the integration model of your O*#P system
#his means that the last deliveries are displayed in the e&ternal procurement relationship
In the SAP APO system
.ake the relevant settings on the *ast (eliveries tab page in the release creation profile of the APO scheduling agreement
#his means that the last deliveries are determined when release creation takes place and sent to the vendor in the release
#he last deliveries are transferred from the SAP 24= system to the SAP APO system over the -)6 when inbound deliveries
are created or changed and when goods movements take place and they are displayed in the e&ternal procurement
relationship
Settings for #onfirmation $eceipt &#DS'
)f you receive confirmations from vendors within Collaborative Manage$ent of ,elivery Sche#ules, then you must make
settings for the process with confirmations for the relevant scheduling agreement item in the e&ternal procurement
relationship
6or confirmations that you receive for SA releases, you can define in -ustomi!ing for Supply -hain Planning how incoming
confirmations are checked, or under which conditions an alert is generated upon receipt of a confirmation
#he confirmation profiles (or procedures) delivered in the standard system control whether, upon receipt of a confirmation8
An alert is always generated (no tolerance check)
)f you only receive confirmations in e&ceptional cases then you should use the confirmation profile (Alert Always with -onf
2eceipt), so that an alert informs you of every incoming confirmation
#he current confirmation is compared with the last confirmation (tolerance check)
#he current confirmation is compared with the operative delivery schedule (tolerance check)
6or the process with confirmation you must make the following settings in -ustomi!ing for Supply -hain Planning under
-ollaborative Procurement @ -onfirmation 2eceipt8
1. (efine checking procedures
2. (efine tolerance profiles
)n the tolerance profile you can set an individual or a totals check
)ndividual -heck
Page 161 of 251
)f you want an individual check of "uantity and date pairs then you can either choose either an e&act%to%the%day or
to%the%second check Select -heck #ime Stamp
)n this way you can define a more e&act check for the near future and a more appro&imate check for the distant
future
#otals -heck
)f you want to carry out the totals check for periods in your planning calendar then you must create a planning
calendar in -ustomi!ing for Advanced Planning and Optimi!ation under .aster (ata @ -alendar @ .aintain
Planning -alendar (#ime Stream), and assign this planning calendar to the tolerance profile
3. (efine confirmation profiles
4. Assign the confirmation profile to the re"uired item in a procurement scheduling agreement in the e&ternal procurement
relationship (.aster (ata Procurement .aster (ata 0&ternal Procurement 2elationship)
igration of Procurement Scheduling Agreements
6or more information, see the SAP Note FDJF9;
SAP $!8 System
Document Type of Scheduling Agreement
As a rule, the APO scheduling agreement in the SAP 24= system is a scheduling agreement with the document type (P or a
scheduling agreement without release documentation
)f you use scheduling agreements of the document type (PA without confirmation control key then no default "uantities can
be determined from the release upon goods receipt
)f you use scheduling agreements of the document type (PA with confirmation control key then the default "uantities from
the confirmation (shipping notification) are used
As a rule, the O(TP scheduling agreement in the SAP 24= System is a scheduling agreement with the document type (PA.
aterial aster
1ou should assign the .P2 type @4 ('4o .2P with +O. 0&plosion) to the materials used 1ou do this in the material
master, on the .2P ; tab page
$elease #reation
#he schedule lines and releases for APO scheduling agreements are generated in the SAP APO system 1ou specify this in
the additional data for the scheduling agreement item by choosing the setting =enerate and output SA release in APO for
the 0&ternal Planning indicator
Note that you must not have any items with different 0&ternal Planning settings in a scheduling agreement because this
leads to problems in the message determination process )n other words, all items of a scheduling agreement must be
planned either in the SAP APO system or in the O*#P system
)f delivery schedule lines already e&ist for an SA item, the setting for the 0&ternal Planning indicator can no longer be
changed
#reate and Acti%ate Integration odel
-reate an integration model that contains material masters, plants, delivery schedule items, vendors, stocks and purchase
orders4re"uisitions (for transferring the release schedule lines or shipping notifications4inbound deliveries)
Activate the model
)n the SAP 24= system, choose *ogistics -entral 6unctions Supply -hain Planning )nterface -ore )nterface
Advanced Planner and Optimi!er @ )ntegration .odel @ Cenerate
#hange Transfer
A change transfer only takes place for certain data, for e&ample for 0&ternal Planning (APO.S) or (eletion )ndicator
(*O0LX) that are defined as change%relevant fields for the message type -)6S2- (APO -)68 -hange (ocuments for
Sources of Supply)
6or a change transfer in SAP 24=, choose *ogistics -entral 6unctions Supply -hain Planning )nterface -ore
)nterface Advanced Planner and Optimi!er @ )ntegration .odel @ -hange #ransfer @ .aster (ata
)f you want to transfer additional fields to SAP APO then you must add these fields to the change%relevant fields 6or
e&ample, you can add the vendor material, that is used when confirmation are received to determine the relevant scheduling
agreement
-hoose #ools A*0 A*0 (evelopment )(oc 0ngineering -hange .anagement (efine -hange%2elevant
6ields, to add fields
#ustomer.Specific 0nhancements and )AdIs
As of SAP 24= 2elease >F- with Plug%0n P) <::;<, the following enhance$ents are available8
Page 162 of 251
SAP APO SAP $!8
#IFP/$47 (0nhancement Purchase Order )nterface ()nbound),
#o change purchase order data from the SAP APO System before a purchase re"uisition, scheduling agreement
schedule line or a purchase order is created in the O*#P system
0@ITKSAP(#P/$K445 -ustomer 0&it 2eceiver .odule for APO Purchase Order (ocuments ()nbound),
change scheduling agreement schedule lines for e&ample
SAP $!8 SAP APO
#IFP/$45 -nhance$ent for the #ransmission of -ustomer%specific Purchase Order 6ields (SAP 24= SAP APO)
0W)#?SAP*.0AP?::; E -ustomer 0&it for Selecting -ustomer%Specific Purchasing (ata, to control which scheduling
agreement, contract and purchasing info record data you send from your SAP 24= system to your SAP APO system
#IFS$#45 (0nhancement for the #ransmission of -ustomer%specific 6ields, Sources of Supply)
#o control which data for scheduling agreements, contracts and purchasing info records are sent from the O*#P system to
the SAP APO system
0W)#?SAP*-S2S?::< -ustomer%0&it for Selection of customer%specific scheduling agreement data
0W)#?SAP*-S2S?::> -ustomer%0&it for customer%specific selection of vendor4plant location
SAP APO
P/$ 0nhancements
0W)#?4SAPAPO4SAP*..P/220*?::>, to change release header and schedule lines when the release is created in
the SAP APO system
0W)#?4SAPAPO4SAP*..P/220*?::D, to change the )(oc data that is generated when release output takes place
Scheduling Agreement $elease #reation
)n the SAP APO system, scheduling agreement (SA) releases take the form of operative and forecast4planning delivery
schedules
1ou can use this function to create operative #elivery sche#ules or forecast<planning #elivery sche#ules against APO scheduling
agreements
SA releases against O*#P scheduling agreements (that is, forecast and I)# delivery schedules) are created in the O*#P
system
1ou use the release creation profile 2APO sche#uling agree$ent3 to define the conditions under which releases issued against
a scheduling agreement item are generated 1ou assign a release creation profile to an item of a scheduling agreement in
the e&ternal procurement relationship
1ou can also set in the e&ternal procurement relationship whether the operative delivery schedule, that is its schedule lines,
is transferred to the SAP 24= system when the release is created or when it is output in the SAP APO system 1ou define
this in the update live-ache field (;: E At #ime of Ceneration of Operative (elivery Schedule, >: E At #ime of Output of
Operative (elivery Schedule)
Integration
)f you use 0nternet releases, then your vendors can display and acknowledge these releases in the Supplier =orkplace, which
your vendors can access over the )nternet
#o make this possible, you must select )nternet 2el in the e&ternal procurement relationship and set the update of the
live-ache there accordingly (G: E At #ime of -onfirmation of Operative (elivery Schedule in S'P) 1ou make these settings
to define at what time the schedule lines are transferred to the connected O"!P syste$ (generally an SAP 24= system)
)n this case, the schedule lines are only transferred to the SAP 24= system when the vendor acknowledges the release in the
Supplier 'orkplace
6or further information on the Supplier 'orkplace see the SAP *ibrary for .aterials .anagement (..) under Supplier
'orkplace
6or )nternet releases, no actions are generated at the time that the release is created
6or more information see Procure$ent /sing an APO Sche#uling Agree$ent
Prere*uisites
)n the release creation profile, which you maintain in -ustomi!ing for Advanced Planning and Optimi!ation (SAP APO) under
Supply -hain Planning -ollaborative Procurement, you can specify when and how often SA releases are to be generated
Page 163 of 251
)f you create a release using the release creation report (4SAPAPO4P'+?20*0AS0?-20A#0), the system determines the
date of the ne&t release creation (provided that you have defined a planning calendar in the release creation profile)
'e recommend that you choose a suitable date for the periods when maintaining the planning calendar, because the system
only creates releases during release creation if the ne&t creation date lies before ;<8:: on the same day
6or e&ample, in the e&ternal procurement relationships, <F:> ;>8:: has been defined as the ne&t release date
1ou e&ecute the release creation report at ;J8::
#he system does not create a release for this e&ternal procurement relationship because the time for the creation of releases
is after ;<8::
#he release creation report does not create the release for this e&ternal procurement relationships until the ne&t day
6or more information see Prere:uisites for the APO Sche#uling Agree$ent and +elease Creation Profile 2APO Sche#uling
Agree$ent3
Features
Scheduling Agreement $elease #reation
1ou can create operative and forecast4planning delivery schedules )n addition, you can first carry out a test run to see which
SA releases would be created
1ou can display a detailed log listing all the relevant scheduling agreement items
An SA release can be stopped if it differs from the last%transmitted release to such a large e&tent that the tolerance check
reveals a ma3or change in the overall delivery schedule situation that is outside the specified tolerances
See also Stopping an# +eleasing SA +eleases
)n addition to the delivery schedule lines, the SA release you transmit to your vendor can also include up to nine of the most
recent deliveries received for a scheduling agreement item
1ou can specify whether and how many of the last deliveries are to be shown in an SA release in the release creation profile
under -ollaborative Procurement in -ustomi!ing for Supply -hain Planning
Scheduling Agreement $eleases in the Product "iew and the Product Planning Ta+le
)n the product view, on the Periods tab page, or in the product planning table, you can also create SA releases for selected
delivery schedule lines
)f you enter or change a re"uirement in the product planning table, choose 0N#02 #he system issues a message advising
you that the order or schedule line was created successfully or (if applicable) with a delay
#o generate scheduling agreement releases you must carry out the following steps8
1. Select the chosen item (Sch*ne) and choose
2. )n the conte&t menu, choose -reate Operative (elivery Schedule or -reate 6orecast4Plng Schedule
1ou can also display e&isting SA releases from the menu
3. #o save, choose
Operative delivery schedules are displayed as new orders with the category SAg 2el 6orecast4planning delivery schedules,
that is long%term re"uirements (fi&ed) that are transmitted to the vendor and are not delivery%relevant, are not displayed
#he new data completely replaces the last transmitted data in the live-ache )n the SAP APO system, only the operative
delivery schedules are needed in the live-ache8 forecast4planning schedules are not needed
#he live-ache contains the following categories8 Sch*ne, SAg 2el, and PO memo (shipping notification)
#he database contains additional data on operative delivery schedules, forecast4planning schedules, and acknowledgments
See Processing APO Sche#uling Agree$ents in the Pro#uct Planning !able an# Pro#uct 4ie
#he purchase order (PO) history contains information on goods and in%oices recei%ed Since there should be no
superfluous PO history in the SAP APO system (that is data that is already present in the SAP 24= system), the data is newly
imported from the SAP 24= system by 2emote 6unction -all (26-) each time it is needed
1ou can notify your vendor of up to nine last deli%eries in an SA release #he SAP APO system determines the last
deliveries relating to the relevant SA item at the time of release creation and includes them in the SA release output
#his provides the vendor with more e&act information about which deliveries you have already received at the time of release
creation (that is, which data the SA release is based on)
See also 0nboun# ,elivery1 5oo#s +eceipt an# 0nvoice<Cre#it Me$o
Acti%ities
6rom the menu, choose Supply -hain -ollaboration @ -ollaborative Procurement @ Scheduling Agreement 2eleases @
-reate 2eleases
Page 164 of 251
0nter the necessary data (for e&ample, location and product) and choose
A window appears, showing you8
5ow many scheduling agreement items have been selected
5ow many operative and4or forecast4planning delivery schedules have been created
)f you are using a detailed log, the system will show which scheduling agreement, which location, which product, and which
item were taken into account in the SA release creation process
6or more information on outputting scheduling agreement releases and how you can process previously created4outputted
releases, see Outputting Scheduling Agreement 2eleases and Processing Scheduling Agreement 2eleases
DisplayI Output and Acknowledge SA $eleases
1ou can use this function to display or output scheduling agreement (SA) releases that have already been created, or to
acknowledge them yourself over the )nternet
1ou can simultaneously display the SA releases (operative and forecast4planning delivery schedules) that have been created
against several scheduling agreements
1ou can use the following functions8
-ompare releases
(isplay last deliveries
(isplay action log for an SA release
(isplay product planning table
(isplay source of supply
2elease stopped SA releases
Output SA releases
Acknowledge )nternet releases yourself
'ith this function, you can only process SA releases against APO scheduling agreements SA releases against O*#P
scheduling agreements are processed in the O*#P system
1ou can also view confirmations$ however, you cannot process them
Prere*uisites
6or more information on the prere"uisites, see Prere:uisites for the APO Sche#uling Agree$ent
Features
#he following functions are available for processing SA releases8
#ompare releases
#o compare two SA releases, select them and then choose (-ompare 2eleases)
)n the window that appears, you see a comparison of the release "uantities, the open "uantities, and the cumulative
"uantities
1ou can use the graphical display function ( Craphic) to compare more than two SA releases with each other
Display last deli%eries
-hoose (*ast (eliveries) to display the last deliveries for an SA release #he last deliveries are included in the SA
release transmitted to the vendor
Display action log for an SA release
-hoose (Action *og of a 2elease) to view the processing steps carried out for an SA release to date (for e&ample,
stopped, released)
Display product planning ta+le
-hoose ((isplay Product Planning #able) to branch directly to the product planning table
Display source of supply
-hoose ((isplay Source of Supply) to display the e&ternal procurement relationship for an SA release
$elease stopped SA releases
-hoose (2elease Stopped 2eleases) to release stopped SA releases or stopped )nternet releases
Page 165 of 251
6or more information on stopped SA releases, see Stopping an# +eleasing SA +eleases
Output SA releases
-hoose ()ssue 2eleases) to output (print, transmit) an SA release directly
Acknowledge Internet releases yourself
-hoose (Acknowledge )nternet 2elease) to acknowledge )nternet releases yourself
See Acknole#ging 0nternet +elease
Acti%ities
1. -hoose Supply -hain -ollaboration @ -ollaborative Procurement Scheduling Agreement 2eleases Process
Scheduling Agreement 2eleases
)n the product view and product planning table, you can display and process the transmitted SA releases for the e&ternal
procurement relationship per scheduling agreement item -hoose to process scheduling agreement releases
1ou can display and process releases against a scheduling agreement from within the e&ternal procurement
relationship -hoose SA releases
2. 0nter the necessary data (for e&ample, product and location) and choose
3. #he system displays a list showing all the scheduling agreements that meet your selection criteria, and the SA releases
that relate to them
#his list includes the following data8
#he "uantity (the release "uantity) that was notified to the vendor as open
#he open "uantity E that is, the open schedule line "uantity less the "uantity already confirmed (notified) that is still
in transit
#he -2A (-umulative 2eceived Auantity)
#he cumulative released "uantity (total of the "uantities of an item procured % that is, released % against a
scheduling agreement)
#he cumulative (total) re"uested "uantity of an SA release
#he time stamp of the scheduling agreement release
#he status of the scheduling agreement release8
SA release was created but has not yet been transmitted
SA or )nternet release was stopped
Stopped SA or )nternet release has been released
SA release has already been transmitted
Bendor has acknowledged the )nternet release
Outputting Scheduling Agreement $eleases
#he schedule lines in a scheduling agreement (SA) release inform the vendor of e&act re"uired delivery "uantities and dates
#he delivery schedule lines transmitted to the vendor in an SA release can be viewed at any time and you can trace their
history (see Processing Sche#uling Agree$ent +eleases)
1ou can use this report program to send releases against APO scheduling agreements to the relevant source locations, (eg
vendors) on a regular basis 1ou can transmit SA releases by e%mail, W.*, or the )nternet, or in hardcopy form and by fa&
)n the SAP APO system, actions are generated for SA releases which you can then process (output) 1ou use actions to
control the creation and output of SA releases (See also Setting Message Actions)
#he Post Processing 6ramework (PP6) replaces message control (which has been used in SAP 24= until now) and provides
a standardi!ed interface to any type of output medium SAP Smart 6orms are used for creating and maintaining forms for
mass printing
6or more information, see the SAP *ibrary for mySAP #echnology -omponents under Post Processing Fra$eork 2PPF3
and SAP S$art For$s 2BC%S+4%SC+3
#his function can only be used to output SA releases against APO scheduling agreements SA releases against O*#P
scheduling agreements are output in the O*#P system
Page 166 of 251
6or more information, see the SAP *ibrary for Purchasing (..%P/2), under Bendor Outline Agreements (..%P/2%OA) c
Scheduling Agreement
Integration
Automoti%e ! SAP for Discrete Industries
)f you implement an SAP 24= system (Automotive) then the unloading point stored in the additional data for the scheduling
agreement is displayed as the Staging Area on the Scheduling Agreement tab page in the e&ternal procurement
relationship
)f you want to copy the unloading point from the SAP 24= system to the SAP APO system you must use the Custo$er%-&it
-)6S2-:; (0W)#?SAP*-S2S?::< -ustomer 0&it for Selecting -ustomer%Specific Scheduling Agreement (ata)
SAP 0nterprise Portals . )usiness Package for Automoti%e Suppliers
)f you use 0nternet releases, then your vendors can view and acknowledge these releases in the Supplier 'orkplace (S'P),
which your vendors can access over the )nternet
#o make this possible, you must select )nternet 2el in the e&ternal procurement relationship and set the update of the
live-ache there accordingly (G: E At #ime of -onfirmation of Operative (elivery Schedule in S'P) 1ou make these settings
to define at what time the schedule lines are transferred to the connected O"!P syste$ (generally an SAP 24= system)
)n this case, the schedule lines are only transferred to the SAP 24= system when the vendor acknowledges the release in the
Supplier 'orkplace
6or more information about the Supplier 'orkplace, see the SAP *ibrary for (iscrete )ndustries under Supplier
=orkplace
6or )nternet releases, no actions are generated at the time that the release is created
6or more information see Procure$ent /sing an APO Sche#uling Agree$ent
Prere*uisites
aintaining the $elease #reation Profile
1ou can maintain a release creation profile in -ustomi!ing for Advanced Planning and Optimi!ation, under Supply -hain
Planning -ollaborative Procurement Procurement Scheduling Agreement .aintain 2elease -reation Profile 1ou
can then assign it to an APO scheduling agreement in the relevant e&ternal procurement relationship
6or more information, see +elease Creation Profile 2APO%Sche#uling Agree$ent3
Setting essaging Actions
)f you wish to output SA releases using this program, then Processing via selection report must be set as the dispatch time
(Supply -hain Planning -ollaborative Procurement Procurement Scheduling Agreement (efine Actions for the
Output of Scheduling Agreement 2eleases)
1ou can set in the e&ternal procurement relationship whether the operative delivery schedule, that is its schedule lines, are
transferred to the SAP 24= system when the release is created or output in the SAP APO system 1ou define this in the
update live-ache field (;: E At #ime of Ceneration of Operative (elivery Schedule, >: E At #ime of Output of Operative
(elivery Schedule)
6or more information on the prere"uisites, see Prere:uisites for the APO Sche#uling Agree$ent and Setting Messaging Actions
Features
#his report processes actions for scheduling agreement releases selected according to the criteria entered
Acti%ities
-hoose Supply -hain -ollaboration -ollaborative Procurement Scheduling Agreement 2eleases )ssue 2eleases
On the ne&t screen, enter your selection criteria
1. Select the desired scheduling agreements and choose
A list of actions for SA releases appears
#here you see the status, indicating whether the action has been processed or not and if so, whether or not processing
was successful
#he following statuses are possible8
Processed
#his means that the SA release has already been output, but it can be output again
Not yet processed
)ncorrectly processed
Page 167 of 251
#he application key you see in the list of actions is made up of the following8
Scheduling agreement number
)tem number
2elease type (operative delivery schedule or forecast4planning schedule$ technical values ;, <)
2elease number
2. #o output operative and forecast4planning delivery schedules, select the re"uired actions for SA releases and choose
1ou can also send actions for SA releases several times or choose another printer
#he SA release is sent to the address in the e&ternal procurement relationship )f no address is recorded there, it is sent
to the address in the source location (address number in source location)
6urther functions are available to you in the list8
Preview
)f _printout` has been defined for the selected action for the SA release, you can view the print preview
Processing log
#he processing log is only available in the case of incorrectly processed actions for SA releases (status )ncorrect)
(uring the output of actions for SA releases, the print%dependent data is updated Print%dependent data is, for e&ample,
the data in the SA release such as the processing data (time stamp) or live-ache (if defined in the e&ternal procurement
relationship)
'hen displaying scheduling agreements, you see from the status which SA releases have already been sent
Stopping and $eleasing Scheduling Agreement $eleases
)n the case of materials sub3ect to substantial fluctuation in re"uirements, or materials in the process of introduction or
discontinuation, it may be necessary for the responsible production planner to take another look at the relevant SA releases
before they are sent to the vendor
#his function enables you to create an SA release but, after doing so, initially withhold it from the message output process
(W.*, printout, 0() and so on) E that is, to stop it
#hese stopped SA releases must then be released by the responsible production planner, in a separate step Only once
they have been releases is the SA release action generated
Once you have released the stopped SA releases, you can output the actions generated as a result in the usual way (see
Outputting Sche#uling Agree$ent +eleases)
Prere*uisites
)f you wish to use this function, you must make the relevant settings in -ustomi!ing for Advanced Planning and Optimi!ation
(SAP APO) under Supply -hain Planning -ollaborative Procurement Procurement Scheduling Agreement .aintain
SA 2elease -reation Profile on the (ynamic Stopping tab page
#he SAP APO system can only stop SA or )nternet releases against APO scheduling agreements, because in the SAP APO
system, releases are generated against this type of scheduling agreement only
#he SAP APO system can only stop SA releases generated by the release creation program (transaction
4SAPAPO4P'+S-5;)
SA releases generated manually in the product view are not stopped
)f you are using an SAP 24= system (Automotive), you can also stop releases against O*#P scheduling agreements
6or more information, see the documentation for SAP for Automotive under Scheduling Agreement Automotive8
0nhancements for Scheduling Agreement 2eleases (62- or I)# (elivery Schedules) Stopping and 2eleasing SA
2eleases
Features
#he SAP APO system can dynamically stop operative and forecast4planning delivery schedules generated by the SA release
creation program
(ynamic stopping means that an SA release is withheld from the message output process because it differs to such a large
e&tent from the last%transmitted SA release that the tolerance check reveals a ma3or change in the overall delivery schedule
situation that is outside the accepted tolerances
Page 168 of 251
Acti%ities
Stop SA $eleases
#o dynamically stop SA releases, you must maintain tolerance limits for dynamic stopping in the release creation profile
1ou can also tell whether or not an SA release has been stopped from the Status column in the Process SA 2eleases
function8
Shows that this SA release was stopped during the release creation process and still has the status Stopped
Shows that this SA release was stopped during the release creation process but in the meantime has been released
$elease Stopped SA $eleases
)n the Process SA 2eleases function, you can display and release stopped SA releases An SA release action is not
generated until you release stopped SA releases #his must then be output in the usual way
#o release a stopped SA release, proceed as follows8
1. -hoose Supply -hain -ollaboration -ollaborative Procurement Scheduling Agreement 2eleases Process
2eleases
)f you want to display only stopped SA releases then you can select releases according to their status
#o do so, enter 74 (SA release stopped), for e&ample, in the 2elease Status field in the Ob3ect -haracteristics (SA
2eleases Only) area
2. Select the SA release you want to release and choose
$elease #reation Profile &APO Scheduling Agreement'
#he release creation profile is used to specify the following for operative and forecast4planning delivery schedules issued
against APO scheduling agreements8
5ow the hori!on of the scheduling agreement (SA) release (delivery schedule) is determined
5ow schedule lines from the past are handled in the SA releases
'hich event triggers the release creation process (changes to schedule lines and4or the ne&t transmission date being
arrived at)
'hether a tolerance check is carried out for releases that are created due to changes
'hether and how many _last deliveries` the vendor is informed of in the SA release
#hose tolerances are to be checked and, if necessary, SA releases stopped in the event of changes in the overall
delivery schedule situation
#he settings in the release creation profile can have the following effects for an e&ternal procurement relationship for a
scheduling agreement item8
1our vendor receives operative delivery schedules on a weekly basis 0ach schedule contains lines covering the ne&t three
weeks )n addition, the vendor receives a forecast4planning delivery schedule at the beginning of each month, which covers
the following three months
)f the scheduling agreement schedule lines have changed significantly, updated SA releases can be sent to the vendor
#he release creation profile that you maintain in the APO system is only valid for APO scheduling agreements
6or releases against an O*#P scheduling agreement, which are created in the O*#P system, it is the release creation profile
in the O*#P system that is applicable
Prere*uisites
Features
1ou can define the following in the release creation profile8
Area For each SA release type &operati%e or F!P schedule' you defineC
*ayout
'hether backlogs and immediate re"uirements should be determined
'hether schedule lines should be added together so that all schedule lines with a date in the past
or present are added to the current dayOs schedule line
'hether all schedule lines are issued 3ust as they are maintained in the system
6or which release hori6on release "uantities are displayed
.odes of creation 'hether (and if so, under which conditions) an SA release is created (creation strategy)
Page 169 of 251
#olerances
'hether a tolerance check is carried out for releases that are created due to changes )n this way
you can define that releases are only created when significant changes occur
*ast (eliveries 'hether and how many _last deliveries` the vendor is informed of in the SA release
(ynamic stopping
'hether a tolerance check is to be carried out for an SA release and whether a release is to be
stopped if it differs too greatly from the last release transmitted
1ou assign the release creation profile to an e&ternal procurement relationship for an APO scheduling agreement and in this
way you define how SA releases are generated for this SA item
'hen scheduling agreement data is transferred from your O*#P system to the SAP APO system via the SAP APO -ore
)nterface (-)6), the release creation profile is not included in the data transmitted 1ou must create a new release creation
profile for APO scheduling agreements in your SAP APO system and assign it to the relevant SA item (of procurement
category APO scheduling agreement) in the e&ternal procurement relationship
)f you wish to use forecast4planning (64P) delivery schedules in addition to operative delivery schedules, you must specify
this in the e&ternal procurement relationship (in the Scheduling Agreement with 6orecast field on the Scheduling
Agreement tab page)
#he settings for 64P delivery schedules from the release creation profile are only taken into account in the SA release
creation process if you have specified in the e&ternal procurement relationship that 64P delivery schedules are to be created
1ou wish to provide your vendor not only with data on your concrete short%term product re"uirements (using operative
delivery schedules) but also with data on your more tentative longer%term re"uirements (using forecast4planning delivery
schedules) #herefore, you select the Scheduling Agreement with 6orecast indicator for this item in the e&ternal procurement
relationship
Acti%ities
1ou define the release creation profile in -ustomi!ing for Advanced Planning and Optimi!ation (SAP APO), under Supply
-hain Planning -ollaborative Procurement Procurement Scheduling Agreement .aintain 2elease -reation Profile
1ou then assign this release creation profile to the e&ternal procurement relationship for the scheduling agreement item on
the Scheduling Agreement tab page
Direct Deli%ery from Production Plant
)f you deliver large "uantities of a finished product to a specific customer (such as for promotions), it makes sense to deliver
these "uantities directly to the customer from the production plant, for e&ample Since the products do not have to go to a
distribution center first, you can thus save transportation and storage costs
6or the heuristic%base# planning in Supply Network Planning (SNP), you can specify that certain products are to be preferred
for direct delivery #he system then uses the #ransport *oad +uilder (#*+) to check which product "uantities can be
delivered directly by which means of transport #he system covers any remaining "uantities using standard source
determination
)n most cases, only a small percentage of the products to be planned can be considered for direct delivery (appro&imately <%
=a8 for e&ample, promotion products) 6or performance reasons, we recommend that you do not select a large number of
products for direct delivery
#he process described is an e&ample (irect delivery is not limited to one location type, such as a production location or a
customer location
Prere*uisites
1ou have set the (irect (elivery indicator for the transportation lanes between the production locations and customer
locations for which you want to specify a direct delivery 1ou set the indicator for a specific product in the product%
specific section of the transportation lane 1ou can also set the indicator for a specific means of transport or for all
means of transport
1ou have created at least one #*+ profile for the #*+ used in the process and have assigned the profile to the
transportation lanes that you have flagged for direct delivery 1ou do this on the SAP 0asy Access screen under
Advanced Planning and Optimi!ation Supply Network Planning 0nvironment -urrent Settings Profiles
(efine #ransport *oad +uilder (#*+) Profiles 1ou make the assignment in the #*+ Profile field of the transportation lane
for a specific means of transport Note that the #*+ will use this profile again if there is #*+ planning at a later time 6or
more information, see #*+ Profile
)f you want the #*+ to combine the transport loads evenly or according to product, you can specify this in the *oading
.ethod field of the transportation lane #he default value is Straight *oading
Page 170 of 251
#he system does not consider any other #*+ settings such as the pull%in hori!on or the available%to%deploy (A#()
"uantity
)n -ustomi!ing for Supply Network Planning under +asic Settings .aintain Clobal SNP Settings, you have specified
that the SNP heuristic is to consider the direct delivery via transportation lanes in the 5eu8 (irect (elivery field #he
default value is No (irect (elivery
1ou have made the master data settings and any other settings necessary for e&ecuting an SNP heuristic 6or more
information, see 2unning the 5euristic in the +ackground
)n particular, you have determined the low%level codes before the first SNP heuristic run or when changing the master
data 6or more information, see "o%"evel Co#e ,eter$ination
Process
1. 1ou e&ecute an SNP heuristic 6or more information, see 2unning the 5euristic in the +ackground 1ou can also
e&ecute the SNP heuristic interactively )n contrast to running the SNP heuristic in the background, in which the system
considers all the products of the transportation lane, you can interactively select a partial "uantity of the products
'e recommend that you select the location heuristic #he network heuristic takes considerably longer because it does
not consider any cross%location low%level codes
'e recommend that you use the planning book 9A(2P or a planning book based on it so that you can display the
interactive SNP planning results (see 2esult section)
2. #he SNP heuristic first tries to cover the demand "uantities of the customer location via the transportation lanes you
have flagged for direct delivery )f there are more than one direct delivery transportation lanes for a product, the system
considers the procurement priorities of the transportation lanes )n this step, the system does not consider "uota
arrangements
3. #he #*+ uses the settings made in the #*+ profile to check which product "uantities can be delivered by which means
of transport via the flagged transportation lanes
)n contrast to the normal #*+ run, the #*+ does not create any #*+ shipments in this process #he SNP heuristic
creates SNP stock transfers as usual
4. #he SNP heuristic checks if there are any remaining "uantities )t then e&ecutes a standard source determination for
these remaining "uantities 6or more information, see Source ,eter$ination 2.euristic3
$esults
)n interactive SNP planning, you can see which product "uantities have been delivered via which transportation lanes
-hoose (isplay dependent ob3ects (ependent transportation lanes in the planning book 9A(2P or a book based on
it
#he log contains the SNP stock transfers created as well as any error messages, 3ust as in a normal SNP heuristic run )f you
want to see information about the integrated #*+ run in the log, you can activate it by defining the user parameter
4SAPAPO4#*+?S5O'?.SC in your user settings
Phase.Out #ontrol for 0nd Products
Note8 As of SAP APO >:, this function has been replaced by the pro#uct interchangeability function #his function is still
available but we recommend that you use the new function 6or more information, see Pro#uct 0nterchangeability in Supply
Netork Planning
Purpose
1ou use this process to model the discontinuation of end products to set how one product replaces another 1ou can define
introductory periods for specific products and allow an overlap between the two products to allow stocks of the product to be
discontinued to be reduced +oth products are compounded within one product group
Prere*uisites
1ou have created a location product hierarchy in the master data
1ou have created the demand plan on the basis of this product group or location product group (that is, the forecast has
been created at product group level)
Page 171 of 251
Process Flow
1. )n the Product Split function (APO 0asy Access menu @ (emand Planning @ 0nvironment @ Product Split), you set the
SNP ()SACC indicator and specify the product to be discontinued, the product you want to be its replacement, and
when you want this to happen )n this transaction, you also define a period for reducing stock of the old product, with the
result that the system only takes the new product into account when there is no more stock of the old product Once this
period has come to an end, the system only takes into account stock of the new product
6or more information about maintaining product discontinuation data with the Product Split function, see the 6; help
for the SNP ()SACC field
2. )n interactive (emand Planning (APO 0asy Access menu @ (emand Planning @ Planning @ )nteractive (emand
Planning), you run a product group heuristic based on planning book 9ASNP5)02 (and data view SNP5)02)
3. #he system aggregates the stock of individual products to product group level and creates a replenishment plan using
forecasts, stocks, and possible safety stocks, and taking into account the latest introduction date (Supply (ate) that was
specified in the Product Split
4. 1ou then run the time%based disaggregation
5. #he system disaggregates the product group receipt elements (shown in the upper table of the planning table) over the
individual products as demands (shown in the lower table), taking into account the earliest introduction date for the
replacement product that is specified in the Product Split (from date)
Supply and Demand Propagation
Supply and demand propagation in Supply Network Planning is a means of implementing changes caused by constraints
throughout your supply chain in search of a feasible solution to fulfill demands #he aim of constraint propagation in Supply
Network Planning is to propagate changes in key figure values in time series throughout an entire time series network )t is
therefore necessary that your planning is based on time series, and not orders, when you wish to use Supply , (emand
Propagation #he Supply Network Planning relationships that reflect the dependencies between the key figures are used in
propagation
Propagation is not carried out infinitely )nstead, "uantity restrictions, for e&ample resource capacities, and time restrictions,
such as transportation times and calendars, are taken into account #aking into account such restrictions implies that, at
times, only a portion of a given demand can be confirmed
1ou use propagation in interactive planning in Supply Network Planning 6or that reason, the propagation algorithm is very
rapid )t propagates "uantities by taking "uota arrangements and priorities into account Only SNP production process
models are used with constraint propagation
/nlike heuristic or optimi!ation planning, supply and demand propagation does not consider lot si!es$ that is, it does not use
a rounding logic
Prere*uisites
1ou have created the items below in the following se"uence8
aster planning o+,ect structure (1ou can use the standard master planning ob3ect structure 9ASNP+AS which is
shipped with APO, or create your own, keeping in mind that it should contain SNP characteristics only)
Page 172 of 251
Storage +uckets profile (if you are not using the planning area 9ASNP:;) (#he storage buckets profile must contain all
buckets that are later used in the planning buckets profile)
Planning area (1ou can use the standard planning area 9ASNP:; which is shipped with APO or create your own 1ou
can combine key figures from SOP, SNP and (P 1ou can also create your own key figures)
aster data (1ou must create the products and locations and assign the location products to a model)
Planning area (1ou also must activate the planning area for simulations)
Planning +ook (1ou can use the standard planning book 9ASOP which is shipped with APO or create your own)
acro (1ou can create your own macros to fle&ibly control propagation)
1ou have defined your constraints are RhardR in the planning area
Process Flow
#he following is a simple step%by%step e&ample of how to e&ecute Supply , (emand Propagation8
1. )n the SAP 0asy Access menu, you choose Supply Network Planning c Planning c Sales , Operations Planning
(SOP)
2. On the Supply Network Planning desktop, you double%click on a data view of the planning book
3. )n the shuffler, you choose APO location product
4. 1ou choose 0nter
5. 1ou double click on a location product in the list
6. As the constraint, you enter a value of the key figure 9A#S.*:SW) (fi&ed storage demand)
7. As the demand, you enter a value in the key figure 9A#S.*:*6O (forecast) in a later bucket
8. -hoose 0nter
#his action causes propagation Only the deliverable portion from the storage location (fi&ed receipt) is confirmed
1ou choose Save to transfer the values from the simulation in interactive planning to live-ache
01ecuting Supply > Demand Propagation
#he following is an step%by%step procedure of how you would go about e&ecuting Supply , (emand Propagation 1ou can
use this procedure as a tutorial
Prere*uisites
1ou have entered all the master data re"uired for Supply , (emand Propagation
-hoosing a procurement type for the location products is essential for Supply , (emand Procurement #he procurement
type dictates, which procurement options are available for the propagation7
Procedure
1. -reate a master planning o+,ect structure, or use 9ASNP+AS, which is shipped with APO 2elease =:A #he
characteristics relevant for planning are thereby determined
a. 6rom the SAP 0asy Access menu, choose Supply Network Planning c 0nvironment c -urrent Settings c
Administration of (emand Planning and Supply Network Planning
$esult8 #he S,(P Administration screen appears
$. -hoose the Planning area icon and select Planning ob3ect structures
c. Place your cursor on Planning ob3ect structures in the Name column and click the right mouse button
%. -hoose -reate planning ob3ect structure
$esult8 #he -reate planning ob3ect structure dialog bo& appears
e. Specify a name for your master planning ob3ect structure and choose 0nter
$esult8 #he S,(P Administration E -onfigure .aster Planning Ob3ect Structure screen appears
f. 0nter a longer description of your master planning ob3ect structure in the #e&t field
&. Set the SNP Planning indicator
$esult8 #he columns on the left side of the screen are filled with the relevant info ob3ects
". -hoose Activate
#. 2eturn to the S,(P Administration screen and right mouse click on the your newly created master planning ob3ect
-hoose -reate Standard SNP planning level
$esult8 #he SNP%relevant aggregates are created
Page 173 of 251
2. -reate a storage +uckets profile (only if you are not using 9ASNP:;) +y creating it, the periods in which the data is
stored in live-ache are defined
Periodicities for Planning Area
$esult8 #he .aintain Periodicity screen appears
$. Specify a name in the Storage buckets profile field
c. Set one or more of the period indicators (day, week, month, "uarter, and so on) )f you select more than one
indicator, the average of the periods selected is used
%. 0nter a start and end date
3. -reate a planning area, or use the standard planning area 9ASNP:; that is shipped with 2elease =:A )n the planning
area, the key figures are defined and the database in which they are stored is determined 6or Supply , (emand
Propagation, the key figures are always stored in time series ob3ects in live-ache
$esult8 #he S,(P Administration screen appears
$. Place your cursor on Planning areas (the top node of the tree displayed) and click the right mouse button
c. -hoose -reate planning area
$esult8 #he -reate Planning Area dialog bo& appears
%. Specify a name for the planning area, and choose your select your master planning ob3ect structure and storage
buckets profile that you previously created from the Possible 0ntries in each of the respective fields
e. 0nter a unit of measure (to display product "uantities) and then choose 0nter
f. )n the menu, choose 0dit c #ime series ob3ects
$esult8 #he key figures used to fill the characteristics for Supply , (emand Propagation are displayed
&. -hoose Save
4. )nitiali!e the planning area for a simulation version +y doing this, you create the time series ob3ects (that is, the actual
ob3ect instances) in live-ache and generate the relationships between them
$. )n the S,(P Administration screen, place your cursor on your planning area, click the right mouse button, and
choose -reate time series ob3ects
c. 0nter the planning version, and the start and end date
%. Set the /pdate master data indicator
e. -hoose 0nter
1. )nitiali!e the planning area again for a simulation version #his is necessary in order to include changes to the master
data or to determine a planning interval
$. )n the S,(P Administration screen, place your cursor on your planning area, click the right mouse button, and
choose (elete time series ob3ects
c. )n the S,(P Administration screen, place your cursor on your planning area, click the right mouse button, and
choose -reate time series ob3ects and follow the steps as described in step > (see above)
6. -reate planning book or use the standard planning book 9ASOP that is shipped with APO 2elease =:A
a. 6rom the SAP APO 0asy Access menu, choose Supply Network Planning c 0nvironment c -urrent Settings c
(esign Planning +ook
$esult8 #he S(P8 )nteractive Planning E )nitial Screen appears
$. Select the Planning book radio button, specify a name in the Planning book field, and choose -reate
c. 0nter a description for your planning book , choose your planning area from the Possible 0ntries, and choose
-ontinue
%. -hoose to insert all key figures, and then choose -ontinue
e. -hoose to insert all characteristics and then choose -ontinue
Page 174 of 251
f. -reate one or more data %iews 0nter the description for the data view, choose a time buckets profile from the
Possible 0ntries in the #+ profile )( (future) field and choose -ontinue
&. -hoose to insert all key figures (or per drag , drop, remove particular key figures from the data view), and then
choose -ontinue
". -hoose -omplete
7. 0&ecute Supply , (emand Propagation
a. 6rom the SAP APO 0asy Access menu, choose Supply Network Planning c Planning c Sales , Operations
Planning (SOP)
$. (ouble%click on a data view of the planning book
c. )n the shuffler, choose APO location product
%. -hoose 0nter
e. (ouble%click on a location product in the list
f. As the restriction, enter a value of the key figure 9A#S.*:SW) (fi&ed storage demand)
&. As the demand, enter a value in the key figure 9A#S.*:*6O (forecast) in a later period
#his action actually e&ecutes propagation Only the deliverable portion from the storage location (fi&ed demand) is
confirmed
". -hoose Save to transfer the values from this simulation in interactive planning to live-ache
Aggregated Planning
Aggregated planning in Supply Network Planning (SNP) supports planning scenarios in which you carry out heuristic% or
opti$i6ation%base# planning at header location product level of a location product hierarchy 1ou then disaggregate the
planning result to the individual sub products of this two%level hierarchy 1ou might want to use this type of planning to8
)mprove performance
Simplify the planning process
Simplify the supply chain model to be planned (option of planning large models)
.ake planning decisions at aggregated level (for e&ample, selecting sources of supply, considering capacities, or
defining lot si!es)
After the SNP planning run and SNP #isaggregation, you can display and change the data in interactive Supply Network
Planning 1ou can also display the resource consumption at header product and sub product level and run capacity leveling
for the resources of the sub products in the capacity view of interactive planning
Prere*uisites
See Prere:uisites for Aggregate# Planning
Process
An e&ample of a process for aggregated planning is given below )t is assumed for this process that you are planning
interactively 6rom the SAP 0asy Access screen, choose Supply Network Planning @ Planning @ )nteractive Supply Network
Planning (all +ooks) #hen choose planning book 9ASNPACC2 and data view SNPACC2(;) 6or more information about
interactive Supply Network Planning, see 0nteractive Supply Netork Planning ,esktop
1ou can also run the SNP heuristic, SNP optimi!er, and SNP disaggregation in the background 1ou can then view and
change the results in interactive Supply Network Planning
1. Aggregated Safety Stock Planning
1ou carry out safety stock planning based on aggregated data #his process step is optional 6or more information, see
Aggregate# Safety Stock Planning
2. Single.(e%el Supply and Demand apping
1ou e&ecute a single%level assignment of distribution receipts and demands at sub product level #his process step is
optional An assignment at sub product level can prevent the system from making incorrect assignments at header
product level at a later time
6or more information, see Single%"evel Supply an# ,e$an# Mapping
3. Aggregation of Demand Data
)n the interactive SNP shuffler, you select the header location product for which you want to carry out planning #he
aggregated demand values for the header location product are then displayed in the demand key figures, such as
6orecast or -ustomer 2e"uirements #he demand values of the sub products are automatically aggregated to a total
value for the header product in these key figures (depending on the aggregation indicator$ see Prere:uisites for
Page 175 of 251
Aggregate# Planning) #he values remain at sub product level, which means, if you choose a sub product, the value for
this product is displayed in the key figure 6urthermore, a macro aggregates the opening stock for the header location
product and displays it in the initial column of the Stock on 5and key figure
)f the unit of measure of the sub products differs from that of the header product, the system converts the product unit of
measure into the header product unit of measure during aggregation
4. SNP Planning $un at Aggregated (e%el
1ou perform an SNP heuristic or optimi!ation run for the header location product #he header location product planning
results are then stored and displayed in the ,istribution +eceipt 2Planne#3, ,istribution ,e$an# 2Planne#3, Production
(Planned) and (ependent (emand key figures
+efore creating new orders during the planning run, the system first deletes all the planned orders from outside of the
SNP production hori!on and e&tended SNP production hori!on, and all SNP stock transfers outside of the SNP stock
transfer hori!on that were created but not fi&ed in previous planning runs )t deletes the orders at header product level
and at sub product level (depending on the setting in SNP -ustomi!ing$ see Prere:uisites for Aggregate# Planning)
5. Disaggregation of Planning Data
1ou perform SNP disaggregation for the header location product #hat means you disaggregate the planning result for
the header location product over the sub products 6or more information, see SNP ,isaggregation
After disaggregation, the system transfers the aggregated values to the Aggregated (istribution 2eceipt or Aggregated
(istribution (emand (Planned) key figures and to the Aggregated Production (Planned) or Aggregated (ependent
(emand key figures #o display the values, select the header location product #he disaggregated values for the sub
products are displayed in the non%aggregated key figures, such as (istribution 2eceipt (Planned), and so on 6or this,
select a sub product )n addition, you can display and change the individual orders for the sub products of the header
product in the detail view for the aggregated values
6. Display of $esource #onsumption
1ou can display the effects of planning on resource consumption in the capacity view of interactive planning 5ere, you
can drill down the header location product and display the resource consumption for this product in the upper table
#he resource consumption at header location product level is the total of the resource consumption of the sub products
and the resource consumption of the header product #hat way you can see the resource consumption at header
product level before and after SNP disaggregation #he prere"uisite for this is that you are using a resource hierarchy or
the same resource at header product and sub product level
)n the lower table, you can also display the product "uantities for all PP.s or P(Ss that belong to the selected header
location product and use the selected resource 6or this, choose (isplay dependent ob3ects and then choose
PP.4P(S
7. #apacity (e%eling
)f necessary, you can then run capacity leveling for the resources of the sub products
6or more information, see Capacity "eveling
8. #hange Data at Header (e%el
)f you want to change the data for specific header location products after an aggregated SNP planning run and
disaggregation, you can run aggregation again for the planned orders and stock transfer orders created by SNP
Afterwards, you can disaggregate the changed data again
6or more information, see SNP Aggregation
Prere*uisites for Aggregated Planning
#o e&ecute aggregate# planning in Supply Network Planning (SNP), you have to fulfill the following prere"uisites8
1ou have made the master data settings and any other settings necessary for e&ecuting the SNP heuristic or the SNP
optimi!er 6or more information, see 2unning the 5euristic in the +ackground and 2unning the Optimi!er in the
+ackground
1ou have also defined the master data appropriately for aggregated planning 6or more information, see .aster (ata
Setup for Aggregated Planning
6or aggregated planning and planning ith aggregate# resources, there is the standard planning book 9ASNPACC2
with data views SNPACC2(;) and SNPACC2(<) based on the standard planning area 9ASNP:< #his planning area
and planning book contain the key figures re"uired for aggregated planning and the assignment of key figure attributes,
such as the Aggregation indicator and the key figure functions 9::; to 9:<F #he Aggregationindicator specifies whether
the aggregated value or the normal value is calculated and displayed at header location product level in a key figure
#his indicator also controls whether the value is kept or deleted at sub product level after aggregation
Page 176 of 251
5owever, you can also use the standard planning area and planning book as a basis for creating your own planning
area and planning book 6or more information, see Planning Area Administration and Planning +ook
)f you use the standard planning area 9ASNP:<, standard hierarchy structures are already assigned to it #hey form the
basis for the hierarchies that you create yourself 5owever, you can also create your own hierarchy structures for
location products, resources, and production process models (PP.s) or production data structures (P(S), and assign
them to the planning area you are using (Aggregated Planning tab page) 6or more information, see .aster (ata
Setup for Aggregated Planning and 5ierarchy
Standard planning book 9ASNPACC2 also contains au&iliary key figure N0#(. that SNP disaggregation uses as a
basis for determining product demand #he system uses macro Net 2e"uirements ((isaggregation)to calculate the net
re"uirements at sub product level that are stored in this key figure and takes into account the stock on hand )t ignores
the demand from previous periods (shown in the Supply Shortage key figure) and only considers the demand starting
with the period containing the value to be disaggregated
)f you wish to calculate product demand differently for SNP disaggregation, you can also create your own demand key
figure for the planning book as an au&iliary key figure and use a macro to define your calculation formula Assign key
figure function 9:;: (Aggr Planning8 (isaggregation (emand) to this key figure 6or more information, see Planning
+ook .aintenance and Advanced .acro Structures
1ou have specified (elete at sub location product levelin the Aggr8 Old Orders field in -ustomi!ing for SNP under +asic
Settings .aintain Clobal SNP Settings (this is only valid for the e&ample process described in Aggregated Planning
See step >)
)f you want to use or#er groups, you must also have specified /se order group in the Agg8 Order Croup field #he
system considers the order group during aggregation and disaggregation 1ou can also use the order group after
disaggregating data from header to sub product level to determine the connectivity between the orders at header and
sub product level, as well as between the individual orders at sub product level, for e&ample
1ou have released the forecast data from demand planning ((P) or from an O*#P system to the level of the sub
products in SNP #he planning data must be available at sub product level for aggregated planning 6or more
information, see 2elease of 6orecast (ata
Aggregated Safety Stock Planning
)n aggregate# planning in Supply Network Planning (SNP), you can e&ecute safety stock planning on the basis of aggregated
data as a preliminary step to actual SNP planning Since safety stock planning occurs at header location product level, all
necessary data such as master, demand, and historical data must also be available at this level 1ou can have the system
automatically aggregate some of this data from sublevel to header level, or you can provide the data at header level yourself
#he following describes which data you can have the system aggregate and which settings you need to make 6or more
information about safety stock planning in SNP, see Safety Stock Planning
Prere*uisites
1ou have made the general settings re"uired for e&ecuting safety stock planning in SNP 6or more information, see
Standard Safety Stock Planning and 0&tended Safety Stock Planning
Since safety stock planning occurs at location product level, you have created a location product hierarchy 6or more
information, see .aster (ata Setup for Aggregated Planning
1ou use the standard planning book 9ASNPACC2 intended for aggregated planning, or your own planning book based
on it
)f you want to use other safety stock methods in addition to the standard safety stock methods S+, SX, and S., you
have added two live-ache time series key figures for the planned safety stock and the safety daysO supply to the
planning book 6or more information, see SAP Note JDJG9>
Features
Standard Safety Stock Planning
6or standard safety stock planning at aggregated level, the system a can aggregate master data and demand data as
follows8
Safety stock and safety daysE supply8 1ou define this data either time%independent in the location product master data
or time%dependent in interactive SNP planning
)n the master data of the location product hierarchy, you can define at header location product level that the system
automatically aggregates the data from the sub location product level to the header location product level (Agg
ProcS(S and Agg ProcS6# fields) Barious procedures are available for aggregation, such as average and total
Page 177 of 251
So that the time%dependent data can be automatically aggregated, it has to be saved in time series key figures in
live-ache Aggregation is only temporary, meaning the aggregated data is not saved permanently
#he aggregated data is only available for the SNP planning procedures SNP heuristic and SNP optimi!er, and for the
SNP mode of -apable%to%.atch planning (-#.) Production planning and detailed scheduling (PP4(S) and the PP4(S
mode of -#. planning cannot access the data 6or these applications, you must provide the data at header location
product level manually
Demand data8 #he demand data is used by the safety stock methods based on the safety daysO supply (SX, S., .X,
and ..) 1ou provide this data in an order key figure in live-ache
)n the planning area on the Ley 6igures tab page, you can specify that the data saved in the key figure is automatically
aggregated from the sub location product level to the header location product level 6or this, specify either value 5 or 7
in the Aggregation field
Safety stock methods &SFT methods'8 #he system cannot automatically aggregate this master data, meaning you
must define it for the header location product
)f you want to plan at both aggregated level and detailed level in an SNP planning process, you should define the S6#
methods identically at both levels )f you only want to plan at aggregated level, it is not necessary to do so, since the
system then only considers the data of the header location product
01tended Safety Stock Planning
6or e&tended safety stock planning at aggregated level, the system can aggregate demand forecast data and historical data
as follows8
Demand forecast data8 1ou provide the demand forecast data in an order key figure in live-ache
)n the planning area on the Ley 6igures tab page, you can specify that the data saved in the key figure is automatically
aggregated from the sub location product level to the header location product level 6or this, specify either value 5 or 7
in the Aggregation field
Historical data8 1ou provide the historical demand data and the historical replenishment lead time (2*#) data in
live-ache in time series key figures
)n the master data of the location product hierarchy, you can define at header location product level that the system
automatically aggregates the data from the sub location product level to the header location product level (5ist2*# (ata
and 5ist(mnd (ata fields)
Aggregation occurs by adding the demand forecasts 4 actual demands period by period or by finding the average of the
2*# forecasts 4 actual 2*# period by period
(ocation product master data8 #he system cannot automatically aggregate the master data delivery service level,
target daysO supply, forecast error, or S6# methods #his means that you have to define them for the header location
product
Acti%ities
1. 1ou e&ecute standard or e&tended safety stock planning as described in Standard Safety Stock Planning or
0&tended Safety Stock Planning #he system saves the results for standard safety stock planning in an au&iliary key
figure (for e&ample, SA6#1) and, for e&tended safety stock planning, in a live-ache time series key figure (for e&ample,
9ASA60#1)
2. 1ou then e&ecute an SNP, -#., or PP4(S planning run at aggregated level #he system uses the safety stock data it
calculated or that you provided as a basis for planning and creates planned orders and stock transfers accordingly for
covering the planned safety stock re"uirement
6or more information, see Aggregated Planning
3. 1ou e&ecute SNP disaggregation in which the orders are disaggregated from header location product level back to sub
location product level 6or more information, see SNP (isaggregation
)t is not possible to disaggregate the calculated safety stock values directly 5owever, this is not necessary because the
safety stock planning results only enter SNP planning at header level as entry information
Single.(e%el Supply and Demand apping
1ou can use this function before you e&ecute aggregate# planning in Supply Network Planning (SNP) to assign receipts that
are directly assigned to a location product with a transportation lane to the corresponding demands 1ou can thus prevent
the system from assigning receipts to the wrong demands during aggregated planning, due to detailed information no longer
being available at aggregated level
Single%level mapping means that the system only considers the receipts of one level of the distribution network
Page 178 of 251
Prere*uisites
So that the system can determine the receipts and demands for assignment, it must first delete all stock transfers originating
from SNP planning runs )f you leave the default setting on the initial screen unchanged, the system automatically e&ecutes
this delete operation
5owever, you can also specify that you do not want the system to delete the SNP stock transfers for simulation purposes
#hen the system can only assign receipts that are new with respect to the previous planning situation
Features
)n SNP planning at aggregated level, the system takes the aggregated receipt and demand situation into account )f the
available receipts were not previously assigned to the corresponding demands at sub product level, the system might use
the receipt for a specific sub location product to cover the demand for another sub location product )n this case, it does not
create a new receipt that could fulfill the demand of the sub location product after disaggregation )t is possible, for e&ample,
that the receipt for a red #%shirt would fulfill the demand of a blue #%shirt
#o prevent this, you can carry out single%level assignment of receipts and demands at sub product level before aggregation
#he system first checks if the transportation lanes that are directly assigned to the location product have any receipts #hen it
creates fi&ed SNP stock transfers that are considered during the aggregated SNP planning run and cannot be deleted
Since the assignment is single%level, it may fail if the receipts are not available in the source of supply for e&ternal
procurement directly assigned to the location product
Scope of Planning
1ou can define whether the system carries out the assignment for the products you have entered in all locations or only in
selected locations of the network
Assignment Time Frame
1ou can define a hori!on for the assignment, meaning a time frame in which the system reads the receipts and demands
and assigns them to one another #he hori!on commences on the start date for assignment
1ou can also specify a time offset #hen the hori!on begins after this offset, calculated from the start date
#he system does not consider any other hori!ons, such as the SNP production hori!on or the SNP stock transfer hori!on
Aggregation (e%el
1ou can define the hierarchy level at which the system carries out the assignment #he system can thus make the
assignment at header level or at lower level or at both levels #he standard case, however, is an assignment at sub location
product level
(og
#he system automatically creates an application log #he log contains, among other things, detailed information about the
processed location products and the fi&ed SNP stock transfers that were created 6or more information, see Application
"ogs
Acti%ities
#o carry out single%level supply and demand mapping, from the SAP 0asy Access screen, choose Advanced Planning and
Optimi!ation Supply Network Planning Planning Supply Network Planning in the +ackground Single%*evel Supply
and (emand .apping
SNP Disaggregation
1ou can e&ecute this function within aggregate# planning in Supply Network Planning (SNP) )t disaggregates the results of
heuristic% or optimi!ation%based planning that you have performed at header location product level of a location product
hierarchy, to the level of the individual sub products
Features
SNP disaggregation disaggregates the planning result saved in the #istribution receipt 2planne#3, #istribution #e$an# 2planne#3,
Production (planned) or (ependent (emand key figures, to the individual sub products #he aggregated value for the header
location product is displayed in the Aggregated (istribution 2eceipt or Aggregated (istribution (emand (Planned) key
figures, and in the Aggregated Production (Planned) or Aggregated (ependent (emand key figures after disaggregation in
interactive Supply Network Planning #he disaggregated value for the individual sub products is again displayed in the non%
aggregated key figures, such as (istribution 2eceipt (Planned) and so on (when you select the individual sub product)
)f you display the detail view of the aggregated key figures with a right mouse click, you will see a list of orders that the
system created for the sub products of the header product 1ou can change this order data
Disaggregation ethods
1ou can choose between two disaggregation methods or combine both methods
Disaggregation According to Demands
Page 179 of 251
Balues are disaggregated from header product level to sub product level according to fair share distribution or push
distribution principles that are also used by deployment 'ith fair share distribution, if demand e&ceeds supply, the
system distributes the supply evenly over the individual sub products according to their demand 'ith push distribution,
the procedure is similar but is used when supply e&ceeds demand
SNP disaggregation determines disaggregation demand$ in other words, the demand of the sub products, based on the
N0#(. au&iliary key figure or a user%defined au&iliary key figure (see Prere:uisites for Aggregate# Planning) #he system
calculates the net demand saved in the N0#(. key figure at sub product level using the Net (emand ((isaggregation)
macro, while taking the stock level changes into account )t ignores the demand from earlier periods (shown in the
Supply Shortage key figure) and only considers the demand starting with the period containing the value to be
disaggregated
Disaggregation According to Juota Arrangements
Balues are disaggregated from header product level to sub product level according to "uota arrangements that you have
defined for the sub products 1ou define these "uota arrangements either time%independent in the master data of the
product hierarchy or location product hierarchy, or time%dependent in a time series key figure 1ou specify the time
series key figure in the disaggregation settings 1ou can either use an e&isting (not yet used) key figure of your planning
area, or create a new key figure and assign it to your planning area and planning book 6or more information, see
ethod #om+ination
Select the (isaggregation According to Auota Arrangements method and specify a hori!on #he system performs
disaggregation according to demands for orders within the hori!on, and disaggregation according to "uota
arrangements for orders outside the hori!on #his is useful, for e&ample, if you have more e&act demand information for
a timeframe in the near future than for a later timeframe
Disaggregation odes
1ou can specify how the system processes the orders within a certain period (bucket) during disaggregation #he following
disaggregation modes are available8
Period.)ased &)ucket.Oriented' Disaggregation
'ithin one period, the system adds up all order "uantities from orders at header product level that have the same
source of supply, and disaggregates this total "uantity to the sub products )n so doing, the system applies the minimum
lot si!es and the rounding values to the total "uantity of one period
Order.)ased Disaggregation
#he system disaggregates each order that e&ists at header product level to the sub products )t applies the minimum lot
si!es and rounding values to the order "uantity of each individual order
'hen creating orders at sub product level, the order%based disaggregation mode creates a uni"ue reference to the
original order at header product level #his reference is represented by the order group number 1ou can see this
number in the detailed display for the orders in interactive planning and use it to understand the correlation between the
orders 6or this you must have specified in -ustomi!ing for SNP that you want the system to use the order group (see
Prere"uisites for Aggregated Planning)
1ou can change the order group number for an order and thus assign the order to another order group (ata such as
the fi&ing indicator and availability date4time are automatically ad3usted to the data of the order group
Scope of Planning
1ou can e&ecute location or network disaggregation
Network disaggregationC #he value stored at header product level is automatically disaggregated at all locations in the
distribution network where the chosen header product and sub products e&ist
(ocation disaggregationC #he value stored at header product level is only disaggregated at the selected locations for
the selected products
)f you have #eter$ine# the lo%level co#es before e&ecuting network or location disaggregation, the system automatically
processes the locations in a specific se"uence, so that it can correctly determine the disaggregation demand #he
system begins with the final location of the supply chain where the demand e&ists at sub product level (a distribution
center, for e&ample)
Disaggregation Time Frame
1ou can define a special disaggregation hori!on, meaning a timeframe in which the system reads the aggregated orders at
header product level and creates the disaggregated orders at sub product level #he hori!on commences on the start date
for disaggregation
*ike the SNP heuristic and SNP optimi!er, SNP disaggregation also considers the following SNP hori!ons of the header
location product8
SNP pro#uction hori6on
Page 180 of 251
-&ten#e# SNP Pro#uction .ori6on
SNP stock transfer hori6on
6or this reason, you should always run SNP disaggregation on the same day as the SNP (heuristic or optimi!er) planning
run Otherwise, the receipts generated in the planning run could be moved to hori!ons in which the system can no longer
disaggregate them An e&ception is if you enter (or use a user e&it to specify) a start date for disaggregation )n this instance,
the hori!ons are not taken into account during disaggregation
Delete Orders at Header (e%el
1ou can configure how you want the system proceed after disaggregation with the orders at header location product level
#his refers to the values saved in the (istribution 2eceipt or (istribution (emand (planned) and Production (planned) or
(ependent (emand key figures 1ou can specify that the system deletes, reduces, or does not change the orders Note the
following8
$educeC #he system reduces the orders at header product level by the total of disaggregated orders at sub product
level in the respective period #here might be a remainder if you have defined different rounding values or minimum lot
si!es for the sub products and header product in the product master data (see Master ,ata Setup for Aggregate#
Planning) #his remainder is then displayed in the (istribution 2eceipt or (istribution (emand (Planned) and Production
(Planned) or (ependent (emand key figures in interactive planning
Do not changeC #he values saved in the (istribution 2eceipt or (istribution (emand (planned) and Production
(planned) or (ependent (emand key figures are retained #he system takes these values into account when it
calculates the total receipt4demand, thus calculating them twice #his can cause problems when the data is processed
further$ in other locations, for e&ample
#he system deletes or reduces the orders in the disaggregation hori!on 1ou should mainly use the option of retaining
the orders for simulation purposes
(og
)f you run SNP disaggregation in the background, the system generates an application log )t contains, among other things,
detailed information about the disaggregated planned orders and stock transfers 6or more information, see Application
"ogs
Acti%ities
1ou can e&ecute SNP disaggregation both in interactive SNP and as a background 3ob #o e&ecute it in interactive planning,
select *ocation (isaggregation Network (isaggregationin planning book 9ASNPACC2 and data view SNPACC2(;)
#o make the settings, choose with "uick info )nitScreen for ((is%)Aggr
#o e&ecute it in the background, from the S%P &asy %ccess screen, choose Supply Network Planning @ Planning Supply
Network Planning in the +ackground SNP (isaggregation
SNP Aggregation
1ou can use this function after aggregate# planning in Supply Network Planning (SNP) and subse"uent SNP #isaggregation to
aggregate the created stock transfers and planned orders back to header level #his is useful if you want to make changes
for specific location products at header level, for e&ample Afterward, you perform disaggregation again
#his function can be used for SNP planned orders and stock transfers 5owever, it cannot be used for stock transfers and
planned orders of type Subcontracting, scheduling agreement delivery schedule lines, or SNP product substitution orders
Features
Aggregation Procedures
(epending on whether the orders have an or#er group nu$ber or not, the system applies the following aggregation
procedures8
Orders with order group num+er
#he system pools the orders according to their order groups and aggregates all suborders of an order group to one
header order of the same order group #he prere"uisite is that you have defined the use of order groups in -ustomi!ing
for SNP (see Prere:uisites for Aggregate# Planning) #he order group number for the orders is displayed in the detail view
of interactive planning
Orders without order group num+er
)f the orders do not have an order group number (because you have specified in -ustomi!ing that you are not using
order groups or the orders in "uestion were not created by SNP), the system pools them according to period and source
of supply
After aggregation, you can change the header order and use SNP disaggregation to disaggregate the changes back to
the suborders )f you want to ensure that the system again considers the reference created by the order group during
Page 181 of 251
disaggregation as well, choose the order%oriented disaggregation mode )f you have carried out aggregation according to
periods and sources of supply, you can create the parallelism by choosing period%based (bucket%oriented)
disaggregation 'or more information a(out disaggregation modes) see SNP ,isaggregation.
(uring aggregation, the system considers the lot si!es defined for the header location product, as long as they do not
inhibit aggregation Otherwise, the system ignores the lot si!es #his is the case, for e&ample, if the "uantity at sublevel
is ;J:, but the lot si!e at header level is ;::
Scope of Planning
1ou can e&ecute location or network aggregation8
Network aggregationC #he system aggregates the orders for the selected products in all locations of the distribution
network in which the products e&ist #he processing se"uence is based on the logic used in the SNP network heuristic
(ocation aggregationC #he system only aggregates the orders for the selected products in the selected locations
#o make specific changes, for e&ample, you can even apply aggregation on 3ust one specific header location product
Aggregation Timeframe
1ou can define a special aggregation hori!on, meaning a timeframe in which the system reads the aggregated orders at sub
product level and creates the aggregated orders at header product level #he hori!on commences on the aggregation start
date
1ou can also specify a time offset #hen the hori!on begins after this offset, calculated from the start date
Delete Orders at Su+le%el
1ou can define what the system is to do after aggregation with the orders at sublevel8 delete them or not change them #he
default setting is delete )f you specify that you do not want the system to change the orders, it will copy them during
aggregation 1ou should only use this setting for simulation purposes because the order "uantities and the resource
consumption are doubled
#he system deletes the orders in the aggregation hori!on
(og
)f you run SNP aggregation in the background, the system generates an application log )t contains, among other things,
detailed information about the aggregated planned orders and stock transfers 6or more information, see Application "ogs
Acti%ities
1ou can e&ecute SNP aggregation in both interactive Supply Network Planning and as a background 3ob #o e&ecute it in
interactive planning, select *ocAgg for location aggregation or NetwAgg for network aggregation in planning book
9ASNPACC2 and data view SNPACC2(;) #o make the settings, choose with "uick info )nitScreen for ((is%)Aggr
#o e&ecute it in the background, from the S%P &asy %ccess screen, choose Supply Network Planning Planning Supply
Network Planning in the +ackground SNP Aggregation
Planning with Aggregated $esources
)n this Supply Network Planning (SNP) planning process, you carry out heuristic%based or optimi!ation%based planning at
aggregated resource level, that is at header resource level of a resource hierarchy 1ou then disaggregate the result to the
subresources #his enables you to use resources evenly and achieve better performance
1ou can use the following process variants8
1ou e&ecute an SNP heuristic run with source determination at the lower le%el of a hierarchy for production process
models (PP.s) or production data structures (P(S) 1ou then run capacity leveling in which the system aggregates the
orders from the subresources to the header resource of a resource hierarchy and levels the header resource 6inally,
you disaggregate the result back to the subresources
1ou e&ecute an SNP heuristic run or optimi!ation run with source determination at header le%el of a PP. or P(S
hierarchy )f you carried out heuristic%based planning, it is necessary to run capacity leveling to level the header
resource 6inally, you disaggregate the result back to the subresources
)n addition, you can use the resource hierarchy to determine alternative resources for overloaded resources during
capacity leveling 6or more information, see Consi#eration of Alternative +esources
Prere*uisites
#he process has the following general prere"uisites 6or the specific prere"uisites for each planning step, see the respective
sections in the SNP documentation under Process8
1ou have created a resource hierarchy and a PP. or P(S hierarchy that is consistent with the resource hierarchy 1ou
have assigned the hierarchies to the supply chain model you are using
Page 182 of 251
#he header and sub PP.s of the PP.4P(S hierarchy should be defined for the same product Otherwise the product
might be changed during resource disaggregation
Standard hierarchy structures for resources and PP.s are already assigned to the standard planning area 9ASNP:<
1ou can create hierarchies based on these structures )n SNP -ustomi!ing, you can also create your own hierarchy
structures and assign them to the planning area you are using A standard hierarchy structure is also predefined for a
P(S hierarchy 5owever, it is not assigned to the standard planning area 9ASNP:<, so you have to assign it to your
own planning area
6or more information about creating hierarchy structures, see the )mplementation Cuide ().C) under Advanced
Planning and Optimi!ation .aster (ata 5ierarchy (efine 5ierarchy Structure 6or more information about
creating hierarchies, see the hierarchy section in the SAP APO master data documentation
6or planning with aggregated resources and for aggregate# planning, there is the standard planning book 9ASNPACC2
with data views SNPACC2(;) and SNPACC2(<) based on the standard planning area 9ASNP:< 5owever, you can
also use the standard planning area and planning book as a basis for creating your own planning area and planning
book 6or more information, see Planning Area A#$inistration and Planning Book
Process
Process "ariant 5
1. 1ou perform e&tended safety stock planning with source determination at the lower level of the PP. or P(S hierarchy
#his process step is optional
6or this, specify Only Sublevel in the Source (etermination field in the safety stock planning profile
6or more information, see 0&tended Safety Stock Planning
2. 1ou e&ecute a heuristic run in the background On the initial screen for e&ecuting the heuristic in the background,
choose Only Sublevel in the Source (etermination field
6or more information, see 2unning the 5euristic in the +ackground
3. 1ou perform capacity leveling at header resource level )f you perform heuristic%based capacity leveling, you have two
options8
#he system aggregates all orders of subresources at header level
6or this, set the .anual Parameter Selection and 2aise Orders to 5eader *evel indicators on the initial screen for
e&ecuting capacity leveling in the background
#he system only aggregates orders to header level that need to be moved so that overloads can be remedied
6or this, do not set the 2aise Orders to 5eader *evelindicator
Optimi!ation%based capacity leveling always aggregates all orders to header level 6or more information, see -apacity
*eveling
4. 1ou e&ecute resource disaggregation 6or more information, see +esource ,isaggregation
Process "ariant 7
1. 1ou perform e&tended safety stock planning with source determination at the header level of the PP. or P(S hierarchy
#his process step is optional
6or this, specify Only 5eader *evel in the Source (etermination field in the safety stock planning profile
6or more information, see 0&tended Safety Stock Planning
2. 1ou e&ecute a heuristic run or optimi!ation run in the background On the initial screen for e&ecuting the heuristic or the
optimi!er in the background, choose Only 5eader *evel in the Source (etermination field
6or more information, see 2unning the 5euristic in the +ackground or 2unning the Optimi!er in the +ackground
3. )f you have e&ecuted a heuristic run, also perform capacity leveling at header resource level 6or more information, see
-apacity *eveling
4. 1ou e&ecute resource disaggregation 6or more information, see 2esource (isaggregation
$esource Disaggregation
1ou can use this function in planning ith aggregate# resources to disaggregate the resource consumption from the header
resource to the subresources of a resource hierarchy #he system disaggregates the e&isting planned orders that cause the
resource consumption of the header resource to new orders that consume the subresources
1ou can e&ecute this function interactively and in the background, each for one header resource )f you select more than one
header resource, the system processes them one at a time
Page 183 of 251
Prere*uisites
#o prevent overloading the subresources, the capacity of the header resource should be e"ual to or less than the total
capacity of the subresources 6urthermore, the resource consumption of the header production process models (PP.s) or
header production data structures (P(S) should be e"ual to or greater than the resource consumption of the sub
PP.s4P(Ss
Features
)n resource disaggregation, the system assumes that the availability dates4times and the total "uantity of the newly created
orders for the subresources must be identical to those of the e&isting order for the header resource )t can therefore only
make decisions regarding the following aspects8
Number of new orders
Order "uantities of the new orders, whereby the total of the individual "uantities must be the same as the total "uantity
of the header order
Source of supply, whereby the system must use the subresources of the processed header resource
)f the system determines the source of supply, it makes the decisions regarding the subresource and the resource
consumption
Disaggregation ethods
#he following methods are available for resource disaggregation8
inimum $esource #onsumption
#he goal of this method is to keep the resource consumption of the subresources as low as possible #he system proceeds
as follows8
1. 6or each header order, the system determines the respective sub PP.s or sub P(Ss of the PP.4P(S hierarchy used
2. #he system sorts the PP.s or P(Ss according to their priority
+y default, the priority is based on which PP. or P(S can produce the greatest "uantity without overloading the
resource (dynamic priority) 1ou can also use the +Ad) 4SAPAPO4S(P?()SAC20S to specify the following additional
prioriti!ation logics8
.ethod S0#?P2)O?#1P08 1ou can define that the priority is based on the lowest resource consumption (static
priority)
.ethod P2)O2)#)X0?PP.8 1ou can define your own prioriti!ation logic
3. #he system determines the subresources for the sub PP.4P(S with the highest priority #he system uses the available
capacity of the subresource and the capacity consumption of the order "uantity to be disaggregated to calculate the
ma&imum order "uantity possible without overloading the resource )t then creates the orders as follows8
)f the ma&imum order "uantity is greater than or e"ual to the "uantity to be disaggregated, the system creates an
order with this PP. or P(S and the "uantity to be disaggregated
)f the ma&imum order "uantity is less than the "uantity to be disaggregated, the system creates an order with this
PP. or P(S and the ma&imum order "uantity #he system then continues with the PP.s or P(Ss successively
that have ne&t highest priority and disaggregates the rest of the order "uantity
4. )f all the subresources are completely utili!ed and there is still a "uantity remaining, the system repeats the process
starting with the first PP. or P(S #his leads to an overload of the respective subresource 1ou can minimi!e the risk of
an overload by fulfilling the prere"uisites for this function (see Prere"uisites section) 5owever, since the system does
not take fi&ed resource consumption into account, resource overloads can still occur
#he system ensures that the orders are distributed among the subresources according to their capacity utili!ation by
taking the available capacity into account during source determination #hat means that it prefers a resource with low
utili!ation An order split only occurs if the entire order "uantity overloads the selected resource or the ma&imum lot si!e
of the selected PP.s4P(S is less than the order "uantity
)ADI
1ou can use the method ()SACC20CA#0 of +Ad) 4SAPAPO4S(P?()SAC20S to implement your own disaggregation
method
Disaggregation Time Frame
1ou can define a special disaggregation hori!on, meaning a time frame in which the system reads the aggregated orders at
header resource level and creates the disaggregated orders at sublevel #he hori!on commences on the start date for
disaggregation
Page 184 of 251
Delete Orders at Header (e%el
1ou can define what the system is to do with the orders at header level after disaggregation8 delete them or not change
them #he default setting is delete )f you specify that you do not want the system to change the orders, it will copy them
during disaggregation 1ou should only use this setting for simulation purposes because the order "uantities and the
resource consumption are then doubled
#he system deletes the orders in the disaggregation hori!on
/se Order =roups
#he orders the system creates at subresource level receive the same or#er group nu$ber as the respective header order
#his way you can see the connection between the orders in the detail view of interactive SNP planning #o be able to display
the order group number, you must have specified the use of order groups in -ustomi!ing for SNP under +asic Settings
.aintain Clobal SNP Settings
(og
)f you run resource disaggregation in the background, the system generates an application log #he log contains, among
other things, detailed information about the processed resources and the orders that were created 6or more information, see
Application "ogs
Acti%ities
1ou can e&ecute SNP disaggregation both in interactive SNP and as a background 3ob #o e&ecute disaggregation in
interactive planning, choose 2esource (isaggregation in the planning book 9ASNPACC2 and data view SNPACC2(<)
#o make the settings, choose )nitScreen for 2esource (is
#o e&ecute disaggregation in the background, from the S%P &asy %ccess screen, choose Supply Network Planning Planning
Supply Network Planning in the +ackground 2esource (isaggregation
Product Interchangea+ility in Supply Network Planning
)n Supply Network Planning (SNP), both heuristic%base# and opti$i6ation%base# planning take into account the
interchangeability of products 1ou can use product interchangeability in the Supply Network Planning run to transfer
demands for a product that is to be discontinued onto a successor product for instance, or to use e&isting stock of a current
product to fulfill demand for the successor product
SNP supports the following product interchangeability methods8
Pro#uct #iscontinuation
Supersession chain
SNP supports the following different supersession chain types8
A%Q+S%Q-
A%Q+%QA (for promotions, for e&ample)
A%Q+%Q-%Q(%QA%Q+%Q-%Q( (when products are changed on a seasonal basis, for e&ample)
#he arrows here indicate the #irection of interchangeability for the products Products can be forward interchangeable (%
Q) or fully interchangeable (S%Q)
For$%fit%function class 2FFF Class3
6or more information about these types of product interchangeability, see the Supersession Chain and For$%Fit%Function
Class 2FFF Class3 sections in the cross%application documentation about product interchangeability in SAP APO
1ou have to use the standard SNP planning book called 9ASNP?PS with data view P2O(?S/+S# to be able to take
product interchangeability into account in Supply Network Planning #his planning book contains the re"uired key figures
Substitution (emand and Substitution 2eceipt, and an adapted macro (that takes these key figures into account) for
calculating the stock balance 5owever, you can also create your own planning book based on this standard planning book
Integration
Product interchangeability in SNP is a fully integrated part of the entire SAP APO product interchangeability process 6or
more information about this process, see the product interchangeability documentation in Product )nterchangeability for
instance
#he SNP planned orders and stock transfers generated during planning are transferred to a connected SAP 24= system
5owever, the SNP pro#uct substitution or#ers that are also generated and linked to these orders are not transferred,
with the result that the product substitution data is not visible in the SAP 24= system during Supply Network Planning
5owever, SNP product substitution data can also be integrated with SAP 24= using Production Planning and (etailed
Scheduling (PP4(S) 6or more information about this, see 24= )ntegration of Planned Orders with )nterchangeable
-omponents
Page 185 of 251
Product substitutions for #istribution #e$an#s cannot be transferred to the SAP 24= system #herefore, product
interchangeability should not be used for distribution demands
Prere*uisites
1ou have activated product interchangeability in SNP -ustomi!ing, .aintain Clobal SNP Settings (the SNP8 (eact )n-
indicator)
1ou have created the master data for running the SNP heuristic or the SNP optimi!er and have made the re"uired
settings for these planning runs 6or more information, see 2unning the 5euristic in the +ackground or 2unning
the Optimi!er in the +ackground
1ou have defined the product substitution data in the master data for product interchangeability$ that is, you have
created an interchangeability group (choose .aster (ata @ .aintain )nterchangeability Croup) and have assigned this
group to your model (choose .aster (ata @ Assign )nterchangeability Croup to a .odel) Note the following8
1ou can choose Supersession -hain or 666 -lass as the interchangeability group type for SNP (product discontinuation
is created as a supersession chain with only one discontinuation step) SNP does not support group type 2estricted
interchangeability for 666 classes Nor does it support rules
#he interchangeability group always has to be created at the location where there is e&isting demand
6or more information about maintaining master data, see the following product interchangeability documentation8
Supersession -hain, -reate )nterchangeability Croup, 6orm%6it%6unction -lass (666 -lass), and Cenerating
666 Subsets from 666 -lasses
)f you wish to run product interchangeability in the background, you have set the Add products from supersession chains
in the functions that you use to run the heuristic or the optimi!er in the background All products of a supersession chain
are then included in the selection and planned
)f you do not set the indicator, the system does transfer the demand to a successor product by creating product
substitution orders, but it does not plan the receipt for the successor product Note that this type of planning does not
provide correct results for the entire supply chain, since the system does not plan all products in the supersession chain
Features
#he different types of product interchangeability in SNP are described below8
Discontinuation of Products &A.M)'
A product (A) is superseded by a successor product (+) on a specific date (uring the planning run, all demands that
e&ist for this product are transferred to the successor product from this date onwards (defined as the Balid%from (ate in
the product interchangeability master data) 1ou can specify that you first want to use up e&isting stock of product A by
setting the /se%/p indicator for this product in the product interchangeability master data 1ou can also specify a date
by which the stock of A has to be used up
)f the system detects demand for A during the planning run and determines that A is no longer valid, it creates a receipt
(SNP pro#uct substitution or#er) for A in the Substitution 2eceipt key figure to compensate for the demand for A #he
system also creates a demand for + in the Substitution (emand key figure to transfer the demand onto + (emand for +
is then fulfilled as usual during the planning run (by creating an SNP planned order in the Production (Planned) key
figure, for instance) )f you have set the /se%/p indicator for A, any remaining stock of A is used to fulfill demand for A,
even after the discontinuation date, until the stock is used up or until the specified use%up date is reached
Supersession #hain &A.M)N.M#I for instance'
A product (A) is superseded by a successor product (+) on a specific date (uring the planning run, the system transfers
demands for A to + from this date onwards 5owever, demands for + cannot be transferred to A since A was assigned
the interchangeability direction 6orward interchangeable Product + is then to be superseded by product - at a later
date (emands for + will be transferred to - from this date onwards As the direction of interchangeability 6ully
interchangeable was defined for +, re"uirements for - can also be covered by surplus warehouse stock for +
#o replace A with +, the system proceeds as described in the (iscontinuation of Products section above )f the system
detects that there is demand for + and that + is no longer valid, it creates a substitution receipt for + to compensate for
the demand for + and a substitution demand for - to transfer the demand onto - )f the system detects demand for -
and had determined beforehand that there was still surplus stock of +, it creates a substitution receipt for - and a
substitution demand for + /ntil the use%up date, the system uses the surplus stock of + for covering demand + first
Only if stock of + is still available afterwards does the system also cover demand of -
Form.Fit.Function #lass &FFF #lass'
(ifferent products with almost identical technical properties are grouped into 666 classes and 666 subsets (on a
location%specific basis) )t is only possible to procure the product that is labeled as the leading product of the 666 subset
)n SNP, all demands that e&ist for the other products of the 666 subset are transferred onto the leading product )f there
is insufficient stock of the leading product, stock is used of the other products from the 666 subset #he leading product
will be procured (that is, produced in%house or procured e&ternally) only if none of the products have sufficient stock
Page 186 of 251
)f the system detects demand for any product other than the leading product and there is insufficient stock of this
product, it creates a substitution receipt for this product to compensate for the demand and a substitution demand for the
leading product to transfer the demand onto this leading product
Interchangea+ility with the SNP OptimiGer
)n addition to the details given above, the following information applies specifically to interchangeability with the SNP
optimi!er
#he optimi!erOs decisions are based on the costs defined for the supply chain model (storage, transportation, production,
and procurement costs) )t always finds the most cost%effective solution
#he optimi!er does not calculate costs for interchanging products at the same location
)n contrast to the heuristic, the optimi!er does not consider the product in one location only, but in all locations of the
model
#he following e&ample shows the effect of this on product interchangeability8
Product A is to be superseded by product + in location - #here is no remaining stock of product A at location - )f
demand is received for product A, the heuristic would transfer the demand to product + 5owever, the optimi!er checks
whether there is any stock of product A in other locations of the model 6or instance, if there is still sufficient stock at
location (, the optimi!er checks the costs for transferring the stock of product A from location ( to location - )f this is
the most cost%effective solution (because storage costs at ( are higher than the costs for transporting to -, for e&ample),
the optimi!er plans the stock transfer from ( to - #he demand for product A is then covered by the transferred stock
Acti%ities
1. 0&ecute an SNP heuristic or optimi!ation run in the background for the products to be planned /se standard planning
book 9ASNP?PS with data view P2O(?S/+S# or your own planning book that you based on the standard planning
book 1ou can only use the location heuristic for the heuristic run #he network heuristic is not available )f you set the
Add products from supersession chains indicator (see above), you only have to select one product from the
interchangeability group and the other products will be included in planning automatically
)f you run the location heuristic ort he optmi!er in interactive planning, the system also plans all products of the
supersession chain automatically in the correct se"uence
6or more information, see 2unning the 5euristic in the +ackground and 2unning the Optimi!er in the +ackground
2. #he system takes into account the product substitution data that has been defined for product interchangeability in the
master data and, alongside SNP planned orders and stock transfers, creates SNP product substitution orders in the
Substitution (emand and Substitution 2eceipt key figures if re"uired
3. Biew the results in interactive Supply Network Planning #he following display options are available for product
interchangeability in addition to the usual display options8
Shuffler 8 1ou can choose the Product )nterchangeability Croup characteristic in the shuffler and display all the
location products, products, or locations for a particular interchangeability group
#he (isplay dependent ob3ects function8 1ou can use this function to display the demands for predecessor or
successor products, for instance
)n the Stock on 5and key figure, stock of a product that is no longer valid and may no longer be used is highlighted
in color
#he predecessor and successor products are displayed in the detail view #he product you selected in the selection
area for planning or displaying data is highlighted in color
$!8 Integration of Planned Orders with Interchangea+le #omponents
Planned orders that you create in Supply Network Planning (SNP) can be transferred to SAP 24= Product substitution
orders, on the other hand, are not integrated with SAP 24= #herefore, any product substitutions that you plan for an
assembly with interchangeable components are not visible in SAP 24= 5owever, the substitute components have to be
contained in the planned order by the time of order processing in SAP 24= at the latest Only Production Planning and
(etailed Scheduling (PP4(S) provides the necessary functions for including substitute components in a planned order with
interchangeable components #herefore, if you wish to integrate product substitutions with SAP 24=, you have to use PP4(S
Note that PP4(S does not support manufacturer part number management (666 classes) at component level
Acti%ities
(ecide which of the following two cases applies to you and then perform the activities described8
Bou are already using SNP and PP!DS together and are using PP4(S to plan on a more detailed basis after SNP has
been run )n this instance, after Supply Network Planning has been run, you generate PP4(S planned orders that you
integrate into SAP 24= +efore transferring the planned orders to SAP 24=, use the relevant PP4(S functions to update
the planned order components #his ensures that the substitutes are also visible in SAP 24= 6or more information, see8
Page 187 of 251
Pro#uct 0nterchangeability in SNP%PP<,S 0ntegration
Pro#uct 0nterchangeability ith Or#er Processing in SAP +<>
Bou ha%e not used PP!DS as of yetI but would like to integrate product substitutions with SAP 24= )n this instance,
follow this procedure8
Set up the PP4(S master data, including PP4(S PP.s and resources, for instance #he master data settings that
you make for PP4(S have to be identical to those for SNP
)n SNP, plan on a multilevel basis (with all components included)
-onvert the SNP planned orders into PP4(S planned orders
)n PP4(S, adopt the substitute components into the PP4(S planned orders
#ransfer the PP4(S planned orders to SAP 24=
6or more information about steps c, d, and e, see the documentation in the above links
Su+contracting with Source (ocation in SNP
Subcontracting involves the procurement of a product from a supplier (the subcontractor) to whom the procuring entity
provides components for the purpose
A screw manufacturer makes screws in his plant 5owever, an e&ternal service provider E a subcontractor, packs the screws
#he screws are sent to the latter, who duly packs them and returns the packed screws to the screw manufacturer
)n planning with a source location, an SNP planned order is generated for the supplier (source location) who acts as a
subcontractor (uring the manufacture of the screws, the subcontracting component _packaging` is managed from the legal
and cost standpoints as part of the manufacturerOs stock on hand 'hen the goods receipt against the PO is recorded for the
packed screws, the screw manufacturerOs consumption of the subcontracting component is also posted
1ou can make use of this scenario if you work with several subcontractors or if you allow both in%house manufacture and
procurement on a subcontracting basis for a product
Only one plant per subcontractor is currently supported (for each product) in SAP APO #his means that always only
one plant can order from one subcontractor and the subcontracting components (materials4components provided to the
subcontractor) can only come from the plant to which the ordered product is supplied )f you have modeled several
plants per subcontractor in SAP 24=, you can transfer these relationships to the SAP S-. system via APO%-)6 (SAP
APO -ore )nterface) #hey are then represented as one%to%one relationships between subcontractors and plants in SAP
APO 6or more information, see *ocation #ype Subcontractor
)n SNP, the heuristic%base# and opti$i6ation%base# planning approaches are available for the subcontracting
process #he planning procedures #eploy$ent, transport loa# buil#ing (#*+), and capacity leveling are not possible
Page 188 of 251
Prere*uisites
#he system plans in the source location if a location%specific product master record e&ists for the ordered product (for
e&ample, packed screws)
)f the master record for the ordered product is created retrospectively, stock inconsistencies may arise
A report is available to correct this error 6urther information is available in SAP Note D>>;F;
Data in the SAP $!8 System
#he following data must have been created in the SAP 24= system and transferred to the SAP S-. system via APO -)6
(SAP APO Core 0nterface)8
The end &finished' product. #he procurement indicator 6 for e&ternal procurement must have been set in order for the
source determination facility to be able to find the subcontractor
The su+contracting components +elonging to the end product. #he procurement indicator 6 for e&ternal
procurement must have been set in order for the source determination facility to be able to find the subcontractor
#he supplier who is to manufacture the end product as subcontractor
A purchasing info record of the category subcontracting which documents the subcontractor as the source of supply of
the end product
)f necessary, an SNP pro#uction #ata structure 2SNP%P,S3, if you are using this instead of a pro#uction process $o#el
2PPM3 and wish to generate it from SAP 24= data (see also Pro#uction ,ata Structure in SNP)
Integration odel
#he integration model of the APO -)6 with which you wish to transfer your data from the SAP 24= system to the SAP S-.
system must contain all the above%mentioned data
)f you are using an SNP P(S and wish to generate it from SAP 24= data, you must choose the option SNP Subcontracting in
the integration model )n this case, all master data in the subcontractor location, such as the product master data and the
transportation lane from plant to subcontractor, is automatically created in the SAP S-. system
6or more information, see 0ntegration of Master an# !ransaction ,ata
Data and Settings in the SAP S# System
#he following data and settings must e&ist in the SAP S-. system8
01ternal procurement relationships and transportation lanes
6rom the purchasing info records, the SAP S-. system automatically generates an e&ternal procure$ent relationship of
the category subcontracting for the finished product and a transportation lane from subcontractor (source location) to
plant (#estination location) #his transportation lane is assigned to the e&ternal procurement relationship for the end
product
SeeC !ransportation "ane and Auto$atic Creation of !ransportation "anes
Transportation lanes from plant to su+contractor
)f you are using an SNP PP., you must manually create a transportation lane from the plant (source location) to the
subcontractor (destination location) for all components that are to be provided by the plant )f you are using an SNP P(S
generated from SAP 24= data, this step does not apply
(ocation of type su+contractor
#his is only re"uired, if the subcontractor processes the same product for multiple plants )n this case, you must
manually create a location of the type subcontractor for each plant%vendor combination
eans of Transport
1ou must maintain the means of transport for all relevant transportation lanes
Product master in the su+contractor location
)f you are using an SNP PP., you must create the finished product and all components in the subcontractor location
and assign them to model ::: )f you are using an SNP P(S, this step does not apply
Production process model
1ou create an SNP PP. for the end product and assign it to model ::: 1ou specify the subcontractor location as the
planning location )n doing so, note that the transportation lot si!e defined in the transportation lane and the production
lot si!e specified in the PP. should be identical )f this is not the case, the system takes the transportation lot si!e into
account
)f you are using an SNP P(S, this step does not apply See alsoC Pro#uction Process Mo#el
Transfer to SAP $!8 system
Page 189 of 251
1ou must make the relevant settings in -ustomi!ing so that SNP orders can be transferred to the SAP 24= system #o
do so, choose SAP Advanced Planning and Optimi!ation %Q Supply -hain Planning %Q Supply Network Planning %Q
+asic Settings %Q -onfigure #ransfer to O*#P Systems Note the following8 )f you have set No #ransfer, the orders will
not be transferred, even if you have made a different setting at the Supply -hain Planning interface for SAP APO
Further settings
1ou must also take into account the prere"uisites set out in the documents +unning the .euristic in the Backgroun#
und +unning the Opti$i6er in the Backgroun# #he following special aspect applies to optimi!ation%based planning8
Only either the transportation capacity or the production capacity should represent a constraint for planning 6or the
SNP Optimi!er, production and transportation represent a coherent unit
Process
1. $elease of the Demand Plan to Supply Network Planning
1ou release the demand plan from (emand Planning to Supply Network Planning See also8 +elease of the ,e$an#
Plan to SNP
2. 01ecute a multile%el heuristic or an optimiGation run
#o plan the subcontracting, you can use the standard planning book 9ASNPS+- with the data view
S/+-ON#2A-#)NC )t contains the key figures specific to the subcontracting
1ou e&ecute a multilevel heuristic or an optimi!ation run for the end product #he SAP S# system carries out the
following activities at the su+contractor location8
)t generates the following for the end product8
An SNP planned order of the category subcontracting containing the PP. for the end product as the source of
supply
An SNP stock transfer of the category subcontracting containing the plant as the destination location
On the basis of the SNP PP., it plans the su+contracting components for the SNP planned order and carries out
a source determination process there )f a transportation lane from the plant to the subcontractor e&ists, the system
creates stock transfer reservations, specifying the subcontractor location as the destination, for the subcontracting
components in the plant #hese are transferred to SAP 24=
6ollowing the -)6 transfer, a purchase re"uisition is created for the end product in the SAP $!8 system )t contains the
components for the end product
See alsoC +unning the .euristic in the Backgroun#, +unning the Opti$i6er in the Backgroun#, Source ,eter$ination in
Supply Netork Planning
3. #on%ersion of $!8 purchase re*uisition for end product
1ou convert the 24= re"uisition of the category subcontracting for the end product into a purchase order 1ou make the
conversion in the SAP 24= system #hrough the conversion, the SNP stock transfer is deleted in SAP APO and the PO
created
See alsoC Converting Purchase +e:uisitions
4. Sending the su+contracting components to the %endor
)f you work with .2P areas for subcontractors in the SAP 24= system, the following processes take place in the
latter system8 a delivery is created for the stock transfer reservation, picking takes place for this delivery, and a
goods issue is posted #he subcontracting components are transferred from plant stock to the stock of material
provided to the vendor (subcontracting stock4stock with subcontractor) Since the delivery is not .2P%relevant, it
does not appear in the SAP S-. system
)f you do not work with .2P areas for subcontractors in the SAP 24= system, the subcontracting components are
transferred directly from `plant stock` to `stock of material provided to vendor`
)n each case, `stock of material provided to vendor` shows a plus and `plant stock` is reduced
5. Posting the goods receipt for the end product
1ou post the goods receipt for the end product in the SAP 24= system )n the SAP S-. system, the PO "uantity is reduced
by the "uantity of the goods receipt #he system increases the unrestricted%use stock for the end product
At the same time the goods receipt is posted, the goods issue for the subcontracting components provided to the
subcontractor is posted #he _stock of material provided to the vendor` is reduced accordingly
Su+contracting with Third.Party Pro%ision of #omponents in SNP
#he functionality for the third%party provision of components enables the components of a product that is to be manufactured
by a subcontractor to be provided by an e&ternal supplier instead of your own plant
Page 190 of 251
6or e&ample, a firm sells handheld devices in the /SA 5owever, it does not manufacture them itself, but has the entire
production carried out by a subcontractor in Asia #he components for the handheld device, such as the housing, and so on,
are procured from an e&ternal supplier who is likewise located in Asia
)n the normal form of subcontracting, the Asian supplier would deliver the components to the plant in the /SA #he latter
would then send them back to Asia E to the subcontractor #o avoid this unnecessary detour, the supplier can send the
components directly to the subcontractor
See alsoC Subcontracting ith Source "ocation
#hrough third%party provision of materials in e&ternal procurement, you can now replicate this process in the SAP system
)n the SAP S-. system, you must manually create a transportation lane for the components that are to be procured
e&ternally between the supplier who is to provide the components (start location) and the subcontractor (destination location)
who is to manufacture the handheld devices #he transportation lane must reference the e&ternal procurement relationship )f
you are using an SNP production data structure generated from SAP 24= data, this step does not apply (see below)
)f an SNP stock transfer is created for the end product in the subcontractor location, a purchase re"uisition is generated from
it in the SAP 24= system after the -)6 transfer #his automatically contains the address of the subcontractor in Asia (not that
of the plant in the /SA) as the delivery address At the same time, the Subcontracting Bendor indicator is set #he delivery
address in the re"uisition is adopted in the PO during the document conversion process 'hen a goods receipt is posted
against such a purchase order, the components of the handheld device are automatically posted to the _stock of material
provided to vendor` (stock with subcontractor)
)n SNP, the heuristic%based and optimi!ation%based planning approaches are available for the subcontracting process
#he planning procedures deployment, transport load building (#*+), and capacity leveling are not possible
Prere*uisites
)usiness partners in%ol%ed $epresentation in SAP $!8 $epresentation in SAP APO
-ustomer Plant4*ocation *ocation % type plant ;::;
Bendor Bendor *ocation % type vendor ;:;;
Subcontractor Bendor *ocation % type vendor ;:;;
Data in the SAP $!8 System
#he following data must have been created in the SAP 24= system and transferred to the SAP S-. system via APO -)6
(SAP APO Core 0nterface)8
#he end product
#he components to be provided to manufacture the end product
#he supplier who is to manufacture the end product as subcontractor
A purchasing info record of the category subcontracting which documents the subcontractor as the source of supply of
the end product
)f necessary, an SNP pro#uction #ata structure 2SNP%P,S3, if you are using this instead of a pro#uction process $o#el
2PPM3 and wish to generate it from SAP 24= data (see also Pro#uction ,ata Structure in SNP)
Page 191 of 251
Integration odel
#he integration model of the SAP APO Core 0nterface (APO -)6) with which you wish to transfer your data from the SAP 24=
system to the SAP S-. system must contain all the above%mentioned data
)f you are using an SNP P(S and wish to generate it from SAP 24= data, you must choose the option SNP Subcontracting in
the integration model )n this case, all master data in the subcontractor location, such as the product master data and the
transportation lane from plant to subcontractor, is automatically created in the SAP S-. system
6or more information, see 0ntegration of Master an# !ransaction ,ata
Data and Settings in the SAP S# System
#he following data must e&ist in the SAP S-. system8
01ternal procurement relationships and transportation lanes
6rom the purchasing info record, the SAP S-. system automatically generates an e&ternal procure$ent relationship of
the category subcontracting for the end product, and a transportation lane from subcontractor (source location) to plant
(#estination location) #his transportation lane is assigned to the e&ternal procurement relationship for the end product
See alsoC !ransportation "ane and Auto$atic Creation of !ransportation "anes
Transportation lanes from plant to su+contractor
)f you are using an SNP PP., you must manually create a transportation lane from the plant (source location) to the
subcontractor (destination location) for all components that are to be provided by the plant )f you are using an SNP P(S
generated from SAP 24= data, this step does not apply
(ocation of type su+contractor
#his is only re"uired, if the subcontractor processes the same product for multiple plants )n this case, you must
manually create a location of the type subcontractor for each plant%vendor combination
eans of Transport
1ou must maintain the means of transport for all relevant transportation lanes
Product master in the su+contractor location
)f you are using an SNP PP., you must create the end product and all components in the subcontractor location and
assign them to model ::: )f you are using an SNP P(S, this step does not apply
#he procurement indicator must be set to 6 in the product master records for the end product and the components
Production process model
1ou create an SNP PP. for the end product and assign it to model ::: 1ou specify the subcontractor location as the
planning location )n doing so, note that the transportation lot si!e defined in the transportation lane and the production
lot si!e specified in the PP. should be identical )f this is not the case, the system takes the transportation lot si!e into
account
)f you are using an SNP P(S, this step does not applySee alsoC Pro#uction Process Mo#el
Transfer to SAP $!8 system
1ou must make the relevant settings in -ustomi!ing so that SNP orders can be transferred to the SAP 24= system #o
do so, choose SAP Advanced Planning and Optimi!ation %Q Supply -hain Planning %Q Supply Network Planning %Q
+asic Settings %Q -onfigure #ransfer to O*#P Systems
Note the following8 )f you have set No #ransfer, the orders will not be transferred, even if you have made a different
setting at the Supply -hain Planning interface for SAP APO
Further settings
1ou must also take into account the prere"uisites set out in the documents +unning the .euristic in the Backgroun#
und +unning the Opti$i6er in the Backgroun# #he following special aspect applies to optimi!ation%based planning8
Only either the transportation capacity or the production capacity should represent a constraint for planning 6or the
SNP Optimi!er, production and transportation represent a coherent unit
Process
1. $elease of the Demand Plan to Supply Network Planning
1ou release the demand plan from (emand Planning to Supply Network Planning
See also8 +elease of the ,e$an# Plan to SNP
2. 01ecute a multile%el heuristic or an optimiGation run
#o plan the subcontracting, you can use the standard planning book 9ASNPS+- with the data view
S/+-ON#2A-#)NC )t contains the key figures specific to the subcontracting
Page 192 of 251
1ou e&ecute a multilevel heuristic or an optimi!ation run for the end product #he SAP S# system carries out the
following activities8
In the plant
)t creates an SNP stock transfer of the type Subcontracting, containing the subcontractor location as the source
location, for the end product
At the su+contractor location
)t creates an SNP planned order of the category subcontracting containing the PP. for the end product as the
source of supply
)t creates an SNP stock transfer of the type subcontracting, containing the plant as the destination location, for the
end product
On the basis of the SNP PP., it plans the su+contracting components for the SNP planned order and carries out
a source determination process there )f a valid transportation lane from the vendor (supplier) to the subcontractor
e&ists with the corresponding info record, the system creates stock transfer reservations, specifying the
subcontractor location as the destination, for the subcontracting components in the plant
6ollowing the -)6 transfer, a purchase re"uisition is created for the end product in the SAP $!8 system )t contains the
components for the end product
See alsoC +unning the .euristic in the Backgroun#, +unning the Opti$i6er in the Backgroun#, Source ,eter$ination in
Supply Netork Planning
3. #on%ersion of $!8 purchase re*uisition for end product
1ou convert the re"uisition of the category subcontracting for the end product into a purchase order 1ou make the
conversion in the SAP 24= system #hrough the conversion, the SNP purchase re"uisition is deleted in SAP APO and
the PO created
See alsoC Converting Purchase +e:uisitions
4. #on%ersion of $!8 purchase re*uisition for su+contracting components
1ou convert the 24= re"uisition (category standard) for the subcontracting components into a purchase order #hrough
the conversion, the re"uisition is deleted in SAP APO and the PO created 'hen creating the purchase order, the
system adopts the delivery address from the re"uisition
5. Posting the goods receipt for the su+contracting components
1ou post the goods receipt for the subcontracting components in the SAP 24= System )n the material document, it is
noted that the movement type goods receipt to subcontractor%vendor is involved and the address of the subcontractor is
specified as the receiving vendor #his means that the subcontracting components are posted to stock with
subcontractor in the SAP 24= system -orrespondingly, in the SAP S-. system the open PO "uantity is reduced and
the stock of $aterial provi#e# to ven#or increased accordingly
6. Posting the goods receipt for the end product
1ou post the goods receipt for the end product in the SAP 24= system )n the SAP S-. system, the PO "uantity is
reduced by the "uantity of the goods receipt #he system increases the unrestricted%use stock for the end product
At the same time the goods receipt is posted, the goods issue for the subcontracting components provided to the
subcontractor is posted #he _stock of material provided to the vendor` is reduced accordingly
Sourcing of Forecast
-ustomers usually create characteristic combinations on the customer4product level and e&ecute a demand planning ((P)
run to arrive at a forecast #his forecast is generated at the customer4product level for a long hori!on of typically ;< to ;J
months /ntil the introduction of the sourcing process, this forecast was released to supply network planning (SNP) to carry
out mid%term planning #he release process was not influenced by material or resource constraints that e&ist in the supply
chain model #he decision about the release "uantity at each production location was predetermined before the release
process
Sourcing of forecast offers a higher level of intelligence to the sourcing process #his new function e&tends the classic SNP
supply chain to include the customer, because this is where the initial demand originates #he sourcing of customer forecast
to the production locations is carried out by an SNP planning run that is encapsulated in the sourcing process )n the current
implementation, the SNP optimi!er serves as a sourcing tool
Another aspect that impacts the sourcing process is the sourcing of sales orders Sourcing of forecast results in the creation
of forecast orders at the production locations to satisfy the customer demands +ased on the result of the sourced forecast,
the allocation situation (in global available%to promise (CA#P) product allocations) is updated to reflect the decision of the
sourcing process #he impact of this on subse"uent incoming sales orders is that the CA#P performs a check against the
_updated` allocation situation and assigns the sales order to the appropriate production location based on the most recent
Page 193 of 251
allocation situation #herefore, you achieve the sourcing of sales orders based on material and resource constraints in
addition to availability check at the production plants
Integration
Sourcing of forecast is integrated with SAP APO and the SAP 24= system )n SAP APO SNP, a product can have more than
one production location that delivers to the customers, and forecasting is traditionally carried out for these customer locations
in the (P planning area #he sourcing process introduces a new link between the (P and the SNP planning area #he
sourcing process can be invoked only through an SNP planning area #his is an inherent restriction because the sourcing
process uses the SNP optimi!er as the sourcing tool #his link specifies from which (P planning area (and from which key
figure in the (P planning area) the (P forecast data is read
)n addition, there is already a standard link between a CA#P product allocation group and a (P planning area #his link is
used to map characteristics and key figures between a CA#P allocation group and a (P planning area #he sourcing
process uses this link with standard features and without any modification
#herefore, what the sourcing process effectively creates is a three%way link between an SNP planning area, a (P planning
area, and a CA#P product allocation group
Features
Sourcing of forecast is a more accurate way of deciding from where the customer forecasts are sourced #his function allows
you to source incoming sales orders while considering the material and resource constraints #hrough the sourcing process,
you achieve what could be termed as _location%independent consumption` #his is because sales orders at production
locations can now consume forecasts originally generated at customer locations
#his new function also offers the following features8
A one%level location%independent consumption of forecasts and sales orders
-onsideration of only the sourcing%relevant transportation lanes and the corresponding location products
No need to e&plicitly release the (P forecast at the customer location to the various production locations
Forecast Determination
#he purpose of the sourcing of forecast process is to source customer forecasts created by demand planning ((P) to
possible production locations using an SNP planning tool, thereby considering material and resource constraints that e&ist
through the supply network #his sourcing decision then impacts the assignment of subse"uent incoming sales orders to the
appropriate production locations
Prere*uisites
aster Data
#he customer locations are maintained as SAP APO master data
#ransportation lanes between the source and the customer locations are maintained as SAP APO master data
All location products that take part in the sourcing have the8
Same consumption group for the same product
Necessary CA#P product allocation settings maintained
Sourcing flag set in the transportation lane master with respect to the source and target locations
#he usage for descriptive characteristics are appropriately set for all the location products that participate in the sourcing
process
Standard SNP optimi!er settings are maintained
#ustomiGing
#he ob3ect structure in the planning area of the consumption group contains all characteristics, such as the source
location and the participating customer, for the product
#he date to be checked with A#P is the material availability date (#his date will be used to update the allocation)
+Ad) 4SAPAPO4(.?S0*?.O( is activated and implemented
#he global rules%based A#P check has confirmed the desired "uantity
Now, the allocation check decides about the sourcing of the sales order to the appropriate production location #he
global rules%based part is necessary, because all sources for a customer have to be searched
#he results of sourcing from the previous planning cycle in live-ache are deleted
Process Flow
#he sourcing of forecast process results in the following8
Page 194 of 251
A customer%specific forecast at the production locations
Sourcing of sales orders, based on the forecast sourcing decision
Sourcing a customer.specific forecast
1. #ustomer forecast in DP
#he basis for the sourcing decision is the final customer%specific forecast that is planned in SAP Advanced Planner and
Optimi!er (SAP APO) (P #he characteristic combination for this step is customer, location, and product (#he customer
location has to be the same as the location in the master data)
#o set up customer%specific allocations that are consumed by sales orders from various plants and to derive the
consumed allocations for these plants (or any possible source locations attached to the customer), there must be a
characteristic for the plants inside the (P ob3ect structure
#he customer%specific forecast is accessed per bucket from its key figure inside (P for the time hori!on specified for the
sourcing process 6orecasts outside this hori!on are not considered
2. Determine the forecast organiGation
6orecast organi!ation is when the sourced forecast orders are protected from being consumed by e&isting sales orders
at the plants
Since the open forecast is sourced with the SNP optimi!er, e&isting sales orders at the plants need to be attached to
local consumption partners )f these consumption partners are not attached, the sales orders at the plants consume the
sourced forecast
#he forecast from the forecast organi!ation must be customer%specific, so that the automatic consumption process can
take place at the plants for each customerOs forecast and the sales orders #o allow customer%specific forecasts at the
plant, the following descriptive characteristics are used8
; PlantP'02LS
< ProductP.A#N2
= -ustomerPL/NN2
3. #alculate the open forecast +y using location.o%erlapping forecast consumption
#he open forecast is determined by subtracting the cumulated sales order "uantities from the customer%specific forecast
per bucket #his forecast is converted to the format of the SNP optimi!er input and is calculated for the time hori!on that
is specified for the sourcing process ()f the cumulated sales orders are greater than or e"ual to the customer%specific
open forecast, this forecast is set to !ero)
#he dates and the buckets from which to subtract the sales orders are determined by the delivery dates of the sales
orders at the customer location
4. Source the open forecasts with the SNP optimiGer
#he SNP optimi!er is used to determine the process of distributing the open forecasts to the plants
#he following factors are considered by the SNP optimi!er to source the open forecast8
Supply chain, including the customer and transportation lanes between the customer and other locations
6or the sourcing process, transportation lot si!es or rounding values at the lanes between sources and customer
are not allowed #ransport lot si!es could lead to an over%delivery in transport orders, but the sourcing process
depends on the real, transported "uantities
0&isting sales orders at the plants
#he optimi!er run results in8
2eceipts for the sales orders at the plants
New customer%specific forecast orders at the plants that represent the sourcing decision
2eceipts for the dependent re"uirements at the plants
#he forecast is now distributed to the plants
Sourcing sales orders
Sales orders can be checked against allocations in the different plants and can be distributed to the plants using rules%based
A#P (2+A) New sales orders from the SAP 24= system are allocated to plants based on the sourcing decision for the
customer%specific forecast )ncoming sales orders can be checked with rules%based CA#P against the allocation
/nconfirmed schedule lines are additional re"uirements that can be handled with backorder processing
Page 195 of 251
#alculating the Forecast
Sourcing of forecast allows customer%specific forecasts from SAP APO (P and sales orders from the SAP 24= system to be
sourced from different plants, while taking into account resource and material constraints #his function e&tends the classic
SNP supply chain and adds the customer, since this is where the initial demand originates
#his e&ample is to help you understand how sourcing of forecast works
Prere*uisites
6or a complete list of prere"uisites, see Forecast ,eter$ination
Sourcing a #ustomer.Specific Forecast
Initial situation
#he (P forecast in this e&ample is 544 pieces for customer ; and 94 pieces for customer < #here are also e&isting sales
orders of 69 pieces for customer ; and 74 pieces for customer <
#alculating the open forecast
#o calculate the open forecast, use the following e"uation8
(P forecast E cumulative sales orders P the open forecast
)n our e&ample, the open forecast totals are8
99 [;:: E (=: T ;D)\ for customer ;
84 [D: E <:\ for customer <
The optimiGer run
#he ne&t step is to perform an optimi!er run, which calculates the optimum sourcing situation 6or our e&ample, here are the
results8
Page 196 of 251
#o calculate allocation, use the following e"uation8
sourced forecast T sales orders P new allocation situation
New sales orders from the SAP 24= system are allocated to plants, based on the sourcing decision for the customer%specific
forecast
#he sourcing results depend on the cost associated with each of the production locations and the transportation lanes )f
there are capacity constraints at both plants (for e&ample, each plant can only produce DD pieces4bucket), the production
costs are the same at both plants$ the transportation costs from plant ; to customer ; and from plant < to customer < are ;
APO%U4P- +ut, the transportation costs from plant ; to customer < and from plant < to customer ; are ;: APO%U4P-
#he result of the sourcing process varies depending on the SNP optimi!er parameters (cost profile)
Sourcing Sales Orders
'hen sales orders are sourced, new sales orders from the SAP 24= system are allocated to plants based on the sourcing
decision for the customer%specific forecast
#o continue with this e&ample, in the SAP 24= system, a sales order has been created for ;4 pieces for customer ; for the
product in the sourcing process
'hen you check the availability of the "uantity with CA#P, using the allocation method, at plant ; there an open allocation of
99 pieces and at plant < there is an open allocation of 4 pieces 'hen this A#P check result is accepted, two new subitems
are created for the main item in the sales order #his step leads to two sales orders at each supplying plant in SAP APO #he
confirmed "uantity for the sales order is =: T ;D P 69
Interacti%e Supply Network Planning Desktop
#he interactive planning desktop in Supply Network Planning (SNP) is where you display both aggregated and detailed
planning information, and where you make manual modifications to your data 1ou can also e&ecute SNP planning runs
(such as optimi!ation%based or heuristic%based planning) directly from this screen
Page 197 of 251
Structure
#he interactive planning desktop has two ma3or components8 #he selector and the workspace
The Selector
#he selector is your primary tool for locating, sorting, and organi!ing information 1ou find the selector on the left of the
screen #o show4hide the selection area, in the application toolbar, choose Switch Selector On4Off #he selection area
comprises the following areas8
)nfoOb3ects (with the shuffler)
Selection Profile
(ata Biews
-omponents
InfoO+,ects
#he )nfoOb3ects area shows you all of the characteristic values for which data can be planned and viewed 0&amples of
)nfoOb3ects in Supply Network Planning are specific products, locations, resources, production process models (PP.s), or
transportation lanes 1ou populate the )nfoOb3ects area by opening the shuffler (see below) and making a selection, or by
choosing an e&isting selection from the selection profile
#he )nfoOb3ects area has a toolbar with icons representing different functions8
Icon Function
#oggle between the )nfoOb3ects area (where the selection profile is found), the data views area, the macros
area, and the overview 1ou can resi!e the areas by dragging their borders
Open the shuffler 1ou make and save new selections in the shuffler (see below)
(isplay dependent ob3ects, such as all locations for a product
Select all the characteristic values in the )nfoOb3ects area
(eselect all the characteristic values in the )nfoOb3ects area
2eturn to the previous selection
2edo the last selection
(etermine the format in which you want the characteristic values in the )nfoOb3ects area to be displayed
Show the definition of the current selection
)f you right%click one of the selected )nfoOb3ects, you will see further options, such as set or delete processing indicator 1ou
can use the processing indicator to select location products that you have already processed 1ou could then select location
products in the shuffler by processing indicators, for instance #he indicator is reset during the ne&t SNP run
The Shuffler
#he shuffler is the window in which you select the )nfoOb3ects you want to plan 1ou select the types of information fulfilling
specific conditions from dropdown bo&es in the sort statements (Show$ that fulfill the following conditions) 6or e&ample,
you might want to show all location products in version W1X for a particular SNP planner )n the shuffler, you choose8
Show that fulfill the following conditions... APO location products
APO E planning version W1X
APO SNP Planner Paul Smith
)n the shuffler, you can save selections that you intend to use fre"uently and load e&isting selections #o open the shuffler, in
the )nfoOb3ect area toolbar, choose Selection 'indow
Selection Profile
#he selection profile shows selection )(s used by the current planner #he supply chain planner uses the selection profile to
"uickly access fre"uently used selections #o add selection )(s to the selection profile, choose Selection Profile See also8
Selection Manage$ent
Data "iews
#he data views area is where the planner selects planning books and data views )f you access interactive Supply Network
Planning by selecting8 Supply Network Planning Planning )nteractive Supply Network Planning (All +ooks) from the
SAP 0asy Access screen, all planning books that are available for selection are listed in the data views area 5owever, SAP
Page 198 of 251
also provides standard planning books and data views for the different types of planning in Supply Network Planning 1ou
can choose the following ones directly from the SAP 0asy Access screen8
Interacti%e Supply Network Planning
)n interactive Supply Network Planning (from the SAP 0asy Access screen, choose Supply Network Planning @
Planning @ )nteractive Supply Network Planning), you see the standard planning book 3ASNP36 with the views
SNP36&5' . SNP Plan and SNP36&7' . #apacity #heck (capacity view) in the data views area #he planning book
SNP9> provides the standard functionality to e&ecute interactive Supply Network Planning
Sales > Operations Planning &SOP'
)n Sales , Operations Planning (from the SAP 0asy Access screen, choose Supply Network Planning Planning
Sales , Operations Planning (SOP)), you see the standard planning book 3ASOP with the views SOP&5' L SOP
(ocation ProductsI SOP&7' L (anesI SOP&8' L SOP PPI and SOP&6' L SOP $esource in the data views area 1ou
use this planning book to run SNP planning method, supply an# #e$an# propagation
Distri+ution $esource Planning &D$P'
)n (istribution 2esource Planning (from the SAP 0asy Access screen, choose Supply Network Planning Planning
(istribution 2esource Planning ((2P)), you see the standard planning book 3AD$P with the views D$P5 . D$P in the
data views area #his interface is practically identical with interactive Supply Network Planning, however here you can
also view the distribution receipts and distribution issues
Transport (oad )uilder &T()'
)n the standard planning book 3ASNP36, the #ransport *oad +uilder (from the SAP 0asy Access screen, choose Supply
Network Planning Planning #ransport *oad +uilder (#*+), or #ransport *oad +uilder on the
)nteractive Supply Network Planning screen) provides the standard interactive !ransport "oa# Buil#er planning
functionality
Interacti%e "I
)n interactive B.) (from the SAP 0asy Access screen, choose Supply Network Planning Planning B.)
)nteractive B.)), you see the standard planning book 3A"I with the view 3A"I&5' . "I in the data views area )n
addition to the typical SNP data that you can display, you also can display the values for your B.) receipts and
demands (planned, confirmed, and #*+%confirmed)
Interacti%e Scheduling Agreements
)nteractive Scheduling Agreements (from the SAP 0asy Access screen, choose Supply Network Planning Planning
Scheduling Agreements (Procurement) )nteractive Scheduling Agreements), has planning book 3ASA and view
SA&5' 1ou use this planning book to display and change all data that is relevant for sche#uling agree$ent processing
The data %iews area has a tool+ar with icons representing different functions.
Icon Function
#oggle between the )nfoOb3ects area (where the selection profile is found), the data views area, the macros
area, and the overview 1ou can resi!e the areas by dragging their borders
Set a filter on the data views that are shown in this area
(isplay only the data views you created yourself
2emove filter in order to reshow all the planning books and data views
.ake settings for data view, such as planning buckets profile and planning start
Specify a planning version for key figures for which you have defined a variable planning version as a key figure
attribute in the planning book settings )f you work with different planning versions, you can use this to compare
the planning results
-lose data views area
#omponents
#he components area shows macros that are active both for all data views in this planning book and for this data view 6or
each of these categories you see8
(irectly e&ecutable macros
1ou can e&ecute these macros by double clicking (irect e&ecution is not possible for the standard macros (that is, for
start, default, level change, or e&it macros)
Start macros
Page 199 of 251
(efault macros
*evel change macros
0&it macros
6or more information about macros, see A#vance# Macros
Toggling )etween Selections and Data "iews
1ou can toggle between different selections and data views without saving )f you do this, the data is saved temporarily and
the individual selections are locked for other users )f you choose 2efresh, the system resets the data to its last active
save status and removes the lock from the selection
Note that this only applies if you are working with SNP planning areas
The -orkspace
#he workspace is the main data display and planning area )t is on the right of the screen and consists of one or more ta+les
(depending on the planning book and data view) and a graphic +y default, only the tables are shown
Tool+ar
#he workspace has a toolbar with icons representing different functions, some of which are supported by Supply Network
Planning and (emand Planning ((P)8
Icon Function

Populate the table and4or graphic with data for the current selection

Switch to design mode

#oggle between the table and the graphic
Save graphical settings
(isplay dependent ob3ects, such as all the PP.s for a resource (in the capacity view)
Apply a standard mathematical operator or a self%defined distribution function to a value to
distribute the value across a row
Save the data currently visible in the table to an 0&cel file #he system prompts you to
enter the file name and path
Send the data currently visible in the table to another user
Show4hide4refresh alerts
Open the Alert .onitor and Notes .anagement
.aintain4show a note relating to a point in the graphic
Show one key figure, multiple key figures, or all key figures
0&ecute macros
Others are specifically for Supply Network Planning8
Icon Function
*ocation 2un location heuristics
Network 2un network heuristics
.ulti%level 2un multilevel heuristics
Optimi!er 2un the optimi!er
(eployment 2un deployment
(eployment settings .ake (or alter) your deployment settings
Drilldown Function
1ou use 5eader On4Off to access the drilldown function for the tables of the workspace 6or more information, see /sing
the .ea#er in 0nteractive Planning
Page 200 of 251
)f you navigate using the drill down function or the (isplay (ependent Ob3ects function, you can save the navigation
path for future work 2ight click Save Navigation Path in the top left cell of the planning table 1ou can also temporarily
deactivate navigation path, or delete it again
Detail "iew
)f you right%click on a cell in the table and select (isplay (etails (or call up the detail view with a double click), an e&tra table
is displayed showing the order details for the selected cell #his table shows the individual orders and includes information
about "uantity, source of supply, and the order availability or demand date 1ou can also set the fi&ing indicator in this table
(see Or#er Fi&ing), change the "uantity, date, and time of orders, and assign alternative sources of supply to orders Note
that an order may move to a different period if you change the date and time #his may also mean that the order disappears
from the current (cell%based) detail view
#he standard display of fields changes according to the type of order, that is, depending on whether it is a planned order, a
stock transfer, or a planned independent re"uirement 1ou can design the layout of the display yourself and show or hide
specific fields #he detail view also has sorting, filtering and search options for your orders
PersonaliGed Settings
)f you choose .aintain /ser Settings from the menu bar, you can personali!e your settings for the interactive planning
desktop 1ou can define settings, such as showing and hiding specific key figures, for certain planning books, data views,
and selections 6or more information, see the relevant help documentation (choose )nformation)
)f you want to personali!e settings, from the SAP 0asy Access screen, choose /ser Settings for )nteractive Planning
Data "iew Design Functions
#o create your own design for a data view in a planning book, you can use the following functions 1ou access these
functions by choosing (esign mode in interactive planning
Acti%ities
Ta+le
-lick on the top left cell with the right mouse button to pull down a conte&t menu with the following functions #hese functions
apply to the table as a whole
To #hoose this function
/se enhanced scroll functions that scroll by several lines4once at once, thus improving
performance
Navigation bar

Switch the position of rows and columns Switch columns4rows
(isplay the same periods in the table and the graphic 'hen you scroll in the table the
graphic moves correspondingly
1ou must have enabled the navigation bar to use this function
Synchroni!e table4graphic
Alter the width of columns and the height of rows (if you have enabled this function) 0nable resi!e
Biew column and row headings in a three%dimensional display =( display
0nhance performance
1ou can use this option if you entered a planning buckets profile for history in the planning
book
)f you do not select this function, the historical periods in which data cannot be changed are
grayed out #his graying out costs system performance 1ou select this function to prevent
the graying out of unchangeable periods #he periods themselves remain changeable 1ou
receive a system message if you try to change them
5ide display of history
-hange the color of the gridlines in the table Crid color
(isplay a graphic by default when you open the interactive planning screen Craphic
5ide rows in this view or show hidden rows .anage hidden rows
$ows
-lick on a row heading with the right mouse button to pull down a conte&t menu with the following functions for individual
rows and selected rows
To #hoose this function
(elete the current row (elete row
-ancel the grouping of rows of which this row is the master row (see -ancel grouping
Page 201 of 251
the e&planation of Croup below)
5ide the selected row (to show it again, use the .anage hidden rows
function e&plained above)
5ide
(elete the selected row from this view (elete
(efine the selected row so that can data can be displayed in it, but
not changed
Output only
-ancel the Output only function for the selected row )nput4output
(efine the fill%in color of the selected row
+ackground color
Note8 )t is not possible to change the color of rows
that are Output only
(efine the color of the font in the selected row
6oreground color
Note8 )t is not possible to change the color of rows
that are Output only
-hange the number of decimal places displayed for the selected
row
(ecimal places
Prefi& a row heading with an icon (the icon does not affect the way
data is managed in the system)
)cons
(elete the icon that is attached to the heading of the selected row (elete icons
Set the standard row height for the selected row (efault row height
Set the standard row width for the selected row (efault row width
Set the standard row attributes for the selected row (efault row attributes
Show the selected row in the graphic Show in graphic
5ide the selected row in the graphic 5ide in graphic
Croup together the selected rows (at least two) behind a master row
#he planner can e&pand and collapse the grouping by clicking on the
0&pand and -ollapse icons in the interactive planning table
Croup
#olumns
-lick on a column heading with the right mouse button to be able to set the standard column width and4or the standard
column height #hese functions apply to the selected columns
)t is not possible to move columns to different positions in the grid, even if you first switch the position of rows and columns
Application Tool+ar
To Select this push+utton
-reate a planning book -reate planning book
-hange a planning book (for e&ample, by adding a new view) -hange planning book
(efine that the table or the graphic or both appear by default when you open the planning
book and view (you can still switch between the two interactively)
*ayout
(efine whether the table and graphic are displayed side by side or with the table above
the graphic (this setting can be different for different grids)
*ayout
Personali!e the interactive planning toolbar (this function is active if one or more of the
Supply Network Planning applications were selected when the planning book was
created)
#oolbar
Show4hide e&isting icons in rows )cons
Ta+le Tool+ar
To #hoose
2eturn to live mode, first saving the current design -hange live4design mode
Save the current design of the graphic (you must choose this function if you have
made changes to the graphic but not to the table design$ for e&ample, if you have
changed the color setting of a line in the graphic)
Save graphic setting
(efine macros for all the views in a planning book .acro+uilder PQ Planning book
Page 202 of 251
To #hoose
(efine macros for one data view .acro+uilder PQ (ata view
=raphic
See Functions of the 5raphic in 0nteractive Planning
$eturning to Interacti%e Planning
#o return to interactive planning, choose A dialog bo& appears in which you can decide whether to save
individual ob3ects or all changes Alternatively you can e&it without changing (in this case choose -ontinue without saving)
/sing the Header in Interacti%e Planning
#he header tells you which version and which characteristic values you are planning, as defined in the info ob3ects area )n
addition, you can set up a toolbar in the header to drill up and down in the data, to scroll through multiple values of a
characteristic, and to view the both the total and the details of all key figures and characteristic values on one screen
Prere*uisites
1ou have made a selection
Features
/se the header8
)n combination with the info ob3ects area in the selector to navigate in multiple characteristics
)n a self%defined data view, not in one of the standard data views (statistical forecasting, multiple linear regression,
composite forecasting, or promotion planning) #his restriction is not relevant to SNP
Acti%ities
#o use the header you must do two things8
1. -onfigure the header
2. Show the header
#onfiguring the Header
1. -hoose Settings c 5eader information
2. 0nter the characteristics in the order in which you wish to see them and number this se"uence
3. )f you do not number the characteristics, your entries are lost
4. Specify for each characteristic whether you wish to see its values as te&ts (for e&ample, (istribution center North%0ast)
or as )( numbers ((-?:::;?N0)
5. )f you wish to be able to drill down, scroll, and navigate between total and details, select .odif for each characteristic )f
you wish the header to have a display character only, do not select .odif
6. -hoose Adopt
Showing the Header
1. )n the application toolbar, choose 5eader on4off
2. )n the header toolbar, show the characteristic values currently selected in the info ob3ects area by choosing
-orking with Headers
6or each characteristic for which you have made an entry and set the .odif indicator there are four buttons on the top of the
screen8
#he short description of the characteristic
An arrow up and an arrow down with which you navigate up and down the list of values
A pull%down down in which the current selection is displayed )f you open the bo&, you can select a value directly, display
all the values % (etails (all), or the #otal (aggregated) value
Order Fi1ing
)n interactive planning, you can fi& and unfi& orders 6i&ing an order means that the order cannot be changed or deleted in
the ne&t Supply Network Planning run (heuristic or optimi!ation) or during capacity leveling (depending on the capacity
leveling parameter settings)
Page 203 of 251
Acti%ities
#o fi& or unfi& orders, you can choose one of the following options8
1. 1ou set or delete the fi&ing indicator in the detail view (see the (etail Biew section in the interactive planning desktop)
2. 1ou select a row (key figure) and a column (period) in the table (using the shift and control key), position the cursor over
the corresponding key figure, use the right%hand mouse button, and choose8 Selected Area (Orders) 6i&4/nfi& Orders
1ou can also fi& or unfi& orders in a range of periods #o do this, ne&t to the row, select the start and end period of the
range in which you want to fi& or unfi& the orders and then choose the menu path mentioned above All e&isting orders
within this range will be fi&ed or unfi&ed 5owever, it is possible for you to create additional orders within this range
1ou can also fi& or unfi& the orders for several location products and periods at the same time #o do this, you use the
#rill#on function ((etails (all)) to display the key figure data for several location products, you then select the
location products (using the Shift and -ontrol key or by choosing the left%hand column) and choose the menu path
mentioned above #o see the conte&t menu, the cursor has to be positioned over the left column (key figure) and a valid
location product row (not a totals row) 1ou can select specific periods or a range of periods )f you do not select any
periods, then all the periods are either fi&ed or unfi&ed
1ou can also select and fi& an entire range (as described above) in the capacity view by choosing with "uick info
(isplay dependent ob3ects and then choosing PP.
3. .anually created orders are normally fi&ed automatically 1ou can, however, change this setting by setting the No 6i&ing
indicator (on the SNP< tab page) in the location product master data
#hanging Orders Interacti%ely
0ntries can be made in some of the key figure fields in the interactive planning table, meaning that you can change the key
figure values and thus also the orders interactively #he same applies to the planned distribution receipt (SNP stock transfers),
the confirmed distribution demand (#eploy$ent stock transfers), planned production (planned orders), and planned safety
stock
Features
#he following options are available to you when changing orders interactively8
)f you change the confirmed distribution demand$ that is, the deployment stock transfers resulting from adeployment run,
the system checks the available%to%deploy "uantity (A#( "uantity) and informs you if there is insufficient "uantity
available
1ou have the option of moving deployment stock transfers from one transportation lane to another (isplay the
associated transportation lanes for this using the (isplay (ependent Ob3ects function in the interactive planning table
1ou have the option of moving planned orders from one bucket to another #o do this, place the cursor in a cell, use the
right%hand mouse button, and choose .ove order to buffer #hen place the cursor in the cell into which you want to
move the value and choose )nsert order from buffer 5ere, the entire order "uantity is moved to the other bucket,
meaning that it is not possible to move partial "uantities or distribute order "uantities over several buckets
1ou can move planned orders from one resource to another in the interactive Supply Network Planning capacity view
using the buffer function described above #o do this, select several resources in the shuffler, and then select (isplay
(ependent Ob3ects %Q PP. or (isplay (ependent Ob3ects %Q Products
)f there are multiple sources of supply available for one location product at the same time, you can display e&isting
orders with their sources of supply in the detail view and process them there (to do this, right%click (isplay (etail or call
up the view with a doubleclick) 1ou can also create new orders for the various sources of supply by creating a new row
in the detail screen, entering the "uantity, and selecting the source of supply 1ou can create multiple orders per source
of supply
#his applies for planned orders as well as for stock transfers
1ou can also use a macro to specifiy that, when there are multiple sources of supply per location product, the
corresponding row is not ready for input, and that this is indicated with a green marker )n this case, you can only
process orders in the detail view 6or more information, see SAP note G:>FD;
Notes anagement
/se notes to remind yourself or inform other demand planners of the reasons why the demand forecast in a particular period
at a particular level is as low or high as it is
Page 204 of 251
Features
Notes are planning area specific #his means that if you create a note for a key figure and time bucket in one planning area,
you can see this note in all planning books in this planning area provided the same key figures and time buckets e&ist in the
planning books
#he notes management screen area has a status bar and a toolbar
Status )ar
#he status bar is visible when you open the notes management screen area
Tool+ar
Note O%er%iew
1ou can call up an overview of all the notes in the planning area you can do so either
6rom planning area administration by choosing Coto Notes Overview
+y starting transaction 4SAPAPO4S(P?NO#0S
1ou can further restrict the selection to individual key figures or versions )n the notes overview you cannot change notes
Acti%ities
To Do this
Open the notes management screen
area with the status bar
-lick on a cell with the right mouse button and choose (isplay note
#he key figure and period to which the note relates are shown at the top of
the editing area
Show the notes management toolbar -hoose Biew Show4hide toolbar from the status bar
'rite a note
1. -lick on the cell with the right mouse button and choose (isplay note
2. 'rite your note
3. Save your note by choosing on the status bar
#he note is saved for the period on the level at which you created it
(rill down from a high level to a note
written at a lower level
(o this, for e&ample, if you are a
demand planner working on a high
level (eg regional level) and you
wish to see the e&planation for a
forecast made by another planner at
a lower level (eg product level)
1. -hoose (isplay note hierarchy from the status bar
#he key figure and period to which the note relates are shown in the
attribute column of the hierarchy area
2. )n the hierarchy area of the screen, choose from the -hoose charact
pull%down menu the characteristic to whose note level you want to drill
down (Scroll across the screen to see the characteristic values)
3. #o display the note for a characteristic value, click on its icon
4. #o drill down to another level, double%click on the drill%down icon and
choose another characteristic from the pull%down menu
A red traffic light beside a characteristic value indicates that you
cannot drill down any further
(ownload a note to your hard disk
1. (isplay the note
2. 6rom the toolbar, choose Save as local file
3. Save the file with the e&tension t&t
/pload a file as a note from your hard
disk
6rom the toolbar, choose *oad local file
)f you select several values of a characteristic in the shuffler and load the data for this selection, it is not possible to create
notes for the sum4aggregate value of the individual values 1ou can only create notes for the individual values Similarly if
after loading the multiple selection you then drill down on another characteristic, you cannot create notes for the individual
values #here can only be one value for each characteristic in a selection -haracteristics
Page 205 of 251
6or e&ample in the shuffler you select location :::; and :::<, and load the data )f you then try to write a note for a key
figure and time bucket, the note area appears in read%only )f you drill down in the grid on location :::;, you can create a
note 'hen you now drill up again and then drill%down on product, you cannot create notes for products that e&ist in both
locations (6or products that only e&ist in one location the selection is unambiguous and therefore a note can be created)
Distri+ution Functions
)n interactive planning, promotion planning, and forecasting you can use distribution functions in order to enter data in
multiple cells "uickly and easily #o access these functions, click in the workspace toolbar
Features
#he function distributes values over a selected period )n the function you enter a value which is the basis for the distribution
5ow this value is entered in the cells depends on the operator you assign to the value in the Operator field )n general these
operators are self%e&planatory 6or details of which operators are available use the 6> help
#he following operators re"uire e&planation8
Operato
r
01planation
PP #he value is distributed evenly over the selected period and overwrites e&isting cell values
Pa
#he value is distributed over the selected period in the same proportions as the e&isting cell values #he
e&isting values are overwritten
TP
#he value is added to the total of the selected period and distributed evenly over the cells 6or e&ample, if the
value is ;<:: and you have selected ;< monthly periods, the system adds ;:: to each cell
%P As above, but the value is subtracted from the total
Q
#he system compares the value and the value of each cell in the selected period )f the value is larger than cell
value, it is written to the cell, otherwise not
S As above, but the system overwrites the entry, if the value is less than the cell value
1ou can save series of figures in distribution patterns for future use #hese are number series that are not connected to a
period in time 1ou use the following operators in combination with a distribution pattern
Operato
r
01planation
(0
(istribution pattern8 copy
#he values are copied from the distribution pattern to the selected key figure(s)
(6
(istribution pattern8 percentage
#he figures you enter here are interpreted by the system as percentages 'hen you use the distribution pattern
in the application, the system multiplies the value you enter in the value field by this percentage and inserts it in
the relevant time bucket
(S
(istribution pattern8 normali!ed
#his is similar to the above case 5owever the system first forms the sum of all the values in the distribution
pattern and then calculates the proportion that each individual entry represents 'hen you then use the
distribution pattern in the application, the system multiplies the value you enter in the value field by this
proportion and inserts it in the relevant time bucket
Acti%ities
1ou define distribution patterns in -ustomi!ing or under (emand Planning %Q 0nvironment %Q -urrent Setting %Q .aintain
(istribution Patterns Alternatively you can edit distribution patterns from the function in the application )n this case you also
see the periods in the planning table to which the value are to be saved
#hese periods are only for your information #hey are not saved with distribution pattern 1ou can so assign the distribution
pattern to another planning book with completely different time buckets
1ou start distribution by choosing #he (istribution functions dialog bo& appears )n the top 5ori!on section you select
the periods between which the distribution function is to be used
#he lower section is in the form of a table )n the top line in which no key figure is displayed you can assign a distribution
pattern to all modifiable key figures
)n the area below you can see the modifiable key figures )f you have previously selected a key figure, you only see this key
figure 1ou enter an operator together with a value and4or a distribution pattern, depending on the operator Similarly whether
the value is an absolute value or a percentage depends on the operator
Page 206 of 251
Functions of the =raphic in Interacti%e Planning
#he graphical display in interactive planning depends on the following factors8
)t is user%specific
)t is planning book%specific
)t is data view%specific
)t can be used in any of the standard views (statistical forecast, .*2 or composite)
-lick on a graphical element with the right mouse button to pull down a conte&t menu with functions for that element #here
are conte&t menus for8
Plotting area
Cridlines
W a&is
1 a&is
#he y%a&is comes preformatted, but you change it
(ata lines (if you have selected a data line, its start and end points are marked)
#o save the design of the graphic, you must choose Save graphic setting from the table toolbar before you save the
data
(o not change the chart type #he default chart type is Scatter
#he graphic itself is a general SAP +asis function 6or detailed information see SAP Craphics (+-%60S?C2A)
+usiness Craphics /ser ,ocu$entation
Acti%ities
Toggling +etween the =raphic and the Ta+le
JC 5ow can ) toggle between the table and the graphic7
AC -lick the icon Craphic or #able
Displaying +oth the =raphic and the Ta+le
JC 5ow can ) switch from displaying either the table or the graphic, to displaying both 7
AC -hoose Craphic from the tableKs conte&t menu (to display this menu, right mouse click the top left cell of the table)
Sa%ing PersonaliGed =raphic Settings
JC 'hen ) customi!e the time a&is my customi!ing changes are not saved 'hy not7
AC -ustomi!ing changes made interactively are not saved automatically #o save them, choose before you save the
data
Scrolling
JC )s the table at the top of the screen automatically synchroni!ed with the graphic below 7 )f ) scroll to earlier 4 later periods
in the table, does the graphic automatically get scrolled as well 7
AC No, there is no automatic synchroni!ation #o scroll the graphic with the table, choose Synchroni!e table 4 graphic from
the tableKs conte&t menu (to display this menu, right mouse click the top left cell of the table)
#hanging (ine Thickness
JC 5ow can ) change the thickness of a line7
AC -arry out the following steps8
1. 2ight mouse click the line
2. -hoose 6ormat data series
3. )n the dialog bo&, choose the re"uired line thickness in the Style field
#hanging the )ackground #olor of the Historical HoriGon
JC 5ow can ) change the background color of the historical hori!on7
1. 2ight mouse click on the vertical line dividing the historical period and the forecast period
2. -hoose 6ormat Balue 2ange
3. -hoose Pattern
Page 207 of 251
4. -hoose the re"uired color from the field -olor in the 6ill bo&
#hanging the Time A1is
JC 5ow can ) change the time a&is7
1. 2ight click on the time a&is below the graphic
2. -hoose 6ormat a&is
3. On the Scale tab, deselect the checkbo& 'idth of a day if it is not already deselected
4. Specify the width of a day manually
5. (2e) select 'idth of a day
6. -lick OL
JC 5ow can ) display all the values for the time a&is on a single screen (without a scrollbar)7
1. 2ight click on the time a&is below the graphic
3. On the Scale tab, select the checkbo& to the left of 'idth of a day Alternatively, change the ma3or and the minor
units
JC -an ) change the &%a&is formatting by changing the time scale type7
AC No *eave #ime as the value a&is scale type
#hanging the "alues of Points Interacti%ely
JC 5ow can ) change the value of a point in the graphic interactively7
1. -lick on the line for which you want to change a value
#he points on the line are marked with a black bo&
2. -lick on the point whose value you want to change
3. -hange the value of the point by dragging it to the re"uired position
)nformation about the current date and time as well as the key figure value at that point appears in a small bo&
NoteC Not all values can be changed interactively 1ou cannot change values in (isplay mode or for an Output only row
/sing the (egend
JC Are changes to the legend settings saved automatically7
AC Only if you save the graphical settings by clicking before saving the data
#he default setting for the legend is Show on demand #hat means that an icon for the legend is displayed to the right of
the graphic and when this icon is selected the legend is displayed
JC 5ow can ) get the legend to display automatically7
1. 2ight mouse click the plotting area
2. -hoose -hart options
3. On the *egend tab, click the desired legend type
4. (eselect Show on demand
5. -lick OL
JC 5ow can ) print the legend7
1. 2ight mouse click the plotting area
2. -hoose -hart Options
3. -hoose *egend
4. (eselect Show on demand
5. Select a legend and press OL
6. -lick on the graphic with the right mouse button
Page 208 of 251
7. -hoose Print preview to see how the graphic will look when printed
8. -lick on the graphic with the right mouse button
9. -hoose Print
#hanging the $ange of "alues Displayed on the B A1is
JC 5ow can ) specify the ma&imum and minimum values on the 1%a&is so that ) can include all the values that interest me in
the range of values displayed7
1. 2ight click the 1 a&is
3. On the Scale tab, deselect the checkbo&es to the right of the labels .a&imum and .inimum
4. 0nter the re"uired range of values in the fields to the right of these labels
5. -lick OL
Sending the Plan
1ou can send plans via e%mail internally or e&ternally if the system is connected to a mail server #he system automatically
creates a .icrosoft 0&cel attachment containing the plan
Procedure
1. 'ith the plan you want to send displayed in the )nteractive Planning table, choose Send Plan
2. 0nter the recipients name, choose a recipient type (for e&ample, SAP user name or e&ternal address
3. 1ou also have the following options8
)ndicate a status of e&press, copy, blind copy
Add a note
Send in background
Specify no forwarding
(o not send before a specified date
After sending put in outbo&
4. -hoose Send plan
$esult
#he system automatically creates a .icrosoft 0&cel attachment containing the plan and sends it to the designated recipient
Transfer of the SNP Planning $esults
#here are various options available for transferring the results of the SNP planning run to other upstream and downstream
SAP APO applications or planning stages8
1ou can release the SNP planning results to (emand Planning ((P) to compare the SNP plan that is constraint%based
with the demand plan that is not constraint%based (see 2eleasing the Supply Network Plan to (emand Planning)
1ou can release more detailed results of an SNP optimi!ation run to (emand Planning (see 2eleasing the 2esults of an
Optimi!ation 2un to (emand Planning)
1ou can release the SNP planning results to the supply and demand propagation planning method to transfer the data
stored in order key figures to time series key figures (see 2eleasing the SNP Plan to (emand Planning)
1ou can release the planning results back to SNP if you have used the supply and demand propagation planning
method (see 2eleasing the 2esults of Supply and (emand Propagation to SNP)
1ou can convert SNP orders into PP4(S orders to transfer the planning results to Production Planning and (etailed
Scheduling (PP4(S) (see -onversion of SNP and -#. Orders into PP4(S Orders)
1ou can transfer the planning results directly to the 02P system 6or further information, see the component )ntegration
of SAP APO and the 02P System under )ntegration of #ransaction (ata
$eleasing the Supply Network Plan to Demand Planning
Page 209 of 251
1ou use this report to release the final supply network plan back to the demand planner to compare the unconstrained
demand plan with the constrained supply network plan )n addition, you also use this report if you wish to conduct Sales ,
Operations Planning
'hen you use this report, technically, you are transferring the data stored in orders to time series #his is relevant because
the data used in Sales , Operations Planning must be stored in time series As a conse"uence, you must transfer the
relevant order categories (from Supply Network Planning) to the appropriate time series key figures (to SOP)
Procedure
1. 6rom the SAP 0asy Access .enu, choose Supply Network Planning c 0nvironment c 2elease to (emand Planning
$esult8 #he (ata #ransfer8 Order Network E #ime Series screen appears
2. 1ou enter the target planning area, source planning version, and target planning version
3. 1ou specify from and #o (ates to define the beginning and end of the release hori!on
#hese dates are mandatory
4. 1ou specify a planning buckets profile
#he use of a planning buckets profile for the release from SNP to (P is optional )f you use a planning buckets profile,
the system releases the supply network plan in the buckets in which data was planned #he time frame of the planning
buckets profile must be as big as, or bigger than, the release hori!on specified in the 6rom and #o (ates
)f you do not specify a planning buckets profile, the data is read in technical periods #he storage buckets profile
determines what the technical periods are #echnical periods are not visible to the user
5. 0nter the products or range of products for which you wish to release the plan
#his setting is optional )f you do not make an entry here, all the products in the model of the specified planning version
are used
6. 0nter the locations or range of locations for which you wish to release the plan
#his setting is optional )f you do not make an entry here, all the locations in the model of the specified planning version
are used
7. 0nter the resources or range of resources for which you wish to release the plan
#his setting is optional )f you do not make an entry here, all the resources in the model of the specified planning version
are used
8. -hoose the Ley figure assignm icon to transfer the key figures to the order categories 6or more details about the key
figure assignment, see below
9. Set the *og indicator, if you wish to view the results from the release
#he transfer of data from the orders to the time series is carried out before planning begins in order to load the data from
the order categories to time series 1ou must determine which order categories (stock types) are taken into account in
SOP, and then copy them to the correct key figure
#he default settings for the key figure assignment for the SOP standard planning area 9ASNP:; are listed below
Transfer Data from Orders to Time Series
Type Source 2ey Figure Target 2ey Figure
Ley figure
copy (Any
orders whose
A#P category
is contained in
the specified
A#P category
group are
read)
A key figure with an A#P category
group, or simply an A#P category
group without a key figure E #his
is necessary for planning area
9ASNP:; (perhaps you are using
SOP) because it does not contain
any key figures stored in orders
/sing the key figure semantic,
you can decide if the re"uested or
the confirmed "uantity of the
orders is read See the following
two e&amples
Sales Orders8 A#P category (;;,
key figure semantic8 *-
re"uested "uantity from order
network
6orecasts8 A#P category group
(6;, key figure semantic8 *-
confirmed "uantity from order
9A#S.*:*SO (period E customer demand)
1ou can use any number of key figures
9A#S.*:*6O (period E forecast demand)
'hen you transfer the data to the key figures 9A#S.*:*SO and
9A#S.*:*6O, propagation is triggered automatically, and the
values are overwritten with the results from the propagation 6or that
reason, SAP recommends that you create your own planning area
that contains, in addition to the key figures for 9ASNP:;, further key
figures (stored in time series) for the location product for (emand
Planning
6irstly, you would transfer the order "uantities to the (P key figures
(as RsetR "uantity) and then copy the values to the SNP key figures
(for e&ample, via a macro) Propagation is then triggered again
automatically, and provides the confirmed "uantity in SNP key
figures
)n contrast to orders, consumption of the forecasts against, for
Page 210 of 251
network e&ample, customer demand, does not take place in the key figures
)nitial stock
#here is no default key figure
)nitial stock is read from the stock
category group in the location
master
9A#S.*:SW) (period E fi&ed storage location receipts)
1ou must have set the )nitial indicator in the Ley 6igures (etails for
the planning area #he stock "uantity that is read is written to the
initial value of the target key figure )n the interactive planning
desktop, you can see the initial values in the initial or totals column
2esource
capacity
#here is no default key figure
#he resource capacity in
live-ache is read
9A#S2::::- (period E available capacity)
Scheduling of $eceipts and Demands During $elease to DP
)n Supply Network Planning (SNP) and Production Planning and (etailed Scheduling (PP4(S), you can create receipt
elements in order live-ache, which are connected (that is, _pegged`) to demand elements using pegging 'hen you release
the SNP plan to (emand Planning ((P) you transfer these pegged demand and receipt elements from the order live-ache to
the time series live-ache #his raises the "uestion of which time series periods the system transfers the receipt elements to
Features
1ou define how the system schedules receipts and demands by specifying an Aggregation .ethod for the release #o do
this, select Advanced Planning and Optimi!ation Supply Network Planning 0nvironment 2elease to (emand
Planning from the SAP 0asy Access .enu
#he following aggregation methods are available8
/se No Scheduling (ogic &ethod 4'8 #he system does not consider pegging #he system transfers the "uantities of
the order elements (receipt or demand elements) to the periods of their availability or demand dates
/se $eceipt Periods &ethod 5'8 #he system transfers the "uantities of the order elements that are not connected by
pegging (un%pegged order elements) to the periods of their availability or demand dates )f an order element is pegged,
the system transfers its pegging :uantity to the period of the pegged receipt
/se Demand Periods &ethod 7'8 #he system transfers the "uantities of the un%pegged order elements to the periods
of their availability or demand dates )f an order element is pegged, the system transfers its pegging "uantity to the
period of the pegged demand
/se Demand!$eceipt Periods &ethod 8'8 #he system transfers the "uantities of the un%pegged order elements to the
periods of their availability or demand dates )f an order element is pegged, the system transfers its pegging "uantity for
backwards pegging (on time) to the period of the pegged demand, and for forward pegging (late) to the period of the
pegged receipt
Only /se $eceipt Periods for Pegging Juantity &ethod 6'8 #he system does not transfer "uantities of un%pegged
order elements )f an order element is pegged, the system transfers its pegging "uantity to the period of the pegged
receipt
Only /se Demand Periods Pegging Juantity &ethod 9'8 #he system does not transfer "uantities of un%pegged order
elements )f an order element is pegged, the system transfers its pegging "uantity to the period of the pegged demand
Only /se Demand!$eceipt Periods for Pegging Juantity &ethod :'8 #he system does not transfer "uantities of un%
pegged order elements )f an order element is pegged, the system transfers its pegging "uantity for backwards pegging
(on time) to the period of the pegged demand, and for forward pegging (late) to the period of the pegged receipt
01ample
#he following graphic shows an e&ample of scheduling receipts and demands
Page 211 of 251
01planation of =raphic
'hen releasing receipt and demand "uantities from order live-ache to time series live-ache, you can select a category
group that contains the order categories #o do this, assign key figures and select Ley 6igure -opy as the type in the (ata
#ransfer (etails section #he selected category group may contain only receipt categories, only demand categories, or both
category types #here are different possibilities for combinations of category groups and aggregation methods depending on
which categories are contained, #he e&ample detailed in the graphic shows the various combinations
Prere*uisites
#he selection time period for the release covers = periods
)n period ; of the order live-ache for SNP, there is a receipt with "uantity G 6rom this receipt, the system forwards the
pegging "uantity > to a demand in period < with "uantity ;D (on%time pegging) An un%pegged receipt "uantity of =
remains for the receipt in period ;
)n period =, there is a receipt with "uantity J 6rom this receipt, the system forwards the pegging "uantity F to the
demand in period < (late pegging) An un%pegged receipt "uantity of = remains for the receipt in period =
#herefore, the system forwards a total pegging "uantity of ;: to the demand in period < #here is an un%pegged demand
"uantity of D at this demand
#he type of pegging relationship (dynamic or fi&ed) is irrelevant
1ou have selected a target key figure using key figure assignment
Possible -ombinations of -ategory Croups and Aggregation .ethods
Si& of the possible combinations shown in the graphic are e&plained in the following table8
#om+ination Description
Only receipt
categories in
the category
group and
aggregation
method 5
)n period ;, the system releases the sum of pegging "uantity > of the on%time receipt and its un%
pegged "uantity = #he system saves the resulting "uantity of G in the target key figure
)n period <, the system releases no "uantity #he system saves the resulting "uantity of : in the
target key figure
)n period =, the system releases the sum of pegging "uantity F of the late receipt and its un%pegged
"uantity < #he system saves the resulting "uantity of J in the target key figure
2eceipt and
demand
categories in
the category
group and
aggregation
6or mi&ed category groups, the system calculates the result "uantity as the sum of the result "uantity for
the combination of receipt categories in the category group and aggregation method 7 and the result
"uantity for the combination of demand categories in the category group and aggregation method 7.
)n period ;, the system releases the un%pegged "uantity = of the on%time receipt #he system saves
the resulting "uantity of = in the target key figure
Page 212 of 251
method 7
)n period <, the system releases the sum of the result "uantity ;: for the combination of receipt
categories in the category group and aggregation method 7 and the result "uantity ;D for the
combination of demand categories in the category group and aggregation method 7 #he system
saves the resulting "uantity of <D in the target key figure
)n period =, the system releases the un%pegged "uantity < of the late receipt #he system saves the
resulting "uantity of < in the target key figure
Only demand
categories in
the category
group and
aggregation
method 8
)n period ;, the system releases no "uantity #he system saves the resulting "uantity of : in the
target key figure
)n period <, the system releases the sum of pegging "uantity > of the on%time receipt and the un%
pegged "uantity D of the demand #he system saves the resulting "uantity of 9 in the target key
figure
)n period =, the system releases the pegging "uantity F of the late receipt #he system saves the
resulting "uantity of F in the target key figure
Only demand
categories in
the category
group and
aggregation
method 6
)n period ;, the system releases the pegging "uantity > of the on%time receipt #he system saves the
resulting "uantity of > in the target key figure
)n period <, the system releases no "uantity #he system saves the resulting "uantity of : in the
target key figure
)n period =, the system releases the pegging "uantity F of the late receipt #he system saves the
resulting "uantity of F in the target key figure
Only receipt
categories in
the category
group and
aggregation
method 9
target key figure
)n period <, the system releases the sum of pegging "uantity > of the on%time receipt and the peggin
"uantity F of the late receipt #he system saves the resulting "uantity of ;: in the target key figure
)n period =, the system releases no "uantity #he system saves the resulting "uantity of : in the
target key figure
2eceipt and
demand
categories in
the category
group and
aggregation
method :
6or mi&ed category groups, the system calculates the resulting "uantity as the sum of the resulting
"uantity for the combination of receipt categories in the category group and aggregation method : and
the resulting "uantity for the combination of demand categories in the category group and aggregation
method :.
target key figure
)n period <, the system releases the sum of the resulting "uantity > for the combination of receipt
categories in the category group and aggregation method : and the resulting "uantity > for the
combination of demand categories in the category group and aggregation method : #he system
saves the resulting "uantity of J in the target key figure
)n period =, the system releases the sum of the resulting "uantity F for the combination of receipt
categories in the category group and aggregation method : and the resulting "uantity F for the
combination of demand categories in the category group and aggregation method : #he system
saves the resulting "uantity of ;< in the target key figure
$eleasing the $esults of an OptimiGation $un to Demand Planning
1ou use this function to release the results from an SNP optimi!ation run back to (emand Planning ((P) for comparison with
the unconstrained demand plan All the data from the sales order priority class and the forecast and B.) promotions
category types is transferred to (emand Planning +y specifying a target key figure for (emand Planning, you can write the
results from an SNP optimi!ation run to a (P key figure without overwriting the original (P information, thereby enabling
comparison and analysis
Prere*uisites
1ou must have previously performed an SNP optimi!ation run
Procedure
1. 6rom the SAP 0asy Access menu, choose Supply Network Planning @ 0nvironment @ 2elease SNP%confirmed forecast
to (emand Planning #he 2elease SNP%confirmed forecast to (emand Planning screen appears
2. )n the SNP optimi!ation run field, choose an optimi!ation run #he results from this optimi!ation run will be transferred
back to (emand Planning
Page 213 of 251
3. )n the Ley figure field, choose from which of the three key figures (9A(6-S# 6orecast, 9A(.(P; Sales Orders, or
9AP6-S# B.) Promotions) the data will be pulled
4. 0nter the products or the range of products for which you wish to release the plan
5. 0nter the locations or the range of locations for which you wish to release the plan
6. 6or (emand Planning, enter the target%planning version, planning area, master planning ob3ect structure, and target key
figure where you would like to store the optimi!ation run results
7. -hoose 0nter
$esult
1ou can then display this information for comparison on the interactive desktop in (emand Planning
$eleasing the $esults of Supply and Demand Propagation to SNP
)f you are using the supply an# #e$an# propagation planning method (from SOP) and wish to subse"uently use your planning
results in Supply Network Planning, you must transfer the data stored in time series key figures back to the appropriate order
types and categories
Procedure
1. 6rom the SAP 0asy Access .enu, choose (emand Planning @ 0nvironment @ 2elease to Supply Network Planning,
and then choose the 2elease8 0nhanced icon #he (ata #ransfer8 #ime Series E Order Network screen appears
2. 1ou enter the source planning area, source planning version and target planning version
#he planning area 9ASNP:< (the standard planning area for order%oriented planning) is used as the target planning
area #herefore, all of the specified target key figures are contained in 9ASNP:<
3. 1ou specify 6rom and #o (ates to define the beginning and end of the release hori!on #hese dates are mandatory
4. 1ou specify a planning buckets profile
#he use of a planning buckets profile for the release from (P to SNP is optional )f you use a planning buckets profile,
the system releases the demand plan in the buckets in which data was planned #he timeframe of the planning buckets
profile must be as big as, or bigger than, the release hori!on specified in the 6rom and #o dates
)f you do not enter a planning buckets profile, the data is read in technical periods #he storage buckets profile
determines what the technical periods are #echnical periods are not visible to the user
5. 0nter the products or range of products for which you wish to release the plan
#his setting is optional )f you do not make an entry here, all products in the model of the specified planning version are
used
6. 0nter the locations or range of locations for which you wish to release the plan
#his setting is optional )f you do make an entry here, all locations is the model of the specified planning version are
used
7. -hoose the Ley fig assignm icon to assign the key figures to order categories 6or more details about the key figure
assignment, see below
8. Set the *og indicator, if you wish to view the results from the release
Transfer Data from Time Series to Orders
Type Source 2ey Figure Target 2ey Figure
6orecast
9A#S.*:*6O (period E
forecast demand)
1ou can use any number
of time series key figures
9A(6-S# (forecast)
1ou must use order key figures for the location product
(characteristic 9A.A*O) with an A#P category
Production, SNP
planned
9A#S.*:PS; (period E
production receipt)
.aster product (primary demand)8 9APP2O( (planned production)
Secondary product (dependent demand)8 9A(.(S0
-o%product8 9ALP2O( (co%production)
1ou must use order key figures for the location product
(characteristic 9A.A*O) with A#P category
0&ternal
procurement, SNP
planned
9A#S.*:0:) (period E
e&ternal receipt)
9APS5)P
1ou must use the order key figure for the location product
(characteristic 9A.A*O) with A#P category
Page 214 of 251
Stock transfer, SNP
planned
9A#S.#:::O
1ou can use any key
figure from characteristic
9A.A*A
#he system determines the key figures according to the location
type
)f the target location is a customer, then the B.) conditions are
valid
)f the target location is not a customer, the key figures from the
standard planning book 9SNP9> are used
Stock transfer,
(eployment
confirmed
9A#S.#::(O
#he system determines the key figures according to the location
type
)f the target location is a customer, then the B.) conditions are
valid
)f the target location is not a customer, the key figures from the
standard planning book 9SNP9> are used

#on%ersion of SNP and #T Orders into PP!DS Orders
)n Production Planning and (etailed Scheduling (PP4(S), if you want to e&ecute detailed planning for the receipts you have
created with Supply Network Planning (SNP) or with -apable%to%.atch (-#.), you have to convert the SNP or -#. orders
into PP4(S orders (uring the conversion, the system creates PP4(S orders from the SNP or -#. orders and then deletes
the SNP4-#. orders 1ou can convert orders as follows8
1ou can e&ecute a mass conversion for all SNP or -#. orders that begin in the PP4(S hori!on or in a larger
conversion hori!on
)n interactive planning, you can specifically convert individual SNP or -#. orders within or outside the PP4(S
hori!on
1ou e&ecute the conversion within a planning version #he system takes account of the current propagation range when
creating the PP4(S orders
Prere*uisites
1ou have defined resources and sources of supply for SNP and PP4(S that are consistent with each other 6or more
information, see )ntegrating SNP and PP4(S
1ou cannot convert the following orders into PP4(S orders8
#P4BS orders
Product substitution orders in SNP
Features
1ou use a special heuristic based on the algorithm 4SAPAPO422P?SNP<PP(S for the conversion, such as the standard
heuristic SAP?SNP?SNC* #he mass conversion that you can call in the area menu for Production Planning is an e&ception
)f you have upgraded to SAP APO >:, the system performs the mass conversion using the report
4SAPAPO422P?SNP<PP(S #his report was available in SAP APO =;
Procurement Juantity #alculation
#o determine the procurement "uantities of the PP4(S orders from the receipt "uantity of an SNP or -#. order, PP4(S
performs a procurement "uantity calculation during the conversion (_lot formation`) 1ou have various options in this
situation 1ou could perform a ;8; conversion or an SNP%independent redetermination of the procurement "uantities using
the lot si!e settings from the location product master 6or more information, see Procure$ent 8uantity Calculation for SNP%
PP<,S Conversion
Source Determination
#he procedure selected determines which sources of supply PP4(S uses to create the PP4(S orders 1ou have the following
options8
PP4(S determines the sources of supply independently of SNP using automatic source determination from PP4(S
PP4(S determines the source of supply from the SNP4-#. order being converted
6or more information, see Source ,eter$ination for SNP%PP<,S Conversion
Order Status
)n the settings, you can specify the status with which you want the system to create the PP4(S orders 1ou have the
following options8
#he PP4(S orders have the status firmed output
Page 215 of 251
1ou can only make manual changes to the receipt "uantities of PP4(S orders with the status firmed output
#he system sets the conversion indicator for the PP4(S orders
After the transfer to a connected SAP 24= system, the system immediately and automatically converts planned orders
and purchase re"uisitions (whose conversion indicators are set) into manufacturing orders or purchase orders
)f you e&ecute the conversion in the active planning version :::, the system performs the conversion checks defined in
the conversion rule (such as an A#P check) before the conversion indicator is set #he system only sets the conversion
indicator if the PP4(S order passes the checks without any errors 6or more information, see Converting Or#ers
Scheduling the PP!DS Orders
)f you have set forward scheduling, the system begins at the start date4time of the first activity in the SNP4-#. order as
standard )n backward scheduling, as standard, the system begins at the end date4time of the period that contains the
availability date4time of the SNP4-#. order being converted
1ou can specify a safety time for backward scheduling )n this case, the system does not start backward scheduling at the
end of the period but at a correspondingly earlier date4time
See also
SAP note >J;9:F
Deployment
After production is complete, deployment determines which demands can be fulfilled by the e&isting supply )f there are
insufficient "uantities available to fulfill the demand or the "uantities available e&ceed the demand, deployment makes
ad3ustments to the plan created by the SNP run
#he deployment run generates #eploy$ent stock transfers based on the SNP stock transfers that were created during the
SNP run #he #ransport *oad +uilder (#*+) then uses these deployment stock transfers to create transport loads, thus
generating !"B ship$ents
1ou can run deployment from the interactive planning table in Supply Network Planning (from the SAP APO 0asy Access
menu, choose Supply Network Planning c Planning c )nteractive Supply Network Planning), or as a background 3ob (from
the SAP APO 0asy Access menu, choose Supply Network Planning c Planning c Supply Network Planning in the
+ackground cH(eployment or (eployment Optimi!ation)
Prere*uisites
1ou cannot use deployment for stock transfers involving storage location .2P areas 6or more information, see Stock
!ransfer ith Storage "ocation M+P Areas
Features
Deployment Heuristic
#he deployment heuristic creates a distribution plan for one product at one location )f the available "uantities are insufficient
to fulfill the demand, the system uses fair share rules to determine the distribution plan 5owever, if there is more supply than
is necessary to meet demands, the system uses push rules to determine the distribution plan 1ou define fair share and push
rules in the SNP deployment profile 6or more information, see ,eploy$ent .euristic
$eal.Time Deployment
#his variant of the deployment heuristic is used to e&ecute deployment based on the most recent results from the SNP run
5ere, the system considers the current demand situation at the destination locations by first e&ecuting an SNP run between
the source location and its associated destination locations before the actual deployment run
'hen using fair share rule + (see ,eploy$ent Profiles), it is particularly important that distribution is based on the most e&act
calculation of target and planned stock levels possible
Deployment OptimiGation
#he deployment optimi!er creates a distribution plan for all the products you chose in all the chosen locations of the supply
chain model )n the main, the deployment optimi!er bases its decisions on all the costs defined in the supply chain model
(such as transportation and storage costs), as does the SNP optimi!er )t also takes into account the following factors8
6air share rules and push rules
-onstraints such as transportation capacity, storage capacity, and transportation lot si!es
1ou make most of the deployment optimi!ation settings in the SNP #eploy$ent opti$i6er profile 6or more information, see
,eploy$ent Opti$i6ation
Page 216 of 251
#he deployment heuristic creates a distribution plan for one product at one location of the supply chain model Once
production is complete, the system first checks what product "uantities are actually available at the source locations
(locations where there is stock) #he sum of these product "uantities is known as the available%to%deploy (A#() "uantity #he
system then determines how the A#( "uantity is to be distributed to destination locations (locations where there is demand)
#he system considers the various distribution rules if the available product "uantities e&ceed or fall below the demand (fair
share and push rules) 1ou can set these rules in the SNP deployment profile or on the SNP < tab page of the location
product master (eployment takes into account a number of deployment hori!ons that you also define in the location product
master
Distri+ution $ulesC Fair Share $ules
)f demand e&ceeds supply, the system can use fair share rules to calculate deployment using the available%to%deploy (A#()
"uantity Barious methods use fair share rules to assign a limited amount of available product to sources of demand #he
following rules are available8
Fair Share $ule AC Proportional Distri+ution )ased on Demands
#he ob3ective of fair share rule A is to distribute the stock proportionally to all demand locations according to planned
distribution demand
Fair Share $ule )C Proportional Distri+ution )ased on Target Stock
#he ob3ective of fair share rule + is to raise the stock levels at all demand locations to appro&imately the same
percentage of target stock level #he percentage at each destination location is defined as the deployment%relevant
stock (Pstock on hand E SNP stock transfers) divided by the target stock level )f the deployment%relevant stock, is
negative the system first attempts to raise the stock level at all destination locations up to !ero #he system then
attempts to raise the stock level at all destination locations to the same target stock level percentage
Fair Share $ule #C Percentage Distri+ution )ased on Juota Arrangements
#he ob3ective of fair share rule - is to distribute the stock according to "uota arrangements at the demand locations #o
apply rule -, you have to define outbound "uota arrangements for source location products in the Supply -hain
0ngineer
Page 217 of 251
Fair Share $ule DC Distri+ution )ased on Distri+ution Priority
#he ob3ective of fair share rule ( is to distribute stock according to priorities that you defined for the outbound
transportation lanes of the source location (distribution priority) At the onset of a fair share situation, the system
attempts to fulfill all of the current dateOs demands until the A#( "uantity is e&hausted 6or e&ample, you have three
outbound transportation lanes to your destination locations (A, +, and -), each with corresponding priorities (;, <, and
=) 1our A#( "uantity is ;D: pieces and the re"uired "uantity in each location is ;:: pieces )f you choose fair share
rule (, destination location A receives a "uantity of ;:: pieces over the transportation lane with priority ; (estination
location + receives a "uantity of D: pieces over the transportation lane with priority <, and destination location -
receives nothing over the transportation lane with priority =
Push $ules
SNP only uses push rules to calculate deployment if the A#( "uantity covers the demand #he following rules are available8
Pull Distri+ution
(eployment fulfills all of the demand within the pull deployment hori!on (for definition, see below) Products are
distributed according to the due date specified at the demand locations #he system does not distribute any supply to
the demand source in advance of the demand date
Pull!Push Distri+ution
#he system immediately distributes all supply to the demand locations (ignoring the demand dates specified at the
demand locations) to fulfill all demands within the pull deployment hori!on
Push Distri+ution +y Demand
#he system immediately distributes the entire supply for the entire planning hori!on to the demand locations to fulfill all
demands #he pull deployment hori!on is ignored
Push Distri+ution +y Juota Arrangement
#he system immediately distributes the supply according to the "uota arrangements defined for the demand location
#he demand situation at destination locations is ignored
Push Distri+ution Taking the Safety Stock HoriGon into Account
#he system confirms planned issues that are to be covered by safety stock at the source location if the difference
between the demand and deploy date is smaller than the safety stock hori!on (see below) #his means, the system will
only fall below the safety stock level that you defined on the *ot Si!e tab page of the location product master if the
demand to be fulfilled is in the safety stock hori!on Note that the safety stock hori!on moves forward (rolls) with
planning
#he following e&ample illustrates the three push rules8 Pull distribution, pull4push distribution, and push distribution by
demands
Page 218 of 251
Pull distri+ution % A "uantity of <:: is distributed to the distribution centers on every day within the pull hori!on where there
does e&ist demand (four days into the future)
Pull!Push % A "uantity of <:: pieces is distributed on the first day, when supply amounts to <:: pieces On the second day,
a "uantity of F:: pieces is distributed Although supply is ;::: pieces, the demand within the pull hori!on is for only F::
pieces$ so only F:: pieces are distributed
Push distri+ution +y demands % <:: pieces are distributed on the first day when supply amounts to <:: pieces$ on the
second day, when the supply is ;:::, ;::: pieces are distributed Since the demand in the system is ;>::, all the supply
can be distributed A demand of <:: at the end of the planning hori!on is left unfulfilled due to insufficient supply within the
push hori!on )f the demand in the system had been J::, only J:: would be distributed on the second day
)f you set the Push not allowed indicator on the SNP tab page of the location master (only possible in active version), the
available supply is distributed according to the daily demand at the demand locations only
Deployment HoriGons
#he deployment heuristic takes into account the following four different deployment hori!ons (that you define on the SNP<
tab page of the location product master)8
Pull deployment horiGon8 #his hori!on refers to the period of time over which deployment takes into account the
planned distribution demand #he hori!on starts from todayOs date
(uring the deployment run, the system attempts to fulfill all distribution demands within this hori!on (istribution begins
on the first day for which distribution demands e&ist in the system and ends on the last day of the pull deployment
hori!on
#he pull deployment hori!on is also used during push distribution )n this instance, it specifies whether the demand is to
be fulfilled immediately (pull4push distribution) or according to the due date (pull distribution) )t puts a limitation on the
date by which SNP stock transfers are to be considered as relevant for deployment 'ithin this hori!on, deployment only
fulfills planned demand that has been confirmed
Push deployment horiGon8 #his hori!on refers to the period of time over which deployment takes into account the
receipts defined in the A#( receipt category group of the location master #he hori!on starts from todayOs date
)f push distribution has been specified (if the distribution demand is smaller than the supply and stock on hand), this
hori!on determines whether stock on hand is to be distributed before the distribution demand due date according to the
push rule specified Only stock on hand within the push deployment hori!on is taken into account for push deployment
(deployment before the actual demand date)
Safety stock horiGon8 #his hori!on is only used during push rule Push distribution taking the safety stock hori!on into
account (for an e&planation, see below)
SNP checking horiGon8 (eployment uses this hori!on to calculate the "uantity available for distributing to demand
locations )t puts a limitation on the "uantity that is available within the push deployment hori!on 'ithin the SNP
checking hori!on, deployment calculates the A#( "uantity for a period by adding up the A#( receipts from the current
and preceding periods, and subtracting all the A#( issues within the SNP checking hori!on
Page 219 of 251
Deployment Heuristic Profiles
#he following table describes the profiles used by the deployment heuristic 1ou can define these profiles partly in the
location product master and partly in the -ustomi!ing or in the current settings for Supply Network Planning (SNP) 6or more
information, see the )mplementation Cuide ().C) or the field%level help (6; help)
Profile /se in Deployment $un
Planning calendar (time
streams)
Specifies the planning calendars the system uses to determine when you can produce,
transport, and so on
SNP demand profile
(product master)
Specifies how the system calculates demand 1ou define the pull #eploy$ent hori6on in this
profile
SNP supply profile
(product master)
Specifies how the system calculates supply 1ou define the push #eploy$ent hori6on in this
profile
SNP deployment profile
Specifies the logic used by the system to distribute the available supply to the demand
locations 1ou define #istribution rules in this profile
SNP rounding profile Specifies how the system is to round order proposal "uantities to create deliverable units
SNP lot si!e profile
(transportation lanes)
)n this profile, you define minimum and ma&imum lot si!es for the shipment 1ou then specify
this profile for one specific product in the Product%Specific .eans of #ransport section of the
transportation lane 1ou can thus define minimum and ma&imum transportation lot si!es for
specific products
)f you wish to make shipments in integer multiples of a transportation lot si!e only, you can also
define the transportation lot si!e as a rounding value in this profile
SNP planning profile
heuristic, optimi!er, deployment heuristic, deployment optimi!er, and #ransport *oad +uilder
(#*+)
Settings applies globally for all SNP planning procedures 6or some planning procedures, you
can overwrite the settings of the active profile by entering another SNP planning profile during
e&ecution of planning in the background
Parallel processing
profile
1ou use this profile to define how background 3obs are divided in parallel processes 1ou can
specify the number of concurrent parallel processes, the number of ob3ects per processing
block, and the server group 1ou define the profile for each application function, for e&ample
deployment heuristic

$unning the Deployment Heuristic
After production planning is complete and the system knows what is actually to be produced (this information is stored
automatically in live-ache), the deployment run generates #eploy$ent stock transfers
Prere*uisites
1ou have maintained category groups in -ustomi!ing for Supply Network Planning (.aintain -ategory Croups) 1ou
then have to assign these category groups to a location in the location master data (the SNP tab page) ((efault
settings8 A#( receiptsgA#2, all categories that describe demand$ A#( issuesgA#), all categories that describe
supply)
.aster (ata Setup for (eployment 5euristic
1ou have maintained the relevant deployment heuristic profiles
1ou have run the SNP heuristic, SNP optimi!er, supply and demand propagation, or -apable%to%.atch (-#.)
Procedure
6rom the SAP 0asy Access screen, choose Supply Network Planning @ Planning @ Supply Network Planning in the
+ackground @ (eployment #he Supply Network Planning8 (eployment screen appears
2. 0nter an SNP planning profile that you defined in the -ustomi!ing #his contains basis settings for the SNP planning
procedures )f you do not specify a profile, the system uses the default profile activated in the -ustomi!ing
3. 0nter a parallel processing profile that you defined in the -ustomi!ing for SNP #his determines how the background
3obs are divided into parallel processes
4. )n the (eployment 5ori!on in (ays field, enter the number of days you want the system to take into account during its
deployment calculations
Page 220 of 251
planning data 'hen selecting this data manually, enter the planning version, location (or range of locations), and
product (or range of products) that you want to plan
6. )n the (estination *ocations field, you can limit deployment of supply to specific destination locations 1ou may wish to
use this option if there are high priority destination locations, such as B.) customers 1ou should run deployment for
important destination locations first
7. -hoose one of the following options to indicate how you wish the system to proceed with the SNP stock transfers after
the deployment run8
Select (o not change if you only want to run a simulation (so that no deployment stock transfers are created)
Select 2educe if you want the system to create deployment stock transfers and reduce the SNP stock transfers
accordingly
Select (elete if you want the system to create deployment stock transfers and delete all the SNP stock transfers
from within the planning period, irrespective of whether or not they were able to be confirmed by the deployment
run
8. Set the 2eal%#ime (eployment indicator, if you wish the system to take into account the current demand situation at the
destination locations during the deployment heuristic run instead of the results from the last SNP run 0nter a
(eployment (estinatn *ocation if you want the demand of only this destination location to be considered during real%
time deployment
6or real%time deployment, you can specify that you want already e&isting deployment stock transfers to be deleted and
replanned during this planning run #he following options are available8
Select 2eplan All if you want the system to delete all deployment stock transfers that e&ist from the selected source
location to the selected destination locations and to replan them on the basis of the current demand situation
Select 2eplan Non%6i&ed if you want the system to delete all non%fi&ed deployment stock transfers that e&ist from
the selected source location to the selected destination locations and replan them on the basis of the current
demand situation
Select (o Not (elete if you do not want the system to delete any e&isting deployment stock transfers #he demand
situation at the destination locations is used as a basis for creating new deployment stock transfers (taking into
account the confirmed distribution receipt)
9. .ake settings for the application log generated in the planning run )n the log availability field, enter the number of days
you want the log to be saved for #he default value is =: days
1ou define whether the log contains detailed information, such as data for the deployment stock transfers created, and
whether this is displayed directly at the end of the planning run 1ou can also display the log after the heuristic run by
choosing (isplay *ogs
1ou can also specify whether you want a spool list to be generated as well as the application log, and whether you want
this to be displayed automatically at the end of the planning run
Set the No .essage for .issing (estination *oc indicator if you do not want the following message to appear8 No
destination locations found for material ,;, location ,< #his message is fre"uently displayed (particularly when multiple
products are selected) if the system does not determine a destination location for a source location product during the
deployment run
10. Set the ,o Not /se Alerts indicator if you do not wish to use the Alert .onitor and want to improve performance of the
deployment run
11. -hoose -&ecute
$esult
After the deployment run, the system automatically converts SNP stock transfers into deployment stock transfers, which are
used for transportation planning in the #ransport *oad +uilder (#*+)
#onsideration of Demands in the Source (ocation
)f you e&ecute a deployment heuristic in Supply Network Planning (SNP), the system only considers the distribution demand
at the destination locations by default #he system does not consider the demand at the source location, that is, the customer
demand and planned independent demand (forecasts) 1ou can, however, specify that the system reserve part of the
available "uantity (available%to%deploy "uantity, A#( "uantity) to cover the customer demand and4or the planned
independent demand at the source location
#his function is only available if you e&ecute the deployment heuristic in the real%time deployment mode
Features
#here are two possibilities for considering the demand at the source location8
Page 221 of 251
-overage of the demand at the source location is preferred
-overage of the demand at the source location and destination locations with fair share distribution
#o%erage of the Demand at the Source (ocation Is Preferred
)f you want the demand at the source location to have a higher priority for the system than the distribution demand, include
the order categories for the customer demand and4or planned independent demand in the category group with which the
system calculates the A#( "uantity (issue category group A#)) 1ou specify the category groups in -ustomi!ing for SNP
under +asic Settings .aintain -ategory Croups
)n this case, the system uses the A#( "uantity to cover this demand first and only after that does it cover the distribution
demand at the destination locations
Fair Share Distri+ution for #o%ering the Demand
1ou can specify that the system carry out a fair share distribution of the A#( "uantity to cover both the demand at the source
location as well as the distribution demand at the destination locations #o do so, you first enter in the master data of the
source location product (SNP< tab page), whether you want the system to consider the customer demand and4or planned
independent demand #he system carries out the fair share distribution using the fair share rule you have also defined in the
master data of the source location product #he only appropriate rules are A and +, that is, the distribution on percentage
basis according to the demand and the target achievement on percentage basis
)n order for the system to be able to carry out a fair share distribution of the demand, you must e&ecute deployment in the
real%time deployment mode )n addition, you must use the special planning area 9AB.):= and the planning book
9A(2P?6SS that contain the key figure (eployment 2eservation Auantity (or use a planning area you have defined and a
planning book with this key figure) )n this key figure, the system saves the "uantity that it reserves for the demand at the
source location
Note that the system does not create any orders for the demand at the source location, but rather saves the reserved
"uantity as information in a time series key figure #he system does not support the integration of the deployment reservation
"uantities in the 02P system or other systems
)n the active version, you can only use this function if the system does not transfer deployment stock transfers to the 02P
system or transfers them as purchase re"uisitions to the 02P system
)n addition, make sure that you run real%time deployment with the 2eplan All option, since the system has to replan all the
deployment stock transfers
After you have e&ecuted the deployment run, you can display the reserved "uantities in interactive SNP planning or in the
deployment application log
01ample
#he following table shows how the system uses the A#( "uantity to cover the demand at the source location and4or
destination locations, depending on the settings you have made8
Deployment ode
No #o%erage of the
Demand at the
Source (ocation
#o%erage of the
Demand at the Source
(ocation Is Preferred
Fair Share Distri+ution Across
the Demand at Source and
Destination (ocations
A#( "uantity ;:: ;:: ;::
Planned distribution demand ;:: ;:: ;::
Planned distribution demand at
source location
;:: ;:: ;::
-onfirmed distribution demand ;:: : D:
(eployment reservation "uantity
for demand at source location
: ;:: D:

Deployment OptimiGation
#he deployment optimi!er creates a distribution plan for all products you selected in all selected locations of your supply
chain model Once production is complete, the system first checks what product "uantities are actually available at the
source locations (locations where there is stock) #he sum of these product "uantities is known as the available%to%deploy
(A#() "uantity #he system then determines how the A#( "uantity is to be distributed to destination locations (locations
where there is demand) #o do this, the optimi!er considers the following factors8
(istribution rules (such as fair share and push rules) if the available product "uantities e&ceed or fall below the demand
All costs defined in the supply chain model, such as transportation costs, storage costs, and penalties for non%delivery
-onstraints such as transportation capacity, storage capacity, and transportation lot si!es
Page 222 of 251
1ou define constraints and distribution rules in the SNP #eploy$ent opti$i6er profile )n this profile, you can also define
additional parameters for deployment optimi!ation, such as decomposition methods for improving runtime
#he aim of the deployment optimi!er is to find the most cost%effective plan from all feasible plans (plans that consider all the
specified constraints)
Distri+ution $ules
Supply Shortage
)f the deployment optimi!er detects that the A#( "uantity falls below the demand at the destination locations, it applies the
supply shortage rule you defined in the SNP deployment optimi!er profile #he following rules are available8
Distri+ution )ased on (owest #osts .
'hen calculating the product "uantities to be distributed, the deployment optimi!er only considers the costs defined in
the supply chain model and the constraints specified in the SNP deployment optimi!er profile #he calculated distribution
plan will be the plan with the lowest costs
'ith this option, it is possible that the demand at one location will not be covered because the demand at another
location can be covered at less cost
Fair Share Distri+ution +y Demands
#he deployment optimi!erOs main ob3ective is to distribute the A#( "uantities evenly, according to the demands (sales
orders and forecasts) at the destination locations
'hen distributing the calculated "uantities, the system also considers the costs defined in the supply chain model 6or
e&ample, if transportation costs are high, the optimi!er can decide not to distribute the allocated amount directly to a
demand location, but rather to make a detour through another location )f the calculated fair share "uantities cannot be
distributed to individual locations due to identified constraints, these "uantities are distributed to other destination
locations on the basis of costs
0arliest Deli%ery
'hen used in con3unction with the 6air Share by (emands option, you can specify that, in fair share distribution, the
deployment optimi!er is to completely fulfill the earliest demands if possible, before planning the fulfillment of later
demands )f you do not choose this option, the optimi!er will attempt to distribute the A#( "uantities evenly over the
demands in various periods
Supply Surplus
)f the deployment optimi!er detects that the A#( "uantity e&ceeds the demand from the destination locations, it applies the
supply surplus rule you defined in the SNP deployment optimi!er profile #he following rules are available8
Distri+ution )ased on (owest #osts
'hen calculating the product "uantities to be distributed, the deployment optimi!er only considers the costs defined in
the supply chain model and the constraints specified in the SNP deployment optimi!er profile 5owever, as a rule, the
system does fulfill all demands at the destination location, since high non%delivery costs prevent a demand from not
being fulfilled #he optimi!er distributes e&cess stock to the lowest cost locations #his does not necessarily have to be a
location where there is demand
Push Distri+ution +y Demand
#he deployment optimi!erOs main ob3ective is to distribute the A#( "uantities evenly, according to demands at the
destination locations Since the A#( "uantity e&ceeds the demand "uantity, the calculated percentage, in contrast to the
fair share situation, is over ;::a (the destination locations may receive a "uantity that e&ceeds their demand)
As with fair share distribution, when distributing calculated "uantities, the system also considers the costs defined in the
supply chain model and, if necessary, accepts detours in the supply chain, if this means that the total cost can be
reduced
0arliest Deli%ery
'hen used in con3unction with the option Push (istribution by (emand, you can specify that, in push distribution, the
deployment optimi!er is to distribute all available A#( "uantities to destination locations at the earliest demand time )f
you do not choose this option, the optimi!er will attempt to distribute the A#( "uantities evenly over the demands in
various periods
#onsideration of #osts
#he deployment optimi!er considers the following costs defined in the supply chain model8
Storage and transportation costs
-osts for increasing storage, transportation and handling capacity
Safety stock penalty
*ate delivery penalty
Page 223 of 251
Non%delivery penalty
1ou use the SNP cost profile to set the relative importance of different cost types
#onsideration of #onstraints
#he optimi!er considers that a plan is feasible when it satisfies all the supply chain model constraints that you set in the SNP
deployment optimi!er profile A feasible solution might involve due date or safety stock constraint violations (ue dates and
safety stocks are soft constraints (constraints to which you assign violation costs) #he optimi!er only proposes a plan that
will violate soft constraints if, according to the costs specified in the system, it is the most cost%effective plan
#he optimi!er uses the linear programming method to take account of all planning%problem%related factors simultaneously
within one optimal solution As more constraints are activated, the optimi!ation problem becomes more comple&, which
usually increases the time re"uired to solve the problem As a rule, you should run optimi!ation as a background 3ob
#he optimi!er makes a distinction between continuous linear optimi!ation problems and discrete optimi!ation problems
(inear OptimiGation
1ou can choose one of the three following methods from the SNP deployment optimi!er profile to solve continuous linear
deployment optimi!ation problems8
Primal simple& method
(ual simple& method
)nterior point method
All three methods arrive at an optimal solution 2untime could be the main influencing factor when deciding which of these
methods to use 5owever, there is no general rule for selecting the best method for a given problem (apart from to test each
method individually) A good way of assessing the application is to do a benchmarking based on a test scenario #his is
because the optimal choice of method depends more on the structure of the supply chain and less on the input data
#herefore, in a productive environment, daily benchmarking is not necessary
Discrete OptimiGation
A problem is not continuous (and is therefore discrete) for the deployment optimi!er when the model contains8
(iscrete (integer value) lot si!es for transportation
(iscrete means of transport
.inimum lot si!e for transportation
Piecewise linear cost functions for transportation
Storage, transportation and handling capacity
)f you want the optimi!er to consider any of the above constraints, you must use one of the discrete optimi!ation methods
from the SNP deployment optimi!er profile
#he piecewise linear cost function that you can define in master data makes a distinction between the conve& cost function
(cost per unit increases for higher volumes$ for modeling overtime or night shifts for instance) and the concave cost function
(cost per unit decreases for higher volumes$ for modeling freight rates for instance)
-onve& cost functions do not complicate the planning problem and can be solved efficiently 5owever, they can also be
modeled using alternative modes without using piecewise linear cost functions
)n contrast, concave piecewise linear cost functions cannot be solved by an *P solver but only by using discreti!ation
methods (mi&ed integer linear programming) )f piecewise linear functions are modeled but the optimi!er is run without
discreti!ation or the discreti!ation hori!on is smaller than the planning hori!on, the optimi!er takes into account the linear
cost function defined in addition to the piecewise linear cost function
#he discrete optimi!ation method cannot be used with strict prioriti!ation (see below)
/sing the discrete optimi!ation method can significantly increase runtime re"uirements Note that Supply Network Planning
is a medium%term planning function and its focus should not be on solving integer problems (that is, using the discrete
optimi!ation method)
Decomposition
#he primary focus of decomposition is on reducing the runtime and memory re"uirements of optimi!ation (ecomposition
may also represent the only way for the deployment optimi!er to find a feasible solution in the event of large discrete
problems
(ecomposition is a fle&ible tool for the user to balance the tradeoff between optimi!ation "uality and re"uired runtime 'hen
runtime is unrestricted, the optimi!er usually provides a better (optimal) solution without decomposition$ however, when a
fi&ed runtime has been specified, using decomposition could assist the optimi!er to find a better or, in fact, feasible solution
#he decomposition methods available for the deployment optimi!er are detailed below #he time, product, and internal
deployment decomposition methods can be used in con3unction with the linear and discrete optimi!ation methods )t is only
advisable to use resource decomposition in con3unction with discrete optimi!ation
Page 224 of 251
Time decomposition speeds up the solution process by dividing the source problem into a series of partial problems
#hese sub%problems are then solved in se"uence
Product decomposition speeds up the solution process by forming product groups #he complete model solves one
product group at a time according to the window si!e chosen #he rule of thumb is as follows8 #he smaller the window
si!e, the less time it will take to find a solution, but the larger the window si!e, the better the "uality of the solution found
$esource decomposition speeds up the solution process by analy!ing the material flow and basic optimi!er decisions
about transportation and storage determine a resource se"uence #he optimi!er can then create sub%problems for the
individual resources, which are solved in se"uence #he optimi!er makes decisions in every sub%problem that cause the
resource to be loaded
)t is particularly advisable to use resource decomposition if the resources are always loaded in a similar se"uence
2esource decomposition does not reduce memory re"uirements )f you would like to reduce memory re"uirements, you
could use time decomposition alongside this decomposition method 2esource decomposition cannot be used in
con3unction with product decomposition or strict prioriti!ation
Internal deployment decomposition can speed up the solution process by dividing the optimi!ation problem into the
smallest partial problems possible #hese partial problems are then solved se"uentially )t is particularly advisable to use
this decomposition method if the supply chain model has a particular problem structure 6or e&ample, is the model does
not contain capacitiy restrictions, the products can be distributed independently in deployment, which can help reduce
runtime
1ou can also use the SNP priority profile to define priorities for product and resource decomposition, that is, you can
change the se"uence in which the optimi!er groups and plans products and resources in partial problems 6or more
information, see the SNP Priority Profile section in ,eco$position (SNP optimi!er documentation)
PrioritiGation
#he deployment optimi!er can differentiate between the priority of sales orders and forecast demand 'ith strict
prioriti!ation, sales orders always have priority ;, the corrected demand forecast priority D, and the demand forecast priority
F 'ithin every priority class, the system uses all available cost information to determine the final solution )f you are using
cost%based prioriti!ation, the optimi!er uses penalty cost information from the product master data (on the SNP; tab page) to
determine the optimal solution
Other #onsiderations
#he deployment optimi!ation run results do not include pegging orders back to the original individual re"uirements
because re"uirements are bucketed
#he deployment optimi!er considers the entire capacity and the entire alternative capacity that is globally available (at all
locations)
)n the event of a capacity overload, the deployment optimi!er, depending on the system settings, either does not provide
a solution or increases the capacity based on a penalty cost calculation
#he deployment optimi!er considers the shelf life of a product in a restricted way (see the information about the SNP
optimi!er in stock planning, which is also applicable to the deployment optimi!er)
#he deployment optimi!er considers the three following deployment hori!ons8 Pull #eploy$ent hori6on, push #eploy$ent
hori6on, and SNP checking hori6on 1ou define these in the deployment optimi!er profile

Deployment OptimiGer Profiles
#he following table describes the profiles used by the deployment optimi!er #o access each profile individually, choose
Supply Network Planning @ 0nvironment @ -urrent Settings @ Profiles from the SAP 0asy Access screen 1ou can also
define the profiles in the -ustomi!ing for Supply Network Planning (SNP) 6or more information, see the )mplementation
Cuide ().C) or the field%level help (6; help)
SNP
deploymen
t optimi!er
profile
)n this profile, you choose which optimi!ation method you want to use during the optimi!ation run (linear
optimi!ation or discrete optimi!ation) and which constraints you want the system to take into account
Although almost identical to the SNP optimi!er profile, this profile only contains parameters that are relevant
for the deployment optimi!er )t also contains a tab page where you can define deployment%specific
parameters (distribution rules and deployment hori!ons)
SNP cost
profile
)n this profile, you assign a weighting to different cost elements in the ob3ective function (thus determining
how the costs relate to one another)
'e recommend that you only change the standard settings for test purposes when modeling #o avoid
undesired side%effects, you should not change the default setting of ;: in the production system if possible
#his setting corresponds to the costs entered in cost maintenance
SNP lot )n this profile, you define minimum and ma&imum lot si!es for the shipment 1ou then specify this profile for
Page 225 of 251
si!e profile
(transportat
ion lanes)
one specific product in the Product%Specific .eans of #ransport section of the transportation lane 1ou can
thus define minimum and ma&imum transportation lot si!es for specific products
)f you wish to make shipments in integer multiples of a transportation lot si!e only, you can also define the
transportation lot si!e as a rounding value in this profile
#o enable the deployment optimi!er to take into account the minimum lot si!es and rounding values
defined, you have to choose the discrete optimi!ation method in the SNP deployment optimi!er profile
SNP
optimi!atio
n bound
profile
)f you want to perform a new planning run after a deployment optimi!er planning run, you use this profile to
improve planning stability by restricting possible decision variable deviations from the previous optimi!ation
plan 6or e&ample, you can permit smaller deviations at the start of the planning hori!on and then increase
these towards the end of the hori!on to avoid too many last%minute planning changes
1our new plan does not have to be based on the directly preceding optimi!ation run, you can also choose
earlier runs
SNP
planning
profile
)n this profile, you can make basic settings for the various SNP planning procedures, such as heuristic,
optimi!er, deployment heuristic, deployment optimi!er, and #ransport *oad +uilder (#*+)
#he SNP planning profile that you activate in the SNP -ustomi!ing under .aintain Clobal SNP Settings
applies globally for all SNP planning procedures 6or some planning procedures, you can overwrite the
settings of the active profile by entering another SNP planning profile during e&ecution of planning in the
background
Parallel
processing
profile
1ou use this profile to define how background 3obs are divided in parallel processes 1ou can specify the
number of concurrent parallel processes, the number of ob3ects per processing block, and the server group
)n each case, you define the profile for one specific application function, such as the deployment optimi!er

$unning Deployment OptimiGation
After production planning is complete and the system knows what is actually to be produced (this information is stored
automatically in live-ache), the deployment optimi!ation run generates #eploy$ent stock transfers 1ou can run deployment
optimi!ation in the background and in interactive Supply Network Planning
Prere*uisites
1ou have maintained category groups in -ustomi!ing for Supply Network Planning (.aintain -ategory Croups) 1ou
then have to assign these category groups to a location in the location master data (the SNP tab page) ((efault
settings8 A#( receipts % A#), all categories that describe demand$ A#( issues % A#2, all categories that describe
supply)
Master ,ata Setup for the ,eploy$ent Opti$i6er
1ou have maintained the relevant deployment optimi!er profiles
1ou have run the SNP heuristic, SNP optimi!er, supply and demand propagation, or -apable%to%.atch (-#.)
Procedure
To $un Deployment OptimiGation in the )ackgroundC
6rom the SAP APO 0asy Access menu, choose Supply Network Planning @ Planning @ Supply Network Planning in the
+ackground @ (eployment Optimi!ation
2. 0nter an SNP planning profile that you defined in the -ustomi!ing #his contains basis settings for the SNP planning
procedures )f you do not specify a profile, the system uses the default profile activated in the -ustomi!ing
3. 0nter a parallel processing profile that you defined in the -ustomi!ing for SNP #his determines how the background
3obs are divided into parallel processes
planning data 'hen selecting this data manually, enter the planning version, level )(, product (or range of products),
and the location (or range of locations) that you want to plan
5. Specify the start and end date that you want the system to consider for planning #his entry is optional )f you do not
enter a start and end date, the system uses the planning buckets profile that was specified in the data view
0nter the SNP deployment optimi!er profile to be used for deployment optimi!er calculations #o define a
deployment optimi!er profile, choose Supply Network Planning @ 0nvironment @ -urrent Settings @ Profiles @
(efine SNP (eployment Optimi!er Profiles
Specify the cost profile that you want to be used for deployment optimi!er calculations #o maintain a cost profile,
choose Supply Network Planning @ 0nvironment @ -urrent Settings @ Profiles @ (efine SNP -ost Profiles
Page 226 of 251
6. )f re"uired, specify the optimi!ation bound profile that you want to use for the deployment optimi!er calculations #o
maintain an optimi!ation bound profile, choose Supply Network Planning @ 0nvironment @ -urrent Settings @ Profiles @
(efine SNP Optimi!ation +ound Profiles )n the accompanying field, you can still specify or choose a previously
e&ecuted optimi!ation run that you want the profile specified in the Optimi!ation +ound Profile field to reference
7. -hoose 0&ecute
To $un Deployment OptimiGation in Interacti%e Supply Network PlanningC
6rom the SAP 0asy Access screen, choose Supply Network Planning @ Planning @ )nteractive Supply Network Planning
1. -hoose (eployment Optimi!er( #he (eployment Optimi!er window appears #he pushbutton for accessing the
deployment optimi!er is displayed on the interactive desktop automatically if you are using the standard SNP planning
book SNP9> 5owever, if you create your own planning books and wish to use the deployment optimi!er in interactive
planning, you must specify that you want this pushbutton to be displayed 1ou do this in the (esign mode of the
interactive planning desktop
2. On the Optimi!ation tab page in the (eployment Optimi!er window, you can choose one of your predefined deployment
optimi!er profiles, cost profiles, and optimi!ation bound profiles +y choosing the icons , , and , you branch to
the maintenance screens for the deployment optimi!er profiles, cost profiles, and optimi!ation bound profiles to make
changes to e&isting profiles, for e&ample
3. -hoose to start the optimi!ation run
#he current solution resulting costs determined by the optimi!er are displayed in the -urrent Solution area of the
Optimi!ation tab page #he individual steps of the optimi!ation process are displayed in the Status area during the
optimi!ation run and information about intermediary solutions is displayed in the Solution 2un area )n addition to this,
messages about the current optimi!ation run are displayed in the .essages area
1ou can also display the products that were selected for this optimi!ation run by choosing -hoose to branch to
the Supply Network Planning8 Optimi!er log file screen 6rom there, you can decide which type4form of log to display
(the message log, input log, or results in a te&t file for e&ample)
4. -hoose the Solutions tab page to view information about the previous optimi!ation runs )f you select a solution in the
right%hand screen area, the data corresponding to that solution appears in the left%hand area
5. -hoose the .essages tab page to view messages about the previous optimi!ation runs )f you select an optimi!ation
run in the left%hand screen area, the messages corresponding to that optimi!ation run appear in the right%hand area
$esult
After the deployment optimi!ation run, the system automatically converts SNP stock transfers into deployment stock transfers,
which are used for transportation planning in the #ransport *oad +uilder (#*+)
Automatic #ost =eneration
plan with the lowest total costs from all the permitted production and distribution plans #his means that the optimi!er also
makes business decisions based on the costs involved for covering a demand at a certain point in time, for e&ample
1ou can provide the optimi!er with the costs for planning by specifying your actual costs such as production and
transportation costs in the system 1ou can also define control costs that are in accordance with your business goals 6or the
planner, however, the conversion of business goals into control costs is not easy
'ith the automatic cost generation function, you can easily generate all the control costs relevant to the optimi!er (that is,
the cost model) #he system generates these costs automatically based on the business goals you have defined #he
system re"uires the main goal to be the ma&imi!ation of the service level 1ou can also define the following goals8
)n addition, you can use this function to "uickly and easily create an optimi!ation%based production plan #o create a finite
(capacity%based) production plan, you only have to make a few additional settings (such as the consideration of capacities)
Features
=enerating the #ost odel
#he system generates the following control costs8
Storage costs
Production costs, that is, costs of the production model (PP.) or of the production data structure (P(S)
Product%specific transportation costs
Procurement costs
Page 227 of 251
Penalty costs for non%delivery
Penalty costs for late delivery
)n order for the system to be able to calculate the costs for a late delivery, you must define a ma&imum delay in the product
master data on the SNP ; tab page
#he system ignores all the costs you may have defined in the master data #hey remain unchanged in the system even after
cost generation, however
#he system does not generate the following costs, because it would re"uire additional information from the planner or
because the costs are only relevant to comple& scenarios8
-ost functions (production, shipment, procurement)
-osts for means of transport
-osts for the use of the available capacity of resources (costs for using the normal and ma&imum available capacities or
for falling short of the minimum available capacity)
)n addition, the system does not consider the cost profile for weighting costs that you can define for optimi!ation%based
planning
Properties of the =enerated #ost odel
#he system ensures the following properties of the generated cost model8
#he model has no anomalies
#he system defines the costs such that undesired effects do not arise, such as8
Not covering a demand due to too low penalties costs for non%delivery
Planning a shipment due to too low costs at the destination location
Planning a shipment to save storage costs
#he system also covers the demands as timely as possible
#he model is stable
#he costs are, for e&ample, independent of period length and transaction data
#he model is coherent
6or e&ample, the transportation costs increase proportionally to the shipment length and the product value increases
with the depth of production
#he system automatically uses the value ; for the value of raw products (products without input products) )f you want
the system to base the calculation of the product value on the actual storage costs, you can make this setting in the SNP
or #eploy$ent opti$i6er profiles on the Automatic -ost Ceneration tab page
#he system cannot guarantee this model property, because the first two properties have higher priority and it is not
always possible to guarantee all three
#he generated cost model is independent from the costs defined in the master data (e&cept for possible consideration of
storage costs) #he system does not support a combination of these two cost models (for e&ample, completion of the master
data cost model)
#he system calculates the costs based on the business goals you have defined 6or further information see ,efinition of the
Business 5oals
Actions
1. (efine your goals for optimi!ation%based planning as described
2. )f, for e&ample, you want to create a finite (capacity%based) plan, set the corresponding indicator for the consideration of
capacity restrictions on the Ceneral 2estrictions tab page of the SNP or deployment optimi!er profile
3. Set the Automatic -ost Ceneration indicator in the SNP or deployment optimi!er profile
4. 0&ecute an SNP or deployment optimi!ation run 6or more information, see 2unning the Optimi!er in the +ackground,
2unning the Optimi!er from the )nteractive Planning (esktop, or 2unning (eployment Optimi!ation
5. (isplay the application log that is in the 2esults *og section and contains information about the generated costs 6or
more information about optimi!ation logs, see Application *ogs for Optimi!ers
Page 228 of 251
)f you want to create an optimi!ation%based production plan with the auto$atic cost generation function, first define your
business goals for planning #he system then uses these goals to automatically generate the corresponding control costs,
based on which the optimi!er makes planning decisions
#he main goal of planning is to ma&imi!e the service level 1ou can also define the following additional goals8
1ou define these goals in the SNP or #eploy$ent opti$i6er profile on the Automatic -ost Ceneration tab page
Features
#onsideration of demand and product priorities
1ou can define priorities for three different priority classes of the #e$an# and the safety stock8
-ustomer demand
(emand forecast
Safety stock
#he standard setting is that all priority classes and the safety stock have the same priority
)n addition, you can define that the system also considers the priority of products 1ou can enter this priority in the master
data of the location product on the SNP < tab page #he system considers the product priority in combination with the
demand priority 1ou can define which priority is more important and is to be considered by the system first
#o simplify this combination of both priority types, you must also subdivide the product priorities into three classes of A, +,
and - products
#he following figure shows e&actly how the system proceeds if the demand priority is more important than the product priority
or vice versa8
#onsideration of procurement priorities
1ou can define that the system considers the procurement priorities of production process models (PP.s) or production data
structures (P(S) as well as transportation lanes 1ou define this priority in the master data of the PP.s4P(S and
transportation lanes (specific to the product) #he procurement priority of sources of supply for in%house production is always
more important than the priority of sources of supply for e&ternal procurement (same as the SNP heuristic procedure)
#he system always tries to first cover all the demand of a period with receipts from all the sources of supply available in this
period (in the se"uence of the procurement priority of these sources of supply) Only after this does it try to cover the
demand with receipts from sources of supply from an earlier period )f the system has to switch to an earlier or later period, it
may not be able to follow this principle in this period
#osts aintenance
plan with the lowest total costs from all the permitted production plans
/se this function to define all costs used by the optimi!er and assigned to the master data from a single point of access #he
master data is then automatically updated for the selected planning version
Page 229 of 251
#o call the function, on the SAP 0asy Access screen, choose Advanced Planning and Optimi!ation .aster (ata @
Application%Specific .aster (ata@ Supply Network Planning @ .aintain -osts((irectory) or .aintain -osts (#able)
Features
1ou can define the following costs8
Production costs
Storage costs
5andling costs
Procurement costs
-osts for non%delivery
-osts for using the available capacity of resources
-ost functions
SNP Optimi!er
Features
#he Optimi!er *og (ata function provides an overview of the generated logs Amongst other things, the list of logs
*og status
*og creator
order creation)
*og e&piration date
)f you double click a log or choose (isplay *og, you receive the following data and sub%logs for the log
Input Parameter . -ontains the settings that you made on the initial screen for the planning function
(ocation Products . -ontains the location products selected for the optimi!ation run
Page 230 of 251
Deletion Time Period . Specifies a time period in which the system deletes e&isting planned orders and stock
transfers before actual optimi!ation
Input (og . -ontains the input data considered by the system during the optimi!ation run (that is, master data and
transaction data) #he data is divided into a number of tables (such as 0#?*O-.A#) 1ou can display the content
of these tables on the right%hand side of the screen 6or more information, see Opti$i6ation 0nput "og
$esults (og . -ontains all results of the optimi!ation run, such as planned orders, stock transfers, resource
consumption, costs, and penalty costs #he data is divided into a number of tables (such as 0#?P2O.O) 1ou can
display the content of these tables on the right%hand side of the screen
$esult Indicators . -ontains indicators that display the "uality of the optimi!ation solution, such as service level
and shortfall of safety stock 6or more information, see +esult 0n#icators
01planations % -ontains the results of an e&planation tool run (see below)
01tended $esults (og % )n this log, you can display the results of the optimi!ation run in the interactive SNP
planning form
essage (og % -ontains error messages, warning messages, and information messages generated by the system
during the optimi!ation run #hey are ordered according to meaning, that is, whether they refer to the optimi!ation
run settings or to the three main steps of the run
Trace File % All individual optimi!ation run steps are logged in this te&t file )t is saved on the optimi!ation server, but
you can also download it to your own computer
#osts % -ontains detailed information about the costs of the solution determined by the optimi!er 6or more
information, see +esulting Costs of Opti$i6ation
Solution Juality % -ontains the costs of the best solution determined by the optimi!er up to the time displayed )f
you used a decomposition method, you can also relate the costs the partial problem solved up to this time
1ou can also download the input log and the results log to your own computer #o do this, choose (ownload )nput
*og or (ownload 2esults *og #he logs are then saved in 20*A#)O. te&t format
)f you select a log and choose 0&plain, you go to the 0&planations of SNP Optimi!ation 2esultsscreen 6rom this
screen you can e&ecute the e&planation tool which e&plains two important e&ceptional situations of an optimi!ation run8
non%deliveries and shortfall of safety stock
onitoring T() and Deployment Alerts
1ou can use the Alert Monitor to monitor alerts for the !ransport "oa# Buil#er and for ,eploy$ent #o do this, you define
a #*+ alert profile containing a user%specific selection of alerts that are relevant for your planning area
Features
#he following table shows you the alert types available, and a brief description of each one
6or all the alerts e&cept )nvalid (elivery (ate, you can enter priority variants based on critical values
T()!deployment alerts Description
6air share (general)
#he fair share percentage is determined according to the rule specified in the #eploy$ent
heuristic profile (SNP< tab in the location product master) #he system triggers this alert if the
percentages to deploy in order to meet product demand fall below the percentages specified
in the master data
6air share (customers
only)
Same as above, e&cept in this case fair share distribution refers only to customers instead of
locations (for e&ample, B.) customers)
)nvalid shipment
'hen the shipment does not fulfill the parameters for the capacity of the means of transport
(such as volume, weight, and pallet positions) defined in the !"B profile, the system
generates an alert
)nvalid delivery dates 1ou active this alert using the 4SAPAPO4#*+?-5L?(A#0 +Ad)
Acti%ities
1. Select the alert types that are relevant to you, and define threshold values where re"uired
2. Select the ob3ects (products, transportation lanes, means of transport) for which the system should determine alerts
Page 231 of 251
3. )f necessary, assign the #*+ alert profile to your Overall Alert Profile, your SCC /ser Profile , or your user by selecting
Advance Planning and Optimi!ation @ Supply Network Planning @ 0nvironment @ -urrent Settings @ Assign Planners
to Alert Profiles from the SAP 0asy Access screen
6or performance reasons, we recommend restricting the number of alerts to be displayed to a minimum

Transport (oad )uilder
1ou can use the #ransport *oad +uilder (#*+) to group transport loads for certain means of transport whilst ensuring that the
capacity of the means of transport is utili!ed as much as possible #he main aims of #*+ planning are8
+uilding of transport loads that are within the parameter limits defined by the user (such as weight and volume)
Straight loading or load balancing of means of transport
#he #*+ groups #eploy$ent stock transfers or replenishment orders that were generated for individual products in the
previous planning runs, into !"B ship$ents for several products
1ou can use the #*+ in the SAP )nventory -ollaboration 5ub (SAP )-5) or in Supply Network Planning (SNP) )n SAP )-5,
there are additional functions available #hese are features that are not available in the SNP #*+ 6or more information, see
A##itional !"B Functions in SAP 0C.
1ou have set up the master data for the #*+ 6or more information, see Master ,ata Setup for the !ransport "oa#
Buil#er
1ou have defined upper and lower limits for the #*+ parameters in a #*+ profile, and have assigned this profile to the
means of transport in the transportation lane #o create the #*+ profile, proceed as follows8
SAP )-58 )n the SAP )-5 'eb Application menu, choose #ransport *oad +uilder Profiles and 2ules
SNP8 On the SAP 0asy Access screen, choose Advanced Planning and Optimi!ation Supply Network Planning
0nvironment @ -urrent Settings @ Profiles@ (efine Profiles for #ransport *oad +uilder (#*+)
6or more information, see #*+ Profile
1ou have defined a profile for the #*+ basic settings in -ustomi!ing for SAP )-5 or SNP )f you do not define a profile,
the #*+ uses the default settings #o create the profile, proceed as follows8
SAP )-58 )n -ustomi!ing for SAP )-5, choose -ustomer -ollaboration #ransport *oad +uilder .ake #*+%+asic
Settings
SNP8 )n -ustomi!ing for SNP, choose +asic Settings .ake #*+ +asic Settings
6or more information, see the )mplementation Cuide ().C)
)f you are using SNP, you can make settings for the layout of interactive #*+ planning in SNP in -ustomi!ing for SNP
under +asic Settings -hange (isplay of Parameters in )nteractive #*+ 6or more information, see the ).C
)f you want the #*+ to be able to load a pallet with several different products, you can set the #*+8 Pallet *oading
parameter to Product .i& in -ustomi!ing for SNP under .aintain Clobal SNP Settings )f you do not make this setting,
the SNP #*+ is permitted to load pallets with products of the same type only
)f you are using SAP )-5, you must make additional settings for the #*+ 6or more information, see A##itional !"B
Functions in SAP 0C.
FeaturesC )uilding of Transport (oads
#he #*+ first groups deployment stock transfers or replenishment orders from the current period into #*+ shipments )n
doing so, the #*+ tries to load the shipments as far as possible to the upper parameter limits that you defined in the #*+
profile for that means of transport
#he #*+ also considers the loading method that you defined for the means of transport in the transportation lane As far as
possible, the #*+ loads the transport loads with the same products, or products from the same loa#ing group &straight
loading', or distributes the products evenly amongst all transport loads built &load +alancing' (o note, however, that the
#*+ does not use optimi!ation methods and can, therefore, not guarantee the optimal solution #he #*+ considers the
individual loading methods as follows8
Straight loading8 #he #*+ sorts the loading groups and then the products within the loading group alphabetically )n the
second step, the #*+ distributes the loading groups and products into shipments, in the se"uence in which they were
sorted
)f a loading group can only be partially loaded onto a shipment, the #*+ loads the rest of the loading group onto the ne&t
shipment )n this way, it is possible for a loading group to be too large or too small for a shipment
(oad +alancing8 #he #*+ tries to distribute products to shipments in such a way, that the product percentages are, as
far as possible, the same for every shipment
Page 232 of 251
#o do this, each time, the #*+ adds a rounding value of that product to a shipment #his is the smallest ratio of the
"uantity already loaded and the total demand of the product )f the ratios of all products are the same, the #*+ adds a
rounding value of a product selected at random to the shipment
Once all #*+ shipments lie within the valid parameter limits, the #*+ ends the planning run
1ou can also make detailed settings for transport load building by creating your own profile for the #*+ basic settings in
-ustomi!ing for SAP )-5 or SNP (see the Prere"uisites section above)
Procedure for $emaining Juantities
#he #*+ may not be able to load one of the #*+ shipments to the defined lower limits with deployment stock transfers or
replenishment orders from the current period 6or more information about how the #*+ proceeds in this situation, see !"B
Proce#ure for +e$aining 8uantities
$unning the T() and #hecking the $esults
1ou can also start the #*+ as a background 3ob or run it directly from interactive #*+ planning )n interactive #*+ planning,
you can display the results after the #*+ run and then change the shipments manually 1ou receive a list of generated #*+
shipments and possibly also deployment stock transfers that have not been processed 1ou can then remove or add
deployment stock transfers from or to the #*+ shipments
1ou can also display the results of the #*+ run in the application log that is generated during the run
Acti%ities
#he following table details the activities that you have to carry out in SNP or SAP )-5 to run the #*+ and check the results8
Acti%ity SNP SAP I#H
$unning
the T() as
a
)ackgroun
d Oo+
On the SAP 0asy Access screen choose, Advanced Planning and
Optimi!ation Supply Network Planning Planning Supply
Network Planning in the +ackground #ransport *oad +uilder
(#*+) #he SNP #ransport *oad +uilder screen appears where you
can make settings for the background run and for the #*+ run
1ou can also plan the #*+ run as a background 3ob using the
Process -hain in S-. function
1ou e&ecute the #*+ as a
background 3ob using the Planning
Service Manager
$unning
the T()
from
Interacti%e
T()
Planning
and
#hecking
the $esults
-hoose Advanced Planning and Optimi!ation @ Supply Network
Planning @ Planning @ #ransport *oad +uilder (#*+)
#hen make a selection #o make settings for the #*+ run, choose
with the "uick info te&t #*+ Parameters )n this dialog bo&, you
can also temporarily change #*+ profile settings and transportation
lane settings #hen choose #*+
#he results are then displayed in the planning table
)n the SAP )-5 'eb Application
.enu, choose #ransport *oad
+uilder @ #ransport *oad +uilder
1ou make the settings for the #*+
run in the !"B service profile #hen
choose #*+ Planning 2un
#he results are then displayed in
the planning table
#hecking
the T()
$esults in
Application
(ogs
6or more information about application logs in SNP, see
Application *ogs
On the SAP 0asy Access screen,
choose )nventory -ollaboration
5ub @ Administration @ Application
*ogs @ (isplay Application *ogs
T() Profile
1ou use this profile to determine within which parameter limits the #ransport *oad +uilder (#*+) groups shipments for a
means of transport
1ou can use the #*+ profile for the #*+ in the SAP )nventory -ollaboration 5ub (SAP )-5) or in Supply Network Planning
(SNP)
Structure
Parameter (imit
)n the Parameters for #*+ Profile8 WW section of the #*+ profile, you can define upper and lower limits for the following
standard parameters8
'eight
Bolume
Pallet Positions
1ou can also define additional customer%specific parameters using +Ad)s 6or more information, see SAP note G;:;9J
Page 233 of 251
$ule $elationships
)n the #*+ profile section, you can define very fle&ible rule relationships for linking upper and lower limits #he following
standard connections are available8
-onnect upper limits with KandK, lower limits with VorO 'hen building transport loads, the #*+ may not e&ceed any of the
upper limits defined One lower limits must also be reached or e&ceeded, depending on how you have defined the rules
-onnect upper limits with KandK, lower limits with VandO #he #*+ may not e&ceed any of the upper limits defined All lower
limits must be reached or e&ceeded
)f you have chosen the KPK operator, the #*+ also interprets the lower limits as upper limits
)n addition to the standard connection, you can also define user%specific relationships between the rules /sing the &$D and
,- operators as well as brackets, you can determine which combinations of rules you want the #*+ to use when building
transport loads
'hen processing the rules, the #*+ always considers the AN( connection first and then the O2 connection )f you want to
change this se"uence, you can put the O2 connection in brackets
1ou have defined specific upper and lower limits for the parameters8 'eight (2ule ;), Bolume (2ule <), and Pallet Positions
(2ule =) 1ou now want to specifiy that you want either both rules ; and <, or rule = to be fulfilled 1ou then enter 5 AND 7
O$ 8 in the 2ule (etails field
)f you want to define a rule connection, such as 5 O$ 7 AND 8 and also want the #*+ to consider the rules in this se"uence,
you must define the rules as follows8 &5 O$ 7' AND 8
T() Procedures for $emaining Juantities
)f the #ransport *oad +uilder (#*+) has not been able to load one of the !"B ship$ents to the upper limits defined with the
#eploy$ent stock transfers or replenishment orders of the current period, the #*+ first redistributes product "uantities #he
#*+ tries to ensure that all shipments lie within the valid upper and lower parameter limits by only loading some shipments to
the defined lower limits #o do this, the #*+ rebuilds all transport loads, taking the loading method into account
)f the #*+ does not produce a valid solution this way either, it uses the following shipment si!ing methods
Shipment /psi!ing
Shipment (ownsi!ing
Features
Shipment /psiGing
#he #*+ upsi!e the product "uantities to be transported by including further deployment stock transfers or replenishment
orders that lie within the pull%in hori6on #he #*+ also sorts the stock transfers within this hori!on according to their daysO
supply
1ou can also define a coverage period for a product in the master data for location product #he #*+ is then only allowed to
bring forward as many products that are necessary to cover demand within this time period 1ou can also rule our shipment
upsi!ing for a product
#he #*+ system upsi!e the shipment "uantities with individual rounding values of the product until all shipments lie within the
valid upper and lower parameter limits
Shipment DownsiGing
#aking daysO supply into account, the #*+ downsi!es the product "uantities to be transported by prioriti!ing and reducing
deployment stock transfers or replenishment orders in the current period
Shipment /psiGing or DownsiGing Decision
#he #*+ decides whether the to upsi!e or downsi!e a shipment based on a threshold value and a decision basis for
shipment si!ing )n the SAP )nventory -ollaboration 5ub (SAP )-5), the #*+ can also make the decision based on costs
1ou make these settings in the transportation lane for the means of transport 6or more information, see Master ,ata
Setup for the !ransport "oa# Buil#er
Detailed Setting
1ou can also make detailed settings for shipment si!ing by creating your own profile for the #*+ basic settings in the SAP
)-5, or Supply Network Planning (SNP) -ustomi!ing (see Prere"uisites section under #ransport *oad +uilder) 6or e&ample,
for shipment upsi!ing, you can specify that you want the shipments to be loaded, as far as possible, to the upper parameter
limit
Page 234 of 251
aster Data Setup for the Transport (oad )uilder
)n addition to the general master data settings for planning in Supply Network Planning (SNP), or in the SAP )nventory
-ollaboration 5ub (SAP )-5), you can also make additional settings for the #ransport *oad +uilder (#*+) #he following is
intended to provide an overview of the #*+ settings 6or more information, see the 6; 5elp for the individual fields
6or more information on the master data settings that you can make for the additional #*+ settings in SAP )-5, see
A##itional !"B Functions in SAP 0C.
Settings
Product aster Data
1ou make the following settings in the product, or location product, master data8
Ta+ Field
Properties
Stacking Factor ' #his fields is relevant if you want to use the Pallet Positions #*+ parameter in the
!"B profile #he stacking factor indicates how many pallets of a product can be stacked on top of each
other 6or mi&ed pallets, the system uses the smallest stacking factor of all products
/nits of
.easu
6or the parameters, weight, volume, and pallet positions (only SNP #*+) that you use in the #*+ profile, you
must determine conversion of the parameter unit of measure into the base unit of measure for the product
SNP <
"I Purchasing =roup . #he #*+ can divide the !"B ship$ents into individual orders according to the
purchasing group of the B.) customer
ATD $eceipt and ATD Issue . #hese fields are only considered by the SNP #*+ 1ou can enter the
category groups that you have defined in the SNP -ustomi!ing under +asic Settings @ .aintain
-ategory Croups /sing the category groups, you define which order categories are included in the
"uantity that is available for transport load building
)f you do not enter a value here, the system uses the value from the location master data or the standard
category groups AT$ and ATI
*ot Si!e 4
Auantity
and (ate
(etermina
tion
$ounding %alue . #he #*+ uses the rounding value for building transport loads 5owever, the #*+ first
uses the value that you have defined in the transportation lane, that is, in the lot si!e profile (SNP) or
transportation guideline set (SAP )-5) )f no value is assigned, the #*+ then uses the value specified
here or 5 So that the SNP #*+ can use this rounding value, you must set the relevant indicator in the
SNP -ustomi!ing under +asic Settings @ .aintain Clobal SNP Settings Otherwise, the SNP #*+ uses
the rounding value from the transportation lane
C24C)
Handling unit = . #he #*+ can only pack products with the same handling unit group together in the
same han#ling unit 2./3 )n the SNP #*+, which does not use handling units, this field applies to pallets
a1. #o%erage . #he #*+ considers the ma&imum coverage time during ship$ent upsi6ing #he system
only brings forward as many #eploy$ent stock transfers as are necessary to cover demand within this
time period
Shipment /psiGing . 6or the location product, you specify whether shipment upsi!ing is allowed and
whether is is permitted beyond the ma&imum coverage time period
(oading =roup . #he #*+ considers the loading group for the straight loa#ing loading method
Not Palleta+le . 1ou specify whether the location product may be stacked on pallets )f you set this
indicator, the #*+ considers no pallet positions for this product
(ocation aster Data
1ou make the following settings in the location master data8
)nitial screen
(ocation Type . #his field is relevant if you want to use transportation !ones 6or more
information, see /se of !ransportation 7ones
SNP
ATD $eceipt and ATD Issue . )f you have not defined category groups for the location
product (see above), the SNP #*+ considers the category groups defined here
Transportation (ane aster Data
1ou make the following settings for the means of transport in the transportation lane master data8
Section Field
.eans of T() Profile . 1ou must assign a !"B profile that you created previously
Page 235 of 251
#ransport
(oading ethod . 1ou specify whether you want the #*+ to consider the straight loa#ing oder loa#
balancing loading method
Pull.In HoriGon . )f the #*+ carries out a shipment upsi!ing, it considers the pull%in hori6on
SiG.Desn and Shpmt Thr."al. . )n the Si!(ecsn field, you determine how the #*+ calculates the
value it uses to decide about shipment si!ing #he system compares the base value calculated with
the value you have entered in the Shpmt #hrBal field, and then carries out ship$ent upsi6ing or
#onsi6ing
Product%
specific
transportation
T. (ot Prfl . #his field is only considered by the SNP #*+ 1ou can enter a profile here that you
created in the SNP -ustomi!ing under +asic Settings @ Profiles @ SNP%*ot Si!e Profile
(#ransportation *ane) #he #*+ considers the value defined in this profile (see above)

/se of Transportation Pones
)n the #ransport *oad +uilder (#*+), you can use transportation !ones to group several locations together in one group (that
is, one !one) and use one means of transport to ship !"B ship$ents to multiple locations #he system regards #*+
shipments for multiple locations as one shipment for one location
Acti%ities
)f you want to use transportation !ones, create a location as location type ;::D (transportation !one) or ;::F (stock transfer
point)in the location master data for the -ross%(ocking scenario in the SAP )nventory -ollaboration 5ub (SAP )-5))
After creating the location (type transportation !one or stock transfer point), assign the relevant location in the hierarchy
master data for transportation !ones (select .aster (ata 5ierarchy) 1ou can display location hierarchies in the shuffler for
interactive #*+ planning
)n addition, you must create a transportation lane that has this transportation !one as its destination or source location, and
the same destination or source locations as the locations contained within this transportation !one
)n this instance, the #*+ only considers the #eploy$ent stock transfers or the replenishment orders of locations you have
assigned to the transportation !one
onitoring T() and Deployment Alerts
1ou can use the Alert Monitor to monitor alerts for the !ransport "oa# Buil#er and for ,eploy$ent #o do this, you define
an #*+ alert profile containing a user%specific selection of alerts that are relevant for your planning area
Features
#he following table shows you the alert types available, and a brief description of each one
6or all the alerts e&cept )nvalid (elivery (ate, you can enter priority variants based on critical values
T()!deployment alerts Description
6air share (general)
#he fair share percentage is determined according to the rule specified in the #eploy$ent
heuristic profile (SNP< tab in the location product master) #he system triggers this alert if the
percentages to deploy in order to meet product demand fall below the percentages specified
in the master data
6air share (customers
only)
Same as above, e&cept in this case fair share distribution refers only to customers instead of
locations (for e&ample, B.) customers)
)nvalid shipment
'hen the shipment does not fulfill the parameters for the capacity of the means of transport
(such as volume, weight, and pallet positions) defined in the !"B profile, the system
generates an alert
)nvalid delivery dates 1ou active this alert using the 4SAPAPO4#*+?-5L?(A#0 +Ad)
Acti%ities
2. Select the ob3ects (products, transportation lanes, means of transport) for which the system should determine alerts
3. )f necessary, assign the #*+ alert profile to your Overall Alert Profile, your SCC /ser Profile , or your user by selecting
Advance Planning and Optimi!ation @ Supply Network Planning @ 0nvironment @ -urrent Settings @ Assign Planners
to Alert Profiles from the SAP 0asy Access screen
6or performance reasons, we recommend restricting the number of alerts to be displayed to a minimum
Page 236 of 251
PrioritiGation of Deployment Stock Transfers
#he #ransport *oad +uilder (#*+) uses the results of the deployment run (#eploy$ent stock transfers) to create !"B ship$ents
for multiple products to optimi!e the loading of means of transport )t takes into account the constraints defined in the #*+
profile, such as weight and volume 'hen the #*+ upsi6es or #on si6es shipments, it prioriti!es deployment stock transfers
according to their daysO supply
1ou can use the function for prioriti!ing stock transfers to separate deployment transfers according to demand type, and then
assign priorities to the resulting stock transfers 1ou can then also use these shipment priorities for manual transport load
building, in order to ensure that the important product "uantities are given priority during loading
#he #*+ does not consider shipment priority during a #*+ run
Integration
1ou can prioriti!e only those deployment stock transfers not to be transferred to a connected O*#P system or those to be
transferred as purchase re"uisitions 1ou cannot use this function to process deployment stock transfers that are to be
transferred to the O*#P system as purchase orders (see also the Prere"uisites)
Prere*uisites
#he prere"uisites for deployment stock transfer prioriti!ation are much the same as those for performing a deployment run )t
is essential that the relevant transportation lanes and products are valid Note that the prioriti!ation function only takes into
account the rounding value that you specified at the transportation lane or in the location product master (first, the value from
the transportation lane and, if this does not e&ist, then the value from the product master)$ it does not consider the rounding
profile, nor does it consider ma&imum or minimum lot si!es 6or more information, see +unning the ,eploy$ent .euristic or
+unning ,eploy$ent Opti$i6ation
#he following prere"uisites also apply8
)n -ustomi!ing for Supply Network Planning (SNP), you have set (in -onfigure #ransfer to O*#P Systems) that the
deployment stock transfers you want to prioriti!e are not to be transferred to a connected O*#P system or are to be
transferred as purchase re"uisitions
1ou have performed a deployment run that has created deployment stock transfers
Features
Shipment Priority #alculation
#he deployment stock transfer prioriti!ation function first splits the "uantity of one deployment stock transfer into a ma&imum
of three new deployment stock transfers according to the following categories8
-ategory ;8 Stock transfers for fulfilling current demands and shortages
-ategory <8 Stock transfers for fulfilling demands based on a predefined target stock level
-ategory =8 Stock transfers representing a surplus delivery that e&ceeds the target stock level (based on push
deployment, for instance)
#he original deployment stock transfer is deleted after this splitting
#he system then assigns a priority to the new deployment stock transfers #here is a specific range of priorities available for
each category #he system makes another weighting within this priority range #he assigned shipment priority then indicates
the relative significance of the deployment stock transfer (or product "uantity) in terms of demand fulfillment #he following
table illustrates how the priorities are calculated8
Shipment Priority #alculation
#ategoryC Priority range Formula
-at;8 -urrent demands and shortages : -at;%Prio P :
-at<8 (emands based on the target stock level ; % ;: -at<%Prio P AvStock4#gtStockY;:
-at=8 Surplus delivery e&ceeding the target stock level ;; E 99 -at=%Prio P ;: T #(-at=)4#gtStockY;:
2ey to the ta+leC
AvStock P Available stock at the destination location before current demands and shortages at the destination location
have been fulfilled
#gtStock P #arget stock level
#(-at&) P Auantity of the respective category
)n the priority range of category <, the priority indicates what proportion of the target stock level was already covered
before the stock transfer was received A small proportion indicates a high stock transfer priority (small priority number)
Page 237 of 251
)n the priority range of category =, the priority indicates how much surplus stock the stock transfer is to provide above
the target stock level #he higher the surplus stock, the lower the priority of the stock transfer (large priority number)
/se of the Shipment Priority
#he shipment priority assigned to the deployment stock transfer is displayed for you in the #*+ view of interactive Supply
Network Planning 1ou can use the priority to estimate the relative significance of a stock transfer and uses this information
when manually creating #*+ shipments
Simulation and (ogs
1ou can specify whether you want the prioriti!ation results to be saved immediately or displayed only for simulation
purposes )f you decide to save them immediately, the deployment stock transfers are created in live-ache
)f you run the function for prioriti!ing deployment stock transfers directly, a results log is automatically displayed showing a
list of the deployment stock transfers that have been created )f you run the function in the background, you can access the
results in the spool list 1ou can also display an error log #o do this, choose (isplay *ogs
Acti%ities
1. Perform a deployment run 6or more information, see 2unning the (eployment 5euristic or 2unning (eployment
Optimi!ation
2. Access the deployment stock transfer prioriti!ation function from the SAP 0asy Access screen (Supply Network
Planning @ Planning @ Supply Network Planning in the +ackground @ Prioriti!e (eployment Stock #ransfers)
3. .ake the relevant settings 1ou define the following parameters8
Prioriti!ation hori!on8 1ou specify the number of days over which the system is to take deployment stock transfers
into account for prioriti!ation )f you run the function directly, the time period starts from todayOs date$ if you run it in
the background, it starts from the date specified for the run
(estination *ocations8 1ou can restrict prioriti!ation of deployment stock transfers to specific destination locations )f
you do not specify a location, the system runs prioriti!ation for all the destination locations
6i& (eployment Stock #ransfers8 1ou can specify that you want all deployment stock transfers that were created
after prioriti!ation to be fi&ed (which means they cannot be changed in any subse"uent planning runs) (eployment
stock transfers that had previously been fi&ed are split independently of the setting made in this field and then re%
fi&ed
4. 1ou run the function #he result of this a list of the newly created deployment stock transfers with assigned priorities
0ach original deployment stock transfer can be split into a ma&imum of three new deployment stock transfers
5. 1ou can build transport loads manually in interactive #*+ planning (after a #*+ run, if necessary) Select Advanced
Planning and Optimi!ation @ Supply Network Planning @ Planning @ #ransport *oad +uilder (#*+) from the SAP 0asy
Access screen
Source Determination in Supply Network Planning
#he individual planning procedures in Supply Network Planning (SNP) have very different source determination methods
'hile the SNP heuristic uses :uota arrange$ents and procurement priorities as a basis for choosing the source of supply, the
SNP optimi!er bases its source determination decisions on costs (eployment, on the other hand, uses source determination
not to determine sources of supply but instead to determine the destination locations to which product stock is to be
distributed
Features
SNP Heuristic
#he heuristic determines the sources of supply as follows8
1. #he system first takes into account the defined "uota arrangements
2. )f there are no "uota arrangements available, the procurement priority specified in the Production Process .odel (PP.),
in the Production (ata Structure (P(S), or in the transportation lane is used
3. )f both "uota arrangements and procurement priorities have been defined, the system uses the "uota arrangements
4. )f neither "uota arrangements nor procurement priorities e&ist, the system chooses the most cost%efficient source of
supply
5. )f all sources of supply have the same costs, the general guidelines for source determination apply (see ,eter$ination of
Source of Supply +anking "ist)
)f there is neither a valid transportation lane (for procurement type 6$ e&ternal procurement) nor valid PP.4P(S (for
procurement type 0$ in%house production), the system creates an SNP stock transfer or SNP planned order with no reference
to a source of supply #he same applies if there is no product in the source location of the transportation lane
Page 238 of 251
SNP OptimiGer
Since the SNP optimi!er basically determines the most cost%efficient solution, its sourcing decisions are also cost%based,
which means the optimi!er does not take into account "uota arrangements or procurement priorities
#his also means that you can only influence source determination or, to a certain e&tent, prioriti!e sources by specifying
costs 6or e&ample, you can use production costs to prioriti!e production resources and transportation costs to prioriti!e the
procurement location Note however, that the optimi!er always takes all influencing factors into account (such as storage
costs)
transfer with no reference to a source of supply )f there is no valid PP.4P(S for procurement type 0 (in%house production),
the systemOs behavior is governed by whether or not the SNP8 No Planned Order indicator has been set in the planning
version )f this indicator is set, the SNP optimi!er does not create any planned orders$ if it is not set, the SNP optimi!er
creates planned orders with no reference to a PP.4P(S
6or more information, see Source ,eter$ination 2Opti$i6er3
Deployment
(eployment determines the destination locations to which the product stock is to be distributed #herefore, deployment only
considers transportation lanes as RsourcesR
)n the deployment heuristic, it is cruicial that the corresponding transportation lanes and one of the means of transport
assigned to it are valid in the planning time period #he system first determines all valid means of transport for every
individual period and every target location, and then decides which means of transport to use to create the #eploy$ent stock
transfers Cenerally, the system tries to orientate itself on the results of the SNP run and adopt the SNP%stock transfers
created there )f there a multiple means of transport, or if there are no SNP stock transfers in a period, the system chooses
the means of transport with the shortest mover time )f no valid transportation lanes or means of transport are available, the
system cannot create any deployment stock transfers
(eployment uses #istribution rules to decide which product stock proportions are to be distributed to the different destination
locations$ for e&ample, it uses fair share rules in the event of a supply surplus or push rules if there is insufficient supply to
fulfill demand #hese rules are based partly on "uota arrangements or priorities (distribution priority in the transportation
lane)
Deployment OptimiGer
#he deployment optimi!er generally decides which source locations to distribute available product stock to and which means
of transport to use, based on the lowest total costs and by considering all restrictions (such as transport capacity) )n doing
so, the system may also take detours into consideration
#he deployment optimi!er also decides which proportion of product stock is distributed to which source location based on the
distribution rules
#apacity (e%eling
-apacity leveling performs a source determination if the system decides to switch the source of supply )f the chosen leveling
procedure is heuristic%based, sources are determined in the same way as for the SNP heuristic, if optimi!er%based, source
determination corresponds to that of the SNP optimi!er 5owever, with optimi!er%based capacity leveling, you cannot define
the costs yourself, which means you cannot influence the source determination
anual Source Selection in Interacti%e Planning
)n interactive planning, you can modify planned distribution receipts (SNP stock transfers), confirmed distribution receipts
(deployment stock transfers), and planned production (planned orders) manually6or SNP stock transfers and planned
orders, you receive a ranked list of all possible sources from which you can choose your source of supply 6or more
information, see Source ,eter$ination in 0nteractive Planning
A list of possible destination locations is displayed for deployment stock transfers #hese destination locations are prioriti!ed
according to transportation costs and transport duration #he source of supply (destination location) with the lowest
transportation costs and shortest transport duration is displayed as the RbestR source of supply (and is shown at the top of the
selection list, highlighted in green)
Source Determination &Heuristic '
'hen the heuristic is run in Supply Network Planning (SNP), the system determines the source automatically 1ou use the
following parameters to control this supply source determination8
Auota Arrangements for locations, e&ternal procurement relationships, Production Process .odels (PP.s) and
Production (ata Structures (P(Ss)
Procurement priorities for transportation lanes and PP.s4P(Ss
Page 239 of 251
Features
Source Determination /sing Juota Arrangements
1ou can use "uota arrangements to determine which percentage of the demand should be covered by which supply sources
1ou can create the following types of "uota arrangement8
Auota arrangements for locations
Auota arrangements for e&ternal procurement relationships
Auota arrangements for in%house production (PP.s4P(Ss)
1ou can define "uota arrangements for in%house production by specifying a PP.4P(S 6or e&ample, you can specify that
locations A and + will each fulfill =:a of the demand and PP.4P(S 1 will fulfill >:a
1ou can create "uota arrangements in the Supply -hain 0ngineer or in master data 6or more information, see 8uota
Arrange$ent Maintenance in the Supply -hain 0ngineer documentation
)f you do not define any "uota arrangements, you must determine a procurement priority on the transportation lane, or in the
PP.4P(S )f both "uota arrangements and procurement priorities have been defined, the system takes into account the
"uota arrangements
Source Determination /sing Procurement Priorities
1ou can define priorities for specific supply sources by specifying a procurement priority at the transportation lane or in the
PP.4P(S #he following prere"uisites have to be met for the SNP heuristic to be able take this priority into account8
#he transportation lane or PP.4P(S must be valid
#he order must fall within the lot si!e parameters defined at the transportation lane or in the PP.4P(S (the _6rom` and
_#o` lot si!e)
#he Aggr Planning indicator must be set for the means of transport
#here must be no transportation cycles defined$ this means, the transportation lane is only permitted to go in one
direction and cannot return to the source location )f the system detects one of these transportation cycles, it does not
take into account the procurement priority and instead uses the "uota arrangements that were defined
)f more than one means of transport have been defined for a transportation lane, the system chooses the means of transport
with the lowest costs )f all sources of supply have the same costs, the general guidelines for source determination apply
(see ,eter$ination of Source of Supply +anking "ist)
)f there is neither a valid transportation lane (for procurement type 6$ e&ternal procurement) nor valid PP.4P(S (for
procurement type 0$ in%house production), the system creates an SNP stock transfer or SNP planned order with no reference
to a source of supply #he same applies if there is no product at the source location of the transportation lane
See also8 6or more information, see Production Data structure in SNP, Transportation (ane aintenance in the
Supply -hain 0ngineer (S-0) documentation, and aintain PP in the SAP S-. master data
documentation
Source Determination &OptimiGer'
)f your company has alternative source of supply options with different costs, you can use the optimi!er in Supply Network
Planning (SNP) to solve the following issues8
'here to produce, procure, store, and deliver (for e&ample, it can decide whether to use in%house production or e&ternal
procurement)
'hich products and product "uantities to produce, transport, procure, store, and deliver (product mi&)
'hich resources and which production process models (PP.s) or production data structures (P(Ss) to use (technology
mi&)
'hich locations to transport from and to (for e&ample, production plant%Q distribution center or distribution center %Q
customer)
/nlike heuristic%base# planning and Capable%to%Match planning (-#.), the SNP optimi!er does not base its sourcing
decisions on predefined :uota arrange$ents or rules but instead bases its decisions on costs #he optimi!er uses the
following as possible sources8
PP.s4P(Ss
Page 240 of 251
#he main purpose of optimi!ed source determination using the SNP optimi!er is to define the production locations in such a
way as to reduce the number of stock transfers and associated stock transfer costs
#onstraints
#he SNP optimi!er does not take into account "uota arrangements or procurement priorities 5owever, it can be used to
create "uota arrangements for subse"uent heuristic%based planning runs 6or e&ample, after a longer term optimi!ation%
based planning (monthly, for instance) you can run shorter term heuristic planning runs using the "uota arrangements
created in the optimi!ation planning run as a basis for the heuristic planning runs 6or this, set the .odify "uota
arrangements indicator when you run the optimi!er in the background (see also the 6; help)
Since the optimi!er does not take into account "uota arrangements, it does not support an even distribution of
production over various locations either (regarding resource utili!ation or "uantity%based "uota arrangement) Nor does
it support single sourcing (procuring a product from only one preferred source)
#he optimi!er does not take into account e&ternal procurement relationships as sources of supply$ that is, no scheduling
agreements, contracts, nor purchasing info records )f you have assigned a means of transport to the transportation lane
generated from the e&ternal procurement relationship, the optimi!er takes this transportation lane into account
5owever, the optimi!er does not create any orders for scheduling agreements or contracts during planning (it only takes
into account e&isting orders as fi&ed orders)
Prere*uisites
#he prere"uisites for source determination are the same as those for general optimi!ation%based planning8
/sing #osts to #ontrol Source Determination
Since the SNP optimi!er simultaneously takes into account all the conditions of a model to determine an optimal (most cost%
effective) solution, it is generally only possible to influence its choice of sources by using costs 6or e&ample, you can use
costs to prioriti!e sources by reducing the production costs at your preferred location 5owever, remember that the optimi!er
always takes all influencing factors into account8
/sing Production #osts to PrioritiGe Production $esources
1ou can influence the optimi!erOs decision regarding which location and resources to use for production by defining
corresponding production costs in the PP.4P(S 6or e&ample, if you want to define priorities for three different PP.s4P(Ss,
you can specify the lowest production costs for your highest priority PP.4P(S, higher costs for the PP.4P(S with medium
priority, and the highest costs for the PP.4P(S with lowest priority #o do this, define single%level production costs or a cost
function in the PP.4P(S
Note however that in addition to taking into account production costs when making its decision, the optimi!er considers the
costs for storing the PP.4P(S products and the available capacity of the resources re"uired for the PP.4P(S
/sing Transportation #osts to PrioritiGe the Procurement (ocation
1ou can influence the optimi!erOs decision regarding which locations to procure from, by defining corresponding costs in the
transportation lane 6or e&ample, if you want to define the priorities of two different procurement locations, enter lower
transportation costs for the transportation lane of your preferred location than those for the other transportation lane
#ransportation costs consist of the means of transport costs (costs from the .eans of #ransport section of the transportation
lane) and the product%specific means of transport costs (from the Product%Specific .eans of #ransport section)
Note however that in addition to taking into account transportation costs when making its decision, the optimi!er also
considers other influencing factors, such as the storage costs and production costs of the location
transfer with no reference to a source of supply )f there is no valid PP.4P(S for procurement type 0 (in%house production),
the systemOs behavior is governed by whether or not the SNP8 No Planned Order indicator has been set in the planning
version )f this indicator is set, the SNP optimi!er does not create any planned orders$ if it is not set, the SNP optimi!er
creates planned orders with no reference to a PP.4P(S
Additional Planning Functions
#he following topics describe additional planning functions that you can use8
Process Chains in SCM
Page 241 of 251
Application "ogs
Application "ogs for Opti$i6ers
,elete !ransaction ,ata
Monitoring Macro%,epen#ent Alerts 2,P an# SNP3
Authori!ation in Supply Network and (emand Planning
Process #hains in S#
As of 2elease S-. >;, you can use this +usiness )nformation 'arehouse (+') function together with S-. transactions )t
allows you to set up chains of background 3obs 6or instance, in (emand Planning you could program a chain that uploads
data from a data source to an )nfo-ube, generate any new characteristic value combinations, upload the data from the
)nfo-ube to a planning area, carry out a forecast, and release the data to SNP 0ach step should only be carried out if the
previous step finished without errors
6or a general description of process chains, see the +' documentation Process Chains and subordinate documentation
Integration
All other process steps that are available in process chains in the +usiness )nformation 'arehouse are also available here
#his means for instance that you combine +' processes with S-. processes in one process chain 1ou can also include
'orkflow processes in your chains
Prere*uisites
)n order to use the graphic interface for process chains, users must install the SAPC/) +' Add%on on their P-s
Features
Several S-. process types have been included in the process chain maintenance tool
S# Demand Planning
=enerate characteristic %alue com+inations. 6or details of this process, see 5enerating Master ,ata for ,e$an#
Planning
Add +ill of material information. 6or details of this process, see Forecasting ith Bills of Material
InitialiGe planning area &#reate time series o+,ects'. 6or details of this process, see Planning Area Functions in
S?,P A#$inistration
DeinitialiGe planning area &Delete time series o+,ects'I 6or details of this process, see Planning Area Functions in
S?,P A#$inistration
DP +ackground processing 6or details of this process, see 6orecast 0&ecution with .ass Processing
/se this process type to add (P background 3obs to a process chain
#he following activities can be carried out in a (P background 3ob8
0&ecute a forecast
0&ecute macros
2elease from (P to SNP
2elease to 02P
#alculate proportional factors. 6or details of this process, see 5eneration of Proportional Factors
(oad data from Info#u+e. 6or details of this process, see "oa#ing ,ata fro$ an 0nfoCube into a Planning Area and
Copy Manage$ent
#opy planning %ersion. 6or details of this process, see Copy Manage$ent
Data $ealignment. 6or details of this process, see +ealign$ent an# Copying of ,ata
Time series consistency check. 6or details of this process, see Consistency Checks for Planning Areas
Ad,ust time series. 6or details of this process, see A#just$ent of !i$e Series Objects
#haracteristics.)ased ForecastingC $ounding of Time Series "alues. 6or details of this process, see
(isaggregation and 2ounding in -+6 #his function is only available for characteristics%based forecasting
Direct release from an InfoPro%ider to Supply Network Planning 6or details of this process, see +elease fro$ an
0nfoProvi#er to SNP
Page 242 of 251
Direct release from an InfoPro%ider to Supply Network Planning. 6or details of this process, see +elease fro$ an
0nfoProvi#er to an -+P Syste$
S# Promotion Planning
/pdate Promotions
Activate4(eactivate Promotions
-opy Promotions
-hange Promotions
6or details of these processes, see Pro$otion Manage$ent
S# Supply Network Planning
SNP heuristic. 6or details of this process, see 5euristic%+ased Planning
SNP OptimiGation. 6or details of this process, see Optimi!ation%+ased Planning
#apacity le%eling. 6or details of this process, see -apacity *eveling
Deployment. 6or details of this process, see (eployment
Deployment optimiGation. 6or details of this process, see (eployment
Transport (oad )uilder &T()'. 6or details of this process, see #ransport *oad +uilder
Safety Stock Planning. 6or details of this process, see 0&tended Safety Stock Planning
SNP Disaggregation. 6or details of this process, see SNP ,isaggregation
$elease to Demand Planning. 6or details of this process, see +elease of Supply Netork Plan to ,e$an# Planning
Parallel #onsumption in the )ackground. 6or details of this process, see -onsumption using "26- or
+ackground Processing
Planned Independent $e*uirement $eorganiGation L Ad,ust $e*uirements. 6or details of this process, see
Ad3ustment of Planned )ndependent 2e"uirements
=eneration of Forecast. 6or details of this process, see Ceneration of Planned )ndependent 2e"uirements
#on%ert aster Data Jueue &(e%el 5' for SNP.
#his process enables you to plan the calculation of changes to master data made after initiali!ing the planning version
as a separate step /sually, the system updates the master data "ueue automatically at the start of a planning run
5owever, in certain cases (for performance reasons, for e&ample), it can make sense to carry out this process
seperately 6or more information, see the relevant 6; 5elp
erge Planning "ersions &SNP'. 6or details of this process, see Planning Bersion .erge
SNP Aggregation. 6or details of this process, see SNP Aggregation
Single.(e%el Supply and Demand apping. 6or details, see Single%*evel Supply and (emand .apping
$esource Disaggregation. 6or details, see +esource ,isaggregation
S# #apa+le.to.atch &#T'
01ecute #T Planning. 5ere you assign a -#. profile directly to the process 6or details of this process, see
Capable%to%Match Planning 2C!M3
S# Planned Independent $e*uirements
Parallel #onsumption in the )ackground. 6or details of this process, see -onsumption using "26- or
+ackground Processing
Planned Independent $e*uirements $eorganiGation Ad,ust $e*uirements. 6or details of this process, see
Ad3ustment of Planned )ndependent 2e"uirements
=eneration of Planned Independent $e*uirements. 6or details of this process, see 5eneration of Planne#
0n#epen#ent +e:uire$ents
S# Alert onitoring
Alert Determination in the )ackground. 6or details of this process, see Alert ,eter$ination in the Backgroun#
Page 243 of 251
S# "ersion #opy
"ersion #opy. 6or details of this process, see Creating1 Copying1 an# ,eleting Mo#el<Planning 4ersion
Additional Functions
#onte1t enu
Several functions are available in the conte&t for processes Some of these are available for all process types, for e&ample
.aintain process variant
0&change process variants
(isplay all 3obs with the process chain
Specify that a message is sent to recipient when a process is completed
(elay the start of a process for a specified length of time
2emove a process from the chain
5owever, other functions depend on the process in "uestion 6or Cenerate characteristic combinations, for instance, you can
display the e&isting characteristic combinations )f the transaction involved has its own log, you can also call up this log from
here
Application (ogs
'hen you e&ecute planning functions in Supply Network Planning (SNP) in the background (mass processing), the system
automatically generates an application log #his log contains planning results, such as data for the planned and stock
transfers created, as well as error, warning, and information messages
1ou can access this log using the central Application *ogs function 1ou can also display the log directly in the respective
planning function
Application logs are generated by the following SNP planning functions8
0&tended Safety Stock Planning
SNP 5euristic
-apacity *eveling
(eployment 5euristic
#ransport *oad +uilder (#*+)
SNP Aggregation
SNP (isaggregation
2esource (isaggregation
Single%*evel Supply and (emand .apping
#he separate Optimi!er *og (ata function is available for accessing logs for optimi!ation%based planning functions in Supply
Network Planning, such as the SNP optimi!er, and deployment optimi!er 1ou can, of course, access these logs using the
Application *og function 5owever, in the Optimi!er *og (ata function, you get e&tensive information, such as the costs of
the solution determined by the system 6or more information, see Application "ogs for Opti$i6ers
Features
#he central Application *ogs function provides an overview of the generated logs 6or e&ample, you can display the
following data for each log8
)nput data for the planning run
-ustomi!ing settings and +Ad)s that are relevant for the planning run
.essages that appeared during the planning run
Planning results, such as the planned orders and stock transfers created
#he messages are displayed according to the message type specification (termination message, error message,
warning message, and information message) 1ou can sort the messages by message type or in ascending or
descending order 1ou can also set different filters$ to display by message type or message te&t, for e&ample
#he planning results differ depending on the planning function 6or e&ample, the following data is displayed8
01tended safety stock planning8 Planned safety stock per location product and period, as well as important
location product master data, such as safety stock methods, service level, and target daysO supply
SNP heuristic8 (etailed information on the SNP planned orders, SNP stock transfers, and product substitution
orders
Page 244 of 251
#apacity le%eling8 Auantities per period and resource utili!ation before and after capacity leveling, as well as
output product surplus and shortage situations
Deployment heuristic8 (etailed information on the deployment stock transfers created, such as source location,
target location, and means of transport
Transport (oad )uilder8 (etailed information on the deployment stock transfers not processed and the #*+
shipments created
SNP aggregation8 (etailed information on the location products and orders to be processed
SNP disaggregation8 (etailed information on the planned orders and stock transfers to be disaggregated
$esource disaggregation8 (etailed information on the resources to be processed and created orders
Single.le%el supply and demand mapping8 (etailed information on the location products to be processed and the
fi&ed SNP stock transfers created
)f you want to improve performance and reduce the amount of memory space used, or if you do not want detailed
information to be displayed in the application log, you can deactivate the (etailed 2esult indicator on the initial screen of
the planning function #he log then only contains the number of generated orders, for e&ample, and not detailed data for
the individual orders
On the initial screen of the planning function, you can also specify how long you want the log to be stored for #he
default value for storage is 84 days 1ou can overwrite this value with anything between 5 and 333days
Once this specified period has come to an end, the log is flagged for deletion 1ou can then either delete it manually
using transaction S(=7 or automatically using the delete program 1ou can also delete the log before the end of this
period
Acti%ities
1. 6rom the SAP 0asy Access screen, choose Advanced Planning and Optimi!ation Supply Network Planning @
2eporting @ Application *ogs, or select (isplay *ogs on the initial screen of the planning function
2. #he SNP4-#.8 (isplay Application *ogs screen appears )n the Application field, select which planning function you
want to display the logs for 1ou can also make additional settings, such as user name 5owever, you can also leave
these fields blank
)f you set the Only +ackground 2uns indicator, the system only selects application logs generated using background
processing (that is, if you scheduled the planning run as a background 3ob)
3. -hoose 0&ecute
4. #he SNP 5euristic8 Application *og screen appears
#he individual logs are displayed on the left%hand side of the screen )n order to display log data, the following options
are available8
)f you select a log and choose #echnical )nfo, you see additional detailed information about the log, such as its
e&piration date and the specification as to whether it can be deleted before this e&piration date
)f you double click on a log, the messages are displayed on the right%hand side of the screen 1ou can then use the
toolbar pushbuttons to sort and filter these messages
)f you select Available (etail in the right%hand side of the screen in the (etail column, the detailed information is
displayed in the lower part of the screen
SNP Optimi!er
Page 245 of 251
Features
#he Optimi!er *og (ata function provides an overview of the generated logs Amongst other things, the list of logs
*og status
*og creator
order creation)
*og e&piration date
)f you double click a log or choose (isplay *og, you receive the following data and sub%logs for the log
Input Parameter. -ontains the settings that you made on the initial screen for the planning function
(ocation Products. -ontains the location products selected for the optimi!ation run
Deletion Time Period. Specifies a time period in which the system deletes e&isting planned orders and stock
transfers before actual optimi!ation
Input (og. -ontains the input data considered by the system during the optimi!ation run (that is, master data and
transaction data) #he data is divided into a number of tables (such as 0#?*O-.A#) 1ou can display the content
of these tables on the right%hand side of the screen 6or more information, see Opti$i6ation 0nput "og
$esults (og. -ontains all results of the optimi!ation run, such as planned orders, stock transfers, resource
consumption, costs, and penalty costs #he data is divided into a number of tables (such as 0#?P2O.O) 1ou can
display the content of these tables on the right%hand side of the screen
$esult Indicators. -ontains indicators that display the "uality of the optimi!ation solution, such as service level and
shortfall of safety stock 6or more information, see +esult 0n#icators
01planations. -ontains the results of an e&planation tool run (see below)
01tended $esults (og. )n this log, you can display the results of the optimi!ation run in the interactive SNP
planning form
essage (og. -ontains error messages, warning messages, and information messages generated by the system
during the optimi!ation run #hey are ordered according to meaning, that is, whether they refer to the optimi!ation
run settings or to the three main steps of the run
Trace File. All individual optimi!ation run steps are logged in this te&t file )t is saved on the optimi!ation server, but
you can also download it to your own computer
#osts. -ontains detailed information about the costs of the solution determined by the optimi!er 6or more
information, see +esulting Costs of Opti$i6ation
Solution Juality. -ontains the costs of the best solution determined by the optimi!er up to the time displayed )f
you used a decomposition method, you can also relate the costs the partial problem solved up to this time
1ou can also download the input log and the results log to your own computer #o do this, choose (ownload )nput
*og or (ownload 2esults *og #he logs are then saved in 20*A#)O. te&t format
Page 246 of 251
)f you select a log and choose 0&plain, you go to the 0&planations of SNP Optimi!ation 2esults screen 6rom this
screen you can e&ecute the e&planation tool which e&plains two important e&ceptional situations of an optimi!ation run8
non%deliveries and shortfall of safety stock
Delete Transaction Data
1ou use the (elete #ransaction (ata function to delete transaction data that was planned in SAP APO from the SAP APO
system and a connected SAP 24= system )t is generally not recommended to use this function in the production system$
instead, you should use it for testing and correction purposes Apart from a few e&ceptions, it is not necessary to run the
function in the production system 6or e&ample, you do not need to run this function before an SNP heuristic run, SNP
optimi!ation run, or real%time deployment run because the system automatically deletes all orders from previous planning
runs during these planning runs
1ou can run the function in the production system under the following (e&ceptional) circumstances8
#o delete #eploy$ent stock transfers after a deployment run before you perform a new SNP run Otherwise, the
deployment stock transfers would not be modified during the SNP run 5owever, this only applies if you specified in
Supply Network Planning -ustomi!ing that the deployment stock transfers are to be transferred to the SAP 24= system
as purchase re"uisitions (not purchase orders)
#o periodically delete stock in transit "uantities during the Bendor%.anaged )nventory (B.)) process
1ou can use this function to delete data from the time series live-ache (by specifying planning areas, planning ob3ect
structures, and key figures) and to delete orders from the order live-ache (by specifying A#P categories or order numbers,
for e&ample) Note, however, that you can only delete SNP orders (and not PP4(S orders)
#o access the function from the SAP 0asy Access menu, choose Supply Network Planning @ 0nvironment @ (elete
#ransaction (ata
Integration
1ou can also delete the data in SAP 24= by using the APO -ore )nterface (-)6) to transfer the deletion activities to SAP 24=
Features
#his function provides four main data deletion options8
Delete data +y key figures. 'ith the Select Ob3ects +y Ley 6igures option, you can delete data from both the time
series live-ache and the order live-ache (by specifying key figures that contain time series or order data)
5owever, time series key figures can only be deleted if they have been assigned with key figure semantic ::; or
have not been assigned a key figure semantic
-hoose a planning area and, if necessary, a planning ob3ect structure plus one or more key figures )f you only
select a planning area and do not select any key figures, the system deletes all the key figure data from this
planning area 5owever, you can significantly improve performance by specifying specific key figures
Delete orders +y ATP categories. 'ith the Select Ob3ects +y -ategories option, you can delete orders from the
order live-ache by choosing one or more A!P categories 5owever, note that you cannot delete all order types (see
below)
Delete orders +y order num+ers. 'ith the Select Ob3ects +y Order Numbers option, you can delete orders from
the order live-ache by choosing one or more order numbers 1ou can specify order numbers from both SAP APO
and SAP 24= for deletion
Delete orders for a PP. )f you wish to delete a PP. that still has orders assigned to it, you first have to delete the
assigned orders 1ou use the Select Ob3ects +y PP. (All Planning Bersions) option to delete all the orders for a
specific PP. in all planning versions to which this PP. has been assigned
1ou can significantly improve performance of the deletion report by specifying the products and locations whose data
you want to delete 1ou can also improve performance by specifying a hori!on for the data to be deleted
1ou can select specific products and locations by specifying the planner to which they are assigned
#o further restrict the selection of location products, you can specify a consumption group As a result, the system only
deletes orders for location products that were assigned with this consumption group
1ou can improve performance by specifying the number of orders and location products to be processed by the system
at the same time #o do this, choose Performance and enter the package si!e #he default value if ;:: 1ou can
increase this value if you are using a larger live-ache 5owever, you can only determine the optimum value by testing
1ou can either delete data in SAP APO only or transfer the deletion activities to SAP 24= using the -ore )nterface #o
delete data in APO only, go to the (elete #ransaction (ata screen area and set the Only in APOindicator #o also delete
data in 24=, set the )n 24= and APO indicator
Note that only deleting orders in SAP APO can result in inconsistencies if these orders are linked to orders in a SAP 24=
system 5owever, it can be advisable to only delete orders in SAP APO if you no longer want to plan orders in SAP
APO and instead want to use SAP 24= e&clusively
Page 247 of 251
Orders can only be deleted in SAP APO and SAP 24= simultaneously in the active version ::: because -)6 can only be
used to transfer data for this version (ue to -)6 limitations, you cannot delete orders from the following categories 1ou
should delete these orders directly in the 24= system8
AA % Process order (open)
A+ % Process order (released)
A- % Production order (open)
A( % Production order (released)
+6 % Purchase order delivery schedule line
+C % Purchase order returns item
+) % Stock transport order
+* % -ustomer "uotation
+. % Sales order
01ecution ode
1ou can run the function in test mode, dialog mode, or as a background 3ob8
(ialog mode or background 3ob8 #he delete operation is run immediately or in the background -hoose (with "uick
info 0&ecute) or Program @ 0&ecute in +ackground
1ou can then view a log (see below) by choosing *og )f you run the report in dialog mode, the associated messages
are also displayed in the status bar in the lower screen area
#est mode8 #he delete operation is not run immediately$ you are first shown a log of the data to be deleted 1ou can
then check this data and decide whether you really want to delete or whether you want to cancel the process )f you
choose (elete, the data is deleted )f you choose (with "uick info +ack), the data is not deleted
#o activate test mode, set the #est .ode indicator
Deletion (og
(epending on the e&ecution mode chosen, the generated log contains information either about the data that has been
deleted or that is to be deleted #he individual logs are displayed on the left%hand side of the screen, listed by creation date,
time, and user
#he individual messages for each log are displayed on the right%hand side of the screen with creation date and time 1ou can
display detailed information about the logs and messages
#he messages are displayed with the message type specification (termination message, error message, warning message,
and information message)1ou can sort the messages by message type or in ascending or descending order 1ou can also
set different filters$ by message type or message te&t, for e&ample
#he following standard messages are displayed8
Selection parameters chosen by the user
#he number of key figures that were included
#he number of location products that were included
#he number of orders that were deleted for the selected planning version
#he total number of deleted ob3ects
A description of each deleted ob3ect showing the following information (choose with "uick info (etail e&ists)8
Planning version
Product
*ocation
A#P category and category type
Order number
Auantity
#he order date and time
1ou can also specify for how long the generated log is to be stored #o do this, go to the (elete #ransaction (ata screen and
enter the number of days in the *og Availability field
Page 248 of 251
onitoring of acro.Dependent Alerts &DP and SNP'
1ou can use the Alert Monitor to monitor macro%dependent alerts for ,e$an# Planning 2,P3, for Supply Netork Planning
2SNP3, and for ,e$an# Co$bination #o do this, you define an S(P alert profile containing a user%specific selection of
alerts that are relevant for your area of responsibility
Features
)n Supply and (emand Planning, the system differentiates between dynamic alerts and database alerts 1ou can create your
own dynamic alerts or database alerts for use with macros
Dynamic alerts reflect the current planning situation that is stored in the SAP live-ache
6or performance reasons, we do not recommend that you use dynamic alerts for large numbers of alerts
Data+ase alerts show the planning situation as it was during the planning run or last e&ecuted macro 'hen dealing
with large data volumes, use the database macro to perform a planning run
)n interactive planning in (P and SNP, you can compare dynamic and database alerts with each other
6or more information about using macros in (P and SNP, see ,e$an# Planning, Planning Book, and A#vance#
Macros
5ere are two overviews #he first overview lists the S(P alert types and the second overview lists the demand combination
alert types
O%er%iew of SDP Alerts
Alerts Description
2esource overload in bucket
1ou define the capacity of bucket resources in the resource master by "uantities (for
e&ample, by transportation capacity) or by daily rates (;,::: pieces per day) )f a bucket
resource is overloaded, the system generates an alert 1ou can maintain priority variants
for this alert based on critical values
)nsufficient resource
utili!ation in bucket
As above
2esource utili!ation in
bucket P ;::a (dyn alert)
#his warning alert is triggered if the limit has been reached
2e"uirement undercoverage
#his alert is triggered if the "uantity that was calculated during the SNP run cannot be
delivered on time #his shortage can result from a limited capacity at production resources,
storage resources, transportation resources, or handling resources
#arget stock level
e&ceeded4shortfall
An error alert is triggered if the inventory is below or above the "uantity of a product
necessary to fulfill demand for a specified dayOs supply #he target daysK supply is defined
in the lot si!e profile of the product master #he system creates warning and information
alerts dependent on the threshold values you have defined
Safety stock shortfall
An alert is triggered if the safety stock falls below the safety stock designated in the lot si!e
profile of the product master #he system creates warning and information alerts dependent
on the threshold values you have defined
O%er%iew of Demand #om+ination Alerts
Alerts Description
#emporal violation in demand combination
#his alert is triggered if the system e&ecutes an activity and does not
determine any values that it can transfer to the combined key figure
Auantity violation in demand combination
#his alert is e&ecuted during a condition check #his alert is dependent on
the setting you made for the condition 1ou can specify that you want an alert
to be triggered in the #2/0 case, in the 6A*S0 case, or in both cases
Actions
1. )f re"uired, create new alert types or change e&isting ones in the Alert .onitor window by choosing 0nvironment @
-hange (atabase Alert #ypes for (P4SNP or -hange (ynamic Alert #ypes for (P4SNP
3. Select the planning book and then data views for all the database or dynamic alerts for which you want the system to
determine alerts
)f you want to choose all the database alerts for a planning book, enter a blank row in the selection area for data views
Page 249 of 251
4. #o assign the S(P alert profile, if necessary, to your overall alert profile, your SCC user profile, or your user, in the
(emand Planning or Supply Network Planning menu, choose 0nvironment @ -urrent Settings @ Assign Planners to
Alert Profiles
)f you access the Alert .onitor directly, specify the planning version you want to evaluate and the time frame for alert
selection in the overall alert profile
6or performance reasons, we recommend that you restrict the hori!on and number of alerts to be displayed to a
minimum
AuthoriGation in Supply Network and Demand Planning
Supply Network Planning and (emand Planning (S(P) use the standard SAP authori!ation functionality to control access to
applications #he SAP Authori6ation Concept topic provides an overview of the ob3ects involved 6or more information
about authori!ations, see /sers an# +oles 2BC%S-C%/S+3 and its related documentation, as well as Checking
Authori6ations
See below for an overview of the authori!ation ob3ects used in S(P and other information specific to authori!ations in S(P )t
assumes that you are familiar with the basic principles involved (see above)
AuthoriGation O+,ects
#he following authori!ation ob3ects are used in APO S(P #hey are also available for customer enhancements #hese
ob3ects are described in more detail (in particular, the fields that are available together with their possible values) in the
online documentation in the relevant maintenance transactions
acros
#KAPOKA# % 0&ecution of macros
#KAPOK AD"% .aintenance of macros
#KAPOKAD"N% .acro name check
aster Data
#KAPOK(O# % .aster data, location
#KAPOKP$OD % .aster data, product
#KAPOK$0S % .aster data, resource
#KAPOKT(AN % #ransportation lanes
Planning AreaI )ook
#KAP4KP) % Planning book
#KAPOKS0(8 % Selections in planning books
Authori!ation ob3ects -?APO?S0*0 (2elease <:) and -?APO?S0*< (2elease =: up to Support Package 9) still e&ist
in the system #hey are however obsolete )f -?APO?S0*< has been assigned to a profile, set all field values to RYR
#KAPOKIO)O E Ley figure
#KAPOK#PB E -opy function in data realignment
#KAPOK $(= E 2ealignment, maintain realignment table
=eneral Demand Planning
#KAPOKDPP$ L Product
As opposed to #KAPOKP$OD,which checks the authori!ation for the master data ob3ect product, #KAPOKDPP$
checks against the values of the characteristic that you have defined as the product in the master planning ob3ect
structure #he location is not re"uired in the authori!ation check, which means that the same user can work
independently of a location in (P and restricted to a location in SNP
Forecast
#AKAPOKP$PF E 6orecast profile
#AKAPOKTSID E #ime series (weighting profile, and so on)
Promotion
#KAPOKP$O E Promotion
(ifecycle Planning
#KAPOK(I20 E *ifecycle profile
Page 250 of 251
SDP Functions
#KAPOKF/N % 6unctions in S(P
=eneral APO Functions
#KAPOKOD % .odel
#KAPOK"0$S % Bersion
AuthoriGation #hecks for #haracteristics in SAP Net-ea%er /sage Type )usiness Intelligence &)I'
6or more information, see /sing the B0 Authori6ation Concept in ,e$an# Planning
AuthoriGation #hecks in SDP
All authori!ation checks in S(P are performed by the function module 4SAPAPO4.-P?P02.)SS)ON?-50-L< for
individual data ob3ects and 4SAPAPO4.-P?P02.)SS)ON?S0*0-# for a range (table) of ob3ects such as products,
locations, or planning books #his second function module incorporates the first one
)f you want to ad3ust the result of the check, or program your own authori!ation check, you can do so by using user e&it
4SAPAPO4SAP*.-P2?:;D in function group W(./S02
Interacti%e Planning
-orking with Selections
Authori!ation for working with selections is checked using ob3ect -?APO?6/N and the functions -?S0*-#)ON and
-?S0*O2C )f the user has not been assigned the -?S0*-#)ON function, the selection icon does not appear when they
open a planning book As a result, the user cannot use the shuffler to make their own selections, but have to choose
predefined selections from the list of selections
#he -?S0*O2C function permits the user to administer selections, that is to save selections and assign them to users
#he system checks the authori!ations for both of these functions when the user calls up )nteractive Planning
Indi%idual Selections
#he user re"uires authori!ation via ob3ect -?APO?6/N for functions -?S0*0 and S?S0*0 to e&ecute a KfreeK selection #o
load a saved selection, they must have authori!ation for function S?S0*0 and for authori!ation ob3ect -?APO?S0*=
(-?APO?S0*<), and they need the relevant selection
(uring the transfer of the ob3ects contained in the selection, the system first checks the authori!ation for the selected version
(-?APO?B02S) )n (emand Planning, authori!ation checks are only performed for the ob3ects version (-?APO?B02S),
product (-?APO?P2O(), and location (-?APO?*O-) for selections in the standard system )n SNP, you can check the
ob3ects version (-?APO?B02S), product (-?APO?P2O(), location (-?APO?*O-), location product (-?APO?P2O(),
resource (-?APO?20S), and transportation lane (-?APO?#*AN) Additional authori!ation checks, in particular those
concerning other characteristics in the selection (such as sales organi!ations in (P) are not provided in the standard system
1ou can run additional checks if necessary by using the user e&it for authori!ations 'ith this user e&it or the +Ad) method
KS0*0-#)ON?-50-LK (+Ad) K4SAPAPO4S(P?S0*0-#O2K), you can, for e&ample, force a user to make a selection for a
certain characteristic (uring the authori!ation check in (P, only the ob3ects specified in the selection condition are checked
(uring these authori!ation checks for ob3ects, the activity K(isplayK (:=) is used 6or the ob3ects mentioned above (in (emand
Planning product and location, in SNP product, location, location product, resource, and transportation lane), the system
carries out an authori!ation check in the S(P selector for the hit list entries )f the user does not have at least display
authori!ation for an ob3ect, this ob3ect is not displayed in the hit list
(oading Data in Interacti%e Planning
'hen you actually load one or more ob3ects, the permitted activities are checked )f you are in change mode, the activity
K0&ecuteK(;F) is used for all checked authori!ation ob3ects )f no change authori!ation is available, the corresponding checks
are continued with the activity K(isplayK(:=) #he transaction switches to display mode if the data may only be displayed )f no
authori!ation for displaying the data e&ists, an appropriate error message appears No data is displayed
)ackground Processing
'hen the system carries out authori!ation checks in background 3obs, it checks the authori!ations of the user who created
the 3ob 1ou can use the method S0#?/S02 in +Ad) 4SAPAPO4S(P?+A#-5 to assign the 3ob to another user
)f you have activated the +' authori!ation concept, the system checks all selected characteristic value combinations before
it starts any other processes )f the user has no authori!ation for one characteristic value, the system stops the complete 3ob
and writes the corresponding messages into the log 1ou can check that you (or the background 3ob user defined in the
+Ad)) have the necessary authori!ations when creating the planning 3ob by choosing the icon with the "uick info -heck
Authori!ation for -haracteristic Balues
Page 251 of 251

Supply Network Planning

Hochgeladen von

Dokumentinformationen

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

Supply Network Planning

Hochgeladen von

Copyright:

Verfügbare Formate

Advanced Planning and optimizer Supply Network Planning

Supply Network Planning

a. 6irst create your supplier as a location in your model

Das könnte Ihnen auch gefallen