Get Example source ABAP code based on a different SAP table
ABAP_DDIC - Table Buffering of Database Tables It is possible to define whether and how table buffering of a DDIC database table is allowed in the table buffer of an ABAP_ASINSTANCE . ITOC The table buffer is managed by the database interface. When tables with active buffering are accessed using AB_SQL BEGIN_SECTION VERSION 5 OUT or from classic dynpros END_SECTION VERSION 5 OUT , the table buffer is used implicitly.
Buffering Permission Table buffering can be configured for a DDIC database table as follows:
Buffering not allowed The table is not buffered. The database interface always passes the accesses to the DDIC database table and the current data is used directly. This setting also specifies that table buffering should not be activated for this table in any other systems due to the way the table is used.
Buffering allowed, but switched off The table is not buffered when delivered. This setting indicates, however, that buffering is possible in principle and can be activated in other systems depending on how the table is used.
Buffering switched on The table is buffered. The database interface redirects any reads to the table buffer in the shared memory of the current ABAP_ASINSTANCE , if possible.
Latest notes: Certain prerequisites, some of which depend on the buffering type, must be met before AB_SQL can access the table buffer instead of accessing the DDIC database table directly. NON_V5_HINTS ABAP_HINT_END
Buffering Type The buffering type determines which data is loaded from the table to the table buffer when a table entry is accessed and buffering is switched on. The possible buffering types are:
