Skip to Content

Besides a lot of different blogs on the topic „Your Path to SAP S/4HANA – New Implementation” I will provide here an entry point for the tool that facilitates the transfer of business data to an SAP S/4HANA system: the SAP S/4HANA migration cockpit.



Quick facts:

  • Migrates master and business data to SAP S/4HANA
  • Source systems can be SAP Systems or non-SAP Systems
  • Target system is SAP S/4HANA (for both cloud and on-premise)
  • Uses predefined migration objects (e.g. customers) to identify and transfer the relevant data
  • Predefined Microsoft Excel templates can be downloaded, filled with data, and uploaded to SAP S/4HANA
  • To import the data, SAP standard function modules and BAPIs are used
  • Natively build in in SAP S/4HANA, included in SAP S/4HANA license
  • Overview Presentation: SAP S/4HANA Migration Cockpit


SAP S/4HANA Migration Cockpit – Cloud

Demo/Click Through:

SAP S/4HANA Cloud – Configuration  – Choose “Introducing SAP S/4HANA Migration Cockpit”

Further Documents:



SAP S/4HANA Migration Cockpit – on Premise

For the on-premise version, the inherent migration object modeler allows you to integrate your custom data into the migration. For example, you can adjust the predefined standard migration objects delivered with the SAP S/4HANA migration cockpit by adding fields to them. With FPS02 you can also create your own custom-specific migration objects.

Transactions in the Backend:

  • Migration Cockpit – LTMC; required role: SAP_CA_DMC_MC_USER.
  • Migration Object Modeler – LTMOM; required role: SAP_CA_DMC_MC_DEVELOPER

Demo/Click Through:

SAP S/4HANA Data Migration – On Premise – 4 different scenarios:

  1. Introducing SAP S/4HANA Migration Cockpit
  2. Working on a migration object with the migration object modeler
  3. Adding additional fields to a migration object
  4. Creating a new migration object

Further Documents:

Further Blogs:

Imporant Notes:

To report this post you need to login first.


You must be Logged on to comment or reply to a post.

  1. George Procak


    I am trying to complete the LTMC process for a very simple scenario:  7 materials and only MARA, MARC, and MAKT entries.  I find this error on the 4th step: Execute Import

    The applied combination of translation has status AUTO .

    I see the text on the BP document:

    This message means that the uploaded file contains source data values in fields where a value mapping (translation) rule is assigned. These values are automatically added as new source data values to the translation rule and must be assigned to a correct target value in the Convert Values step.

    I deleted any blank cells from my source file and the process ran through to the finish, but no new materials were created .

    2 questions:

    Can you share an example of what that error means and how to clear it?

    Do you have any guidance on why the process can finish but no data is imported to my 1610 system?


    1. Kirstin Siebenmorgen


      Hello George,

      which feature pack are you working with? 1610 FSP01 or FPS02?

      The message normally indicates, that you need to maintain / confirm the value mapping in the next step of the guided procedure. Have you maintained/confirmed the value mapping in step “Convert Value”? Did you get any messages during the step “Simulation”? If you leave the guided proecedure with the “Finish”-Button and go back to your project overview, you can check the notification section. Can you see an error message for Activity “Execute Import” there?

      Best regards


    2. Sybille Lackermeier Post author



      1. Question:

      in the FSP´s of 1610 the the Message “The applied combination of translation has status AUTO” has already been updated to “Information required; specify mapping values in step ‘Convert Values”.

      That means: please go back to Step 3 and check your mapping.

      2. Question:

      The migration cockpit will not prevent you from proceeding if mapping for some entries is missing. Imagine you have a file with 30.000 entries, and only in 5 of them the mapping is missing. You proceed, 29.995 entries will be transferred, 5 will remain. A delta file will be generated telling you what is missing.

      In your case, a delta file should have been created indicating that your entries have not been transferred.


      If you still encounter problems you are welcome to open an SAP Incident.

      Best regards, Sybille

  2. George Procak

    Thanks Kristen and Sybille, the first question about the error is solved and my system is FSP01.

    For the data load, I see entries in the table DMC_FM_RESTART for both tests I completed.

    There are no errors in the “Execute Import” activity, only Success and Information messages.

    But my bank example and my materials were not created in the system.  Is there another area to find errors?

    1. Sybille Lackermeier Post author

      Two ideas:

      • Did you check in the migration object if a delta file was created?

      • In table DMC_FM_RESTART is SUCCESS flagged?


      If your answers are YES then please open an SAP Incident in CA-GTF-MIG.


      1. George Procak

        Thanks Sybille.

        I ran this twice with a group of 7 materials and then one bank.  All display the success X, but there is no data created for either LTMC run.  I will proceed with an SAP Incident next.

  3. Delon Ndlovu

    Hello Sybille,

    I have created a object using Migration Modeller but I need to delete the object but I can not figure out how to do it.


    Kind regards,


    1. Sybille Lackermeier Post author


      Hello Delon,

      indeed this is not possible with 1610 – there is no delete functionality for migration objects.

      Further releases will support deletion of migration objects.

      Best regards, sybille

  4. Walter Westerveld

    Working with the LTMC is sometimes easy does it (filling in templates etc. and knowing how sensitive the templates are 🙂 but sometimes I’m completely lost.

    Question about loading the BP Vendor. Is it true that if you have loaded the BP, you can not add addtional fields (Like bankdata etc..)

    I already emptied the DMC_FM_RESTART. But everytime the error message is dat BP is already created.

    Can some-one please assist me on this matter?



    1. Sybille Lackermeier Post author

      Hello Walter,

      the migration object SUPPLIER (source is classic ERP vendor) is used to create new suppliers (insert – not update on database).

      For 1709 we deliver a new migration object called SUPPLIER – EXTEND EXISTING RECORD BY NEW ORG LEVELS which is exactly used to update an already existing supplier.

      If this BAPI does not support the update of the fields you need you can delevop your own BAPI.



Leave a Reply