Work Processes in SAP ABAP :
A).Work Processes : Work processes execute the individual dialog steps in R/3 applications. The next two sections describe firstly the structure of a work process & secondly the different types of work process in the R/3 System. Each work process contains two software processors & a database interface.
a).Screen Processor : In R/3 application programming, there is a difference between user interaction & processing logic. So from a programming point of view, a user interaction is controlled by screens. As well as the actual input mask, a screen also consists of flow logic and the screen flow logic controls a large part of the user interaction. Also the R/3 Basis system contains a special language for programming screen flow logic.The screen processor executes the screen flow logic. Via the dispatcher, it takes over the responsibility for communication between the work process & the SAP gui, calls modules in the flow logic, and ensures that the field content are transferred from the screen to the flow logic.
B).ABAP Processor :Actual processing logic of an application program is written in ABAP - SAP’s own programming language. The ABAP processor execute the processing logic of the application program & communicate with the database interface.The screen processor tells the ABAP processor which module of the screen flow logic should be processed next. The following screen illustrate the interaction between the screen & the ABAP processors when an application program is running.
B).Types of Work Process :
The various work processes are described briefly below. Other part of this documentation describe the individual component of the application server and the R/3 System in more detail.
a).Screen Processor : In R/3 application programming, there is a difference between user interaction & processing logic. So from a programming point of view, a user interaction is controlled by screens. As well as the actual input mask, a screen also consists of flow logic and the screen flow logic controls a large part of the user interaction. Also the R/3 Basis system contains a special language for programming screen flow logic.The screen processor executes the screen flow logic. Via the dispatcher, it takes over the responsibility for communication between the work process & the SAP gui, calls modules in the flow logic, and ensures that the field content are transferred from the screen to the flow logic.
B).ABAP Processor :Actual processing logic of an application program is written in ABAP - SAP’s own programming language. The ABAP processor execute the processing logic of the application program & communicate with the database interface.The screen processor tells the ABAP processor which module of the screen flow logic should be processed next. The following screen illustrate the interaction between the screen & the ABAP processors when an application program is running.
B).Types of Work Process :
The various work processes are described briefly below. Other part of this documentation describe the individual component of the application server and the R/3 System in more detail.
1).Dialog Work Process: The Dialog work processes deal with requests from an active user to execute dialog steps.
2).Update Work Process : The Update work processes execute database update requests. So update requests are part of an SAP LUW that bundle the database operations resulting from the dialog in a database LUW for processing in the background.
3).Background Work Process: The Background work processes process programs that can be executed without user interaction [background jobs].
4).Enqueue Work Process :The enqueue work process administer a lock table in the shared memory area. So the lock table contains the logical database lock for the R/3 System and is an important part of the SAP LUW concept. In an R/3 System, we may only have one lock table. We may therefore also only have one application server with enqueue work processes.
5).Spool Work Process :The spool work process passes sequential dataset to a printer or to optical archiving.So each application server may contain only one spool work process.The services offered by an application server are determined by the types of its work processes.One application server may, of course, have more than one function.For ex: it may be both a dialog server and the enqueue server, if it has several dialog work processes & an enqueue work process.
We can use the system administration functions to switch a work process between dialog & background modes while the system is still running. This allows us, for ex: to switch an R/3 System between day & night operation, where we have more dialog than background work processes during the day & the other way around during the night.
2).Update Work Process : The Update work processes execute database update requests. So update requests are part of an SAP LUW that bundle the database operations resulting from the dialog in a database LUW for processing in the background.
3).Background Work Process: The Background work processes process programs that can be executed without user interaction [background jobs].
4).Enqueue Work Process :The enqueue work process administer a lock table in the shared memory area. So the lock table contains the logical database lock for the R/3 System and is an important part of the SAP LUW concept. In an R/3 System, we may only have one lock table. We may therefore also only have one application server with enqueue work processes.
5).Spool Work Process :The spool work process passes sequential dataset to a printer or to optical archiving.So each application server may contain only one spool work process.The services offered by an application server are determined by the types of its work processes.One application server may, of course, have more than one function.For ex: it may be both a dialog server and the enqueue server, if it has several dialog work processes & an enqueue work process.
We can use the system administration functions to switch a work process between dialog & background modes while the system is still running. This allows us, for ex: to switch an R/3 System between day & night operation, where we have more dialog than background work processes during the day & the other way around during the night.
Comments
Post a Comment
If you have any doubts let me know