How To Fix ESH_CM_SYS_COUP_MSG058 - You are not authorized to delete system pair data

ESH_CM_SYS_COUP_MSG058 - Overview

• Message type: E = Error

• Message class: ESH_CM_SYS_COUP_MSG - Texts for Top Level Info Tagging

• Message number: 058

• Message text: You are not authorized to delete system pair data

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.

ESH_CM_SYS_COUP_MSG058 - Details

• The SAP error message ESH_CM_SYS_COUP_MSG058 indicates that a user is attempting to delete system pair data but does not have the necessary authorization to perform this action. This error typically arises in the context of SAP's Enterprise Search or related components where system pairs are used to manage connections between different systems.
  
  Cause:
  The primary cause of this error is a lack of appropriate authorizations assigned to the user trying to delete the system pair data. In SAP, authorization checks are performed to ensure that users have the necessary permissions to execute specific actions, such as deleting data.
  
  Solution:
  To resolve this issue, you can follow these steps:
  
  
  Check User Authorizations:
  
  Use transaction code SU53 immediately after encountering the error to see which authorization check failed. This will provide insight into what specific authorization is missing.
  
  
  
  Review Role Assignments:
  
  Check the roles assigned to the user in transaction SU01 (User Maintenance). Ensure that the user has the necessary