Get Example source ABAP code based on a different SAP table
Calling Programs If allowed by the package concept, the following can be called in each processing block of an ABAP program:
Executable programs
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 ABAP_ISESS . The ABAP_ISESS 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 ABAP_ISESSNS . 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 ABAP_ISESS , which replaces the ABAP_ISESS of the calling program. A program that creates an ABAP_ISESS when it is called represents the main program of the main program group in the ABAP_ISESS .
Latest 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 ABAP_ISESS of the calling program directly. If the calling program was not started with SUBMIT itself, its ABAP_ISESS is preserved in the call sequence and is only deleted after the submitted program is completed. ABAP_HINT_END
