Skip to Content
Product Information

Starter Blog for SAP S/4HANA Migration Cockpit

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.

NEW 07.10.2020  New Fiori UI for Staging now released in SAP S/4HANA OP2020

We released a new Fiori app with lots of new functionalities. Please check slides


NEW 31.7.2020  New Fiori UI starting with SAP S/4HANA Cloud CE2008

We released a new Fiori app with lots of new functionalities. Please check


NEW 16.6.2020  Meet the Expert Session- LTMOM Direct Transfer

SAP S/4HANA Migration Cockpit Product Management holds a training course on LTMOM for Direct Transfer within the SAP Enterprise Support Academy’s.

Please check you details in this blog post:


NEW 29.4.2020  Create your Test System

Check out the possibility to create a test system in fully-activated appliance:

NEW 5.2.2020 New openSAP Course

Migrating Your Business Data to SAP S/4HANA – New Implementation Scenario
With this course, you’ll get an introduction to data migration with SAP S/4HANA, and where it fits in with respect to the different transition scenarios. The course will focus on the new implementation scenario, with a deep dive into the SAP S/4HANA migration cockpit and the migration object modeler. We’ll also offer optional hands-on exercises so you can better familiarize yourself with the different migration approaches. For these exercises, you can use a system image from the SAP Cloud Appliance Library. The course starts March 25.


NEW 26.11.2019:

Newsletter SAP S/4HANA Data Migration Content Development 1911 PDF

Find all Data Migration Content Newsletters here

Find all SAP S/4HANA Migration Cockpit – Development Newsletters here

Check Data Migration Landing page on

Landing Page SAP S/4HANA
Landing Page SAP S/4HANA Cloud

Check Quick Links for available migration objects

Available migration objects SAP S/4HANA
Available migration objects SAP S/4HANA Cloud



Newsletter SAP S/4HANA Data Migration Content Development 1905 PDF


How-to Guides SAP S/4HANA Migration Cockpit

  • Creating a New Migration Object with the migration object modeler – find PDF


Development News on SAP S/4HANA Migration Cockpit

  • 1902 / 1809 FPS01 – find PDF


Newsletter SAP S/4HANA Data Migration Content Development 


SAP S/4HANA Migration Cockpit – Development News

  • 1808 – 1809 – find ppt here


SAP S/4HANA Migration Cockpit – Overview


Pre-delivered Migration Objects


SAP S/4HANA Migration Cockpit – Cloud

Imporant Notes:

  • SAP Note 2538700 – Collective SAP Note and FAQ for SAP S/4HANA Migration Cockpit (Cloud)
  • SAP Note 2400789 – SAP S/4HANA Migraition Cockpit (Cloud) – Sample data migration templates
  • SAP Note 2568909– SAP Release Note for SAP S/4HANA Cloud data migration content (lists all changes in the current + previous releases)


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
Imporant Notes:


Further Documents

Important Notes:
  • SAP Note 2481235 – SAP S/4HANA Migration Cockpit (on premise) – restrictions and extensibility of pre-delivered migration objects
  • When you created your own migraton object with the migration object modeler (XML template), you may want to run a simulation/test. This report for kind of debugging funciontality is availabe from 1709 FPS01. lease check note SAP Note 2630182
Further Blogs:
Selective Data Transition

