Masterdata for Snp apo

8/21/2019 Masterdata for Snp apo

1/32

Master Data Setup for the HeuristicPurpose

This section lists all the master data you have to create to run the heuristic successfully in Supply Network Planning.

It lists all of the required fields and other data considered by the heuristic. Use this information as a checklist beforeyou run the heuristic to make sure you have created all the master data for your supply chain model.

For detailed information, see the field-level help (F1 help). For more information, see the APO

master data document.

If you want to work with local time zones, you have to set the Local Time Zone indicator

in Model and Version Management. If you do not set this indicator, we recommend that you use

the UTCtime zone. When using local time zones, we also recommend that you use the same time

zone for both the location and the planning calendar or for the location and the resource.

Process Flow

1. Create Locations (that are not product-dependent)

Location type

Storage resource

Handling resource

Calendar (production, shipping)

ATD category groups (for deployment, TLB)

Time zone

2. Create products

Tab page/screen Field

Initial screen and header

data

Lot size profile

Demand profile

SNP demand profile

SNP supply profile

Deployment profile

Base unit

Attributes Gross weight

Volume

Units of Meas. Define a conversion from the volume unit into the base unit of measure (based on the unit of measure of the

planning area)

Lot size Procedure (lot-for-lot, fixed lot size etc.)

Safety stock method

SNP 2 SNP production horizon

SNP stock transfer horizon

These two horizons are also relevant if you are using Production Planning and Detailed Scheduling

(PP/DS).

Procurement Procurement type


2/32

Planned delivery time (with external procurement)

GR/GI Handling capacity consumption

Storage consumption

3. Create Resources (optional).

You have the option of creating the following resource types for Supply Network Planning: Single-mixed resource

Multimixed resource

Bucket resource

Transportation resource

Use single-mixed or multimixed resources if you want to use the resources for both Supply

Network Planning and Production Planning and Detailed Scheduling (PP/DS). Bucket resources

can only be used for SNP. We recommend that you create mixed resources if possible. Note

however that bucket-oriented block planning is possible in PP/DS in conjunction with SNP only if

you are using different resources for block planning in PP/DS and Supply Network Planning. You

ensure this by setting the Not SNP-Relevnt indicator for the resource used in PP/DS.

To create transportation resources, use the same procedure as for creating bucket resources.

For general information about creating resources, see the resourcesection in the APO master

data document. Below is a list of the exact data you have to define for heuristic-based planning in

SNP.

Single/Multimixed Resources

Tab

page/screen

Field

Standard

Capacity

You must define the available bucket capacity:

Bucket definiton - if you choose From Cont.Capacity, the PP/DS available capacity is used to generate

the available bucket capacity. You can also define a loss factor here (for maintenance or setup times for

example). If you choose Maintain, you must enter the following additional data:

Period type

Number of periods

Bucket capacity

Rate of bucket-oriented capacity utilization (%)

You can use the Bucket Capacity button to display the available bucket capacity that was defined for the individual

buckets.

You can also still define an available capacity profile and capacity variants, and change the periodicity and capacity of

individual buckets. For more information, see the APO master data document.

Bucket Resources


General Data Resource

Resource category

Locationif you define a location, the system adopts the time zone from the location master data; if

not, you have to enter the time zone
http://help.sap.com/saphelp_SCM700_ehp02_hana/helpdata/en/74/a07337e68ac526e10000009b38f889/frameset.htmhttp://help.sap.com/saphelp_SCM700_ehp02_hana/helpdata/en/74/a07337e68ac526e10000009b38f889/frameset.htmhttp://help.sap.com/saphelp_SCM700_ehp02_hana/helpdata/en/74/a07337e68ac526e10000009b38f889/frameset.htmhttp://help.sap.com/saphelp_SCM700_ehp02_hana/helpdata/en/74/a07337e68ac526e10000009b38f889/frameset.htmhttp://help.sap.com/saphelp_SCM700_ehp02_hana/helpdata/en/74/a07337e68ac526e10000009b38f889/frameset.htmhttp://help.sap.com/saphelp_SCM700_ehp02_hana/helpdata/en/74/a07337e68ac526e10000009b38f889/frameset.htm


3/32

Time zone

Planner group

Factory calendar

Active variant

Reference resource

Planning Parameters Day -/Day + - validity period for the resource capacity

Overload (%)

Minimum load (%)

Standard Capacity Period type

Number of periods

Bucket capacity


Capacity variants

button

You can define up to 99 capacity variants in order to define the available capacity for specific validity periods.

Capacity variant

Valid from/to

Rate of bucket-oriented capacity utilization (%) Quantity/rate definition

The system takes into account the default available capacity for periods without a capacity variant.

Definitions button You use the quantities/rates definition to define the available capacity for the capacity variant.

Qty/rate definition (name)

Valid to

Planner group

Number of periods

Period type

Bucket capacity

Unit

4. You assign resources to locations in location master data

5. You create PPMs


Initial screen Plan number

Use of a plan: S(for SNP)

Operations Description of PPM

Operation

Description (of operation)

Activities In Supply Network Planning, each activity must be at least one day long or a multiple of one

day. Each operation can contain only one activity.

Activity number

Description (of activity)

Activity type

Scrap %

Components Product


4/32

Input/output indicator

From date

To date

Unit of measure

Material consumption (variable)

Time-dependent data, if required

Modes Mode - you can specify only one mode per activity

Unit of measure (must be Day)

Fixed duration

Primary resource (required only if resources are connected to this PPM)

Location (required only if resources are connected to this PPM)

Resource consumption (rate) and Unit (required only if resources are connected

to this PPM)

Resources Resource (can enter several, but required only if resources are connected to this

PPM)

Unit of measure (required only if resources are connected to this PPM)

Calendar resource (for the entire PPM)

Variable and fixed bucket consumption (required only if resources are connected

to this PPM)

Time-dependent data, if required

Activity relationships -

Predecessor/successor tab pages

Operation name

Activity number

Product plan assignment button PPM and description

Output product

Validity (date/time)

Location

Procurement priority

Period factor

Minimum and maximum lot size

6. You create transportation lanes in the Supply Chain Engineer or in master data.

Means of transport (using the Aggr. Planning key figure)

Transportation calendar

Procurement priority

For more information, seeSupply Chain Model Set Up.

7. You have the option of creating quota arrangements in the Supply Chain Engineer or in master data.

Quota arrangement at location, external procurement relationship, or in-house production (PPM) Quota arrangement (percentage)

If you do not define any quota arrangements, you must determine a procurement priority on the

transportation lane, or in the PPM for automatic source determination. If both quota arrangements

and procurement priorities have been defined, the heuristic includes the quota arrangements.
http://help.sap.com/saphelp_SCM700_ehp02_hana/helpdata/en/c7/707b37db6bcd66e10000009b38f889/content.htmhttp://help.sap.com/saphelp_SCM700_ehp02_hana/helpdata/en/c7/707b37db6bcd66e10000009b38f889/content.htmhttp://help.sap.com/saphelp_SCM700_ehp02_hana/helpdata/en/c7/707b37db6bcd66e10000009b38f889/content.htmhttp://help.sap.com/saphelp_SCM700_ehp02_hana/helpdata/en/c7/707b37db6bcd66e10000009b38f889/content.htm


5/32

ResultOnce you have set up the master data, you have toset up the supply chain modelin the Supply Chain Engineer

before you can perform any planning runs.

Configuring Master Data for the Optimizer

Purpose

This section lists all the master data that must be created to successfully run the optimizer in Supply Network

Planning. It also lists all the required entry fields and other data that the optimizer takes into account. Use this

information as a checklist before you run the optimizer to make sure you have maintained all the master data for

your supply chain model.

For detailed information, see the field-level help (F1 help). For more information, see the SAP

APO master data documentation.





Process

1. You create locations (that are not product-dependent).

Location type

Storage resource

Handling resource

Calendar

Time zone

2. You create products.

Tab

Page/Screen

Field

Header data Base Unit of Measure

Attributes Gross Weight and Unit

Volume and Unit

Shelf Life

Units of

Measure

Define a conversion from the volume unit into the base unit of measure (based on the unit of measure of the planning

area)

SNP 1 For customer demand, demand forecast, and the corrected demand forecast. Location-dependent penalty costs are also

available.

No delivery penalty

Delay penalty

Maximum lateness

SNP 2 SNP production horizon

SNP stock transfer horizon


6/32

SNP forecast horizon

The first two horizons are also relevant if you are using Production Planning and Detailed Scheduling (PP/DS).

You can specify in the SNP optimizer profileon theIntegration tab page whether the horizons are to be taken into

account or not.



Cost function (with external procurement)

Procurement costs

Production storage costs

Penalty costs for shortfall of safety stock

GR/GI Handling capacity consumption - if not specified, the optimizer uses the Volume specified on

theAttributes tab page as the default value.

Storage consumption - if not specified, the optimizer uses the Volume specified on the Attributes tab

page as the default value.

3. You create resources.You have the option of creating the following resource types for Supply Network Planning:

Single-mixed resource

Multimixed resource

Bucket resources


Use single-mixed resources or multimixed resources if the resources are to be used for both

Supply Network Planning and Production Planning and Detailed Scheduling (PP/DS). A bucket

