06-29-2007 1:51 PM
hi friends,
can you please help me to understand how do Debuging the reports..how useful is the debuging . plz also tell me how to debug SAP Scripts.
plz help me with steps..
mahesh
06-29-2007 1:53 PM
Hi,
Check the following documents
http://www.cba.nau.edu/haney-j/CIS497/Assignments/Debugging.doc
http://help.sap.com/saphelp_47x200/helpdata/en/c6/617ca9e68c11d2b2ab080009b43351/content.htm
http://www.cba.nau.edu/haney-j/CIS497/Assignments/Debugging.doc
http://help.sap.com/saphelp_erp2005/helpdata/en/b3/d322540c3beb4ba53795784eebb680/frameset.htm
http://help.sap.com/saphelp_nw04/helpdata/en/84/1f624f4505144199e3d570cf7a9225/frameset.htm
http://help.sap.com/saphelp_bw30b/helpdata/en/c6/617ca9e68c11d2b2ab080009b43351/content.htm
http://help.sap.com/saphelp_erp2005/helpdata/en/b3/d322540c3beb4ba53795784eebb680/frameset.htm
Reward if helpful.
06-29-2007 1:53 PM
Hi,
Check the following documents
http://www.cba.nau.edu/haney-j/CIS497/Assignments/Debugging.doc
http://help.sap.com/saphelp_47x200/helpdata/en/c6/617ca9e68c11d2b2ab080009b43351/content.htm
http://www.cba.nau.edu/haney-j/CIS497/Assignments/Debugging.doc
http://help.sap.com/saphelp_erp2005/helpdata/en/b3/d322540c3beb4ba53795784eebb680/frameset.htm
http://help.sap.com/saphelp_nw04/helpdata/en/84/1f624f4505144199e3d570cf7a9225/frameset.htm
http://help.sap.com/saphelp_bw30b/helpdata/en/c6/617ca9e68c11d2b2ab080009b43351/content.htm
http://help.sap.com/saphelp_erp2005/helpdata/en/b3/d322540c3beb4ba53795784eebb680/frameset.htm
Reward if helpful.
06-29-2007 1:55 PM
Hi,
About debugging...
3 types update,normal and system debugging
check this for update debugging
If you set "Update Debbugging" you can debug the codes which works in update tusk.
SAP std often runs the routine (function or form) to update the database in update tusk mode, these routine start as soon as a commit work is done.
The commit is called at the end of the program, so you can't debug them by "normal debbugging" because it ends as soon as the program ends
or----
All the database updates are performed by the update work processes by calling the functions/subroutines in update tasks.
These tasks are executed after a commit work is reached in the application. By default you cannot debug these functions.
TO debug these u need to explicitly activate update debugging.
for system debugging check the below link
http://help.sap.com/saphelp_nw2004s/helpdata/en/ef/5f0640555ae369e10000000a155106/content.htm
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.
BREAKPOINT
In the source code we set the Break-point there by clicking the stop button, the system will stop there when you execute the program.
Watchpoint
For watchpoints, we need to give some condition and when this condition is satisfied, program will stop
example : if you want to debug only
for matnr value 100 than set watch point
matnr = 100. when value reaches 100 than
program stops at that point.
reward points if it is helpful...
regards,
Omkar.
06-29-2007 1:56 PM
Every developer should know the debuggoing techniques.
How to set: se38 utilities>breakpoints>set. If run the program the program stoips in the break point.
Script: SE71 form name Utilities-->Activate debugger. then run your print prog the program will stop in script form.
06-29-2007 1:58 PM
Debugging is must if you want to find the bugs and issues.
and Also to find some tables and data related check you need to know debugging.
To Debug in sap Script you need to activate the Debugger. In SE71 menu utitlities -> Activate Debugger
Regards
Vijay
06-29-2007 1:59 PM
Hi Mahesh
to debug a script goto tcode se71 and
give ur script name
then on the menu bar
Utilities--> Activate Debugger
Then run the script as usually it will lead u to the debugging
reward all helpfull answers
Regards
Pavan
06-29-2007 2:01 PM
Hi,
<u><b>Script Debug:</b></u>
This can done in two ways:
In the form Utilities->debugger / RSTXDBUG FM for debugging script
The Procedure for debugging SAP script is:
Generally SAP script contains the Layout and corresponding print program.
First go to SE71 and enter ur script name. In the same screen go to Utilities->click on activate debugger option.
Now go to SE 38 and enter ur Print Program name and execute the program.
Now you can debug the script Page wise and window wise.
<u><b>ABAP Debug:</b></u>
You use ST05, Trace Request, to do a SQL trace.
When using SQL trace, it is good to run the program in debugger and just before you execute the SQL, go to ST05 in another session and turn the trace on.
After, or when, the SQL is finished, you can turn the trace off.
Then click on List Trace to see the details.
This is the way to control the traces.
If you just turn the trace on and then execute the program, you will get everything and will be overflooded with unnecessary information.
For more information check the following link:
http://www.sapbrainsonline.com/TOOLS/SQLTRACE/SQL_TRACE.html
http://www.sapbrainsonline.com/TOOLS/RUNTIMEanalysis/SAP_runtime_analysis.html
Regards,
Bhaskar
06-29-2007 2:01 PM
hi ,
debugging reports...
USE Breakpoints
it can be of different types.
Hard Break-Points : written in the code like
'Break-point 'Login- User Name''.
2)Soft Breakpoints
This is placed by placing the cursor at the line required by u and click the 'STOP' button or CntlShiftF12 in the std. menu
while executing your report the execution will stop at your break-point and will execute statements one by one
by using F5,F6,F7 & F8 function keys
3) By giving the command '/h' in the command box the debugging mode is opened from the starting of the program.
if u need further info u can go with these links
http://help.sap.com/saphelp_erp2005/helpdata/en/b3/d322540c3beb4ba53795784eebb680/frameset.htm
Debugging Document.
http://www.cba.nau.edu/haney-j/CIS497/Assignments/Debugging.doc
F5 is used to debug line by line code it will nevigate to each step wheter it is a method call or function it will go in side it.
F6 u will move line by line but does now enter inside any function call
F7 will return u to the upper level
Ex if u are inside any method that is called from any other main method u will move to the main method
regards
reena