Performance Tunning 4j13z

Performance Tuning Writing a program is not that tough, but the tough part is how optimize is that code is. Means, if the code is not optimized it might fail in future and create a big trouble for business. Therefore, code optimization or performance tuning is very important part of ABAP code. A performance optimized ABAP program reduces the load on the system, Executes faster thus saving the time of the end and increasing the productivity. There are several ways to measure or do the performance tuning in SAP abap. 1)

Database operation tuning

2)

Application code issues

3)

Performance Analysis

4)

Runtime analysis

Database Operation Tuning Encountered during dealing with ABAP Dictionary Objects while selecting data from the database table, we can follow the following rules while dealing with ABAP Dictionary Objects. 1.

Do not use SELECT * from….ENDSELECT. While selecting data from any table, these acts like a loop and fetch all records. For few fields we can specifically SELECT only those fields.

2.

Use WHERE clause in your SELECT statement to get specific records.

3.

Always try to use all the primary keys of the table in the WHERE clause to get best result.

4.

In case not all the primary keys are available, use UP TO 1 ROWs.

5.

Avoid using NESTED SELECT statement, SELECT within Loops.

6.

Avoid using INTO CORRESPONDING FIELDS OF TABLE instead use INTO TABLE.

7.

Use FOR ALL ENTRIES in your SELECT statement to retrieve the matching records at one shot , and before using FOR ALL ENTRIES always check whether the table is initial or not.

Created By: Rounak Ghodke.

Page 1

Avoid using ORDER BY in SELECT statements (instead, sort the resulting

8.

internal table); because this may add additional work to the database system which is unique, while there may be many ABAP servers. Avoid Executing a Select multiple times in the program. Instead of that, we

9.

can create a subroutine and use that multiple times if required. 10.

For SELECT from multiple tables try to search for any combine VIEW, if not available then go for Inner .

11.

While reading data from internal tables, always sort the table and try to use BINARY SEARCH.

Application Code Issue The main important entity of abap code is internal tables. Whatever data we select form database tables, has to store in internal table first and then we process them as per clients requirement. Internal tables are of different types. Each internal serves a particular task to improve performance of code. 1. Standard table can be accessed by Index operation (primary key), we should sort them by the key and use BINARY SEARCH. 2. Sorted table serves the same purpose of Standard table after applying sort. 3. Hash Table is different type of table. It can only accessed by a unique key field. Generally while declaring an internal table we have to consider few points to optimize our code: 1. Declare a table without header line. Make the table declaration more in general. Declare work area separately to use that table. 2. While declaring a table, specify the table type as Standard/sorted/hashed. 3. Do not use INTO CORRESPONDING FIELDS, use APPEND work area to internal table. During coding, we have to follow the below points: 1.

Don’t use nested loop. Try to use READ inside LOOP.

2.

For specific record, you should use LOOP with WHERE clause.

3.

Don't delete table entries inside a LOOP. Always flag that entry inside that LOOP or CLEAR the key field value of that table. After the LOOP delete that table where key field is SPACE.

Created By: Rounak Ghodke.

Page 2

4.

Use field symbols instead of modifying any entry.

5.

Check SY-SUBRC value after every command statement.

6.

After appending always clear work area.

7.

Follow the naming standards of projects.

8.

Use syntax check and pretty printer.

9.

If similar code need to use multiple times, it is better to create sub routine and use it multiple times.

Performance Analysis Performance analysis performs a wide range of functions used to supervise and examine the performance of the system while accessing databases, performance locking activities and remotely calling reports or transaction. It helps to analyze a trace file individually. To access performance analysis, go to SAP Easy Access screen in that select SAP Menu Tools SQL Trace or enter ST05 T-Code in the command fields and press enter. When Performance Analysis Screen appears the following types of traces are available on its screens.    

SQL Trace: Keeps Track of the various database accesses of reports and transactions. Enqueue Trace: Monitors the locking system. RFC Trace: Provide information about the remote function calls Table Buffer Trace: Monitors the database calls of reports and transactions made through the table buffer.

Runtime Analysis It is the tool used to trace the time duration and performance of the ABAP Source code. To open the initial screens of ABAP Runtime Analysis go to SAP Easy Access screen in that select. SAP Menu  Tools  ABAP Workbench  Test  Runtime Analysis or enter SE30 T-Code in the command field and press enter. Created By: Rounak Ghodke.

Page 3

ABAP Runtime Analysis screen allows you to display the following     

The execution time of each statement in a program The tables accessed at run time The execution time of all statements, you can also group the statements based on the type of command. The execution time of each statement in the order in which they have been executed The level of nesting of statements within subroutines

Tools Used for Performance Tuning 

ST05 is the performance trace. It contains the SQL Trace, RFC, Enqueue and buffer trace. Mainly the SQL trace used to measure the performance of the select statements of the program.



SE30 is the Runtime Analysis transaction used to measure the application performance.



SAT transaction is the replacement of the outdated SE30. Provides same functionality as SE30, with some additional features



ST12 transaction (part of ST-A/PI software component) is a combination of ST05 and SAT. Very powerful performance analysis tool used primarily by SAP One of the best tools for static performance analyzing is Code Inspector (SCI). There are many options for finding common mistakes and possible performance bottlenecks.



Created By: Rounak Ghodke.

Page 4