Know ABAP debugging

ABAP Bebugger

Classic Debugger.

The classical Debugger has always had certain limitations.
A maximum of eight data objects could be displayed, and also 4 at a time.
The layout is fixed to display the data objects.
There is no way, from within the Debugger, to look up within the repository a function module, method, or subroutine name to set a breakpoint.

New ABAP Debugger

It is generally not possible to analyze programs in debugging mode that run in an ABAP processor unit.

This had made SAP releases its new version of Debugger "New Debugger". The reason for this is that the new Debugger executes in its own external mode. This allows the code to be analyzed to run with virtually no impact from the Debugger. It has more interaction with the developer and the system allowing search help use, the display of more than one internal table simultaneously, and an unlimited number of data objects.



You can set the New Debugger as the default debugger in
Utilities =>Settings=>ABAP Editor =>Debugging.

It is possible to switch between the classic Debugger and the new Debugger by selecting 

Debugger=> Switch to New ABAP Debugger or 

Debugger => Switch toClassic ABAP Debugger.

You can exit the new Debugger while debugging in the following ways.

1. Debugger =>Exit Debugger, which closes just the Debugger, and the application continues to run.

2. /hx” in the command field and press Enter closes just the Debugger and allows the application to continue to run.

3. Debugger =>Exit Application and Debugger, which closes both the Debugger and the application.

When the Debugger starts, It opens as – "ABAP Debugger Controls Session x (Exclusive)", where again X is the external mode of the application.

If the debugger opens in "ABAP Debugger Controls Session x (NOT Exclusive)". You can change the non-exclusive mode to exclusive mode using the option in the Debugger menu 

"Debugger Exclusive Debugging Mode On"

In Non-Exclusive mode, the debugger has limited functionality.
1. You cannot debug between the statements SELECT and ENDSELECT.
2. Debugging mode is not possible for conversion or field exits.
3. COMMIT statement can lead to an inconsistent datasets in the database.

New ABAP  Debugger Tools
The tools are grouped into four categories:



1. Standard Tools
2. Data Objects
3. Memory Management
4. Special Tools

For more Tutorials, visit ABAP Tutorials, Tips & Tricks and Certification Questions