Apo SNP

Carlsberg IT A/S 457425880.
doc
457425880.doc
Carlsberg IT A/S
Business Application
29-01-2020 Page 1 of 107

Carlsberg IT A/S 457425880.doc
Table of Content
1 Change History.............................................................................................................................................. 6
2 Overview of SNP..................................................................................................................................... 7
2.1 Purpose.............................................................................................................................................7
2.2 Overview..........................................................................................................................................7
2.2.1 SNP Optimizer............................................................................................................7
2.2.2 SNP Deployment........................................................................................................7
2.2.3 Transport Load Builder (TLB)......................................................................................8
3 SNP Configuration.................................................................................................................................. 9
3.1 Optimizer servers..............................................................................................................................9
3.2 Planning area..................................................................................................................................10
3.2.1 Customizing.............................................................................................................. 10
3.2.2 LiveCache reorganisation.........................................................................................13
3.3 Version management (Active and inactive).....................................................................................14
3.3.1 Current versions........................................................................................................14
3.3.2 Create version.......................................................................................................... 15
3.3.3 Copy version............................................................................................................. 16
3.4 Planning books...............................................................................................................................17
3.4.1 Assignment of planning book to user........................................................................17
3.4.2 Define time buckets to use in planning views............................................................17
3.4.3 CDK_SNP................................................................................................................. 18
3.4.4 DEPLOY_STOCK.....................................................................................................22
3.4.5 PURCHASE_TLB.....................................................................................................23
3.4.6 Other planning books assigned to SNP Planning area..............................................23
4 Integration between APO and R/3....................................................................................................... 24
4.1 APO customizing............................................................................................................................24
4.1.1 Publications.............................................................................................................. 24
4.1.2 Transfer with change pointers...................................................................................24
4.2 Integration models..........................................................................................................................26
29-01-2020 Page 2 of 107

4.3 Mismatch between APO and R/3....................................................................................................26
4.3.1 Post processing monitor...........................................................................................26
4.3.2 CIF comparison.........................................................................................................26
4.3.3 Realign sales orders in R/3 and APO........................................................................27
5 Release Forecast to SNP...................................................................................................................... 30
5.1 Release............................................................................................................................................30
5.2 Forecast consumption.....................................................................................................................30
5.2.1 SNP Requirements Strategies..................................................................................30
5.2.2 Forecast Consumption..............................................................................................31
6 Safety Stock Planning.......................................................................................................................... 33
6.1 Safety stock strategies.....................................................................................................................33
6.1.1 Calculations based on forecast accuracy and service level......................................33
6.1.2 Fixed safety stock copied from product master.........................................................34
6.1.3 Safety stock calculated from original forecast...........................................................34
6.2 Country specific safety stock calculation........................................................................................34
6.2.1 Denmark................................................................................................................... 34
6.2.2 Norway...................................................................................................................... 39
6.2.3 Sweden..................................................................................................................... 41
7 Optimizer profiles................................................................................................................................. 47
7.1 Cost profile.....................................................................................................................................47
7.2 Optimizer profiles...........................................................................................................................49
7.2.1 SNP optimizer profiles...............................................................................................49
7.2.2 COPT10 parameters for SNP optimizer profiles........................................................52
7.2.3 Deployment optimizer profiles...................................................................................52
8 SNP optimization.................................................................................................................................. 53
8.1 Preconditions and optimization flow..............................................................................................53
8.1.1 Preconditions............................................................................................................ 53
8.1.2 Optimizer flows......................................................................................................... 53
8.2 Linear optimization.........................................................................................................................55
29-01-2020 Page 3 of 107

8.3 Discrete optimization......................................................................................................................57
8.4 Order conversion to PP/DS.............................................................................................................58
8.5 Optimizer Batch jobs......................................................................................................................59
8.5.1 Denmark................................................................................................................... 59
8.5.2 Norway...................................................................................................................... 60
8.5.3 Sweden..................................................................................................................... 61
8.6 Inactive versions.............................................................................................................................64
8.6.1 Version 100............................................................................................................... 64
8.6.2 Version 101............................................................................................................... 64
8.6.3 Other versions.......................................................................................................... 65
9 Special SNP functionality..................................................................................................................... 66
9.1 Planning with production quarantine..............................................................................................66
9.1.1 Functionality in brief..................................................................................................66
9.1.2 Planning flow............................................................................................................ 66
9.2 Transport load builder for SNP orders............................................................................................68
10 Deployment Optimization................................................................................................................. 70
10.1 Deployment optimization................................................................................................................70
10.1.1 Optimizer run............................................................................................................ 70
10.1.2 Maintain category groups..........................................................................................71
10.2 Deployment optimizer batch jobs...................................................................................................72
10.2.1 Denmark................................................................................................................... 72
10.2.2 Norway...................................................................................................................... 74
10.2.3 Sweden..................................................................................................................... 75
10.3 Transport Load Builder...................................................................................................................76
11 Validation of optimizer result........................................................................................................... 77
11.1.1 Optimizer log............................................................................................................. 77
11.1.2 Alerts........................................................................................................................ 82
12 SNP Master Data............................................................................................................................... 86
12.1 SNP Master Data transferred from R/3...........................................................................................86
29-01-2020 Page 4 of 107

12.2 SNP Master Data maintained in APO.............................................................................................86
12.2.1 Transportation Lane Master......................................................................................86
12.2.2 Planning Calendar....................................................................................................88
12.2.3 SNP planner.............................................................................................................. 89
12.2.4 Production version....................................................................................................90
12.2.5 Update out of stock penalties....................................................................................90
13 BW SNP Reports............................................................................................................................... 91
13.1.1 ZSNPOGL1 Planning data........................................................................................91
13.1.2 ZSNPOGL2 Transportation data...............................................................................93
13.1.3 ZSNPOGL3 Production capacity...............................................................................95
14 Change request documentation...................................................................................................... 97
14.1 Clustering purchasing requisitions..................................................................................................97
14.1.1 Planning flow............................................................................................................ 97
14.1.2 Customizing and development Carlsberg IT.............................................................98
14.1.3 Master data update by business.............................................................................100
14.2 Production quarantine using QM-lot.............................................................................................100
14.2.1 Planning flow.......................................................................................................... 100
14.2.2 Customizing and integration models.......................................................................105
14.2.3 Business maintenance of master data....................................................................107
29-01-2020 Page 5 of 107

1
1 Change History
Name Change Date New Version
Stephane Foulon Created 29.05.2008
Frank Christensen First draft ready for review 14.11.2012
Frank Christensen Uploaded to Share Point Server 23.11.2012
29-01-2020 Page 6 of 107

2 Overview of SNP
2.1 Purpose
The purpose of SNP is to provide a rough cut production plan to lowest possible cost. The production plan
should take capacity constraints into account, so early production is planned if there is a lack of capacity on
the optimal production time. This is important, especially when planning seasonal products for Easter and
Christmas. The production is planned in the SNP optimizer, which can fulfill these demands.
The detailed planning is carried out in PP/DS after conversion of SNP plans in a short period of 2-4 weeks.
The PP/DS planning is not a part of this documentation.
Furthermore distribution is planned in Deployment optimizer to the lowest possible cost.
It is important to state that examples in this documentation manual are screenshots of current setup. So
please be aware that things might have changed, when you need the documentation
2.2 Overview
The SAP Advanced Planner and Optimization (APO) component Supply Network Planning (SNP) integrates
the procurement, production, distribution and Transportation areas. It therefore provides users with a global
and consistent model for simulating and implementing comprehensive tactical planning decisions and
options regarding source of supply.
2.2.1 SNP Optimizer

SNP uses sophisticated optimization procedures to plan the flow of products along the supply chain on the
basis of constraints and penalty costs. The result is optimized procurement, production and distribution
decisions, reduced order processing times and stock levels, and improved customer service.
Using a demand plan as a basis, SNP calculates a feasible short term to medium term plan to address the
estimated demand quantities. This plan covers both quantities that are to be transported between 2 locations
(e.g., from the production plant to the distribution center) using means of transport, and quantities to be
produced and procured. Once SNP has generated a proposed plan, the system compares all the logistical
activities with the available capacity.
2.2.2 SNP Deployment

SNP s deployment function calculates when and how stock is to be delivered to distribution center. It creates
optimized distribution plans on the basis of constraints and business rules (such as replenishment strategies)
• After production has been completed, deployment determines which requirements can be covered by
the supply that is actually available.
• Deployment stock transfers
• Fulfilling demands
• Handling stock shortage
29-01-2020 Page 7 of 107

• Handling stock surplus
• Only distribution!
• No creation of production orders to fulfil demand
2.2.3 Transport Load Builder (TLB)

The transport Load Builder (TLB) function is used to create stock transfer orders suggested by the
deployment optimizer. This is also used for figuring out the exact number of trucks needed for the
transportation in the next days.
In the standard set up, the transport load builder is collecting deployment purchase requisition for the
creation of stock transfer orders, but it is possible using a separate planning book to let the transport load
builder collect SNP purchase requisitions for creation of purchase orders.
29-01-2020 Page 8 of 107

3 SNP Configuration
3.1Optimizer servers
2 optimizer servers are allocated to APS, namely SNP01 and SNP02. The servers are set up as windows
servers. The set up and maintenance of the RFC connection is an IBM responsibility.
The SNP02 server is the main server with 8 processors, and it is linked with the SNP01 server with 4
processors in a load balance, meaning that is the first 8 processors are active, the processors in the secondary
server is used.
The servers is found using transaction SM59 RFC destinations, and is the type TCP/IP connections.
An example of the SNP02 server
29-01-2020 Page 9 of 107