resource can only be used for SNP. We recommend that you create mixed resources if

possible. Note however that bucket-oriented block planning is possible in PP/DS in conjunctionwith SNP only if you are using different resources for block planning in PP/DS and Supply

Network Planning. You ensure this by setting the Not SNP-Relevnt indicator for the resource used

in PP/DS.


For more information about creating resources, see the resourcesection in the SAP APO master data

documentation. Below is a list of the data that must be defined for optimization-based planning in SNP.

Single-Mixed Resources/Multimixed Resources

Tab

Page/Screen

Field

StandardCapacity

You must define the available bucket capacity: BucketsIf you choose Buckets from Conti., the PP/DS available capacity is used to generate the

available bucket. You can also define a loss factor (for maintenance or setup times, for example,)

here.If you choose Maintain Buckets, you must enter the following additional data:

Period type

Number of periods

Bucket capacity

Utilization rate for bucket-oriented capacity (%)
http://help.sap.com/saphelp_SCM700_ehp02_hana/helpdata/en/c0/717b37db6bcd66e10000009b38f889/frameset.htmhttp://help.sap.com/saphelp_SCM700_ehp02_hana/helpdata/en/c0/717b37db6bcd66e10000009b38f889/frameset.htmhttp://help.sap.com/saphelp_SCM700_ehp02_hana/helpdata/en/c0/717b37db6bcd66e10000009b38f889/frameset.htmhttp://help.sap.com/saphelp_SCM700_ehp02_hana/helpdata/en/74/a07337e68ac526e10000009b38f889/frameset.htmhttp://help.sap.com/saphelp_SCM700_ehp02_hana/helpdata/en/74/a07337e68ac526e10000009b38f889/frameset.htmhttp://help.sap.com/saphelp_SCM700_ehp02_hana/helpdata/en/74/a07337e68ac526e10000009b38f889/frameset.htmhttp://help.sap.com/saphelp_SCM700_ehp02_hana/helpdata/en/74/a07337e68ac526e10000009b38f889/frameset.htmhttp://help.sap.com/saphelp_SCM700_ehp02_hana/helpdata/en/c0/717b37db6bcd66e10000009b38f889/frameset.htmhttp://help.sap.com/saphelp_SCM700_ehp02_hana/helpdata/en/74/a07337e68ac526e10000009b38f889/frameset.htmhttp://help.sap.com/saphelp_SCM700_ehp02_hana/helpdata/en/c0/717b37db6bcd66e10000009b38f889/frameset.htmhttp://help.sap.com/saphelp_SCM700_ehp02_hana/helpdata/en/74/a07337e68ac526e10000009b38f889/frameset.htmhttp://help.sap.com/saphelp_SCM700_ehp02_hana/helpdata/en/c0/717b37db6bcd66e10000009b38f889/frameset.htmhttp://help.sap.com/saphelp_SCM700_ehp02_hana/helpdata/en/74/a07337e68ac526e10000009b38f889/frameset.htmhttp://help.sap.com/saphelp_SCM700_ehp02_hana/helpdata/en/c0/717b37db6bcd66e10000009b38f889/frameset.htm


7/32

You can use the Available Bucket Capacity button to display the defined available bucket capacity for the individual

buckets.

You can also still define an available capacity profile and capacity variants, and change the periodicity and capacity of

individual buckets. For more information about this, see the SAP APO master data documentation.

You can define costs for the SNP optimizer in the capacity profile or in the quantity/rate definition for the individual

capacity variants (for details, see the Capacity variants button section below).

Planning

Parameters

Cross-period lot sizes (only valid for single-mixed resources!) - set this indicator if you want to run SNP optimizer

cross-period lot size planning on this resource.

Bucket Resources

Tab Page/Screen Field


Resource category

Locationwhen you define a location, the system refers to the time zone from the location

master data, otherwise you have to enter the time zone.

Time zone

Planner

Factory calendar

Active variantinformation about the active variant of a resource is required for liveCache

purposes only. If you have defined multiple capacity variants, you should specify the maximum

capacity variant as the active variant or, if this has not been defined, the normal capacity

variant. During the capacity check in interactive planning, the system considers the active

variant. For more information, see the explanation of the Capacity Variants button.

Planning Parameters Day -/Day + - The resource capacitysvalidity period

Capacity overload (%)

Minimum load (%)

Cross-period lot size planning - Activate this indicator if you want to run an SNP optimizer

cross-period lot size planning on this resource.


Number of periods

Bucket capacity

Utilization rate for bucket-oriented capacity (%)

Capacity Variants

Button

Capacity variant

Valid from/to

Capacity utilization

Qty/rate definition

You can define multiple capacity variants and use a status indicator to label the available capacity of this variant

as normal capacity, maximum capacity, or minimum capacity.You can define costs for using the normal or

maximum capacity and for falling below the minimum capacity in the quantity/rate definition or the capacity

profile of the resource.The SNP optimizer then takes these costs into account during planning. However, the

SNP optimizer only takes into account the minimum available capacity and the costs you defined for a capacity

variant with the status Normal Capacity for production resources.

You define the status indicator globally for all resources that have been assigned with the capacity variant. From

the resource initial screen, choose Current Settings Capacity Variants.The default value is a maximum


8/32

capacity (blank field). If you have defined multiple capacity variants with the same status, the system uses the

smallest numbered variant.

We recommend that on the General Data tab page you always define the maximum capacity variant as the

active variant or, if this has not been defined, the normal capacity variant.

The system includes the default available capacity for periods for which you have not created a capacity

variant. If the normal capacity is below the minimum capacity, the system uses the normal capacity as the

minimum capacity.If the normal capacity exceeds the maximum capacity, the system uses the normal capacity

as the maximum capacity.

The SNP optimizer does not consider the Workdays field for planning. The optimizer considers the entries

within this field when calculating the available capacity of the capacity variant but always uses the factory

calendar for planning.

Definitions Button - the

Quantities/Rates Tab

Page

You use the Qty/Rate Definition to define the available capacity for the capacity variant.


Valid to

Planner

Number of periods

Period type

Bucket capacity

Unit

CostsYou define costs for falling below a minimum capacity or for using a normal or

maximum capacity (you define costs for a capacity variant that you assign with status Minimum

Capacity, Normal Capacity, or blank ( = maximum capacity). For more information, see

the Capacity Variants Button section above. The optimizer only takes into account costs you

define for a capacity variant with status Normal Capacity if the resource is a production

resource.)

4. You assign resources to locations in the location master data.

5. You create PPMs.Tab Page/Screen Field

Initial screen Plan number

Use of a plan: S(for SNP)

Operations Description of PPM

Single level costs

Cost function (cost profile)

Operation

Description (of operation)

Activities In Supply Network Planning, each activity must be at least one day long or a multiple of one

day. Each operation can also contain only one activity.

Activity number

Description (of activity)

Activity category

Scrap %

Components Product

Input/output indicator


9/32

From date

To date

Unit of measurement

Material consumption (variable)

Time-dependent data

Modes Mode - you can specify only one mode per activity

Unit of measure (must be Day)

Duration (fixed)

Primary resource (required only if resources are connected to this PPM)

Location (required only if resources are connected to this PPM)

Resource consumption (rate) and unit (required only if resources are connected

to this PPM)

Resources Resource (can enter several, but required only if resources are connected to this

PPM)

Unit of measure (required only if resources are connected to this PPM)

Calendar resource (for the entire PPM)

Variable and fixed bucket consumption (required only if resources are

connected to this PPM)

Time-dependent data

Activity relationships -

Predecessor/successor Tab Pages

Operation name

Activity number

Product plan assignment button PPM and description

Validity (date/time)

Location

Discretization

Bucket offset

Minimum and maximum lot size

Results

After you have configured the master data, you mustset up the supply chain modelin the Supply Chain Engineer,

including the creation and maintenance of transportation lanes, before you can perform any planning runs.

Master Data Setup for Supply & Demand

Propagation

Purpose

The master data fields that are supported by Supply & Demand Propagation are listed below.


10/32

Process Flow

You must enter the products and locations and assign the location products to a model.

You can enter the data, which should be taken into account during Supply & Demand Propagation, in

the fields listed below:

Product Master

Tab Field

Attributes Gross weight and unit

Volume and unit

SDP relevance (Optional field)

Product Location Master

Tab Field


The procurement type in the location product master is essential for Supply & Demand Propagation. By choosing a

procurement type, you prioritize the various procurement options used in propagation. The options available are:

E and no PPM: Check inventory first.

E and PPM: Check storage location first, then produce

F and no incoming transportation lanes: Check storage location first, then create external procurement

F and incoming transportation lanes: Check storage location first, then create stock transfer receipts

X and PPM and incoming transportation lanes: Check storage location first, then produce, then use stock transfer receipts

Other combinations using X: Analogous to E and F .

P: Check storage location first.

GR/GI Optional Fields:

Goods rcpt timeGoods issue time

HandlCap consump. GR and unit

HandlCap consump. GI and unit

Master Data Setup for Aggregated PlanningUse

In aggregated planning,you execute the SNP heuristic or the SNP optimizer at header location product level of a

location product hierarchy. To do so, you must first have made the general master data settings for running the SNP

