Skip to content

ABAP Keyword Documentation →  ABAP - Release-Specific Changes →  Changes in Release 7.0 and its EhPs →  Changes in Release 7.0 

Tools in Release 7.00


1. ABAP Debugger

2. Memory Inspector

3. ABAP Unit

4. Logpoints

Other versions: 7.31 | 7.40 | 7.54

Modification 1

ABAP Debugger

The new two-process debugger has been further developed as follows:

  • Alignment to the functions of the previous debugger:

    Rows can be inserted and deleted in the display of internal tables.

    Watchpoints can be created.

    External programs (RFC, update function modules, BSP, ...) can be debugged.

    Integration of memory analysis and Memory Inspector.

  • New tools:

    New Editor Control used for source code, which displays the content of variables as a tooltip.

    Display of differences between complex data objects.

    Display of data object graphs.

    Display of global data objects of all loaded programs.

    Structured display of the current screens and container controls.

  • Enhancements:

    Variable fast display split into global and local data. Display of current parameter interface with local data.

    Complete screen and ABAP stack in the stack display.

    Pausing of a running process at a particular point by setting a session breakpoint in a parallel ABAP session.


    • Note

    From Release 7.0, the default setting is the use of the two-process debugger. This setting can be changed in ABAP Editor by choosing Utilities → Settings → ABAP Editor → Debugging.

    Modification 2

    Memory Inspector

    • Memory Inspector can now be called in every transaction by choosing System → Utilities → Memory Analysis → Compare Memory Snapshots.
    • Memory snapshots can now be created in every transaction by choosing System → Utilities → Memory Analysis → Create Memory Snapshot.

    Modification 3

    ABAP Unit

  • The pseudo comments

    "#AU Risk_Level ...
    "#AU Duration ...

    can be used to define test properties when creating test classes using the statement CLASS ... FOR TESTING.

  • To enable the reuse of extensive test preparations, global test classes can be defined in Class Builder. Global test classes should always be abstract, can only be used in local test classes, and, like these, are not generated in production systems.

    • Modification 4

    Logpoints