Enterprise Resource Planning Blogs by SAP
Get insights and updates about cloud ERP and RISE with SAP, SAP S/4HANA and SAP S/4HANA Cloud, and more enterprise management capabilities with SAP blog posts.
cancel
Showing results for 
Search instead for 
Did you mean: 
BethBerr
Product and Topic Expert
Product and Topic Expert
836

Introduction

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: 

  1. Use the configuration activity Copy of Movement Type (ID 103898) to Copy an Existing Movement Type. This blog post will focus on this step.
  2. Implement the BAdI Change Header and Item Data in Goods Receipts MMIM_GR4XY_PROVIDE_DATA. For more information on how to do this see the following blog post: Custom Movement Types in Inventory Management Fiori apps 

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.

Example

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:

  1. In your configuration environment, find and open the configuration activity Copy of Movement Type (ID 103898).
  2. Select the row for movement type 101.
  3. Choose "Copy as" in the top toolbar. A new screen will open.
  4. In the Movement Type field, enter a new 3-character key of your choice. It must begin with 9, X, Y, or Z. For this example, we will use Z01.
  5. Choose Apply.
  6. To add a new text description for your new movement type, choose the row for the new movement type Z01.
  7. In the Dialog Structure, double-click on Short Texts.
  8. Choose Position.
  9. In the pop up, using an example of a company using English, enter the following: Language: EN, Movement Type: Z01
  10. Choose Continue.
  11. Under Movement Type Text, enter a new description for your new movement type and press enter.
  12. Choose Save.
  13. To change the Help Texts for your new custom movement type, double-click Help Texts in the Dialog Structure.
  14. Enter your new texts into the Text column. Note: You must maintain the Help Texts for transaction code MIGO and, if available, MB11.
  15. Choose Save.

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).

 

Custom Movement Types for Fiori apps

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

  • Original Movement Type 101: Does not require a reason code entry (field is suppressed).
  • Copied Movement Type Z01: Configured to require a reason code entry.

Cases:

  1. Without Control Field Logic Changes: The reason code entry remains suppressed when posting a goods receipt with a Fiori app.
  2. With Control Field Logic Changes: Implementing changes for the copied movement type supports posting a goods receipt using Z01 in the Fiori app, including the required reason code entry.
1 Comment