How To Take The Headache Out Of SAP System Monitoring

SAP System Monitoring: Overview

In the past few years, SAP system monitoring has become popular among businesses as a way of ensuring that technical systems run smoothly. Many organizations and enterprises depend on technical systems for the smooth running of their operations.

However, these systems are prone to failures and hitches, which may affect their general performance and reliability. As a result, there is a need for regular monitoring of the systems to ensure they work optimally.

Regular SAP monitoring includes checking the servers, vital applications, connections, and the system’s overall health. Therefore, if you are an IT database administrator, a system engineer, or just interested in running a flawless system, you need to be conversant with SAP system monitoring.

This guide seeks to shed light on everything you need to know about SAP system monitoring, including how to check your system’s performance.

SAP System Monitoring

Defining System Monitoring in SAP

System monitoring in SAP is an activity that involves proactive monitoring of servers, databases, log files, vital applications and CPU utilization to provide an overview of the current status of a technical system.

This system monitoring depends on automated checks done in regular time intervals revolving around four categories; availability, exceptions, performance and configuration. Each of these categories allows for the definition of several metrics and corresponding thresholds as per the managed object.

System monitoring helps increase the system efficiency and general profitability of an organisation. Some of the main monitoring tasks under SAP are:

  • Checking application servers
  • ABAP dump analysis
  • Monitoring lock entries
  • CPU utilization
  • Monitoring update processes
  • Monitoring system log, among others

The daily system monitoring uses codes, Tcodes, to represent tasks some of which are detailed out below:

  • DB13: Database statistics log
  • SM12: Check out for “old” locks
  • SM13: Check any failed updates
  • SM50: View work processes
  • SM51: Check whether all the application servers are up

SAP system monitoring has the following features:

  • Status overview of technical systems, including databases, instances and hosts
  • Visualization of events and metrics with their last reported value and current rating
  • Drill-down capabilities on technical systems from status information to single metrics
  • Jump-in capability to display historical metric values of the selected timeframe

Main uses of system monitoring:

System monitoring helps detect any issues with the system early enough before they become major disruptions. The goals of system monitoring include:

  • Transparency: Revolves around the visibility of the status of the system
  • Single source of truth: Collects all alerts from the system in one place
  • Proactive monitoring: Detects issues before they become critical for the organization

Monitoring a Web Service in SAP

Monitoring a web service may appear like a complex process for a layman. However, with SAP system monitoring, the process is much simple. Here is how you go about starting the web service monitor:
  • Choose CCMS followed by Control/Monitoring then Alert monitor. Or simply call transaction RZ20
  • On the CCMS Monitor sets screen, click and expand the SAP Web Service Monitor Templates
  • Start your Web Service Monitor by double-clicking it in the monitor list

The web service monitor trigger alerts if the web service run time does not function accordingly. A web service monitor alert consists of two areas, the infrastructure and the message processing.

The infrastructure checks the technical systems that are required by the web service infrastructure to operate smoothly. On the other hand, message processing displays important errors from the web service error log.

Checking Performance Using SAP Basis

Checking work performance using SAP monitoring is quite simple; first, select an application server in transaction SM51 and simply log in to it. Now, use the SAP transaction SM50 to show the work process list on that particular server.

The display will show work in different status such as “running,” “stopped,” or “waiting.” Under this monitoring step, if the work process status reflects something else other than running, stopped or waiting, you need to check the issue with that particular process.

This display makes it easy to tell how many work processes are occupied. Additionally, you can tell which database table is being worked on or which ABAP program is running in the work process.

Using this performance display screen, you can tell at a glance some details about a work process such as:

  • The current status of each application server
  • A reason why it is not running optimally
  • Whether the user has restarted it
  • Request run time
  • Logged in users and the clients they have logged on to
  • The running reports

Knowing if an SAP System is Slow

Technical system sow downs often happen at the most inconvenient and unexpected times. However, here is a guide on knowing if your system is slow through CPU utilization to avoid unexpected work disruptions.

An idle CPU utilization ST06 should read between 60-65%, if your readings deviate from this, then your system may be slow and you need to check the following issues:

  • Run OS-level commands -top, this helps you identify the work processes that are taking up many resources
  • Go to either SM50 or SM66 to check for any long-running updates or jobs that may slow down the entire system
  • Check the available lock entries on SM12
  • Go to SM13 to check any Update active status
  • Check and analyse the errors in SM21


Technical systems are the basis of operations in an organisation or business. Therefore, you need to ensure that they are working optimally for improved performance and profitability. You can achieve this by adopting an efficient SAP system monitoring application such as This webapp allows you to monitor your systems through your mobile phone wherever you are.

Leave a Reply

Your email address will not be published. Required fields are marked *

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <s> <strike> <strong>

This site uses Akismet to reduce spam. Learn how your comment data is processed.