heuristic or the SNP optimizer. For more information, seeMaster Data Setup for the HeuristicandMaster Data

Setup for the Optimizer.There are also some distinct features for aggregated planning described below that you

must remember when defining the master data.

You must define all the master data at sub product level as well as at header product level. That

means that the system cannot automatically generate the master data from sub product level.
http://help.sap.com/saphelp_SCM700_ehp02_hana/helpdata/en/2c/c557e9e330cc46b8e440fb3999ca51/frameset.htmhttp://help.sap.com/saphelp_SCM700_ehp02_hana/helpdata/en/2c/c557e9e330cc46b8e440fb3999ca51/frameset.htmhttp://help.sap.com/saphelp_SCM700_ehp02_hana/helpdata/en/2c/c557e9e330cc46b8e440fb3999ca51/frameset.htmhttp://help.sap.com/saphelp_SCM700_ehp02_hana/helpdata/en/25/a4e44a64fe11d3b6390000e82de178/content.htmhttp://help.sap.com/saphelp_SCM700_ehp02_hana/helpdata/en/25/a4e44a64fe11d3b6390000e82de178/content.htmhttp://help.sap.com/saphelp_SCM700_ehp02_hana/helpdata/en/25/a4e44a64fe11d3b6390000e82de178/content.htmhttp://help.sap.com/saphelp_SCM700_ehp02_hana/helpdata/en/25/a4e44d64fe11d3b6390000e82de178/content.htmhttp://help.sap.com/saphelp_SCM700_ehp02_hana/helpdata/en/25/a4e44d64fe11d3b6390000e82de178/content.htmhttp://help.sap.com/saphelp_SCM700_ehp02_hana/helpdata/en/25/a4e44d64fe11d3b6390000e82de178/content.htmhttp://help.sap.com/saphelp_SCM700_ehp02_hana/helpdata/en/25/a4e44d64fe11d3b6390000e82de178/content.htmhttp://help.sap.com/saphelp_SCM700_ehp02_hana/helpdata/en/2c/c557e9e330cc46b8e440fb3999ca51/frameset.htmhttp://help.sap.com/saphelp_SCM700_ehp02_hana/helpdata/en/2c/c557e9e330cc46b8e440fb3999ca51/frameset.htmhttp://help.sap.com/saphelp_SCM700_ehp02_hana/helpdata/en/2c/c557e9e330cc46b8e440fb3999ca51/frameset.htmhttp://help.sap.com/saphelp_SCM700_ehp02_hana/helpdata/en/25/a4e44d64fe11d3b6390000e82de178/content.htmhttp://help.sap.com/saphelp_SCM700_ehp02_hana/helpdata/en/25/a4e44d64fe11d3b6390000e82de178/content.htmhttp://help.sap.com/saphelp_SCM700_ehp02_hana/helpdata/en/25/a4e44a64fe11d3b6390000e82de178/content.htmhttp://help.sap.com/saphelp_SCM700_ehp02_hana/helpdata/en/2c/c557e9e330cc46b8e440fb3999ca51/frameset.htm


11/32

In the following setting recommendations, the use of the word shouldmeans that planning can

otherwise lead to incorrect or unexpected results.

Settings

Create Products and Locations

The following distinct features apply to aggregated planning:

You execute aggregated planning at header location product level. A header location product is the header

product of a location product hierarchy that you have generated from a location hierarchy and a product

hierarchy (see Create Hierarchies section). You create all the levels of these two-level hierarchies as standalone

products and locations in the product and location master data.

If you want to plan multiple levels (locations) of your network, the same header products should be defined in all

locations. There should not be any cycles in your network.

SNP disaggregation takes into account the rounding values and lot size parameters defined for the individual

header and sub products. If you want to ensure that during SNP disaggregation there are no remainders at

header product level, the rounding values defined at sub product level must be the same within a location

product hierarchy. The rounding value of the header product must be a multiple of the value at sub product

level. In addition, the minimum lot size at header level should be larger than or equal to the minimum lot size

defined at sublevel.

The procurement type defined at header product level should also be supported at sub product level.

The same SNP production horizon, extended SNP production horizon, and SNP stock transfer horizon should be

defined for all products of the location product hierarchy (including the header product).

Create Resources, PPMs/PDS and Tr ansportation Lanes

The following distinct features apply to aggregated planning:

If you carry out optimization-based planning with resources, you must also always create a resource at header

product level. The SNP optimizer uses the resource and costs defined at header product level for aggregated

planning. Creating resources is optional for the SNP heuristic.

To ensure that the resource consumption of fixed orders at sub product level is correctly taken into account

during planning, you should note the following restrictions for creating resources:

You should use the same resources at header and sub product level. If you use a resource hierarchy, this

restriction does not apply.

The resource consumption of the production process models (PPMs) or production data structures (PDSs),

and transportation lanes at header and sub product level should be similar.

The total of the resource capacities defined at header product level should form the resource capacity at sub

product level. If you are using several PPMs/PDSs at sub product level, the resource consumption of the

PPM/PDS at header product level should form the resource consumption of the different PPM/PDSsat sub

product level.

For external procurement, the same transportation lanes must apply for the header and sub products, since SNP

aggregation and disaggregation use the source determination decisions from header product level.

Create Hierarchies

Standard hierarchy structures are already assigned to the standard planning area 9ASNP02. You can create

hierarchies for location products, resources, and PPMs based on these structures. In SNP Customizing, you can also

create your own hierarchy structures and assign them to your planning area. A standard hierarchy structure is also


12/32

predefined for a PDS hierarchy. However, it is not assigned to the standard planning area 9ASNP02, so you have to

assign it to your own planning area.

For more information, see the Implementation Guide (IMG) under Advanced Planning and Optimization Master

Data Hierarchy Define Hierarchy Structure.

Location Product Hierarchy

To create a location product hierarchy required for the standard aggregated planning process, first create a product

hierarchy and a location hierarchy in the SAP-APO master data. You then generate a location product hierarchy

from the product hierarchy and the location hierarchy. The header location product is at the top of a hierarchy tree of

this hierarchy. The sub location products are at the second level. A hierarchy can consist of several hierarchy trees.

You can create the location product hierarchy as a location hierarchy for a product or as a product hierarchy for a

location, for example. In the first instance, you must create a location hierarchy with one header location and

multiple child locations as well as a product hierarchy. In this instance, the product hierarchy can only consist of one

hierarchy level and must contain a sub product. In the second instance (in which you create a product hierarchy for a

location), you have to do the opposite. In addition, when you define the hierarchy structure (see above), you mustspecify in the HierPos field the position in which the hierarchies will be in the generated location product hierarchy.

Example for Creating a Location Product Hierarchy

The figure shows the different possible combinations when you create a location product

hierarchy. In this example, the product hierarchy consists of header product A with sub products B

and C. The location hierarchy consists of header location 1 with sub location 2. In addition, there

are location products A/1, A/2, C/2, and B/3, and location 3.


13/32

The generated location product hierarchy consists of the following levels: Header product/sub

location level (level 1) and sub product/ sub location level (level 2). A/2 is located on level 1 and

C/2 on level 2. C/2 is subordinate to A/2. A/1 is not a component of the generated location product

hierarchy since the header product/header location level was not defined in the generated

hierarchy. B/3 is not a component of the hierarchy since location 3 is not a component of the

location hierarchy and nor are there any header product/sub location nodes for B/3 (which would

then have to be called A/3).

PPM / PDS Hierarchy

For in-house production, you must also create a PPM or PDS hierarchy that contains its own hierarchy tree for each

PPM or PDS at header product level, since SNP aggregation and disaggregation use the source determination

decisions of the header product level. The PPM or PDS hierarchy should be consistent with the location product

hierarchy.

For more information about creating hierarchies, see the hierarchysection in the SAP APO master data

documentation.

Resource HierarchyIf you want to display the resource consumption at header level and you are not using the same resources at header

and sub level in the PPMs or PDS, you should create a resource hierarchy so that the resource consumption is

displayed correctly. This hierarchy should be consistent with the PPM/PDS hierarchy used.

Master Data Setup for Safety Stock Planning

Purpose

This document describes which specific master data you must define for safety stock planning in Supply NetworkPlanning (SNP). For more information, see the associated F1 Help.

Process1. Determine whether you want to use standard or extended safety stock planning.

2. If you use standard safety stock planning, enter the relevant data in the following fields on the Lot Size tab

page in the location product master:

Safety Stock MethodMethods SB, SZ, SM for time-independent determination and methods MB, MZ,

MM for time-dependent determination.

Safety Stock - is considered by the system during safety stock methods SB and SM.

Safety DaysSupply - Considered by the system during safety stock methods SZ and SM.

3. If you use extended safety stock planning, enter the relevant data in the following fields on the Lot Size tabpage in the location product master:

Safety Stock MethodMethods AT, AS, BT and BS.

Service Level (%)

Demand Fcast Err. (%)Can also be calculated by the system using historical data.

RLT Fcast Error (%)Can also be calculated by the system using historical data.

Target DaysSupplyDuring safety stock methods AT and BT the system interprets this value as an order

