2611243 - T-code MD01N doesn't consider BOM changes made with change numbers

Symptom

After changing BOM components with change numbers, run MRP by t-code MD01N. However, t-code MD01N is not recognizing the changes. It is still using the old BOM components to create planned order or subcontracting purchase requisitions. It may cause missing of components or duplicated components in planned orders. Classic MRP t-codes like MD01/MD02/MD03 are working fine.

Environment

SAP ERP Production Planning (PP)
SAP ERP Logistics (LO)
SAP Enhancement package for SAP ERP, version for SAP HANA
SAP S/4HANA, on-premise

Product

SAP ERP Central Component all versions ; SAP ERP all versions ; SAP R/3 Enterprise all versions ; SAP R/3 all versions ; SAP S/4HANA 1610 ; SAP S/4HANA all versions ; SAP enhancement package for SAP ERP all versions ; SAP enhancement package for SAP ERP, version for SAP HANA all versions

Keywords

BOM explosion, MD01N, MRP live, change number, ECN, CS_BOM_VALID_TO_CALC, STKO, valid to date, VALID_TO, STPO, CL_CS_AMDP_BOM_RTO_CREATE, BOM_MRP_RTO_SINGLE_LEVEL, duplicated component, double components, missing component , KBA , LO-MD-BOM , Bills of Material , PP-MRP , Material Requirements Planning , Problem

About this page

This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).

Search for additional results

Visit SAP Support Portal's SAP Notes and KBA Search.