In my experience as MM Support Consultant, I faced many customers reporting poor performance issues in transaction MIGO when posting goods movements.
A common cause of poor performance in MIGO is due to a “COMMIT WORK” being sent in a user-exit, or BADI, or even custom modification. And, this is not recommendable under SAP-standard perspective.
For more details read note 607203 which shows an example.
So, we should look for BADIS and EXITS which are called during MIGO. The easiest way of checking would be by debugging mode.
In case, we should run the steps below:
- Navigate to MIGO
- Activate the debugging, input ‘/h’ in the command
- Carry out the goods posting
- Once the debugging session is triggered, go to the menu ‘Debugging’ > ‘Switch to classic ABAP debugger’
- Go to the menu ‘Breakpoint’ > ‘Breakpoints at’ > Statement
- Input the statement ‘COMMIT’ and confirm, then the system will stop at each ‘COMMIT WORK’, and you can click the button ‘Call stack’ to see in which program (BADI or user exit or modification) the commit is called
If you are not aware of debugging, you may work with an ABAP developer.
Usually, it points to BAdi MB_MIGO_BADI.
In case, you should deactivate BAdi MB_MIGO_BADI and retest your scenario in MIGO.
I hope this information could be useful for SCN community.
Fábio Almeida – MM Support Consultant