" 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."
SAP ABAP SELECT-OPTIONS to have Upper and Lower Case
SELECT-OPTIONS by default displays all characters in UPPER CASE. This happens once the user hits the ENTER Key. If you wish to force Lower Case on the field values entered in the SELECT-OPTIONS fields use the addition LOWER CASE.
The Syntax is as follows.
SELECT-OPTIONS: s_ernam for vbak-ernam LOWER CASE.
The code is as follows.
REPORT ZEX_SELECTOPTIONS.
Tables: VBAK, VBAP.
Data: int_vbak type vbak occurs 0 with header line.
Select-options: s_vbeln for vbak-vbeln , s_auart for vbak-auart, s_ernam for vbak-ernam LOWER CASE.
Select * INTO int_VBAK from VBAK where VBELN in s_vbeln. APPEND int_VBAK. CLEAR int_VBAK. ENDSELECT.
loop at int_vbak. Write:/ int_vbak-vbeln, int_vbak-AUART. endloop.
write:/ s_vbeln-low, s_auart-low, s_ernam-low.
In the above example, s_ernam has the addition of LOWER CASE where as s_auart does not have the addition. Once you execute the program the output will show auart in upper case where as ernam in the case that has been entered by the user as it is.
Not: If TYPE addition is used to refer data types from the ABAP dictionary, then you cannot use the LOWER CASE addition. If you enter the following data
Sales Order 4969 Order Type or Created By JohN
Then the Output would be as follows.
Select Options in SAP ABAP 4969 OR 4969 OR JohN
This is because s_ernam has the LOWER CASE addition where as s_auart does not have the addition.
SAP ABAP POPUP Function Module to Confirm Data SAVE
In ABAP if you wish to POP up a Dialog BOX asking the user if the data needs to be saved. Basically this function module POP-UP a dialog box asking for confirmation to SAVE the data, or proceed without saving.
The Parameters
START COLUMN and START ROW define the position of the POP-UP Dialog BOX.
Find the code below.
REPORT ZEX_POPUPTOCONFIRMDATALOSS .
Data: d_ans(20).
CALL FUNCTION 'POPUP_TO_CONFIRM_DATA_LOSS' EXPORTING DEFAULTOPTION = 'J' TITEL = 'Dialog for Data' START_COLUMN = 25 START_ROW = 6 IMPORTING ANSWER = d_ans .
* Based on the answer you can select the step in the flow logic. Write:/ 'Answer =', d_ans.
Based on the User Input the logic in the program can take the desired flow.
SAP ABAP Selection Screen Making Fields Obligatory
In ABAP Selection Screen you can make certain fields OBLIGATORY. This can be done by using the addition OBLIGATORY. Please find the syntax below.
SELECT-OPTIONS: s_vbeln for vbak-vbeln OBLIGATORY
If the addition OBLIGATORY is used the user is forced to enter values in the respective fields before proceeding further. A question mark appears in the selection screen for the SELECT-OPTIONS field.
Find the code below.
REPORT ZEX_SELECTOPTIONS.
Tables: VBAK, VBAP.
Data: int_vbak type vbak occurs 0 with header line.
Select-options: s_vbeln for vbak-vbeln OBLIGATORY.
Select * INTO int_VBAK from VBAK where VBELN in s_vbeln. APPEND int_VBAK. CLEAR int_VBAK. ENDSELECT.
loop at int_vbak. Write:/ int_vbak-vbeln, int_vbak-AUART. endloop.
SAP ABAP SELECT-OPTIONS restricting entry to single fields
In the selection screen if the entry is to be restricted to single field then the following Syntax can be used.
SELECT-OPTIONS s_vbeln FOR VBAK-VBELN NO INTERVALS
If the above statement is used in the program then only one field appears in the Selection-Screen. You can also use NO-EXTENSION in case you want to suppress the push button for multiple selection. In that case the syntax would be as follows.
SELECT-OPTIONS: s_vbeln for vbak-vbeln NO-EXTENSION NO INTERVALS
Find the code below.
REPORT ZEX_SELECTOPTIONS.
Tables: VBAK, VBAP.
Data: int_vbak type vbak occurs 0 with header line.
Select-options: s_vbeln for vbak-vbeln NO-EXTENSION NO INTERVALS.
Select * INTO int_VBAK from VBAK where VBELN in s_vbeln. APPEND int_VBAK. CLEAR int_VBAK. ENDSELECT.
To restrict entry to only one row you can use the following Syntax.
SELECT-OPTIONS s_vbeln FOR VBAK-VBELN NO-EXTENSION
If NO-EXTENSION is used then the Push Button for multiple selection does not appear on the selection screen and hence multiple selections are not available for the User.
Find the code below. REPORT ZEX_SELECTOPTIONS. Tables: VBAK, VBAP. Data: int_vbak type vbak occurs 0 with header line. Select-options: s_vbeln for vbak-vbeln NO-EXTENSION. Select * INTO int_VBAK from VBAK where VBELN in s_vbeln. APPEND int_VBAK. CLEAR int_VBAK. ENDSELECT. Loop at s_vbeln. WRITE: / 'SIGN:', s_vbeln-sign, 'OPTION:', s_vbeln-option, 'LOW:', s_vbeln-low, 'HIGH:', s_vbeln-high. Endloop. loop at int_vbak. Write:/ int_vbak-vbeln, int_vbak-AUART. endloop.
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.
