Skip to Content
0
Oct 25, 2006 at 12:36 PM

BADi / User exit after MIGO COMMIT ?

561 Views

Hi !

We need to populate some characteristic values for a batch of a material while running txn. code MIGO, after the MIGO COMMIT. We have used BADi 'MB_DOCUMENT_UPDATE' to write the bespoke code. However, while updating the characteristic values, using FM 'VB_CHANGE_BATCH', we are getting EXCEPTION 'lock_on_plant'.

This sounds like FM 'VB_CHANGE_BATCH' is COMMITting at the same time / before MIGO is COMMITting. Is there a BADI / user exit that works after MIGO COMMIT ?

Cheers,

Ashok.