How To Fix GLE_UI_ADB038 - No source accounts were found for the source selection criteria

SAP Error Message - Details

• Message type: E = Error

• Message class: GLE_UI_ADB - Average Daily Balance UI: Messages

• Message number: 038

• Message text: No source accounts were found for the source selection criteria

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 GLE_UI_ADB038 - No source accounts were found for the source selection criteria ?

  The SAP error message GLE_UI_ADB038: No source accounts were found for the source selection criteria typically occurs in the context of financial accounting or during the execution of certain reports or transactions that require the selection of source accounts. This error indicates that the system could not find any accounts that match the criteria specified in your selection parameters.
  Causes:
  
  Incorrect Selection Criteria: The criteria you have entered (such as account range, company code, fiscal year, etc.) may not match any existing accounts in the system.
  Missing Accounts: The accounts you are trying to access may not exist in the specified company code or chart of accounts.
  Authorization Issues: You may not have the necessary authorizations to view certain accounts.
  Data Consistency Issues: There may be inconsistencies in the data, such as missing master data or configuration issues.
  Filters Applied: There may be filters applied in the report or transaction that are too restrictive.
  
  Solutions:
  
  Review Selection Criteria: Double-check the selection criteria you have entered. Ensure that the account range, company code, and other parameters are correct and that they correspond to existing accounts.
  Check Account Existence: Verify that the accounts you are trying to access actually exist in the system. You can do this by navigating to the relevant account master data.
  Adjust Filters: If you are using a report or transaction with filters, try removing or adjusting them to see if that resolves the issue.
  Authorization Check: Ensure that you have the necessary authorizations to access the accounts in question. You may need to contact your system administrator for assistance.
  Consult with IT Support: If the issue persists, it may be necessary to consult with your IT support team or SAP Basis team to check for any underlying data consistency issues or configuration problems.
  
  Related Information:
  
  Transaction Codes: Depending on the context, you may be using transaction codes like FBL1N (Vendor Line Item Display), FBL3N (G/L Account Line Item Display), or others related to financial reporting.
  SAP Notes: Check the SAP Support Portal for any relevant SAP Notes that may address this specific error or provide additional troubleshooting steps.
  Documentation: Review SAP documentation related to financial accounting and reporting for further insights into the selection criteria and account management.
  
  By following these steps, you should be able to identify the cause of the error and implement a solution. If the problem continues, further investigation into the system configuration and data may be necessary.