Show TOC Start of Content Area

Component documentation  New Debugger  Locate the document in its SAP Library structure

Purpose

The New Debugger is a test tool that you use for testing the source code of an ABAP program. The Debugger checks the program logic and finds errors in the code.

Integration

The ABAP Debugger is an integrated test tool within the ABAP Workbench.

Example

You want to debug an application and start the Debugger by entering /h in the command field of the application. The Debugger remains active until control passes back to the application as a consequence of a user action. The Debugger receives control again when a breakpoint is reached or when the application explicitly activates the Debugger using /h. The application session is subject to the control of the Debugger session until the application session is closed or the Debugger session is cancelled explicitly by entering /hx, in case the setting Close Debugger After Continue‘F8’ And Roll Area End is not selected.

Features

      The user interface of the New Debugger has a large number of customizing options. You can configure it according to your requirements and needs.

      The new Debugger runs in an additional external session which is separated from the application’s external session. As long as this external session of the application is active, the Debugger remains open and controls this session.

This is useful when analyzing internal session-independent programs in debugging mode. For example, if you open a new one using SUBMIT REPORT or CALL TRANSACTION statements, the Debugger session remains open and all settings, such as the arrangement of tools or list of variables, remain unchanged.

      When the input focus changes from the Debugger to the application and vice versa, the system automatically places the session that is ready for input in the foreground by the SAP GUI.

Constraints

The New Debugger can run in exclusive and non-exclusive mode. Exclusive mode means that the application that is being analyzed exclusively occupies a work process of the application server during debugging. In non-exclusive mode, the Debugger functions are limited. In non-exclusive mode, after each Debugger interaction, the system requests a roll-out in the application. Therefore, an implicit database commit must be executed. This has the following consequences:

      Debugging is not possible between the statements SELECTand ENDSELECTbecause the database cursor needs to be closed when using an implicit database COMMIT statement.

In this case, program execution is terminated.

·        Debugging is not possible for conversion or field exits.

·        Due to the implicit database commit, inconsistent datasets can occur in the database.

For this reason, non-exclusive mode is not possible in productive systems.

 

End of Content Area