In the DDLA source code of a CDS annotation definition delivered by SAP, the new annotation @CompatibilityContract must be used to specify the usability of the annotation in CDS entities, depending on their release contract.

Modification 5

New Scope for Annotations

In a CDS annotation definition, the new enumeration symbol #ENTITY, which defines a scope for entity annotations, can be specified after the annotation @scope. Annotations with this scope can be specified in the definitions of all CDS entities in front of the statement DEFINE.

The ABAP annotations @EndUserText.label and @Metadata.allowExtensions were switched to this scope.

Modification 6

Abstract CDS Entities

An abstract CDS entity defines the type attributes of a CDS entity without creating an instance of a database object. An abstract CDS entity is defined using DEFINE ABSTRACT ENTITY in a CDS data definition.

Modification 7

Metadata Extensions for CDS Entities

The variant ANNOTATE ENTITY was added to the previous statement ANNOTATE VIEW. This makes it possible to define CDS metadata extensions for any CDS entities with the exception of CDS table functions. Metadata extensions of this type can contain entity annotations, parameter annotations, and element annotations.

Modification 8

Access Control

The following enhancements have been implemented in CDS access control:

New Boolean predicates TRUE and FALSE can now be used as part of an access condition.
New inheritance conditions can be used as access conditions in CDS roles. They make the previous inherited access rules obsolete. Some inheritance conditions apply conditions from existing CDS roles and some inheritance conditions apply access rules defined for other CDS entities.
In a PFCG condition, a PFCG mapping can be mapped to an element list. This mapping assigns the CDS elements to the authorization fields of an authorization object. A PFCG mapping is defined in a CDS access policy using DEFINE PFCG_MAPPING.