Do you have any question about this error?
Message type: E = Error
Message class: ESH_OM_OBJ_MODEL_RP2 - Object Model Repository (2)
Message number: 752
Message text: Boost condition &1 (no user), selection &2 already exists
Boost condition (Ranking factor/application object type/boost
guid/ranking factor attribute/condition guid): &v1&, selection (sign,
opt, low, high - condition guid &v2&) already exists.
The system issues an error message and will not allow you to continue with this transaction until the error is resolved.
Error message extract from SAP system. Copyright SAP SE.
ESH_OM_OBJ_MODEL_RP2752
- Boost condition &1 (no user), selection &2 already exists ?The SAP error message ESH_OM_OBJ_MODEL_RP2752 typically occurs in the context of the SAP Enterprise Search or SAP HANA when there is an issue related to the boost conditions defined for search objects. This specific error indicates that there is an attempt to create or modify a boost condition for a search object, but a selection with the same name already exists, and it is not associated with any user.
Cause:
- Duplicate Boost Condition: The error arises when you try to create a new boost condition with a name that already exists in the system. The system does not allow duplicate entries for boost conditions.
- Missing User Association: The existing selection might not be associated with any user, which can lead to confusion in the system regarding ownership or usage of that selection.
Solution:
Check Existing Boost Conditions:
- Go to the relevant transaction or configuration area where boost conditions are defined (e.g., transaction
EHS_SEARCH
or similar).- Look for existing boost conditions and see if there is one with the same name as the one you are trying to create.
Modify or Delete Existing Condition:
- If you find a duplicate boost condition, you can either modify it to meet your needs or delete it if it is no longer required.
- Ensure that the existing condition is properly associated with a user if necessary.
Create a Unique Name:
- If you need to keep the existing boost condition, consider creating a new boost condition with a unique name that does not conflict with existing entries.
Check User Assignments:
- If the existing selection is not associated with any user, you may want to assign it to a user or group to avoid confusion in the future.
Related Information:
EHS_SEARCH
, EHS_BOOST
, or others depending on your SAP version.By following these steps, you should be able to resolve the ESH_OM_OBJ_MODEL_RP2752 error and manage your boost conditions effectively.
Get instant SAP help. Start your 7-day free trial now.
ESH_OM_OBJ_MODEL_RP2751
Boost condition &1, condition guid &2 already exists
What causes this issue? Boost condition (Ranking factor/user/boost guid/ranking factor attribute/condition guid): &v1&, selection (sign, opt,...
ESH_OM_OBJ_MODEL_RP2750
Boost condition &1 (no user), condition guid &2 already exists
What causes this issue? Boost condition (Ranking factor/boost guid/ranking factor attribute/condition guid): &v1&, condition (sign, opt<(&...
ESH_OM_OBJ_MODEL_RP2753
Boost condition &1, condition guid &2 already exists
What causes this issue? Boost condition (Ranking factor/application object type/user/boost guid/ranking factor attribute/condition guid): &v1&...
ESH_OM_OBJ_MODEL_RP2754
Where-used request for categories could not be executed
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
Click on this link to search all SAP messages.