ABAP Keyword Documentation → ABAP - Reference → Creating Objects and Values → Shared Objects → Shared Objects - Areas
Areas - Fixed Area Properties
Like basic properties, fixed properties of an area can be only be changed by developers. When the fixed properties of an area are changed during operation, all area instances of the area are set to status expired. The area class does not have to be regenerated however.
- Area Binding
- Application server
Area instance versions exist until the application server is shut down.
- User session
Area instances exist until the last ABAP session of the current user session ends. For area binding, every user logon to an AS ABAP counts individually. This also applies in particular when users log on using external interfaces such as RFC or ICF.
- Top level transaction
The top level transaction is the first program in a call sequence. These area instances exist for as long as the ABAP memory assigned to a call sequence is loaded, in other words for as long as the internal session of the top level transaction is loaded.
- Area Instance Versioning
Other versions:
7.31 | 7.40 | 7.54