How To Fix ESH_OM_OBJ_MODEL_RP2674 - Ranking fact. &1 for appl. object type id &2, attribute &3 does not exist

SAP Error Message - Details

• Message type: E = Error

• Message class: ESH_OM_OBJ_MODEL_RP2 - Object Model Repository (2)

• Message number: 674

• Message text: Ranking fact. &1 for appl. object type id &2, attribute &3 does not exist

Self-Explanatory Message

Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of messages in the SAP system have a message text, however this is frequently insufficient to comprehend or resolve the problem.

To make things easier, more detailed information is frequently added to describe the issue, how to fix it, and the necessary steps or configuration modifications.

Unfortunately, there isn't any extra information in this error notice.

What else can you do?

First, use our AnswerBot below to get a possible cause and solution (requires a premium subscription).

Also, review the in-depth Common Questions & Answers listed below; you could discover a solution there or be able to connect with others who have faced similar challenges.

You can also try searching the SAP support portal (support.sap.com) but you need a special user ID to access it. It is possible that an SAP support note exists that provides additional details about the mistake or even steps for fixing it.

Smart SAP Assistant

• What is the cause and solution for SAP error message ESH_OM_OBJ_MODEL_RP2674 - Ranking fact. &1 for appl. object type id &2, attribute &3 does not exist ?

  The SAP error message ESH_OM_OBJ_MODEL_RP2674 typically indicates that there is an issue related to the ranking facts in the context of the SAP Enterprise Search or SAP HANA Search. This error suggests that the system is trying to access a ranking fact for a specific application object type and attribute, but it cannot find it.
  Cause:
  
  Missing Configuration: The ranking fact may not be properly configured in the system. This could be due to missing entries in the relevant configuration tables or settings.
  Object Type or Attribute Not Defined: The application object type ID or the attribute specified in the error message may not exist in the system. This could happen if the object type was deleted or if the attribute was not defined correctly.
  Data Model Issues: There may be issues with the data model that prevent the system from recognizing the specified ranking fact.
  Transport Issues: If the system has recently undergone a transport of changes, it is possible that the necessary configurations were not transported correctly.
  
  Solution:
  
  Check Configuration: Verify the configuration for the ranking facts in the relevant application. Ensure that the ranking fact is defined for the specified application object type and attribute.
  Validate Object Type and Attribute: Check if the application object type ID and attribute mentioned in the error message exist in the system. You can do this by navigating to the relevant configuration areas in SAP.
  Recreate Missing Entries: If the ranking fact is missing, you may need to recreate it. This can involve adding the necessary entries in the configuration tables or using transaction codes related to the specific application.
  Check Transport Logs: If the issue arose after a transport, review the transport logs to ensure that all necessary objects were transported correctly.
  Consult Documentation: Refer to SAP documentation or notes related to the specific application and ranking facts for additional guidance.
  
  Related Information:
  
  SAP Notes: Check for any relevant SAP Notes that might address this specific error or provide additional troubleshooting steps.
  Transaction Codes: Familiarize yourself with transaction codes related to the configuration of the application object types and ranking facts, such as EHS or SE11 for data dictionary objects.
  SAP Community: Engage with the SAP Community forums to see if other users have encountered similar issues and what solutions they found effective.
  
  If the problem persists after following these steps, it may be beneficial to reach out to SAP support for further assistance.