ABAP Keyword Documentation →  ABAP − Reference →  Creating Objects and Values →  Shared Objects →  Shared Objects - Areas → 

Areas - Dynamic Area Properties

The dynamic properties of an area are not considered when the area class is generated. These properties can be changed by developers only. When the dynamic properties of an area are changed dynamically during operation, the current area instance versions (versions that are being built, active or obsolete) are not affected. The new dynamic properties are not used until the next change lock is set in the corresponding version that is being built.

Any global class that implements the SHM_IF_SHM_BUILD_INSTANCE interface can be specified as an area constructor class. The implementation of the IF_SHM_BUILD_INSTANCE~BUILD interface method is used as the area constructor.
An area constructor class has to be specified if automatic area building is activated in the basic properties. The IF_SHM_BUILD_INSTANCE~BUILD interface method of the specified class is called implicitly in a separate main session when an area is built automatically.
An area constructor class can be specified if automatic area building is not activated in the basic properties. The IF_SHM_BUILD_INSTANCE~BUILD interface method of the current area constructor class can be called explicitly in the current internal session - using the BUILD method generated in every area class.
You can find an example of how to implement the IF_SHM_BUILD_INSTANCE~BUILD interface method in an area constructor class under Area Constructor Class.
This property determines whether and how instances of the area can be displaced. Displacement may be necessary if the available addressing area of the shared memory is not sufficient for all area instance versions. This may be the case in 32-bit systems, but should not be an issue for 64-bit systems. Possible displacement types are: