ABAP Keyword Documentation →  ABAP - Reference →  Declarative statemnts →  Data Types and Data Objects →  Types and Objects - Overview →  Data Objects →  Memory Consumption of Deep Data Objects 

Sharing Between Dynamic Data Objects

When reference variables are assigned, only the references are copied. After an assignment, source and target variables point to exactly the same data object or the same instance of a class (to the header).

Sharing takes place internally when assignments are made between strings and similar internal tables that have line types that do not contain table types or boxed components. This means that the actual data values are not copied for the time being. Only the necessary administration entries are copied, so that the target object refers to the same data as the source object.

With strings, a new internal reference is generated that points to the existing string header. With internal tables, a new internal reference is generated along with a new table header that refers to the existing table body.

Naturally, sharing between dynamic data objects is active only as long as multiple dynamic data objects are involved or if more than one internal reference points to the data values. As soon as only one internal reference points to the data, sharing becomes inactive. This can occur, for example, if dynamic data objects only exist during the lifetime of a procedure or are recorded as anonymous data objects by Garbage Collector.

Active sharing between existing dynamic data objects is canceled at the precise moment when either the source object or target object is accessed in change mode (copy-on-write semantics). The data values are then copied and the references and headers modified accordingly.

The following figure illustrates how dynamic data objects are shared. The upper left section shows how strings are shared and the right section shows how internal tables are shared. The lower section shows how sharing is terminated when the source or target object is modified.

Other versions: 7.31 | 7.40 | 7.54

Notes

• Tables are generally only shared that have line types that do not contain table types or boxed components. Otherwise, the prerequisite for "similar tables" is kept deliberately vague. Tables are considered to be similar if they at least have the same table type, that is, the same line type, table kind, and keys. Additional table combinations are also considered to be similar and may be shared. However, this is an internal optimization measure that may change between releases. You should therefore never program when table sharing should occur and when it should be canceled.

• Sharing also occurs during value transfer to procedures.

• Sharing is also supported when accessing shared objects as long as an area instance version is bound to the current internal session using an area handle.

• Sharing is not canceled when objects are modified for reference variables that refer to the same data object or the same instance of a class.

• Another kind of sharing is the initial value sharing of boxed components for which the initial value is stored only once for each application server.