Starting and Stopping the New Debugger 

       1.      To select the New Debugger as default in the ABAP Editor, choose Utilities → Settings.

A dialog box appears.

       2.      From the tabstrip, choose the ABAP Editor tab and then choose the Debugging tab.

       3.      In the ABAP Debugger screen area, select the New Debugger radio button.

       4.      To start the Debugger, perform one of the following:

○       From the ABAP Editor, choose Program → Test →Debugging.

○       In the command field of any application, enter transaction /h.

The New Debugger is automatically started each time in a new session. There is a maximum of six external sessions available. If no further external session is available, the Debugger start is cancelled.

If you want to debug system programs or screens, choose System → Utilities → Debug System or Debug Screen.

       5.      To switch to the Classic Debugger, choose Debugger → Switch to Classic Debugger.

When you switch from the New Debugger to the Classic Debugger, the system may reach ABAP code that you cannot process with the Classic Debugger. This is ABAP code (for example a conversion exit) that is called directly from the kernel. If you are analyzing this kind of code and you try to switch from the New Debugger to the Classic Debugger, the runtime error RPERF_ILLEGAL_STATEMENT appears.

       6.      To stop the New Debugger, perform one of the following:

○       If the Debugger is ready for input and the application is waiting for input, choose Debugger → Exit Debugger.

The Debugger closes and the application continues to run.

○       If in Settings, you have selected Close Debugger After Continue’F8’ And Roll Area End, the Debugger is automatically closed.

If the setting is not selected and the application is ready for input and the Debugger is waiting for input, enter transaction /hx.

○       To close both the Debugger and the application, choose Debugger → Exit Application and Debugger.

The New Debugger waiting time is determined by the profile parameter rdisp/max_debug_lazy_time, which is set to 600 seconds in the standard version. Afterwards, the Debugger process is exited automatically and control is passed back to the application. The system administrator can use transaction RZ11 to change the value of this parameter.