Have a look at below link.
I hope it helps.
Best Regards,
Vibha
<b>*Please mark all the helpful answers</b>
hi,
http://help.sap.com/saphelp_47x200/helpdata/en/c6/617ca9e68c11d2b2ab080009b43351/frameset.htm
For debugging tutorial:
http://help.sap.com/saphelp_erp2005vp/helpdata/en/5a/4ed93f130f9215e10000000a155106/frameset.htm
http://www.sapdevelopment.co.uk/tips/debug/debughome.htm
http://www.sap-basis-abap.com/sapab002.htm
System Debugging
If you set this option, the Debugger is also activated for system programs (programs with status S in their program attributes). When you save breakpoints, the System Debugging setting is also saved.
Update Debugging
Update function modules do not run in the same user session as the program that is currently running in the ABAP Debugger. These function modules are therefore not included in debugging. Only if you select the Update Debugging option can you display and debug them after the COMMIT WORK.
Normal Debugging
Normal debugging is the one we do it by the normal dynamic break points or by /H or by using stattic break points.
You can switch to diffferent debuggin modes while processing.
Regards
Anver
refer this link.
abap debugger is the tool which is used to execute the program step by step and view/modify the results at runtine.
to debug the program go to program ->test->debugging.
or else you can set the breakpoint at some code and execute the program.
by executing the program you will view the abap debugger. here you can execute the program:-
step by step...f5
step by step(whole subroutine as aa single step)...f6
exectue upto the end of the function module...f7
execute upto end or upto break point....f8
Debugging is useful when you have written some code and want to observe the behaviour of what exactly is happening at the various steps,what values are being passed to the variables,calls being made etc.
e.g you have a report which prints 10 values,however you see that only 8 are getting printed and want to know why the remaining two are missing or get incorrect values,debugging the code will help you identify the problem and fix it.
In ABAP context,you can set a session or external breakpoint in the ABAP workbench or you can set this manually in your code as:
SET-BREAKPOINT
It is advisable to set it only for your user name as others will hit this
ie. SET-BREAKPOINT <username>
If breakpoints are set as above and the report or transaction is run,the debugger is opened if the debugger hits the breakpoints you have set during execution.
Some of the frequently used shortcuts are F5(step into),F6(step out of execution of current call),F7(step out) and F8(execute).
Regards,
Vidya
hi,
while debugging we can see what each line in our code does and what are the value the variables contain at runtime, and its very useful to check the errors and rectify them and even the flow of program can be known.
u need to just enter /h b4 executing the program in the command line to start debugging and then go on pressing F5 to execute program line by line.
hope this will be helpful to u.
reward some points if satisfied.
Add a comment