cycle. During safety stock method BS the system uses this value to calculate the purchase order quantity.
http://help.sap.com/saphelp_SCM700_ehp02_hana/helpdata/en/49/75a7d7e0771ec8e10000000a42189b/frameset.htmhttp://help.sap.com/saphelp_SCM700_ehp02_hana/helpdata/en/49/75a7d7e0771ec8e10000000a42189b/frameset.htmhttp://help.sap.com/saphelp_SCM700_ehp02_hana/helpdata/en/49/75a7d7e0771ec8e10000000a42189b/frameset.htmhttp://help.sap.com/saphelp_SCM700_ehp02_hana/helpdata/en/49/75a7d7e0771ec8e10000000a42189b/frameset.htmhttp://help.sap.com/saphelp_SCM700_ehp02_hana/helpdata/en/49/75a7d7e0771ec8e10000000a42189b/frameset.htm


14/32

Replen. Lead TimeCan also be calculated by the system using historical data.

Min. SFT

Max. SFT

Master Data Setup for the Deployment

HeuristicPurpose

This section lists the master data you have to create to run the deployment heuristic successfully in Supply Network

Planning (SNP). It lists all of the required fields and other data considered by deployment. Use this information as a

checklist before you run deployment to make sure you have maintained all the master data for your supply chain

model.

For more information, see the SAP APO master data documentation.

Process Flow

1. Create locations (choose the SNP tab page in the location master)

ATD receipt

ATD issue

You can define these fields in the location master as well as the location product master. During the

deployment run, the system first checks whether the category group is specified for the location product. If

not, the system checks the entry at location level. If no category group is defined for the location either,

the system uses the standard category groups ATRor ATI.

You define category groups in the Customizing for SNP under Basic Settings Maintain Category

Groups.

Push not allowed

You set this indicator to restrict the locations to which the system distributes the supply available during

deployment. For example, you may not wish to push supply to a location that has low demand.

2. Create products

Deployment profile

If you choose fair share rule C or push rule Q, the system uses the quota arrangements defined in the

Supply Chain Engineer (SCE); therefore, you must also define the quota arrangements when you set up

the supply chain model.

SNP supply profile

SNP demand profile

SNP 2 tab page ATD receipt

ATD issue

(see above)

Lot Size tab page

Maximum lot size

Rounding value
http://help.sap.com/saphelp_SCM700_ehp02_hana/helpdata/en/c7/707b37db6bcd66e10000009b38f889/content.htmhttp://help.sap.com/saphelp_SCM700_ehp02_hana/helpdata/en/c7/707b37db6bcd66e10000009b38f889/content.htmhttp://help.sap.com/saphelp_SCM700_ehp02_hana/helpdata/en/c7/707b37db6bcd66e10000009b38f889/content.htmhttp://help.sap.com/saphelp_SCM700_ehp02_hana/helpdata/en/c7/707b37db6bcd66e10000009b38f889/content.htmhttp://help.sap.com/saphelp_SCM700_ehp02_hana/helpdata/en/c7/707b37db6bcd66e10000009b38f889/content.htmhttp://help.sap.com/saphelp_SCM700_ehp02_hana/helpdata/en/c7/707b37db6bcd66e10000009b38f889/content.htm


15/32

If you have assigned an SNP lot size profile for transportation lanes to the relevant transportation lane, the

system first takes into account the rounding data that you have defined in this profile.

The deployment heuristic does not consider the minimum lot size or the rounding profile, which

you can define on the Lot Size tab page in the location product master data, as well as in the SNP

lot size profile for transportation lanes.

Note in addition that deployment heuristic values generally round down.

Result

After you have set up the master data, you mustset up the supply chain modelin the Supply Chain Engineer before

you can execute a planning run. This includes creating and maintaining transportation lanes.

Master Data Setup for the Deployment

Optimizer

PurposeThis section lists all the master data you have to create to successfully run the deployment optimizer in Supply

Network Planning. It lists all of the required entry fields and other data that the deployment optimizer considers. Use

this information as a checklist before you run the deployment optimizer to make sure you have maintained all the

master data for your supply chain model.

For more information, see the SAP APO master data documentation.





Process Flow1. Create Locations (that are not product-dependent)

Location type

Storage resource

Handling resource

Calendar

ATD category groups (for deployment and the TLB); if you do not make any entries, the optimizer uses

default values

Time zone

2. Create products

Tab

Page/Screen

Field

Header data Base unit

Properties Gross weight and unit

Volume and unit


16/32

Shelf life

Units of Meas. Define a conversion from the volume unit into the base unit of measure (based on the unit of measure of the planning

area)

SNP 1 Penalty costs for customer demand, the demand forecast, and the corrected demand forecast (required only for products

that fulfill demand; not required for components): No delivery penalty

Delay penalty

Maximum delay

SNP 2 SNP stock transfer horizon

This horizon is relevant if you are using Production Planning and Detailed Scheduling (PP/DS).

The deployment optimizer does not consider the forecast horizon. It calculates total demand as a total of the forecast

plus sales orders. If you want the deployment optimizer to consider the forecast horizon, you can set it up by making

changes in Customizing. To do this, see SAP note 412551.

Lot Size Fixed lot size

Minimum lot size

Rounding value



Cost function (with external procurement)

Procurement costs

Product-dependent storage costs

Safety stock penalty

GR/GI Handling capacity consumption. If not specified, the deployment optimizer uses the Volume specified

on the Attributes tab page as the default value

Storage consumption. If not specified, the deployment optimizer uses the Volume specified on

the Attributes tab page as the default value

3. Create Resources

You have the option of creating the following resource types for the deployment optimizer:

Single-mixed resource

Multimixed resource

Bucket resource


For general information about creating resources, see the resourcesection in the APO masterdata document. Below is a list of the data that you must specify for deployment optimizer planning

in SNP.


Bucket resources

Tab Page/Screen Field
http://help.sap.com/saphelp_SCM700_ehp02_hana/helpdata/en/74/a07337e68ac526e10000009b38f889/frameset.htmhttp://help.sap.com/saphelp_SCM700_ehp02_hana/helpdata/en/74/a07337e68ac526e10000009b38f889/frameset.htmhttp://help.sap.com/saphelp_SCM700_ehp02_hana/helpdata/en/74/a07337e68ac526e10000009b38f889/frameset.htmhttp://help.sap.com/saphelp_SCM700_ehp02_hana/helpdata/en/74/a07337e68ac526e10000009b38f889/frameset.htmhttp://help.sap.com/saphelp_SCM700_ehp02_hana/helpdata/en/74/a07337e68ac526e10000009b38f889/frameset.htmhttp://help.sap.com/saphelp_SCM700_ehp02_hana/helpdata/en/74/a07337e68ac526e10000009b38f889/frameset.htm


17/32


Resource category

Locationif you specify a location, the system refers to the time zone from the location master

data; if not, you have to enter the time zone.

Time zone

Planner group Factory calendar

Active variantinformation about the active variant of a resource is required for liveCache

purposes only. If you have defined multiple capacity variants, you should specify the

maximum capacity variant as the active variant or, if this has not been defined, the normal

capacity variant. The system considers the active variant during the capacity check in

interactive planning. For more information, see theCapacity variants button section below.

Planning Parameters Day -/Day + - validity period for the resource capacity

Overload (%)

Minimum load (%)

Finite schedulingis used for lot size planning, that is, the set up status from Production

Planning and Detailed Scheduling


Number of periods

Bucket capacity


Capacity variants

button

Capacity variant

Valid from/to


Quantity/rate definition

You can define multiple capacity variants and use a status indicator to label the available capacity of this

variant as normal capacity, maximum capacity, or minimum capacity. You can define costs for using thenormal or maximum capacity and for falling below the minimum capacity in the quantity/rate definition or the

capacity profile of the resource.The deployment optimizer then takes these costs into account during planning.

However, the optimizer only takes into account the minimum available capacity and the costs you defined for a

capacity variant with the status Normal Capacity for production resources.

You define the status indicator globally for all resources that have been assigned with the capacity variant.

From the resource initial screen, choose: Current Settings Capacity Variants. The default value is a

maximum capacity (blank field). If you have defined multiple capacity variants with the same status, the

system uses the smallest numbered variant.

We recommend that on the General Data tab page you always define the maximum capacity variant as the

active variant or, if this has not been defined, the normal capacity variant.

The system includes the default available capacity for periods that you have not created a capacity variant for.

If the normal capacity is below the minimum capacity, the system uses the normal capacity as the minimum

capacity. If the normal capacity exceeds the maximum capacity, the system uses the normal capacity as the

maximum capacity.

The deployment optimizer does not consider the Workdaysfield for planning. The optimizer does consider the

entries within this field when calculating the available capacity of the capacity variant but always uses the

factory calendar for planning.

Definitions button You use the Qty/Rate Definition to define the available capacity for the capacity variant.


18/32

the Quantities/Rates

tab page


Valid to

Planner group

Number of periods

Period type

Bucket capacity Unit

CostsYou define costs for falling below a minimum capacity or for using a normal or

maximum capacity (you define costs for a capacity variant that you assign with

status: Minimum Capacity, Normal Capacity, or blank ( = maximum capacity)for details, see

the Capacity variants button section above. The optimizer only takes into account costs you

define for a capacity variant with status Normal Capacity if the resource is a production

resource.)

