Skip to Content
Technical Articles
Author's profile photo Pulla Rao Tulava

LTMC S/4HANA 2022 – Migrate Your Data

In this blog post, I am going to explain the step-by-step execution of data migration through “Migrate Your Data” app in S/4HANA 2022 version. As you are aware that Migration Cockpit (Transaction LTMC) – Deprecated from 2020 version onwards. So, to migrate your data, we need to use “Migrate Your Data” app only. The app Migrate Your Data – Migration Cockpit is the successor of the Migration Cockpit (Transaction LTMC) app. The Migration Cockpit (transaction LTMC) app is deprecated and can no longer be used to migrate data to SAP S/4HANA.

Some of our friends already posted blog posts on LTMC topic with lower versions. In this version (2022) is little different than other old versions. Preparing the Migration template with Excel file wise there is no difference but process wise have some differences.

This topic we can divide into two parts.

A. Project Creation

B. Data Migration

Part A: Project Creation:-

Typically, you first create a project in a test system which is a copy of the SAP S/4HANA production system. The more the data in the test system resembles the data in the production system, the more precise your test will be.

For each test transfer, you create a new migration project in the test system that includes any corrections or refinements identified in the previous test. When you are finally ready to transfer your data to the SAP S/4HANA production system, you create a project in the production system.

To transfer data using the SAP S/4HANA migration cockpit, a user with the role SAP_CA_DMC_MC_USER is required in the SAP S/4HANA system. This user must also have the role SAP_BR_CONFIG_EXPERT_DATA_MIG for the front-end server.

To create a Project, use “Migrate Your Data” app. With this app, you can migrate business data to SAP S/4HANA. You can migrate data directly from certain SAP source systems, or you can use staging tables to migrate data.

Choose Create and then Migrate Data Using Staging Tables. The system displays the New Migration Project screen.

Under Development Package, you specify a development package for your project. If you are unsure about which option to use, please contact your system administrator.

If you use a local development package ($TMP), it is not possible to transport the project to another system in your system landscape using the Change and Transport System (CTS).

Under Migration Objects, the system displays a list of available migration objects. Select the migration objects that are relevant for your project.

Review your settings and choose Create Project to create your project.

Here you can see your Migration Projects list, and also you can edit, copy, delete and finish the existing projects.


Part B: Data Migration:-

When you open a migration project, the system displays the Migration Project screen. On the Migration Project screen, you trigger the steps that are required to transfer the data for each migration object to the target SAP S/4HANA system.

For your Migration Object, download the relevant template. Here you have two options. 1. Download with XML file, 2. Download with CVS file.

Using XML template files is the default option for filling the staging tables with data. The XML template file contains detailed information about the relevant data structures as well as instructions about how to enter data in the file.

For each migration object, these steps are:

  • Uploading a template file for a migration object (if using template files to fill the staging tables with data).
  • Preparing the staging tables.
  • Processing any open mapping tasks.
  • Simulating the migration to the target SAP S/4HANA system (optional).
  • Migrating the data for the migration object to the target SAP S/4HANA system.


Source: SAP help portal

Once you have filled the XML template file for a migration object with data, you can upload the file to the SAP S/4HANA migration cockpit. The system then validates the data in the file and transfers the data to the staging tables that were generated for that migration object.

If there are any issues with the data in the file, you can view the relevant messages. To resolve any validation issues, you must delete the file and adjust the data in your file accordingly. You can then upload the file and the system will start the validation process again.

Once the file has been validated successfully, the system automatically starts transferring the data in the file to the staging tables that were generated for that migration object. Once all the data in the file has been transferred to the staging tables, the system displays the information Data Successfully Transferred to Staging Tables.

The system will prepare the staging tables so that they can be used to transfer data to SAP S/4HANA. This process must be repeated whenever new data is added to the staging tables.

You can monitor the status of the migration for a migration object. On the Migration Project screen, choose the button Monitoring.

Now, you need to process any open mapping tasks for the migration object before you can proceed with the simulation or the migration.

