Data Migration Cockpit: TRCO transformation rule framework

[moritzbp]

Dear SAP-Community,

I am currently trying to run a direct data migration from SAP ERP to SAP S/4HANA via the data migration cockpit (DMC). I keep getting errors related to certain fields, with the note: "please go to the transformation rule framework and release the mapping entry"

There is absolutely no documentation that I could find, either here or on help.sap.com on that framework. Is this maybe a name for something much simpler than a framework? I am kind of lost as to where to continue.

Any help is much appreciated!

Best regards,

Moritz

[Kirstin]

Hello Moritz,

which S/4HANA release are you working with? It is hard to tell from only one screenshot, but it seems, that some mapping values, which you need to process the instances (maybe to simulate or migrate) have not been confirmed yet. If you want to run a simulation at least all the mapping values, which are relevant for the instances you want to simulate/migrate need to be confirmed in the mapping task screen.

The error message you got seems to be from an older version of S/4HANA. In the meantime the error messages have been adapted to guide the user to the mapping task.

I hope this helps to resolve your issue.

Best regards, Kirstin

[moritzbp]

Dear Kirstin,

thank you very much for your reply! I am using SAP S/4HANA 2023 (see screenshot). The confusing thing is that I have indeed confirmed all mapping tasks, but once I simulate it says the values have not been confirmed, and then I see that the confirmed values have been reset to the old values after the simulation is done. The problem might be that the Business Partner numbers from the old system are different in the new system, so I change them with staging tables in the mapping task window. A colleague said it might be related to the BP not having been migrated correctly since the Table "BUT0ID" being empty, even though the BP are in the system.

I just got confused by the term "transformation rule framework" that really made me think there must be a place where I fundamentally have to change something about mapping tasks in the backend.

Best regards,

Moritz