How To Fix ESH_OM_OBJ_MODEL_RP2153 - Authorization check &1 has been deleted in the meantime

SAP Error Message - Details

• Message type: E = Error

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

• Message number: 153

• Message text: Authorization check &1 has been deleted in the meantime

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_RP2153 - Authorization check &1 has been deleted in the meantime ?

  The SAP error message ESH_OM_OBJ_MODEL_RP2153, which states "Authorization check &1 has been deleted in the meantime," typically occurs in the context of the SAP Enterprise Search or the SAP NetWeaver system when there is an issue with authorization checks related to object models.
  Cause:
  
  Deleted Authorization Object: The error indicates that an authorization object that was previously available has been deleted or is no longer valid in the system. This can happen due to changes in the authorization model, such as modifications to roles or profiles.
  Role Changes: If a user’s role has been modified or if the authorization object has been removed from the role, the system may throw this error when trying to perform an action that requires that authorization.
  Transport Issues: If changes were transported from one system to another (e.g., from development to production), and the transport did not include the necessary authorization objects, this error may occur.
  
  Solution:
  
  Check Authorization Objects: Verify if the authorization object mentioned in the error message still exists in the system. You can do this by using transaction code SU21 to check the authorization objects.
  Role Assignment: Ensure that the user has the correct roles assigned that include the necessary authorization objects. You can check this using transaction SU01 (User Maintenance) and SU02 (Role Maintenance).
  Recreate or Restore Authorization Object: If the authorization object has been deleted, you may need to recreate it or restore it from a backup if available.
  Transport Check: If the issue arose after a transport, check the transport logs to ensure that all necessary objects were included in the transport request.
  Authorization Trace: Use transaction SU53 to analyze the authorization check failure. This will provide insights into which specific authorization is missing.
  Consult Documentation: Review SAP documentation or notes related to the specific authorization object or the error message for any additional guidance.
  
  Related Information:
  
  Transaction Codes: 
  
  SU01: User Maintenance
  SU02: Role Maintenance
  SU21: Authorization Object Maintenance
  SU53: Authorization Check Analysis
  
  
  SAP Notes: Check SAP Notes for any known issues or patches related to this error message.
  Support: If the issue persists, consider reaching out to SAP support for further assistance, especially if it involves complex authorization scenarios.
  
  By following these steps, you should be able to identify the root cause of the error and implement a solution to resolve it.