How To Fix ESH_ENG_CDSVAL_ES013 - Key field &1 is not from table &2, as the others

ESH_ENG_CDSVAL_ES013 - Overview

• Message type: E = Error

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

• Message number: 013

• Message text: Key field &1 is not from table &2, as the others

What causes this issue?

The search engine needs all key fields to come from the same data base
table; including the client field. This is not the case here. The first
key field are from data base table &V2&; key field &V1& is from another
table.

System Response

The system issues an error message and will not allow you to continue with this transaction until the error is resolved.

How to fix this error?

Remove element &V1& from the key definition in annotation
@ObjectModel.semanticKey. Check whether the field- if needed - can be
taken alternatively from table &V1&, as the other key field(s).
Mind that this is independently of how the view stack looks like - it is
the actual data base table which is decisive.

Procedure for System Administrators

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_ES013 - Key field &1 is not from table &2, as the others ?

  The SAP error message ESH_ENG_CDSVAL_ES013 indicates that there is an issue with the key field in a Core Data Services (CDS) view or a related entity. Specifically, the error message states that the key field specified (denoted as &1) is not from the table (denoted as &2) that is expected in the context of the operation being performed.
  
  Cause:
  
  Incorrect Key Field Definition: The key field specified in the CDS view or the data model is not correctly defined or does not belong to the expected table.
  Data Model Mismatch: There may be a mismatch between the data model and the actual database schema, where the key field is expected to be part of a specific table but is not.
  Join Conditions: If the CDS view involves joins, the key field may not be properly aligned with the tables being joined.
  
  Configuration Issues: There could be configuration issues in the CDS view or the underlying