How To Fix ESH_OM_OBJ_MODEL_RP2143 - The referenced authorization object key does not exist

SAP Error Message - Details

• Message type: E = Error

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

• Message number: 143

• Message text: The referenced authorization object key does not exist

What causes this issue?

The authorization object key you referenced in the authorization check
was deleted in the meantime.

System Response

The authorization check cannot be saved because it is inconsistent.

How to fix this error?

Adjust the authorization check accordingly.

Procedure for System Administrators

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.

Smart SAP Assistant

• What is the cause and solution for SAP error message ESH_OM_OBJ_MODEL_RP2143 - The referenced authorization object key does not exist ?

  The SAP error message ESH_OM_OBJ_MODEL_RP2143 indicates that there is an issue with an authorization object key that is being referenced but does not exist in the system. This error typically arises in the context of the Enterprise Search (ESH) or when dealing with authorization checks in SAP applications.
  Cause:
  
  Missing Authorization Object: The specific authorization object that is being referenced in the system is not defined or has not been created.
  Incorrect Configuration: There may be a misconfiguration in the authorization settings or in the way the authorization objects are being referenced.
  Transport Issues: If the authorization object was recently transported from another system, it may not have been transported correctly or may not exist in the target system.
  User Role Issues: The user role assigned to the user may not include the necessary authorization objects.
  
  Solution:
  
  Check Authorization Objects: Verify if the authorization object that is being referenced exists in the system. You can do this by using transaction code SU21 to check for the specific authorization object.
  Create or Adjust Authorization Object: If the authorization object does not exist, you may need to create it or adjust the existing one to ensure it meets the requirements of the application.
  Review User Roles: Check the roles assigned to the user encountering the error. Ensure that the roles include the necessary authorization objects. You can use transaction code PFCG to manage roles and authorizations.
  Transport Check: If the issue arose after a transport, check the transport logs to ensure that all necessary objects were transported correctly. You may need to re-transport the missing objects.
  Consult Documentation: Review SAP documentation or notes related to the specific application or module you are working with to see if there are any known issues or additional configuration steps required.
  
  Related Information:
  
  Transaction Codes:
  
  SU21: To check and manage authorization objects.
  PFCG: To manage roles and authorizations.
  SU53: To analyze authorization failures.
  
  
  SAP Notes: Search for relevant SAP Notes in the SAP Support Portal that may address this specific error or provide additional troubleshooting steps.
  System Logs: Check system logs (transaction SM21) for any additional error messages or warnings that may provide more context about the issue.
  
  If the problem persists after following these steps, it may be beneficial to consult with your SAP Basis or Security team for further assistance.