Community
Application Development and Automation Blog Posts
Learn and share on deeper, cross technology development topics such as integration and connectivity, automation, cloud extensibility, developing at scale, and security.
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 

Introduction 

The Blog provides step by step guide on how to debug the report programs, classes and Function modules using Eclipse ADT (ABAP Development Tool). 
 
In this blog, we will be covering  
1.How to set the Toggle Breakpoint and the Soft Toggle Breakpoint. 
2.How to debug in multiple sessions 
3.How to check call stack 
4.How to debug update Function module 
5.How to set Watchpoint 
6.How to set Conditional breakpoint 
7.How to set user specific breakpoint 
8.How to Activate, Deactivate and Delete the Breakpoints 
9.How to Add new variable to observe the values in variables tab

Toggle Breakpoint (Regular/Hard Breakpoint): 

  • This is the standard breakpoint type, typically indicated by a blue icon in the editor margin. 
  • It serves to launch a new debugging session when the program execution reaches the line where it is set. 
  • If no debugger session is active, encountering a regular breakpoint will automatically trigger the debugger and stop execution at that point. 
    To set Toggle Breakpoint, we can right click on the left vertical bar as shown 
    SUMAIYAKHATOON_1-1755683564063.png

Soft Toggle Breakpoint: 

  • This is a specialized breakpoint type, typically indicated by a green icon in the editor margin. 
  • Crucially, a soft breakpoint cannot launch a new debugging session on its own. 
  • It becomes effective only when a debugging session is already active. If a debugger is already running (e.g., initiated by a regular breakpoint or external debugging), a soft breakpoint will then cause the execution to pause at its location. 
  • Soft breakpoints are often used in scenarios where you want to selectively stop execution within an already active debugging session, especially in situations with high-frequency calls or when you only want to debug specific parts of a larger process without repeatedly launching new sessions. 

To set the Soft Toggle Breakpoint, we can Right click on the left vertical bar as shown 

SUMAIYAKHATOON_3-1755683564064.png

Debugging in multiple sessions 

By clicking on Application run (maximum 4 debugging sessions can be opened), we can debug the same program in multiple sessions 

SUMAIYAKHATOON_4-1755683564066.png

After 4 debugging session if we again click on Application run it gives us error message at right edge of exclipse 

SUMAIYAKHATOON_5-1755683564067.png

Debugging through Call Stack 
 
We can observe the events and navigate to the events in call stack at left side in Debug tab  

SUMAIYAKHATOON_6-1755683564068.png

Debugging Update Function Module

Click on ABAP Debugger Action icon and then click on Update Debugging. 

SUMAIYAKHATOON_7-1755683564069.png

Click on Ok to continue with update debugging. 

SUMAIYAKHATOON_8-1755683564070.png

Setting the Watchpoint 

 Right click on the variable and then click on the Set Watchpoint 

SUMAIYAKHATOON_9-1755683564070.png

we can observe the watchpoint for changed values 

SUMAIYAKHATOON_10-1755683564071.png 

Term 

Description 

Recent Value 

The value of the variable before the change that triggered the watchpoint. 

Current Value 

The value of the variable after the change, at the moment the debugger stops. 

For SY-INDEX = 12, the current value changed 

SUMAIYAKHATOON_11-1755683564072.png 

We can check the information whether watchpoint is reached or no 

SUMAIYAKHATOON_12-1755683564072.png

Setting the Conditional Breakpoint 

Right click on the toggle breakpoint and then click on Breakpoint properties 

SUMAIYAKHATOON_13-1755683564073.png

Set the condition and then click on Apply and close 

SUMAIYAKHATOON_14-1755683564074.png

Before pressing F7  

SUMAIYAKHATOON_15-1755683564074.png

After pressing F7 

SUMAIYAKHATOON_16-1755683564075.png

Setting the User specific Breakpoint 

In debugging right click the toggle breakpoint and then click on Debugging Properties 

SUMAIYAKHATOON_17-1755683564075.png

Select the User radio button and provide the username and then click on Apply and close

SUMAIYAKHATOON_23-1755684110983.png

We can observe the u symbol on toggle breakpoint

SUMAIYAKHATOON_24-1755684139926.png

Activating, Disabling (Deactivating) and Removing (Deleting) the Breakpoints 

 To deactivate the breakpoint, uncheck the checkbox 

SUMAIYAKHATOON_22-1755684082789.png

To activate the breakpoint, check the unchecked checkbox

SUMAIYAKHATOON_21-1755684058405.png

To remove the breakpoint, click on remove icon

SUMAIYAKHATOON_20-1755684024981.png

Adding new variables such as SY-TABIX and SY-INDEX in Variables tab 

To add new variable in variable tab, click on Enter variable 

SUMAIYAKHATOON_18-1755683564076.png

Enter the name of the variable (SY-INDEX) and press Enter 

SUMAIYAKHATOON_19-1755683564077.png

 

 

Conclusion
Debugging in ADT isn’t just a technical exercise—it’s a strategic advantage. It transforms reactive troubleshooting into proactive insight. With its modern interface, modular object navigation, and precision tools like watchpoints and expression evaluators, ADT empowers developers to dissect complex logic, trace runtime behavior, and optimize code with surgical clarity.

 

Comment
7 Comments