How to work with Standard Migration Object in Migration Object Modeler App

[Moumita2001]

Introduction:

Let’s explore the options for adapting delivered content of the SAP S/4HANA migration cockpit to meet our customer-specific circumstances.

The SAP S/4HANA migration object modeler is name of the modelling environment in the migration cockpit. Available in the on-premises version of SAP/4HANA, you can call it using Transaction LTMOM. In SAP S/4HANA Cloud Public Edition, the migration object modeler is called via the SAP Fiori tile Model Migration Objects - Migration Object Modeler.

Prerequisite:
Before proceeding with adding any field, it is necessary to verify if the specific Migration Object allows the addition of the required field. The business role SAP_BR_ADMINISTRATOR is required to use the SAP S/4HANA Migration Object Modeler.

To check which Migration Object support field additions, refer to SAP Note 2999428 - Collective Note for extensions via Model Your Migration Objects - Migration Object Modeler App in SAP S/4HANA Cloud, public edition (Migrate Data Using Staging Tables), this specific KBA outlines the objects that permit fields to be added.

Use Case:
The field "Document Number" is not present in the Migration Object “Product” template. Downloaded template is not having any field “Document Number” in the Basic Data Tab as shown below.

Image/data in this blog is from SAP internal systems, sample data, or demo systems. Any resemblance to real data is purely coincidental.

Standard Template:

Steps to follow:

1. Create a Migration Project from “Migrate Your Data” App, here as an example I have created the Migration Project “Test_Sap”.
   
2. Open the Project (Test_Sap) in the Object Modeler App and go to the Migration Object “Product” and open the Source Structure in Edit mode.
   
3. Then click on the create button.
   
4. Once clicked you will see a new row got added with the prefix “ZZ”. Create the field as per your requirement and then click on Save.
   
5. Now the field is created. We can see the field ZZ_ ZEINR in the Source Structure of the Migration Object. We need to map the newly added field to the Target Structure of the underlying API.
   
   
6. To perform the Field Mapping, double-click on the Field Mapping node.
   
7. Now as mentioned in the Prerequisite section the newly created field needs to be mapped to the underlying API Structure. Here the mapping is done with the field ZZ_ZEINR with the API field Document number (without document management system).
   
8. To map it drag and drop the Source Structure to the Target Structure. Once mapped it will turn the Document Number sign in Green. By default, the Rule MOVE is used to map the Source and Target Structure, you can change the rule as per your business requirement.
   
9. In the Object Modeler app regenerate the Migration Object using the Reset Migration Object option.
   
   
10. Now download the Template from the app Migrate Your Data app.
    
    
11. The required field will be added in the template.

To add fields in a Migration Object within the S/4 HANA Private Edition using LTMOM, refer to this specific blog.

To add custom fields using the App "Custom Fields" refer to the help portal Overview | SAP Help Portal.

This change is update-safe. The object will still receive updates.