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: 066
Message text: DDIC-type of element &1 does not fit to ConfigurationSet IDSEARCH
The configuration set IDSEARCH - annotated via
@EnterpriseSearch.configurationSet at element &V1& - can be used only
with elements of types CHAR and NUMC which do not have a fulltext index.
The system issues an error message and will not allow you to continue with this transaction until the error is resolved.
The CDS-entity cannot be activated for Enterprise Search.
Remove the annotation.
Error message extract from SAP system. Copyright SAP SE.
ESH_ENG_CDSVAL_ES066
- DDIC-type of element &1 does not fit to ConfigurationSet IDSEARCH ?The SAP error message
ESH_ENG_CDSVAL_ES066
indicates that there is a mismatch between the data type of a field in a Core Data Services (CDS) view and the expected data type for a specific configuration set, in this case,IDSEARCH
. This error typically arises in the context of SAP's Enterprise Search or when working with CDS views that are used for search functionalities.Cause:
- Data Type Mismatch: The field defined in the CDS view has a different data type than what is expected by the configuration set
IDSEARCH
. This could be due to changes in the underlying data model or incorrect definitions in the CDS view.- Configuration Issues: The configuration for the search might not be aligned with the data model, leading to inconsistencies.
- Changes in Data Dictionary (DDIC): If there have been recent changes to the data dictionary elements that are not reflected in the CDS view, this can lead to such errors.
Solution:
- Check Data Types: Review the data types of the fields in the CDS view and compare them with the expected data types for the
IDSEARCH
configuration set. Ensure that they match.- Adjust CDS View: If there is a mismatch, you may need to adjust the CDS view definition to ensure that the data types align with what is expected.
- Update Configuration: If the configuration for
IDSEARCH
is incorrect, update it to reflect the correct data types and structures.- Re-activate the CDS View: After making changes, re-activate the CDS view to ensure that the changes take effect.
- Check for Transport Issues: If this issue arose after a transport, ensure that all related objects were transported correctly and that there are no missing dependencies.
Related Information:
If the issue persists after following these steps, consider reaching out to SAP support for further assistance, providing them with detailed information about the error and the context in which it occurs.
Get instant SAP help. Start your 7-day free trial now.
ESH_ENG_CDSVAL_ES065
Sensitive data must not be used in search (&1)
What causes this issue? Element &V1& is annotated with @AccessControl.readAccess.logging.logdomain.domain or with @AccessControl.readAccess.l...
ESH_ENG_CDSVAL_ES064
&1 is a shared multi-tenancy table - cannot be used (&2)
What causes this issue? Table &V1& is shared in a multi-tenant installation; this means that shared parts of the table are kept centrally, wh...
ESH_ENG_CDSVAL_SRCH000
CDS-domain @Search
What causes this issue? CDS: Checks on annotations of domain @SearchSystem Response The system issues an error message and will not allow you to con...
ESH_ENG_CDSVAL_SRCH001
At least one element has to be set as 'defaultSearchElement'
What causes this issue? The view is defined as searchable by annotation @Search.searchable, but none of its elements is annotated as relevant for a f...
Click on this link to search all SAP messages.