Skip to Content
Technical Articles

Deep dive on SAP S/4HANA Migration Cockpit – Direct Transfer

HOT NEWS (23.03.2021):

We have released a new video. It demonstrates the enhanced error analysis capabilities which come with 2020 FPS1 for file/staging and direct transfer.

Different views on messages are possible:

Activity – which messages occurred?

Message – which instances are concerned? NEW WITH 2020 FPS1

Migration object instance – which messages occurred?

If you are interested in more deep dive material on the Migration Cockpit, pls. visit our landing page!



HOT NEWS (02.02.2021):

We have released a video: How to create an own mapping rule (OnPrem 2020): LINK

Enjoy 🙂

HOT NEWS (11.11.2020):

We have released a lot of material (PDF, videos, click-troughs) on our Migration Cockpit landing page: landing page

Click on News => get to the development news for Onprem 2020

Click on Training and Education => some examples:

Deep dive Direct Transfer LTMOM => get real deep insights on how to use the modelling environment

Customer/Vendor integration in Direct Transfer

… take your time to surf all the material!


The SAP S/4HANA Migration Cockpit offers different approaches. Since 1909 there is a third approach available: transfer data directly from an SAP system.

In this blog and the linked blog posts I will provide deep dive material on the Direct Transfer approach.

If you are looking for more general or overview information pls. go to the SAP S/4HANA Migration Cockpit starter blog: LINK

There is an openSAP Course available which gives insight into all three approaches – on a very detailed level! It also treats the topic how to create own migration objects. You can download and/or view a huge amount of PPTs & videos. The hands-on experience is still possible for another 2 months, afterwards you can use the so-called “Fully activated appliance” in order to practice.

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. Week 3 (of 4 in sum) treats exclusively the “Direct Transfer” approach – including an example how to create an own migration object. 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. For the Direct Transfer there is one E2E exercise where you migrate “Activity Types”. In a second exercise you adapt the selection from the source system.


Table of contents

1. General: Can a non-unicode SAP system be the source system for the Direct Transfer?

2. LTMOM: Can I create all kinds/types of transfer rules (1909)?

3. MC & LTMOM: SAP S/4HANA Migration Cockpit – Direct Transfer – Value mapping (1909) – see LINK

4. MC: Can I repeat the selection (1909)? See LINK

5. LTMOM: How can I influence the selection (1909)? See LINK

6. LTMOM: How to create an own migration object (1909)?

7. LTMOM: How to exclude a field from being migrated in (1909)?

8. LTMOM: How to add a Z-field to a Migration Object?

9. LTMOM: How can I transfer completely self-defined custom developments, for example a Z table?



1. General: Can a non-unicode SAP system be the source system for the Direct Transfer?

Yes, a non-unicode should also work as source system. The MC uses RFC to connect the two systems, the RFC should do the converting automatically.

This blog post might be of use: . Some of the mentioned notes might be of interest.

2. LTMOM: Can I create all kinds/types of transfer rules (1909)?

In 1909 you can create:

  • transfer rules of type “move” – means, you move the content of this field unchanged from the source field to the target field
  • transfer rules of type” fixed value” – examples: posting date; a migration account as offset account for initial postings in the target
  • transfer rules of type “value mapping” – map a source value 1:1 to a new value in the target system. Pls. note that the automatic creation of mapping proposal does not work in 1909, means you have some manual steps to do in addition (see next question).

In 1909 it is not possible to create own source code rules.

6. LTMOM: How to create an own migration object (1909)?

This video shows how to create an own migration object.

I use the example: new migration object “Cost Center Texts”.

Video (37 min): LINK

Slides shown in the video: LINK

7. LTMOM: How to exclude a field from being migrated in (1909)?

To exclude fields from the transfer you have to remove the field level mapping of data for the respective field that you do not want to migrate. It depends on the respective API used for this migration object if this approach works. It only works if the API supports migration without the respective fields being mapped.

Starting 27:08 you see how to maintain the “field mapping” in the Direct Transfer approach for a migration object. Link demo video create own migration object (Direct Transfer)

8. LTMOM: How to add a Z-field to a Migration Object?