Definitions of target hosts in APS are for SNP01: 10.45.46.76 and for SNP02: DKSW0122.
The developement system APB and the quality assurance system APL are sharing 2 other servers with target
hosts dksw0004 and alcapone.
3.2Planning area
3.2.1 Customizing
Planning area and planning object structure is controlled with transaction /SAPAPO/MSDP_ADMIN. Menu
path: Supply Network Planning  Environment  Current Settings  /SAPAPO/MSDP_ADMIN -
Administration of Demand Planning and Supply Network Planning
Double click on Planning Area CB_SNP_PLANNING_AREA to check the set up.
The info screen shows basic informations of the Planning Area, such as Planning object structure, liveCache
connection, Units of measure and change information.
29-01-2020 Page 10 of 107

The aggregate screen shows a list of the aggregates linked to the planning area.
The key figure screen shows, which key figures are assigned to the planning area. In the detail screen (press
the Details button) a list of key figures are shown with informations about Key figure function, category
group and category.
29-01-2020 Page 11 of 107

Find below the online documentation of key figure function, category group and category.
The key figure aggregation screen shows the aggregation rules of each key figure. Calculation type is defines
as S (Prorata), see documention below
The used time based disaggregation rules are:
N: No disaggregtion
P: Equal distribution
29-01-2020 Page 12 of 107

In the key figure assignment screen the assingment to each aggregation is shown.
There is no set up in the Hierarchical planning screen.
3.2.2 LiveCache reorganisation

Reorganization of liveCache is executed on a daily basis with batch job APO_NORDIC_SNP_
OPTIMIZER_INITIAL.
29-01-2020 Page 13 of 107

First step of the job is an update of late delivery and out of stock penalties to avoid that new products is
optimized with no penalties, which will force the optimizer to skip the product from planning, as this is the
cheapest solution. Description of the Carlsberg specific report is found in the chapter SNP Master data.
Second step initialize time series for new products. Missing time series forces the optimizer to cancel.
Initialization cancel’s if a user is locking the planning area, which happens from time to time. This is not the
big problem for a shorter period of time. Optimizer cancels can be avoided by running time series
consistency check with the repair option activated.
Third step is the time series consistency check, which is executed in repair mode.
Fourth and fifth step executes reorganization on the liveCache.
Beside this batch job, a number of batch jobs are executed of the SAP Basis group. AM Support is not
controlling these batch jobs.
3.3Version management (Active and inactive)

3.3.1 Current versions
Current versions can be checked with transaction /SAPAPO/MSDP_ADMIN. Menu path: Supply Network
Planning  Environment  Current Settings  /SAPAPO/MSDP_ADMIN - Administration of Demand
Planning and Supply Network Planning
With a right click on the planning area CB_SNP_PLANNING_AREA it is possible to display Initialized
Time Series Objects or to initialize new time series for a planning version.
See below a list of created time series:
29-01-2020 Page 14 of 107

To update time series for a planning version choose created Time Series Objects
Key in number for the planning version to be changed, and press enter
Change the time period for initialization of the planning version, flag for “Execute in Background”, and
press execute. It is important the no users are locking the planning area, as the initialization then is denied.
Check locks in transaction SM12
Initialization of the active version 000 is important for the optimizer, as this will cancel if time series for a
product is missing. If this happens, and it is not possible to initialize emidiately because of a user lock, a
consistency check for time series will create the missing liveCache anchor, and make the optimization
possible.
When a copy of a planning version has been done, it is neccesary to initialize the copied version before it is
ready for use.
3.3.2 Create version

If a new version is needed this can be created in transaction /SAPAPO/MVM. Menu path: Master Data 
Planning Version Management  /SAPAPO/MVM - Model and Version Management.
Normally easiest way of creating a new planning version is to copy an existing one.
Choose source model and press the copy button, choose function Model/Version. In below example source
version 101 is chosen.
29-01-2020 Page 15 of 107

Key in number and description of the new version, and press the button Copy and Save.
After creation the new planning version has to be initialized before it is ready for use.
3.3.3 Copy version

Version is copied using transaction /SAPAPO/VERCOP. Menu path: Master Data  Planning Version
Management  /SAPAPO/VERCOP - Copy Planning Version or by executing report /SAPAPO
/VERSION_COPY_TRANS from transaction SA38 or as a step in a batch job. A lot of variants are created
to use in batch jobs, and covers most of the normally used copies for budgets and estimates.
In the example below is version 000 copied to version 054 (Swedish budget). Update the input screen with
Source and target version, and decide which order categories should be copied
29-01-2020 Page 16 of 107

The version copy is normally scheduled by the user, who normally don’t call for AM support.
It is important to know that first step in the copy is deletion of target version, so all existing data is lost. The
copy takes app. 1 hour, and should be followed up of an initialization of target version.
3.4Planning books
3.4.1 Assignment of planning book to user
When a new user is created to the APO system, he/she should be assigned to planning books before he/she is
ready to use planning books. When created, APO controls which planning view was used in latest logon.
This will be assigned to the user, when he logs off the planning view.
Assignment is defined with using transaction /SAPAPO/SDPPLBK. Menu path: Supply Network Planning
 Environment  Current Settings  /SAPAPO/SDPPLBK - Assign User to Planning Book.
Easiest way of assigning planning books to a new user is to copy the assignment of a similar user.
29-01-2020 Page 17 of 107

The assignment is after creation updated automaticly with the latest view, which was opened with the
transaction. In the example SAFETY STOCK was the last view in interactive SNP Planning, transaction
/SAPAPO/SNP94.
3.4.2 Define time buckets to use in planning views

Time buckets are maintained in transaction /SAPAPO/TR30. Menu path: Supply Network Planning 
Environment  Current Settings  /SAPAPO/TR30 - Maintain Time Buckets Profile for Demand Plng and
Supply Network Plng
The example shows a time bucket to use for display of 12 months of data with the split in daily, weekly and
monthly buckets.
First line defines the display period of 12 months. Of those are the the first 5 months displayed in weeks, and
the first 2 weeks are displayed in days.
3.4.3 CDK_SNP
The planning book CDK_SNP is created with the possibilities of creating view for Supply Network Planning
and Capacity Planning.
IMPORTANT SUPPORT MESSAGE. Normally planning books are maintained in the development
system and then transported to QA and production, but the definition of planning books in development is so
different from the production system that changes has to be done directly in the production system. Created a
ticket to the SAP Basis group, and ask them to open customizing rights in APS.
Macros are created to planning views. It is chosen that each planning view is not documented. The same
goes for macros. Used macros is documented, where they are used.
29-01-2020 Page 18 of 107

The key figre screen shows key figures in the planning area, and which of these key figures are used the
planning book. It is also shown which key figures are used in macros, and which are not.
The Characteristics screen shows characteristics in planning area and planning book
29-01-2020 Page 19 of 107

The key figure attributes screen per key figure. Key figure 9ATSHIP is shown as example.
A lot of planning view are created to the CDK_SNP planning book
29-01-2020 Page 20 of 107

To document the set up of planning viwes an example – the SAFETY STOCK view - is chosen.
In this screen it is possible to assign future and history timebuckets, and to decide visibility- and input from
date.
And in the last view the key figure assignment to planning view is controlled
29-01-2020 Page 21 of 107

3.4.3.1 Example of a production planning view in CDK_SNP
29-01-2020 Page 22 of 107

3.4.3.2 Example of a capacity view in CDK_SNP
In the capacity view available capacity, capacity consumption and capacity utility is displayed per bucket.
In the quantity view the production quantity is displayed. This can be opened per product by pressing the
button “display dependent objects”, choose products and select all products or just a few products.
3.4.4 DEPLOY_STOCK
Planning book is used for deployment planning. Set up after same rules as documented for CDK_SNP
3.4.5 PURCHASE_TLB
Planning book is used for running transport load builder for SNP purchaserequisitions. Set up after same
rules as documented for CDK_SNP
3.4.6 Other planning books assigned to SNP Planning area

3 more planning books DEPLOYMENT_TLB, DEPLOYMENT_TLB_1 and DEPLOYMENT_
PRODUCTION are assigned to the planning area CB_SNP_PLANNING_AREA. These are not in use
anymore, and therefore not documented.
29-01-2020 Page 23 of 107

4 Integration between APO and R/3

4.1APO customizing
4.1.1 Publications
To make it possible to transfer transactional data between the 2 systems, publication information’s has to be
maintained per location and logical system.
Maintenance of publications is done in customizing, using transaction SPRO. Menu path: Integration with
SAP Components  Integration of SAP SCM and SAP R/3  Basic Settings for Data Transfer 
Publication  Maintain Distribution Definition
The important publication types for SNP are 21 External procurement that allows transfer of purchase
requisitions and purchase orders, and 31 Inhouse production that allows transfer of planned order and
process orders.
More detailed informations about publication in the CIF support manual.
4.1.2 Transfer with change pointers

Transfer of SNP data is defined as periodic transfer in customizing, transaction SPRO. Menu path: Supply
Chain Planning  Basic Settings Configure Transfer to OLTP Systems
When an SNP order is created or changed it is not transferred emidiately, but the order informations are
saved in a change pointer. Activation of change pointers are done with transaction /SAPAPO/C5, report
29-01-2020 Page 24 of 107

/SAPAPO /RDMCPPROCESS. Screen dump below shows the selection for activating in house production
change pointers for Denmark.
Change pointer activation is included in a lot of batch jobs, so normally it is not necccesary to run it
manually. Find the actual batch jobs using transaction SM37, searching use of report /SAPAPO
/RDMCPPROCESS.
29-01-2020 Page 25 of 107

