Solution: • Screen Layouts can be managed for Enjoy transaction MIGO for each movement type. • In case of MB1A, MB1B such t codes also respective screen layout change options are available in SAP • But Reason for Movement etc type fields which are visible at initial screens of MB1A, MB1B etc are managed below … Continue reading How can you keep Reason for Movement type as mandatory for MB1A, MB1B and MB1C Transaction codes?