Scribd
Upload
9 views3 pages

Debugging

The document provides an overview of debugging techniques for SAP ABAP developers, including how to activate debugging and set breakpoints. It details various types of breakpoints, such as session and external breakpoints, and explains how to navigate the SAP Debugger using function keys. Additionally, it covers creating breakpoints on message IDs and saving function module variants from the debugging environment.

Uploaded by

Roshini Bommireddy
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
9 views3 pages

Debugging

The document provides an overview of debugging techniques for SAP ABAP developers, including how to activate debugging and set breakpoints. It details various types of breakpoints, such as session and external breakpoints, and explains how to navigate the SAP Debugger using function keys. Additionally, it covers creating breakpoints on message IDs and saving function module variants from the debugging environment.

Uploaded by

Roshini Bommireddy
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 3

Debugging

• It’s a tool which is used SAP ABAP developer to see how SAP is processing our code

• How to activate the Debugging:

• Using /h

• To put a key word called BREAK-POINT in the source code.

• The issue is when ever we send the code to QAT or PROD and if the user is
trying the execute the program, debugger will get opened in the system,
which it should not.

• To put a key word called BREAK ‘Username’ in the source code.

• The advantage is the breakpoint will never trigger for any other user apart
for the user which we maintained in user name

• The disadvantage is same as above.

• As we cant use the three above command, SAP has provided 2 buttons in the source
code

• Static break point/session break point

• User defined break point/external break point

• Session break point: the breakpoint will only be applicable for that session, once you
terminate the session the breakpoint will get removed.

• How to place the session break point  place the cursor on the line and then select
the button session break point.

• In the grey out are of the code, just do a click, SAP will set the session breakpoint
and we can see the message in the status bar too.

• Note: to activate the session break point and user defined breakpoint we need to active the
code first.

• When we open the SAP Debugger, we have to move the source code from one line to
another line to do this we has 4 function keys

• F5  single step  to move the cursor from one step to another step.

• F6  execute  if I don’t want to see that execution of sub routine or fm or the


class method the we will click on F6.

• F7  Return  If we are inside the sub routine or fm or class method and I want to
come out from the sub routine or fm or class method then we will click on F7.

• F8  continue ( Full execution)  Directly we will see the o/p

• External breakpoint or user defined breakpoint: to debug the 3rd party data which we are
receiving the data

• To do the external debugging we need to change the user in the program settings 
To do this open the program in SE38 display mode  utilities  settings 
debugging  change the user name.
Debugging
• Once the external debugging is completed we need to change the user name back to
our user name.

• How to create a breaking on the message Id inside the debugger:

• To activate the break point the messages either you can use the following path or in
the dubegger click on F9 or

• Under the menu bar click on break points  Break point at  Break point on
message

• Provide the message class

• Provide the message number

• How to save the variant of FM from the debugging:

• Once we enter into the FM we need select the service button, click save parameters

• SAP will open window to provide the test data name


Debugging
 Now open the FM click on execute and select the button test data directory, we
can find out the test data.

You might also like