How To Fix CFD_REGISTRY_CHECK121 - On clause of Association &1 in CDS View &2 contains not only elements

CFD_REGISTRY_CHECK121 - Overview

• Message type: E = Error

• Message class: CFD_REGISTRY_CHECK - Custom Fields: Messages for Registry Check

• Message number: 121

• Message text: On clause of Association &1 in CDS View &2 contains not only elements

What causes this issue?

In the on condition of the association you use $projections fields which
are calculated. This is currently not possible as such associations
cannot be used in view extensions and will lead to syntax errors
(General CDS restriction).

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?

Instead of using $projections fields which are calculated you have to
use the fields from the underlying data source.

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 CFD_REGISTRY_CHECK121 - On clause of Association &1 in CDS View &2 contains not only elements ?

  The SAP error message CFD_REGISTRY_CHECK121 indicates that there is an issue with the definition of an association in a Core Data Services (CDS) view. Specifically, the error message states that the "On clause of Association &1 in CDS View &2 contains not only elements." This typically means that the ON clause of the association is incorrectly defined, possibly including non-element expressions or conditions that are not valid for an association.
  
  Cause:
  
  Incorrect ON Clause: The ON clause of the association may include conditions that are not based solely on the fields of the associated entities. For example, it might include calculations, functions, or other non-element expressions.
  Syntax Errors: There may be syntax errors or misconfigurations in the CDS view definition that lead to this error.
  Incompatible Data Types: The fields used in the ON clause may have incompatible data types or may not match the expected types for the association.
  
  
  Solution:
  
  
  Review the ON Clause: Check