4. Assign resources to locations in location master data

Result

After you have set up the master data, you mustset up the supply chain modelin the Supply Chain Engineer before

you can execute a planning run. This includes creating and maintaining transportation lanes.

See also:

APO master data documentation

Supply Chain Model Setup

Master Data Setup for the Transport Load

Builder

UseIn addition to the general master data settings for planning in Supply Network Planning (SNP)or SAP Supply

Network Collaboration (SAP SNC), you can make additional settings for the Transport Load Builder (TLB). The

following is intended to provide an overview of the TLB settings. For more information, see the input help for the

individual fields.

For more information about master data settings that you can make for the additional functions of

TLB in SAP SNC, see the SAP SNC documentation under Replenishment Transport Load

Builder Additional TLB Functions in SAP SNC.
http://help.sap.com/saphelp_SCM700_ehp02_hana/helpdata/en/c7/707b37db6bcd66e10000009b38f889/content.htmhttp://help.sap.com/saphelp_SCM700_ehp02_hana/helpdata/en/c7/707b37db6bcd66e10000009b38f889/content.htmhttp://help.sap.com/saphelp_SCM700_ehp02_hana/helpdata/en/c7/707b37db6bcd66e10000009b38f889/content.htmhttp://help.sap.com/saphelp_SCM700_ehp02_hana/helpdata/en/c7/707b37db6bcd66e10000009b38f889/content.htmhttp://help.sap.com/saphelp_SCM700_ehp02_hana/helpdata/en/c7/707b37db6bcd66e10000009b38f889/content.htmhttp://help.sap.com/saphelp_SCM700_ehp02_hana/helpdata/en/c7/707b37db6bcd66e10000009b38f889/content.htmhttp://help.sap.com/saphelp_SCM700_ehp02_hana/helpdata/en/c7/707b37db6bcd66e10000009b38f889/content.htm


19/32

Settings

Product Master Data

You make the following settings in the product or location product master data:

Tab Page Field

Attributes Stacking Factor

This field is relevant if you want to use the Pallet Positions TLB parameter in theTLB profile

The stacking factor indicates how many pallets of a product can be stacked on top of each other. For mixed

pallets, the system uses the smallest stacking factor of all products.

Units of measure For the Weight, Volume, and Pallet Positions parameters (only SNP TLB) that you use in the TLB profile, you

must define the conversion of the parameter unit of measure to the base unit of measure for the product.

SNP 2 VMI Purch. Group

The TLB can divide theTLB shipmentsinto individual orders according to the purchasing group of the VMI

customer.

ATD Receipt and ATD IssueThese fields are only considered by the SNP TLB. You can enter the category groups that you have defined

in the SNP Customizing under Basic Settings Maintain Category Groups. Using the category groups, you

define which order categories are included in the quantity that is available for transport load building.

If you do not enter a value here, the system uses the value from the location master data or the standard

category groups ATRand ATI.

Lot Size/Quantity and

Date Determination

Rounding Value

The TLB uses the rounding value for building transport loads. However, the TLB first uses the value that

you have defined in the transportation lane, that is, in the lot size profile (SNP) or transportation guideline

set (SAP SNC). If no value is assigned, the TLB uses the value specified here or 1.

So that the SNP TLB can use this rounding value, you must set the relevant indicator in the SNP

Customizing under Basic Settings Maintain Global SNP Settings. Otherwise, the SNP TLB uses the

rounding value from the transportation lane.

Goods receipt/goods

issue

Handling unit G

The TLB can only pack products with the same handling unit group together in the samehandling unit (HU).

In the SNP TLB, which does not use handling units, this field applies to pallets.

Max. Coverage

The TLB considers the maximum coverage time duringshipment upsizing.The system only brings forward

as manydeployment stock transfersas are necessary to cover demand within this time period.

Shipment Upsizing

For the location product, you specify whether shipment upsizing is allowed and whether it is permitted

beyond the maximum coverage time period.

Loading grp.

The TLB considers the loading group for thestraight loadingloading method.

Not Palletable

You specify whether the location product may be stacked on pallets. If you set this indicator, the TLB does

not consider any pallet positions for this product.
http://help.sap.com/saphelp_SCM700_ehp02_hana/helpdata/en/76/2f7b37e12a7a09e10000009b38f889/content.htmhttp://help.sap.com/saphelp_SCM700_ehp02_hana/helpdata/en/76/2f7b37e12a7a09e10000009b38f889/content.htmhttp://help.sap.com/saphelp_SCM700_ehp02_hana/helpdata/en/76/2f7b37e12a7a09e10000009b38f889/content.htmhttp://help.sap.com/saphelp_SCM700_ehp02_hana/helpdata/en/36/5f0d6bfb14247fe10000009b38f9b7/content.htmhttp://help.sap.com/saphelp_SCM700_ehp02_hana/helpdata/en/36/5f0d6bfb14247fe10000009b38f9b7/content.htmhttp://help.sap.com/saphelp_SCM700_ehp02_hana/helpdata/en/36/5f0d6bfb14247fe10000009b38f9b7/content.htmhttp://help.sap.com/saphelp_SCM700_ehp02_hana/helpdata/en/36/18aa32895864d8e10000009b38f985/content.htmhttp://help.sap.com/saphelp_SCM700_ehp02_hana/helpdata/en/36/18aa32895864d8e10000009b38f985/content.htmhttp://help.sap.com/saphelp_SCM700_ehp02_hana/helpdata/en/36/18aa32895864d8e10000009b38f985/content.htmhttp://help.sap.com/saphelp_SCM700_ehp02_hana/helpdata/en/bf/8cf41cf84ec948b66fc9889d71630e/content.htmhttp://help.sap.com/saphelp_SCM700_ehp02_hana/helpdata/en/bf/8cf41cf84ec948b66fc9889d71630e/content.htmhttp://help.sap.com/saphelp_SCM700_ehp02_hana/helpdata/en/bf/8cf41cf84ec948b66fc9889d71630e/content.htmhttp://help.sap.com/saphelp_SCM700_ehp02_hana/helpdata/en/36/5f0d58fb14247fe10000009b38f9b7/content.htmhttp://help.sap.com/saphelp_SCM700_ehp02_hana/helpdata/en/36/5f0d58fb14247fe10000009b38f9b7/content.htmhttp://help.sap.com/saphelp_SCM700_ehp02_hana/helpdata/en/36/5f0d58fb14247fe10000009b38f9b7/content.htmhttp://help.sap.com/saphelp_SCM700_ehp02_hana/helpdata/en/5a/0c04aae64dae458a8170e183088342/content.htmhttp://help.sap.com/saphelp_SCM700_ehp02_hana/helpdata/en/5a/0c04aae64dae458a8170e183088342/content.htmhttp://help.sap.com/saphelp_SCM700_ehp02_hana/helpdata/en/5a/0c04aae64dae458a8170e183088342/content.htmhttp://help.sap.com/saphelp_SCM700_ehp02_hana/helpdata/en/5a/0c04aae64dae458a8170e183088342/content.htmhttp://help.sap.com/saphelp_SCM700_ehp02_hana/helpdata/en/36/5f0d58fb14247fe10000009b38f9b7/content.htmhttp://help.sap.com/saphelp_SCM700_ehp02_hana/helpdata/en/bf/8cf41cf84ec948b66fc9889d71630e/content.htmhttp://help.sap.com/saphelp_SCM700_ehp02_hana/helpdata/en/36/18aa32895864d8e10000009b38f985/content.htmhttp://help.sap.com/saphelp_SCM700_ehp02_hana/helpdata/en/36/5f0d6bfb14247fe10000009b38f9b7/content.htmhttp://help.sap.com/saphelp_SCM700_ehp02_hana/helpdata/en/76/2f7b37e12a7a09e10000009b38f889/content.htm


20/32

Location M aster Data

You make the following settings in the location master data:

Screen/Tab

Page

Field

Initial screen Loc. Type

This field is relevant if you want to use transportation zones. For more information, seeUse of Transportation

Zones.

SNP ATD Receipt and ATD Issue

If you have not defined category groups for the location product (see above), the SNP TLB considers the category

groups defined here.

Transportation Lane Master Data

You make the following settings for the means of transport in the transportation lane master data:

Stage Field

Means of transport TLB profile

You must assign aTLB profilethat you created previously.

Loading Method

You specify whether you want the TLB to consider thestraight loadingorload balancingloading method.

Pull-In Horizon

If the TLB carries out a shipment upsizing, it considers thepull-in horizon.

Siz.Desn and Shpmt Thr.Val.

In the Siz.Decsn field, you determine how the TLB calculates the value it uses to decide about shipment sizing.

The system compares the base value calculated with the value that you have entered in the ShpmThrVal field

as the threshold value for shipment sizing, and then carries out eithershipment upsizingordownsizing.

Product-Specific

Transportation

T. Lot Prfl

This field is only considered by the SNP TLB. You can enter a profile here that you created in the SNP

Customizing under Basic Settings Profiles SNPLot Size Profiles (Transportation Lanes). The TLB

considers the value defined in this profile (see above).

Production Data Structure in SNP

Structure containing the master data for planning in SAP APO. Production data structures vary in the following

ways:

Origin:

