SAP PROGRAM TYPES

SAP ABAP PROGRAMS

Each ABAP program has a type, which is defined in the program attributes. The program type determines which processing blocks a program can contain, and how the program is handled and executed by the runtime environment.

 In the R/3 System, there are various ABAP program types. The program type determines the basic technical attributes of the program, and you must set it when you create it. The main difference between the different program types is the way in which the runtime environment calls its processing blocks.

  

Type 1 programs

Type 1 programs do not have to be controlled using user-defined screens. These are controlled by the runtime environment. Type 1 programs are called as Executable programs as they can be executed by typing the name of the program directly. Type 1 programs are also called as Online program. Type 1 programs (executable programs) in the R/3 System are often referred to as reports. Executable programs do not require any user dialog. You can also assign a transaction code to an executable program. This kind of transaction is called a report transaction.

Type M programs

Type M programs can only be controlled using screen flow logic. You must start them using a transaction code, which is linked to the program and one of its screens (initial screen). You must define your own screens in the Screen Painter (although the initial screen can be a selection screen). Type M programs are called as Module pools or Dialogue programs.

Type F programs

Type F programs are containers for function modules. These programs cannot be started using a transaction code or by entering their name directly. Type F programs can be called from other executable programs or Module Pool programs by inserting the code of the Function Module. Type F programs are called as Function groups. Function modules may only be programmed in function groups. Apart from function modules, function groups can contain global data declarations and subroutines. These are visible to all function modules in the group. Function Modules and Function groups can be created using transaction code SE37 or SE80.

Type K programs

Type K programs are containers for global classes in ABAP Objects. They cannot be started by using a program name or using a Transaction Code. Type K programs are known as Class definitions or Class pool. Type K programs are created using a Class Builder (SE 24).

Type J programs

You cannot start type J programs using a transaction code or by entering the program name directly. These programs are containers for global interface in ABAP Objects. Type J programs are known as Interface definitions or Interface pool. You create interface definitions in the Class Builder.

Type S programs

Type S programs are known as Subroutine pools. These types of programs are containers for subroutines. You cannot start a type S program using a transaction code or by entering the program name. Instead, they are containers for subroutines, which you can call externally from other ABAP programs. They cannot contain screens.

Type I programs

Type I programs are called as Includes or Include program. They are used to make code simpler by breaking it into smaller units. You can insert the coding of an include program at any point in another ABAP program using the INCLUDE statement. There is no technical relationship between include programs and processing blocks. These types of programs cannot be run using the program name or a transaction code. The ABAP Workbench has a mechanism for automatically dividing up module pools and function groups into include programs.