How To Fix SXIVERI012 - ID hachage non unique:&1 type:&2 nom:&3 esp. nom:&4

SAP Error Message - Details

• Message type: E = Error

• Message class: SXIVERI -

• Message number: 012

• Message text: ID hachage non unique:&1 type:&2 nom:&3 esp. nom:&4

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.

Quelle est la cause de ce problème?

Multiple metadata entries (that is, multiple ABAP names) were found for
a WSDL key (type/name/namespace). The only way to correct this
inconsistency is to remove the incorrect metadata.
This problem can occur as a result of the following:
Proxies have been generated in different systems for the same WSDL key
(type/name/namespace), with different ABAP names resulting from the
generation procedure, and then transported to a common system.
A proxy has been generated in a subsequent system as a local object
($TMP); following this, a transport from a previous system has been
imported for the same WSDL key. -> You must delete the local object in
$TMP, see reference to report below.
Ultimately, this problem is an indication that the organizational
allocation of software components/namespaces as regards development
systems has not been adhered to.

Réponse du système

Since a proxy is identified by the WSDL key, the assignment of the WSDL
key and proxy metadata is no longer unique, that is, it may no longer be
possible to load the metadata. Other more severe side effects cannot be
ruled out.

Comment corriger cette erreur?

Case 1: You must delete one of the two proxies in its original system by
using transaction SPROXY. You must transport the deletion to the
subsequent system.
Case 2: You can use report
<DS:REPO.SXIVERI_PROXY_HASHID_CHECK>SXIVERI_PROXY_HASHID_CHECK</> to
find the affected objects and then delete the respective "wrong" proxy
locally.

Procédure pour les administrateurs système

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