Ansicht
Dokumentation
ABENABAP_PROGRAM_CALL - ABAP PROGRAM CALL
CPI1466 during Backup BAL_S_LOG - Application Log: Log header dataThis documentation is copyright by SAP AG.
Calling Programs
If allowed by the package concept, the following can be called in each processing block of an ABAP program:
- Transactions, that is, programs linked to a transaction code
When a program is called, the calling program can be exited either temporarily or completely.
IMAGE @@ABDOC_Call_Prog.gif@@623@@623@@
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 form a call sequence. Within a call sequence, there is 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 completely exited (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.
Notes
- When a called program is loaded, the event LOAD-OF-PROGRAM is raised in that program.
- The statement SUBMIT without the addition AND RETURN shown on the right side of the figure does not always replace the internal session of the calling program directly. If the calling program was not started with SUBMIT itself, its internal session is preserved in the call sequence and is only deleted after the submitted program is completed.
PERFORM Short Reference BAL_S_LOG - Application Log: Log header data
This documentation is copyright by SAP AG.
Length: 2941 Date: 20240426 Time: 154719 sap01-206 ( 45 ms )
