Do you have any question about this error?
Message type: E = Error
Message class: ESH_ENG_CDSVAL_ES - ES-CDS/ABAP: Validation of domain @EnterpriseSearch
Message number: 061
Message text: Sucessor &1 lacks @EnterpriseSearch-annotations
You have set a CDS-entity on API-state "deprecated" which carries an
@EnterpriseSearch.enabled-annotation. This CDS-entity does also have
successors. Successor &V1& does not have annotation
@EnterpriseSearch.enabled.
A CDS-entity which is not enabled for Enterprise Search cannot be a
semantically comparable successor of a CDS-entity which is enabled for
Enterprise Search. Hence, this successor is not possible.
Either the successor lacks the @EnterpriseSearch-annotations, or the
intended successor is not suitable at all.
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.
ESH_ENG_CDSVAL_ES061
- Sucessor &1 lacks @EnterpriseSearch-annotations ?The SAP error message ESH_ENG_CDSVAL_ES061 indicates that a successor entity in a Core Data Services (CDS) view lacks the necessary
@EnterpriseSearch
annotations. This error typically arises in the context of SAP Enterprise Search, where the system expects certain annotations to be present for the entities involved in the search.Cause:
The error occurs when:
- A CDS view or entity that is expected to be part of the Enterprise Search configuration does not have the required annotations.
- The annotations are necessary for the system to understand how to index and search the data properly.
Solution:
To resolve this error, you need to ensure that the successor entity has the appropriate
@EnterpriseSearch
annotations. Here are the steps to do this:
Identify the Successor Entity: Determine which entity is being referenced in the error message (the
&1
placeholder will be replaced with the actual entity name).Add Annotations: Open the CDS view definition in the ABAP Development Tools (ADT) or the relevant development environment. Add the necessary
@EnterpriseSearch
annotations to the successor entity. Common annotations include:
@Search.searchable
: Marks the field as searchable.@Search.defaultSearch
: Indicates the default search field.@Search.result
: Specifies how the field should be displayed in search results.Example:
define view ZMy_CDS_View as select from my_table { key field1, field2, @Search.searchable: true field3 }
Activate the CDS View: After adding the annotations, activate the CDS view to ensure that the changes take effect.
Re-index the Search: If necessary, re-index the search to ensure that the changes are reflected in the search results.
Test the Search: After making the changes, test the Enterprise Search functionality to confirm that the error has been resolved.
Related Information:
By following these steps, you should be able to resolve the ESH_ENG_CDSVAL_ES061 error and ensure that your CDS views are properly configured for Enterprise Search.
Get instant SAP help. Start your 7-day free trial now.
ESH_ENG_CDSVAL_ES060
View is deprecated: no ES-Connector will be generated!
What causes this issue? The view has been set as deprecated.System Response While the view still can be used as a Transient Connector, i.e. the sear...
ESH_ENG_CDSVAL_ES059
Test search error: &1
What causes this issue? To finally validate whether the view can be processed by the Enterprise Search-API, some test searches are carried out on the...
ESH_ENG_CDSVAL_ES062
DDL w/o @EnterpriseSearch must not be succeeded by one with this anno
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
ESH_ENG_CDSVAL_ES063
Fatal DDIC-inconsistency
What causes this issue? The DDL with the definition of the CDS-entity contains elements which are not present in the SQL-view generated from this CDS...
Click on this link to search all SAP messages.