4.2Integration models
Integration models are maintained in R/3, and are documented in the CIF Support Manual. Integration
models are executed on a daily basis for Denmark, Norway and Sweden, and successfully update is
important for the SNP planning.
Note that only the active version 000 is transferred through the CIF interface. For inactive version Carlsberg
specific development is introduced to transfer planned orders to an R/3 Long Term Planning Scenario.
The report is named ZRPP_APO_LTP, and the functionality is documented in details in the CIF Support
Manual.
4.3Mismatch between APO and R/3

4.3.1 Post processing monitor
If mismatch is found between transactional data in the 2 system, check if the order is hanging in
inbound/outbound queues or in the Post Processing Monitor. If so, find the reason why, and retransfer it, with
or without corrections. The use of Post Processing Monitor is documented in details in the CIF Support
Manual.
The post processing monitor is called with transaction /SAPAPO/CPP. Menu path: APO Administration 
APO Administration  CIF Error Handling  /SAPAPO/CPP - CIF Post processing
4.3.2 CIF comparison

Another useful transaction for finding and repairing mismatch between the 2 systems are the delta report,
transaction /SAPAPO/CCR. Menu path: APO Administration  Integration  CIF Comparison/
Reconciliation of Transaction Data  /SAPAPO/CCR - Execute Comparison/Reconciliation.
29-01-2020 Page 26 of 107

This example gives the result that no inconsistences for planner orders is found for product 502/1002.
The delta report openes for aligning inconsistences by sending the to APO or R/3, or by deleting them in
APO or R/3. But before doing so, be sure that the order with mismatch is without errors, so the reconsiled
order will not appear as an error in post processing or delta report again.
More information of the delta report in the CIF Support Manual.
4.3.3 Realign sales orders in R/3 and APO

When sales orders are delivered in R/3, they are deleted from table VBBE, Sales Requirements: Individual
Records. This deletion is not transferred to APO, so reorganization is necessary. This is executed in APO on a
weekly basis by running batch job APO_NORDIC_DELETE_SDTABLE.
First step is running report /SAPAPO/SDRQCR21 to delete obsolete sales orders from APO after compare
with the R/3 table VBBE.
Next steps are cleaning SD-tables in APO to align them with the sales ordersituation after deletion of
obsolete orders in step 1. If this cleaning is not done over a longer period of time there is a risk of
performance problems.
It is important to run the variants in right order, first plant deletion in several tables. The most important is
/SAPAPO/SDFIELD (Sales order items) that could grow dramatically. Next step is adjustment of ATP, and
last step reorganisation of table /SAPAPO/POSMAPN (deliveries).
29-01-2020 Page 27 of 107

/SAPAPO/SDRQCR21 Variant for aligning with R/3
Plant specific variant of /SAPAPO/SDORDER_DEL
29-01-2020 Page 28 of 107

/SAPAPO/SDORDER_DEL variant for adjusting ATP tables
/SAPAPO/SDORDER_DEL variant for deleting obsoletes from table /SAPAPO/POSMAPN
29-01-2020 Page 29 of 107

5 Release Forecast to SNP

5.1Release
Forecast for Denmark, Norway and Sweden is released from Demand Planning, currently on a daily basis.
Promotions are released for Denmark and Sweden, also on a daily basis. Release of forecast and promotions
must have finished before safety stock calculation as safety stock is calculated from these 2 key figures.
Release of forecast updates 2 key figures in planning area CB_SNP_PLANNING_AREA: Info objects
9AAFCST, forecast and ORIG_FC, original forecast. Both are assigned to category group FA.
Transfer of promotions updates planning area CB_SNP_PLANNING_AREA in key figure: Info object
CB_DUMM10, promotions from DP. This is not assigned any category groups or order types to promotions.
Release of forecast and promotions are documented in details in the Demand Planning Support Manual.
5.2Forecast consumption
5.2.1 SNP Requirements Strategies
The requirement strategy determines how production quantities are planned in SAP APO and how the
forecast is consumed by other orders
The requirement strategy is defined in transaction S_AP9_75000142, menu path: Supply Network Planning
– Environment – Current Settings – Profiles – Define SNP Requirement Strategies.
The requirement strategy chosen is 20 as this is the most used
29-01-2020 Page 30 of 107

5.2.2 Forecast Consumption

Sales orders are transferred to APO, and are visible in planning books as key figure “Sales order”. Info object
9ADMDP1 assigned to category type BM.
Each sales order consumes forecast in APO as defined in R/3 material master and transferred to the APO
product master. There is no consumption of the key figure “Original forecast”.
See below an example in R/3, where plant material 502/1002 is defined with planning strategy 40, and
consumption mode 2.
This means that if forecast in actual bucket is consumed, APO consumes forecast first 2 days in the past, and
then 1 day in the future. The SNP planning is executed on the basis of the sum of forecast and sales order,
meaning that if sales order quantity is less than forecast, planning is based on forecast (Sales order + non-
consumed forecast). If the sales order quantity is exceed the forecast, SNP planning will be based on the
sales order quantity.
The consumption strategy is transferred to APO with the integration model for material master. In APO the
corresponding data is found in product master. Planning strategy 40 as defined in R/3 is transferred to APO
as proposed strategy 20.
29-01-2020 Page 31 of 107

29-01-2020 Page 32 of 107

6 Safety Stock Planning

6.1Safety stock strategies
Basically Carlsberg is calculation safety stock using 3 different methods:
6.1.1 Calculations based on forecast accuracy and service level

Calculation based on forecast accuracy using transaction /SAPAPO/MSDP_SB. This method has been tested
in Norway, but only for a few products. It is never implemented as a standard method, and is therefore not
supported.
Find below an example on selections for calculating the safety stock
29-01-2020 Page 33 of 107

6.1.2 Fixed safety stock copied from product master

Define safety stock in R/3 material master using safety stock strategy SB. As safety stock strategy is not
available in standard R/3 maintenance is done in the APO tab. Safety stock is defined in material master, lot
size view and is transferred to APO as a standard field. The safety stock value is transferred to the APO key
figure running a macro in the SAFETY STOCK view of planning book CDK_SNP.
Execution of this macro will be documented with the country specific safety stock calculation.
6.1.3 Safety stock calculated from original forecast

Calculation is based on macros executed in the SAFETY STOCK view of planning book CDK_SNP.
Calculations are executed for products maintained with safety stock strategy BS.
Each country is using different calculations, so current setup will be documented with the country specific
safety stock calculation.
6.2Country specific safety stock calculation

6.2.1 Denmark
Calculation of safety stock is defined as step 8, 9 and 14 in batch job APO_DK_SNP-OPTIMIZER_PPDS
currently running on a weekly basis every Friday evening.
6.2.1.1 Step 8: DK_SAFETY_0
This step executes the DP background job DK_SAFETY0, which set safety stock to zero for all products
with SNP planner 425 (products excluded from planning)
29-01-2020 Page 34 of 107

The called activity DK_SS_ZERO executes macro Update safety stock = 0 in the SAFETY STOCK view in
planning book CDK_SNP.
Macro definition:
29-01-2020 Page 35 of 107

This step executes the DP background job DK_SAFETY6, which calculates safety stock as weekly original
forecast divided with 5 and multiplied with safety stock days of defined in product master in user defined
field. The calculation takes promotions from DP into account in the calculation.
Safety stock days defined in product master:
The called activity DK_SS_ALL executes macro SAFETY ST (ORG.FC X SAF STCK D) W/ZERO in the
SAFETY STOCK view in planning book CDK_SNP.
29-01-2020 Page 36 of 107

Macro definition:
29-01-2020 Page 37 of 107

This step executes the DP background job DK_SAFETY7, which safety stock based on total demand
The called activity DK_SAFETY6 executes macros CALCULATE TOTAL DEMAND and SAFETY
STOCK (TD X SA ST DA) W/ZERO in the SAFETY STOCK view in planning book CDK_SNP.
Definition of Macro CALCULATE TOTAL DEMAND
29-01-2020 Page 38 of 107

Definition of Macro SAFETY STOCK (TD X SA ST DA) W/ZERO
6.2.2 Norway
Calculation of safety stock is defined as step 7 in batch job APO_NO_DP_RELEASE_FC_TO_SNP_V2
currently running daily with the exception that batch job is not executed on Sundays and holy days based on
calendar ZV.
Step 6: NO_SAFETY
This step executes the DP background job NO_SAFETY, which calculates safety stock as weekly original
forecast divided with 5 and multiplied with safety stock days of defined in product master in user defined
field. The calculation does not take promotions from DP into account in the calculation.
29-01-2020 Page 39 of 107

The called activity SE_SAFETY executes macros SAFETY STOCK (ORG.FC X SAFETY STCK DAYS) in
the SAFETY STOCK view in planning book CDK_SNP.
Macro definition:
29-01-2020 Page 40 of 107

6.2.3 Sweden
Calculation of safety stock is defined as step 2-5 in batch job APO_SE_SNP_OPTIMIZER_INITIAL
currently running daily with the exception that batch job is not executed on Sundays and holy days based on
calendar ZS.
6.2.3.1 Step 2: SE_SAFETY4
This step executes the DP background job SE_SAFETY4, which calculates safety stock from an average of 4
weeks original forecast per day multiplied with safety stock days of defined in product master in user defined
field. The calculation takes promotions from DP into account in the calculation.
Activity SE_SAFETY4 executes the macro SAFETY STOCK (AVG4(OFC-DP) X SAF STCK D) in
planning view SAFETY STOCK, planning book CDK_SNP
29-01-2020 Page 41 of 107

Macro definition:
29-01-2020 Page 42 of 107

6.2.3.2 Step 3: SE_SAFETY3
This step executes the DP background job SE_SAFETY3, which calculates safety stock from an average of 4
weeks total demand per day multiplied with safety stock days of defined in product master in user defined
field. The calculation does not take promotions from DP into account in the calculation.
29-01-2020 Page 43 of 107

