Big4GuyWelcome to Big4Guy.com. Big4Guy is an online resource where I will share with you the latest news, insights, knowledge and some experiences as a Big 4 consultant. We will discuss some of the important issues which organisations are facing today in the areas of information security, security and controls in SAP R/3, Oracle Applications, J.D.Edwards, Peoplesoft and various other ERP's. You will also find information on latest complaince regulations like Sarbanes Oxley, Basel II and so on. Big4guy will also attempt to provide valuable resources for individuals interested in examinations the CISA, CISM, CISSP, PMP and various other security certifications considered essential for entry in any Big 4 accounting, auditing and consulting firms. You are invited to post your comments and viewpoints to posts here. I sincerely hope this online journal will be useful to everyone from a budding student to a professional in the accounting, auditing, management and consultancy professions.
|
Because of the inherent complexity of the SAP ERP system, system performance depends upon many factors. Factors such as the operating system, network, database and SAP configuration itself contribute to the system performance. SAP system comes with tools for system performance monitoring. Several SAP transactions are available to monitor the performance. Some of the important ones are mentioned below:
1. ST03N - Workload Monitor
2. SM50 / SM66 - Work Process Overview
3. ST06 - Operating System Performance
4. ST04 - Database Monitor
5. ST02 - Setup Buffers
The above are some of the central monitoring transactions used in SAP R3 performance analysis. To move a bit in detail, transaction ST06 can provide valuable information on the operating system performance at the server level. CPU usage, memory allocation etc can be looked at in detail using this transaction. SQL request on the underlying system database can be monitored using ST04 i.e. the database monitor. In real life instances, many factors can be responsible for slow SAP system performance. The root cause normally is not that apparent. In some cases due to peak workload, even system administrators will not be able to call transactions. In such rare cases, it is better to use tools at the operating system to solve performance problems.
Related Posts
Logistics Information System in SAP
Concept of Release Procedures in SAP MM
Access Authorization Check SU53
ABAP Workbench SAP
No Comments for this post yet...
| Mon | Tue | Wed | Thu | Fri | Sat | Sun |
|---|---|---|---|---|---|---|
| << < | > >> | |||||
| 1 | ||||||
| 2 | 3 | 4 | 5 | 6 | 7 | 8 |
| 9 | 10 | 11 | 12 | 13 | 14 | 15 |
| 16 | 17 | 18 | 19 | 20 | 21 | 22 |
| 23 | 24 | 25 | 26 | 27 | 28 | 29 |
| 30 | ||||||