Professional Documents
Culture Documents
The following figure shows the memory organization within an internal session:
Program Groups
In an internal session it is possible to load multiple programs that can be organised in program groups. After
returning from an internal session, this is dismantled. It is then no longer possible to access data and objects of
the internal session.
During the creation of an internal session using the call of an ABAP program using SUBMIT or a transaction
code, the main program group is created and the called program makes up its main program. The internal
session exists for as long as the main program of the main program group is executed. This can be an
executable program, a module pool, or a function group.
during the external call of subroutines that are defined in executable programs, module pools or
subroutine pools
when using the screen statement CALL SUBSCREEN sub_area INCLUDING prog, if the screen is
not defined in a function group
during dynamic access to a local data type or object type of an executable program, module pool, or a
subroutine using absolute type names
with statements such as SET PF-STATUS OF PROGRAM, if the program of the necessary component
is not a function group.
Notes
It is not the program type that is important for the assignment of a program to a program group, but the
introductory program statement. For example, if the the statement FUNCTION-POOL is used in a
subroutine pool instead of PROGRAM, when the program is loaded by an external usage it forms an
additional program group.
Since all the programs of a program group use the interface work area, the screens, lists, and GUI
statuses of the main program (more below), the assignment of a program that is loaded into a program
group is particularly important if procedures of this program are called externally.
Data Objects
The data objects of a program, with the exception of the interface work area, belong exclusively to their
program and are only visible there. A loaded program exists for the same length of time as the internal session.
After returning from a program, its data objects are retained and are available if a procedure of the program is
called again.
Class Instances
Objects as instances of classes can be used by all programs (and objects) of an internal session. An object
exists for as long as there are users for (and hence references to) the object.
Note
This means that references to objects of the internal session can be transferred to externally called procedures.