Show TOC

Object documentationInteractive Reports for Systems - Overview Locate this document in the navigation structure


Unlike the system reports (see Interactive Reports for ABAP Systems and Interactive Reports for Java Systems), the reports on the Overview tab page offer you an overview across multiple systems. For each report, one value is displayed for each system; that is, you do not see the development over time of the metrics displayed in these reports, but rather an average value for the selected time period. The metrics are displayed both graphically and in a table.

The reports therefore provide you with a comparison of the most important metrics for the administered systems that are relevant ffor you, so that you can quickly identify outliers for particular metrics. You can then use the respective reports for the individual systems to perform a more detailed investigation.

Note Note

For information about how you can specify the desired systems and the time interval to be displayed, and how to call Interactive Reporting, see Using Interactive Reporting.

End of the note.


The following reports are displayed:

  • System Availability (  Availability   System Availability  )

    Probably the most important metric for systems is their availability. This report shows the system availability; non-availability due to planned downtimes is considered (see also: Managing Work Modes); the availability can have the following values:

    • Available

    • Not available during a planned downtime

    • Unplanned downtime

    • No availability information available. Availability undefined

  • Response Times (  Performance   Response Times  )

    From the point of view of the end user, the response times is one of the most important criteria for system performance. For ABAP systems, the mean response time per dialog step is output. The metric is taken from the CCMS monitoring infrastructure; for more information about the dialog response time, see Dialog Overview Monitor, where this performance value is described in the context of the Alert Monitor.

    For Java systems, the mean response time per servlet, or per Web Dynpro call is output, this represents the mean response time accurately, from a user perspective.

  • ABAP Response Time Distribution (  Performance   ABAP Response Time Distribution  )

    In addition to the average response time, the distribution of the response times is important for judging the system performance. The response time distribution specifies how many dialog steps were performed with which response time. The metric is taken from the ABAP statistics records; for more information, see Displaying Response Time Distribution, where this performance value is described in the context of the Workload Monitor.

  • Java Garbage Collection (  Performance   Java Garbage Collection  )

    During Garbage Collection (GC), the Java Virtual Machine cannot perform any other tasks, such as user requests. GC therefore directly affects system performance, and increased GC load indicates other performance problems. For more information, see How the Local Garbage Collector Works.

    The proportion of all GCs of the total Java process runtime, is displayed. The mean value should not exceed 5% of the total runtime.

  • ABAP Exceptions(  Exceptions   ABAP Exceptions  )

    The report shows the number of errors in the following categories for the selected systems:

    • Dumps (ABAP runtime errors; for more information, see ABAP Dump Analysis).

    • Update Errors; for more information, see Updates in the SAP System (BC-CST-UP)

    • Terminated Jobs; a job can be terminated manually by an administrator, or if a job step contains a program that generates an error (for more information about error analysis for terminated jobs, see Job is Terminated)

  • CPU (  Capacity   CPU  )

    The report shows the CPU load of the hosts of the selected systems. The value is the general CPU load of the host, not the CPU load of a particular system. These performance values are described in the alert monitor under Operating System Monitor.

    In the report, two metrics are shown per system – the average CPU load in the displayed time interval, and the CPU load during the hour of the day during which the CPU load reaches the maximum value.

  • Database Usage (  Capacity   DB Utilization  )

    The report shows the usage and growth of the databases of the selected systems. For more information, see SAP Note 1068204.

  • Logons (  Usage   Logons  )

    The number of simultaneously logged-on users is an important measurement of the usage of a system. The metric is taken from the CCMS monitoring infrastructure; for more information about the number of logged-on users, see Dialog Overview Monitor, where this performance value is described in the context of the Alert Monitor.

    For Java systems, the mean number of active HTTP sessions is displayed, which is a corresponding value for Java systems to the number of users logged on at the same time.

  • User Activity (  Usage   User Activity  )

    In addition to the number of users logged on, information about how many of these users are using the system and how intensively is particularly important for judging the usage of a system. The measure of the intensity of use is the number of dialog steps which the user performs per week in the system. The following values apply:

    User Category

    Number of Dialog Steps per Week

    low activity

    less than 400

    medium activity

    between 400 and 4800

    high activity

    more than 4800

    The report displays the number of users that belong to the categories specified above for the selected ABAP systems.

    Note Note

    The activity is determined by dialog steps per week. If you choose a shorter period, less steps are required for the user to belong to the category.

    End of the note.


Interactive Reporting is part of the Technical Monitoring work center in the Solution Manager.