LTMC - Migration Cockpit [rev]

-
The SAP S/4HANA migration cockpit uses migration objects to identify and transfer the relevant data. A migration object describes how to migrate data for a specific business object to SAP S/4HANA.We can access the SAP S/4HANA migration cockpit by using transaction LTMC.
  1. Run the transaction code LTMC
  2. Search for a migration object
  3. Read carefully the documentation for the migration object 
  4. Download a template 
  5. Change the template
  6. Upload the template
  7. Start transfer 
  8. Mapping values
  9. Simulation 
  10. Actual transfer

Transporting migration objects

We do changes in the Migration object modeler and can then export/ import the project to the Quality and Production system. The ID must be the same. Using the transaction: LTMC

Migration objects 

Customer - extend existing record by Credit Management data

What do we need to consider? 
  • This migration object is based on the assumption that business partners and customers are using the same partner ID. Otherwise, the migration object must be adjusted. The BP and customer are checked in the standard: BUPA_INBOUND_MAIN_SAVE -> PROCESS_CUSTOMER_DATA (CVI_EI_ADAPTER)
  • No updates of existing fields/records are possible. It means the process can create a segment. 
  • If the new role ( not UKM000 ) has been created, then the mapping rules must be changed.

Customer - Extend by new Org. levels 

If BP and a customer have different numbers, then put a coding to fill a business partner in the rule.

Supplier - Extend by new Org. levels 

If BP and a supplier have different numbers, then put a coding to fill a business partner in the rule.

Instruction on how to develop user-defined objects? 

Select in top navigation "PROJECT" -> "Create Migration Object" -> "User-Defined" -> "Migrate Data Directly from SAP System
This will bring you to a wizard that supports in creating your new object.

Somewhere it was a guide from SAP how to create it to align with the target design..

Structure:
  • Global data: declare variables to be used inside the project.
  • Source structure: set the levels as CDS views and relationships. It should correspond to an uploaded file structure.
  • Target structure is read from the FM
  • Structure-mapping: match the structures of the object to the structures of the Function Module 



The main thing is to configure the access type, that can be:
  • Mapping Only, Direct Mapping
  • Loop At Table, to use this you need to have a superior structure as read table or mapping only. You can use default path or user defined path.
  • Read table, you have to set a user defined path. This its only to write the condition of the clause.Then you have to configure it is default path or user define path (Only for loop at table or read table)
  • Default Path, it will use as a clause build with the key field set in the “Source Structure” Step
  • User Defined Path, it will allow you yo create a custom clause.In Loop at table / read table to create the clause (Data Path) click this button on the right
Field mapping: match the source fields to the target fields. We can user local variables here. 

How to debug the processing of a migration object? 

Step 1: Run LTMOM



Step 2: Activate all checkbox ( before conversion and before postings)
Step 3: Check simulation result 

Additional information



Comments

Post a Comment