" 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."
In ABAP HIDE is an important technique and is used in interactive reporting. The HIDE statement defines the information that needs to be passed to the subsequent lists.
We will see a very simple example of the HIDE statement to understand the concept. In this example we will select the Header data of all the sales order into an internal table. We will then display only the customer numbers. Once the user clicks on the customer number the Following information will be displayed as the Secondary list.
CUSTOMER NUMBER PURCHASE ORDER NUMBER SALES ORDER NUMBER SALES ORGANIZATION DISTRIBUTION CHANNEL DIVISION
To achieve this we will hide the above mentioned fields using the HIDE statement. The Program is given below.
REPORT ZEX_HIDE . *&---------------------------------------------------------------------* *& ABAPLOVERS THE HIDE STATEMENT *&---------------------------------------------------------------------*
* Tables TABLES VBAK. * Internal table DATA int_VBAK LIKE VBAK OCCURS 100 WITH HEADER LINE. * Processing data START-OF-SELECTION.
SELECT * FROM VBAK INTO TABLE INT_VBAK.
LOOP AT int_vbak. WRITE / int_vbak-kunnr HOTSPOT ON. HIDE: int_VBAK-VBELN, int_VBAK-KUNNR, int_VBAK-BSTNK, int_VBAK-VKORG, int_VBAK-VTWEG, int_VBAK-SPART.
ENDLOOP.
* Secondary List AT LINE-SELECTION. WRITE: / 'Sales Order Details', int_VBAK-KUNNR, int_VBAK-BSTNK, int_VBAK-VBELN, int_VBAK-VKORG, int_VBAK-VTWEG,
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.
No comments:
Post a Comment