Resolving Key Mapping Missing Issues while sending Freight Unit from Cloud ERP to On Premise system

[Saurabh_Goyal]

Introduction

The process for Scope Item 6W1 for External Transportation Planning enables transportation requests created in SAP S/4HANA Cloud ERP to be planned within an SAP On Premise system. In this case, Freight units generated in SAP S/4HANA Cloud ERP can be transferred to the On Premise system (with SAP TM) for detailed transportation planning.

Once planning is completed, the results are sent back and integrated into SAP S/4HANA Cloud ERP in the form of freight orders. Upon transfer, transportation charges for these freight orders are calculated automatically. Based on the finalized freight orders, outbound deliveries can then be initiated.

This post covers the scenario where an error is received and the possible workaround for the error.

Kindly note that below steps are a workaround and steps must be taken to resolve error by undertaking the master data replication as per the set up guide.

Process Details

Complete the set up for the scenario including the set up of communication scenario and Data replication. The process requires the Purchase order be created within the SAP S/4HANA Cloud ERP. Ensure that the Purchase group is selected as "006" External TM Planning (refer below screenshot).

Based on settings a Transportation Management Freight unit is created. The same can be seen within the Purchase order app under the tab "TM Status"

As the Process needs the Freight Unit planning within the external TM system the scope items 6W1 in SAP S/4HANA Cloud ERP should be activated. Once done the Freight Unit from Public Cloud system is replicated to the On Premise system.

This replication message should create a Freight Unit within the On Premise / Decentralized TM system.

Challenge

In case of Failure of the FU replication, check the message within the SAP Message Monitor to identify the type of error. One of the error that can occur may relate to Invalid data. As you can see in the below screenshot the error related to invalid data.

This blog covers on the process to be followed to resolve this issue.

To resolve the issue, as you can see the below warnings need to be removed to resolve the error. These warning relate to incorrect / missing key mapping for different Master Data Objects like Location / Business Partner / Product between the Public Cloud and the On Premise system. This can happen in case the replication was not performed correctly.

Resolution

To resolve the issue, key mapping needs to be maintained in both the Public Cloud and the On Premise system.

You can follow the following steps for the same.

1. Use the Tcode MDG_KM_MAINTAIN within the On Premise SAP system. Manage Key Mapping UI opens.

1. For each of the impacted Business Object Type (as per the error) select the Object Type (example Business Partner in above screenshot) and Object Type ID, Business System and the Master Data ID (example Business partner ID).
2. Click on Add Row to add the entries as below. Fill in the details such that there are 2 rows each of Public cloud and On Premise system
   1. Row 1 with Public Cloud System ID and BP number and Row 2 for BP UUID in the standard format: 8-4-4-4-12 (hexadecimal groupings). Example – If location UUID is 355F4B6A67ED1EEE9297A3E7521BF064 it should be mentioned as 355F4B6A-67ED-1EEE-9297-A3E7521BF064
   2. Repeat the same for the On Premise system with corresponding details added in row 3 & 4.

1. Save
2. Repeat the same process from steps 1 to 4 for all other Master data objects as per the error.
3. Repeat the same process from steps 1 to 5 within the Public Cloud system using the app „Manage Key Mapping“.

Rerun the process of FU replication and mapping error should be resolved now.