Value mapping issue Migration Cockpit ERP to S/4HANA Migration

[moritzbp]

Dear all,

I have been trying to migrate data from an ERP to an S/4HANA system via the Fiori migration cockpit. So I set up the RFC connection and the bank key values are correctly detected from the ERP system. However, the system does not automatically take the detected values from the source system as the values for the target system as can be seen below:

So I would need to confirm them manually and since we have over 4k values, this would be very inefficient. I have found out about the option to get mapping tables in Excel but it would be more convenient to solve this issue to be able to apply the solution to all values.

In the SAP documentation it already hints that the values will not always be provided. Now I just haven't been able to find what this depends on.

Are there settings in the target system that are outside the Migration Cockpit that I have to change? I feel like I have exhausted all the options within the cockpit.

Any help or ideas are much appreciated! If there are any clarification questions, please do not hesitate to ask.

Best wishes,

Moritz

[FrankFinkbohner · Accepted solution]

Hello Moritz,

the target values are not pre-filled with the source values if the source value is longer than the target value.

For example, a company code (BUKRS) has length 4. If you provide a value longer than 4 characters as source value for example "100035" than it will not be transferred as target value. The reason why this happens is to avoid truncations and as consequence wrong value confirmations.

For example "100035", "100040" are valid source values.
If they were transferred to the target values there were truncated and both would get target value "1000". If the user now doesn't check the target values for correctness, "1000" is a valid value for company codes, and then click on "confirm all", the mapping will probably be wrong as both will get the same target company code "1000".

Instead of transferring and truncating values that does not fit into target value field, no value is provided. The user must then select the correct value via the value help.

In your case, if you are are using the staging tables approach, you either provide bank keys that are longer than the target keys (15) or there is a error in the cockpit. Check your source values and compare the length if it is longer than 15 characters.

But I guess you are using Direct Transfer approach as you said you set up RFC connection. Here it looks more like an error with the cockpit and you should follow the procedure provided by Prithvi to first check that all relevant SAP Notes to correct errors are installed.

BR

Frank

[moritzbp · Accepted solution]

I never thanked you for your effort! Thank you Frank, it was indeed an issue with the length of this input. I first had to change the cutomizing to allow the desired character length.

[PMG1 · Accepted solution]

Hi Moritzbd,How was this error solved?

[PMG1 · Accepted solution]

Hi Moritzbp, I'm also facing the same issue. I don't see any error in Migration cockpit. How was this error solved?

[prithvispandana]

Hello,

Please confirm if all the latest corrections related to Migration cockpit is implemented. If not, please implement them and try again with a new project.

How to implement the latest corrections released for Migration cockpit

If the issue still persists, please create an support incident under CA-LT-MC component.

Thanks,

Prithvi

[moritzbp]

Thank you Prithvi!