MDGM - Activation Error - Field not on Database tables

[benjamin_allsopp]

Hi,

I've recently added some custom fields to the UNITOFMSR entity.

These fields were not added to the database tables for business reasons. And so are only found on the generated tables.

When the user tries to activate a subsequent CR there is an activation failure due to these fields. It can't find the fields on MARM so takes the value as 0 and when comparing this to what it expects the value to be it fails saying that the data has been changed in the reuse active area.

How can I stop failures like this on fields that don't exist on the database tables? I

I thought of removing the UNITOFMSR entity type (as it's not needed here) from the CR that's having issues but I need the material entity and it won't let me take of UNITOFMSR and leave MATERIAL on the CR.

Any ideas?

[d024348 · Accepted solution]

Hi, in this case, a flex entity with a 1:1 cardinality to UNITOFMSR would be the idea. This means that the fields are not added to the backend but still carry over from one CR to another.

Regards, Ingo Bruß