S&OP Master Data for Supply Chain

Planning
November 29, 2013

Table of Contents
1. Overview ............................................................................................................................................... 2
1.1 SCM Model .................................................................................................................................... 2
1.1 Navigation and Aggregation Attributes ........................................................................................ 2
2. Master Data Types ................................................................................................................................ 3
2.1 Product .......................................................................................................................................... 3
2.2 Component ................................................................................................................................... 4
2.3 Customer ....................................................................................................................................... 4
2.4 Customer Product ......................................................................................................................... 4
2.5 Location......................................................................................................................................... 5
2.6 Ship-From Location ....................................................................................................................... 5
2.7 Resource........................................................................................................................................ 6
2.8 Resource Location ......................................................................................................................... 6
2.9 Resource Location Product ........................................................................................................... 7
2.10 Customer Source of Supply (Shipment to Customer) ................................................................... 7
2.11 Location Source of Supply (Transport).......................................................................................... 8
2.12 Production Source of Supply ......................................................................................................... 9
2.13 Production Resource ................................................................................................................... 12
3. Interchangeability of Products ............................................................... Error! Bookmark not defined.
3.1 Customer Source Substitution ....................................................... Error! Bookmark not defined.
3.2 Location Source Substitution ......................................................... Error! Bookmark not defined.
4. Example Model ................................................................................................................................... 12
 1. Overview
1.1 SCM Model

For S&OP we need to model a supply chain network that can be visualized as shown in Figure . To do this
we introduce a number of different master data types as described in chapter 2.

