Get Example source ABAP code based on a different SAP table
ABAP_SHM - Restrictions Currently, the following restrictions apply to shared objects:
When data objects referenced using data references are stored, there is a restriction that the dynamic type cannot have been created at program runtime. Direct references to data elements and table types in the ABAP Dictionary are, however, possible.
Memory bottlenecks can occur in the shared objects memory, but can also be handled. The associated exception class is CX_SHM_OUT_OF_MEMORY.
There is no memory restriction for logical areas, which generally consist of many area instances. There are currently only memory restrictions for individual area instances.
The lifetime of area instances cannot be bound to the lifetime of user sessions, ABAP sessions, or transactions. Area instances currently exist as long as the ABAP_ASINSTANCE .
Latest notes: On 32-bit systems, only a limited amount of memory space is available for storing shared objects, due to the limited address space. For this reason, shared objects could only be used on 32-bit systems under certain conditions. ABAP_HINT_END
