cancel
Showing results for 
Search instead for 
Did you mean: 
Read only

Hana Migration Cockpit Direct Transfer Error

0 Kudos
1,031

Hello,

In simulating data for the 'Product' direct transfer object from ECC to 2021 S4, I get this error message: "The field MARC-PRCTR is defined as a required field; it does not contain an entry."

In the source system, the field is not empty, and in LTMOM mapping I have tried multiple options - keeping the default CVT mapping, mapping directly by dragging MARC-PRCTR to PROFITCENTER in the target API, and also creating a mapping rule that allows me to see and confirm the profit centers in the fiori app. When looking at the selected data, I see profit centers present on all entries, and in looking at the failed simulated data I also see profit centers in MARC-PRCTR.

I'm lost and am not sure what to try next.

Thanks in advance for the help!

Accepted Solutions (0)

Answers (2)

Answers (2)

zeyad99
Discoverer
0 Kudos

Hello, I had the same error as the screen shot even though the profit center field was filled. After further analysis I found that the instance in the valuation data sheet was mapped to an additional plant that was not maintained in the plant data sheet for the same instance (This issue was not shown during the validation). After adding the additional plant in the plant data sheet the issue was solved. You can check your instance for other maintained views as well.

Orfeas_Skn
Discoverer
0 Kudos

Hello, Have you come with a solution to the problem? We face the same error in S4HANA Cloud 2023 Private edition. Despite the profit center being defined in the template, the error seems to persist from the majority of the materials.

zeyad99
Discoverer
0 Kudos
Hello, I had the same error as the screen shot even though the profit center field was filled. After further analysis I found that the instance in the valuation data sheet was mapped to an additional plant that was not maintained in the plant data sheet for the same instance (This issue was not shown during the validation). After adding the additional plant in the plant data sheet the issue was solved. You can check your instance for other maintained views as well.