Overview – Features & Functions

With the new Legacy Data Migration strategy, the functional consultants without developer skills will benefit from the functionality.

This solution will be replaced by the BDC – Batch Data Communication / LSMW – Legacy System Migration Workbench / LTMC – Legacy Transfer Migration Cockpit starting with SAP S/4HANA Cloud 2008 and later.

The functional consultant can easily move their legacy/mass load data (Greenfield/support projects) with this application.

There are two ways to upload data into the SAP S/4HANA system.

  • Directly migrate data from the SAP system.
  • Utilize staging tables to migrate data.

Beneficiaries & key facilitators:

Available with licences for SAP S/4HANA and SAP S/4HANA Cloud.

  • Ready-made migration objects.
  • There is no need for developer expertise.
  • He system’s step-by-step wizard.
  • Migration objects and rules that have been preconfigured.
  • Users can fill in missing data while migrating (while uploading the data from the staging table or file, if any key data is missing, the user can enter details on the same screen without returning to reprocess the full file).
  • This functionality will make it easier to upload transactional and master data (GL, Vendor-BP, Customer-BP, Assets, House bank accounts, and Transaction data).
  • Depending on the migration scenario, predefined staging tables are by design available, as well as distinct file templates for each migration object.
  • The computerised conversion of the source and target structures.
  • Data migration programmes are automatically developed; customers do not need to provide them.

Simulated step-by-step approach, associated screenshots, and outcomes are below:

Data Migration using the Fiori App

  • AP BR CONFIG EXPERT DATA MIG is the business role.

Procedural Flow:

1. Choose the migration object: Each object’s staging table is automatically created by the system.

2. Utilize the given Templates files or your favourite tools to transfer data to staging tables.

3. Setup Staging Tables: Setup the staging tables to allow for data transfer.

4. Check the source data’s mapping to make sure it is accurate.

5. Repeat the Migration: In order to check for errors, call the function module in test mode.

6. Migrate data: Check the pertinent reports and tables and update data in SAP.

Access the Fiori app and move your data there.

  • Choose the Create button.
  • Select Use Staging Tables to Migrate Data.

  • Name: GL Account (freely defined text)
  • Click Step 2 to continue the procedure.

  • Select “FI-G/L account,” the appropriate Migration item.
  • Click the button to choose the migration objects.
  • To move on to the following step, select “Review.”

  • Select “Create Project” to confirm your data choices.

  • Choose the “>” button.

Note: More details can be found by selecting “Monitoring / Mapping Task / Job Management / Finish Project” from the list of options.

The staging tables for the chosen migration objects are here created automatically by the system.

  • FI – G/L account migration object should be chosen.

Select previous screen or the Back Arrow.

You start all the procedures necessary to transfer the data for each migration object to the destination SAP S/4HANA system on the migration project screen. You may easily get more information and duties as well.

  • For the migration objects, select the “Download template button” option.


  • All provided migration objects come with XML template files, which you can download to a local folder and use to maintain data in the template fields.
  • If any of the template’s fields are irrelevant to your company’s operations, leave them empty rather than deleting or hiding them.

For further information on how to fill up the template, refer to the Introduction worksheet.


  • Before beginning to fill out the template, read the introduction and double-check the field list.
  • Only use the following choices when copying and pasting values: –
  • Paste option followed by Values (V) in an XML file
  • Then, select Text – from somewhere else – after choosing Paste Special.
  • With the paste option, keep the text in the editor or notepad only.

Place the migration file online:

Choose “Upload file” from the menu that appears below the screen.

  • Choose “Upload” from the menu.

  • Choose a file from the desktop directory

When a file is uploaded, the initial status is changed to “Validation planned” and then, as shown in the second screen below, to “Data successfully moved to staging tables.”

  • Scheduled validation, current

  • Status: Information has been successfully moved to staging tables.

To view the details of the messages, select “display messages” from the screen above (error, Warning, Success, Information).

  • To access the screen below, select the Back Arrow 2 times.

  • Once the data has been successfully uploaded to the staging tables, choose “Prepare” from the drop-down menu.

  • When the “prepare” option is chosen, the procedure will begin for the subsequent action.


  • As preparation gets underway, it will automatically update as it is finished.
  • The GL staging tables, tables “5”, are updated from the upload file.
  • The number of records from the upload file is instances “19.”
  • Open “11” how many business codes, controlling regions, forms of reconciliation, FSG, etc. there are in a given set of GL accounts.

The target values can be modified while the data is being uploaded (After executing the preparation step).

  • To access the screen below, select the Back arrow twice.
  • Choose Mapping Tasks from the drop-down list (the system will suggest “Mapping Task” automatically).

  • For each item, check the Mapping Task box.
  • Clicking the confirm button

  • When you click OK, the status will change to From confirmation to confirmation

The mapping tasks’ status was changed to confirmed after confirmation.

  • Updated mapping task status: “11” Done
  • When the mapping values are confirmed, the status is immediately changed to “simulation.”
  • Choose “simulation” from the drop-down menu.

  • Simulation began.

  • Completed simulation
  • Successful simulation status “19” has been updated.
  • The screen’s next action, Migration, was automatically modified.


  • Choose “Migrate” from the drop-down menu.

  • Press the OK button

  • The migration process has started.

  • Status of the migration process: finished.
  • “19” Successful migration


  • The new process method makes it simple to use and allows us to upload all master records and transactional data without the need for special programming.
  • The only activity that I can see as being time-consuming is maintaining the data by uploading a file with multiple tabs, however this software will enable us to upload legacy data and other large amounts of data for business operations without the need for technical assistance into the SAP S/4HANA system.
  • This package/solution is by default available starting with SAP S/4HANA 2020 coupled with LTMC, and starting with 2021, we only have one solution, “Migration your data – Migration cockpit(old),” and LTMC is no longer available.
  • This new app does not provide access to projects made using transaction LTMC (for SAP S/4HANA) or the app “Migrate your Data – Migration Cockpit (Old)” (for SAP S/4HANA Cloud).
  • If the company is still utilising SAP-GUI, we can still upload data via LSMW or BDC.




The OSS Notes

Information about the various versions of 2988692 – SAP S/4HANA Migration Cockpit

FAQ for the SAP S/4HANA migration cockpit is 2733253. Migration strategy: Data migration and transfer from staging tables