Activity SE_SAFETY3 executes the macros CALCULATE TOTAL DEMAND and SAFETY STOCK
(AVG4(TD) X SAF STCK D) NP in planning view SAFETY STOCK, planning book CDK_SNP
Definition of macro CALCULATE TOTAL DEMAND
29-01-2020 Page 44 of 107

Definition of macro SAFETY STOCK (AVG4(TD) X SAF STCK D) NP
6.2.3.3 Step 4: SE_SS_PROD
This step executes the DP background job SE_SS_PROD, which calculates transfer safety stock from
product master.
Activity SE_SS_PROD executes the macro SAFETYSTCK in planning view SAFETY STOCK, planning
book CDK_SNP
29-01-2020 Page 45 of 107

Definition of macro SafetyStck
6.2.3.4 Step 5_IC_SS_PROD
This step executes the DP background job IC_SS_PROD, which calculates transfer safety stock from product
master.
Activity SE_SS_PROD is the same as for background job SE_SS_PROD, and executes the macro
SAFETYSTCK in planning view SAFETY STOCK, planning book CDK_SNP
29-01-2020 Page 46 of 107

7 Optimizer profiles
7.1 Cost profile
Cost profiles for use in the optimizer are maintained with transaction S_AP9_75000101. Menu path: Supply
Network Planning  Environment  Current Settings  Profiles  S_AP9_75000101 - Define SNP Cost
Profiles.
 Prod. Cap. is the factor used for the weight of production cost as maintained in the SNP PPM. The
production cost is calculated in R/3 and transferred to the SNP PPM in the PPM transfer job.
Detailed decription of the calculation is found in the CIF Support Manual.
 Trans.cap. is the factor for weight of the transportation capacity assigned to resource master in
Active variant 01. Transportation resource is assigned to transportation lane.
 Stor.Cap. is the factor for weight of the storage capacity assigned to location master in Active variant
01. Storage cost used by the storage capacity is maintained in R/3 material master, APO tab, and
transferred to the APO location master, where it is found in the procurement tab
29-01-2020 Page 47 of 107

 Sfty Stock. is the factor for weight of the safety stock penalties. Safety stock penalties is maintained
in R/3 material master, APO tab, and transferred to the APO location master, where it is found in the
procurement tab.
 Lateness and no Deliv. is the factor for weight of the lateness and nodelivery penalties. These
penalties is maintained in the the APO location master, where it is found in the SNP1 tab. The
penalties are maintained as a global price covering all location products by executing report
ZCALC_LATE_DELIVERY_COST. The report is executed daily after activation of the material
integration model with batch job APO_NORDIC_SNP_OPTIMIZER_INITIAL.
If penalties are not maintained the optimizer will assume that lowest cost will be found with no
planning. It is there fore important to make sure that product master is updated and factors are
greater that zero.
29-01-2020 Page 48 of 107

Currently lateness and no delivery penalties are defined as global penalty costs. A report for updating these
penalties as location dependent is available, but not in use.
7.2 Optimizer profiles

7.2.1 SNP optimizer profiles
SNP optimizer profiles are maintained from transaction S_AP9_75000102. Menu path: Supply Network
Planning  Environment  Current Settings  Profiles  S_AP9_75000102 - Define SNP Optimizer
Profiles
Profiles starting with a Z, is Carlsberg specific profiles, and the ones, we should care about:
29-01-2020 Page 49 of 107

As an example of set up, we can look at one of the the most used profiles Z01-00TM01, which start an
optimization within one hour using product decomposition.
This optimizer profile calls for a discrete optimization, meaning that roundings are taken into account.
The discrete optimization in used for planning inside the production location.
The other posibility Linear optimization is used of the optimizer profiles ZHOR_DI_ND, ZHOR_DI_N2 and
ZHOR_DI_SL. The liniar optimization creates order to fullfil requirements without rounding, and do not use
as long runtime as the discrete optimization.
The Carlsberg set up operates with running a liniar optimization for all locations in the network, to collect
the total requirement in the production location. Then a discrete optimization is run for the production
location to create order with roundings as defined in product master.
This optimizer profiles takes production capacity and safety stock into account.
29-01-2020 Page 50 of 107

The view ”Model params” is used for defining buckets
The ”Solution methods” tab defines the maximum runtime allowed to find a proper solution, in this example
1 hour, and the use of product decomposition 1 %.
The product decomposition split the optimization into small sub-tasks to be optimized one of the time. It
works the way that the optimizer starts with calculating a opportunity price for each location product. The
formula is not known in details, but it is close to quantity multiplied with production price. In this way the
most important product is optimized as the first one, the second most important as the second etc.
There has been a lot of religious discussions of the use of product decompositions. Some like it, and others
do not. The product decomposition has a severe effect on performance, and as we plan with an optimization
per SNP planner (filling line), it does not harm the result too much – is my oppinion.
The “Integration” tab holds the information of horizons
29-01-2020 Page 51 of 107

7.2.2 COPT10 parameters for SNP optimizer profiles

As we need more functions in the optimizer than the optimizer profiles provide in current version 4.1, we
have the possibility to add these additional parameters with transaction /SAPAPO/COPT10.
Additional functions are defined separately for both servers SNP01 and SNP02. Easiest way to update a new
profile is to copy one block, and then copy it to the new profile for both servers.
7.2.3 Deployment optimizer profiles

Deployment optimizer profiles are maintained from transaction S_AP9_86000062. Menu path: Supply
Network Planning  Environment  Current Settings  Profiles  S_AP9_86000062 - Define SNP
Deployment Optimizer Profiles
The Z-profiles are the Carlsberg specific ones defined for discrete optimization with product decomposition.
There is no COPT10 parameters assigned to the deployment optimizer profiles.
29-01-2020 Page 52 of 107

8 SNP optimization
8.1Preconditions and optimization flow
8.1.1 Preconditions
Integration models for master data should be finished to make sure that SNP is updated with new master data
before optimization.
Creation of time series for finished goods products has to be finalized before optimization to avoid cancel of
optimizer. If initialization of live Cache time series has failed, a time series consistency check will do.
Release of forecast and promotions from Demand Planning should be finished before calculation of safety
stock and optimization.
Calculation of safety stocks should be finished before optimization.
8.1.2 Optimizer flows
8.1.2.1 Deletion of planned orders
Forecast in SNP is deleted for the total planning period before starting a new optimization. Deletion of SNP
orders category EE is done with transaction /SAPAPO/RLCDEL or executing report /SAPAPO/RLCDELE
from transaction SA38, deletion of PP/DS orders category AI is done with report
/SAPAPO/DELETE_PP_ORDER. There is no transaction code for this deletion. The optimizer will as a part
of the optimization delete SNP orders in the planning period, but to make sure to also delete obsolete orders,
this extra deletion is introduced.
Example of selection for deletion of SNP planned orders with /SAPAPO/RLCDEL. The example is based on
variant DEL_SNP_PLO_NO deleting categories EE and AG for a specified number of Norwegian locations
for all SNP planners except 410-449 and 268 in the period between current date -50 and current date + 500.
The settings for deletion both in R/3 and APO means that when the order is deleted from APO liveCache, the
deletion is also sent to R/3 through the CIF interface. This gives from time to time a problem; if the order is
locked in R/3, it is not deleted, so orders are found in R/3 that doesn’t exist in APO. This can be corrected by
sending the order to APO from the delta report, and then delete the order in R/3 and APO again.
If you want to start a deletion manually, e.g. deletion of a single product it is recommended to run
RLCDELETE in test mode. This gives a list of orders, which are ready for deletion. After checking the list,
you can press the delete button to delete the orders from liveCache.
29-01-2020 Page 53 of 107

Example of selection for deletion of PP/DS planned orders with /SAPAPO/DELETE_PP_ORDER. The
example is based on variant DEL DS PL.O NO deleting category AI for Norwegian locations 3101 – 3105
for all PP/DS planners (planner is no specified) in the period between current date and current date + 500.
The control parameters could be used to control functionality of the report
29-01-2020 Page 54 of 107

 Display orders make is possible to run a test to check a selection. If you are running a special
deletion manually, it is recommended to run the report with only this flagged. The run gives a list of
orders, which are ready to be deleted with the actual selection. After check of the list go back to the
selection screen, set the other two control parameters and run the report again.
 Delete orders delete orders from APO liveCache
 Send the deletion to R/3 through the CIF interface
8.1.2.2 Optimization
After deletion of planned orders, a linear optimization is executed per SNP planner (or a number of SNP
planner’s) to collect requirement from the total network in the production location.
A discrete optimization is executed to per SNP planner (or a number of SNP planners) to create planned
orders with lot sizes as defined in product master.
Detailed description of optimizer jobs are found in following chapters.
8.1.2.3 Order conversion and activation of change pointers
SNP orders are category EE is converted to PP/DS orders category AI for a shorter period of 2-4 weeks,
depending on the country. This functionality is described in details in a following chapter.
As explained earlier in the chapter SNP setting, SNP orders are not transferred immediately to R/3, but a
change pointer is created for later activation. After optimization these change pointers are activated by
running batch job steps executing /SAPAPO/RDMCPPROCESS. Activation of change pointers are explained
in details in chapter ”Integration between APO and R/3”, sub-chapter “Transfer with change pointers”.
8.2Linear optimization
To collect requirement from the entire network a linear optimization is executed. This is running without
rounding’s, and therefore and therefore the run time is pretty short.
The linear optimization is normally executed with optimizer profile ZHOR_DI_ND, and cost profile could
be Z01C, in special cases another cost profile could be chosen.
The optimizer is started from transaction /SAPAPO/SNPOP or from a batch job running report
/SAPAPO/RMSNPOPT. Optimization of a single location product could also be executed from a planning
book.
Find below an example of selection screen for running linear optimization for Sweden, filling line KO65:
29-01-2020 Page 55 of 107

