Tools in Release 7.00
1 ABAP Debugger
2 Memory Inspector
3 ABAP Unit
4 Logpoints
ABAP_MODIFICATION_1 ABAP Debugger
The new two-process debugger has been further developed as follows:
Alignment to the functions of the previous debugger:
Lines 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 the Memory Inspector .
New tools:
Use of a new Editor Control for the source code, which displays
the content of variables as a Quickinfo .
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 dynpro and container controls .
Enhancements:
Division of variable fast display into global and local data. Display of
current parameter interface with local data.
Complete dynpro and ABAP stack in the stack display.
Pausing of a running process at a particular point by setting a
session breakpoint in a parallel main session.
Latest notes: As of Release 7.0, the default setting is the use of the
two-process Debugger, which can be changed in the ABAP Editor by
choosing Utilities - Settings - ABAP Editor - Debugging .
ABAP_MODIFICATION_2 Memory Inspector
The 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.
ABAP_MODIFICATION_3 ABAP Unit
The pseudo comments
"#AU Risk_Level ...
"#AU Duration ...
can be use to define test properties when creating
test classes with the statement
CLASS ... FOR TESTING .
To enable the reuse of elaborate and extensive test preparations, you
can define global test classes in the
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.
ABAP_MODIFICATION_4 Logpoints
The new LOG-POINT statement allows you
write unconditional log entries into the log, which is also used by
ASSERT . Logpoints are
activatable checkpoints , whose
activation must be controlled using
checkpoint groups or activation
variants . Logpoints replace the incorrect usage of ASSERT for
pure logging purposes.
Documentation extract taken from SAP system, � Copyright SAP AG. All rights reserved