Skip to Content
Technical Articles

SAP S/4HANA Migration Cockpit – Direct Transfer – Value mapping (1909)

1. General information about value mappings

Cross and not cross

Mappings work within a project cross-object. This means once you have edited mapping (e.g. for controlling area) for one object it is then already done and available for all other objects within this project.

Mappings do not work cross-project.

Currently (1909) there is no central mapping capabilities across different projects or across the different MC approaches (file, staging, direct transfer). Mappings can be exchanged via download/upload functionality which the approaches offer.

Where can I edit mapping?

Editing single value mapping entries is only possible in the Migration Cockpit (using the Fiori tile) in the section “Mapping tasks”.

In the SAP S/4HANA backend (logon using SAP GUI) you can enter the modelling environment – use transaction LTMOM.

In the folder of your migration objects (e.g. S4_CO_Activity_Type) you find a folder rules. Here, you can download and upload mapping for single objects or for all objects within this project.

There are different download possibilities:

  • As XML or as ZIP
  • Only the empty mapping template, documentation and signature
  • Template plus value mappings:
    • All mappings
    • Only mappings which have been created automatically. This happens when you select data from the source system. The Migration Cockpit automatically creates mapping values 1:1 for each predefined mapping task, e.g. source value: KOSTL1, target value: KOSTL1.
    • Only mapping which have been created or changed manually by a user.
  • As soon as there are mapping values available the arrow gets a green bar in LTMOM (as shown in the screenshot above).

There are different upload possibilities:

  • Replace all old mapping entries or let existing mapping values stay unchanged and upload only the new entries
  • Set the uploaded entries automatically to status “confirmed” or keep them in status “to be confirmed”

In this place you can’t see the mapping values!

If you go to the folder rules which is on the same level as Migration Objects and you click on value mappings, you see all value mappings delivered for the respective scenario (e.g. migrating from an ERP source system).

If you click e.g. on rule MAP_LSTAR you see the mapping values for Activity Type mapping.

In LTMOM you can view single entries – but it is not possible to change single values in this place. This is because of technical reasons (LTMOM locking logic, update logic).

There are discussions to integrate the whole mapping topic including download/upload functionality in the Migration Cockpit (Fiori) in the future. Mapping is a run time topic (not a design time topic). So it would better fit in the Migration Cockpit which is the run time environment.

When can I edit mapping?

Once at least one instance of a migration object is migrated it is not possible any more in LTMOM to upload mappings for this object in order to avoid severe inconsistencies/damages.

There are discussions to offer more differentiated possibilities regarding the upload in the future.

Editing single value mappings in the Migration Cockpit (in Fiori) is possible at all times.


With 1909 there is no tracking or locking concept for mappings implemented. This topic is under discussion.

2. How can I create own value mappings (1909)?

You create value mappings using transaction LTMOM (Migration Object Modeler). Open your project, position the cursor on “rules”, right mouse-click: “create value mapping”.

Assign the value mapping to the field where you want to use it.

The automatic creation of value mapping proposals (1:1) is not yet realized for custom-own value mappings (in 1909), so some additional manual steps are necessary.

Before starting the selection in the Migration Cockpit (Fiori) from the source system, the Z value mapping must be created and uploaded manually.

  • Download the “old” values from the source system for example into an excel.
  • Create the mapping 1:1 (source value : target value).
  • Upload it in LTMOM.
  • In the MC you see now the mapping task marked as „done”.

