Entering content frameObject documentation Analysis Views for SAP R/3 Systems Locate the document in its SAP Library structure

Definition

You can perform a detailed analysis of the workload of SAP R/3 Systems and non-SAP R/3 systems with the global workload monitor. If you select an SAP R/3 System for analysis, the same analysis views are available to you as in the Structure linkSAP R/3 workload monitor.

An analysis view is a particular aspect of the workload. Depending on which aspects of the workload you are interested in, you can output various workload parameters, sorted by different sort criteria (such as by users, transaction steps, RFC destinations, and so on).

Use

To activate a particular analysis view, choose the desired view in the Analysis Views subscreen by double clicking it.

Structure

The following table contains the analysis views for SAP R/3 Systems. If you follow one of the links in this table, you will be taken to the corresponding documentation for the SAP R/3 workload monitor. The operation of the global workload monitor is largely identical; there are only two differences:

Analysis View

Meaning

This graphic is explained in the accompanying text Structure linkWorkload Overview

Workload distribution for the individual task types.

This graphic is explained in the accompanying text Structure linkTransaction Profile

Most important performance data for all executed transactions; you can also output the data for summarization levels Packages, Subapplications, or Applications

This graphic is explained in the accompanying text Structure linkApplication Statistics

Statistics about workload distribution within a transaction step (activation at transaction level required)

This graphic is explained in the accompanying text Structure linkTime Profile

Temporal distribution of transaction steps over a day; this allows you to easily identify periods of higher and lower workload

This graphic is explained in the accompanying text Structure linkHitlists

The 40 transaction steps with the highest response time and database time; the same hit lists also exist for application statistics

This graphic is explained in the accompanying text Structure linkMemory Usage Statistics

Average and maximum memory usage per dialog step for each transaction and each user.

This graphic is explained in the accompanying text Structure linkRFC Profiles

Workload caused by Remote Function Call, broken down by transactions, function modules or destinations

This graphic is explained in the accompanying text Structure linkUser Profile and

This graphic is explained in the accompanying text Structure linkAccount Statistics

Workload broken down by users, account numbers and clients

This graphic is explained in the accompanying text Structure linkFrontend Statistics

Sent/received volume of data and the frontend processing time of the individual presentation server

This graphic is explained in the accompanying text Structure linkSpool statistics

Statistics about the number and volume of spool requests

This graphic is explained in the accompanying text Structure linkResponse Time Distribution

Statistics about the distribution of the response times, showing what percentage of the system requests were dealt with in what time (with and without GUI time)

This graphic is explained in the accompanying text Structure linkTable Access Statistics

Workload, broken down by table accesses (optional)

This graphic is explained in the accompanying text Structure linkLoad from External Systems

Workload for a system caused by requests from other systems, broken down by systems, actions, or users

This graphic is explained in the accompanying text DB Procedure Calls

Statistics about the called database procedures.

This graphic is explained in the accompanying text Global Workload Monitor first page

 

 

Leaving content frame