Define Time Characteristic

Field with data type DATS will be generated with base characteristic 0Calday
Use annotation @Semantics.calendar.* or @Semantics.fiscal.* to define fields as time characteristics

Important points to know:

Multiple fields in a CDS view can have the same time semantic
There is no dependency between different time fields by default
With annotation @ObjectModel.value.derivedFrom: '<field name>', the time fields can be defined with dependency
To use Time Hierarchy, see Note 2289865 → Section: Configuration of Hierarchies for Time Characteristics (optional)
See also Virtual Time Hierarchies
The long timestamp (data type TIMESTAMPL) field is not supported. The field is ignored. (Note 2737769, 2887459 )
In a query built on a CDS provider, time fields (defined in the way as listed above) will be always sorted by key no matter what is the display format.