
Custom movement types in Inventory Management - SAP S/4HANA Cloud Public Edition - are variations of standard movement types that have been tailored to meet specific business requirements. These custom movement types can be identified by their initial character because they always start with 9, X, Y, or Z.
Creating a custom movement type is useful when you need more detailed specifications for a particular business process. The most straightforward method to create a custom movement type is to copy an existing standard movement type and then modify it according to your specific needs.
The implementation of custom movement types in your system is a 2-step process:
Custom movement types are currently only supported for Fiori apps Post Goods Receipt for Purchasing Document (F0843), Post Goods Receipt for Inbound Delivery (F2502) and Post Goods Receipt for Production Order (F3110), Post Goods Receipt for Process Order (F3244) and Post Subsequent Adjustment (F5476) via Cloud BAdI MMIM_GR4XY_PROVIDE_DATA.
Note: This functionality only supports the main items of subcontracting purchase orders. Movement types for sub-items in subcontracting purchase orders cannot be modified.
For example, let's say that a company needs to use movement type 101 -post goods receipt - but wants to post the goods receipt to a different account. To achieve this, they must first copy movement type 101. The following shows you how:
Note: If you create a custom movement type, we recommend creating a corresponding reversal movement type immediately. You can use the configuration activity Set Reversal Movement Types (ID 104062).
After creating your custom movement type, you must implement the BAdI MMIM_GR4XY_PROVIDE_DATA to enable the use of your new movement type in one of the supported Goods Receipt Fiori apps.
It is also possible to modify the control field logic in connection with the copied movement type (see example below). For more information about this BAdI, refer to App Extensibility: Post Goods Receipt for Purchasing Document.
All Goods Receipt Fiori apps support custom movement types using the above-mentioned BAdI, except for the Post Goods Receipt without Reference app. You can also implement the BAdI MMIM_GR4XY_CHECK_DATA to apply custom validation logic for the copied movement type before posting the material document.
The primary use case for copying a movement type is to enable customers to modify account determination when posting a goods receipt. However, it is also possible to implement different control field behavior for the copied movement type compared to the original, supported by the above-mentioned BAdI.
Example: Posting a Goods Receipt with a Reason Code
Cases:
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
9 | |
7 | |
6 | |
4 | |
4 | |
4 | |
4 | |
3 | |
3 | |
3 |