On the Mapping Tasks screen, you can view the open mapping tasks (open mapping tasks have the status To be Confirmed) as well as any confirmed mapping tasks. You can also view whether any errors exist for mapping tasks. The system displays the mapping tasks in a list.

Once you have prepared the staging tables and processed all open tasks for a migration object, you can simulate the transfer of data to the target SAP S/4HANA system.

Once Simulation processed you can see the successful instances for the migration object, now you can migrate the object.

You can monitor the status of the migration for a migration object. On the Migration Project screen, choose the button Monitoring. The system displays the Monitoring screen, where you can view the active and completed activities, for example Migration Started or Migration Completed. You can view the number of migration object instances that have been processed, as well as the number of background jobs that are used for the migration.

When you click on successful instance numbers, it will take you to Migration Object Instances screen, you can view the migration results for migration object instances by switching to the Migration Results view.

Herein you can see the migrated data which we have done through Migrate Your Data App.

For more detailed information please visit SAP help portal.

I would very much appreciate your comments and suggestions.

Happy Learning, see you in my next blog 🙂


Thanks & Regards

Pulla Rao Tulava

Assigned Tags

      You must be Logged on to comment or reply to a post.
      Author's profile photo Avik Mazumder
      Avik Mazumder

      Thank you! Good read. Here is a follow up query- “Migrate Your Data” app - is it capable of handling Mass changes/ delta changes on the already loaded object(addition of new column values/remove some data prefilled wrongly by Business users etc.- example Product/Vendor/Customer files?

      Author's profile photo Madalina Moisa
      Madalina Moisa


      The migration tools should be used only for loading/migrating data, not for updating it.

      Nevertheless, if in your migration object accessed via the LTMOM t-code you find fields like ACTION which can be mapped with I (Insert), U (Update) and other such variables, you should be able to update your data with this.

      Else, you could build a custom migration object using the same LTMOM t-code with the BAPI designed for changing/updating data.


      Author's profile photo Avik Mazumder
      Avik Mazumder

      In most of the S/4 implementations we face this practical challenge to update pre loaded data files during multiple mocks and only loading works fine but it is not feasible to refresh the data client each time you need new updates on source files from business workshops. So we already adopt hybrid approach- however, without LTMC /LTMOM &Migrate Your Data” app also we could do this loading in traditional SAP since ages specially with LSMW/IDOC/BAPI etc. It would be real game changer to have SAP app to manage mass updates - basically the GAP addressed by product like Winshuttle!  (apart from standard MASS t-codes)




      Author's profile photo Rudi Vloeberg
      Rudi Vloeberg

      totally agree ,  LTMC nice tool but we need updating possibilities.

      if anyone has some working examples for updating/changing via ltmc / ltmom ...

      please share

      Author's profile photo Rudi Vloeberg
      Rudi Vloeberg


      do you have an example how we can use ltmom with a bapi .?


      Author's profile photo Madalina Moisa
      Madalina Moisa

      Please see this post for a tutorial: Custom Migration Objects using BAPI | SAP Blogs

      Author's profile photo Rudi Vloeberg
      Rudi Vloeberg

      Wow LTMC the tool where you don't need any programming experience to maintain your data....

      hmmm...  but you need a functional consultant and a technical consultant ..... ..   haha

      Author's profile photo Madalina Moisa
      Madalina Moisa

      Or a good data migration consultant, which is a hybrid of the two you mentioned. Good luck!

      Author's profile photo Avik Mazumder
      Avik Mazumder

      Pun intended -:)  It's like- 'going from my thumb to my pinky by way of my elbow'.

      Author's profile photo Sayon Biswas
      Sayon Biswas

      Thanks Pulla very much!

      Author's profile photo Satwik Joshi
      Satwik Joshi

      Much informative ! Thanks for Sharing Pulla Rao Tulava

      Author's profile photo Madalina Moisa
      Madalina Moisa

      Including the LTMC in the title knowing that it is actually deprecated is a bit confusing, IMO.

      Besides that, good read *thumbs up*!

      Author's profile photo venu gopal
      venu gopal

      Very good presentation.. Keep it up.

      Author's profile photo venu gopal
      venu gopal

      It is a very good presentation.