" In a SAP system, the work process play a very important role. It is seen that a majority of the processing is done by work processes. Work processes execute dialog steps in user transactions, updates, lock administration can display the status of the work process running on your application server after logon. To display the status choose Administration --> System Administration ---> Monitor ---> System Monitoring ----> Process over view or Execute transaction SM50. To get the updated information, the display must be refreshed regularly. The administrator must regularly monitor the system processes for checking the appropriateness of the number and configuration. Generally possesses are monitored to obtain information. The information obtained can be used for many purposes. It can be used to determine, whether the number of work processes in your system is adequate to assess if the instance is working to its ultimate capacity and to gather information for troubleshooting or for tuning. The SAP work processes correspond to operating system processes, these processes can be monitored through other operating systems also. Or it can be said that process ID (PID) of the SAP system is the same as PID of the other operating systems. SAP has a runtime directory /usr/sap//SYS/exe/run. Some programs are present in this runtime directory for monitoring. You can monitor some of the work processes and the dispatcher from the operating system with the help of these monitoring programs. To display the overview of SAP application server choose System Monitoring ---> Servers. You can also display the overview of the work process running on this particular server in the SAP system. To display the overview of the work process first click on the desired server name. "
"The flow of a program is determined by a sequence of screens in a dialog transaction. The screens that are called within a transaction, must belong to a single ABAP program, usually a module pool (Type M). You have to use the transaction maintenance transaction (SE93) to create a dialog transaction. Once you have entered a transaction code and a short description, chose transaction type program and screen. Then enter data on the next screen as required. The transaction code in a dialog program must be linked to the number of its initial screen. Finally enter this number in the screen number field."
Thursday, August 14, 2008
SAP ABAP Important Keywords : The following list displays some of the important Keywords in ABAP
No
Keyword
Description
1
AT END OF … ENDAT
Control group end in LOOP
2
AT Fg … ENDAT
Processing specific to record type in LOOP
3
AT FIRST … ENDAT
Execute processing block within a LOOP before processing single lines
4
AT LAST … ENDAT
Execute processing block within a Loop after processing single lines
5
AT NEW … ENDAT
Control group end during LOOP
6
CALL
Call processing (Program, function module, screen)
7
CHECK
Selection condition, leave loops and subroutines
8
CONTINUE
Exit current loop pass within a DO, WHILE, LOOP or SELECT loop
9
DO … ENDDO
Loop processing
10
EXEC SQL … ENDEXEC
Execute a Native SQL Statement
11
EXIT
Leave loops or subroutines
12
FORM … ENDFORM
Definition of a subroutine
13
IF … ELSE … ENDIF
Conditional processing
14
LEAVE
Leave program processing, go to a transaction, list (or) menu
Always specify your conditions in the Where-clause instead of checking
them yourself with check statements. The database system can then use an index
(if possible) and the network load is considerably less.
Always use Pretty Printer and Extended Program Check before releasing the code.
Do not leave unused code in the program. Comment the code thoroughly. Align the comments and the Code. Follow the SAP Standards and SAP Best Practices guidelines. It’s a good practice to take a dump of the code on your local drive.