o Generated from iPPE data (product structure, process structure, factory structure)

o Generated from SAP ERP data, that is, classical master data, such as bill of materials, phantom assembly,

work plan, and master recipe.

In both cases, the production version serves as the basis for generating the production data structure.
http://help.sap.com/saphelp_SCM700_ehp02_hana/helpdata/en/6b/0bd64098de8431e10000000a1550b0/content.htmhttp://help.sap.com/saphelp_SCM700_ehp02_hana/helpdata/en/6b/0bd64098de8431e10000000a1550b0/content.htmhttp://help.sap.com/saphelp_SCM700_ehp02_hana/helpdata/en/6b/0bd64098de8431e10000000a1550b0/content.htmhttp://help.sap.com/saphelp_SCM700_ehp02_hana/helpdata/en/6b/0bd64098de8431e10000000a1550b0/content.htmhttp://help.sap.com/saphelp_SCM700_ehp02_hana/helpdata/en/76/2f7b37e12a7a09e10000009b38f889/content.htmhttp://help.sap.com/saphelp_SCM700_ehp02_hana/helpdata/en/76/2f7b37e12a7a09e10000009b38f889/content.htmhttp://help.sap.com/saphelp_SCM700_ehp02_hana/helpdata/en/76/2f7b37e12a7a09e10000009b38f889/content.htmhttp://help.sap.com/saphelp_SCM700_ehp02_hana/helpdata/en/5a/0c04aae64dae458a8170e183088342/content.htmhttp://help.sap.com/saphelp_SCM700_ehp02_hana/helpdata/en/5a/0c04aae64dae458a8170e183088342/content.htmhttp://help.sap.com/saphelp_SCM700_ehp02_hana/helpdata/en/5a/0c04aae64dae458a8170e183088342/content.htmhttp://help.sap.com/saphelp_SCM700_ehp02_hana/helpdata/en/f0/b188e0848da64aa627f7b983b50611/content.htmhttp://help.sap.com/saphelp_SCM700_ehp02_hana/helpdata/en/f0/b188e0848da64aa627f7b983b50611/content.htmhttp://help.sap.com/saphelp_SCM700_ehp02_hana/helpdata/en/f0/b188e0848da64aa627f7b983b50611/content.htmhttp://help.sap.com/saphelp_SCM700_ehp02_hana/helpdata/en/36/3d6d626ae92097e10000009b38f984/content.htmhttp://help.sap.com/saphelp_SCM700_ehp02_hana/helpdata/en/36/3d6d626ae92097e10000009b38f984/content.htmhttp://help.sap.com/saphelp_SCM700_ehp02_hana/helpdata/en/36/3d6d626ae92097e10000009b38f984/content.htmhttp://help.sap.com/saphelp_SCM700_ehp02_hana/helpdata/en/bf/8cf41cf84ec948b66fc9889d71630e/content.htmhttp://help.sap.com/saphelp_SCM700_ehp02_hana/helpdata/en/bf/8cf41cf84ec948b66fc9889d71630e/content.htmhttp://help.sap.com/saphelp_SCM700_ehp02_hana/helpdata/en/bf/8cf41cf84ec948b66fc9889d71630e/content.htmhttp://help.sap.com/saphelp_SCM700_ehp02_hana/helpdata/en/61/a3bb85bc6c1d4c9cd36761c533d062/content.htmhttp://help.sap.com/saphelp_SCM700_ehp02_hana/helpdata/en/61/a3bb85bc6c1d4c9cd36761c533d062/content.htmhttp://help.sap.com/saphelp_SCM700_ehp02_hana/helpdata/en/61/a3bb85bc6c1d4c9cd36761c533d062/content.htmhttp://help.sap.com/saphelp_SCM700_ehp02_hana/helpdata/en/61/a3bb85bc6c1d4c9cd36761c533d062/content.htmhttp://help.sap.com/saphelp_SCM700_ehp02_hana/helpdata/en/bf/8cf41cf84ec948b66fc9889d71630e/content.htmhttp://help.sap.com/saphelp_SCM700_ehp02_hana/helpdata/en/36/3d6d626ae92097e10000009b38f984/content.htmhttp://help.sap.com/saphelp_SCM700_ehp02_hana/helpdata/en/f0/b188e0848da64aa627f7b983b50611/content.htmhttp://help.sap.com/saphelp_SCM700_ehp02_hana/helpdata/en/5a/0c04aae64dae458a8170e183088342/content.htmhttp://help.sap.com/saphelp_SCM700_ehp02_hana/helpdata/en/76/2f7b37e12a7a09e10000009b38f889/content.htmhttp://help.sap.com/saphelp_SCM700_ehp02_hana/helpdata/en/6b/0bd64098de8431e10000000a1550b0/content.htmhttp://help.sap.com/saphelp_SCM700_ehp02_hana/helpdata/en/6b/0bd64098de8431e10000000a1550b0/content.htm


21/32

Application:

o Demand Planning (DP)

o Supply Network Planning (SNP)

o Capable-to-Match Planning (CTM)

o Production Planning and Detailed Scheduling (PP/DS)

In SAP APO, the production data structure is used as a source of supply.

Constraints

Engineering Change Management (ECM) is not supported for operations, activities, modes and capacity

requirements.

Only data that is valid at the provided routing explosion date is considered for the PDS.

Only bucket or mixed resources are supported (or else an error is generated during transfer).

No product variants supported; configuration is ignored.

Fixed duration (multiple of days) is required.

Breaks between activities are ignored.

Only linear chains of activities are modeled.

Relations in recipes are checked and error is generated if not linear.

Only the standard sequence of the routing is considered.

Time-dependent process parameters (TDPP) only use BAdI SNP-PPM Generation: It is not possible to generate

SNP-PPMs from a PP/DS-PDS. Instead, the generation of the SNP-PDS from SAP ERP should be used.

In Supply Network Planning, you can use the production data structure as an alternative to the production process

model (PPM) Similar to the PPM, the PDS is a combination of the work plan and the bill of materials. Compared to

the PPM, the PDS offers more flexible ways of combining and reusing data from individual work plans and bills of

materials.

The SNP PDS is supported by all SNP planning processes, except for demand and stock propagation. There is afurther restriction for the Delete Transaction Datafunction. With this function, you cannot select or delete according

to specific PDSs.

The following options are available for creating an SNP production data structure:

Generation of an SNP Production Data Structure from iPPE Data

You can either create the iPPE data in a connected DIMP system, and then transfer it to an SAP SCM system

using the APO Core Interface (CIF), or you can create the data directly in the SAP SCM system. Note that, for

SNP, you must use an SNP work plan in the iPPE data. You then create a product version for the iPPE data, and

generate an SNP production data structure from there.

You determine the validity of a product and a location in the production version, as in a PPM or an SAP ERP

production version. You can also define costs and enter co-products. If necessary, you can also specify a PP/DS

production version in the production version, which is considered by PP/DS when converting SNP orders into

PP/DS orders.

Generation of an SNP Production Data Structure from SAP ERP Data

You can generate the SNP PDS directly from work plan, bill of materials, and production version data in SAP

ERP. To do this, you must select SNP or SNP Subcontracting as the PDS type in the CIF integration model. The

relevant SAP ERP data is then transferred to the SAP SCM system automatically, and an SNP PDS is then

generated from it in the SAP SCM system.


22/32

If you select SNP Subcontracting, the master data (also for components) is automatically created at the

subcontractor location. The transportation lane between plant and subcontractor is also generated automatically

(this is not possible when using SNP PPM).

You can also influence the generation of a SNP PDS from SAP ERP data with the following Business Add-Ins

(BAdIs).

o /SAPAPO/CURTO_SNP: You can calculate bucket consumption of resources with the

CALC_BUCKET_CONSUMPTION method of this BAdI. This method, which executes standard

calculation of bucket consumption, is active automatically. However, you can change the calculation.

o /SAPAPO/CULLRTOSNP: If you want to carry out optimization-based SNP planning, you can use the

FILL_COST_FIELDS method of this BAdI to fill the SNP PDS cost fields.

You can use both BAdIs to change the SNP PDS data to be generated.

Once an SNP PDS has been generated, you can only display that source of supply. You can make changes in the

iPPE or SAP ERP. You must then, however, regenerate the PDS.

The SNP PDS is used in SNP like the SNP PPM. The source determination considers all existing sources of supply,

irrespective of whether it concerns an SNP PPM or an SNP PDS.

NOTE:Note that most SNP PPM procedures also apply for the SNP PDS. This is not always explicitly mentioned in SNP

documentation

You cannot generate an SNP PDS from Production Planning and Detailed Schedulingstructures (PP/DS PDS).

The SNP PDS can also be used in CTM planning.

Generating SNP PPMs from PP/DS PPMs

Use

SAP APO allows you to generate SNP production process models (PPMs) based on existing PP/DS PPMs. For

instance, this may be a good idea if you are using both Production Planning and Detailed Scheduling (PP/DS) and

Supply Network Planning and after the SNP planning want to convert SNP orders into PP/DS orders. During order

conversion, the system is then able to automatically determine the correct PP/DS PPM mode combination that is

appropriate for the SNP order. The following is a list of the generation options available:

SNP PPM generation with lot size margin:

