Get Example source ABAP code based on a different SAP table
ABAP_CONTEXT - Buffering Concept A context buffer is managed by the context program CONTEXT_X_...> of a context>. From a technical point of view, it is a cross-transaction application buffer> of the structure CONTEXTB>> and the ID IB> in the shared memory> of the current ABAP_ASINSTANCE >, which is processed in the context program with the statements EXPORT TO SHARED BUFFER>> and IMPORT FROM SHARED BUFFER>>. The context program renews the context buffer at specific times but does not try to synchronously or nearly synchronously track current changes. ITOC
Buffering Types
Permanent (P)>: This is the default setting. In this case, the data is preserved across the transaction context. However, they are always reset to the full hour (8:00, 9:00...). Entries that are not found are not buffered. The buffer for each context can be deleted manually using the Context Builder>. and affects all ABAP_ASINSTANCE s.
Temporary (T)>: Data is only buffered for the duration of the current transaction>.
No buffering (N)>
Buffer Size The maximum number of entries to be buffered can also be defined. The default value is 128. This number refers to the permanent buffer per module. Within a transaction, everything that is written to the context is stored in the buffer unless buffering is switched off for this module. We recommend keeping a default value of 128. This is intended to prevent a module from occupying the entire buffer. Different combinations should no longer occur within an hour in a single ABAP_ASINSTANCE . The system resets the buffer after one hour.
Buffering Types
An I buffer is a table that assigns derived values to the input fields of the module. It
only contains one entry with key values.
An E buffer is a table that assigns the derived values of the module to the key fields of the context. It:
also contains multiple entries with the key values.
can be a join of all I buffers for the upstream modules
Performance The E buffer provides the fastest access, since it can find the values requested in the DEMAND> statement in a single step. However, it may return a smaller number of hits than the I buffer.