How To Fix /SMB/ATC_ERROR035 - You're not allowed to execute transaction &1

SAP Error Message - Details

• Message type: E = Error

• Message class: /SMB/ATC_ERROR -

• Message number: 035

• Message text: You're not allowed to execute transaction &1

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 /SMB/ATC_ERROR035 - You're not allowed to execute transaction &1 ?

  The SAP error message /SMB/ATC_ERROR035 You're not allowed to execute transaction &1 typically indicates that the user does not have the necessary authorizations to execute a specific transaction in the SAP system. This error is often encountered in the context of the SAP Application Lifecycle Management (ALM) tools, particularly when using the ABAP Test Cockpit (ATC) or similar tools.
  Cause:
  
  Authorization Issues: The user executing the transaction does not have the required authorization object or role assigned to their user profile.
  Transaction Restrictions: The transaction may be restricted based on user roles or profiles defined in the system.
  Configuration Settings: Certain configurations in the system may prevent specific users from executing certain transactions.
  
  Solution:
  
  
  Check User Authorizations:
  
  Use transaction SU53 immediately after encountering the error to check the authorization check that failed. This will provide insight into which authorization object is missing.
  Review the user's roles and profiles in transaction SU01 or PFCG to ensure that the necessary authorizations are included.
  
  
  
  Assign Missing Authorizations:
  
  If you identify missing authorizations, you may need to assign the appropriate roles or create a custom role that includes the necessary authorizations.
  Work with your SAP security team or administrator to ensure that the user has the correct access.
  
  
  
  Review Transaction Restrictions:
  
  Check if there are any specific restrictions on the transaction in question. This can be done by reviewing the transaction's configuration or any related security settings.
  
  
  
  Consult Documentation:
  
  Refer to SAP documentation or notes related to the specific transaction to understand any known issues or additional configuration that may be required.
  
  
  
  Testing:
  
  After making changes to user roles or authorizations, have the user log out and log back in to ensure that the changes take effect. Then, attempt to execute the transaction again.
  
  
  
  Related Information:
  
  
  Transaction Codes: Common transaction codes related to user management and authorization include:
  
  SU01 - User Maintenance
  PFCG - Role Maintenance
  SU53 - Display Authorization Check
  SUIM - User Information System
  
  
  
  Authorization Objects: Familiarize yourself with common authorization objects that may be relevant to the transaction in question. This can include objects like S_TCODE (Transaction Codes) and others specific to the functionality of the transaction.
  
  
  SAP Notes: Check SAP Notes for any specific issues or patches related to the error message or the transaction you are trying to execute.
  
  
  If the issue persists after following these steps, it may be beneficial to consult with your SAP Basis or security team for further assistance.