How To Fix FE790 - No data was selected; authorizations may be lacking

SAP Error Message - Details

• Message type: E = Error

• Message class: FE - CO-PA module pool messages

• Message number: 790

• Message text: No data was selected; authorizations may be lacking

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 FE790 - No data was selected; authorizations may be lacking ?

  The SAP error message FE790 "No data was selected; authorizations may be lacking" typically indicates that the user does not have the necessary authorizations to access the data they are trying to view or manipulate. This can occur in various SAP transactions, especially when dealing with reports, data extraction, or any functionality that requires specific permissions.
  Cause:
  
  Lack of Authorizations: The user may not have the required roles or authorizations assigned to their user profile to access the specific data or transaction.
  Data Selection Criteria: The selection criteria used in the transaction may not match any data available to the user due to restrictions in their authorization profile.
  Data Visibility Restrictions: Certain data may be restricted based on organizational units, company codes, or other criteria that the user does not have access to.
  User Role Configuration: The roles assigned to the user may not include the necessary authorizations for the specific transaction or data set.
  
  Solution:
  
  
  Check User Authorizations:
  
  Review the user's roles and authorizations using transaction code SU53 immediately after encountering the error. This transaction shows the last authorization check and can help identify which authorization is missing.
  Use transaction code PFCG to review and modify roles if necessary.
  
  
  
  Consult with Security Team:
  
  If you do not have the necessary permissions to change roles, contact your SAP security or basis team to request the required authorizations.
  
  
  
  Adjust Selection Criteria:
  
  Ensure that the selection criteria used in the transaction are correct and that they align with the data the user is authorized to access.
  
  
  
  Testing with Different User:
  
  If possible, test the same transaction with a user who has the necessary authorizations to confirm whether the issue is indeed related to authorization.
  
  
  
  Review Data Access Policies:
  
  Check if there are any specific data access policies or restrictions in place that might be affecting the user's ability to see the data.
  
  
  
  Related Information:
  
  
  Transaction Codes:
  
  SU53: Display Authorization Check
  PFCG: Role Maintenance
  SU01: User Maintenance (to check user roles)
  
  
  
  Authorization Objects: Familiarize yourself with the relevant authorization objects that may be required for the transaction in question. Common objects include S_TCODE (Transaction Codes), S_USER_AUTH (User Authorizations), and others specific to the module being accessed.
  
  
  Documentation: Refer to SAP documentation or your organization's internal documentation for specific roles and authorizations related to the transactions you are working with.
  
  
  By following these steps, you should be able to identify the cause of the error and take appropriate action to resolve it.