Customer

DP-BOM in IBP
Rainer Moritz, Product Manager, SAP SE
September, 2017
DP-BOM in IBP

• The example planning area described in this document is using generic existing IBP modeling
capabilities on top of SAP6 sample model, no special BOM algorithm etc. is needed
• DP BOM functionality is modeled to fit to the SAP6 Key figures on level
Product/Location/Customer/Technical Week
• In case your planning area is on a different level the DP-BOM modeling need to be adapted
accordingly
• Example Planning Area name SAP6BOM6A:
• “Classical” DP-BOM: product specific, time independent and single level BOM information

ATTENTION:
This documents describes an example implementation. For a concrete implementation project the
configuration need to be adapted as needed and tested.

© 2015 SAP SE or an SAP affiliate company. All rights reserved. Customer 2

SAP6BOM6A - General Assumptions and Remarks

• Only single level BOM is modeled

• In case multi level BOMs exist, the multilevel BOM need to be “exploded” (see next slide)
• BOM Ratio defined for base UoM of all involved products
• Different base UoMs are supported
• BOM relation is modeled to be product specific only, e.g. no location or customer specific BOM
• If the BOM relation is not only product specific but e.g. also location or customer specific
this can be modelled as well but this is not described in this document
• “Header” product is only relevant in demand planning. Follow up planning steps in e.g. supply
or Inventory are using the propagated demand for the “normal” product
• BOM relation and ratio is modeled time independent

© 2015 SAP SE or an SAP affiliate company. All rights reserved. Customer 3

Example of BOM explosion: usage of multi-level BOMs

Prod 1
*2 *1

Prod 2a Prod 2b

*2 *1 *2 *4 2-level BOM is exploded outside IBP,

e.g. in HCI
Prod 3a Prod 3b Prod 3c Prod 3d

Prod 1
Single-level BOM is loaded into IBP and used
for planning.
*4 *2 *2 *4 Intermediate products Prod 2a and Prod 2b
Prod 3a Prod 3b Prod 3c Prod 3d are not used in planning at all

© 2015 SAP SE or an SAP affiliate company. All rights reserved. Customer 4

SAP6BOM6A – Example Data

Sales Item 1 Sales Item 2

BaseUoM = PC BaseUoM = KG

*5 *1 *10 *5 *2 *2

PROD1_1 PROD1_2 PROD_ALL PROD2_1 PROD2_2

BaseUoM = PC BaseUoM = PC BaseUoM = PC BaseUoM = PC BaseUoM = KG

© 2015 SAP SE or an SAP affiliate company. All rights reserved. Customer 5

SAP6BOM6: Key figure modeling example

• INDEPENDENTDEMANDQTY: Key figure for planning

the independent demand of the “Header” product as “Header” INDEPENDENTDEMANDQTY
well as the direct demand of the “Normal” product Product

• DEPENDENTDEMANDQTY: Calculated Key figure x BOMRATIO

based on INDEPENDENTDEMANDQTY and BOM
ratio (indirect demand = BOM exploded Demand) “Normal”
DEPENDENTDEMANDQTY INDEPENDENTDEMANDQTY
Product
• TOTALDEMANDQTY: Calculated Key figure for
planning summing up the direct and indirect demand of
the “Normal” product. This key figure is input for the
following Supply planning steps
TOTALDEMANDQTY

• BOMRATIO: Time independent Attribute as Key figure

containing the BOM ratio information

This example focuses on the Demand Qty key figure as example. Similar key figure modeling is very likely needed
for additional key figures like Statistical Fcst Qty.

© 2015 SAP SE or an SAP affiliate company. All rights reserved. Customer 6

Example View in Excel

PROD1_1: Total Demand = Ind. + Dep. Demand

= 250 + 500 = 750

*5
*1

SALESITEM1: Propagation of “Header” Product

demand of 100 to all relevant components according
*10 to BOM Ratio

© 2015 SAP SE or an SAP affiliate company. All rights reserved. Customer 7

SAP6BOM6A: Example View in Analytics

© 2015 SAP SE or an SAP affiliate company. All rights reserved. Customer 8

SAP6BOM6A – Overview of Enhancements

• 8 additional attributes

• 2 additional MDTs:
• New Reference MDT for the Header Product (Referencing to Product MDT)
• New Compound MDT for BOM Ratios (BOMRATIO = Attribute as key figure)

• 6 additional Planning Levels

• 4 additional Key Figures

• 1x Attribute transformation: Dependent and Independent Demand can be shown for both “Header”
Product and Components for the same column “Product”

© 2015 SAP SE or an SAP affiliate company. All rights reserved. Customer 9

SAP6BOM6A: why attribute transformation?

Attribute transformation done due to usability reason: Sales item and Product ID in the same column:

Excel View WITHOUT attribute transformation: Excel View WITH attribute transformation:

© 2015 SAP SE or an SAP affiliate company. All rights reserved. Customer 10

SAP6BOM6A – 8 new Attributes

These attributes are just examples. Different and more attributes can be modelled as well
Idea is to use some (or all) attributes of the “normal” Product MDT and define new attributes with similar names used in the reference
MDT later on. In this example the pre-fix “SALESITEM” was used and only some attributes of the normal product MDT were selected.
In addition a new attribute (used as attribute as key figure) is required to represent the BOM ratio. In our example we use “BOMRATIO”
© 2015 SAP SE or an SAP affiliate company. All rights reserved. Customer 11
SAP6BOM6A – 2 new MDTs

• New Master Data Type

representing the
“Header” Products.
• Modeled as reference to
the “normal” Product
MDT in order to avoid
double maintenance of
Master Data

