How To Fix RSEC358 - The check for query &1 and user &2 was not executed

SAP Error Message - Details

• Message type: E = Error

• Message class: RSEC -

• Message number: 358

• Message text: The check for query &1 and user &2 was not executed

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 RSEC358 - The check for query &1 and user &2 was not executed ?

  The SAP error message RSEC358 indicates that the authorization check for a specific query and user was not executed. This typically occurs in the context of SAP BW (Business Warehouse) or SAP BI (Business Intelligence) when there are issues related to authorizations or the configuration of the query.
  
  Cause:
  
  Missing Authorizations: The user does not have the necessary authorizations to execute the query.
  Query Not Active: The query might not be active or properly configured in the system.
  Authorization Objects: The relevant authorization objects for the query might not be assigned to the user.
  Query Definition Issues: There may be issues with the query definition itself, such as missing InfoObjects or incorrect settings.
  User Role Issues: The user might not be assigned to the correct roles that include the necessary authorizations for the query.
  
  
  Solution:
  
  
  Check User Authorizations:
  
  Use transaction code SU53 to analyze the authorization check after the error occurs. This will show you which authorizations are missing.
  Ensure