Problems with migration object Product - extend existing record by new org levels

[ornecogli]

Dear all,

I am in the migration phase in my project. I have created a separated project for the migration object Product - extend existing record by new org levels and tried to upload a file with several materials and plants, but I get an error message from the app. I made a test with 3 materials that need to be extended in 3 different plants, so I created 9 lines, each one with a different RUN ID. Only one line per material has been simulated correctly, the other lines have been skipped to avoid multiple updates on same target instance. 

Do I have to prepare one file per plant? Or is there another way to centralize all the records in one file?

Thank you in advance.

Best regards,

Ornella

[Chris1973 · Accepted solution]

Hi @ornecogli 

Thank you for your question.

Have a look at

Enhanced Migration Object: Product - extend existing record by new org levels

https://help.sap.com/docs/SAP_S4HANA_CLOUD/3c916ef10fc240c9afc594b346ffaf77/7a2ad47f16d54850b2a88bef... for details.

Based on your screenshots, that error happens because multiple rows in your migration file refer to the same product number even if they are for different plants. The migration cockpit only allows you to use one update per product and per migration run. This is done to prevent conflicting updates.

Try splitting your file by product or plant, keep one file but run filtered migrations per plant. For large updates use API_PRODUCT_SRV to extend your plant data.

Best regards

Chris

[ornecogli · Accepted solution]

Hi @Chris1973, Thank you for your response. I did the migration cockpit as you explained, with one update per plant. I had to extend materials for 53 different plants, and I wondered if there was a simpler way to do it. Thank you for your time. Best regards, Ornella"

[Chris1973 · Accepted solution]

Good day @ornecogli

Good to know you were able to progress with your task.

Unfortunately, the public cloud does not provide a more simplified approach.

The API-based extension and automating your cockpit runs per plant are currently the options available at the moment.

You may consider influencing SAP development journey by  taking part in the Customer Influence and Adoption community.  

Best regards

Chris