The application statistics allow you to analyze resource consumption in more detail than the workload monitor. Using special calls within the ABAP coding, the system collects statistics for individual parts of an application. While the workload statistics always analyze a complete dialog step, you can use the application statistics to analyze the resources used by an individual function within a dialog step (such as price determination). In some cases, the application statistics can therefore replace an SQL trace.
The statistical data collected by the application statistics is the same as the workload statistics (response time, and so on).
To use the application statistics, corresponding function calls must be implemented in the application programs. No data can be collected for application statistics without these calls. You also need to ensure that the following profile parameter values are set:
stat/as_level = 1
stat/as_collect = 2
You must also have scheduled the collector for the application statistics. In addition, you need to activate the individual components of the application statistics, by calling transaction ST03 and choosing Collector & Performance DB → Statistics Records + File ® Application Statistics.
...
1. Start the Workload Monitor by calling transaction ST03.
2. In the Workload tree, choose the instance and period to be analyzed.
3. Choose Analysis Views → Application Statistics.
4. The system displays the usual output are, in which the requested workload is displayed.
If no application statistics are available for the specified instance or period, the system does not display the icon for application statistics.
The output area contains the desired workload data, broken down by transaction. To display the data broken down by users, double-click a line.
You require a special authorization (profile S_TOOLS_EX) to display user-specific data.
Workload Monitor start page