How To Fix ESH_BOS_INDEX_CTRL058 - Logical system &1 or object type &2 is empty

SAP Error Message - Details

• Message type: E = Error

• Message class: ESH_BOS_INDEX_CTRL - Trex Inderxing on the ES Hub

• Message number: 058

• Message text: Logical system &1 or object type &2 is empty

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_BOS_INDEX_CTRL058 - Logical system &1 or object type &2 is empty ?

  The SAP error message ESH_BOS_INDEX_CTRL058 indicates that there is an issue with the logical system or object type being empty in the context of the SAP Enterprise Search (SAP ESH) framework. This error typically arises during the configuration or execution of search-related functionalities, particularly when dealing with Business Object Search (BOS) indexing.
  Cause:
  
  Empty Logical System: The logical system identifier that is expected to be provided is missing or not properly configured.
  Empty Object Type: The object type that is supposed to be indexed or searched is not defined or is incorrectly specified.
  Configuration Issues: There may be issues in the configuration settings for the search or indexing process, leading to missing parameters.
  Data Issues: The data source or the objects that are supposed to be indexed may not be available or properly set up.
  
  Solution:
  
  
  Check Logical System Configuration:
  
  Go to the transaction code SCC4 to verify the logical system settings.
  Ensure that the logical system is correctly defined and active.
  
  
  
  Verify Object Type:
  
  Check the configuration for the object types in the SAP ESH settings.
  Ensure that the object types you are trying to index or search are correctly defined and not empty.
  
  
  
  Review Indexing Configuration:
  
  Navigate to the relevant configuration settings for the Business Object Search (BOS) in the SAP ESH.
  Ensure that all required parameters are filled in and that there are no missing entries.
  
  
  
  Check Data Sources:
  
  Ensure that the data sources from which the objects are being indexed are available and correctly configured.
  Use transaction SLG1 to check for any logs related to the indexing process that might provide more context on the error.
  
  
  
  Re-indexing:
  
  If the configuration appears correct, consider re-indexing the objects to refresh the index and resolve any inconsistencies.
  
  
  
  Consult Documentation:
  
  Refer to the SAP Help Portal or relevant SAP Notes for specific guidance related to the version of SAP you are using.
  
  
  
  Related Information:
  
  
  Transaction Codes: 
  
  SCC4: To check logical system settings.
  SLG1: To view application logs for errors.
  SE11: To check the data dictionary for object types.
  
  
  
  SAP Notes: Search for relevant SAP Notes that might address this specific error or provide additional troubleshooting steps.
  
  
  SAP Community: Engage with the SAP Community forums for insights from other users who may have encountered similar issues.
  
  
  By following these steps, you should be able to identify the root cause of the error and implement the necessary solutions to resolve it.