The supply chain network in S&OP is modeled with S&OP master data types. Master data types in S&OP
are generally fully configurable and described by S&OP metadata (see the S&OP application help at
http://help.sap.com/sop20 ).
However, for the Supply Chain planning algorithms to work there has to be a specific set of master data
types defined and these objects have to possess a specific minimal set of fields. These objects and fields
are described in this document.

The document describes the existing model as of S&OP Version 2 Support Package 3. It also contains
planned additions for the ExxonMobil requirements. The latter are marked in blue. No completion time
for these new features is implied in this document.

C1 L1 L5
P1 P1 Produce Or Ship P1
Product Substitution
w quota for heuristic
w quota for heuristic

C1 L1
P2 P2

L4 L6
P4 P4

C1
P3
L4 Production
Substitution P2

L4
P5
L7
P2'

C2 L2 L6
Substitution
P2' P2' P5

L4
C2 L2 P5
P3 P3

L7 L4 Production
P1' P1

L4 L6
C3 L3
Substitution P6 P6
P1 P1'

Figure 1: Supply Chain Network Example with Customers (C1, C2, ...), Products (P1, P2, ...) and Locations (L1, L2, ...)

1.1 Navigation and Aggregation Attributes

All master data types can carry additional attributes for selection as well as for grouping and
aggregation/disaggregation of planning data.
In the following definitions we have added some example attributes to illustrate this concept. Any other
attribute is possible.
 2. Master Data Types
Figure gives an overview of the relationships between the following master data entities.
2
2
Customer
Customer Product
Product 1 Location
Location 1 1
1 1

1 1 1 1 1...n 1

*
Component
Component Ship-From
Ship-From 1
* Customer
Customer 1 Location
Location
Product
Product 1
1

* * *
Location
Location
Location
Location
* Customer
Customer * * * Source
Source
Source
Source
Source
Source Substitution
Substitution
* *

Customer
Customer*
*
Source
Source
Substitution
Substitution

* Production
Production
Source
Source (BOM)
(BOM)
1

* 1...n
Resource
Resource * Production
Production
Location
Location Source
Source Item
Item
Product
Product
*
*

1
Resource
Resource
Resource
Resource 1 *
Location
Location

Figure 2: Entity-Relationship-Diagram for S&OP Supply Chain Network

2.1 Product
Products are produced, transported and stored in the supply chain network. The S&OP product ID
corresponds to a material number in ERP and a product number in APO.

Naming Convention for the master data type: <prefix>PRODUCT, for example SM4PRODUCT.

The product master data type has the following fields (only PRDID is required and PRDSUBFAMILY,
PRDFAMILY and PRDSERIES are examples of optional attributes for aggregation, independent of the
supply chain network structure):

Field Key Not Data type Content Comments

Null
PRDID X X NVARCHAR(40) Product ID
PRDSUBFAMILY X NVARCHAR(40) Example Attribute
PRDFAMILY X NVARCHAR(40) Example Attribute
PRDSERIES NVARCHAR(40) Example Attribute
 2.2 Component
Components are products that are used as inputs in production (see Bill of Material below). One can
either define a separate master data type for components, which then comes with its own set of master
data entries, or one can reuse the entries already maintained as products by defining a so-called view
master data type. This is up to configuration.

Naming Convention for the master data type: <prefix>COMPONENT, for example SM4COMPONENT.

The component master data type has the following fields (PRDFR is required):

Field Key Not Data type Content Comments

Null
PRDFR X X NVARCHAR(40) Component ID

2.3 Output Product

Output products are products that are used as outputs in production sources. The corresponding master
data type works completely analogously to Component.
This master data type is required if key figures are used that have a base planning level with output
product and product rather than product and component. These kind of key figures are mirrors of the
“regular” key figures which depend on product and components.

2.4 Customer
Products are sold to and shipped to customers. The S&OP customer ID corresponds to customer number
in ERP and APO.

Naming Convention for the master data type: <prefix>CUSTOMER, for example SM4CUSTOMER.

The customer master data type has the following fields. Only CUSTID is required and CUSTREGION is an
example attribute:

Field Key Not Data type Content Comments

Null
CUSTID X X NVARCHAR(20) Customer ID
CUSTREGION NVARCHAR(20) Customer Region Code Example Attribute
CUSGRP NVARCHAR(20) Customer Group Example Attribute

2.5 Customer Product

While this master data type is not essential of the supply chain network, we add it here to illustrate that
one can also use aggregation attributes for combinations of simple master data types.
For example, a customer product master data type would have the following fields where only CUSTID
and PRDID would be mandatory and MARKETSEGMENT an attribute not of customer or product
individually but of the combination thereof:

Field Key Not Data type Content Comments

Null
CUSTID X X NVARCHAR(20) Customer ID
PRDID X X NVARCHAR(40) Product ID
MARKETSEGMENT NVARCHAR(10) Example Attribute

In a similar way one could also introduce a location product.

2.6 Location
A location is a logical and often also physical place where products are stored, produced, shipped to or
shipped from (via a transport). In S&OP suppliers can be modeled as locations as well. Customers are
not modeled with locations but as separate entities.
In the standard S&OP supply chain model there is no customer location. However, customer demand for
products is sourced from one or multiple internal locations.

Naming Convention for the master data type: <prefix>LOCATION, for example SM4LOCATION.

The location master data type has the following fields (only LOCID is required and LOCREGION and
LOCTYPE:
Field Key Not Data type Content Comments
Null
LOCID X X NVARCHAR(20) Location ID
LOCREGION NVARCHAR(20) Location Region Code Example Attribute
LOCTYPE NVARCHAR(10) Location Type Code Example Attribute

2.7 Ship-From Location

Ship-From Locations are locations that are used as the source location for transports between locations.
Similarly to components, ship-from locations can be modeled as separate master data types different
from locations with their own data lifecycle or as a “view” master data type on locations. In the latter
case the master data entries available are the same for locations and ship-from locations.

Naming Convention for the master data type: <prefix>LOCATIONFR, for example SM4LOCATIONFR.

The ship-from location master data type has the following fields (only LOCFR is required):
Field Key Not Data type Content Comments
Null
LOCFR X X NVARCHAR(20) Ship-From Location ID
LOCFRREGION NVARCHAR(20) Ship-From Location Example
Region Code Attribute
LOCFRTYPE NVARCHAR(10) Ship-From Location Example
 Type Code Attribute

2.8 Ship-To Location

Ship-To Locations are locations that are used as the target location for transports between locations.
This master data type is defined in the same way as Ship-From Location. Ship-To Locations are required
if key figures are to be used that depend on ship-to location and location as opposed to location and
ship-from location. These two types of key figures are mirrors of each other.

2.9 Resource
Resources describe capabilities of the network. Resources in S&OP can be thought of as capabilities to
manage the receipt of products, either through production or through incoming transportation.
The S&OP network does not model transportation resources themselves. The S&OP network also
doesn’t model resources for outgoing supply.

Naming Convention for the master data type: <prefix>RESOURCE, for example SM4RESOURCE.

The resource master data type has the following fields (only RESID is required):

Field Key Not Data type Content Comments

Null
RESID X X NVARCHAR(32) Resource ID The resource object itself is
not location dependent

Remark: Currently the heuristics only allows a single location per resource

2.10 Resource Location

This master data type describes the properties of a resource in a location. This is where the capacity
supply of the resource is modeled.

Naming Convention for the master data type: <prefix>RESOURCELOCATION, for example
SM4RESOURCELOCATION.

The resource location master data type has the following fields where RESID, LOCID and either
CAPASUPPLY or CAPASUPPLYTS are required:

Field Key Not Data type Content Comments

Null
LOCID X X NVARCHAR(20) Location ID
RESID X X NVARCHAR(32) Resource ID
CAPASUPPLY DECIMAL(18,6) Capacity Supply
CAPASUPPLYTS NVARCHAR(1) Indicator for Indicate that values come
Capacity Supply is from a key figure and not
Time Series from the master data
field CAPASUPPLY
CONSTRAINTTYPE NVARCHAR(1) Constraint Type Constraint Type: Finite =
F, Infinite = null / other
values

2.11 Resource Location Product

This master data type describes the properties of a resource with regard to a location product. This is
where the capacity consumption of the resource is modeled. Different products’ supply chain are
coupled through consumption of the same resources.

Naming Convention for the master data type: <prefix>RESOURCELOCATIONPRODUCT, for example
SM4RESOURCELOCATIONPRODUCT.

The resource location master data type has the following fields where RESID, LOCID, PRDID and either
CAPACONSUMPTION or CAPACONSUMPTIONTS are required:

Field Key Not Data type Content Comments

Null
LOCID X X NVARCHAR(20) Location ID
RESID X X NVARCHAR(32) Resource ID
PRDID X X NVARCHAR(40) Product ID
CAPACONSUMPTION DECIMAL(18,6) Capacity This is the value per
Consumption period for the base
planning level of the
receipt key figures
(production and
transport)
CONSUMPTIONTS NVARCHAR(1) Consumption is Flag to indicate that
Time Series consumption values are
managed as a key figure
and not as master data
field

Notes:
 The resource consumption modeled here is for all types of receipts for the given location
product. For example if a resource could be both sourced via a transport and via production,
capacity consumption would equally apply to both sources. It also applies to “unspecific sources
of supply”, which can be thought of as modeling procurement (see below for production
source).
 To model resource capacity consumption for production only one can use the master data type
for production source resource (see below).

2.12 Customer Source of Supply (Shipment to Customer)

This master data type describes how a product is sourced for a customer: it specifies the locations the
customer product can come from as well as corresponding quotas. This master data type also describes
the lead time for shipping to the customer.
Naming Convention for the master data type: <prefix>SOURCECUSTOMER, for example
SM4CUSTOMERSOURCE.

The customer source master data type has the following fields where CUSTID, LOCFR, and PRDID are
required:

Field Key Not Wildcard Data type Content Comments

Null Allowed
CUSTID X X X NVARCHAR(20) Customer ID Wildcard = '*'

PRDID X X X NVARCHAR(40) Product ID Wildcard = '*'

LOCID X X NVARCHAR(20) Ship-From Location
ID
CRATIO DECIMAL(!8,6) Customer Source of Quota. Value
Supply Ratio between 0 and
1. This number
has to sum up to
1 when one
groups by
CUSTID PRDID
RATIOTS NVARCHAR(1) Ratio is a Time Flag to indicate
Series that the quota is
a key figure and
not a master
data attribute
LEADTIME INTEGER Lead time: duration Expressed as
of shipment to number of
customer periods of the
base planning
level for receipt
key figures

2.13 Location Source of Supply (Transport)

This master data type describes how a product is sourced for a location via a transport from another
location (the ship-from locations). This includes the lead time and lot size information.

Naming Convention for the master data type: <prefix>SOURCELOCATION, for example
SM4SOURCELOCATION.

The location source master data type has the following fields where LOCID, PRDID and LOCFR are
required:

Field Key Not Wildcard Data type Content Comments

Null Allowed
PRDID X X X NVARCHAR(40) Product ID Wildcard = '*'
LOCID X X X NVARCHAR(20) Location ID Wildcard = '*'
LOCFR X X NVARCHAR(20) Ship-From
Location ID
TRATIO DECIMAL(18,6) Transportation Quota
Source of Supply together with
Ratio Production
RATIOTS NVARCHAR(1) Ratio is a Time Flag to
Series indicate that
the quota is a
key figure and
not a master
data attribute
LEADTIME INTEGER Lead time: Expressed as
duration of number of
transport periods
TMINLOTSIZE DECIMAL(18,6) Minimum
Transportation Lot
Size
TMAXLOTSIZE DECIMAL(18,6) Maximum This is only
Transportation Lot used in the
Size optimizer. For
heuristics an
alert can be
used.

2.14 Production Source of Supply

This master data type described how a product is made from components. Header and item of
Production Sources are linked via the source ID.
The items describe the components that go into making the product. Quantities are determined by
component coefficients relative to the produced quantity of the output product. The header table
entries describe products and co-products, where the quantities of co-product and product are related
by the output coefficients:

The main output product carries lot size information, which also applies to the co-product (via the
output coefficient relationship).

Production sources are used to produce the main output product.

Heuristics: If there is only demand for a co-product the main product’s production source is not used.
Optimizer: A production source is used equally for production of main and co-products, based on costs.

In the table of production sources one can also define sources for unspecified “production”, which is not
specified in terms of components. Interpreted differently this is simply an unspecified source of supply
(procurement, transport or production). These unspecified sources represent a boundary of the network
where no further constraints need to be taken into account. If no source of supply is found for a location
product at all, at this boundary of the network the system assumes that such an unspecified production
source exists.
 2.14.1 Production Source Header
Naming Convention for this master data type: <prefix>SOURCEPRODUCTION, for example
SM4SOURCEPRODUCTION.

The production source header master data type has the following fields, where SOURCEID, PRDID, LOCID
and SOURCETYPE are required:

Field Key Not Wildcard Data type Content Comments

Null Allowed
SOURCEID X X NVARCHAR(32) Source ID
PRDID X X NVARCHAR(40) Product ID Also for Co-
Products?
LOCID X NVARCHAR(20) Location ID Wildcard = '*'
SOURCETYPE NVARCHAR(1) Source Type; P Use also for Co-
for production, Product
U for unlimited Indicator: P is
(and main and C is
unspecified), C co-product
for co-product
OUTPUTCOEFFICIENT DECIMAL(18,6) Output Product This number
Coefficient needs be set for
products and
co-products
(unless time
series are used).
For a BOM with
a single output
and component
coefficients per
base unit of
output product
the value is 1.
OUTPUTCOEFFICIENTTS NVARCHAR(1) Flag to indicate
that output
coefficient is a
key figure and
not taken from
the master data
attribute
PRATIO DECIMAL(18,6) Production Quota for
Source of Supply production
Ratio source. Quotas
are used by the
heuristics to
choose a source
of supply.
Quotas need to
 add up to one
across all
sources of
supply including
location
source(s) and
production
source(s)
RATIOTS NVARCHAR(1) Ratio is a Time Flag to indicate
Series that the quota is
a key figure and
not a master
data attribute
PPERIODSOFCOVERAGE INTEGER Production Lot Only relevant
Size indirectly for main output
expressed as product
number of
Coverage
Periods, for
which demand is
to be produced
in one lot
PMINLOTSIZE DECIMAL(18,6) Minimum Only relevant
Production Lot for main output
Size product
PMAXLOTSIZE DECIMAL(18,6) Maximum Only for main
Production Lot output product
Size This setting is
only used in
optimization. An
alert is also
possible

2.14.2 Production Source Item

Naming Convention for this master data type: <prefix>PRODUCTIONSOURCEITM, for example
SM4PRODUCTIONSOURCEITM.

The production source item master data type has the following fields (SOURCEID, SOURCEITMID PRDID,
and COMPONENTCOEFFICIENT or COMPONENTCOEFFCIENTTS are required):

Field Key Not Data type Content Comments

Null
SOURCEID X X NVARCHAR(32) Source ID
PRDID X X NVARCHAR(40) Component Component (not
ID Product)
SOURCEITMID Optional NVARCHAR(32) Source Item
 ID
COMPONENTCOEFFICIENT DECIMAL(18,6) Component
Coefficient
COMPONENTCOEFFICIENTTS NVARCHAR(1) Component Flag to indicate
Coefficient that component
is a Time coefficient is a
Series key figure and
not taken from
master data
attribute

2.15 Production Resource

This master data type describes resource consumption for production source. This is analogous to the
resource location product capacity consumption, but here the resources

Naming Convention for this master data type: <prefix>PRODUCTIONRESOURCE, for example
SM4PRODUCTIONRESOURCE

The production resource master data type has the following fields (SOURCEID and RESID are required):
Field Key Not Data type Content Comments
Null
SOURCEID X X NVARCHAR(32) Source ID
RESID X X NVARCHAR(32) Resource ID
CAPACONSUMPTION DECIMAL(18,6) Capacity This is the value per
Consumption period for the base
planning level of the
receipt key figures
(production and
transport)
CONSUMPTIONTS NVARCHAR(1) Consumption is Flag to indicate that
Time Series consumption values
are managed as a key
figure and not as
master data field

3. Example Model
The S&OP application comes with an SAP-defined example model for Supply Chain Planning: this
consists of a planning area SAP4 and a set of master data types S4PRODUCT, S4CUSTOMER etc.
This model reuses product master data as component master data and location master data as ship-
from location master data via view master data types.

Such a model can be enhanced with financial planning master data and key figures.