How To Fix ESH_ENG_CDSVAL_ES003 - Annotation &1 is obsolete; use &2

ESH_ENG_CDSVAL_ES003 - Overview

• Message type: E = Error

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

• Message number: 003

• Message text: Annotation &1 is obsolete; use &2

What causes this issue?

Meanwhile, the semantics formerly expressed by annotation &V1& of domain
@EnterpriseSearch is available in a general, non-proprietary way as
annotation &V2&. The first one is now obsolete; the latter is to be
used.

System Response

The obsolete annotation is nevertheless evaluated and works as wont.
There is no immediate impact on the use of the view in form of an
Enterprise Search connector.

How to fix this error?

Replace the obsolete annotation by &V2&.

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_ES003 - Annotation &1 is obsolete; use &2 ?

  The SAP error message ESH_ENG_CDSVAL_ES003 indicates that a certain annotation in your Core Data Services (CDS) view is obsolete and suggests using an alternative annotation instead. This typically occurs when SAP has updated its data model or annotations, and the older ones are no longer supported.
  
  Cause:
  
  Obsolete Annotation: The annotation you are using in your CDS view has been marked as obsolete in the latest version of SAP.
  Version Mismatch: You may be using an older version of a CDS view or an outdated annotation that has been replaced in newer releases.
  SAP Notes: Sometimes, SAP releases notes that deprecate certain features or annotations, which can lead to this error if you are still using them.
  
  
  Solution:
  
  Update the Annotation: Replace the obsolete annotation with the recommended one as indicated in the error message. The message will specify the old annotation (&1) and the new one (&2) that you should use.
  Check Documentation: Refer to the