Solution : https://service.sap.com/sap/support/notes/1523750 (SAP Service marketplace login required)
Summary :
SAP Note details the challenges in posting parallel goods movements for the same batch in MIGO, despite the late lock activation in OMJI, leading to error M3 682 indicating a batch lock. To address this, harmonized business processes must ensure no data modification during goods movements, except for specific batch master record transactions which still demand an exclusive lock. The solution involves implementing modifications described, underpinned by prerequisites from Notes 1397313 and 1395364, adjusted in function module VB_ENQUEUE_BATCH, and potential enhancements to the BAdI BATCH_MASTER for better batch master management in MIGO.
Key words :
parametertypetyping methodassociated typeis_bncom importing type bncomi_matnr importing type matnri_charg importing type charg_di_werks importing type werks_d c_lock_mode changing type eqegramodesave, software component sap_appl sap application, typeassociated type, system issues message m3 682, post parallel goods movements, parallel goods movement, function module vb_enqueue_batch, manual pre-implement, existing badi batch_master, classic badi batch_master
Related Notes :
| 633750 | MIGO: Message M3 682 during goods movement to same batch |
| 157423 | Message M3682 for goods movement to the same batch |