SAP Data Migration - SAP LTMC and LTMOM / LSMW vs LTMC

[venkateshgolla]

SAP Data Migration - SAP LTMC and LTMOM

 

Hello 😊,

Today we are discussing SAP Data Migration using SAP LTMC and how to use LTMOM for extended customization here.

When We are Implementing the SAP S/4HANA solution, we can migrate our master data and business data from SAP systems or non-SAP systems to SAP S/4HANA. By using SAP S/4HANA migration cockpit.

In past, I have covered different Data Migration Approaches in the following blog post, that covered LTMC detailed steps using file-based approach Master data migration

https://blogs.sap.com/2019/09/24/sap-s4hana-data-migration-cockpit-insights-and-business-partner/

Let’s get into today’s actual topic:

LTMC is a newer version/ enhanced version of LSMW

• LSMW – Legacy System Migration workbench


• LTMC – Landscape Transformation Migration Cockpit

For the Master/Transactional data transformation, we used to use LSMW from legacy systems like ECC, any other ERP or tally, whatever data like a cost center, profit center, bank, G/L account, BP.

When we have more data, we cannot do this one by one manually (definitely not 😉 ) – so we use a tool like LSMW in past.

And now we have an enhanced version called LTMC.

LSMW Vs LTMC:

LSMW vs LTMC

Note: we do have LSMW still exist in SAP, but not recommended by SAP nowadays.

Well, Data migration using LTMC can be achieved in 2 ways.

1. File-based approach

LTMC File-Based Approach

2. Staging tables approach

Here are the pros and cons, prerequisites on high-level:

Consideration	Files	Staging Tables
Size Limit	160MB limit for SAP S/4HANA Migration Cockpit*	No Limit.
System Considerations	None.	The staging system uses an SAP HANA database.
Data Provisioning	Enter data manually in each Microsoft Excel XML file.	Fill tables manually or by using preferred tools (for example Data services, Syniti).

 

What is LTMOM

LTMOM - Migration Object Modeler

where it is useful?

Scenario: there are few customization fields that must add, the LTMC can’t help and LTMOM has come to the rescue of the situation here.

Steps:

Open the same project in LTMOM and double click on the Source Structures. This will show you the list of fields already added to the migration template. All of them may not be visible in the template.

LTMOM will allow us to create additional fields and customization fields in the source structure and, mapped to the target structure.

Here are the steps:

1. Step1: Go to LTMOM tcode, select the project and data object to add additional/customized fields.

LTMOM_TCODE

Steps 2: Select the Project

Select Project

 

Step 3:

Select the Data Object that needs customization fields:

step 4:

 

Go to the Source structure and click ADD FIELD:

Step 5:

enter the Field name, data type and length, other details as shown below:

Field details

Step 6: After adding the required field, generate the object:

Generate Object

Step 7: wait for the generation:

Generated Changes in Object

Note: Here we need the ABAPer to add the same field name in the target system Structure as well.

 

Step 8: Go to LTMC screen:

 

Step 9:

Select the Proj

Step 10:

Go to the data object in the project

Data Object - Cost Center

LTMC

Step 11: Go to Template and download

Template Download

 

Step 12:

Template Downloaded

Step 13:

Check if the added/customized fields in template:

step 14:

And then, Go to Source and target structures for mapping:

 

and, once finished - fill the template and simulate the process and load the data to the target:

LTMC File-Based Data Migration

 

In the next blog, will see how to deal with staging tables.

In the next blog posts, we can discuss more processing.

That’s all about this blog post.

Thanks for reading, please provide your feedback. ?

Happy Learning, see you in my next blog 🙂

 

Thanks,

Venkatesh Golla