How To Fix ESH_ADM_MSG172 - You are not authorized to delete a back-end system

SAP Error Message - Details

• Message type: E = Error

• Message class: ESH_ADM_MSG - ESH Administration and Monitoring Tool

• Message number: 172

• Message text: You are not authorized to delete a back-end system

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_ADM_MSG172 - You are not authorized to delete a back-end system ?

  The SAP error message ESH_ADM_MSG172 indicates that a user is attempting to delete a back-end system from the SAP system landscape but does not have the necessary authorization to perform this action. This error is typically encountered in the context of the SAP Enterprise Search (ESH) or similar administrative tasks.
  Cause:
  The primary cause of this error is a lack of appropriate authorizations assigned to the user trying to delete the back-end system. In SAP, actions such as deleting a back-end system require specific roles and permissions to ensure that only authorized personnel can make significant changes to the system landscape.
  Solution:
  To resolve this issue, you can take the following steps:
  
  
  Check User Authorizations:
  
  Verify the roles and authorizations assigned to the user who is attempting to delete the back-end system. You can do this by using transaction code SU01 to view the user profile.
  
  
  
  Assign Necessary Roles:
  
  If the user lacks the necessary authorizations, you will need to assign the appropriate roles that include permissions for managing back-end systems. This typically involves roles related to system administration or specific roles for managing the Enterprise Search.
  
  
  
  Consult with Security Administrator:
  
  If you do not have the authority to change user roles, contact your SAP security administrator or BASIS team. They can review the authorization issues and make the necessary adjustments.
  
  
  
  Review Authorization Objects:
  
  The specific authorization objects that may be relevant include:
  
  S_TCODE: for transaction codes
  S_USER_AUTH: for user authorizations
  S_RFC: for remote function calls
  
  
  Ensure that the user has the necessary authorizations for the actions they are trying to perform.
  
  
  
  Testing:
  
  After making changes to the user’s roles or authorizations, have the user log out and log back in to ensure that the new permissions take effect. Then, attempt to delete the back-end system again.
  
  
  
  Related Information:
  
  
  Transaction Codes:
  
  SU01: User Maintenance
  PFCG: Role Maintenance
  SU53: Display Authorization Check (to analyze authorization failures)
  
  
  
  Documentation:
  
  Refer to SAP documentation or help guides related to user authorizations and role management for more detailed information on how to manage user permissions effectively.
  
  
  
  SAP Notes:
  
  Check for any relevant SAP Notes that may address specific issues or provide additional guidance related to this error message.
  
  
  
  By following these steps, you should be able to resolve the authorization issue and successfully delete the back-end system if you have the appropriate permissions.