" 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. "
"SAP has provided two different types of methods for BDC to do its work. Among these the first one is called the classical method. This method is also called as the session method. Through this method the data can be read by the BDC program from a sequential dataset file. This sequential dataset file is stored in batch-input sessions. In order to run the transaction in this session, What you need is to execute the session. For this follow these few steps. YOu an start and subsequently monitor the sessions firstly from System----> Service---->Batch input or have the sessions run in the background."
CLASSICAL EVENTS Initalization At selection-screen output At seelction-screen on field At selection-screen on block At selection-screen Start-of-selection End-of-selection
INTERACTIVE EVENTS At line-selection At user-command At pfnn Top-of-page during line selection
LIST EVENTS Top-of-page End-of-page
CONTROL BREAK EVENTS At first At last At new At end of On change of
INITIALIZATION Before the standard selection screen is displayed
AT SELECTION-SCREEN After user input on a selection screen has been processed, but while the selection screen is still active
START-OF-SELECTION After the standard selection screen has been processed, before data is read from the logical database
GET node After the logical database has read a data record from the node node
GET node LATE After all of the nodes of the logical database have been processed that are hierarchically subordinate to the node node in the structure of the logical database
END-OF-SELECTION After all data has been read by the logical database
List processor events: TOP-OF-PAGE In list processing when a new page starts
END-OF-PAGE In list processing when a page ends
AT LINE-SELECTION When the user triggers the predefined function code PICK
AT PFnn When the user triggers the predefined function code PFnn
AT USER-COMMAND When the user triggers a function code defined in the program
To find User Exits in SAP please follow the steps given below.
1) Run Transaction SE81 2) Select SD 3) From the Menu Click on Edit 4) Select the option ‘Select Subtreee +/-‘ 5) From the Menu bar click on Information system 6) From the R/3 Repository information System open the Envir option 7) Select Exit Techniques 8) Select Customer Exits 9) Double click on Enhancements 10) Press F8
See the screen shots given below. Run Transaction SE81.
Select SD and then from the Edit menu click on Select Subtree
Click on Information System or press Shift+F4
Menu for 'R/3 Repository Information Sys' opens up
Follow the menu path Envir-----> Exit Techniques----> Customer Exits----> Enhancements
Click on the Execute button or press 'F8'
The following list is displayed.
Follow the above mentioned steps to find user exits for other modules.
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.
