How To Fix GU538 - Neither summary records nor line items were selected

SAP Error Message - Details

• Message type: E = Error

• Message class: GU - FI-SL utilities

• Message number: 538

• Message text: Neither summary records nor line items were selected

What causes this issue?

Neither summary records nor line items were selected for the selection
criteria of this report. Thus the statement is meaningless: summary
records match the totals of the line items.

System Response

How to fix this error?

Make your selection criteria for the selected ledger more general so
that the data needed for the reconciliation is selected.

Procedure for System Administrators

The system issues an error message and will not allow you to continue with this transaction until the error is resolved.

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message GU538 - Neither summary records nor line items were selected ?

  The SAP error message GU538, which states "Neither summary records nor line items were selected," typically occurs during the execution of a report or transaction that requires data selection, such as when generating a report for financial documents or when trying to display line items in a certain context.
  Cause:
  
  
  No Data Available: The most common cause of this error is that there are no records available that meet the selection criteria specified in the report or transaction. This could be due to:
  
  Incorrect selection criteria (e.g., date range, document type).
  No transactions recorded in the specified period.
  Filters applied that exclude all records.
  
  
  
  Authorization Issues: Sometimes, the user may not have the necessary authorizations to view the data, leading to the appearance that no records are available.
  
  
  Technical Issues: There could be underlying technical issues, such as problems with the database or the report itself.
  
  
  Solution:
  
  
  Check Selection Criteria: Review the selection criteria you have entered. Ensure that:
  
  The date range is correct and includes periods where transactions exist.
  The document types and other filters are set correctly.
  
  
  
  Verify Data Availability: Check if there are any records in the database that match your criteria. You can do this by running a more general report or querying the database directly.
  
  
  Authorization Check: Ensure that you have the necessary authorizations to view the data. You may need to contact your SAP security team to verify your access rights.
  
  
  Technical Support: If the above steps do not resolve the issue, consider reaching out to your SAP support team or technical team to investigate any potential technical issues with the report or the underlying data.
  
  
  Related Information:
  
  Transaction Codes: Depending on the context, you might be using transaction codes like FBL1N (Vendor Line Item Display), FBL3N (G/L Account Line Item Display), or others that deal with financial reporting.
  SAP Notes: Check SAP Notes for any known issues related to the specific transaction or report you are using. Sometimes, SAP releases patches or notes that address specific error messages.
  Documentation: Review the documentation for the specific report or transaction to understand the expected input and output, as well as any prerequisites.
  
  By following these steps, you should be able to identify the cause of the GU538 error and take appropriate action to resolve it.