Selection and following activities can now be processed as usual in the Migration Cockpit.


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

    My company will embrace S/4 Hana in the near future from Sap R/3, and now we have S/4 Hana sanbox system, but unfortunately, I can’t use direct transfer in migration cockpit due to some kind of reason, so here I would like to check with you, for mapping rule in the method direct transfer,  is it possible to use so-called ‘field-based mapping rule”(see attached picture) like in the method “migration from file/staging table”, to write some customized code to fulfill some special requirement?


    example of field-based mapping rule

           If no, do you have any plan to implement this “field-based mapping rule” in direct transfer method?

    Thanks a lot and wish you had a nice weekend.


    Best regards!

    Zhanxiang Qi(Seven)


    • Hello Zhanxiang Qi(Seven),

      in 1909 it is not yet possible to use custom coding transformation rules in the Direct Transfer approach. Custom coding rules will be possible starting with release 2020 (release to customer: 07 October 2020).

      Best regards,


    • Hello Rahul,

      in transaction LTMOM you can see all mapping tasks with their values. You can download them all at once if you want.

      Here you see all mapping tasks for the project => download button

      Here you see the detail screen for one mapping task (MAP_KOKRS_KOSTL) with its values.

      Is this what you are looking for?

      Best regards,


  • Dear Heike,

    Currently we want to setup the direct transfer between ECC and S4, but there is always an error during the preparation step, see the error below. Because there is a function module not existed in the ECC.

    Is this because there is no template project available for ECC and S4? I copied the template project for S4 to S4?

    the direct transfer between S4 and S4 was tested successfully.


    Could you please guide me to solve this issue? thanks a lot!


    Chen Jun



  • Hello Chen Jun,

    the Direct Transfer is NOT designed to transfer data from S4 to S4. You will not get any support by SAP for this use case.

    I would assume that you did not implement the DMIS-Add-on in the ERP source system.

    Pls. check the standard MC PPT, slide 32. On this slide, technical preconditions for Direct Transfer and system preparations are listed. You also find the link to the relevant implementation guide & the central SAP note.

    I hope this information helps.

    Best regards,


    • Dear Heike,

      Thanks very much for your reply. thanks for your remind, the test for S4 to S4 is just to verify why the transfer from ECC to S4 doesn’t work.

      actually we install the DMIS-Add in the ERP source system(see the version below).

      DMIS 2011_1_731 0017 SAPK-11617INDMIS DMIS 2011_1

      and I reviewed the documentation which you provide, follow the instruction from notes 2747566 and 2836748, but it still doesn’t work. The system call  a function module from Source ERP system, but the function module belongs to S4, I tried to implement the notes  2819257 in Source ERP system, but the system remind me the package CNV_OT_APPL_PE_S4 is not not existed.

      Could you please advice how I can solve this issue? thanks a lot.

      Chen Jun


  • Hello Chen Jun,

    note 2819445 contains all corrections regarding MC basis/direct transfer.

    Pls. check if all listed notes are implemented. If the issue still persists, pls. open a ticket on CA-LT-MC.

    Best regards,


  • Hello Heike,


    this has not quite much to do with value mappings but I did not find the right spot to ask.


    Is is possible to export a project with the direct transfer approach? For example export in dev system and import to q-system or prod-system?

    Best regards,


    • Hello Andreas,

      in the 1909 release, unfortunately there is no export/import or transport function available for the direct transfer approach. This means, you really have to create the project again in Quality and Prod.

      As we get this question quite often, I guess we will soon have an official SAP note which states it.

      With the 2020 release (which will be released to customer on 7 Oct), projects and objects can be transported via the normal SAP transport concept.

      In the Migration Cockpit, you will then assign the project to a transport. In transaction LTMOM you can also then add single objects or rules. Mapping values always have to be down & uploaded (in 2020 in the Migration Cockpit or in LTMOM).

      Best regards,



  • Hello heike,

    we also urgently need the export / import function for direct transfer. We currently have 1909FSP01. Can you say when there will be an advance correction?

    Many thanks


  • Thanks for your blog Heike Jensen

    I have a question about the mapping, with LTMOM, we can upload a mapping for a maximum of 1000 entries, otherwise we need to use LTMC.

    In LTMOM, the format is similar of the mapping, but in LTMC is totally different.

    How can we find the mapping to use with the values for fields : TROBJ_GUID; GUID; DELIVER; STATE; ICON;


    Other question, this mapping will map customer from my legacy system to BP in S4, do we have to add a filler for BP number or do we have to provide value without filler ?

    Thanks for your return


  • Hello Heike Jensen

    Yes, I’m speaking the case using file/staging approach.

    The legacy system is another software, we are not doing a direct transfer between both systems.
    When I use LTMOM to upload the mapping, the file structure is as:

    When I use the LTMC, the file structure is:

    This structure from LTMC transaction is abstruse. Another point, if we have some error on the file (ie, error on mapping) there is no error message, but nothing happens.

    Another question, and it’s not clear, in this case, I translate customer account to BP, do we have to fill the value with a filler of 0 in right?

    I have a last question on mapping, in case a source value has no target, ie payment method, we can’t do mapping with a source to a target = <Null>. How can we do without adding free code ?

    Best regards,
    Philippe Gauthier


  • I’m looking for also all codifications used on LTMOM transactions. Ie on Rules, we have:

    BOL … Before output line?

    BOP …

    EOL …

    And also the codification to use to perform form or translation … where can I find it ?