Preparing Data Export from the Source System

Procedure

To initialize the code extractor in your source system (7.00 - 7.31), execute the ABAP program RS_ABAP_INIT_ANALYSIS.
In the initial screen that appears, leave the predefined entries unchanged and choose the Execute icon or press F8.

Initializing the code extractor in the source system

The ABAP program creates several database tables that are required to store the code extract from the Code Inspector.
In your source system (7.00 - 7.31), launch the Code Inspector using the transaction SCI.
Create a new object set (programs and other development objects) that comprises the custom code to be checked.
See also: Creating and Processing a Set of Objects
Create a new check variant.
See also: Creating and Processing a Check Variant
1. From the list of avaialble checks, select the Export of Program Information check.
2. Enter an appropriate value for the call level.
  
  Remember
  
  Using the call level parameter, you specify the procedure call depth of a program.
  
  For example, with the value = 0, you specify that no calls (call method, call function,..) within the program will be considered by the check.
  
  With the value = 1, you specify that called programs, too, will be considered by the check.
  
  Note
  
  You can derive the appropriate call level value from the maximum level specified by the individual checks in the test system. In particular, the check variant PERFORMANCE_DB contains one SQL performance check with level = 3. Therefore, we recommend value = 3 for the call level when using the PERFORMANCE_DB check variant. Otherwise, you might be faced with a huge number of messages after the check run in the test system that inform you that required data is missing. When using the check variant FUNCTIONAL_DB, we recommend value = 2 for the call level.
  
  Note
  
  As an alternative to the download to a local file, you can use the Export via RFC option. This enables you to analyze data that is exported using RFC into the system that is specified by use of an RFC destination.
Specifying a check variant when using the file download option for data export

Specifying a check variant when using the RFC option for data export

The standard window of the Performance Analysis tool for selecting filter conditions for trace records appears.
Create a new inspection and assign the object set and the check variant created in the steps above.
See also: Creating Code Inspections
Choose Execute or Execute... to execute the Code Inspector check for your object set and the check variant selected.

Results

The Code Inspector performs the inspection run, converts the source code of the selected ABAP programs into an appropriate format, and stores it in several database tables in the source system.

When using the option Export via RFC, the Code Inspector also transfers the resulting code extract to the remote test system that you specified for the RFC destination.