Get Example source ABAP code based on a different SAP table
ABAP_CDS in ABAP Release 7.53 ITOC
ABAP_MODIFICATION_NN CDS Hierarchies>
The new statement DEFINE HIERARCHY >> can be used to create CDS hierarchies> that are accessed as hierarchies> in AB-SQL > read statements.
ABAP_MODIFICATION_NN New Condition IS INITIAL>>
The new condition IS INITIAL>> can be used to check the initial value of operands.
ABAP_MODIFICATION_NN Literals>
A literal> of a respective value is now always handled as a field of the type INT8>, including in the definition of associations.
ABAP_MODIFICATION_NN Annotation Definitions>
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>.
ABAP_MODIFICATION_NN 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.
ABAP_MODIFICATION_NN CDS Abstract Entities>
An CDS abstract entity> defines the type properties 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>.
ABAP_MODIFICATION_NN 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.
ABAP_MODIFICATION_NN 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>>.