How To Fix SO2_TOOL035 - No display authorization

SAP Error Message - Details

• Message type: E = Error

• Message class: SO2_TOOL - Messages for OXYGEN Page Editor

• Message number: 035

• Message text: No display authorization

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 SO2_TOOL035 - No display authorization ?

  The SAP error message SO2_TOOL035, which indicates "No display authorization," typically occurs when a user attempts to access a transaction or report for which they do not have the necessary authorization to view the data. This can happen in various SAP modules, particularly in areas related to reporting and data display.
  Cause:
  
  Missing Authorization Object: The user lacks the required authorization object that grants access to the specific transaction or report.
  Role Assignment: The user’s role may not include the necessary permissions to view the data.
  Profile Issues: The user’s profile may not be correctly configured to include the necessary authorizations.
  Data Restrictions: There may be restrictions on the data that the user can access based on their organizational unit or other criteria.
  
  Solution:
  
  
  Check User Roles:
  
  Go to transaction SU01 (User Maintenance) and enter the user ID.
  Check the roles assigned to the user and ensure that the relevant role includes the necessary authorizations.
  
  
  
  Review Authorization Objects:
  
  Use transaction SU53 immediately after encountering the error to see which authorization check failed. This will provide insight into which specific authorization object is missing.
  If you have access, you can also use transaction SUIM (User Information System) to analyze user authorizations.
  
  
  
  Modify Roles:
  
  If you have the necessary permissions, you can modify the user’s roles using transaction PFCG (Profile Generator) to include the missing authorization objects.
  If you do not have the necessary permissions, contact your SAP security administrator to request the required changes.
  
  
  
  Testing:
  
  After making changes, have the user log out and log back in to ensure that the new authorizations take effect.
  Test the transaction or report again to confirm that the issue is resolved.
  
  
  
  Documentation:
  
  Document any changes made to user roles or authorizations for future reference and compliance.
  
  
  
  Related Information:
  
  Authorization Objects: These are the building blocks of SAP security and define what actions a user can perform on specific data.
  Transaction Codes:
  
  SU01: User Maintenance
  SU53: Display Authorization Check
  PFCG: Role Maintenance
  SUIM: User Information System
  
  
  SAP Security Best Practices: Regularly review user roles and authorizations to ensure compliance with security policies and to minimize the risk of unauthorized access.
  
  If the issue persists after following these steps, it may be necessary to consult with your SAP Basis or security team for further investigation.