Solution : https://service.sap.com/sap/support/notes/490414 (SAP Service marketplace login required)
Summary :
This SAP Note addresses an issue where during the conversion of APO planned orders to SAP R/3, an outdated BOM is used despite a newer version available in R/3. By implementing corrections via customer exit facilitated by project PPAPO004, it ensures utilization of the current BOM in R/3 during conversions without the need for reconciling components from APO. Previous solutions via modifications are cited for earlier versions, now superseded by more streamlined enhancement options. Implementation details include coding at ZXCOXU04 to force BOM explosion status updates for particular planned orders.
Key words :
production data structure generates runtime object, ensures thatwith planned order conversions, pp/ds-rto reason, production data structure, production process model, source code correction, enter source code, function exit exit_saplcoxt_001, sap project ppapo004, desired planned orders
Related Notes :
| 604002 | Modification: Explosion date with new forced explosion |
| 560380 | Enhancement in EXIT_SAPLCOXT_001 (PPAPO004) customer exit |
| 544470 | APO -> R/3: Production version not valid |
| 490422 | Reconciliation of BOM data despite forced explosion |
| 408832 | Forced BOM explosion with planned order conversion |
| 391846 | Modif: Reading master data when converting planned order |