Skip to Content
Product Information
Author's profile photo Sandeep Kumar

Data Migration – Import mappings from Q to P system

Why Mapping values:

A migration object contains mapping information for the relevant fields, as well as any rules used to convert values that are migrated from source fields to target fields. The source file data values and target system field values need to be maintained and confirmed.

Example: The value in the source value column for country code is ‘Canada’ and the target column it has been truncated to ‘CAN’, because SAP S/4HANA allows a maximum of 3 characters for this field. But this does not match the format expected by SAP S/4HANA as this value is mapped to ISO codes for country code which is ‘CA’. Therefore, either change ‘CAN’ to ‘CA’ or select ‘CA’ from the target search list by selecting it from the value help options.

Considerations for moving Mappings to P system:

  • Mappings are applied at migration project level
  • All mappings are maintained andn confirmed in Q system
  • Data migration for all objects is completed successffully and validated

How to Export Mappings:

1. Click on the Export Content button

2. Click on Execute button and a .zip file will be generated, file could be found in Downloads folder

How to Import Mapping Values in P system:

1. Create new migration project

2. Make sure Mass Transfer ID is same as Q-system

3. Click on Import Content button and provide the file path for the generated file in Export mappings step above

4. Click on Execute and you should see a success message

5. Check the imported content under ‘Convert values’ step


For large sets of mapping values to be maintained and confirmed, this could be a time-consuming task.

To save time and avoid human errors, the migration tool does provide a very nice feature to move mappings from Q to P system using Import/Export functions.

Assigned Tags

      You must be Logged on to comment or reply to a post.
      Author's profile photo Riwa Mouawad
      Riwa Mouawad

      Very helpful and detailed - thank you for sharing, Sandeep!

      Author's profile photo Sandeep Kumar
      Sandeep Kumar
      Blog Post Author

      Thanks Riwa.

      Author's profile photo Clare Campbell-Smith
      Clare Campbell-Smith

      Very interesting.

      How do you find the performance when using mappings within the Migration Cockpit? We were warned off using this (by SAP) as it could have a detrimental impact on performance (this was on 1802). Would you recommend its use on a real project - or is it still better to do the data transformation on a separate tool prior to importing in the cockpit?

      Would be interested to know what approach other customers have taken.

      Author's profile photo Sandeep Kumar
      Sandeep Kumar
      Blog Post Author

      Good question - performance impact could be at 2 places

      a. Import/Export itself could take a long time if number of mapping entries are huge

      b. Transformation or mappings should be done in the source file in my opinion so that this can be directly re-used for data validation/reconciliation as well

      However, you still need to confirm some of the mappings like ISO codes, country codes etc in the tool irrespective of they are same in the file or not. This task can be eliminated using import/export function in P system.

      And yes i have used this in a customer project, data volumes were in range of 1000 records for few migraiton objects.

      Author's profile photo Sai Giridhar Kasturi
      Sai Giridhar Kasturi

      thanks for sharing...quite helpful.

      Author's profile photo Sandeep Kumar
      Sandeep Kumar
      Blog Post Author


      Author's profile photo Prateek Agarwal
      Prateek Agarwal

      Useful information. Thanks for sharing.

      Author's profile photo Sandeep Kumar
      Sandeep Kumar
      Blog Post Author


      Author's profile photo Gabriel Mattos
      Gabriel Mattos

      Thanks for sharing!!