Get Example source ABAP code based on a different SAP table
ABAP_BUFFER - Restrictions Only transparent tables can be buffered. Global temporary tables cannot be buffered. There is no special restriction on the key length of the table when buffering, which means that keys in buffered tables can be up to 900 bytes long. For database accesses using BEGIN_SECTION VERSION 5 OUT Native SQL and END_SECTION VERSION 5 OUT AMDP, the table buffer is not used in principle. Any writes access the data in the database table directly and trigger asynchronous buffer synchronization. After the invalidation of an entry in the buffer using a write statement, the next five reads that should have accessed the entry bypass the buffer of the current ABAP_ASINSTANCE by default. The next read performed on the changed entry reloads it into the buffer and removes the invalidation. BEGIN_SECTION VERSION 5 OUT The number of reads that bypass the buffer before the reload is specified in the profile parameter zcsa/sync_reload_c. END_SECTION VERSION 5 OUT The fact that certain operations can only be performed on the database and not in the table buffer produces the further restrictions for reads listed below. If these restrictions are not respected, read AB-SQL statements bypass the table buffer implicitly and access the DDIC database tables, DDIC views or CDS view entities directly.
The following reads always bypass the table buffer:
Use of subqueries, and thus in particular the statement WITH.
The AB-SQL language element GROUPING SETS.
The AB-SQL set operators UNION, INTERSECT, and EXCEPT.
Reads on a table or view for which a replacement object is defined.
Reads using a database connection specified explicitly using the addition CONNECTION. This also applies when the standard connection is specified explicitly.
