Expensive Transactions/Programs in SAP

Workload Monitor
In the workload monitor, you can display the workload in different analysis views which
highlight the workload from a particular perspective. One of these aspects is the question of
which transactions cause which workload.

To display the transactions/programs, please run the following steps:

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 Transaction Profile.
4. Sort according to Response Time Total

Within the above steps, you can select the task type to determine the load for dialog, batch, RFC,
etc. If the performance issue exists on a specific instance, you can select that specific instance;
otherwise, you can select 'Total' to get a view of the system load. You can display more
information for a data record by double-clicking the line for the corresponding transaction
profile. The system opens a second window to display this detailed data. You can also choose
different levels of data aggregation here although the level in the detailed view can be at most
one level beneath the level in the main view. As long as you are displaying daily data for the
current day, the system displays the Single Records button. You can use this button to directly
call the transaction STAD.
To begin the analysis of expensive ABAP programs, examine the single statistical records, which
will give you an overview of the response times of a transaction. For more in-depth analysis, use
SAP Performance Trace for detailed analysis of database accesses, RFCs, and lock operations
(enqueues). If you still cannot find the problem after using these methods, you can use ABAP
trace and ABAP debugger as additional analysis methods. You should also routinely use the
Code Inspector, which has numerous statistical performance checks.