Do you have any question about this error?
Message type: E = Error
Message class: ESH_OM_OBJ_MODEL_REP - Object Model Repository
Message number: 558
Message text: There is already a fixed value definition for source field &3
In a composition or an association, a node field can be:
Assigned to a node field belonging to the opposite node within the
relation
Given a fixed value
You are trying to assign object type &v1&, node &v2&, field &v3& to
another node field, but a fixed value definition already exists there.
The system issues an error message and will not allow you to continue with this transaction until the error is resolved.
Correct your input accordingly.
Error message extract from SAP system. Copyright SAP SE.
ESH_OM_OBJ_MODEL_REP558
- There is already a fixed value definition for source field &3 ?The SAP error message ESH_OM_OBJ_MODEL_REP558 indicates that there is a conflict due to the existence of a fixed value definition for a source field in the context of the Enterprise Search (ESH) or Object Model (OM) configuration. This typically occurs when you are trying to create or modify a fixed value definition for a field that already has a fixed value defined.
Cause:
The error is caused by attempting to define a fixed value for a source field that already has an existing fixed value definition. This can happen during the configuration of the search model or when modifying the object model in the SAP system.
Solution:
To resolve this error, you can follow these steps:
Check Existing Definitions:
- Go to the relevant configuration area in SAP where the fixed value definitions are maintained (e.g., transaction codes like
EHS_SAFETY_DATA_SHEET
orEHS_SAFETY_DATA_SHEET
).- Look for the source field mentioned in the error message (indicated by
&3
in the error) and check if there is already a fixed value defined for it.Modify or Delete Existing Definition:
- If you find an existing fixed value definition that conflicts with your new definition, you can either modify it to meet your requirements or delete it if it is no longer needed.
- Ensure that any changes you make do not disrupt other configurations that depend on the existing fixed value.
Create New Definition:
- After resolving the conflict, you can proceed to create or modify the fixed value definition for the source field as intended.
Transport Changes:
- If you are working in a development environment, ensure that you transport your changes to the appropriate environments (e.g., quality assurance, production) after testing.
Related Information:
By following these steps, you should be able to resolve the error and successfully manage your fixed value definitions in SAP.
Get instant SAP help. Start your 7-day free trial now.
ESH_OM_OBJ_MODEL_REP557
Value is incompatible with type of node field
What causes this issue? The node field has the internal type &v1&. The value specified is not compatible with this type.System Response The ...
ESH_OM_OBJ_MODEL_REP556
Fixed value definitions of association ID &1:
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
ESH_OM_OBJ_MODEL_REP559
There is already a fixed value definition for target field &3
What causes this issue? In a composition or an association, a node field can be: Assigned to a node field belonging to the opposite node within the r...
ESH_OM_OBJ_MODEL_REP560
Object type &1, node &2, field &3 is already assigned to another field
What causes this issue? In a composition or an association, a node field can be: Assigned to a node field belonging to the opposite node within the r...
Click on this link to search all SAP messages.