Registration

Dear SAP Community Member,
In order to fully benefit from what the SAP Community has to offer, please register at:
http://scn.sap.com
Thank you,
The SAP Community team.
Skip to end of metadata
Go to start of metadata
Unknown macro: {gliffy}

ABAP programs consist of processing blocks, and can contain screens as components, controlled by the ABAP runtime environment.ABAP has the following program types:

  • Executable ProgramType 1; introduced with the REPORT statement; can be started by entering the program name or using a transaction code; can be called using SUBMIT; can have its own screens.
  • Module PoolType M; introduced with the PROGRAM statement; can be started using a transaction code; can be called using CALL TRANSACTION or LEAVE TO TRANSACTION; have their own screens.
  • Function GroupType F; introduced with the FUNCTION-POOL statement; non-executable; container for function modules; can have its own screens.
  • Class DefinitionType K; introduced with the CLASS-POOL statement; non-executable; container for classes; cannot (currently) have its own screens.
  • Interface DefinitionType J; introduced with the CLASS-POOL statement; non-executable; container for interfaces; cannot have its own screens.
  • Subroutine PoolType S; introduced with the PROGRAM statement; non-executable; container for subroutines; cannot have its own screens.
  • Type GroupsType T; introduced with the TYPE-POOL statement; non-executable; container for type definitions; cannot have its own screens.
  • Include ProgramType I; no introductory statement; non-executable; container for source code modules.
    Non-executable programs with types F, K, J, S, and T are loaded into memory as required. Include programs are not separately-compiled units; their source code is inserted into the programs in which the corresponding include statement occurs.
  • No labels