topic Re: BADi / User exit after MIGO COMMIT ? in Application Development and Automation Discussions

BADi / User exit after MIGO COMMIT ?

Ash_ok — Wed, 25 Oct 2006 12:36:08 GMT

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.

Re: BADi / User exit after MIGO COMMIT ?

messier31 — Wed, 25 Oct 2006 12:55:21 GMT

Hi Ashok,

Following are the exits and BADI for update in MIGO transaction

EXIT : MB_CF001

BADI : 1. MB_CIN_LMBMBU04

2. MB_DOCUMENT_UPDATE

Try these..see if this helful to you..

Enjoy SAP.

Pankaj Singh.

Re: BADi / User exit after MIGO COMMIT ?

Ash_ok — Wed, 25 Oct 2006 13:11:56 GMT

Hi Pankaj,

We are currently using BADi 'MB_DOCUMENT_UPDATE' and it doesn't seem to do the job we want as we are getting the EXCEPTION 'lock_on_plant'.

Isn't BADi 'MB_CIN_LMBMBU04' for creating excise documents ? Is it a CIN version BADi by any chance ?

Any other inputs ??

Cheers,

Ashok.

Re: BADi / User exit after MIGO COMMIT ?

Ash_ok — Tue, 05 Dec 2006 09:40:23 GMT

Hi !

Setting the value for the field 'BYPASS_LOCK' to 'X', I am able to avoid the exception 'lock_on_plant'.

SAP says that it is not possible to create a batch and change it's characteristic values, other than the batch expiration date, in MIGO using BADi 'MB_DOCUMENT_UPDATE', as the create and change would be part of the same LUW.

Note 92550 lists the inconsistencies that can occur if a separate COMMIT is called in the user exit / BADi.

Cheers,

Ashok.