ABAP Keyword Documentation →  ABAP - Release-Specific Changes →  Changes in Release 7.0 and its EhPs →  Changes in Release 7.0 

Shared Objects in Release 7.0

1. Data references in the shared objects memory

2. Waiting time for change locks

Other versions: 7.31 | 7.40 | 7.54

Modification 1

Data References in the Shared Objects Memory

From Release 7.0, data references that point to data objects of the same area instance version can be stored permanently in the shared objects memory. An instance of a shared memory-enabled class can contain data reference variables as attributes that point to data objects within a closed area instance version. An exception is raised only if the used data type is unknown to the method DETACH_COMMIT in the shared objects memory when the method is executed. This is the case if the types of the referenced data objects were created dynamically. Due to technical reasons, no direct reference to data elements and table types in ABAP Dictionary is possible either.

The opportunity to store data references in closed area instance versions makes it possible (from Release 7.0) to store not only instances of classes, but also anonymous data objects using the addition AREA HANDLE of the statement CREATE DATA as shared objects.

Modification 2

Waiting Time for Change Locks

From Release 7.0, a waiting period can be passed to the parameter WAIT_TIME for the methods ATTACH_FOR_WRITE and ATTACH_FOR_UPDATE of the area class and for MULTI_ATTACH in CL_SHM_AREA.