The selection profile 000 SE LP K65 as used in this example is defined as seen below selects products from
Norway location 3101-3144 and from Sweden location 3203 with procurement type F, and collect the
requirements in production location 3202 with procurement type E.
The updated result is visible in planning book in key figure “Production planned” as order category EE
29-01-2020 Page 56 of 107

8.3Discrete optimization
To create a production plan, which takes lot sizes into account a discrete optimization is run on the
production location with the same SNP planners as used in the linear optimization.
Most of the discrete optimizations in Nordic setup is executed with optimizer profile Z01-00TM01, allowing
the optimizer to use 60 minutes to find a solution using product decomposition with 1 %. Most used cost
profile is Z01C, but in special cases another cost profile could be chosen.
The optimizer is started from transaction /SAPAPO/SNPOP or from a batch job running report
/SAPAPO/RMSNPOPT. Optimization of a single location product could also be executed from a planning
book.
Find below an example of selection screen for running discrete optimization for Sweden, filling line KO65:
In this example another optimizer profile Z01-00TM03 is chosen. This gives the optimizer 180 minutes to
find a solution using product decomposition 1 %. Also another cost profile Z01SE is chosen, which maybe is
a little strange.
The selection profile 000 SE SNPOPT K65 as used in this example is defined as seen below, selects products
production location 3202.
29-01-2020 Page 57 of 107

The updated result is, as for the linear optimization result, visible in planning book in key figure “Production
planned” as order category EE
8.4Order conversion to PP/DS

After finishing optimization a conversion of SNP orders category EE to PP/DS orders category AI is
executed with report /SAPAPO/RRP_SNP2PPDS2, normally as a step in a batch job. The order conversion is
in fact a PP/DS functionality, but is included this document to give a better overview.
In below example, variant 000_SE_K53 conversion is executed in location 3202 for Production planners 409
and 442 with heuristic Z_SNP_CON_21. This converts orders in the period of 21 days after end of the SNP
production horizon as defined in product master
29-01-2020 Page 58 of 107

The heuristics are maintained in APO customizing, transaction SPRO.
Menu path: Supply Chain Planning  Production Planning and Detailed Scheduling (PP/DS)  Heuristics
 Maintain Heuristics
29-01-2020 Page 59 of 107

8.5Optimizer Batch jobs

8.5.1 Denmark
Danish optimization is currently executed weekly on Friday evening by executing the batch job
APO_DK_SNP-OPTIMIZER_PPDS. This batch jobs includes all SNP optimizer activities and run for app. 8
hours. Only precondition is that forecast release with batch job APO_CDK_DP_RELEASE_FC_
TO_SNP_V5 has ended.
8.5.2 Norway
Optimizations for Norway are executed on a daily basis, but not on Sundays and Holy days, determination of
these is based on calendar NO.
Before optimizations old orders are deleted from the SNP plan by running batch job
APO_NO_APO_DELETE-OLD-PLAN_ALL. SNP orders are deleted with /SAPAPO/RLCDELETE, PP/DS
orders are deleted with /SAPAPO/DELETE_PP_ORDER and Change pointers are activated.
29-01-2020 Page 60 of 107

Also before optimization, the forecast release and safety stock calculation has to be fininished. Executed with
batch job APO_NO_DP_RELEASE_FC_TO_SNP_V2.
First job in the planning flow is repacking executed with batch job APO_NO_SNP_SNP-
OPTIMIZER_BEER_13 and intercompany planning between Norway and Sweden with batch job
APO_SE_SNP_OPTIMIZER_IC_NO-SE.
When these two jobs has ended, rest of the optimizer jobs could be run. There is no dependicies between
theese, so they can be moved around without harming the optimizer result. List of these optimizer jobs with
latest start time
Optimizations has to be finished befor 04:30, where copy to version 100 is started.
After end op the optimization SNP orders are converted to PP/DS orders for 10 days after SNP production
horizon by running batch job APO_ALL_PPDS_CONV-SNP-ORD_ALL.
8.5.3 Sweden
Optimization for Sweden is executed on Mondays and Wednesdays.
Before optimization the forecast release with batch job APO_SE_DP_RELEASE_FC_TO_SNP_V2 should
be finished
After forecast release and transfer of promotions, safety stock should be calculated with batch job
APO_SE_SNP_OPTIMIZER_INITIAL.
29-01-2020 Page 61 of 107

Trading goods and subcontraction is planned by running batch job APO_SE_SNP_OPTIMIZER_

TRADING_GDS. Documented here even if is executes PP/DS heuristics as planning tool to complete the
description of the planning flow.
Intercompany planning between Norway and Sweden should also run before filling line optimization by
running batch job APO_SE_SNP_OPTIMIZER_IC_NO-SE.
Optimizations has to start with planning repack by running batch jobs APO_SE_SNP_
OPTIMIZER_RESOURCE_60 and APO_SE_SNP_OPTIMIZER_REPACK.
All swedich optimizer jobs are created per filling line including the total optimizer flow, deleting old orders,
optimizing linear and discrete, conversion to PP/DS and activating change pointers.
After execution of repack rest op the optimizer jobs can be started. There is no dependicies between theese,
so they can be moved around without harming the optimizer result. List of these optimizer jobs with latest
start time.
29-01-2020 Page 62 of 107

After ending optimization of all filling lines in Sweden, an optimization of sorting of empties is executed by
running batch job APO_SE_SNP_SNP-LP_OPT_EMPTIES
The SNP optimization plan sorting of crates mixed bottles product number 50007 using a PPM with 2 output
products 54864 White bottles and 54865 Coloured bottles with the split of 75 % of white bottles and 25 % of
coloured bottles.
When a demand for one of the products is fullfilled by creating a planned order, an order for joint production
of the other product is also created with category EM (Co production). In the planning book this is updated
in the key figure Manufacture of CO-products.
In below planning book view of 54864 is planned orders created after fullfilling demands of 54864, while the
manufacture of Co-Products is created as a by product fullfilling demands of 54865.
Next step in the sorting batch job is a deployment optimization planning transport of sorted white bottles
from 3202 Falkenberg to 3201 Ramlösa.
29-01-2020 Page 63 of 107

Swedish optimizations except from the empties sorting has to be finished befor 04:30, where copy to version
100 is started.
8.6Inactive versions
8.6.1 Version 100
After end of optimization a copy of active version 000 is taken into version 100. The copy is executed on a
daily basis currently at 04:30 with batch job APO_CDK/SE_SNP_100-VERSION-COPY.
This version could be used to take a snapshot of the optimizer result before the end users start there daily
planning.
An optimization of version 100 is executed on a daily basis with batch job APO_CDK_SNP_100_
OPTIMIZER to evaluate the Danish optimization.
No optimizer jobs for version 100 has been created for Norway and Sweden.
8.6.2 Version 101

The active version 000 is copied to version 101 on a weekly basis with batch job APO_CDK_SNP_101-
VERSION-COPY_ALL
29-01-2020 Page 64 of 107

This version is used for capacity planning in Denmark and Norway. Sweden do not use this version.
This version is also the source version for collecting APO data for transfer to BW.
There is created Danish and Norwegian batch jobs to execute an optimization after version copy
Remember for the Norwegian jobs that the delete job and optimizer 13 is prerequisites for rest of the
optimizations, as explained for optimization of the active version.
8.6.3 Other versions

Version copies to other versions is used by the Danish business to plan estimates and for Sales and Operation
Planning The business takes care of this functionality themselves, and a support issue will normally not
occur. But there is no difference between using these versions and using the described versions 100 and 101.
29-01-2020 Page 65 of 107

9 Special SNP functionality

9.1Planning with production quarantine
9.1.1 Functionality in brief
Using QM-lot to manage production quarantine after goods receipt from process order is implemented with
Change request CR 4997 and gives the possibility of setting production into quarantine a number of days
before it is available in unrestricted stock. The production will be posted in quality stock, and a QM-lot is
created to report when the quantity is expected in unrestricted stock. At end of the quarantine the quantity is
released with a usage decision of inspection lot, which posts the quantity in unrestricted stock and deleted the
QM-lot.
9.1.2 Planning flow
9.1.2.1 Create process order and inspection lot
Create process order as usual by converting an APO PP/DS order.
Release the process order. At release an inspection lot of origin 04 will be created. Inspection end date will
be maintained as production date in the process order + average inspection duration from the material master.
9.1.2.2 Goods receipt
Goods receipt will be posted as usual from Astro in Norway and Sweden and from pallet system in Denmark.
Be aware that posting will be to quality stock because of the setting in material master for plant material.
The expected day for end of quarantine is maintained in a QM-lot.
9.1.2.3 Display QM-lot
The QM-lot with the expected date of quarantine end is visible in R/3 and APO.
In R/3 QM-lot is visible in stock requirement list, transaction MD04
In APO PP/DS the QM-lot is visible in product view
29-01-2020 Page 66 of 107

In APO SNP the QM-lot is visible in planning book, key figure "Production (Confirmed)" together with
PP/DS orders and process orders. In details it is represented as category BU.
Production quarantine is ended by given a usage decision to the inspection lot in R/3.
Detailed documentation of change request CR 4997 is found as appendix to this manual.
29-01-2020 Page 67 of 107

9.2Transport load builder for SNP orders

