How To Fix GI573 - An FI-SL document was not found based on the selection conditions

SAP Error Message - Details

• Message type: E = Error

• Message class: GI - FI-SL update

• Message number: 573

• Message text: An FI-SL document was not found based on the selection conditions

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 GI573 - An FI-SL document was not found based on the selection conditions ?

  The SAP error message GI573, which states "An FI-SL document was not found based on the selection conditions," typically occurs in the context of Financial Accounting (FI) and Special Ledger (FI-SL) when a user attempts to retrieve or process a document that does not exist or cannot be found based on the specified selection criteria.
  Causes:
  
  Incorrect Selection Criteria: The selection parameters (such as document number, company code, fiscal year, etc.) entered in the report or transaction may not match any existing FI-SL documents.
  Document Not Posted: The document you are trying to access may not have been posted yet or may have been deleted.
  Data Synchronization Issues: There may be issues with data synchronization between different modules or systems, leading to discrepancies in document availability.
  Authorization Issues: The user may not have the necessary authorizations to view the FI-SL documents.
  Configuration Issues: There may be configuration issues in the FI-SL setup that prevent the system from retrieving the documents correctly.
  
  Solutions:
  
  Check Selection Criteria: Review and verify the selection criteria you are using. Ensure that all fields are filled out correctly and that you are searching for the correct document.
  Verify Document Existence: Use transaction codes like FB03 (Display Document) or other relevant transactions to check if the document exists in the system.
  Check Authorizations: Ensure that the user has the necessary authorizations to access the FI-SL documents. This may involve checking user roles and permissions.
  Review Configuration: If you suspect a configuration issue, consult with your SAP FI consultant to review the settings related to FI-SL and ensure everything is set up correctly.
  Data Consistency Check: Run data consistency checks or reports to identify any discrepancies in the FI-SL data. This may involve using transaction codes like SARA or other relevant tools.
  Consult SAP Notes: Check the SAP Support Portal for any relevant SAP Notes that may address this specific error message or provide additional troubleshooting steps.
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as FB03 (Display Document), FBL1N (Vendor Line Item Display), FBL3N (G/L Account Line Item Display), and others that may help in verifying document existence.
  SAP Documentation: Refer to SAP Help documentation for detailed information on FI-SL and related processes.
  Support Community: Engage with the SAP Community or forums for additional insights and experiences from other users who may have encountered the same issue.
  
  If the problem persists after trying the above solutions, it may be necessary to involve your SAP support team or consult with SAP directly for further assistance.