Skip to Content
Personal Insights
Author's profile photo Didier Ruelens

Direct transfer – Mapping Tasks

Hello everybody and welcome to my blog post. This blog will be dedicated to the Direct Transfer and more specifically the Mapping Tasks. The aim of this blog is to get acquainted with the basics of mapping tasks and get an overview of the different steps explained while processing an example.

The mapping tasks, also called transformation rules, can be used to influence the values that are migrated from source field to their respective target fields or, in case no adjustments are needed, to simply confirm the proposed mapping between source and destination records. Depending on the migration object in question, the system will provide a standardized set of mapping tasks. If unconfirmed mapping tasks exist, both the simulation & migration step of the migration object will fail. Also when the same mapping task exist for different migration objects within the same project, SAP will remember the already saved values.

Prerequisites for this blog are:

  • You already created a project.
  • You already defined the migration objects.

The first example we will work with is mapping the migration object “Bank”.

Select the ‘Mapping Tasks’ option from the Migration Project Cockpit screen:

 

As banks are one of the more ‘simple’ migration objects, the only mapping activity that we need to perform / confirm is the one regarding bank keys

 

 

It is possible to change the automatically determined / proposed target destination field values. As such, we could adjust the proposed mapping so that the source date record with bank key 10010 will be created with bank key 11111 in the destination S/4 system

 

 

However, as there is no business requirement to adjust the mapping of bank keys in my project, I will simply confirm the proposed bank key value mappings.

 

Please note that the operation as shown below will only confirm the mapping value for the first 20 records.

 

 

In order to confirm the value mapping of all instances, confirmation should be executed via the previous screen.

 

 

A second migration object we will use as an example is “cost center”.

In the migration object cost center we want to map our source systems company code 1000 against our destination systems company code 2510. Here we can just fill in the value and confirm the mapping task.

 

The next mapping we want to do is the controlling area, we are going to map the source controlling area 1000 against the targets controlling area A000. You can always get an overview of all possible mapping possibilities by clicking the 2 boxes at then end of the line.

 

 

This way you can finish mapping by mapping to go over them all and continue with the simulation step. This can give errors meaning you might have to make some changes in the mappings.

 

Remarks:

  1. Transformation rules (= mapping tasks) can be transported. Values themselves cannot be transported; they can however be downloaded & uploaded.
  1. If required, it is also possible to perform mapping tasks outside of the SAP environment:
  • Download Mapping Templates:
    • You can download empty mapping templates to fill them. All mapping tasks which are available for the selected migration object are included.

 

  • Upload Values (only possible if the object has not yet been migrated)
    • When you upload the mapping values, you have different options:
      • Confirm values automatically
      • Do not confirm values automatically
      • Replace existing values
      • Modify values / Add values

 

  • Download Values:
    • You can download the automatically filled value mappings.

Conclusion:

Mapping tasks are an important step in the migration process. Therefor it is important to think about the mappings before confirming them. In the simulation step SAP will give an error if he does not recognize certain mappings while proceeding. But it will allow all mappings that are system-wise possible. For example, when you give a material a storage location that exists in the system, but is not correct seeing your physical warehouse structure, the mapping will go through without an error. This will give hick ups while performing warehouse tasks later on.

For the future:

I hope my blog post gave some basic insights in how to do the mapping in Direct Transfer. For more information you can consult: SAP S/4HANA Migration Cockpit SAP S/4HANA 2020 FPS02 and SAP S/4HANA Migration Cockpit – Migrate your Data to SAP S/4HANA. If you have further questions on this matter, please do not hesitate to ask via SAP Q&A.

In my next post I will talk about the next step in Direct Transfer: The Simulation & Migration process steps.

Stay tuned!

Happy Mapping and a successful migration!

Assigned Tags

      Be the first to leave a comment
      You must be Logged on to comment or reply to a post.