HANA Code Inspector on a Different System
  • 3 Minutes to read
  • Dark
    Light
  • PDF

HANA Code Inspector on a Different System

  • Dark
    Light
  • PDF

Panaya allows you to prepare for your HANA migration before upgrading your SAP landscape to HANA.

Note
Before performing any of the options below, please verify you meet the prerequisites described here.

 

Option 1 - Run on a Copied System

  1. Create a copy of your SAP system that contains the source code. Typically, this is the upgraded development system.

  2. Verify this system meets the requirements of SAP note 1912445 - ABAP custom code migration for SAP HANA - recommendations and Code Inspector variants for SAP HANA migration. The copied system must be on at least
    one of the following NetWeaver product versions and SP levels:

    SAP NetWeaver 7.02 as of SAP_BASIS SP14 or higher
    SAP NetWeaver 7.31 as of SAP_BASIS SP09 or higher
    SAP NetWeaver 7.40 as of SAP_BASIS SP02 or higher

    If it is not, it must be upgraded to meet the above requirement.
     

  3. Use the newly created system to Run the HANA SAP Code Inspector in offline mode.

  4. Proceed to export the Excel files below. 

Important!
The limit for exporting Code Inspector variants for SAP HANA to an Excel spreadsheet format is 65,536 lines.
For files containing more than 65,536 lines, please use simple *.txt format.
In such cases, save the file as *.txt instead of *.xls, with the Tab character as a delimiter.



Option 2 - Use Remote Static Checks

  1. Read the following SAP guide - Executing Remote Static Checks in Context of HANA Migration
  2. Implement note 2011106on the test system mentioned in the guide and follow the four procedures in the guide. (Do not delete the data from the Test system at this time, only after step 4 below has been completed)
    • A - Preparing Data Export from the Source System
    • B - Downloading Data from the Source System - Non-RFC option
    • C - Uploading Data into the Test System - Non-RFC option
    • D - Executing Checks in the Test System

      To further clarify steps A and B, there are two SAP systems -

      The source SAP system needs to run the Panaya code extraction (with a low NetWeaver version like 7.0). Here no check variants are set as the low NetWeaver system is not HANA compatible. SAP note 2270689, including manual activities, must be implemented in the source system.

      Another SAP Test system * (with a high NetWeaver like 7.40 SP8) for Executing Remote Static Checks in Context of HANA Migration using the SAP instructions below.
      For the SAP Test system mentioned above, follow these steps.

      You will need to have access, within your system landscape, to an SAP system with SAP NetWeaver Release 7.40, SP8 (or higher); this is the Test system mentioned in the SAP article, Executing Remote Static Checks in Context of HANA Migration.

      This Test system must meet these requirements -
    • Implement note 2011106 mentioned in the SAP guide – on the SAP test system (NW 7.40 and above)
    • Prerequisites mentioned here and the HANA check variants need to be set. Implement SAP note: 1912445 - ABAP custom code migration for SAP HANA - recommendations and Code Inspector variants for SAP HANA migration and the referenced note 1935918, which creates the HANA check variants.

      * If you are in the process of an S/4 Hana conversion project, you can also use the same 7.52 NetWeaver Central Check system that is a prerequisite as your Test system.

  3. On the Test system, run the SAP HANA code inspector as described in the following article -
    Run the HANA SAP Code Inspector in offline mode.
  4. Proceed to export the Excel files (below) and provide them when you run the Panaya extractor on the Source system (low NetWeaver such as 7.00).


Exporting the Excel Files

  1. Under Inspection, click on
  2. Select the relevant FUNCTIONAL_DB execution and click
  3. Click the Display button
  4. Select to view the Results (Shift+F6)
  5. Select to view the Results Table (Ctrl+Shift+F8)
  6. Select to Change Layout
  7. Configure the ALV layout to appear as shown below -
  8. Save the ALV layout for future use
  9. Select to Export Spreadsheet and save it on your local workstation as an Excel (in Office 2007 XLSX Format)
  10. In Excel, select the entire spreadsheet range. Then, select the Data tab and Remove Duplicates. Select all columns and click OK.
    The final XLS file should be in the same column order and naming as provided in this spreadsheet example.
  11. If you have less the 65536 records you can save the XLSX file to XLS (Excel 97-2003 Workbook).  If you have more than 65536 records, do not save it in XLS format, as it will truncate your data, but instead from excel save it as a Text Tab delimited .txt file, for example:
  12. Repeat for FUNCTIONAL_DB_ADDITION and PERFORMANCE_DB variants
  13. Proceed as described in Custom Code Extraction Guide. Use the Choose from excel files option for the HANA SAP Code Inspector Execution Mode.