How To Fix /ACCGO/FEE338 - No records found for the selection criteria

SAP Error Message - Details

• Message type: E = Error

• Message class: /ACCGO/FEE -

• Message number: 338

• Message text: No records found for the 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 /ACCGO/FEE338 - No records found for the selection criteria ?

  The SAP error message /ACCGO/FEE338 No records found for the selection criteria typically occurs in the context of financial accounting or related modules when a user attempts to retrieve data (such as fees, transactions, or other financial records) but the system does not find any records that match the specified selection criteria.
  Causes:
  
  Incorrect Selection Criteria: The parameters entered for the search (such as date range, account number, or other filters) may not match any existing records in the database.
  Data Not Yet Posted: The relevant transactions or records may not have been posted yet, leading to an absence of data for the specified criteria.
  Authorization Issues: The user may not have the necessary authorizations to view certain records, which could lead to the perception that no records exist.
  Data Deletion: Records may have been deleted or archived, making them unavailable for the current selection criteria.
  Configuration Issues: There may be issues with the configuration of the relevant module or application, leading to incorrect data retrieval.
  
  Solutions:
  
  Review Selection Criteria: Double-check the parameters you are using for the search. Ensure that the date range, account numbers, and other filters are correct and relevant.
  Check for Posted Transactions: Verify if the transactions you are looking for have been posted. If not, you may need to wait or check with the relevant team to ensure they are processed.
  Authorization Check: Ensure that you have the necessary permissions to view the records. If you suspect an authorization issue, contact your SAP security administrator.
  Consult with IT or SAP Support: If you suspect that records have been deleted or if there are configuration issues, consult with your IT department or SAP support team for further investigation.
  Use Broader Criteria: If possible, try using broader selection criteria to see if any records can be retrieved. This can help identify if the issue is with the specific criteria used.
  
  Related Information:
  
  Transaction Codes: Depending on the context, you may be using specific transaction codes related to financial reporting or data retrieval (e.g., FBL1N, FBL3N, etc.).
  SAP Notes: Check SAP Notes for any known issues or patches related to the error message. SAP frequently updates its knowledge base with solutions to common problems.
  Documentation: Refer to SAP documentation for the specific module you are working with to understand the expected behavior and data retrieval processes.
  
  If the issue persists after trying the above solutions, it may be beneficial to escalate the matter to your SAP support team for a deeper investigation.