This functionality is implemented with change request CR4749.
In APO standard the transport load builder is used to collect deployment purchase requisitions to TLB
shipments. When sending them to R/3 a stock transfer order is created in R/3 and returned to APO with a
STO number.
By using planning book PURCHASE_TLB, view PURCHASE_TLB it is also possible to collect SNP
purchase requisitions to TLB shipments. When sending them to R/3 a purchase order is created in R/3 and
returned to APO with a Purchase order number. This functionality is very useful when planning Trading
goods transfer e.g. from vendor to production location or distribution center.
Create a selection based on transportation lane
Press the ”TLB view button
Choose transportation lane.
Create a TLB shipment by pressing the ”Create TLB shipment” button
29-01-2020 Page 68 of 107

Move SNP purchase requisitions to the TLB shipment. Load is controlled according to the means of
production defined in the transportation lane.
The TLB shipment is transferred to R/3 by pressing the “Orders Directly to OLTP System”.
Detailed description of the change request CR 4749 is found in appendix to this document.
29-01-2020 Page 69 of 107

10 Deployment Optimization
10.1 Deployment optimization
10.1.1 Optimizer run
Deployment optimization is scheduled to execute with batch jobs calling report /SAPAPO/RMDPLOPT.
The deployment optimizer could also be executed as a onetime job running transaction /SAPAPO/SNP03.
Menu path: Supply Network Planning  Planning  Supply Network Planning in the Background 
/SAPAPO/SNP03 - Deployment Optimization
A lot of variants are created for this report, calling different selections. The below example displays variant
SE_DEP_54 running the deployment optimizer with the bucket definitions from planning book
DEPLOY_STOCK, view DEPLOY_STOCK for the period from current day to current day + 10, optimizer
profile ZD01_5min and cost profile Z01B. The selection profile SE FBG 54 is also opened below.
The deployment optimizer deploys according to requirements, but cannot deploy more than the content in
key figure ATD (Available to deploy) Reciepts.
29-01-2020 Page 70 of 107

The deployed quantity is updated in key figure ATD Issues.
10.1.2 Maintain category groups

ATD receipts and ATD issues are updated according to category groups containing order categories. In this
way it is customized e.g. which order types must be planned for distribution.
ATD Receipt
This field is relevant to Deployment in Supply Network Planning (SNP). With the category group for the ATD receipt, you
specify which order categories contribute to the increase of the Available to Deploy Quantity (ATD quantity) (for example,
EE = SNP planned orders).
See chapter "configuration" of this document to see the description of all category groups and categories
ATD Issue
This field is relevant to Deployment in Supply Network Planning (SNP). With the category group for the ATD issue, you
specify which order categories contribute to the reduction of the Available To Deploy Quantity (ATD quantity) (for
example, BM = sales orders).
See chapter "configuration" of this document to see the description of all category groups and categories
Category groups used by ATD receipts and ATD issues is maintained in location master, SNP tab
29-01-2020 Page 71 of 107

Category groups are customized wiyh transaction SPRO. Menu path: Advanced Planning and Optimization
 Supply Chain Planning  Supply Network Planning (SNP)  Basic Settings  Maintain Category
Groups
Find below the content of the category groups Z03 and Z09, as is maintained in location 3202 as ATD issues
and ATD reciepts
10.2 Deployment optimizer batch jobs

10.2.1 Denmark
Danish deployment jobs are executed on a daily basis by running 3 batch jobs
APO_DK_SNP_DEPLOY_STOCK_BEER
29-01-2020 Page 72 of 107

APO_DK_SNP_DEPLOY_STOCK_CCTD
APO_DK_SNP_DEPLOY_STOCK_TRAD
Deployment alerts are created hourly between 07:00 and 15:00 on a daily basis by running batch job
APO_DK_SNP_DEPLOY_ALERT_CREATION
The steps DEP_DK_BL, DEP_DK2_BL and DEP_DK1_BL are running activity NL_DEP_BL with different
selections
The steps DEP_DK_BS, DEP_DK2_BS and DEP_DK1_BS are running activity NL_DEP_BLS with
different selections
29-01-2020 Page 73 of 107

Activity NL_DEP_DL executes 6 macroes in planning book DEPLOY_STOCK, view DEPLOY_STOCK
 DETERMINE WORKDAYS
 STOCK BALANCE
 SAFETYSTCK
 TOTAL BACKLOG ALERT
 SUPPLY SHORTAGE ALERT
 STOCK BELOW SAFETY STOCK ALERT
Activity NL_DEP_DLS executes 4 macroes in planning book DEPLOY_STOCK, view DEPLOY_STOCK
10.2.2 Norway
Norway deployment is executed on a daily basis by running batch job APO_NO_SNP_DEPLOY_STOCK
29-01-2020 Page 74 of 107

10.2.3 Sweden
Swedish deployment is running twice a day with 3 batch jobs
APO_SE_SNP_DEPLOY_FALKENBERG
APO_SE_SNP_DEPLOY_TRADING_GDS
APO_SE_SNP_DEPLOY_RAMLOSA
29-01-2020 Page 75 of 107

10.3 Transport Load Builder

Transport load builder is a tool to collect deployment purchase requisition into a TLB shipment that is sent to
R/3, where it is replaced with a stock transfer order.
The TLB is opened with transaction /SAPAPO/SNPTLB. Menu path: Supply Network Planning 
Planning /SAPAPO/SNPTLB - Transport Load Builder (TLB)
Create a TLB shipment by pressing the ”Create TLB shipment” button. The TLB shipment is named APO-
000x.
Move Deployment purchase requisitions to the TLB shipment. Load is controlled according to the means of
production defined in the transportation lane.
The TLB shipment is transferred to R/3 by pressing the “Orders Directly to OLTP System”. In R/3 a Stock
Transfer Order is created on basis of the TLB shipment. The Stock Transfer Order is transferred back to APO
through the CIF interface, and replaces the TLB shipment.
29-01-2020 Page 76 of 107

11Validation of optimizer result

11.1.1 Optimizer log
The optimizer log is available after running transaction /SAPAPO/SNPOPLOG.
To find the optimization you want to analyze, read job log for the actual optimization and note the start time.
Then find this optimization in the optimizer log. Time in batch job and optimizer log could differ a few
seconds.
Press the ”Display Logs” button.
In this log you find a lot of usefull information about the optimization
11.1.1.1 Deletion Time Period
In these 2 files you can find information’s about the periods, for which SNP planned orders and SNP
purchase requisitions are deleted per location product.
29-01-2020 Page 77 of 107

11.1.1.2 Input log
In this folder you can find a lot of useful information about input for the optimization. A few examples will
be shown in this document, but you can yourself find more useful information
All results from the optimizer are based on planning buckets, which could be daily, weekly or monthly. In
input files bucket definitions can be controlled in file ET_BUCKDF:
In ET_LOCMAT you can find stock related informations per location product
In ET_RESOURCE you can find resources included in the optimization
In ET_PROMO you can find PPM information per location product, e.g. lotsizes an production cost
29-01-2020 Page 78 of 107

In ET_LOCPROD you can find informations about safetystock. This file is very useful when searching
locations products with negative safety stock after an optimizer cances with SQL error 181.
11.1.1.3 Results log
In IT_RESOURC you can analyze the capacity utilization per bucket
29-01-2020 Page 79 of 107

In IT_PROMO planned orders can be analyzed per PPM and period. Prod.Qty is reported as a factor to
multiply with the location product lot size.
In IT_DEMAND and IT_NOTDELI you can analyse fulfilled and unfulfilled demands per location product
and bucket. Especially the IT_NOTDELI as is showed below is interesting as unfulfilled demands can course
backlogs.
29-01-2020 Page 80 of 107

11.1.1.4 Message log
Here you find the massage log of the optimization
11.1.1.5 Trace file
In this file the opmimization can be traced. In most cases, you would never find any use in analyzing the
trace file, but if you want to analyze the product decompositions the trace file is useful. Search for the term
“Opportunity”, and click forward until you reach the list of atomic subproblems. Here you can analyze in
which order the products are optimized.
29-01-2020 Page 81 of 107

11.1.2 Alerts
Alerts are analyzes with transaction /SAPAPO/AMON1. Menu track: Supply Chain Monitoring 
/SAPAPO/AMON1 - Alert Monitor.
11.1.2.1 Display alert
You can choose alert profile from the list of profiles assigned to your user account.
29-01-2020 Page 82 of 107

When alert profile is chosen, press the button ”Redetermine alerts” and flag for displaying alerts created in
planning book DEPLOY_STOCK, view DEPLOY_STOCK. The alert is listing backlogs per location
product. To minimize the alert list the backlog is only displayed once per location product.
11.1.2.2 Overall profile
The overall profile for the alert is displayed by pressing the “Overall profile” button.
This overall profile is analyzing backlogs the next 21 days using the SDP alert profile SE_KO53
29-01-2020 Page 83 of 107

Open “Database macro alerts” to see the alert setup. SDP Dynamic Alerts is not used in this profile.
The SDP alert profile is collecting Deployment Backlog (DB) alerts from planning book DEPLOY_STOCK,
view DEPLOY_STOCK with variant JOHLIS SE K53 SNP.
11.1.2.3 Alert creation
Before the alerts is available for the alert monitor, it has to be created by running a macro in planning book
DEPLOY_STOCK, view DEPLOY_STOCK. This backlog alert is created with the macro TOTAL
BACKLOG ALERT, which is displayed below:
29-01-2020 Page 84 of 107

2 other alerts is created inDEPLOY STOCK to manage backlogs. These will not be described indetails in this
document.
29-01-2020 Page 85 of 107

12 SNP Master Data

12.1 SNP Master Data transferred from R/3
Many of the SNP master data is transferred from R/3 to APO, and transferred through the CIF interface.
It goes for:
 Location master
 Resource master
 Product master
 PPM’s
 Procurement relationships
