Quick Tip: 3 Methods for Identifying and Remediating Custom ABAP Code Issues when Migrating SAP BW to SAP HANA
- by Christian Savelli, Senior Manager, COMERIT
- April 18, 2016
SAP HANA in-memory technology brings improved performance to standard SAP Business Warehouse (SAP BW) processes. Custom development of ABAP code, however, may require some tweaking to optimize its performance and properly harness the power of SAP HANA. This is especially true for custom ABAP programs that were originally designed to run on older versions of SAP BW based on relational database technology. Learn three ways to execute the analysis of custom ABAP code when migrating an SAP BW application to an SAP HANA database, and how to quickly pinpoint potential issues and find solutions to remediate them.
SAP Code Inspector and SAP Business Warehouse (SAP BW) ABAP Routine Analyzer are tools available for the development team to identify and remediate in advance potential issues in custom ABAP code during an upgrade or migration from SAP BW to SAP HANA. These tools are provided by SAP and allow checks to be performed at the syntax level, assessing custom code adaptability to the new SAP HANA platform, including Unicode evaluation. The logs generated from these tools include detailed explanations of custom ABAP issues identified, their severity levels, as well as suggestions on how to remediate them.
Reading this article, you will learn how to:
- Identify opportunities to enhance custom ABAP code for SAP HANA
- Use the Code Inspector tool to pinpoint potential ABAP issues during an SAP BW to SAP HANA migration project
- Remediate impacts caused by changes to standard structure RRRANGESID
A crucial step during a migration of SAP Business Warehouse (SAP BW) to an SAP HANA database is the analysis of existing ABAP code. As a result of such analysis, potential performance issues can be identified well in advance and remediated by adapting data transformation routines and other custom code to make optimal use of SAP HANA’s in-memory technology.
Besides performance, another major reason for analyzing ABAP code during a migration to SAP HANA is the risk that custom development may simply break, yielding syntax errors after the SAP BW application is upgraded to newer versions (7.4 or higher). This may occur when its syntax relies on Data Dictionary elements whose definitions have been modified by SAP. This is the situation, for example, for Data Dictionary structure RRRANGESID. In this case, its HIGH and LOW field definitions were changed (in the 7.4 of SAP BW release) from being based on CHAR type to SSTRING type. Such a change can easily force remediation activities on custom ABAP code relying on the former CHAR-based definition.
I show three techniques for performing checks and identifying enhancements to custom ABAP code that are required during a migration of SAP BW to an SAP HANA database. I also give an overview of some typical errors and warnings that are issued during such checks, as well as ways to remediate them, including code samples. It is assumed that the original SAP BW system being upgraded is already Unicode-compliant, so no changes to Unicode-related code are discussed.
Identifying the Required ABAP Code Enhancements
There are three methods that you can use to identify the ABAP code enhancements required during an SAP HANA migration project. They are:
- ABAP program ZBW_ABAP_ANALYZER (SAP Note 1847431)
- The Code Inspector tool (accessed via transaction code SCI)
- Program search (in this case, searching for programs that use standard structure RRRANGESID)
Would you like to see this full item?