Skip to content

ABAP Keyword Documentation →  ABAP - Release-Specific Changes →  Changes in Release 6.40 

Tools in Release 6.40


1. Assertions and activatable breakpoints


2. New two-process debugger

3. Enhancements to the previous debugger

4. Memory Inspector

5. Code Inspector


6. ABAP Unit

7. Runtime analysis

Other versions: 7.31 | 7.40 | 7.54

Modification 1

Assertions and activatable breakpoints

The new statement ASSERT can be used to define assertions. Assertions help verify particular assumptions about the state of a program in a particular location, and they guarantee that these assumptions hold.

Assertions can be activated from outside the program using a checkpoint group and the addition ID. The same addition was also introduced for the statement BREAK-POINT to activate breakpoints using checkpoint groups.


Note

This change was also transported to Release 6.20.

Modification 2

New two-process debugger

The new two-process debugger is a completely new development, with particular emphasis on the development of a more modern user interface. The main differences between this and the previous ABAP debugger are that the new debugger is executed in a separate ABAP session and the object that is being analyzed (the debuggee) is now the entire ABAP session instead of an internal session.

The new ABAP debugger provides the user with a flexible and freely configurable interface with over eight desktops, on which between one and four tools, such as source code display or structure display, can be placed and arranged. In Release 6.40, there is now a choice of the previous debugger and the new debugger; it is now also possible to switch between the two at any time during a debugger session.

More details are available in the

SAP NetWeaver documentation in SAP Help Portal.

Modification 3

Enhancements to the previous debugger

  • When internal tables are displayed, offsets and lengths can be specified for the character-like components in the column headers.
  • When internal tables are displayed, the corresponding icons next to the table names can be selected to list the names of all internal tables displayed in the previous debugger session and double-clicked to display them. The display starts from the row number and the component with which the selected table was last displayed.
  • If the program flow is stuck on a CASE statement, the system branches in a single step to the affected WHEN block.
  • In ABAP Editor, external debugging can be activated and deactivated under Utilities → Settings. Depending on the settings and whether a regular ABAP program or an ABAP Script for a BSP is being edited, a prompt may appear (when creating breakpoints in ABAP Editor) asking whether these breakpoints are to be HTTP breakpoints or session breakpoints. HTTP breakpoints are persisted in the database for different logons; session breakpoints are regular breakpoints that refer to the current logon.

    • Modification 4

    Memory Inspector

    The Memory Inspector tool was introduced for the analysis of memory snapshots.


    Note

    This change was also transported to Release 6.20.

    Modification 5

    Code Inspector

    The Code Inspector tool was introduced to check repository objects for performance, security, syntax, and the adherence to naming conventions.

    Modification 6

    ABAP Unit

    The ABAP Unit tool was integrated in the ABAP runtime environment to test individual program sections. ABAP Unit is based on the execution of test methods in test classes.

    Modification 7

    Runtime Analysis

    When measuring BSP applications, it is now also possible to specify a different variant to the standard variant for restrictions (in the runtime analysis transaction SE30).

    The class CL_ABAP_RUNTIME provides methods for creating objects. The method GET_RUNTIME can be used to execute multiple runtime measurements with different resolutions and parallel measurements (see Class for Runtime Measurements).