These are documented in details in the CIF support manual, and don’t need further documentation in this
document.
12.2 SNP Master Data maintained in APO

12.2.1 Transportation Lane Master
Assign one or more means of transport to the transportation lane between a source location and a target
location. Make sure that the needed means of transport is defined in customizing, by checkin transaction
S_AP9_75000130. Menu: Master Data  Transportation Lane  S_AP9_75000130 - Maintain Means of
Transport
The transportation lane is maintained with transaction /SAPAPO/SCC_TL1. Menu: Master Data 
Transportation Lane  /SAPAPO/SCC_TL1 - Transportation Lane
29-01-2020 Page 86 of 107

The means of transport is maintained with validity period, transportation calendar, transprotation cost,
ressource and TLB profile(load capacity).
Product specific transportaion lane is then defined per product maintaining validity period and block
indicator. When created the product is assigned to a means of transport. If there only is one means of
transport assignment is done automaticly.
29-01-2020 Page 87 of 107

The block indicator is usefull, if you want to exclude the product temporary from the transportation lane it
can be changed to ”blocked”. Should the product later on be relevant for transprotation, it could be set
“available” again
Transportation lane is created automaticly after transfer of a contract item together with procurement
relationship. This transportation lane descripes the connection between an external vendor and a production
location or distribution center.
This type of transportation lane could be maintained with a means of transport, is planning of transport lots
from vendor is an issue.
12.2.2 Planning Calendar

Planning Calendar is generated for a fixed period, and therefore is happens from time to time that the
planning calendar do not cover the entire planning period any longer It is therefore necessary to regenerate
the calendar.
Calendar maintenance can be maintained from customizing, transaction SPRO. Menu: Advanced Planner and
Optimizer (APO) -> Master Data -> Calendar -> Maintain Planning Calendar (Time Stream).
The calendar can also be maintained from location master, calendar tab.
The calendar used is Z5DAYS for Denmark, Z5DAYS_NO for Norway and for Z5DAYS_SE for Sweden
29-01-2020 Page 88 of 107

The calculation rule is the same for the 3 countries
The bucket is the same for the 3 countries
12.2.3 SNP planner

The SNP planner is used for selecting a group of products to a job variant. Location product is updated with
the SNP planner. Update is done in R/3 material master, and from here transferred the APO location master.
The SNP planner is customized in APO development, and from there transported to QA and production.
Call customizing with transaction SPRO, and follow menu: Advanced Planning and Optimization  Supply
Chain Planning  Supply Chain Planning
Create a new planner with pressing th new entries button.
29-01-2020 Page 89 of 107

You could assign an SNP planner to be used for other planner too, e.g. Production planner for use in PP/DS
selections.
12.2.4 Production version

PP/DS PPM’s are closely connected to a production version, which provides a safe connection with R/3
through the CIF interface,
As a standard this is not the case with SNP PPM’s, which means that production version in a planned order
in R/3 don’t have the connection to production version used in APO. This has given problems with MRP runs
in R/3 as a wrong Bill of Materials has been chosen.
A Carlsberg specific development Z_SNP_PPM_PRODVERS is implemented in APO.
The program reads every PP/DS PPM in the table /SAPAPO/PRODVERZ, and check if a SNP PPM exists
for the production version. If not, a new entry is created in the table with the production version for the SNP
PPM. After creation, SNP planned orders are transferred to R/3 with the correct production version.
The program is used of Denmark and Sweden, included as a step in daily batch jobs, for Denmark in batch
job APO_DK_SNP-OPTIMIZER_PPDS, and for Sweden in APO_SE_SNP_OPTIMIZER_INITIAL.
12.2.5 Update out of stock penalties

Penalties are in the Carlsberg setup maintained on a global basis, and are all updated with the same values.
The maintenance is possible using transaction /SAPAPO/MAT2. You can find the update be calling product
master. From main screen follow menu: Extras  Mass maintenance product penalties cost
To avoid missing penalties a Carlsberg specific program ZCALC_LATE_DELIVERY_COST is executed on

a daily basis in batch job APO_NORDIC_SNP_OPTIMIZER_INITIAL.
Maintenance of penalties for location products is possible using transaction /SAPAPO/MAT3. This is not
implemented in the Carlsberg solution, but could be used to let the optimizer prefer main products before
less important products. A program to update penalties for location products ZCALC_LATE_
DELIVERY_COST_PLANT is found in APO, but is currently not used.
29-01-2020 Page 90 of 107

13 BW SNP Reports
3 info sources is created in APO to collect SNP data in an ODS structure for later transfer to BW.
The Info sources are:
 ZSNPOGL1 collecting planning data for Norway and Sweden from data source CB_SNP_
PLANNING_AREA / 9AMALO(9ASNP_PLANNING) by running the info packages “Full load
SNP PLANNING NO 000 & 101 PC” and “Full load SNP PLANNING SE 000 & 101 PC”. The info
packages are scheduled to run on a daily basis.
 ZSNPOGL2 collecting transportation data is collecting data for Danish, Norwegian and Swedish
locations from data source CB_SNP_PLANNING_AREA / 9AMALA(9ASNP_ PLANNING_
MALA) by running info package “Full load SNP PLANNING NO 000 & 101 PC” on a daily basis.
 ZSNPOGL3 collecting production capacity data for specified resources in Danish, Norwegian and
Swedish locations from data source CB_SNP_PLANNING_AREA / 9AMALORE(9ASNP_
PRODUCT_CAP_2) by running info package Production Capacity DK/NO/SE on a daily basis.
13.1.1 ZSNPOGL1 Planning data

The ODS structure is updated from planning version 000 and 101 with info packages “Full load SNP
PLANNING NO 000 & 101 PC” and “Full load SNP PLANNING SE 000 & 101 PC”.
Selection screen for Norway is collecting data from location 3101 – 3144, products 1 – 79999 and versions
000 and 100 for a period of time defined in an ABAP routine:
29-01-2020 Page 91 of 107

Selection screen for Sweden is collecting data from location 3201 – 3211, products 1 – 9999999999 and
versions 000 and 100 for a period of time defined in an ABAP routine:
29-01-2020 Page 92 of 107

Both packages are updating PSA as fullload
The key figures in ZSNPOGL1 is:
13.1.2 ZSNPOGL2 Transportation data

The ODS structure is updated from planning version 000 with info “9ASNP_PLANNING_MALA”.
Selection screen specifies collection from version for a period of time defined in an ABAP routine:
29-01-2020 Page 93 of 107

The package is updating PSA as fullload
The key figures in ZSNPOGL2 is:
29-01-2020 Page 94 of 107

13.1.3 ZSNPOGL3 Production capacity

The ODS structure is updated from planning version 101 with info package “Production Capacity
DK/NO/SE”.
Selection screen is collecting capacity data from specified resources and versions 101 for a period of time
defined in an ABAP routine:
The package is updating PSA as fullload
The key figures in ZSNPOGL3 are:
29-01-2020 Page 95 of 107

29-01-2020 Page 96 of 107

14 Change request documentation

14.1 Clustering purchasing requisitions
Purpose of CR 4947 is to give the possibility of clustering SNP purchase requisitions in TLB.
14.1.1 Planning flow
14.1.1.1 Planning book
TLB for SNP purchase requisitions CAN NOT be executed from transaction /SAPAPO/SNPTLB - Transport
Load Builder (TLB), but has to be executed from planning book PURCHASE_TLB.
Press the button "TLB View" and select transportation lane
Now clustering of SNP purchase requisitions can be planned as a normal TLB procedure
29-01-2020 Page 97 of 107

14.1.2 Customizing and development Carlsberg IT
14.1.2.1 Implement SAP note 708197
Maintenance of Old TLB profile is not possible after upgrade to version 4.1. Program error can be repaired
by running report /SAPAPO/REPAIR_TLB_PROF_MAINT implemented with note 708197. Repair is
executed in APB, APL and APS.
If it should be necessary to change from old TLB profiles to new TLB profiles this will be possible after
implementing note 707828. This will affect all countries using TLB, so it is decided to postpone it to after go
live for Norway and Sweden in TLB.
14.1.2.2 Implement SAP Note 514947
Sap note 514947 is implemented to create report Z_PB_MVWOBJ_CHANGE. The report open the
possibility to choose if SNP purchase requisitions or deployment purchase requisitions should be visible in
TLB. Allowing SNP requisitions is a onetime run.
14.1.2.3 Create planning book PURCHASE_TLB
Planning book PURCHASE_TLB with view PURCHASE_TLB is created as a copy of Planning book
DEPLOY_STOCK, view DEPLOY_STOCK. The copy is done from transaction /SAPAPO/SDP8B - Define
Planning Book, menu path: Supply Network Planning  Environment  Current Settings 
/SAPAPO/SDP8B - Define Planning Book.
Macroes are activated in PURCHASE_TLB equal to DEPLOY_STOCK in transaction /SAPAPO/ADVM.
Menu path: Supply Network Planning  Environment  Current Settings  /SAPAPO/ADVM - Define
Planning Book.
29-01-2020 Page 98 of 107

14.1.2.4 Execute report Z_PB_MVWOBJ_CHANGE
Report is executed with transaction SA38.
Press execute
Choose SNP and press execute
14.1.2.5 Create category group Z11
Creation of category group is done in customizing APO, transaction SPRO:
Advanced Planning and Optimization  Supply Chain Planning  Supply Network Planning (SNP) 
Basic Settings  Maintain Category Groups
14.1.2.6 Adjust integration model DK_TRADING
As clustering of purchase requisitions only is possible for SNP and only is possible pointing to procurement
relationships for purchase info records it is necessary to change integration model DK_TRADING, so
products to be planned by this functionality is excluded from transfer of contracts.
29-01-2020 Page 99 of 107

