Optimizing Conventional ABAP code: Part 1

Business Scenario:

The functions of classic Runtime Analysis (SE30) and new ABAP trace (SAT) can be completely used in HANA context.

The new ABAP trace replaces the classical runtime analysis.

Both tools measure runtime of processing blocks (methods, functions, subroutines) or single statements.

No database specific functions are available.

Code Inspector

The below existing rules and guidelines checked by code inspector are still valid in HANA context:

• SELECTS in LOOPs across modularization units
• Problematic SELECT* statements (where less than a certain percentage of the fields are subsequently used)
• Find SELECT…..FOR ALL ENTRIES statements that can be replaced by a join

Use SQL trace (ST05) to

• Display records of all database access (including SQL calls over a secondary database connection)
• Detect redundant/identical SELECT statements
• Locate database related performance issues
• Display database execution plan for statements (SAP HANA execution plans)