Documenti di Didattica
Documenti di Professioni
Documenti di Cultura
Welcome, Guest
Login
Register
Store
Products
About SCN
Downloads
Industries
Partnership
Developer Center
Lines of Business
University Alliances
Innovation
ABAP Debugger
Added by Guest, last edited by Sandra Rossi on May 28, 2010
The 2 debuggers
Classic ABAP Debugger
New ABAP Debugger
Why does it give a dump when I put a break-point in between SELECT and ENDSELECT? (classic debugger only)
A breakpoint in SELECT loops can cause an exception through loss of the database cursor. The reason for this is that during debugging a database commit is triggered and hence the cursor is lost.
How do I enter the debugger (/H) from modal dialogs? (popup windows)
In modal dialogs, the okcode field w here you usually enter /H is protected. You must use a SAPGUI shortcut, as explained in this w iki:
Explanation
Solution
User exit
Make sure you have activated both the function module AND the user exit
wiki.scn.sap.com/wiki/display/ABAP/ABAP+Debugger
1/3
19/11/2013
(CMOD)
Update task
enter /h and activate Update debugging, run the program. When the update debugging starts, press F9 key and enter the
name of the function module to add the break-point. Note: a break-point added before the update debugging starts is
ignored
Set an external break-point (see Note 668256 - Using HTTP/external debugging and Note 751872 - Problem analysis
(aRFC, HTTP)
External break-points are valid only 2 hours. Solution: add them again.
As explained in note 868830 - Cannot debug an RFC in a HTTP session, if you are currently debugging HTTP, you can't
go into a called RFC function module (even synchronous). The w orkaround is to set an external breakpoint in the called
RFC function module, or sw itch to classic debugger (if the button is available). Note: you don't need an external
breakpoint (step into w orks) if the ICF service option "GUI connection" is set to "Yes".
Background
it runs in background
job
SM37, select the job and use JDBG okcode, the job w ill starts interactively w ith sy-batch = 'X' (see Note 573128 Debugging programs in the background)
tRFC
TASK)
run under
you must both set break-points and run code w ithin same client and w ith same user
different user
or client
system
program
you may have to reenter /h and reactivate System debugging if break-point don't w ork again
debugging
program not
restarted
enhancement
framew ork
enhancement options
Little bugs in
local test
classes
in SAPKB70013)
no break
enter /h and add a break-point at the beginning of a form, function module or method by using F9 key and entering its name
A w orkaround is to call a procedure outside the test class and add a break-point in that procedure
add a break-point at an upper level or use SE30 to trace calls to make sure the procedure is called
because no
call
abap
debugger
1 Child Page
Soft breakpoint at statement
1 Comment
wiki.scn.sap.com/wiki/display/ABAP/ABAP+Debugger
2/3
19/11/2013
Guest
Challenge:
The pain is that now either w e have to run behind functional to get another test data (1st case) or have patience to go step by step again to reach that particular loop (2nd case).
Solution:
The 'Goto Statement' option in debugging can save us this effort. It is possible to go back to the previous statement after you position the cursor and click 'Goto statement' menu entry; program
control w ill move to the statement and debugging w ill start from that point.
Contact Us
Privacy
Legal Disclosure
wiki.scn.sap.com/wiki/display/ABAP/ABAP+Debugger
Copyright
Follow SCN
3/3