To gain more information about this topic, feel free to visit the DMLT page, and
the SAPPI Success Story. You can get more information about data migration and main services like
Selective Data Transition, New Implementation and System Conversion which DMLT also delivers remotely.
Please feel free to contact SAP DMLT Global Customer Engagement for business inquires.

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

    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?



      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




      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

      • Hi,

        We are trying to create a automatic data transalation into Cockpit. We cannot find the step to add the data to translate the origin data automatically.

        Please, could you give us the steps?

        Thank you!

        Best regards,


  • 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?

    • 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.


      • 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.

  • 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,



      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

  • 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?



    • 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.


  • Hi Sybille,

    Thanks for the blog. We are already using MC and its capabilities are highly appreciated by the customer in one of our green field implementation.

    But, the matter of concern is the strong disclaimer from SAP about use of LSMW tool in note  2287723.

    LTMC does not support 'batch input recording'. 'batch input recording' is a powerful feature in LSMW for doing mass changes, which is really quick.
    But with the disclaimer in the note like the statement, "The use of LSMW for data load to SAP S/4HANA is not recommended and at the customer’s own risk." makes the customer wary of any use of LSMW especially in Pharma and life science industry, Since they have to comply with GMP.

    It would be great if SAP gives a clear message that of LSMW is still in option where ever LTMC/LTMOM is not an option at the moment.




    • Hi Ramesh,

      LSMW is on the simplification list as the functionality is no longer supported from SAP side and only technically available in the S/4 system.

      So there is no further tool support available for LSMW. Furthermore there are old APIs listed in LSMW which might not work any longer.

      The Migration Cockpit offers the option to use own function modules. With this option you can also wrap old APIs (e.g. IDoc).

      Best regards, sybille

      • Hi Sybille,

        I am trying with this LTMC to do a test run to upload few materials into HANA 1610 on-premise box.

        My input file has material type with internal number range. I see LTMC doesn't support internal number ranges for material types having internal number assigned. If I assign running number from internal number range in this cockpit input file, it works.

        Also I see No functionality for MASS change of material master.

        Is my understanding correct? If Yes, what is the way forward you suggest.

        Beside materials, my BP also has internal number range and I am sure that will also be a challenge.





    Thanks Sybille. really very nice blog for starters in SAP S/4 HANA Like me. Simply Awesome. Can you please share step by step document or blog for migration cockpit. how to handle or work on it.

    Keep on posting blog like this.. it would be more useful to all.



  • Hello Sybille,


    thanks to the starter blog for the migration cockpit. Ihave using LSMW a along time ago and now I have to examine the new data migration cockpit for next project.

    We are now using the SAP S/4 HANA on premise Rel. 1610 (SP 01 (02/2017) FP).

    I have tried to start and exercise the migration cockpit using the LTMC for material master cockpit.

    I started the LTMC transaction, but after uploading the XML Spreadsheet for material migration, the LTMC is not working any longer correctly.

    Every time I start the LTMC, I this screen ist shown:

    I can't do any actions(like going back and start a new project or something else.....).

    Do you have an adivse, that I can use the LTMC in "normal" mode (insert/edit projects,.....).

    Now I am stucked and i can't move on.

    Thank you very much.

    Best regards

    Frank Meyer

    • Hello Frank,

      log on to the sytem with a different user, start LTMC. This will reset some settings. Afterwards, you can proceed with your user.

      This is an issue that was taken care off with 1709 onwards - there this behaviour should not come up any more.

      best regards, sybille

  • Hallo

    I am working with on a 1709 FSP1 System with the migration cockpit object:

    "Customer - extend existing record by new org levels"

    I have upload a file to add addtional sales orgs.

    Now, even more sales orgs are needed for the same customer.

    I get the feedback from migration cockpit that the record already exists. However the records that exist for this customer are for other sales orgs.

    Is it a but, that I can only add sales org one time or a feature?



    • Hello Klaus,

      migration cockpit stores created objects to ensure uniqueness.

      That means that object CUST_EXTEND can be imported only once for every KUNNR. I will take this back to development to discuss.

      In between check table DMC_FM_RESTART and delete appropriate entries. If still problems occur please open an incident in component CA-LT-MC.

      regards, sybille



  • Hi Team,


    I am creating a project using staging table when i build a object it is creating duplicate staging tables. Can you please guide what is gong wrong there.I am working on 1809.

  • Hi,

    NEW – How-to Guide: SAP S/4HANA Migration Cockpit: Creating a New Migration Object with the migration object modeler – find PDF

    The PDF is no accessible..  Can you please check.




  • Hi Sybille

    Thanks a lot for your list !!!

    After some internal port problems I was able to migrate nearly all german banks.

    "Nearly" because (I try to explain my problem with MC and further more transaction FI01):

    1. bank key is a mandatory field (BANKL)
    2. you don't have to fill "bank number" (BANKLEITZAHL/BLZ->BNKLZ) for german banks or where BANKS = DE so BNKLZ will have the value of BANKL
    3. for BANKS = DE it is mandatory to have 8 digits (not more, not less)
    4. see e.g.
    5. So my problem is I am not able to create a key for banks that will have the same banknumber (e.g. banknumber 10020890) and a bankkey where you can see banknumber and (all its) branches in it and in transaction FI01 I am also not able to create a branch with a number I like because this number is taken for BNKLZ and this field is not editable !
    6. So - how to solve this problem to migrate branches for german banks with this rule (where banknumber is not a fake) ?? :S



  • Hi Sybille,


    For Project Systems, the migration cockpit doesn´t have any objets until version 1909, such as Project definition, WBS elements, Networks, Activities, etc. We are on version 1809 FSP2. Is there any way we can install those objects that do exist in version 1909? If not, what is the migration approach suggested for Project Systems in 1809?


    Thanks a lot!


    Best Regards,



    • Hi Gorka,

      unfortunately we can not easily "downgrade" object that come in newer releases, as API changes are possible from release to release.

      What you can do is to create your own migration object via LTMOM. Maybe it helps to check how the object is build in 1909.

      Best regards, sybille

  • Hi Sybille,


    Thanks for the detailed list of notes and documents. I have one question regarding Authorization setup - How do i set up authorization restriction by Migration object like Customer or Vendor or FI-Accounst payble open items & Migration project level? We do not want to give the whole Migration project authorization to User. Is there a way to restrict at this level? or any user can go and execute any project in LTMC ?

    We are on S/4 1809

    Appreciation your help on this.



    Bhanu G

    • Hello Bhanu,

      for SAP S/4HANA (on Premise) we believe that migration experts will do the migration - not the single key users. Therefore there is no authorization in LTMC - as migration experts check the technical results - normally this is not distinguished between the different migration object. Key user should test and check migration via their "normal" application. You an restrict the number of users who can access LTMC. For LTMOM we deliver a separate role - here you have more granularity.

      Best regards,

      Sybille Lackermeier, SAP S/4HANA Migration Cockpit Product Management

  • Hi Sybille,

    I am interested in MC a lot and got a question from a customer who is implementing S/4 HANA.

    They are going to migrate Production Order from Oracle(ERP or DB) to S/4 HANA system. But, They are wondering whether MC can migration their open Production Order because they are implementing the new feature(PEO - extended function of PP) of S/4 HANA.

    Actually, I am not sure there is difference in Production Oder. Anyway, If customer is using the new feature(PEO), can we use MC to migration Production Order?

    I know only direct transfer support the migration of Production Order in S/4 1909 above and direct transfer does not support Oracle ERP or DB.

    Thanks and Best regards,


    • Hi CY,

      yes, right: Direct Transfer is only available for SAP systems.

      As I do not know all the migration objects in details -  please check if relevant migration object is available and carefully ready the documentation. You find the list here:  .

      Hope this helps.

      Best regards,

      Sybille Lackermeier, SAP S/4HANA Migration Cockpit Product Management

  • Hello Sir/Madam,


    I have a query. SAP note 2898388 mentions that the migration object "Customer - extend existing record by new org levels" will only work when customer number is same as BP number. If the customer number is not same as BP number, then we need to modify the migration object in LTMOM.

    My question is - how and where should I add modification in LTMOM to achieve it. How shall I add modification so that I can use this migration object for scenario where customer number is not same as BP number.



    Sunilkumar Gopalkrishnan