on 02-14-2017 4:55 AM
Hi all,
Is there any configuration to make reason code mandatory for movement type 551/552 but it should be plant specific.We have tried with OMJJ --> Control reason as mandatory (+) for these two movement type But it is affecting all the Plants to maintain the reason code for 551/552 mvt. type and effecting other EWM Plants
We are using MB1A for scrapping.we require this functionality only for one plant can't we make it plant specific ?
As you already saw from OMJJ and as you can also see from OMBS there is no option to define this per plant in customizing. And if something that is not possible via customizing then this secures the work of your ABAP developers who can try to change the standard behavior with a BADI or user exit. You should in general plan to move away from MB1A as this transaction is announced to be removed with the next release since it was already replaced back in 2001 with MIGO.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
107 | |
12 | |
11 | |
6 | |
6 | |
4 | |
4 | |
3 | |
3 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.