We Will Divide The Discussion in To The Below Parts
We Will Divide The Discussion in To The Below Parts
parts.
• 1. Programs in SAP ABAP
• 2. Initiating the Debugging
• 3. Breakpoints
• 4. General tips
Programs in SAP ABAP
• As functional consultants, we deal with many transaction codes and
behind each transaction code, there is a ABAP source code.
• When we execute the program, the control runs through the program
and delivers the output. When we debug, the control remains in our
hand and runs through the program line by line, thereby allowing us
to find out a specific bug, or clarity about a specific logic.
Types of Debugger
In SAP, there are 2 types of debuggers. One is Classic debugger and the other one is New
Debugger.
• The Classic Debugger runs in the same roll area as the application to be analyzed
(debuggee). It is therefore displayed in the same window as the application. However,
this technology also has some restrictions. For example, some ABAP programs (such as
conversion exist) cannot be analyzed in debug mode for technical reasons. However, the
most significant restriction is that no ABAP technology can be used for designing the
Debugger interface and it is therefore not possible to create a modern user interface.
• The New Debugger on the other hand, is executed in a separate external session
(Debugger), while the application to be analyzed (debuggee) uses a second external
session. With this technology, the user interface of the Debugger can be designed freely
by ABAP means.
Initiating the Debugging
• Debugging can be initiated in two ways.
• a. Using /h command and executing the transaction.
• b. Putting a break-point, at a particular line of the program and
executing the transaction. To start, open debugger by setting break
points in the ABAP editor. There are two types of break
points: Session Break Point and External Break Point.
Line by Line Debug