Shared Objects to Release 7.0
1 Data references in the Shared Objects Memory
2 Waiting periods for change locks
ABAP_MODIFICATION_1
Data references in the Shared Objects Memory
Since 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 only occurs
if the used data type is unknown to the DETACH_COMMIT
method in the Shared Objects Memory during execution. 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 of the ABAP Dictionary is possible as well.
The opportunity to store data references in closed area instance
versions makes it possible - since release 7.0 - to store not only
instances of classes, but also
anonymous data objects with the addition
AREA HANDLE of the statement
CREATE DATA
as Shared Objects .
ABAP_MODIFICATION_2 Waiting period for change locks
Since release 7.0, a waiting period can be transferred to the
parameter WAIT_TIME for the methods ATTACH_FOR_WRITE and
ATTACH_FOR_UPDATE of the area class
. The same applies for MULTI_ATTACH of CL_SHM_AREA .
Documentation extract taken from SAP system, � Copyright SAP AG. All rights reserved