Está en la página 1de 10

Data model and customizing settings to use DP BOM functionality


For all finished products PPMs with usage D (DP) or S (SNP) have been created.

Only the Output/Input factors are needed.

Data model restrictions

The DP BOM functionality influences the design of the planning objects in DP.
All characteristic values of the output product are copied to the input products when the
BOM information is added.


Normally characteristic combinations are generated using an InfoCube.

5 characteristics are defined and the values for the finished product are as follows:

Core Product Prod. Category Brand Region APO - PPM

100320 FP 1080 EU

In a second step the PPMs are selected for all products included in the characteristic
combinations and for all components the values of the output product are copied. The
existing characteristic combination is deleted and the combination with the PPM is
created. In our example the components 3746799 and 3004538 are needed to produce the
finished product 100320 as defined in the PPM P100320.

Core Product Prod. Category Brand Region APO - PPM

100320 FP 1080 EU P100320
3004538 FP 1080 EU P100320
3746799 FP 1080 EU P100320

If we want to see now all finished products (Category FP) in interactive demand planning
the finished products and the components are displayed. But only finished products
should be displayed.

All characteristics, which are used to distinguish between output and input products, have
to be modeled as navigation attributes. In our example we replace the characteristic Prod.
Category by a navigation attribute linked to the Core Product. The result is as follows:

Core Product Prod. Category Brand Region APO - PPM

100320 FP 1080 EU P100320
3004538 CO 1080 EU P100320
3746799 CO 1080 EU P100320

To keep the Characteristic Combination for Input products (in case they are the same ­
the only difference is the Product) a method in the BAdI /SAPAPO/SDP_MASTER, 
must have the right indicator :
Set Indicator to CV_INPUT_PRODUCT_DELETE to SPACE (' ') to keep the 
Characteristic Combination of the input Products.
Further details are described in note 505595 and in the Nestle example from Alexander
Grages, which is available on the SCM homepage.
Set up of planning object structure

When the planning object structure is created, the flag for DP BOM functionality is

As the InfoObject 9AMATNR is not working with navigation attributes (see note
453644), the product characteristic has to be assigned.

In this example the InfoObject P_MATNR is used as product characteristic.

As described in the previous section we use navigation attributes to model characteristics
which are needed to distinguish between output and input products.
Process to create characteristics combinations

First the characteristics combinations are generated using an InfoCube or created


In a second step the PPMs are added to the characteristic combinations.

The type of PPMs and the planning version have to be specified. If you set the flag ‘Use
only PPM space records’ only new created PPMs are selected and updated in the
characteristics combinations, which is much better for performance. This step increases
the number of characteristic combinations by the number of the components in the PPM
(important for the sizing).
This step is performance critical (e.g. 14000 combinations adding PPMs with 2
components takes 1 hour).
Set up of planning area

The DP BOM functionality uses always a pair of key figures, which are linked by the key
figure semantics (e.g. 401 and 501). For each input key figure a separate key figure to
store the dependent demand is needed. The next key figure pair uses then semantics 402
and 502.

In cases where very small input factors are used (e.g. active ingredient) an additional key
figure with semantics 601 is used to avoid rounding errors and to provide more accuracy.

When the time series are created for the planning area with DP BOM functionality the
coefficients to calculate the dependent demand on component level are transferred to


If only new characteristics combinations have been created the time series can be created
and updated using the consistency check /SAPAPO/TS_LCM_CONS_CHECK with the
repair flag.
When the components or the factors in the PPM have changed the time series are not
updated automatically. All changed planning objects have to be created again.

In a monthly planning cycle the process to update characteristic combinations and time
series is as follows.

1. Save planning data in back up cube

2. De-initialize the planning area
3. Delete all or selected characteristics combinations
4. Generate new characteristics combinations
5. Add BOM information to characteristic combinations
6. Initialize the planning area
7. Reload planning data from cubes

Save planning data

in back up cube

Initialize the De-initialize

planning area and planning area
reload data

Add BOM info to Delete existing

characteristic comb. characteristics comb.

Generate new
characteristics comb.
BOM explosion

The BOMs in demand planning are exploded when the data is loaded into the input key
figure. This can be done via a copy macro or a direct load from the InfoCube.

Month 05/2002 06/2002 07/2002 08/2002 09/2002

Forecast FP 100 PC 100 PC 200 PC 200 200

Copy demand via macro or transfer cube to planning area

Month 05/2002 06/2002 07/2002 08/2002 09/2002

Demand FP 100 PC 100 PC 200 PC 200 200

BOM explosion results in dependent demand for components

Month 05/2002 06/2002 07/2002 08/2002 09/2002

Dependent 20 MG 20 MG 40 MG 40 MG
Demand CO

Restrictions regarding LiveCache:

All units of measure (FP and components) must be convertible to the base unit
LC can only save amounts less than 6,667 X 1013

Further information:

Check OSS component APO-FCS-BOM