How To Fix SADL_GW_DT_CDS086 - &1: Element &2 is typed incorrectly for this annotation

SADL_GW_DT_CDS086 - Overview

• Message type: E = Error

• Message class: SADL_GW_DT_CDS - Messages CDS Checks

• Message number: 086

• Message text: &1: Element &2 is typed incorrectly for this annotation

What causes this issue?

The field must have a suitable underlying type for the following
annotations: @Semantics.dateTime and @Semantics.uuid

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?

For @Semantics.dateTime:
You should use data elements which have domains similar to TZNTSTMPL,
TZNTSTMPS or TIMESTAMP.
You may also do a CAST in the CDS view to the appropriate types: DEC(21
,7), DEC(15,0) or CHAR(14)
For @Semantics.uuid
You should use data elements which have domains similar to SYSUUID_X16,
SYSUUID_C22 or SYSUUID_C32.
You may also do a CAST in the CDS view to the appropriate types: RAW16,
CHAR(22) or CHAR(32)

Procedure for System Administrators

Error message extract from SAP system. Copyright SAP SE.

SADL_GW_DT_CDS086 - Details

• The SAP error message SADL_GW_DT_CDS086 typically indicates that there is a type mismatch in the annotations of a Core Data Services (CDS) view or entity. This error often arises when the data type of an element does not match the expected type defined in the annotation.
  
  Cause:
  
  
  Type Mismatch: The element specified in the error message (&2) is defined with a data type that does not align with what is expected by the annotation. This could be due to:
  
  Incorrectly defined data types in the CDS view.
  Annotations that expect a specific type (e.g., string, integer, date) but are receiving a different type.
  Changes in the underlying data model that have not been reflected in the CDS definition.
  
  
  
  Annotation Misconfiguration: The annotation itself may be incorrectly configured, leading to the system expecting a different type than what is provided.
  
  
  
  Solution:
  
  
  Check the CDS View Definition:
  
  Review the definition of the CDS view where the error occurs. Ensure that the