n the R/3 Program, there are various ABAP system kinds. It type decides the primary specialized features of the system, and you must set it when you make it.
Type 1 do not have to be managed using user-defined displays. These are managed by the playback atmosphere. Type 1 are known as as Exe applications as they can be implemented by entering the name of the system straight. Type 1 are also known as as Online system. Type 1 in the R/3 Program are often termed as reviews. type 1 do not need any individual conversation. You can also determine a deal value to an executable system. This type of deal is known as a review deal.
Type M can only be managed using display circulation reasoning. You must begin them using a deal value, which is connected somewhere and one of its displays (initial screen). You must determine your own displays in the Screen Artist (although the preliminary display can be a choice screen). Type M are known as as Component regularly or Dialogue applications.
Type F are bins for operate segments. They cannot be began using a deal value or by coming into their name straight. They can be known as from other executable applications or Component Share applications by placing the value of the Function Component. Type F are known as as Function categories. Function segments may only be designed in operate categories. Apart from operate segments, operate categories can contain international information conditions and subroutines. These are noticeable to all operate segments in the team. Function Modules and Function categories can be designed using deal value SE37 or SE80.
Type K are bins for international sessions in ABAP Things. They cannot be began by using something name or using a Transaction Code. Type K applications are known as Category explanations or Category pool. Type K are designed using a Category Designer (SE 24).
You cannot begin Type J applications using a deal value or by coming into the system name straight. They are bins for international individual interface in ABAP Things. Type J are known as Interface explanations or Interface pool. You make individual interface explanations in the Category Designer.
Type S are known as Subroutine regularly. They are bins for subroutines. You cannot begin a type S using a deal value or by coming into the system name. Instead, they are bins for subroutines, which you can call on the outside from other ABAP applications. They cannot contain displays.
Type I are known as as Contains or Consist of system. They are used to make value easier by splitting it into small models. You can place the programming of an include system at any point in another ABAP system using the INCLUDE declaration. There is no specialized connection between include applications and handling prevents. They cannot be run using the system name or a deal value.
Article Source: http://EzineArticles.com/7320043