DEBUGGING IN SAP ABAP

Debugging In SAP ABAP

Debugging is the process of analyzing the flow of the program to detect and mitigate defects or bugs. Unlike other programming languages, debugging in SAP involves analyzing different objects. Thus, different techniques are used to debug different types of objects.

In the debugging process, the controller is in our hands, that is, the execution of the program is in our hands.
ABAP Debugger is a tool from ABAP with which you can stop running programs and then execute them line-by-line or section-by-section.

Types of Debugger

  1. Classic ABAP Debugger:
    • The classic ABAP debugger is loaded in the same session as the program. Hence it is displayed in the same window in which the application.
    • There are some technical challenges involved in debugging ABAP programs.
    • A modern and personalized user interface design is not possible in the classic ABAP debugger.
    • For example, some ABAP programs (such as conversions that exist) cannot be analyzed in debug mode for technical reasons.
    • Switching between the classic and new debugger is possible at any time.
    • In this case, all breakpoints are visible to both debuggers.
    • To switch from the classic debugger to the new debugger, you must switch from the debugger switch to the new ABAP debugger.
    • More about this source text.
  2. New ABAP Debugger:
    • For technical reasons, some ABAP programs (for example, conversion exit) can only be analyzed with the new ABAP Debugger.
    • New debugging techniques (such as debugger scripting, external debugging, and layer aware debugging) are only provided in the new ABAP debugger.
    • The New ABAP Debugger runs separately from the main application.
    • It is executed in a separate external session (debugger), while the application (debugger) uses another external session for analysis.
    • With this technology, the user interface of the debugger can be designed independently through ABAP.
    • Therefore the new debugger is displayed in its own window of the SAP GUI.
    • The new debugger provides the user with a flexible interface that can be configured as needed and has more than eight desktops.
    • This way the user can display and organize up to four tools of their choice at the same time - depending on the user's selection.
    • For example, it is possible to display source texts or structures.
    • In this way, the user can design the debugger interface according to his individual needs.
    • The new ABAP debugger runs separately from the main application. This means that the limitations of the old debugger no longer apply.
    • Running in a separate process, thus eliminating any side interactions between the debugger and the debugged application, and also enables debugging for all ABAP coding.
    • Improved UI and personalization capabilities, in addition, increase the efficiency of the debugger.

How to activate the ABAP Debugger

There are mainly 4 ways to start the Debugger Session: 1. /h.
2. Statement: “Break-point”.
3. Push-Button.
4. From the Program.

1. /h:

We can activate the debugger just by writing an /h into the command bar as follow:


Then press enter, you will get a message in status bar as shown figure

Then execute the program you will directly entre into the debugger session.


2. Statement: “Break-point”

This statement defines a breakpoint.
If the program reaches an active breakpoint in dialog processing, execution of the program is interrupted and the ABAP debugger opens.
An inactive breakpoint is ignored and execution of the program continues with the statement after BREAK-POINT.

3. Push-Buttons

There are two buttons available as shown

Left session breakpoint and right external breakpoint.
To set a breakpoint in an ABAP program, simply select the line of executable code.
And click on one of the icons above or just click on the left margin of the line we need to debug. and execute the program which will lead to the ABAP debugger.

4. From the Program

Other way to start debugger is from the editor as follows:


Breakpoint:

Apart from being able to execute an ABAP program in the Debugger, you can also start the Debugger call by the choosing a breakpoint.
This is achieved by setting one or more of these breakpoints in the program.
A breakpoint is a signal at a particular point in the program that tells the ABAP runtime processor to interrupt processing and start the debugger.
When the program reaches this point the debugger is activated.

Types of Breakpoint
1. Session Breakpoint.
2. External Breakpoint.

  1. Session Breakpoint:
    • With session breakpoints you can pause and debug requests that you trigger in the same user session where you have set session breakpoints.
    • Therefore they are particularly useful for debugging SAP GUI-based applications.
    • You set a session break point in the ABAP editor (SE38) as a line break point, that is, for a specific line of source text.
    • In addition, other breakpoint types can be converted to session breakpoints during a debugging session.
    • The session breakpoint is valid in all main modes (external mode) of the user session where it was set.
    • If you end a user session (by logging off from the system), all session breakpoints defined in this session are removed.
    • Session breakpoints are therefore no longer available for implicit new logon, for example when switching servers using transactional SM51.

      • However, you can first save valid session breakpoints in the current user session in the database and reload them in another user session.
  2. External Breakpoint
    • External breakpoints (formerly known as user breakpoints) apply to the current user session in the same way as session breakpoints.
    • Additionally, they remain valid for future user sessions
    • It does not mean only communication sessions, but also sessions initiated with RFC or HTTP requests.
    • You can debug applications with RFC interfaces or external breakpoints that use the HTTP protocol (External Debugging)
    • Function modules, web services and web dynapro applications and BSP applications are also related to this.
    • An external breakpoint may apply to:
      1. A user in the current SAP system
      2. A user in the current application server of the current SAP syste
      3. User sessions started by a request that has a specific terminal ID.
    • You can set external breakpoints:
      1. In the ABAP Editor (SE38) as line breakpoints, that is, for a specific line of the source.
      2. In transaction SICF.e
      3. Other breakpoint types can be converted to session breakpoints during a debugging session.
    • External breakpoints are active for two hours. Then they are disabled.
    • If an external breakpoint is set, all previously set external breakpoints are reactivated.
    • External breakpoints are applied on the calendar day on which they are set. They are removed in the first minute of the next calendar day (at midnight).

Author

Madhura Akiwate
SAP ABAP Consultant, Baranwal Consultancy and Services (BCS), Pune, Maharashtra, India

Go to top

Sidebar Menu