How To Fix ESH_QL_MSG138 - No authorization to delete public variants created by a different user

SAP Error Message - Details

• Message type: E = Error

• Message class: ESH_QL_MSG - ESH Query Logging

• Message number: 138

• Message text: No authorization to delete public variants created by a different user

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_QL_MSG138 - No authorization to delete public variants created by a different user ?

  The SAP error message ESH_QL_MSG138 indicates that a user is attempting to delete a public variant that was created by another user, and they do not have the necessary authorization to perform this action. This is a common issue in SAP systems where authorization roles and object permissions are strictly enforced.
  Cause:
  The error occurs because:
  
  The user does not have the required authorization to delete public variants created by other users.
  The authorization checks in SAP are designed to prevent unauthorized changes to objects that are shared across multiple users.
  
  Solution:
  To resolve this issue, you can take the following steps:
  
  
  Check User Authorizations:
  
  Verify the user's authorization roles to ensure they have the necessary permissions to delete public variants. This can be done by checking the user's profile in transaction SU01 or using transaction PFCG to review the roles assigned to the user.
  
  
  
  Modify Authorization Roles:
  
  If the user needs the ability to delete public variants created by others, you may need to modify their authorization roles. This typically involves adding the necessary authorization objects related to variant management, such as:
  
  S_PROGRAM (Authorization for programs)
  S_VARIANT (Authorization for variants)
  
  
  Ensure that the authorization object includes the appropriate activity (e.g., delete) and the relevant field values.
  
  
  
  Consult with Security Team:
  
  If you do not have the necessary permissions to change roles or authorizations, consult with your SAP security team or system administrator. They can help assess the situation and make the necessary changes.
  
  
  
  Use a Different User:
  
  If the deletion of the public variant is urgent and cannot wait for authorization changes, consider asking the user who created the variant to delete it themselves, or use a user account that has the required permissions.
  
  
  
  Documentation and Training:
  
  Ensure that users are aware of the authorization policies regarding public variants to prevent similar issues in the future. Providing training or documentation can help users understand their permissions and the implications of their actions.
  
  
  
  Related Information:
  
  Transaction Codes:
  
  SU01: User Maintenance
  PFCG: Role Maintenance
  SE93: Transaction Codes for Authorization Objects
  
  
  Authorization Objects:
  
  S_PROGRAM: Controls access to programs and transactions.
  S_VARIANT: Controls access to variants, including creation, modification, and deletion.
  
  
  SAP Notes: Check for any relevant SAP Notes that may provide additional guidance or updates related to this error message.
  
  By following these steps, you should be able to address the authorization issue and resolve the error message ESH_QL_MSG138.