" 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. "
"A subset of Standard SQL that is fully integrated in ABAP is Open SQL statements. Their role is to help you by giving permission to access data irrespective of the database system, which the R/3 installation is using. The Data Manipulation Language (DML) part of the Standard SQL is present in the Open SQL. In other words, it gives you the permission to read (SELECT) and change (INSERT, UPDATE, DELETE) data. In the R/3 system, the tasks of the Data Definition Language (DDL) and Data Control Language (DCL) parts of the Standard SQL are performed by the ABAP dictionary and the authorization system."
Finding and Running programs in SAP is a fairly simple process. Every one know the transaction code SE38 The ABAP Editor. If you have forgotten the program name but you know that it starts with ZSales then you can type the ZSALES* in the transaction SE38 Program Input field and press F4 or the drop down button. You will then be presented with all the programs that have 'ZSALES' as the first 6 characters in their name.
You can also use the Transaction SA38 ABAP EXECUTE PROGRAMS to run programs. Mainly this transaction is used by the Users who do not want to edit/modify or create a new program.
Transaction SA38 does have options to execute the program with variant and in the back ground mode.
In case you wish to find a program either because you have forgotten the name or you are just looking for a report existing in the system, then you can use any of the Transactions mentioned above. Transaction SE38 has more flexibility.
Let us examine Transaction SE38 for the different options available for finding a program.
Transaction SE38 THE ABAP EDITOR
To find a Program in SAP ABAP goto Utilities >>>>> Find Program(CTRL+SHIFT+F4)
Once you are there you can either enter the Program name or Short Description or development class. All the programs with the same description and development class would be displayed depending on what you had entered.
Finding ABAP Program names based on the following criterion.
Program Author Last Changed By Changed On Program Type Status Application Logical Database Authorization Group Only Editor Lock Active Fixed Point Arithmetic Only
This can be easily achieved by clicking the 'ALL SELECTIONS ' Button (SHIFT+F7)
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.
