Analysis Views of ABAP Systems
Definition
You can use the Global Workload Monitor to perform a detailed analysis of both ABAP systems and DSR components. If you select an ABAP system for an analysis, the same analysis views are available to you as in the 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 display 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, double-click the desired view in the Analysis Views subwindow.
Structure
The following table contains the analysis views for ABAP systems. If you follow one of the links in this table, you will be taken to the corresponding documentation for the workload monitor. The operation of the global workload monitor is largely identical; there are only two differences:
- There is no user mode in the global workload monitor. You should therefore ignore the places in which you should set the user mode.
- The transaction code for the global workload monitor is ST03G, while the transaction code for the workload monitor is ST03N.
Analysis View
Meaning
Workload distribution for the individual task types
Most important performance data for all executed transactions; you can also output the data for summarization levels Packages, Subapplications, or Applications
Statistics about workload distribution within a transaction step (activation at transaction level required)
Temporal distribution of transaction steps over a day; this allows you to easily identify periods of higher and lower workload
The 40 transaction steps with the highest response time and database time; the same hitlists also exist for application statistics
Average and maximum memory per dialog step for each transaction and each user
Workload caused by Remote Function Calls on the client- and server-side, broken down by transactions, function modules, or destinations
User Profile andWorkload broken down by users, account numbers, and clients
Volume of data sent and received and the front-end processing times of the individual presentation servers
Statistics about the number and volume of spool requests
Statistics about the distribution of the response times, showing what percentage of the system requests were dealt with in what time (with or without GUI time)
Workload, broken down by table accesses (optional)
Workload for a system caused by requests from other systems, broken down by systems, actions, or users
DB Procedure CallsStatistics about the called database procedures.
Global Workload Monitor start page