Solution : https://service.sap.com/sap/support/notes/186216 (Connexion à SAP Service Marketplace requise)
Résumé :
Due to incorrect low-level codes in material master data, SAP issues arise with table MDVM affecting BOM explosion in MRP planning. This is traced back to incomplete fixes by reports ZZDISK01, ZZDISK02, and ZZDIS50x, which only correct master data without updating MDVM. SAP recommends ensuring the planning file entry's low-level codes are corrected via a consistency check, using path Logistics -> Production -> MRP -> Planning -> Planning file entry -> Consistency check, which utilizes report RMMDVM10 to align MDVM's low-level codes with MARA's.
Mots Clés :
additional key words requirements planning, 'planning --> planning file entry --> consistency check', incorrect low-level codes occur, correct incorrect low-level codes, incorrect low-level codes, planning file entry, low-level codes, low-level code 999, incorrect bom explosion, consistency check calls
Notes associées :
720762 | Serialization of the BOM update/low-level code |
544489 | FAQ Recursiveness check / low-level code assignment |
370860 | CS02: Long runtime for check on class recursiveness |
167523 | Missing recursiveness check for class item |
140573 | Low-level code 999 for joint production |
84195 | Low-level code for classification and MARC |
84153 | Class item: low-level code of components incorrect |
82564 | Incorrect assignment of low-level code for class item |
68792 | Collective note for low-level code / recursiveness |
13023 | Why was a BOM not exploded? |