Get Example source ABAP code based on a different SAP table
ID LOAD-OF-PROGRAM • LOAD-OF-PROGRAM ABAP Statement
LOAD-OF-PROGRAM Short Reference
ABAP_SYNTAX LOAD-OF-PROGRAM.
What does it do? This event keyword defines the program constructor of a function pool BEGIN_SECTION VERSION 5 OUT , executable program, module pool, or subroutine pool. END_SECTION VERSION 5 OUT The program constructor is an event block whose event is raised by the ABAP runtime framework if such a program is loaded into the ABAP_ISESS . BEGIN_SECTION VERSION 5 OUT When a program is called using SUBMIT or a transaction code, a new ABAP_ISESS is opened each time a call is made and the event block is executed once for each call. Global data objects of the program can be initialized here. The event block must be fully executed, otherwise a runtime error occurs. This means that no statements can be executed that exit the event block without returning to it. END_SECTION VERSION 5 OUT The first time an external procedure BEGIN_SECTION VERSION 5 OUT or a subscreen END_SECTION VERSION 5 OUT is called, the compilation unit of the called procedure is loaded into the ABAP_ISESS of the caller and the event LOAD-OF-PROGRAM is raised. The event block is executed before the called procedure. Each time a procedure of the same compilation unit is called again by a caller of the same ABAP_ISESS , the event LOAD-OF-PROGRAM is no longer raised.
Latest notes:
The event LOAD-OF-PROGRAM should not be used to call sophisticated processes, where the program flow cannot be controlled by the caller. This includes especially those that involve user interactions, because then it cannot be guaranteed that the event block is fully executed.
If a program is only loaded because declarations are required of it, for example, when using absolute type names, the LOAD-OF-PROGRAM event is not raised. The program constructor is only executed if an executable unit of the program is called afterwards.
Class pools do not have a program constructor, since the static constructor of the global class defined in the class pool can be used instead. NON_V5_HINTS
The event LOAD-OF-PROGRAM should mainly be used to initialize global data when calling external procedures or transactions.
Any statements that exit the event block LOAD-OF-PROGRAM like RETURN raise the runtime error SYSTEM_LOAD_OF_PROGRAM_FAILED and lead to errors from the extended program check. Although the statement LEAVE PROGRAM does not cause a runtime error, it should still not be used.
It is discouraged to send any messages in the event block LOAD-OF-PROGRAM that require user interaction and block the program flow, because this is not appropriate in the moment of loading a program. Since the behavior of messages depends on the context, where a program is loaded, you should not use them at all. A message of type E leads to runtime error SYSTEM_LOAD_OF_PROGRAM_FAILED anyway.
For executable programs that are called using SUBMIT, it is recommended that the event INITIALIZATION is used, since the start values for parameter and selection criteria are set after LOAD-OF-PROGRAM (see program flow after SUBMIT) and because its event block must not be fully executed. ABAP_HINT_END
ABAP_EXAMPLE_VX5 The include program LABAP_DOCUE00 implements the LOAD-OF-PROGRAM event block of a function pool. It sets a global variable and triggers an action that is relevant for the complete function pool. ABAP_EXAMPLE_END
