How To Fix ESH_ENG_CDSVAL_ES056 - 'configurationSet' &1 does not exist (&2)

ESH_ENG_CDSVAL_ES056 - Overview

• Message type: E = Error

• Message class: ESH_ENG_CDSVAL_ES - ES-CDS/ABAP: Validation of domain @EnterpriseSearch

• Message number: 056

• Message text: 'configurationSet' &1 does not exist (&2)

What causes this issue?

Enterprise Search Configuration Set &V1& which is to be assigned to the
element via @EnterpriseSearch.configurationSet does not exist.

System Response

Enterprise Search Configuration Sets - in contrast to the CDS-definition
- are client-specific. Hence the situation may occur that a
Configuration Set exists in one client but not in another. Configuration
Sets not existing in the respective client will be ignored at search
runtime.

How to fix this error?

Check the Configuration Set for typographical errors, or remove the
annotation with the erroneous Configuration Set.
If the Configuration Set in question does exist, but in a different
client, or further up in the software component stack, nothing needs to
be done.

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_ENG_CDSVAL_ES056 - 'configurationSet' &1 does not exist (&2) ?

  The SAP error message ESH_ENG_CDSVAL_ES056 indicates that a specific configuration set does not exist in the system. This error typically arises in the context of SAP's Enterprise Search or when working with Core Data Services (CDS) views, particularly when trying to access or utilize a configuration that has not been defined or has been deleted.
  
  Cause:
  
  Missing Configuration Set: The configuration set referenced in the error message is not available in the system. This could be due to it never being created, being deleted, or being incorrectly referenced.
  Incorrect Naming: There might be a typo or incorrect naming in the configuration set being called.
  Transport Issues: If the configuration was transported from another system, it may not have been included in the transport request or may not have been activated properly.
  Authorization Issues: The user may not have the necessary authorizations to access the configuration set.
  
  
  Solution:
  
  Check Configuration Set: Verify if the configuration set exists in