Enhancements: Connections PP-SFC to APO
You can use this SAP enhancement to force a re-explosion of the BOM if a planned order is converted to a manufacturing order by an external system (SAP APO, for example). You can use a forced re-explosion of the BOM whenever the most up-to-date BOM status is needed for creating manufacturing orders in SAP R/3.
The following examples describe how you can use the forced re-explosion of BOMs. In general, the re-explosion when a conversion is made in APO can be used so that manufacturing orders are always created using the most up-to-date R/3 BOM information.
- Changes to BOMs are made on a regular basis in SAP R/3. If these changes are not quickly transferred to SAP APO and incorporated in the master data there (in the PPM, for example), planned orders may be created in SAP APO that do not correspond to the current R/3 BOMs. If
these planned orders are converted into manufacturing orders, these orders will have been created using the old BOM status. This system behavior can be prevented by forcing a re-explosion of the BOM.
- Changes are made to BOMs in SAP R/3. The updated BOMs are transferred
to the APO master data (the PPM, for example). Planned orders already exist for this APO master data. The APO planned orders are not exploded using the new BOMs and so they still correspond to the old BOM status. Only a re-explosion of the R/3 BOMs when these planned orders are
converted to manufacturing orders can ensure that the manufacturing order corresponds to the current R/3 BOM status.
Note that SAP R/3 also uses the production version (which results from the PPM explosion, for example) entered in the planned order for
determining R/3 BOMs if a forced re-explosion of the BOMs is made. The explosion date is also specified by SAP APO.
If the conversion of a planned order is triggered from SAP APO and there is a forced re-explosion of the BOM, SAP R/3 does not adopt any
item data (receipts) or component data (requirements) from the APO planned order in the R/3 manufacturing order. As a result, manual changes to components or items that were made in the planned order are lost. Components and items that were manually added in the planned
order are therefore not contained in the manufacturing order after the conversion. Components and items that were deleted in the planned order reappear in the manufacturing order after the conversion.
The following example explains what data is lost when a forced re-explosion of the BOMs is made:
You create a planned order in SAP APO and change requirement quantities of components in such a way that they deviate from the requirement quantities calculated in the BOM explosion. You select this planned order for conversion and send it to SAP R/3. In SAP R/3, a re-explosion
of the BOM is forced and a production order is created with the requirement quantities from the re-explosion. The requirement quantities changed in the APO planned order are not included in the R/3 manufacturing order. See also:
- EXIT_SAPLCOXT_001: Convert Planned Order from External System: Reexplode BOM?