Ansicht
Dokumentation
ABENMEMORY_CONSUMPTION - MEMORY CONSUMPTION
SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up TXBHW - Original Tax Base Amount in Local CurrencyThis documentation is copyright by SAP AG.
Memory Management of Deep Objects
All data types for which the content of their data objects represents the actual work data referred to as "flat" in ABAP. The elementary data types of a fixed length are flat, as are structures with exclusively flat components. The memory requirements of flat data objects are defined statically by the data type. Flat data objects are always static data objects.
On the other hand, data types where the content of their data objects consists of references, which, in turn, refer to work data in another memory area, are referred to as "deep". Types of data reference variables and object reference variables, as well as the types of strings, internal tables, and boxed components are deep. Strings and internal tables are dynamic data objects whose memory requirements can change at program runtime and are managed internally using references. Reference variables are static data objects since their actual size is fixed, whereas the size of the explicitly referenced objects is dynamic. Boxed components are a medium in between because their memory requirements in the internal session are not defined when the program is started in the internal session, but can be handled like static data objects with a fixed length. Structures are referred to as deep, regardless of nesting if they contain at least one deep component.
When using deep data objects, working memory is requested at program runtime. In the case of reference variables, this is the memory for administrative information and the objects created (instances of classes and anonymous data objects). In the case of dynamic data objects (strings, internal tables) and boxed components, this is the memory for administrative information and for the data objects themselves. Objects referenced by reference variables can themselves, in turn, be dynamic, that is, be or contain strings or internal tables.
The requested memory must be available in the session memory of the current internal session, since otherwise a runtime error occurs.
Note
The available session memory is controlled by the profile parameters described under Session Memory. A percentage of the available memory can also be defined as a limit, where a runtime warning occurs if it is exceeded.
RFUMSV00 - Advance Return for Tax on Sales/Purchases TXBHW - Original Tax Base Amount in Local Currency
This documentation is copyright by SAP AG.
Length: 4378 Date: 20240501 Time: 235607 sap01-206 ( 69 ms )
