How To Fix ESH_OM_OBJ_MODEL_REP648 - &1 "&2" a le même nom ds compos. logic. &3 et &4 ; renommer manuellement.

SAP Error Message - Details

• Message type: E = Error

• Message class: ESH_OM_OBJ_MODEL_REP - Object Model Repository

• Message number: 648

• Message text: &1 "&2" a le même nom ds compos. logic. &3 et &4 ; renommer manuellement.

Quelle est la cause de ce problème?

At least two software components contain objects with the same name and
you have established or want to establish a relationship between the
software components. Alternatively, you want to use objects from the two
software components together at runtime (for example, by creating search
connectors). The object type name specified is not unique within the set
of object models.
The naming conflict can arise due to the following situations:
Object types have been delivered or imported. The software component
that the objects have been imported to is used together with a software
component containing an object with the same name.
You have created a new hierarchical dependency between previously
uncorrelated software components that contain object types with the same
name.
Parallel runtime usage of software components containing object types
with the same name within the same logical system.

Réponse du système

The object name has to be unique. As long as there are unresolved naming
conflicts within the hierarchy of software components or within the set
of software components simultaneously assigned to the same logical
system, the software components cannot be used together at runtime. The
conflicts appear in the Enterprise Search object modeler or during
connector creation.

Comment corriger cette erreur?

You must resolve the naming conflict.
Solution options:
Rename the object type in one of the software components mentioned.
Note: Before you rename the object type, check whether data providers,
such as BADI implementations for custom data extraction, are used by the
object type. Ensure that all places that refer to the object type name
are adjusted accordingly.
Alternatively, if the object types are physically identical copies, you
can delete one of them.
<ZK>Example: </>
The object type SERVICE_DOCUMENTS is reported to exist twice.
To resolve the naming conflict, you have to rename the object type in
one of the affected software components or delete one of them. Suppose
you decide to rename the object in your own model to
SERVICE_DOCUMENTS_1.
If possible, you should rename the objects in your development system
and transport the new name within your system landscape.
Suppose the object SERVICE_DOCUMENTS uses a data extractor service (for
example CL_SERVICE_DOC_EXTRACTOR), which is implemented as a BADI
instantiation with a filter on the object type name SERVICE_DOCUMENTS.
In this case, you have to change the BADI filter to SERVICE_DOCUMENTS_1
and also transport this change within your system landscape.
After renaming object types, you must create the search connectors
again.

Procédure pour les administrateurs systè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.

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