The new ABAP Debugger is executed in its own main mode (external mode), while the application to be analyzed (debuggee) uses a second main mode (two-process architecture). The new Debugger is therefore displayed in its own window of the SAP GUI.

The classic ABAP Debugger runs in the same roll area as the analyzed application. It is therefore displayed in the same window as the application.

The new Debugger provides the user with a flexible interface that can be configured as required and has more than eight desktops. In this way the user can display and arrange up to four tools of their choice at the same time.

A modern and individual user interface design is not possible in the classic ABAP Debugger.

For technical reasons, some ABAP programs (for example, conversion exits) can only be analyzed with the new ABAP Debugger.

Newer debugging techniques (such as Debugger Scripting, External Debugging, and Layer Aware Debugging) are only provided in the new ABAP Debugger.

For more information on breakpoint type, see the new ABAP Debugger. See Breakpoints in the New and Classic ABAP Debugger.