You use this generation function to generate SNP PPMs from PP/DS PPMs for lot size margins and several

mode combinations of a PP/DS PPM. The system creates an SNP PPM per PP/DS PPM mode

combination. For more information, seeSNP PPM generation with lot size margin.

As the number of mode combinations and therefore also the number of SNP PPMs will possibly become very large

depending on the number of activities and alternative PP/DS PPM modes, you can choose specific PP/DS PPM

mode combinations for the SNP PPM before the function is run or enter specific parameters to restrict the SNP

PPMs generated. For more information, see

specifying mode combinations for SNP PPM generation.

SNP PPM generation without lot size margin:
http://help.sap.com/saphelp_SCM700_ehp02_hana/helpdata/en/df/40b7841c87d511ae770800062afb0f/content.htmhttp://help.sap.com/saphelp_SCM700_ehp02_hana/helpdata/en/f8/9ab83b5b831f3be10000000a114084/content.htmhttp://help.sap.com/saphelp_SCM700_ehp02_hana/helpdata/en/f8/9ab83b5b831f3be10000000a114084/content.htmhttp://help.sap.com/saphelp_SCM700_ehp02_hana/helpdata/en/f8/9ab83b5b831f3be10000000a114084/content.htmhttp://help.sap.com/saphelp_SCM700_ehp02_hana/helpdata/en/27/9bb83b5b831f3be10000000a114084/content.htmhttp://help.sap.com/saphelp_SCM700_ehp02_hana/helpdata/en/27/9bb83b5b831f3be10000000a114084/content.htmhttp://help.sap.com/saphelp_SCM700_ehp02_hana/helpdata/en/27/9bb83b5b831f3be10000000a114084/content.htmhttp://help.sap.com/saphelp_SCM700_ehp02_hana/helpdata/en/f8/9ab83b5b831f3be10000000a114084/content.htmhttp://help.sap.com/saphelp_SCM700_ehp02_hana/helpdata/en/df/40b7841c87d511ae770800062afb0f/content.htm


23/32

You use this generation function to generate SNP PPMs from PP/DS PPMs for one individual lot size and

exactly one PP/DS PPM mode combination. Each generation report run can generate exactly one SNP PPM

corresponding to one specific PP/DS PPM mode combination. For more information, see

SNP PPM generation without lot size margin.

For example, you can use this function when SNP PPM generation with lot size margins is not possible.

Processing Master Data Queues in Supply

Network Planning (SNP)

Master data in Supply Network Planning (SNP) is used to assign master data combinations in SAP Advanced

Planning and Optimization (SAP APO) to planning objects used in SNP planning (for example, the valid location,

product, and resource combinations). SNP master data queues and SNP master data queue management processes

keep track of the changes in APO master data and update SNP master data when requested by planning applications.

Master data queue processing events in Supply Network Planning occur at many points in the SNP planning process,

for example, when the planner enters interactive planning, loads a master data selection, or starts a planning run.

Prerequisites

You have initialized at least one planning version for at least one SNP planning area.

Note

The term SNP planning area refers to a planning area using one of the SNP standard master planning object

structures 9ASNPBASor 9ASNPSA.

To use time series you need an SNP planning area that contains time series key figures. For more information,

seePlanning Area Administration.
http://help.sap.com/saphelp_SCM700_ehp02_hana/helpdata/en/84/23cb390165ad0ce10000000a11402f/content.htmhttp://help.sap.com/saphelp_SCM700_ehp02_hana/helpdata/en/84/23cb390165ad0ce10000000a11402f/content.htmhttp://help.sap.com/saphelp_SCM700_ehp02_hana/helpdata/en/4a/a06fb5dbfb38dde10000000a42189b/frameset.htmhttp://help.sap.com/saphelp_SCM700_ehp02_hana/helpdata/en/4a/a06fb5dbfb38dde10000000a42189b/frameset.htmhttp://help.sap.com/saphelp_SCM700_ehp02_hana/helpdata/en/4a/a06fb5dbfb38dde10000000a42189b/frameset.htmhttp://help.sap.com/saphelp_SCM700_ehp02_hana/helpdata/en/4a/a06fb5dbfb38dde10000000a42189b/frameset.htmhttp://help.sap.com/saphelp_SCM700_ehp02_hana/helpdata/en/84/23cb390165ad0ce10000000a11402f/content.htm


24/32

Process

SNP Master Data Update

1. APO Master Data Change

If there is a change in the master data of SAP Advanced Planning and Optimization (SAP APO), the system

sends a change notification to SNP, where the changes are lined up in the SNP level one queue (table


25/32

/SAPAPO/TSQUEUE). The system automatically performs change notification and registration and immediately

after the master data change.

2. SNP Queue Update

The system updates SNP queue during planning area initialization, at the start of SNP interactive planning or any

other SNP planning application.

The SNP queue update deletes the entries in the level one queue and by processing them creates entries in the

level two queues (in table /SAPAPO/TSQMLO). Entries in level two queues are more detailed than entries in

level one queue, and they also describe the required changes in SNP master data.

By default the queue update is executed in a background process to speed up the startup of interactive planning.

You can change the runtime behavior of queue update in Customizing forAdvanced Planning and

Optimizationunder Supply Chain Planning Supply Network Planning (SNP) Basic Settings Maintain

Global SNP Settings Change the runtime behavior in the TS: Que. Proc. field.

You can also run the queue update process manually with the /SAPAPO/TS_LCM_QUEUE_UPDATE report

3. SNP Master Data Update

At the start of an SNP application (for example, SNP heuristic), the system updates SNP master data based on

the entries of the level two queue. SNP master data update is also performed as a part of planning areainitialization or at the start of SNP planning applications. SNP interactive planning performs the master data

update when you load a selection to the shuffler.

4. Delta Initialization of Planning Areas

The system updates the time series whenever planning area initialization is carried out. For more information,

seeDelta Initialization of Planning Areas.

The following error messages may occur during planning:

E207(/SAPAPO/TSM) No liveCache anchor found

E020(/SAPAPO/OM_TS) Time series does not exist

E219(/SAPAPO/TSM) Invalid data status

E230(/SAPAPO/TSM) No plannable characteristic combinations available

E001(/SAPAPO/SDP_MD) Planning object could not be determined

E085(/SAPAPO/SDP) Error reading data - planning book cannot be processed

In most cases, errors occur because the time series objects are not updated before planning with planning area

initialization. If you run planning area initialization and it does not solve the error, run the following consistency

checks:

Consistency check for the time series network

On the SAP Easy Access screen, choose Advanced Planning and Optimization Supply Network Planning

Environment Current Settings Time Series Administration Consistency Check of Time Series

Network (transaction /SAPAPO/TSCONS).

liveCache consistency check

On the SAP Easy Access screen, choose Advanced Planning and Optimization APO AdministrationliveCache/LCA Routines Tools liveCache Consistency Check (transaction /SAPAPO/OM17).

For more information, see SAP Help Portal at http://help.sap.com SAP Business Suite SAP Supply Chain

Management SAP SCM 7.0 Application Help SAP Supply Chain Management (SCM) SAP Advanced

Planning and Optimization (SAP APO) Demand Planning Demand Planning Process Planning Area

Administration Planning Area Editing Planning Areas and Additional Functions Consistency Checks for

Planning Areas and SAP Note577038.
http://help.sap.com/saphelp_SCM700_ehp02_hana/helpdata/en/24/07fe2a8b0249679e5d7e36d1bd2f4f/frameset.htmhttp://help.sap.com/saphelp_SCM700_ehp02_hana/helpdata/en/24/07fe2a8b0249679e5d7e36d1bd2f4f/frameset.htmhttp://help.sap.com/saphelp_SCM700_ehp02_hana/helpdata/en/24/07fe2a8b0249679e5d7e36d1bd2f4f/frameset.htmhttp://help.sap.com/http://help.sap.com/http://service.sap.com/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=577038&_NLANG=en&_NVERS=0http://service.sap.com/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=577038&_NLANG=en&_NVERS=0http://service.sap.com/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=577038&_NLANG=en&_NVERS=0http://service.sap.com/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=577038&_NLANG=en&_NVERS=0http://help.sap.com/http://help.sap.com/saphelp_SCM700_ehp02_hana/helpdata/en/24/07fe2a8b0249679e5d7e36d1bd2f4f/frameset.htm


26/32

Performance Optimization

The performance of SNP master data management processes affects the performance of all SNP planning

applications. You can optimize SNP master data management in the following ways:

Master data changes

Changing master data too frequently affects the performance of SNP master data update processes negatively.

Therefore, we recommend that you release master data changes periodically, for example, on a daily basis, and

followed by delta initialization of planning areas.

Regular planning area initialization

If you use SNP planning areas with time series key figures, initialize the planning areas regularly to keep the

liveCache time series up-to-date and to reduce the number of entries in level two master data queues. Initialize

planning areas for all previously initialized planning versions.

De-initialization of unused planning versions

If there are planning versions that you do not use anymore, you should de-initialize them to decrease the data

load on SNP master data update processes, especially the number of entries in level two master data queues.

Monitoring SNP Master Data Queue Update in the Computing Center Management System

(CCMS)

As of SCM 7.0 there are monitoring entries available in CCMS to monitor the status of SNP master data queues.

