Get Example source ABAP code based on a different SAP table
ABAP_BUFFER - Single Record Buffering Only those rows are buffered that are actually accessed. This requires less space in the buffer than when using generic or full buffering. On the other hand, more administration work is required and significantly more direct database accesses. If a WHERE clause is used to access a non-buffered row and this clause specifies equality conditions joined using AND, an attempt is made to load this row. If the row is not found, this is noted in the buffer and a fully specified WHERE clause is used to avoid a new database access in the next read.
Latest notes:
When using single record buffering, any AB-SQL statements must respect the entire primary key to prevent them from bypassing table buffering.
Single record buffering is recommended for large amounts of data from which single rows are often read. For comparatively small amounts of data from which many rows are read, full buffering is usually preferred since this reduces the number of direct database accesses required for loading.
The use of single record buffering depends on the WHERE clause only and not on the use of the addition SINGLE. NON_V5_HINTS ABAP_HINT_END
