How To Fix ESH_DB064 - There are &1 CDS-entities that lack a connector

SAP Error Message - Details

• Message type: E = Error

• Message class: ESH_DB - ES: Dashboard

• Message number: 064

• Message text: There are &1 CDS-entities that lack a connector

What causes this issue?

CDS-entities slipped the obligatory activation for Enterprise Search.
Each CDS-entity relevant for Enterprise Search (i.e. with annotation
@EnterpriseSearch.enabled) must have a corresponding search connector;
which then might have an error status.

System Response

The CDS-entities are missing in all connector lists and are consequently
not available for search.

How to fix this error?

You can enforce the activation by running a complete activation e.g. via
task list SAP_ESH_CONFIGURATION/ step "Activate CDS views with
@EnterpriseSearch annotation" or from transaction ESH_DASHBOARD.

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_DB064 - There are &1 CDS-entities that lack a connector ?

  The SAP error message ESH_DB064 indicates that there are certain Core Data Services (CDS) entities in your system that do not have an associated connector. This can occur in the context of SAP's Enterprise Search or when working with the SAP HANA database, where CDS views are used to define data models.
  Cause:
  The error typically arises due to one of the following reasons:
  
  Missing Connector Configuration: The CDS entities are not properly configured with a connector that allows them to be accessed or utilized in the context of the Enterprise Search or other applications.
  Transport Issues: If the CDS entities were transported from another system, the necessary connector configurations may not have been included or activated in the target system.
  Development Errors: There may be issues in the development of the CDS views themselves, such as missing annotations or incorrect definitions that prevent the creation of a connector.
  
  Solution:
  To resolve the ESH_DB064 error, you can follow these steps:
  
  
  Check Connector Configuration:
  
  Go to the SAP Fiori Launchpad or the relevant transaction for managing connectors (e.g., transaction EHS_COCKPIT).
  Verify if the connectors for the affected CDS entities are defined and activated.
  
  
  
  Create or Activate Connectors:
  
  If connectors are missing, you may need to create them. This can typically be done through the SAP GUI or Fiori apps designed for managing search connectors.
  Ensure that the connectors are properly configured to point to the correct CDS entities.
  
  
  
  Review CDS Annotations:
  
  Check the annotations in the CDS views to ensure they are correctly defined. Look for any missing or incorrect annotations that might prevent the connector from being created.
  
  
  
  Transport Issues:
  
  If the issue arose after a transport, ensure that all necessary objects, including connectors, were included in the transport request.
  You may need to manually create or adjust connectors in the target system.
  
  
  
  Rebuild Indexes:
  
  After making changes, it may be necessary to rebuild the search indexes to ensure that the changes take effect.
  
  
  
  Consult Documentation:
  
  Refer to the official SAP documentation for Enterprise Search and CDS views for more detailed guidance on configuring connectors.
  
  
  
  Related Information:
  
  SAP Notes: Check for any relevant SAP Notes that might address this specific error or provide additional troubleshooting steps.
  SAP Community: Engage with the SAP Community forums to see if other users have encountered similar issues and what solutions they found effective.
  SAP Help Portal: Utilize the SAP Help Portal for detailed documentation on CDS views and Enterprise Search configurations.
  
  By following these steps, you should be able to identify the cause of the ESH_DB064 error and implement the necessary solutions to resolve it.