ABAP Keyword Documentation →  ABAP − Release-Specific Changes →  Changes in Release 6.20 → 

Tools in Release 6.20


1. Code Inspector


2. Run Time Monitor



3. Debugger



4. Runtime Analysis




Modification 1

Code Inspector

The Code Inspector is a tool that allows you statically check ABAP programs, function modules, classes, interfaces, and Dictionary objects for errors, performance, security, and reliability. The development of these repository objects is supported by simple search and check functions. The check results are available in the form of a tree hierarchy

The Code Inspector is called for a single object from the ABAP Editor by choosing Program → Check → Code Inspector, from the Function Builder by choosing Function Module → Code Inspector, or from the Class Builder by choosing Object Type → Check → Code Inspector. If you wish to check several Repository objects, for example all development classes in a package, then these can be grouped together in an object set. You also have the possibility of defining check variants with individual checks. A check of all objects in an object set using a specified check variant is called an inspection.

The Code Inspector executes purely static checks that only return hints and clues for an object. The actual runtime behavior can be ascertained using Runtime Analysis or SQL Trace.



Modification 2

Runtime Monitor

The Runtime Monitor is a framework that supports the recording of ABAP program information at runtime. This information can come from tests that are fixed in the ABAP kernel. ABAP programmers can also query and log specific program conditions at runtime.

With Test > Create ABAP Test, the Runtime Monitor creates a class, which can be called to record data in the source code. The data is first compressed in the main memory and periodically transferred to the database in a background job. The tests can be individually activated and deactivated for different servers. Compressing and saving the data hardly affects the application server, which means that the Runtime Monitor can be used at any time, even in a production operation.



Modification 3

Debugger

Modification 4

Runtime Analysis

In Runtime Analysis, you can no longer create temporary variants. Instead, you can create a separate standard variant, which is automatically assigned the user name by the system. You can also create other variants with your own name or that of other users, as long as a master record exists for them. When you first start the runtime analysis, the system always display your own standard variant. If it does not exist, the system displays the SAP standard variant. If you call the runtime analysis again, the system always displays the last used variant.

Additionally, the create, delete, and copy functions are again included in the measurement restrictions block on the initial screen. While create and copy can only be executed as single functions, you can use the F4 key to delete multiple variants.