Select language:

Executing Remote Static Checks in Context of HANA Migration

Usage Scenario
Restriction This topic does not address the common usage of remote static checks in the Code Inspector. It focuses rather on static checks that are relevant in the context of HANA migration.

Let’s imagine that you, as an SAP customer, are faced with the following situation:

Within your system landscape, you have access to an SAP system with SAP NetWeaver Release 7.40, SP8 (or higher). You also have older systems (7.00, 7.01, 7.02, or 7.31) with their own custom code base. An upgrade of these systems is not planned so far. However, you would like to execute the latest static checks for your custom code and thus benefit from recent check variants in the Code Inspector tool. For this type of scenario, the remote static check might be a best solution for you.

Executing remote static checks
Figure 1: Executing remote static checks

The figure above outlines the components involved and the activities required for the execution of static code inspections based on the current check variants within a test system (AS ABAP 740, SP8 or higher). The source system (AS ABAP 7.00, 7.01, 7.02, or 7.31) includes the custom code (ABAP programs or other development objects) to be checked. The corresponding program data is extracted by means of an extractor utility (ABAP program) from the system and made available, either directly through RFC (A), or by means of a download to your local machine as a set of zip files (B). For the second use case (B), the remote custom code is available as a code information extract in the test system with the help of an upload utility. With the help of an upload utility, the remote custom code is available as a code information extract in the test system. In the Code Inspector of the test system, the new object set is finally created in the form of a remote object.

Target Audience
  • AS ABAP system administrators
  • ABAP developers
  • perform the download or upload of a code information extract, the display authorization profile for object S_DEVELOP (activity: 03) in the corresponding SAP systems is required as a minimum.
  • You have executed the correction instructions according to SAP note 2011106 Information published on SAP site (SAP note for importing the extractor for execution of static checks in remote system).
  • If you decide to use the RFC option for the data export, the communication using RFC is set up correctly (RFC destination for the test system and the users for RFC communications are created).