Get Example source ABAP code based on a different SAP table
Tools in ABAP Release 6.40 ITOC
ABAP_MODIFICATION_NN 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.
Latest notes: This change was also transported back to ABAP_RELEASE 6.20. ABAP_HINT_END
ABAP_MODIFICATION_NN 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 ABAP_ISESS . 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 ABAP_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.
ABAP_MODIFICATION_NN Enhancements to the Previous Debugger
The following improvements were made:
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 line 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.
ABAP_MODIFICATION_NN Memory Inspector
The Memory Inspector tool was introduced for the analysis of memory snapshots.
Latest notes: This change was also transported back to ABAP_RELEASE 6.20. ABAP_HINT_END
ABAP_MODIFICATION_NN Code Inspector
The Code Inspector tool was introduced to check repository objects for performance, security, syntax, and the adherence to naming conventions.
ABAP_MODIFICATION_NN ABAP Unit
The ABAP Unit tool was integrated in the ABAP runtime framework to test individual program sections. ABAP Unit is based on the execution of test methods in test classes.
ABAP_MODIFICATION_NN 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).
