✒️ABAP El debugger ABAP
ABAP El debugger ABAP
ABAP Debugger
The ABAP debugger is a vital tool for problem analysis and resolution. It allows us to run programs step by step, enabling us to check logic, view variable contents, internal tables, system variables, memory areas, etc. The debugger comes in two versions: Classic and New. In older SAP GUI versions, it's possible to switch between debugger versions, but in newer versions, the classic debugger has been replaced and can't be changed through the ABAP editor options menu (although the classic debugger itself can be accessed through alternative means).
Breakpoints
Breakpoints are a crucial aspect of the debugger. They act as markers to halt program execution at a specific point for inspection. There are two types of breakpoints:
Static Breakpoints: Generated by writing the BREAK-POINT statement in the ABAP code editor.
Dynamic Breakpoints: Divided into three sub-types based on creation:
Debugger Breakpoints: Created within the debugger and vanish when closed. You can create them by clicking the breakpoint icon or double-clicking on the left column next to the code line number. Clicking the breakpoint icon in the toolbar opens a dialog for configuring the breakpoint specifics.
Session Breakpoints: Valid only for the current session. These can be created from the ABAP editor toolbar.
External Breakpoints: Valid across any application running in the system, regardless of the launch source. They typically have a 2-hour validity and are associated with a specific SAP user. These can also be created from the ABAP editor toolbar.
Watchpoints
Watchpoints assist in debugging code by stopping program execution when a variable changes or reaches a specific value. Created from the debugging window through a toolbar button, watchpoints, like dynamic breakpoints, are user-specific.
Debugger Insights
How to Open: The debugger can be opened in various ways, with the three most relevant being:
Keyboard Shortcut: Typing the transaction code /h and pressing F8 in the ABAP editor. This opens the debugger without loading a specific program. If a pop-up appears without the desired result, configuring SAP GUI by dragging a script onto the pop-up may be necessary.
Transaction SE80: Right-click on the program -> Execute -> Debugging.
Transaction SE38: Trying to execute the program with an active breakpoint will open the debug program.
How to Use: The two key functions for now are manipulating the program flow and visualizing/modifying variables. To manipulate the program flow, we have buttons for Step-by-step (F5), Execute (F6), Return (F7), and Continue (F8).
Viewing and manipulating data: The debugger is opened with the "Standard" tab, there are two tables - one labeled "ABAP Stack and Dynpro" and another unnamed one. Double-clicking a cell in the "Variable" column, typing the variable name, hitting enter, and the content of the variable should appear in the "Value" column.
 
 
 
Sobre el autor
Publicación académica de Jaime Eduardo Gomez Arango, en su ámbito de estudios para la Carrera Consultor ABAP.
Jaime Eduardo Gomez Arango
Profesión: Ingeniero de Sistemas y Computación - España - Legajo: SW34C
✒️Autor de: 149 Publicaciones Académicas
🎓Egresado de los módulos:
- Carrera Consultor en SAP Fiori
- Carrera Consultor ABAP Nivel Avanzado
- Carrera Consultor ABAP Nivel Inicial
Disponibilidad Laboral: FullTime
Presentación:
Ingeniero de sistemas y computación con 8 años de experiencia el desarrollo frontend & backend (react/node) y en cloud (aws), actualmente desarrollando habilidades en sap btp, ui5, abap y fiori.
Certificación Académica de Jaime Gomez