You can monitor the runtime of queue update process, the number of entries in each queue, the number of entries

belonging to a specific planning area and planning version combination, and the time spent since the last

initialization of a planning area.

To monitor SNP master data queue update, complete the steps below:

1. To call the CCMS, on the SAP Easy Access screen, choose Advanced Planning and Optimization APO

Administration Integration Monitor CCMS Monitor Sets .

2. To call the APO monitor set, choose SAP SCM Monitor Templates APO Monitor SNP Monitor in theCCMS hierarchy tree.

3. Choose SNP Monitor in the CCMS hierarchy tree.

You can navigate to individual monitors grouped by system and client by opening the corresponding nodes of

the hierarchy tree. Choose node SNP Monitor clnt. x SNP Master Data and Timeseries .

4. The monitoring entries are grouped to 3 monitoring objects:

1. SNP MD queue lev. 1

Contains the number of entries in the level one queue and the runtime of the last queue update

2. SNP MD queue lev. 2

Contains the number of entries in each level two queue

3. SNP Time Series

Contains the number of corresponding entries in the level two queues for each initialized SNP planning area

and planning version combination, as well as the time spent since the last initialization

5. The colors of the entries help you to recognize problems at the highest level. For more information about the

color legend, seeDisplay Types and Views of the Alert Monitor.

6. You analyze the problems and can go directly to the relevant transaction to receive more details or to rectify a

problem.

For more information about the CCMS, seeSAP APO Monitoring with CCMS.
http://help.sap.com/saphelp_SCM700_ehp02_hana/helpdata/en/5c/0e4c3b730c8d62e10000000a11402f/frameset.htmhttp://help.sap.com/saphelp_SCM700_ehp02_hana/helpdata/en/5c/0e4c3b730c8d62e10000000a11402f/frameset.htmhttp://help.sap.com/saphelp_SCM700_ehp02_hana/helpdata/en/5c/0e4c3b730c8d62e10000000a11402f/frameset.htmhttp://help.sap.com/saphelp_SCM700_ehp02_hana/helpdata/en/48/218c77932e33efe10000000a42189d/frameset.htmhttp://help.sap.com/saphelp_SCM700_ehp02_hana/helpdata/en/48/218c77932e33efe10000000a42189d/frameset.htmhttp://help.sap.com/saphelp_SCM700_ehp02_hana/helpdata/en/48/218c77932e33efe10000000a42189d/frameset.htmhttp://help.sap.com/saphelp_SCM700_ehp02_hana/helpdata/en/48/218c77932e33efe10000000a42189d/frameset.htmhttp://help.sap.com/saphelp_SCM700_ehp02_hana/helpdata/en/5c/0e4c3b730c8d62e10000000a11402f/frameset.htm


27/32

Purpose

In this process, you create a model name and assign the model to a planning version so that you can you can model

the supply chain in the Supply Chain Engineer in the next step. You must define the model name before you can set

up the supply chain model.

Creating multiple versions of the model allows you to perform simulative planning and what-if scenarios without

corrupting the supply chain model.

Only the active version receives data from R/3 via CIF.

Process Flow

Create a model name and give it a description.

Assign the model to at least one planning version

Planning version name and description

SNP: Change planning active (set flag to active) PP/DS: Change planning active (set flag to active)

If you use PP/DS, you must set the PP/DS: Change planning activeandSNP: Change planning

active indicators to enable automatic planning to be triggered or planning file entries to be created

when changes relevant to planning occur. These indicators are important when converting Supply

Network Planning orders into PP/DS orders and vice-versa. You must set these indicators for the

target planning version; otherwise you will have to plan all orders manually.

See also:

APO Master Data documentation

APO Supply Chain Engineer docume

Planning Version Merge

UseYou use this function to copy selected Supply Network Planning (SNP) key figures that you planned in an APO

planning version (copy of the active version) back into the active version. You can limit your selection to location

products and SNP planners.

Multiple SNP planners can first make copies of the active versionsmaster data and transaction data:


28/32

The SNP planners then revise these copies within their individual planning environments. Each SNP planner has his

or her own planning section (product and location):

The SNP planners then copy the revised planning versions back into the active version:


29/32

You have to ensure that the plans of the various SNP planners do not overlap since, when the individual planning

versions are copied back into the active version, the version that is copied back last overwrites the data from all the

previously copied versions.

Prerequisites You have created one or more copies of the active version (000) as planning versions.

An SNP planner has been assigned to all the location products in master data.

You have authorization for the relevant locations and products to copy the data from the planning version back

into the active version (authorization object C_APO_PLNR). The SNP planner controls authorization.

Features

You can use this function to copy four SNP key figures from a planning version back into the active version. PP/DSorder data cannot be copied. The following is a list of the SNP key figures:

Planned Production (key figure 9APPROD, key figure function 2001)

SNP Distribution Receipt (key figure 9APSHIP, key figure function 4001)

Deployment Distribution Receipt (key figure 9AFSHIP, key figure function 4005)

Safety Stock (key figure function 3003)

Selection of SNP Key Figures

You choose the SNP key figures that you want to copy back into the active version in transaction

/SAPAPO/VERMER:

Planning area: Indicates the SNP planning area that key figures are to be copied from into the active version. Key figures: Indicates the SNP key figures that are to be copied back.

Planning version (source): Name of the planning version to be copied back.

Planning version (target): Name of the active version. You cannot modify this entry.

Product: Name of one or more location products whose previously chosen key figures are to be copied back.

This entry is optional. If you do not make an entry here, the key figures of all the location products that you are

authorized to use and that belong to the underlying model are copied back.


30/32

Location: Limits you to specific locations whose location products the key figures are to be copied back from.

This entry is optional. If you do not make an entry here, the key figures of the location products you are

authorized to use are copied back from all locations belonging to the underlying model.

Planner: Limits you to specific SNP planners whose assigned location products the key figures are to be copied

back from. This entry is optional. If you do not make an entry here, the key figures of the assigned location

products you are authorized to use are copied back for all SNP planners belonging to the underlying model.

The copying of planning versions back to the active version is not a copy process in the strict sense of the word. In

fact, the SNP key figures concerned are first deleted from the active version and then recreated in it from the

planning versions.

Log File Creation

The system generates a log file for storing messages about the copy process. If you run this process online, the log

file is displayed automatically once the copying is complete.

If you run the process in the background, the log file is created but not displayed. You can then call it up using the

identification numbers from the job log.

Log file creation is activated by the system and cannot be deactivated.

Do Not Permit Errors

If this option is set, copying can only proceed if all objects can be copied without errors. If you do not set this

option, it is possible that not all of the objects will be copied.

Test Run

The system runs the entire copy process as a simulation without actually copying the data into the active version. It

runs through all stages of the copy process (authorization checks, log file creation, and so on) apart from the final

copy into the active version. To then start the actual copy process, remove the Test Run indicator.

Stop CIF Queues

If this option is set, the system stops all data transfers from R/3 systems into the SAP APO system through the Core

Interface before starting the copy process. Only inbound queues in the same system are stopped. You have to stop

outbound queues in the source system

During the copy process, stop Core Interface (CIF) using either this function, the monitor, or a

background job in order to prevent lock problems from occurring.

To stop CIF queues, you need authorization object S_ADMI_FCD.

Constraints

SNP orders are not permitted to be published directly into the SAP R/3 system. Communication with the SAP R/3

system is only permitted to take place using the Production Planning and Detailed Scheduling (PP/DS) component.

The system performs a technical check of the corresponding Customizing for this.

It is not permitted for any releases to be made into or out of SNP until all the planning versions that came from an

active version have been copied back into this active version. In particular, no order is permitted to be converted for

PP/DS and no data can be transferred into the active version from Demand Planning.


31/32

An authorization check is made during the copy process. You can only copy key figures for location products whose

SNP planner is assigned to your user.

The copy process ignores scheduling agreement schedule lines.

Activities1. Start transaction: Supply Network Planning Environment Planning Version Merge(/SAPAPO/VERMER).

2. Enter the necessary SNP key figures, planning version, and required restrictions (product, location, SNP

planner).

3. If required, set the following options:

Do Not Permit Errors

Test Run

Stop CIF Queues

Choose Execute to start the function.

4. Choose Supply Network Planning Environment Planning Version Merge: Message Log to display the log

file.

You can also call up the log file directly from transaction /SAPAPO/VERMRM.

Purpose

The supply chain model consists of individual nodes (locations) and links (transportation lanes). You can assign

several different planning versions to a model. It is also possible to create multiple models for simulation purposes.

Only the active version receives data from the R/3 system through the Core Interface (CIF).

Prerequisites

You have to set up the master data for planning in accordance with how you are using this model:

Locations

Resources

Products

PPMs

For more information, see the corresponding SNP documentation sections on setting up master data for the

individual planning methods (the heuristic, the optimizer, and so on).

Process Flow

You create a model and assign objects to it that you want in your model:

Locations

Resources


32/32

Products

PPMs

For more information, see

APO Model Maintenance.

2. Add transportation lanes to the model. For general information about creating transportation lanes, see

Transportation Lane Maintenance.The SNP-relevant fields are list

Documents

Masterdata for Snp apo