Ansicht
Dokumentation

ABENCDS_V2_VIEW_PUFFERING - CDS V2 VIEW PUFFERING

General Material Data   TXBHW - Original Tax Base Amount in Local Currency  
This documentation is copyright by SAP AG.

- Table Buffering of CDS View Entities

The following CDS annotation defines, whether table buffering is allowed for a CDS view entity or not:

@AbapCatalog.entityBuffer.definitionAllowed: true$|false

If buffering is allowed, the actual buffering type can be defined by a separate CDS tuning object called CDS entity buffer with the DDL statement:

DEFINE VIEW ENTITY BUFFER ON cds_view_entity ...

The CDS entity buffer relates the buffering type to one of the layers core, localization, industry, partner and customer. For each layer, one buffering type can be defined for a CDS view entity.

If the @AbapCatalog.entityBuffer.definitionAllowed is set to true, the following restrictions apply to the CDS view entity:

• Only DDIC database tables are allowed as data sources.

• There must be at least one key element and the combined length of the key elements must not be greater than 900 bytes. Key elements cannot be LOBs.

• No input parameters are allowed.

• No calculations are allowed that have results that do not depend on database content only, as e.g. time stamp functions that return or depend on the current time stamp.

• No session variables other than $session.client are allowed.

• No database tables can be accessed where data aging is enabled,

• No customer extensions are allowed. Annotations AbapCatalog.extensibility.extensible or AbapCatalog.viewEnhancementCategory cannot be used to enable extensions or enhancements.

Notes

• The annotations @AbapCatalog.buffering.status, @AbapCatalog.buffering.type, and @AbapCatalog.buffering.numberOfKeyFields are not supported in CDS view entities. They are only valid for CDS DDIC-based views.

• Other than for CDS DDIC-based views, where the buffering is defined for the respective CDS-managed DDIC view, the table buffering of CDS view entities is defined for the CDS entity itself.

• In contrast to table buffering of CDS DDIC-based views where ABAP SQL bypasses the table buffer if the prerequisites are not met, for CDS view entities the restrictions are checked for the view. For a view that does not meet the prerequisites, table buffering cannot be enabled.

Example

Allowing buffering for a CDS view entity. The actual buffering is defined with the DDL for an entity buffer as shown under DEFINE VIEW ENTITY BUFFER.

rdisp/max_wprun_time - Maximum work process run time   CPI1466 during Backup  
This documentation is copyright by SAP AG.

Length: 5205 Date: 20240511 Time: 072042     sap01-206 ( 61 ms )