Consideration before Migrating to SAP HANA

 

1. Which of my ABAP Codes must be changed to avoid potential functional issues when migrating to SAP HANA?
2. Which of my ABAP Codes shall be optimized to ensure good performance?
3. Which of my main business processes have the potential for SAP HANA so that I can spend those up massively?
4. How can I find all this ABAP code easily and do the adaptation efficiently?

 

SAP tools and guidelines help with these issues and enable you to get your custom code ready and optimized for SAP HANA.

 

 

Performance Considerations

Transitioning ABAP Code to SAP HANA – Performance Considerations

 

1. Performance of existing ABAP Code after a migration
• Some code immediately runs faster
• Some code might be negatively impacted and should be revisited
2. Reminder of performance guidelines
• Classical performance recommendations for Open SQL remain valid.
• Some shift priorities, for example, nested selects(higher), indices(lower).

Existing ABAP Code that followed the classical performance recommendations has a good chance of immediately benefiting from SAP HANA.

 

In addition to enabling an existing component, a central goal of SAP HANA is to accelerate performance and to fully benefit from HANA. In many situations, the existing ABAP code might run faster immediately after migration to HANA.

 

However, there can also be situations in which existing code is negatively impacted, especially if the classical performance recommendations were not considered. In general, well-written ABAP code has a good chance of running better immediately on SAP HANA.

 

Runtime Analysis in the ABAP Workbench

 

When discussing the influence of SAP HANA on the performance of an ABAP program, analyzing the runtime behavior can be very helpful.

 

One of the tools to perform such a runtime analysis in the classical SAP GUI is the ABAP Trace (Tcode SAT), which replaces the older Runtime Analysis(SE30).

 

Runtime Analysis and ABAP Trace have the following characteristics:

 

• The functions of the classic runtime analysis(SE30) and the new ABAP Trace(SAT) can be completely used in the SAP HANA context.
• Both tools measure the runtime of processing blocks or single statements
• No database-specific functions are available

 

Runtime Analysis is ABAP Development Tools

 

When using the ABAP Development Tools in Eclipse, an alternative to using the SAP GUI-based ABAP Trace is to use a dedicated perspective in ABAP development tools, called the ABAP profiling perspective. With this perspective, you can also create ABAP Traces. The trace files are the same as those created using the ABAP trace, which means that a trace created using any of the two tools can also be analyzed in the other tool.

 

Depending on which configuration is used to generate a trace, the ABAP profiling perspective provided different views, including the following:

• An overview that’s shown, for example, which percentage of the execution time was spent in ABAP, and which percentage on the database.
• A hit-list of the most time-consuming programs or methods
• Database accesses
• An ABAP trace call tree view to analyze the execution path of a program
• A call timeline view, which visualizes the trace events and time consumed in the form of a diagram.

 

Static code checks to prepare ABAP Code for SAP HANA

 

Before migrating to SAP HANA, a static code analysis should be performed to identify functional issues and potential impairments of performance.

 

 

With the ABAP Code inspector, you can perform a whole range of static functional and performance checks.

 

Code inspector checks to search for potential functional issues

 

Critical Statements: Search for DB Hints and Native SQL