Get Example source ABAP code based on a different SAP table
ABAP_CDS - Table Buffering of CDS DDIC-Based Views The following CDS annotations can define table buffering for a CDS view linked with a ABAP_CDS_MNG_VIEW :
@AbapCatalog.buffering.status defines whether and how table buffering is allowed.
@AbapCatalog.buffering.type determines the buffering type.
@AbapCatalog.buffering.numberOfKeyFields determines the number of key fields covered if generic buffering is used. Table buffering of CDS views is done for the associated ABAP_CDS_MNG_VIEW and the same prerequisites apply as for DDIC database views in ABAP Dictionary. To meet these prerequisites, a CDS view can only be buffered if the following applies:
It cannot contain any views BEGIN_SECTION VERSION 5 OUT (DDIC database views or CDS views) END_SECTION VERSION 5 OUT and no CDS table functions as data sources.
It cannot have any input parameters.
A client-dependent view can use $session.client as the only session variable and must use it directly. This also allows the annotation @ClientHandling.algorithm:#SESSION_VARIABLE to be specified to determine client handling. A client-independent view must not use any session variables.
Key fields cannot contain null values.
The required key fields must be listed directly in the SELECT list. Key fields that only occur as arguments of expressions cannot be evaluated.
