Monitoring SAP system is a must to make sure that everything is running as perfectly as possible. Any of these problems, which might suggest a small problem might very soon creep up to be a big problem. So it is always recommended to monitor SAP sytems everyday and it’s even better if you share these reports to the entire group of SAP technical members working in your project to make sure that they can identify something which was not identified by you or other team members.
Here is the list of things which should be monitored in SAP Systems frequently.
- Check SAP Process Overview (SM51/SM50/SM66) : Use these transactions to monitor work processes which are running for a long time. If you see any proceses running in a Dialog mode for a longer time, then inform and find out from the users what they are trying to do.
- Logged in users in AL08/SM04: This is used to check the no of users logged in the system, Make sure the the users are evenly distributed across all instances, if you see a lot more users in one instance than the other, there is something wrong, check the load balancer settings or other options.
- Spool Requests: Check the no of Spool requests created each day, there shouldn’t suddenly be a spike in the process unless there is a new process in place.
- Lock Objects SM12: check this transaction for any locked objects. if there are any locks for more than a day, than that is a problem, find the user or the programmer to dig more further to see if this is really required.
- Update requests on SM13: There should not be more than 10 updates at a given time.
- System Logs SM21: Check the logs frequently for any abnormal trends, find corresponding system dumps(ST22) and contact the necessary developers or check OSS Notes.
- Check Background Jobs: SM37 is used to check the background jobs. Check for any jobs running for a long time, check for past run time of the same jobs to see if there was a sudden increase in the duration.
- SAP Buffers: User ST02 to check for the SAP Buffers, The “current use” should not be near the value of “in memory”.
- Workload Analysis: Use ST03 is used to check the workload analysis of SAP Instance.
- Operating System Monitor: Use ST06, to check the Operating system status. Check the utilization of system resources, check the event logs. If CPU utilization is higher than 60%, find the programs and transactions and take corrective measures.
- ST11 to dispay Developer traces.
- St22 for ABAP dump analysis
- St04 /ST02 for Database Analysis to monitor expensive Statements, monitor database performances.
- WE02 for failed IDocs.
Additionally, Using OS Monitor(ST06)
OS Montior Fetches the data using service SAPOSCOL and it displays CPU Utilization, Memory Utilization and disk response time.
The CPU idle time should not be less than 30% , If it is below 30% we can consider the following.
- The ABAP programs are expensive with multiple conditions and endless loops.
- The CPU is not sufficient to handle the load because the hardware is not procured as per sizing.
- Probably the hardware is procured as per sizing but the number of users grown dynamically (300-600). In this scenario we advice to deploy additional instances.
- If the programs are expensive then refer to development team. It also displays the memory installed on the machine, Memory available(Free) along with the SWAP space. Ensure that physical memory free is available to handle the user requests. If not memory bottleneck.