SAP NEWS-71-SHARED OBJECTS documentation, setup help and example usage

Shared Objects in Release 7.0, EhP2

1 Handling of Memory Shortages
2 Data References in the Shared Objects Memory
3 Area Binding
4 Replacement of PROPAGATE_AREA and PROPAGATE_INSTANCE
Methods
5 Service Class CL_SHM_UTILITIES


ABAP_MODIFICATION_1 Handling of Memory Shortages

As of Release 7.0, EhP2 , memory shortages in the shared objects memory raise treatable exceptions of the CX_SHM_OUT_OF_MEMORY class. Previously, untreatable runtime errors were caused.


ABAP_MODIFICATION_2 Data References in the Shared Objects Memory


As of Release 7.0, EhP2 , anonymous data objects in the shared objects memory with the AREA HANDLE addition of the CREATE DATA statement can also be created with direct reference to data elements and table types of the ABAP Dictionary.


ABAP_MODIFICATION_3 Area Binding

As of Release 7.0, EhP2 , the lifetime and visibility of area instances can be bound not only to the current
application server but also to:
User sessions
Top level transactions


ABAP_MODIFICATION_4 Replacement of PROPAGATE_AREA and PROPAGATE_INSTANCE Methods

The PROPAGATE_AREA and PROPAGATE_INSTANCE methods of an area class for transactional areas should no longer be used. Instead the AFFECT_SERVER parameter of the
FREE_AREA , FREE_INSTANCE , INVALIDATE_AREA , and
INVALIDATE_INSTANCE methods can be used for this type of area.


ABAP_MODIFICATION_5 Service Class CL_SHM_UTILITIES

You can use the CL_SHM_UTILITIES class to programmatically query the attributes of area instances.

Documentation extract taken from SAP system, � Copyright SAP AG. All rights reserved