How To Fix ESH_OM_OBJ_MODEL_RP2142 - Referenced authorization object key &1 (auth. object &2) does not exist

SAP Error Message - Details

• Message type: E = Error

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

• Message number: 142

• Message text: Referenced authorization object key &1 (auth. object &2) does not exist

What causes this issue?

You referenced an assignment authorization object key &v1& (representing
ABAP authorization object &v2&) in the authorization check, but the
authorization object 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_RP2142 - Referenced authorization object key &1 (auth. object &2) does not exist ?

  The SAP error message ESH_OM_OBJ_MODEL_RP2142 indicates that there is an issue with an authorization object that is being referenced in the system. Specifically, the error states that the referenced authorization object key does not exist for the specified authorization object. This can occur in various scenarios, particularly when dealing with authorization checks in SAP applications.
  Cause:
  
  Missing Authorization Object: The authorization object that is being referenced in the system does not exist in the database. This could be due to a configuration issue or a missing transport.
  Incorrect Configuration: The system might be incorrectly configured, leading to references to non-existent authorization objects.
  Transport Issues: If the authorization object was supposed to be transported from another system and the transport did not occur successfully, this error can arise.
  User Role Issues: The user roles assigned to a user may not include the necessary authorization objects, leading to this error when the system checks for authorizations.
  
  Solution:
  
  Check Authorization Object: Verify if the authorization object mentioned in the error message exists in the system. You can do this by using transaction code SU21 to check for the authorization object.
  Create or Transport Authorization Object: If the authorization object does not exist, you may need to create it or transport it from another system where it exists.
  Review User Roles: Check the user roles assigned to the user encountering the error. Ensure that the roles include the necessary authorization objects.
  Authorization Check: Use transaction SU53 immediately after encountering the error to see which authorization checks failed. This can provide insight into what is missing.
  Consult Documentation: Review SAP documentation or notes related to the specific authorization object to understand its purpose and requirements.
  Contact Basis Team: If you are unable to resolve the issue, it may be necessary to involve your SAP Basis team or security team to investigate further.
  
  Related Information:
  
  Transaction Codes: 
  
  SU21: To manage authorization objects.
  SU53: To analyze authorization failures.
  PFCG: To manage roles and authorizations.
  
  
  SAP Notes: Check for any relevant SAP Notes that may address this specific error or provide additional guidance.
  Authorization Concept: Familiarize yourself with the SAP authorization concept, including how authorization objects, fields, and values work together to control access.
  
  By following these steps, you should be able to identify the cause of the error and implement a solution to resolve it.