How To Fix ESH_DB015 - No non-CDS connectors have been created

SAP Error Message - Details

• Message type: E = Error

• Message class: ESH_DB - ES: Dashboard

• Message number: 015

• Message text: No non-CDS connectors have been created

What causes this issue?

CDS-based connectors are always available, without special configuration
steps. Other connectors - type "Common Runtime" - have to be created
individually per client.
Here, no connectors have yet been individually created, although there
is model content available. It can be assumed that "Common
Runtime"-connectors, too, are relevant in this system.

System Response

Searching is possible only for CDS-based connectors, which are always
present without manual activities.

How to fix this error?

If the system is meant to be run in a pure CDS-based mode, this is fine
and the warning can be ignored.
Use task list (transaction STC01) SAP_ESH_CREATE_INDEX_SC to create
connectors.
You can also start the ES-Cockpit (transaction ESH_COCKPIT), and there
manually create connectors.

Procedure for System Administrators

The system issues an error message and will not allow you to continue with this transaction until the error is resolved.

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message ESH_DB015 - No non-CDS connectors have been created ?

  The SAP error message ESH_DB015 indicates that no non-CDS (Core Data Services) connectors have been created in the Enterprise Search (ESH) configuration. This error typically arises when the system is unable to find the necessary connectors to access the data sources for the search functionality.
  Cause:
  
  Missing Connectors: The most common cause is that the required non-CDS connectors have not been created or activated in the ESH configuration.
  Configuration Issues: There may be issues with the configuration settings for the connectors, such as incorrect parameters or missing entries.
  Transport Issues: If the connectors were recently transported from another system, there may have been issues during the transport process that prevented them from being created properly.
  Authorization Issues: The user may not have the necessary authorizations to access or create the connectors.
  
  Solution:
  
  
  Create Non-CDS Connectors:
  
  Go to the ESH configuration in the SAP system (transaction code ESH_COCKPIT).
  Navigate to the "Connectors" section and check if the non-CDS connectors are listed.
  If they are missing, create the necessary connectors by following the appropriate steps in the ESH configuration guide.
  
  
  
  Check Configuration:
  
  Review the configuration settings for the connectors to ensure that all required parameters are correctly set.
  Make sure that the data sources are properly defined and accessible.
  
  
  
  Transport Check:
  
  If the connectors were transported, check the transport logs for any errors or warnings that may indicate issues during the transport process.
  Re-transport the connectors if necessary.
  
  
  
  Authorization Check:
  
  Ensure that the user has the necessary authorizations to create and manage connectors in the ESH configuration.
  Check the roles and authorizations assigned to the user.
  
  
  
  System Logs:
  
  Check the system logs (transaction code SLG1) for any additional error messages or warnings that may provide more context about the issue.
  
  
  
  Documentation and Support:
  
  Refer to the official SAP documentation for Enterprise Search for detailed steps on configuring connectors.
  If the issue persists, consider reaching out to SAP support for further assistance.
  
  
  
  Related Information:
  
  Enterprise Search (ESH): A feature in SAP that allows users to search across various data sources within the SAP landscape.
  Core Data Services (CDS): A framework for defining and consuming semantically rich data models in SAP applications.
  Transaction Codes: Familiarize yourself with relevant transaction codes such as EHS_COCKPIT for ESH configuration and SLG1 for log analysis.
  
  By following these steps, you should be able to resolve the ESH_DB015 error and ensure that the necessary connectors are in place for the Enterprise Search functionality to work correctly.