How To Fix ESH_BI_CONTENT_GEN021 - No BI DataSources available for updating the ESH repository

SAP Error Message - Details

• Message type: E = Error

• Message class: ESH_BI_CONTENT_GEN - Messeges for BI content generation

• Message number: 021

• Message text: No BI DataSources available for updating the ESH repository

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_BI_CONTENT_GEN021 - No BI DataSources available for updating the ESH repository ?

  The SAP error message ESH_BI_CONTENT_GEN021 indicates that there are no Business Intelligence (BI) DataSources available for updating the Enterprise Search Hub (ESH) repository. This error typically arises when the system is unable to find the necessary DataSources that are required to populate the ESH with relevant data.
  Causes:
  
  Missing DataSources: The most common cause is that the required BI DataSources have not been created or activated in the system.
  Incorrect Configuration: The configuration settings for the ESH or the BI DataSources may be incorrect or incomplete.
  Authorization Issues: The user may not have the necessary authorizations to access the BI DataSources.
  Technical Issues: There may be technical issues with the BI system or the connection between the BI system and the ESH.
  
  Solutions:
  
  
  Check DataSources:
  
  Go to the SAP BW system and verify that the required BI DataSources are created and activated.
  Use transaction codes like RSA1 to check the DataSources in the Data Warehousing Workbench.
  
  
  
  Configure ESH:
  
  Ensure that the ESH is properly configured to recognize the available BI DataSources. This can be done in the ESH configuration settings.
  Use transaction code EHS_CONFIG to check the configuration settings.
  
  
  
  Check Authorizations:
  
  Verify that the user has the necessary authorizations to access the BI DataSources. This can be done by checking the user roles and authorizations in the SAP system.
  
  
  
  Check Connections:
  
  Ensure that the connection between the ESH and the BI system is properly set up and functioning. You can check this in the RFC connections (transaction code SM59).
  
  
  
  Update ESH:
  
  If the DataSources are available and configured correctly, try to manually update the ESH repository using transaction code EHS_UPDATE.
  
  
  
  Consult Logs:
  
  Check the application logs for any additional error messages or warnings that might provide more context about the issue. You can use transaction code SLG1 to view the logs.
  
  
  
  Related Information:
  
  Documentation: Refer to the official SAP documentation for ESH and BI DataSources for detailed configuration steps and best practices.
  SAP Notes: Check the SAP Support Portal for any relevant SAP Notes that might address known issues related to this error message.
  Community Forums: Engage with the SAP Community or 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.