Professional Documents
Culture Documents
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.
Prod 1
*2 *1
Prod 2a Prod 2b
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
*5 *1 *10 *5 *2 *2
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.
*5
*1
• 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)
• 1x Attribute transformation: Dependent and Independent Demand can be shown for both “Header”
Product and Components for the same column “Product”
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:
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
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”
• Key Figure for the BOM ratio (see also previous slide):
Depending on your needs you may define this key figure as “System Editable” instead
This calculation puts the value of SALESITEMPRDID to PRDID in the transformed planning level
TRANSSALESITEMLOCPRODCUSTWEEK
Key figure is defined on the “normal” planning level. No BOM specific special modelling required.
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:
2. UoM Conversion:
3. BOM Conversion Data (to be loaded as Master Data for the BOM Ratio MDT: