User Exit in MIGO or MB1A for reason for movement

[Former Member]

Hi Experts,

Scenario:

Reason for movemnet is defined for each movement type. In our scenario, there are reason for movement which should not be used by user even if they are assigned with movement type.

Transaction:

This is required for all scrapping related movement type.

User will use tcode MB1A or MIGO.

Please suggest an exit where we can write validation during Mb1A and MIGO.

[Former Member · Accepted solution]

Hi,

Give authrization for the object mb1a or MIGO.Go to SE 80 create quthorization object and assign it to user group. Hope it works.

[Former Member · Accepted solution]

creating new authorization object is not allowed as per our project guidelines .

since its an additional requirement for our live and running SAP system.

Please suggest an exit or BADI if available.

[rafael_zaragatzky]

Hi,

I normally use the old-fashioned "include" user exit which is located at the end of the function KOMPBME_FILL. When it comes to BAdI's, then MB_MIGO_BADI or MB_MIGO_ITEM_BADI may suit you, even if I have never tried to throw user messages in them.

BR

Raf

[Former Member]

I guess a specific user exit is the best possible approach for the issue so that in the "include" a piece of code can be written with validation.

[rafael_zaragatzky]

Hi,

The user exit in KOMPBME_FILL works. The only issue with it is that it "fires" quite late, when the user tries to save the document.

BR

Raf

[Former Member]

Thanks for the info. can you please clarify further.

KOMPBME_FILL is a function module and it calls function

"userexit_kompbme_fill" which has include "RVCOMFZ2".

So, do you mean to say that I can write my set of validation in

this include ?

Are you sure system will consider this while user executes MIGO with

551 movement type?

Anybody else is having any other suggestion . Please advice.

[rafael_zaragatzky]

Hi Vineet,

Yes, I am using this user exit and it "fires" for all material movements. Such "include" user exits are very old exits that were available already in R/3 rel. 2.1 if not before. There are many such famous exits in SD, but here you have also one in MM.

This include RVCOMFZ2 is not overwritten by SAP in upgrades.

BR

Raf

[Former Member]

Any other inout to set up validation on "reason for movement " code per movement type in transaction MB1A and MIGO

[former_member329706]

Go with creating screen variant as said ealier and assign to user profile.

[former_member329706]

Hi,

Create a screen variant Using SHD0 and assign it to user profile.

[Former Member]

Hi,

Use GR_BADI_MIGO and HI_BADI_MIGO. Hope it works. Thanks.

[Former Member]

Hi,

please refer below link...

Kuber

[Former Member]

Hi ,

These links does not give me the exit name where i can write my set of validation.