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.

Tracking/locking

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.

 

53 Comments
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%20of%20field-based%20mapping%20rule

    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)

     

    /
    example%20of%20field-based%20mapping%20rule
    • 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,

      Heike

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

      Heike

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

    Heike

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

    Heike

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

    Andreas

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

      Heike

       

  • 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

    Robert

  • 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

    Philippe

    • Hello Philippe,

      as you mention transaction LTMC, I would guess you do not talk about Direct Transfer but about the file/staging approach, right?

      If this is the case, this is the wrong blog 🙂

      However, pls. submit your question to: sap_s4hana_migration_cockpit@sap.com

      Best regards,

      Heike

  • 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:
    IV_BUKRSIV_KUNNREV_KUNNR

    When I use the LTMC, the file structure is:
    OBJECT=Z_MAP_KUNNR;;;;;;;;;;
    TROBJ_GUID;GUID;DELIVER;STATE;ICON;DEF_VALUE;IV_READONLY;VALUE_I1;VALUE_I2;VALUE_O;
    00mfcZVJ7jk0naZy{exFKm;00mfcZVJ7jk1}74sLgxm4m;;1;@17@;;X;2000;5471302;1003;
    00mfcZVJ7jk0naZy{exFKm;00mfcZVJ7jk1}75Kt9nG4m;;1;@17@;;X;2000;9431003;1005;

    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 ?

  • Hi  Heike Jensen

    Could you please support me with migration of materials in Direct Transfer 1909?

    I have migrated materials from Source system  where they have data in Purchasing, MRP and Accounting views at plant level. Unfortunately in the Target system  only Accounting view has been created.

    CVT%20Code%20for%20Views

    CVT Code for Views

     

    I have performed also a simulation with the same BAPI - BAPI_MATERIAL_SAVEREPLICA via transaction SE37 and a material has been created correctly with mentioned views above.

     

    In 1909 it is not possible to modify the CVT rule. Can you advise me, how can I resolve the issue?

    Thanks for sharing your knowledge!

     

    Best regards,

    Desislava Dimova

    /
    CVT%20Code%20for%20Views
    • Hello Desislava Dimova,

      regarding the in scope/out of scope, the migration object documentation should give all the information needed. You see here the information I have copied from an 1909 system. The information is not clustered in views but according to type of data which is migrated.

      Material_1909_in_out_of_scope.png

      Material_1909_in_out_of_scope.png

      Regarding your second question (the CVT rule), pls. be so kind and open a ticket on component CA-DT-MIG-S4.

      Best regards,

      Heike

       

      /
      Material_1909_in_out_of_scope.png
  • Hi Heike,

    in direct transfer 2020, can we also have the same functionality as file/staging approach that we can handle the result after the function module called? in file/staging there is an include for Handling the Result Parameter.

    we want to fill our customized mapping table after the data object created, ideally can we use the 2nd transfer step where we can call a function module to update the mapping table?

    Thanks.

    Chen Jun

    • Hello Chen Jun,

      I have created a video which is called "How to create an own mapping rule" (for release 2020). Pls. see this link.

      Starting at time 18:15, I explain the parameters in transaction LTMOM (modelling environment) which have to be maintained in order to get back the created mapping value. This might be especially interesting in case of internal numbering or for multi-step migration objects such as e.g. fixed asset.

      I hope this answers your question?

      Best regards,

      Heike

       

      • Dear Heike,

        Thanks very much for your feedback, your solution is very good but unfortunately this only works with the value mapping, we have to run a lot of projects in few years to transfer the data from legacy ERP systems to S4. Value mapping is project based mapping strategy, we want to have one central mapping table for specific field, e.g. material number, during this transition period, other applications can also access those mapping tables.

        will we consider such requirement? Thanks.

        Chen Jun

          • Dear Chen Jun,

            I would have a question regarding this topic. Assume, you create a central table to hold the values in a central manner and SAP provides an API which is able to extract and fill the SAP mapping tables of the Direct Transfer. Would this help?

            Best regards,

            Heike

          • Dear Heike,

            Thanks for asking, I think this will help a lot. Just one additional requirement, when we extract the mapping data from value mapping, can we only extract the entries that the data is migrated, since the mapping tasks are confirmed before the data is migrated, often we have the entries are not migrated so far.

            Chen Jun

          • Hello Chen Jun,

            do you mean: regarding this API, it should also be able to extract only the target mapping values for which the migration has already taken place successfully?

            Best regards,

            Heike

          • Dear Heike,

            yes, since the entries in mapping table should reflect the actual migration result, other applications can access the correct mapping result. I hope this is OK?

             

            Chen Jun

          • Hello Chen Jun,

            thanks for clarifying the requirement.

            Currently, there is no such functionality available. The target mapping entries only reflect which entries have been created while selecting the source data sets (old value = new value as proposal value) respectively the values which have been edited manually or uploaded by the customer.

            In case of internal numbering, the target mapping values are written back into the mapping after the internal number has been fetched from the target system number range and used to create the data record in the target system.

            Best regards,

            Heike

          • Dear Heike,

            Thanks for your feedback, for complex mapping relationship or the mapping will be used in a later stage, we will build up our own mapping table.

            I have another question. Now we start the first test in quality system, after we transport the project to quality system. We are aware that we can't change any filters in the selection of source tables in LTMOM. that means we also need to set all the filters in development system, then transport to quality system and later productive system.

            Is this designed like that or just because we can't edit the project in quality system?

            Thanks.

            Chen Jun

          • Hello Chen Jun,

            yes, the design works like this. Pls. see the picture below. I am currently working on a slide deck around the transport topic in MC DT. It will still take some time until it will we published :-), but you will then find it in the MC landing page LINK.

            Transport%20concept

            Transport concept

            Best regards,

            Heike

            /
            Transport%20concept
          • Dear Heike,

            Thanks for your quick feedback.

            from the slides, I can understand the selection for company code is transported, but not all the filters.

            do you think this is reasonable that all the filters need to be transported? The tests in development and quality systems as well as final productive migration scope normally are different, at least it would be good if we can change the filters so that we can influence the test scope?

            I also found there is another transaction code CNV_PE_PROJ, in the transaction code we can change the filters in quality system, do you see risks if we do so?

            Thanks.

            Chen Jun

          • Hello Chen Jun,

            the transaction you mentioned is NOT RELEASED to customers!!

            With SAP S/4HANA 2020 we introduced the transport function to distribute MC projects across the system landscape. Furthermore, we decided to allow the MC project configuration in modifiable environments such as e.g. development systems only. This includes the project creation, adding a migration object (MO) to a project and all configurations in the migration object modeler (LTMOM). I see that some more flexibility might be needed in some rare cases, on the other hand, you have the requirement of minimizing the risk in a productive run - thus only tested customizing shall be used.

            I guess if you talk about "filters", you mean the restrictions on table field level, right? Because filters are basically used in the sense of means to delimitate and derive organizational units as e.g. company codes, controlling areas and so on - pls. see slide 31 in this LTMOM slide deck: LINK

            With 2020 we introduced the mandatory assignment of a development package during the MC project creation process.

            Prerequisites for Modifications

            The check if a project/MO is modifiable or not is based on two criteria

            1. Check for client-specific and cross-client object changes
            2. Check for system change options
              1. Global Setting
              2. Namespace and software component of given development package

            Check for client-specific and cross-client object changes
            → Transaction SCC4

            • client-specific object settings in SCC4
            •  
            • cross-client object settings in SCC4
            •  

            Check for general system change options
            → Transaction SE06 (button "System Change Option")

            Best regards,

            Heike

          • Dear Heike,

            Thanks very much for your detailed explanations.

            I understand that all the "development" of the migration projects should be done in Dev system and transported to Qas and Prd systems. this is the advantage if I compare the file/staging approach which can only be exported and imported.

            but the "filter"(selection or restrictions on table field) could be different in different systems.

            regarding the transaction code CNV_PE_PROJ, this is very powerful and useful though this is not released to us. normally we need to build up complex mapping rules for migration, in this transaction code, I see the possibility that we can define the split/condition rules and so on. we have few use cases which exactly need those features. Compared to file/staging approach, in direct transfer approach, I missed the event-based rule where I can enhance/skip the data entries.

            you know in greenfield projects, we can't simply transfer the data entries, normally we need to define complex mapping relationship since the process/data structure are different. not easy as in brownfield projects.

            Chen Jun

             

          • Hello Chen Jun,

            you are right, in Direct Transfer there are no event-based rules. The rules which are assigned to a field are always called at one point in time: when you start the simulation, the rules are applied to the field values and the instances containing the transformed values are passed to the API.

            There is only one rule which is called at a different point in time: the so-called skip rule. This rule can be applied if instances shall not be passed from the sender system to the Migration Cockpit (available since release 2020). This rule is a coding rule and is maintained in LTMOM, pls. see slide 36 in the above mentioned slide deck.

            Best regards & have a nice weekend!

            Heike

          • Dear Heike,

            Skip rule is useful for us. but skip rule can't fulfill all the requirements since we can only keep or skip at instance level, in some cases we need to decide if we keep or skip the the entries in the second level table based on certain logic.(e.g. schedule lines in schedule agreement)

            that means for the loop of each table, we would need a kind of event-based rule to influence the transformed values to the API. this is already already available in file/staging approach.

            Thanks and wish you have a nice weekend too!

            Chen Jun

          • Hello Chen Jun,

            yes, the requirement you describe above can currently not be covered with the approach Direct Transfer.

            Best regards,

            Heike

          • Dear Heike

            one additional question: can we use the manual defined table?

            I can create the table, but how can I create the include? I learned from the documentation that the include should exist in source system as well. can I simply create the same include in source and target systems manually?

            Thanks.

            Chen Jun

          • Hello Chen Jun,

            yes, it is sufficient to create the include in the source system. It is not necessary to create it in the target system.

            Best regards,

            Heike

          • Dear Heike,

            Thanks for all your professional answers!

            Wish you have a nice holiday!

            Stay safe and healthy!!

            Chen Jun

  • Hello Heiki,

    Is it possible to use the new internal number range while creating the materials in S/4HANA using  direct transfer? or can materials be only created with the same material numbers which exist in ECC? The same thing I would like to also ask for customer and suppliers.

    Regards,

    Lalit Sharma

    • Hello Lalit Kumar Sharma,

      for Migration Cockpit, Direct Transfer, releases 1909 and 2020, only external numbering is available for material (1909) respectively product (2020) => pls. compare migration object documentation on help.sap.co, direct link.

      Regarding customers / vendors / business partners, we have very detailed info material on our Landing page. It explains all possible variants regarding internal/external numbering.

      http://help.sap.com/S4_OP_DM

      => section training, training material, Direct Transfer

      Pls. find here the direct link to the respective PDF (name: CVI integration).

      Best regards,

      Heike

      • Hello Heiki,

        Thanks for your reply and confirmation regarding material number range.

        Regarding customers, I have already looked into this direct transfer CVI document and tried to test the 1st scenario by configuring the internal numbering for both BP grouping and customer account group but I get an error saying "No target value specified for Customer 0000010031;specify target value to proceed". Not sure if there is an error in product 2020 or I'm missing something while transferring the data? Just for your info, I have kept the 'Blank' value in the value mapping step for customer number.

        Moreover I would also like to clarify if I use the internal numbering for both BP grouping and customer account group, can I still create the BP and customer with the same number? The CVI document say that "The business partner number need not be same as the customer/vendor number, they are generated". In our case we are planning to keep the same number for BP and customer using the new internal number range all together, so would like to check if we are allowed to do that via direct transfer?

        Best regards,

        Lalit Sharma

        • Hello Lalit Sharma,

          I would suggest that you go in detail through the migration object documentation of the concerned objects: LINK. Pls. make sure that you use the correct release (in the upper part) & the right approach (Direct transfer SAP ERP). If there are no hints regarding the issues, pls. open a ticket on component: CA-LT-MC.

          Best regards,

          Heike

           

           

           

          • Hello Heiki,

            Thanks for your reply. I have checked the documentation but there is no hint regarding this issue. We will raise this to SAP if needed.

            Regards,

            Lalit Sharma

  • Hello Heiki,

    We are trying to migrate data from ECC to S4 through direct transfer. Until now we have successfully transferred the predessor to the Customer migration object. However, when we try to migrate Customers we experience an error that we cannot solve on our own.

    When we simulate the instance the result is successful. However, when we try to migrate the instance we receive the errors shown in the screenshot below:

     

    Additional question. We have followed the SAP S/4HANA Cookbook - Customer/Vendor Integration. Nevertheless, I cannot find any information about the order of importing the migration cockpit for customers, vendors, and business partners when BP is active in the source system, but the BPs are not correlated to the customers and vendors you want to migrate.

    /
    • Hello Jeppe,

      my name is Heike, not Heiki 🙂

      The cookbook you mention is not Migration Cockpit specific but a general SAP document so-to-say.

      Regarding MC Direct Transfer, pls. refer to this document: LINK. It describes in detail all the possible scenarios as well as CVI objects and their sequence.

      You find a lot of detailed material (also regarding the modeler) regarding MC DT on our so-called landing page: LINK

      Did you make enhancements to the SAP migration object? If not, are you sure that you have the current content in your system? Pls. refer for more information to this slide:

      If this does not solve the issue, pls. open a ticket under CA-LT-MC. Pls. also mention your release.

      Best regards,

      Heike

       

  • Hello Heike,

    Is the "source code" under transformation rules in LTMOM are supported in S/4HANA on Premise 2020? My requirement is to adapt the value mapping of material numbers (based on my own source code) for migration object BOM. If source code is supported in 2020, then do you have any documentation describing the procedure in detail?

    Regards,

    Lalit Sharma

    • Hello Lalit Sharma,

      in this slide deck, you find deep dive material about LTMOM functionality. Also on how to create a source code rule. Own source code rules are supported since onprem 2020.

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

      Best regards,

      Heike