How To Fix RSL_UTILITIES036 - Reading DataSource forbidden by user (DS: &1, logical system &2)

SAP Error Message - Details

• Message type: E = Error

• Message class: RSL_UTILITIES - Messages in Utilities Package

• Message number: 036

• Message text: Reading DataSource forbidden by user (DS: &1, logical system &2)

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 RSL_UTILITIES036 - Reading DataSource forbidden by user (DS: &1, logical system &2) ?

  The SAP error message RSL_UTILITIES036 indicates that a user is attempting to read data from a DataSource, but the action is forbidden due to insufficient authorizations. This typically occurs in the context of SAP BW (Business Warehouse) or SAP BI (Business Intelligence) when a user tries to access data from a DataSource that they do not have permission to access.
  
  Cause:
  The primary cause of this error is a lack of proper authorizations for the user trying to access the specified DataSource. This can happen due to:
  
  Missing Authorization Objects: The user may not have the necessary authorization objects assigned to their user profile.
  Role Assignment: The user may not be assigned to the correct roles that include access to the DataSource.
  DataSource Restrictions: The DataSource itself may have restrictions set up that prevent certain users or roles from accessing it.
  
  
  Solution:
  To resolve this error, you can follow these steps:
  
  
  Check User Authorizations:
  
  Use transaction code SU01 to