Table of Contents

Workload Analysis..................................................................................................................................... 2 STAD..................................................................................................................................... 2 ST03N 3 Performance Tuning.................................................................................................................................. 5 ST055 SE11.. 7

SAP Workload Analysis and Performance Tuning

Workload Analysis

Analyzing a problem with a specific program or transaction

If a problem has been identified, then the first step is to determine where most of the response time is spent. Based on this first step, there are different tools that are used to monitor the ABAP, database, RFCs, etc. Tcode- STAD

Tcode- ST03N

The transaction ST03N is the most important transaction in SAP for a BASIS consultant This transaction provides information on system performance , response times for SAP, Database and frontend , dialog steps information per user , per transaction The information is available as a snapshot , as well as aggregated over days, weeks and months The transaction provides critical data for troubleshooting SAP performance issues There are various profiles for viewing the system performance data , that is , by users , by transactions or by time of the day.

1- Select Service Engineer instead of Expert mode. 2- Click on Transaction Profile -> Standard .
3

If the majority of program or transaction elapsed time is DB time, the first question we need to ask is whether the DB time is high because of a problem in retrieving the data. There are a number of different problems that manifest themselves as high elapsed DB time.

1 If 0DB Time is more than 66% of 0Response Time, problem is in Database Processing.

In general, average sequential read times in ST03N should be less than 5-10 ms.

Performance Tuning:Tcode- ST05

1- In general, a statement that matches the indexes well will take a few ms per row.But, here

after 238 ms, no row is selected.

Click on EXPLAIN

1- Get the local predicates (the WHERE column operator value clauses) from the statement. TABLE ACCESS FULL in figure means that no index on the table is used. Click on tablename j_1IEXCHDR, in orange colour.

Local Predicates

Indexes in Table J_1IEXCHDR~ZIN J_1IEXCHDR~0 MANDT TRNTYP DOCYR DOCNO

MANDT EXDAT WERKS EXGRP TRNTYP STATUS

MANDT EXNUM TRNTYP WERKS EXGRP EXYEAR

In this example, Local PredicatesEXDAT, STATUS are not available in any of the indexes given. So, we will need to create secondary index for EXDAT, STATUS. Oracle will apply predicates to the index columns starting from the top row of an index. With the predicates in the statement, MANDT is the only matching column in these indexes, since EXNUM, which is adjacent to MANDT in J_1IEXCHDR~ZIN, is not in local predicates. Also,in J_1IEXCHDR~0,MANDT and TRNTYP are present in local predicates but DOCYR which is adjacent to TRNTYP is not in local predicates. So, we need to create new index for all local predicates. TCODE- SE11 Click on indexes

Fill in all required fields.

Save, Check & Activate After successful execution of all the above steps, check the sql trace in ST05 and Workload ST03N,which will definitely provide positive result.
8