Entering content frameFunction documentation Dialog Overview Monitor Locate the document in its SAP Library structure


You can use this monitor to check the most important values for the SAP dialog system and the number of users logged on, broken down by application server:

This graphic is explained in the accompanying text


You can find a more detailed display of the relevant times for the dialog system including the response times at the frontend in the Entire System monitor, Dialog subtree.


The monitor contains the current values for the following attributes:

This monitoring tree element (MTE) provides information about the response time of the dialog service. The dialog response time contains the entire processing time that was required for the processing of an SAP R/3 dialog step, including the database processing time. The time for the network transfer and the frontend processing time are not included. The values displayed here are average values of the dialog steps.

The statistics displayed here may contain minor differences from those in the analysis method that is assigned to the MTEs. This deviation is due to the finer granularity of the analysis method statistics. The averaging of the values in the Alert Monitor can lead to minor differences in values.

An alert here indicates a performance problem in your system. The problem can have many different causes, and it is therefore necessary to perform a thorough analysis. You should first ensure that the application server is not overloaded. This is measured, for example, using the statistics for CPU performance, system paging, and dialog work processes. Another possible bottleneck is the database. You should ensure that the database performance is adequate.

If the dialog response time generates an alert, but the response time for the standard transaction (see Standardized Response Time) is not reporting any problems, you should first check the number of users logged on (Users Logged On). If there are only a small number of users, the user of very resource-intensive transactions can, in extreme cases, significantly increase the response time. If this is the case, there is often no serious performance problem.

The network time is the time used in the network during the first data transfer from the frontend to the application server and during the last data transfer from the application server to the frontend. It therefore does not include the "roundtrips" (communication steps during a dialog step).

This monitoring tree element displays the dialog response time of the standard transaction. This standard transaction simulates the normal workload of a transaction by accessing data on the database and executing a range of ABAP function modules.

You can use the standardized workload to compare the performance of the dialog system under uniform conditions. In this way, you can avoid effects that would provide distorted dialog response times on certain servers (for example, if only a small number of users are active, and at least one user is using long-running transactions).

When they log on, users are automatically distributed to the individual servers depending on the dialog quality (response time and number of users logged on) and in accordance with the logon groups that you have created.


To start the monitor, follow the procedure below:

  1. Start the Alert Monitor using transaction RZ20 or choose CCMS ® Control/Monitoring ® Alert Monitor.
  2. On the CCMS Monitor Sets screen, expand the SAP CCMS Monitor Templates set.
  3. Start the Dialog Overview monitor from the list by double clicking it.

The Structure linkworkload monitor is set as the analysis method for the dialog response time and the network time. You can use this to analyze performance problems in great detail, down to the level of individual dialog steps of particular transactions.

For the Number of Users Logged On, the analysis method displays a list of the users that are logged on, broken down by application servers on the Currently active users screen - including information about the terminals used, transactions used, and number of open sessions.

Leaving content frame