ABAP Keyword Documentation → ABAP − Reference → Calling and leaving program units
Calling Programs
If permitted by the package concept, each processing block of ABAP program makes it possible to call the following:
- Transactions (programs associated with a transaction code)
statement. When a program is called, the calling program can be exited either temporarily or completely.
In temporary exits from the calling program (shown on the left side of the figure), the called program is started in a new
internal session. The internal session of the calling program is preserved. The calling program and the called program represent a
call sequence. Within a call sequence, the programs have shared access to the
ABAP Memory (using the
statements IMPORT FROM MEMORY
and EXPORT TO MEMORY).
A call sequence can have a maximum of nine internal sessions. If this maximum is exceeded, the program terminates and the entire call sequence is deleted.
When the calling program is exited in full (shown on the right side of the figure), the called program is started in a new internal session, which replaces the internal session of the calling program.
A program that creates an internal session when it is called represents the main program of the main program group in the internal session.
Other versions: 7.31 | 7.40 | 7.54
Note
When the runtime environment loads a called program, the event LOAD-OF-PROGRAM is raised in that program.