Skip to Content

Do you want to debug your ABAP applications directly within the ABAP Development Tools (ADT) for Eclipse?

There’s good news: Since the availability of the new SAP Kernel 7.21 in combination with SAP Basis 7.31 SP4 (prerequisite for using ADT) it’s possible to use the latest ABAP debugger, which is completely integrated in the Eclipse debug framework. Thus, it behaves like all other debuggers in Eclipse you might be familiar with. In other words, you can now debug your reports, transactions, classes and also Web Dynpro applications natively in Eclipse.

For a quick introduction to ABAP debugging in Eclipse you may watch this video:

Of course, we support all the standard debugging features also in Eclipse:

  • Monitoring the call stack
  • Setting breakpoints
  • Stepping through the code
  • Displaying and changing variable values
  • Viewing internal tables

A big advantage compared to the GUI-based debugger is that the ABAP source code editor which is used to display the source code in the debug session is exactly the same as in the default ABAP perspective. This means that all editor features like navigation or element info are also available during your debug session. Moreover, you can also use the editor to edit your source code during debugging.

For more information about the ABAP debugger in Eclipse please refer to the detailed documentation within the ABAP Development Tools (Help menu -> Help Contents -> ABAP Development User Guide).

To report this post you need to login first.

3 Comments

You must be Logged on to comment or reply to a post.

  1. Deepti Dhingra

    Hi Christopher ,

    Thanks for sharing this post.

    I have one query whenever I try to set a break point in my program it says

    ” ABAP debugger for Eclipse is not available in ABAP system.

    Use SAP GUI for debugging ‘

    Please suggest what configuration do I need to do in my ABAP system, so that I am able to see the ABAP Debugger in Eclipse.

    Thanks & Regards,
    Deepti

    (0) 
  2. Henrik Jarlskov

    What about getting that “Go to Statement”-functionality, which is vital for debugging ABAP, so that you can test directly in the debug-session wherter your idea for a solution actually works?

    (0) 

Leave a Reply