How To Fix ESH_FL_MSG073 - No documents found

SAP Error Message - Details

• Message type: E = Error

• Message class: ESH_FL_MSG - File Processing

• Message number: 073

• Message text: No documents found

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 ESH_FL_MSG073 - No documents found ?

  The SAP error message ESH_FL_MSG073: No documents found typically occurs in the context of the SAP Enterprise Search or SAP Fiori applications when a search query does not return any results. This can happen for various reasons, and understanding the cause is essential for troubleshooting and resolving the issue.
  Causes:
  
  No Indexed Data: The most common reason for this error is that there are no documents indexed in the search system that match the search criteria.
  Search Configuration Issues: The search configuration might not be set up correctly, leading to no results being returned.
  Authorization Issues: The user may not have the necessary authorizations to view the documents that are indexed.
  Search Query Issues: The search query itself may be too restrictive or incorrectly formulated, leading to no matches.
  Data Synchronization Issues: There may be a delay or failure in the synchronization process between the source data and the search index.
  Technical Issues: There could be underlying technical issues with the search engine or the database.
  
  Solutions:
  
  
  Check Indexed Data:
  
  Verify that the data you are searching for is indeed indexed. You can do this by checking the indexing status in the SAP system.
  If necessary, re-index the data to ensure that all relevant documents are included.
  
  
  
  Review Search Configuration:
  
  Ensure that the search configuration is set up correctly. This includes checking the search connectors and ensuring they are active and properly configured.
  
  
  
  Check User Authorizations:
  
  Review the user roles and authorizations to ensure that the user has access to the documents being searched for.
  
  
  
  Modify Search Query:
  
  Try modifying the search query to be less restrictive. Use broader search terms or different filters to see if results can be retrieved.
  
  
  
  Data Synchronization:
  
  Check the synchronization process between the source data and the search index. Ensure that it is running correctly and that there are no errors in the logs.
  
  
  
  Technical Troubleshooting:
  
  If the above steps do not resolve the issue, consider checking the system logs for any errors related to the search functionality.
  Consult with your SAP Basis team to ensure that the search engine and database are functioning correctly.
  
  
  
  Related Information:
  
  SAP Notes: Check SAP Notes for any known issues or patches related to the search functionality.
  Documentation: Refer to the official SAP documentation for Enterprise Search or Fiori for detailed configuration and troubleshooting steps.
  Community Forums: Engage with the SAP Community or forums for additional insights and solutions from other users who may have encountered similar issues.
  
  By following these steps, you should be able to identify the cause of the error and implement a solution to resolve it.