How To Fix ESH_ENG_CDSVAL_ES065 - Sensitive data must not be used in search (&1)

ESH_ENG_CDSVAL_ES065 - Overview

• Message type: E = Error

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

• Message number: 065

• Message text: 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.logging.output. This signifies that the data
is sensitive.

System Response

In order not to risk exposing sensitive data in search - which may
happen either directly as a response attribute, or indirectly as a means
to narrow down the search result - the respective element is not
considered.

How to fix this error?

No action needs to be taken. If you want to have the data in question in
search nevertheless, the annotation has to be removed. It is up to the
customer to weigh the search features against security considerations.

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.

ESH_ENG_CDSVAL_ES065 - Details

• The SAP error message ESH_ENG_CDSVAL_ES065 indicates that sensitive data is being used in a search operation, which is not allowed due to security and compliance reasons. This error typically arises in the context of SAP's Enterprise Search or when using Core Data Services (CDS) views that involve sensitive information.
  
  Cause:
  The error occurs when a search query attempts to access or utilize fields that are classified as sensitive data. Sensitive data can include personal information, financial data, or any other information that is subject to strict data protection regulations (e.g., GDPR, HIPAA). The system is designed to prevent such data from being exposed in search results to protect user privacy and comply with legal requirements.
  
  Solution:
  To resolve this error, you can take the following steps:
  
  
  Review the Search Query: Check the search query or the parameters being used in the search operation. Identify if any fields that are classified as sensitive data are being