Optimizing Custom ABAP code for HANA upgrade can be visualized as a three-act structure – Detect, Optimize and Innovate.

What Needs Optimization? Before HANA implementation/migration, an assessment on current code needs to be made in order to understand which objects need the optimization and based on this understanding, a strategy needs to be devised keeping stakeholders in the loop.

Following are the steps –
1. Use SCI inspection on the object list. It can be done tracks wise or across the system.
2. Use SQL Monitor to create snapshots of the system activity.
3. Execute processes and capture the activity on SQL Monitor. Close the snapshots. These snapshots will be fed to SWLT.
4. In SWLT – use SCI and SQLM data and execute. This will give a detailed report on the performance tuning required.

Once the plan is in place, optimization has to begin. Optimization can be further split into two ideas – Accelerate and Extend.

Accelerate: Using ABAP performance tuning principles, make changes in the ABAP Code to boost performance. Example: changes in tables should happen out of a loop if feasible.

Extend: Use HANA features like views and incorporate in ABAP code to make full use of HANA features and functionality. Example: instead of accessing tables, HANA views can be accessed.

What after Optimization? Innovate: Taking a step further, incorporate new use cases that can either improve the existing processes or replace existing process in order to advance overall performance. This incorporates greater involvement of functional resources and extensive analysis before making changes iteratively.