Solution : https://service.sap.com/sap/support/notes/1501121 (SAP Service marketplace login required)
Summary :
SAP Note addresses an issue where a batch lock causes sporadic M7 001 errors in table OMCHA when the batch level is set to material or client. It reverses previous modifications in Note 157423 and introduces the BAdI method LOCK_BATCH_MASTER in BAdI MATERIAL_READ for configuring batch lock behavior, supporting only lock types E and S. This modification arises due to issues during plant segment creation or modification, leading to potential data inconsistencies. Implementers are advised to remove prior modifications and implement this note while considering risks associated with concurrent batch modifications. Implementation of Note 1513425 is crucial for successful deployment.
Key words :
length field label short 10 lock mode medium 15 lock mode long 20 lock mode heading 55 modesave, system sporadically issues error message m7 001, is_mtcom importing mtcomcv_lock_mode changing eqegramodedescription, software component sap_appl sap application, data element kzspcuse transaction se11, newly created plant segment, error message m7 001, error message occurs, call transaction se11, implemented sap-internally
Related Notes :
| 1617829 | Batch not created during posting with PID creation |
| 1513425 | Overwriting fields in batch |
| 157423 | Message M3682 for goods movement to the same batch |