" 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."
To get a list of all the BAPIs in the system the following BAPI can be used.
BAPI_MONITOR_GETLIST ____________________________
The following Parameters should be passed to the above mentioned BAPI
Object type Release /Reference Release to Display Display Potential BAPIs Display New BAPIs in Release Display BAPIs from Previous Releases Release Status of BAPIs Release Status of Function Modules
The BAPI returns a table with the following information.
Object type, Object name, Method name of BAPI, Function module name, Application component ID, Release at creation, Author, Last changed on, Last changed by, R/3 System, name of R/3 System, Application area or BAPI Work Group reponsible, Interface object type, Release status of BAPI methods, Release status of function module, Release in which object type was set as obsolete, Documentation on function module exists, Documentation for business object exists, Message type, Object type component, Description.
Example:
REPORT ZEX_BAPI_GETLIST .
* Parameters-----------------------------------------------------------* Parameter: p_ojtpe like BAPIMONIT-OBJTYPE default '*', p_rel like BAPIMONIT-CREA_REL default SY-SAPRL, p_poten like BAPIMONIT-OPTSEL default ' ', p_newbp like BAPIMONIT-OPTSEL default 'X', p_oldbp like BAPIMONIT-OPTSEL default 'X', p_relbp like BAPIMONIT-OPTSEL default '*', p_relfun like BAPIMONIT-FUNCREL default '*'.
* Data Declaration-----------------------------------------------------* Data: d_ret like BAPIRET2.
* Internal Table Declaration-------------------------------------------* Data: int_comsel like BAPIMONCOM occurs 0 with header line, int_orgBP like BAPISRCSYS occurs 0 with header line, int_selbap like BAPIMONSTR occurs 0 with header line.
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