SAP ABAP program types
In the R / 3 System, there are several types of ABAP programs. The program type determines the basic technical attributes of the program and you must set it when you create it.
Type 1
Type 1 does not have to be controlled by user-defined screens. These are controlled by the runtime environment. Type 1s are called executable programs, since they can be run by typing the name of the program directly. Type 1 is also called an online program. Type 1s in the R / 3 System are often called reports. type 1 does not require any user dialog. You can also assign a transaction code to an executable program. This type of transaction is called a report transaction.
Type M
Type M can only be controlled by 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). The M types are called groups of modules or dialog programs.
F type
F-types are containers for function modules. They cannot be started by using a transaction code or by entering your name directly. They can be called from other executable programs or module group programs by inserting the function module code. The F types are called function groups. Function modules can only be programmed in function groups. In addition to function modules, function groups can contain subroutines and global data declarations. These are visible to all function modules in the group. Function modules and function groups can be created using transaction code SE37 or SE80.
K type
Type K are containers for global classes in ABAP objects. They cannot be started using a program name or transaction code. K-type programs are known as class definitions or group of classes. K types are created using a Class Builder (SE 24).
Type J
You cannot start Type J programs by using a transaction code or by entering the program name directly. They are containers for the global interface on ABAP objects. J types are known as interface or interface group definitions. Interface definitions are created in Class Builder.
Types
S-types are known as subroutine groups. They are containers for subroutines. You cannot start a type S by 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
Type I is called an Include or Include program. They are used to simplify the code by breaking it down into smaller units. You can insert the encoding of an include program anywhere in another ABAP program using the INCLUDE statement. There is no technical relationship between embedding programs and processing blocks. They cannot be executed using the program name or a transaction code.