Solution : https://service.sap.com/sap/support/notes/720762 (SAP Service marketplace login required)
Summary :
The SAP Note discusses issues surrounding the serialization of Bill of Material (BOM) updates which causes BOM update processes to serially wait for the STVB table, locked by another process. This serialization is vital for stable material structure during the low-level code assignment. The low-level code facilitates correct sequence planning in Material Requirements Planning (MRP). Solutions include adjusting update approaches via SM50 and SM66 transaction monitoring and potentially adjusting serialization during initial BOM data transfers for performance optimization, though any such changes must be carefully managed to avoid operational disruptions.
Key words :
type report action tableupd saplcsvb sequential read stvb, low-level codethe low-level code checks, prerequisites program design - serializationthe bom update, type report action/reason, prevents low-level code assignments, bom update serialization bom data transfers, respective higher-level header materials, waiting tableupd saplcsvb wait, planning file entry table mdvm, low-level code assignment reason
Related Notes :
545676 | FAQ BOM data transfer |
544489 | FAQ Recursiveness check / low-level code assignment |
494236 | Low-level code not reduced |
186216 | Incorrect low-level codes in table MDVM |
140573 | Low-level code 999 for joint production |
84153 | Class item: low-level code of components incorrect |