© 2015 SAP SE or an SAP affiliate company. All rights reserved. Customer 12

SAP6BOM6A – 2 new MDTs

This MDT is the central information how

and which DP-BOMs exists with which
BOM ratios. E.g.:
PRDID SALESITEMPRDID BOMRATIO
SALESITEM1 PROD1_1 5
SALESITEM1 PROD1_2 1
SALESITEM1 PROD_ALL 10
SALESITEM2 PROD2_1 2
SALESITEM2 PROD2_2 2
SALESITEM2 PROD_ALL 5

ATTENTION:
Due to the modeling approach the
BOMRATIOs as shown above have to be
loaded reverse: The Sales Items are in
column “PRDID” and the Products are in
column “SALESITEMPRDID”

© 2015 SAP SE or an SAP affiliate company. All rights reserved. Customer 13

SAP6BOM6A – assign the new MDTs to the planning area

Define “BOMRATIO” as attribute as key figure on

planning level SALESITEMPROD

© 2015 SAP SE or an SAP affiliate company. All rights reserved. Customer 14

SAP6BOM6A – new Planning Level SALESITEMPROD

• Stored base planning level of key figure

BOM Ratio
• Modelled time independent as the BOM
ratio is time independent as well

© 2015 SAP SE or an SAP affiliate company. All rights reserved. Customer 15

SAP6BOM6A – new Planning Level SALESITEMLOCPRODCUSTWEEKLY

• Required for the calculation of the Dependent

Demand key figure
• Same as planning level
LOCPRODCUSTWEEKLY + all attributes of
the MDT SALESITEM

© 2015 SAP SE or an SAP affiliate company. All rights reserved. Customer 16

SAP6BOM6A – new Planning Level SALESITEMLOCPRODCUSTWEEKLYNOAT

• Required for the attribute transformation

• Same as planning level
SALESITEMLOCPRODCUSTWEEKLY
but including only root attributes

© 2015 SAP SE or an SAP affiliate company. All rights reserved. Customer 17

SAP6BOM6A – new Planning Level TRANSSALESITEMLOCPRODCUSTWEEK

• Required for the attribute transformation

• Same as planning level
SALESITEMLOCPRODCUSTWEEKLYNOAT
but including only root attributes

© 2015 SAP SE or an SAP affiliate company. All rights reserved. Customer 18

SAP6BOM6A – new Planning Level LOCPRODCUSTWEEKLYNOATTR

• Required for the attribute transformation

• Same as planning level
LOCPRODCUSTWEEKLY but including
only root attributes

© 2015 SAP SE or an SAP affiliate company. All rights reserved. Customer 19

SAP6BOM6A – new Planning Level LOCPRODCUSTWEEKLY2

• 1:1 copy of already existing planning

level LOCPRODCUSTWEEKLY
• Technically required to ensure a correct
calculation of key figure Total Demand

© 2015 SAP SE or an SAP affiliate company. All rights reserved. Customer 20

SAP6BOM6A – Key Figure for the BOM Ratio

• Key Figure for the BOM ratio (see also previous slide):

Depending on your needs you may define this key figure as “System Editable” instead

© 2015 SAP SE or an SAP affiliate company. All rights reserved. Customer 21

SAP6BOM6A – Attribute Transformation

Input key figure is DEPENDENTDEMANDQTY@SALESITEMLOCPRODCUSTWEEKLYNOAT

This calculation puts the value of SALESITEMPRDID to PRDID in the transformed planning level
TRANSSALESITEMLOCPRODCUSTWEEK

© 2015 SAP SE or an SAP affiliate company. All rights reserved. Customer 22

SAP6BOM6A – Key Figure for Independent Demand

Key figure is defined on the “normal” planning level. No BOM specific special modelling required.

© 2015 SAP SE or an SAP affiliate company. All rights reserved. Customer 23

SAP6BOM6A – Key Figure for Dependent Demand

• For this key figure the special DP-BOM logic is applied.

• Calculated key figure based on the data of the Independent
Demand Key figure and the BOM-Ratio
Note: If you change the BOM ratio after sometime, this will
immediately impact the calculated Dependent Demand
Quantity for all periods – also in the past.
BOM-Ratio is applied

Attribute transformation flow:

3. Post processing: Add the non-root attributes back to the planning level. Define the input key
figures like this:

2. Attribute transformation gets applied: This calculation drops the SALESITEMPRDID

and aggregates on PDRID. Note: PRDID has now the value of SALESITEMPRDID

1. Prepare the attribute transformation: remove all non-root attributes

© 2015 SAP SE or an SAP affiliate company. All rights reserved. Customer 24

SAP6BOM6A – Key Figure for Total Demand

“Simple” calculation to sum up Dependent and Independent Demand

© 2015 SAP SE or an SAP affiliate company. All rights reserved. Customer 25

SAP6BOM6A – Planning Objects

ATTENTION:
The configured calculation of the Dependent
Demand Key figure requires that planning
objects exists for key figure Independent
Demand for the Sales Items as well as for
the “normal” products on planning level
LOCPRODCUSTWEEKLY. Otherwise the
marked calculation step will not work:

© 2015 SAP SE or an SAP affiliate company. All rights reserved. Customer 26

Appendix
Sample Data and order of loading

1. Master Data for Product, Location, Customer and UoM:

2. UoM Conversion:

3. BOM Conversion Data (to be loaded as Master Data for the BOM Ratio MDT:

4. Planning Objects (to be loaded on calendar week level):

© 2015 SAP SE or an SAP affiliate company. All rights reserved. Customer 28

Thank you

© 2015 SAP SE or an SAP affiliate company. All rights reserved.