If there exist z fields (SAP standard table is enhanced by a custom-own field) in the source system, the Migration Cockpit, Direct Transfer, recognizes it and these fields are automatically shown in LTMOM as source fields. In case there exist target fields which match, the Z source fields can be mapped in LTMOM in the field mapping to the target fields.

Pls. note: only primary structures (parent and child tables) of the data model can be adapted.

There may be single cases where Z fields are not covered by the API which is used in the migration object. In this case pls. open a ticket on component CA-DT-MIG.

9. LTMOM: How can I transfer completely self-defined custom developments, for example a Z table?

Create your own API and use it in your own migration object. The pre-requisites for an own API are quite the same as the BAPI definitions in the BAPI Programming Guide (Implementing the Function Module). The API must not execute ‘COMMIT WORK’ commands.


Heike Jensen

Product Management SAP S/4HANA Migration Cockpit


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


    2. LTMOM: Can I create all kinds/types of transfer rules (1909)?

    Is in the Roadmap (future FSP or 2010/2009 ) to include other type of transformation rule? E.g. If field not blank then MOVE or even better we can create our own custom rules?


    • Hi John,

      is it perhaps possible that you enroll to this openSAP course “Migrating Your Business Data to SAP S/4HANA – New Implementation Scenario”? The course is still available. The material is too much to be uploaded here.

      In week 3 the topic is “Direct Transfer“. I have 7 units there (always PPT & demo video), units 5 & 6 are about creating own objects. In the unit 6 video I demonstrate the field mapping and there you see that the Trule type "move" is automatically assigned. We know that "custom rules" is a requested topic but unfortunately, currently I cannot give you a concrete statement about future FPS/releases.

      Best regards,


  • Hi Expert,


    One of our clients is interested in exploring the above suggest option for DM project. But due to high scrutiny on the integrity of data, we have an additional requirement for have a Automated reconciliation tool to recon the data from source & target system post migration.

    Q1: Is there any dashboard/ standard reports available for Summary/Field based recon with this option?

    Q2. Is there any other approach we can use which will suffice our requirements.


    Thanks In Advance


    Shobhit Taggar

    • Hello Shobhit,

      unfortunately, there is no standard functionality available in the Migration Cockpit for comparing/reconciliating data between source and target system.

      The SAP consulting unit (see post above from Olivia Ghebrezghi) offers these kind of services.

      No, there is no standard approach available. You can of course use SAP standard reports e.g. for master data, balances, and so on to compare the data.

      Best regards,


  • Hi Heike;

    Excellent post, i have a questions, regarding point 9, is possible migrate an program “Z”  or Ricef complete from ECC 6.0 to S4 1909 with direct transfer?


    • Hello Nelson,

      thanks for you positive feedback!

      No, the Migration Cockpit does not transfer objects from the ABAP environment.

      It is meant to do a New Implementation and thus, we only offer Migration objects to transfer the necessary application data for a "new start" in S/4. This means: migration objects for master data and "necessary" transaction data" such as FI open items, FI balances and so on.

      You find the complete list of available migration objects for each approach and release on the help portal

      The modelling environment (transaction LTMOM) of the Migration Cockpit offers the possibility to change migration objects or create own migration objects. It is not possible to transfer programs or the like.

      Best regards,


  • Hallo Heike,

    Ist es möglich eine Regel komplett zu kopieren und nicht nur die Einträge einer Regel?

    Grund ist folgender: Bevor wir eine Migration durchführen wollen wir erst einige Test durchführen. Leider sieht es so aus das wir beim Direct Transfer unsere Einstellungen in Migrationsobjektmodeller nicht in ein neues Projekt kopieren können. Nur die Einträge sind über up- and download machbar. Es wäre gut wenn man ein durchgeführtes Projekt kopieren könnte. Gibt es vielleicht so eine Möglichkeit?

    • Hallo Dietmar,

      könntest Du evtl. ein Ticket aufmachen auf CA-LT-MC und mir dort Deine Mailadresse hinterlassen und um Weiterleitung bitten?

      In 1909 gibt es diese Transport- und Kopierfunktion noch nicht. Diese Funktionalität ist nicht ganz so banal wie es evtl. erscheinen mag. Es müssen diverse generierte Objekte gehandhabt werden.

      Diese Funktion sowie diverse weitere neue Funktionen wird es in Version 2020 geben. Am 07.10. ist Release to customer - am besten auf unsere Landing page gehen, man findet dann dort die kompletten DevNews für das Migration Cockpit 2020.

      Gruß, Heike

  • Hello Heike,

    For point #9 (transferring z tables), we have 100+ tables in partner namespace and that need to be copied from ECC to S4. It will be a 1to1 transfer. If we have to create FM for each table, it would be a huge development activity. Is there a simpler way to do this instead of a BAPI as the target ?

    Note that we are not upgrading ECC to S4, its a new S4 implementation but need to copy the data from the partner namespace tables.

    Regards, Parag.

  • Hello Parag,

    The SAP S/4HANA Migration Cockpit is able to migrate custom developments such as

    • additional Z-fields in standard objects or
    • completely individual custom objects

    The design of the Migration Cockpit is for “instance-based” processing. Means, each(!) line of the root table in the source structure definition is treated as “instance”.
    Therefore, the “instance-based” migration means, that each sender record becomes an “instance” in the migration cockpit and is also treated as single instance while transferring the data. This makes sense for processing of an instance as a whole entity (usually an instance consists of several source tables, which entries have a relation to each other via foreign key relations). The target API is doing plausibility checks for each instance before creating the instance on DB level. So, it is an “all or nothing” principle per instance to create/update only logically consistent instances.

    If the intention of your Z migration object is to migrate the Z table from the SAP ERP source system 1:1 to the S/4HANA target system, it is a simple table copy in the end.

    Due to the design of the migration cockpit, the tool is of course able to fulfill such a migration, but in the end, the runtime of such a transfer will never be as expected for a simple 1:1 table transfer as each line of the table is treated individually (for example having an own log).
    If you have for example 3.000.000 entries in your Z table this results in 3.000.000 single instances in the migration cockpit, which will again be processed one by one, just to fill the target table via the API (= single function call per line).

    So if you want to do a simple 1:1 table transfer without the need for any transformations, plausibility and consistency checks you should consider to develop an own RFC-enabled function module (currently used API just RFC-enabled) and a Z program which is retrieving the data from the Z table and transfers it 1:1 from sender to target. This will be the easiest and fastest solution.

    I hope this information helps.

    Best regards, Heike

  • Hi Heike,

    I attended your course on open SAP, it was a real help. Thank you!

    I was wandering if for direct transfer exists something similar with /1LT/DS_MAPPING from staging table approach? I have noticed that the system creates some staging tables also for Direct Transfer after the Select Data.

    Best regards,



    • Hello Christina,

      thanks for your positive feedback 🙂

      You can upload and download mapping entries for some or all mapping tasks in LTMOM and since release 2020 also in the Migration Cockpit (Fiori). For direct transfer, there is no other way to access the mapping. Why are you looking for /1LT/DS_MAPPING like structures? Is it because of the amount of mappings, do you want to fill it with a program or what is the reason behind?

      Best regards,

      • Thank you for your quick reply.

        We investigate the possibility to extract data  from 3 ECC systems to S4/HANA 1909 using  Direct transfer, but we need to reconcile, validate and harmonize the data. Having the mapping tables we would like to create a program/script to help us to do the reconciliation of data.

        Best regards,



        • Hello Christina,

          cleansing & harmonizing data after having selected it into the Migration Cockpit / Direct transfer is not possible. You can adjust the selection (using transaction LTMOM) and skip dedicated items from further processing (Firoi, instance list, with 2020: mass processing in instance list) after you have selected them.

          With 2020, you have a so-called skip-rule available with which you can skip items from the selection by using your own coding.

          Cleansing, golden record and so on are not possible using the Migration Cockpit/DT.

          If harmonization is needed, you have to do it in the source system.

          Mapping in our terminology means: map field values old (selected) to new values and then pass this transformed data record to the API for creation/posting into the target system. E.g. the selected cost center is 567 with responsible Müller, you map 567 to 987 and Müller to Jensen.

          Best regards,





  • Hello Heike,

    is it possible to create custom source code mappings for the direct transfer approach? In case it is not possible: is this planned for the future?


    Best regards