Solution : https://service.sap.com/sap/support/notes/440585 (SAP Service marketplace login required)
Summary :
When master data is re-read for a collective order, if a BOM is re-exploded, lower-level orders for directly produced components are flagged for deletion and get new replacements. This process prevents reuse of order numbers, necessitating reassignment from the available number range. The technical cause is rooted in the system's way of handling internal number assignments and deletion indicators for closely linked production components. This registration ensures correct data handling without archiving/deletion of dependent orders from the database immediately. The noted workflow doesn't constitute an error but a designed feature to maintain data integrity within the production order framework.
Key words :
additional key words process order, deleted lower-level orders, read pp master data, lower-level orders, newly exploded bom, directly produced component, orders receive completely, newly created orders, read master data, directly produced components
Related Notes :
| 1574381 | FAQ: Collective orders |
| 181417 | CO02: Errors CO168 according to further selections master da |