Scribd
Upload
138 views40 pages

ABAP Performance Tuning

The document discusses techniques for improving the performance of ABAP programs, including optimizing SELECT statements, avoiding SELECT *, using table keys in WHERE clauses, limiting joins to two tables, and using internal tables instead of database tables when possible.

Uploaded by

app bundle
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
138 views40 pages

ABAP Performance Tuning

The document discusses techniques for improving the performance of ABAP programs, including optimizing SELECT statements, avoiding SELECT *, using table keys in WHERE clauses, limiting joins to two tables, and using internal tables instead of database tables when possible.

Uploaded by

app bundle
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 40

Uplatz 1

➢ ABAP Performance Tuning

Select Statements of Open SQL

© SAP AG
ABAP Performance Tuning

➢ ABAP Runtime Analysis must be checked to measure/compare program


performance/runtime if program has multiple inefficient databases
selects or complicated internal table operations.

➢ Report Performance & Runtime Analysis - Transaction code :- SE30

➢ SQL Trace - Transaction code :- ST05


ABAP Performance Tuning

➢ Avoid 'SELECT *', especially in tables that have a lot of fields. Use SELECT
A B C INTO instead.

➢ Field-groups can be useful for multi-level sorting and displaying.

➢ Use as many table keys as possible in the WHERE part of your select
statements

➢ Avoid joins using more than 2 tables

➢ Use the SELECT SINGLE command whenever possible

➢ Use “SELECT INTO TABLE” rather than “SELECT INTO CORRESPONDING


FIELDS OF TABLE”
ABAP Performance Tuning

➢ Always select into an internal table, except when the table will be very
large (i.e., when the internal table will be greater than 500,000 records). Use
“Up to N Rows” when the number of records needed is known

➢ LOOP AT ITAB INTO WORKAREA WHERE K = ‘XXX’ should be used


instead of LOOP AT ITAB INTO WORKAREA / CHECK ITAB-K = ‘XXX’.

➢ Nested Select is not used instead “Inner Join” and/or “For all Entries” is used.

➢ Delete adjacent duplicate entries from internal table before selection from
database table using “ FOR ALL ENTRIES” statement

➢ For copying internal tables use ‘=’ operator instead of Looping & Appending
ABAP Performance Tuning

Transaction Code for Performance Tuning :-

➢ SE30

➢ ST05

➢ ST01
➢ ST22

➢ ST12

➢ SAT
ABAP Performance Tuning

Transaction
code :- SE30

Click Execute
Button
ABAP Performance Tuning

OUTPUT

Click Back
Button
ABAP Performance Tuning

Transaction
code :- SE30

Click Evaluate
Button
ABAP Performance Tuning

OUTPUT
ABAP Performance Tuning
ABAP Performance Tuning
Native SQL
ABAP Performance Tuning
ABAP Performance Tuning
ABAP Performance Tuning
ABAP Performance Tuning
ABAP Performance Tuning
ABAP Performance Tuning
ABAP Performance Tuning
ABAP Performance Tuning
ABAP Performance Tuning

Example Program
ABAP Performance Tuning
ABAP Performance Tuning

Example Program
ABAP Performance Tuning

Example Program
ABAP Performance Tuning
ABAP Performance Tuning

Example Program
ABAP Performance Tuning
ABAP Performance Tuning
ABAP Performance Tuning
ABAP Performance Tuning
ABAP Performance Tuning
ABAP Performance Tuning
ABAP Performance Tuning
ABAP Performance Tuning
ABAP Performance Tuning
40
Thank You
Upla
tz

You might also like