How To Fix RSO_RES_ADSO070 - You are not authorized to display DataStore object '&1'

SAP Error Message - Details

• Message type: E = Error

• Message class: RSO_RES_ADSO - Datastore Object

• Message number: 070

• Message text: You are not authorized to display DataStore object '&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 RSO_RES_ADSO070 - You are not authorized to display DataStore object '&1' ?

  The SAP error message RSO_RES_ADSO070 indicates that a user is not authorized to display a specific DataStore Object (DSO) in SAP BW/4HANA or SAP BW on HANA. This error typically arises when a user attempts to access a DSO for which they do not have the necessary authorizations.
  Cause:
  
  Authorization Issues: The user does not have the required authorizations to access the specified DataStore Object. This could be due to missing roles or authorizations in the user's profile.
  Role Assignment: The roles assigned to the user may not include the necessary permissions for the specific DSO.
  Object-Specific Restrictions: There may be specific restrictions set on the DSO that limit access to certain users or groups.
  
  Solution:
  
  
  Check User Authorizations:
  
  Use transaction code SU53 immediately after encountering the error to see which authorization checks failed. This will provide insight into what specific authorizations are missing.
  Review the user's roles and authorizations in transaction code SU01 or PFCG.
  
  
  
  Assign Necessary Roles:
  
  If the user lacks the necessary roles, you may need to assign them roles that include access to the DSO. This can be done through transaction PFCG where you can manage roles and authorizations.
  Ensure that the roles assigned to the user include the necessary authorization objects for accessing the DSO.
  
  
  
  Modify Authorization Objects:
  
  If the roles are correct but the user still cannot access the DSO, check the authorization objects associated with the DSO. You may need to modify these objects to grant the necessary access.
  
  
  
  Consult with Security Team:
  
  If you are not authorized to make changes to roles or authorizations, consult with your SAP security team or administrator. They can help identify and resolve authorization issues.
  
  
  
  Testing:
  
  After making changes, have the user log out and log back in to ensure that the new authorizations take effect. Test access to the DSO again to confirm that the issue is resolved.
  
  
  
  Related Information:
  
  Authorization Objects: Common authorization objects related to DataStore Objects include S_BI_WAA (for BW authorizations) and S_BI_OA (for object access).
  Transaction Codes:
  
  SU01: User Maintenance
  PFCG: Role Maintenance
  SU53: Display Authorization Check
  
  
  Documentation: Refer to SAP Help documentation for detailed information on authorization management in SAP BW/4HANA.
  
  By following these steps, you should be able to resolve the authorization issue related to the RSO_RES_ADSO070 error message.