After transfer the procurement relationships related to contracts is inactivated, so only the relationship
assigned to info records is active.
14.1.3 Master data update by business
14.1.3.1 Assign category group Z11 to vendor location
Assign Z11 as ATD issue in vendor location
14.1.3.2 Material master
 Check that MRP planner is 021, which is a prerequisite for transfer of procurement relationships.
 As we change from planning in PP/DS to planning in SNP planning horizon has to be changed from
900 to e.g. 5 days.
14.1.3.3 Planning jobs
The materials that should be planned as SNP instead of PP/DS have to be excluded from PP/DS heuristic and
added to a SNP optimizer step. Business takes care of the move.
14.2 Production quarantine using QM-lot

This functionality is implemented with change request CR 4997. Find documentation of the change request
below:
14.2.1 Planning flow
14.2.1.1 Functionality in brief
Purpose of CR 4997 is to give the possibility of setting production into quarantine a number of days before it
is available in unrestricted stock. The production will be posted in quality stock, and a QM-lot is created to
report when the quantity is expected in unrestricted stock. At end of the quarantine the quantity is released
with a usage decision of inspection lot, which posts the quantity in unrestricted stock and deleted the QM-lot.
29-01-2020 Page 100 of 107

14.2.1.2 Create process order and inspection lot
Create process order as usual by converting an APO PP/DS order.
Release the process order. At release an inspection lot of origin 04 will be created. Inspection end date will
be maintained as production date in the process order + average inspection duration from the material master.
14.2.1.3 Goods receipt
Goods receipt will be posted as usual from Astro in Norway and Sweden and from pallet system in Denmark.
Be aware that posting will be to quality stock because of the setting in material master for plant material.
The expected day for end of quarantine is maintained in a QM-lot.
14.2.1.4 Display QM-lot
The QM-lot with the expected date of quarantine end is visible in R/3 and APO.
In R/3 QM-lot is visible in stock requirement list, transaction MD04
In APO PP/DS the QM-lot is visible in product view
29-01-2020 Page 101 of 107

In APO SNP the QM-lot is visible in planning book, key figure "Production (Confirmed)" together with
PP/DS orders and process orders. In details it is represented as category BU.
14.2.1.5 Change QM-lot date
As the QM-lot date is updated in the inspection lot at process order release calculated from expected
production date, it might from time to time be necessary to change it.
Call inspection lot change, transaction QA02
Change inspection end date and save. QM-lot will be changed in both R/3 and APO.
14.2.1.6 End quarantine for the total quantity
Quarantine is ended by giving a usage decision to the inspection lot.
29-01-2020 Page 102 of 107

The usage decision can be called from result recording QE51N by dubbel clicking on the inspection lot
number, or by calling transaction QA11.
Update usage decision code and save.
Now the quantity is moved from quality stock to unrestricted stock, and the QM-lot is deleted in both R/3
and APO
14.2.1.7 End quarantine for part of the quantity
If not the total quantity should be released to unrestricted stock, quantities have to be posted before the usage
decision is given.
Call the usage decision from result recording or QA11 as described above, and select the tab strip
"Inspection lot stock".
In the example below 1800 of 2000 PC is released. The remaining quantity 200 PC is updated in QM-lot in
R/3 and APO.
29-01-2020 Page 103 of 107

After this 100 PC is scrapped. QM-lot is updated with the remaining 100
To control the stock use transaction MMBE
You can see that for the batch in example 0014092671 unrestricted stock is 1800, and quality stock is 100.
29-01-2020 Page 104 of 107

We release the remaining 100 to unrestricted stock and by following the menu path Environment  Material
movements you can control the flow in more details:
2000 PC is issued from order with movement type 101
100 PC is moved from quality stock to unrestricted stock with movement type 321
1800 PC is moved from quality stock to unrestricted stock with movement type 321
100 PC is moved out of stock with movement type 553
Important
It is important that quality inspection stock is 0 before usage decision is given as described above from the
tab strip "Characteristics".
14.2.2 Customizing and integration models
14.2.2.1 Open for QM integration
QM integration is set in R/3 customizing, transaction SPRO.
Menu path: Integration with Other SAP Components  Advanced Planning and Optimization 
Application-Specific Settings and Enhancements  Settings and Enhancements for Inspection Lots  Set
Up Transfer of Inspection Lots to SAP APO
Key in Logical system and flag Allow Insp. lot
You can choose logical systems defined as target systems in R/3 customizing menu path: Integration with
Other SAP Components  Advanced Planning and Optimization  Basic Settings for Setting Up the
System Landscape  Set Target System and Queue Type
29-01-2020 Page 105 of 107

14.2.2.2 Add QM-lot to order category group FP1
Category BU for QM-lot is added to category group FP1 to make it visible in SNP planning book in the key
figure "Production (Confirmed)"
Menu path in customizing APO, transaction SPRO:
Advanced Planning and Optimization  Supply Chain Planning  Supply Network Planning (SNP) 
Basic Settings  Maintain Category Groups
14.2.2.3 Create and active integration models
Create integration models in transaction CFM1. Save variants for use in batch jobs.
Find below example for variant for Sweden, integration model SE_FERTQM
29-01-2020 Page 106 of 107

Activate the integration model with transaction CFM2.
When the functionality is introduced for a country, creation and activation of QM-lot will be included in the
master data batch job.
14.2.2.4 Suppress transfer of inspection stock
Transfer of stocks in the core interface need to be changed so inspection stock is no longer transferred. If not,
inspection stock is taken into account in APO at goods receipt and with QM-lot.
Maintain BAdI for stock transfer with APO, transaction ZAPOCAT, and add a new entry per plant to be
implemented:
14.2.3 Business maintenance of master data

Activation of production quarantine for a plant material is maintained in material master by changing the
inspection type 04.
Set flag for "Post to insp. Stock", maintain AVG inspection duration with the number of days for quarantine
and save the changes.
The inspection type will post goods receipt to quality stock, and create a QM lot in R/3 and APO on the end
of average inspection duration.
29-01-2020 Page 107 of 107

Apo SNP

Încărcat de

Informații document

Titlu original

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

Apo SNP

Încărcat de

Drepturi de autor:

Formate disponibile

Carlsberg IT A/S 457425880.

29-01-2020 Page 1 of 107

2.2.1 SNP Optimizer............................................................................................................7

2.2.2 SNP Deployment........................................................................................................7

2.2.3 Transport Load Builder (TLB)......................................................................................8

3.1 Optimizer servers..............................................................................................................................9

3.2 Planning area..................................................................................................................................10

3.2.2 LiveCache reorganisation.........................................................................................13

3.3 Version management (Active and inactive).....................................................................................14

3.3.1 Current versions........................................................................................................14

3.3.2 Create version.......................................................................................................... 15

3.3.3 Copy version............................................................................................................. 16

3.4 Planning books...............................................................................................................................17

3.4.1 Assignment of planning book to user........................................................................17

3.4.2 Define time buckets to use in planning views............................................................17

3.4.6 Other planning books assigned to SNP Planning area..............................................23

4 Integration between APO and R/3....................................................................................................... 24

4.1 APO customizing............................................................................................................................24

4.1.2 Transfer with change pointers...................................................................................24

4.2 Integration models..........................................................................................................................26

29-01-2020 Page 2 of 107

4.3.1 Post processing monitor...........................................................................................26

4.3.2 CIF comparison.........................................................................................................26

4.3.3 Realign sales orders in R/3 and APO........................................................................27

5 Release Forecast to SNP...................................................................................................................... 30

5.2 Forecast consumption.....................................................................................................................30

5.2.1 SNP Requirements Strategies..................................................................................30

5.2.2 Forecast Consumption..............................................................................................31

6 Safety Stock Planning.......................................................................................................................... 33

6.1 Safety stock strategies.....................................................................................................................33

6.1.1 Calculations based on forecast accuracy and service level......................................33

6.1.2 Fixed safety stock copied from product master.........................................................34

6.1.3 Safety stock calculated from original forecast...........................................................34

6.2 Country specific safety stock calculation........................................................................................34

7.1 Cost profile.....................................................................................................................................47

7.2 Optimizer profiles...........................................................................................................................49

7.2.1 SNP optimizer profiles...............................................................................................49

7.2.2 COPT10 parameters for SNP optimizer profiles........................................................52

7.2.3 Deployment optimizer profiles...................................................................................52

8.1 Preconditions and optimization flow..............................................................................................53

8.1.2 Optimizer flows......................................................................................................... 53

8.2 Linear optimization.........................................................................................................................55

29-01-2020 Page 3 of 107

8.4 Order conversion to PP/DS.............................................................................................................58

8.5 Optimizer Batch jobs......................................................................................................................59

8.6 Inactive versions.............................................................................................................................64

8.6.1 Version 100............................................................................................................... 64

8.6.2 Version 101............................................................................................................... 64

8.6.3 Other versions.......................................................................................................... 65

9 Special SNP functionality..................................................................................................................... 66

9.1 Planning with production quarantine..............................................................................................66

9.1.1 Functionality in brief..................................................................................................66

9.1.2 Planning flow............................................................................................................ 66

9.2 Transport load builder for SNP orders............................................................................................68

10.1 Deployment optimization................................................................................................................70

10.1.1 Optimizer run............................................................................................................ 70

10.1.2 Maintain category groups..........................................................................................71

10.2 Deployment optimizer batch jobs...................................................................................................72

10.3 Transport Load Builder...................................................................................................................76

11 Validation of optimizer result........................................................................................................... 77

11.1.1 Optimizer log............................................................................................................. 77

12 SNP Master Data............................................................................................................................... 86

12.1 SNP Master Data transferred from R/3...........................................................................................86