How To Fix UGMD410 - Impossible de mapper attributs &2 sur &3 (voir texte descriptif)

SAP Error Message - Details

• Message type: E = Error

• Message class: UGMD - FIN Master Data: Messages

• Message number: 410

• Message text: Impossible de mapper attributs &2 sur &3 (voir texte descriptif)

Quelle est la cause de ce problème?

Le système émet un message d'erreur et ne vous permettra pas de poursuivre cette transaction tant que l'erreur n'est pas résolue.

TRANSLATORS! Be sure to retain the original order of the numbered
conditions and sequence of the variables.
You want to assign the remote attribute &V3& to the role attribute &v2&
of field &v1&. This is not possible because in this case the condition
&V4& has been violated.
The following conditions must be met before you can allocate the two
attributes to each other:
To characteristic &v1& you need to assign a role that has a &V2&
attribute.
Characteristics &v1& and &v3& must be remote fields (for example,
InfoObjects); and &v3& must be assigned as an attribute to
characteristic &v1&.
Attributes &v2& and &v3& must have the same <DS:DE.DATATYPE_D>data type
</>.
Attributes &v2& and &v3& must have the same <DS:DE.DDLENG>length</>.
Attributes &v2& and &v3& must have the same <DS:DE.CONVEXIT>conversion
routine</>.
Attributes &v2& and &v3& must have the same time dependencies.
Assignments of remote attributes to role attributes must be injective -
that is, only one remote attribute can be assigned a given role
attribute, and only one role attribute can be assigned to a remote
attribute. The only exception to this is stated under condition 8.
If role attribute &v2& has other kinds of dependencies besides possible
time dependencies, and these other dependencies cannot be modeled with
remote attribute &v3&, you need to confine all of these additional key
fields to unique fixed values when assigning the attribute. In this
case, the assignment only applies to these values of the independent
characteristics. In a case as described here, you can also assign
multiple remote attributes to a single role attribute, but then you need
to confine the respective additional key fields to different fixed
values.
Role attribute &V2& may not be mapped to a predefined fixed name of an
InfoObject. This is because, in this specific case, an implicit
assignment already exists. Thus, it is sufficient to assign, as an
attribute, the InfoObject assigned to &V2& in table <AB>UGBW4000</> to
InfoObject &V1&. If you do this, the system will always automatically
transfer any changes of role attribute &V2& to the SAP BW system, as
well.

Réponse du système

The data basis cannot be saved.

Comment corriger cette erreur?

Either correct the attribute assignment (as described above), or delete
it.

Procédure pour les administrateurs système

Extrait du message d'erreur du système SAP. Copyright SAP SE.