Ansicht
Dokumentation

ABENABAP_PROGRAM_STATEMENT - ABAP PROGRAM STATEMENT

ABENABAP_PROGRAM_STATEMENT - ABAP PROGRAM STATEMENT

Vendor Master (General Section)   CL_GUI_FRONTEND_SERVICES - Frontend Services  
This documentation is copyright by SAP AG.
SAP E-Book

Program-Initiating Statements

The program-initiating statements are:

The initiating statement of each program depends on the program type specified in the program attributes.

All statements that follow the program-initiating statements in the source code or that are included as include programs are handled as a single unit by ABAP Compiler.

The first statement of every standalone ABAP program must be a program-initiating statement, and each program can only contain one of these statements. The only other statement allowed at the first position instead of the initiating statement is the statement INCLUDE. In this case, a program-initiating statement must appear at the first position of the program after the include program is resolved when it is generated.

Executable programs, module pools, function pools, class pools, interface pools, subroutine pools, and type pools are independent compilation units. Include programs, on the other hand, are only used in the context of compilation units.

Type pools, also referred to as type groups, are logically independent programs in which no executable code can be stored, only type definitions and constant definitions. For this reason, type pools have their own program-initiating statement, TYPE-POOL.

Note

The assignment of initiating statements to the program types defined in the program attributes is not mandatory. However, the assignment described in the following sections should always be used. When a program is created, the appropriate statement is created automatically by the ABAP Workbench or ADT and should only be changed in the additions during editing. In particular, the keywords FUNCTION-POOL, CLASS-POOL, INTERFACE-POOL, and TYPE-POOL should only be created by the corresponding tools of the ABAP Workbench and never be entered manually in the source code in order to avoid unexpected system behavior.






BAL Application Log Documentation   ABAP Short Reference  
This documentation is copyright by SAP AG.

Length: 3277 Date: 20240420 Time: 150358     sap01-206 ( 60 ms )