How To Fix ESH_HANA_ADMIN139 - There are no customized table source schemata

SAP Error Message - Details

• Message type: E = Error

• Message class: ESH_HANA_ADMIN - ESH HANA Index Administration

• Message number: 139

• Message text: There are no customized table source schemata

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_HANA_ADMIN139 - There are no customized table source schemata ?

  The SAP error message ESH_HANA_ADMIN139 indicates that there are no customized table source schemata available in the system. This error typically arises in the context of SAP's Enterprise Search (ESH) when the system is trying to access or utilize custom table sources for search indexing or configuration.
  Cause:
  
  
  No Custom Schemas Defined: The most common cause of this error is that there are no custom schemas defined in the system for the Enterprise Search to utilize. This could happen if the configuration for custom sources has not been set up or if the necessary tables have not been created.
  
  
  Configuration Issues: There may be issues with the configuration of the Enterprise Search or the HANA database that prevent the system from recognizing any custom schemas.
  
  
  Missing Authorization: Sometimes, the user executing the operation may not have the necessary authorizations to access the custom schemas.
  
  
  Solution:
  
  
  Define Custom Schemas: 
  
  Go to the SAP HANA Studio or the relevant transaction in the SAP GUI.
  Define the necessary custom table source schemata. This involves creating the required tables and ensuring they are properly configured for use with Enterprise Search.
  
  
  
  Check Configuration: 
  
  Review the configuration settings for the Enterprise Search. Ensure that the custom sources are correctly set up and that the system is aware of them.
  You can check the settings in the transaction code EHS_ADMIN or similar configuration transactions.
  
  
  
  Authorization Check: 
  
  Ensure that the user has the necessary authorizations to access the custom schemas. You may need to consult with your security team to verify and adjust the roles and permissions.
  
  
  
  Re-indexing: 
  
  After defining the custom schemas, you may need to re-index the search to ensure that the new sources are included. This can typically be done through the Enterprise Search administration tools.
  
  
  
  Consult Documentation: 
  
  Refer to the official SAP documentation for Enterprise Search and HANA for detailed steps on setting up custom table sources and troubleshooting related issues.
  
  
  
  Related Information:
  
  SAP Notes: Check for any relevant SAP Notes that might address this specific error or provide additional troubleshooting steps.
  Community Forums: Engage with the SAP Community or forums where other users may have encountered similar issues and can provide insights or solutions.
  SAP Support: If the issue persists after trying the above solutions, consider reaching out to SAP Support for further assistance.
  
  By following these steps, you should be able to resolve the error message ESH_HANA_ADMIN139 and successfully configure your custom table source schemata.