Determination of the BOM Explosion Date You use this function to state which date is to be used for exploding iPPE data/BOMs for assemblies and their components during material requirements planning in the DI system .
In this way, you can ensure that:
The correct BOM is used in the DI system for exploding a component that is produced in-house.
The correct historical status is determined for a variant.
Caution
The BOM explosion date cannot be used for assemblies/components that you wish to continue planning in the SAP APO . When planning such assemblies/components in the SAP APO, the system uses the start date from the planned order, which the SAP APO has generated for the corresponding requirements, as the explosion date for the iPPE data.
When the PVS has been exploded, you can use a period profile to group together the requirements for components that are indicated as
Always collective requirements.
This reduces the volume of data. See also:
Grouping of Component Requirements
.
If the requirements for the components and assemblies, which are to be planned in MRP in the DI system, are exploded on the lowest levels of the BOM, the BOM selected there must match the components for final assembly. You can indicate which date is to be used in the DI system for exploding the BOMs for components of an RPM product. The BOM explosion date is transferred to the DI system together with the requirements.
If you have made settings for the BOM explosion number to be used in the DI system, the BOM explosion date is used as a fixed key date in the DI system.
In the product master for the components, you have selected
Always Collective Requirements
on the
Demand
tab page.
You have defined how the system is normally to calculate the BOM explosion date in the
BOM Explosion
field in the
global settings
. If you want to make a different setting for specific components, you can do so in the
BOM Explosion
field on the
PP/DS
tab page in the product master for the components.
As the explosion date/time for the BOMs for the in-house manufactured components, the system is to use the requirement date determined by the Rapid Planning Matrix (using takt-based scheduling) for the installation of the component.
The system uses the BOM explosion date from the planned order for the RPM product as the explosion date for BOMs of components that are produced in-house.
The system uses the valid-from date that you have defined for the component variant as the explosion date/time for BOMs of components that are produced in-house.
Example
In the PVS, there are two assemblies at the component variant for the WHEEL node. Assembly 1 is valid from 1.4.2000, assembly 2 is valid from 1.7.2000. If assembly 1 was calculated by the matrix, 1.4.2000 is used as the BOM explosion date for assembly 1 and its subordinate components. This means that when the BOM for assembly 1 is exploded, the system uses the BOM that is valid on 1.4. and selects the wheel components that valid on that date.
The results of this procedure are correct only if you use the same change numbers for the subordinate BOM levels as for the superior assembly (assembly 1 in this case).
The BOM explosion date for components produced in-house is the date furthest in the future. The system compares the BOM explosion date from the planned order for the final product with the valid-from date for the component variant, determined by the matrix.
Caution
If you have marked the components produced in-house as
Always Collective Requirements
, the
start-up parameters
from the order for the RPM product cannot be considered at explosion.
If you wish start-up parameters to be considered when planning the components, you must set the as
individual customer requirements
indicator in the product masters for components produced in-house.