How to debug a report

Question

how to debug a report
i am new to ABAP

Answer 1

Hi
<b>ABAP Debugger</b>
The ABAP Debugger is an integrated test tool within the ABAP Workbench. You use it to check the program logic and to find errors in the source code of an ABAP program. In the Debugger, you can step through the source code of a program. The running program is interrupted after each step, allowing you to check its processing logic and the results of individual statements.
As of Release 6.10, you can also run Business Server Pages (BSP) in the debugging mode. You can also display and set breakpoints here. Business Server Pages can be displayed in the Object Navigator when you select an appropriate application under BSP Application.
<b>Features</b>
The Debugger provides an efficient means of identifying errors in ABAP programs. It contains the following functions:
•    Ways of starting the Debugger
•     Choosing different views
•     Choosing different execution options in the Debugger
•     Displaying source code in the Debugger
•               Setting and deleting breakpoints
•               Setting and deleting watchpoints
•               Stopping a program at a particular statement or event
•     Displaying and changing field contents at runtime
•     Displaying ABAP Objects and references
•     Displaying and positioning strings
•     Setting and deleting database locks
•     Opening the ABAP Editor, or Object Navigator
•     System settings and runtime warnings
<b>Starting the Debugger</b>
There are two possible strategies for starting the Debugger in the ABAP Workbench:
•     By setting breakpoints then running the program
•     By running the program in debugging mode.
<b>Setting Breakpoints</b>
A breakpoint is a signal in a line of code that tells the ABAP runtime processor to interrupt the program at that line and start the ABAP Debugger. A distinction is made between static and dynamic breakpoints. For further information about the different types of breakpoints and how to use them, refer to Breakpoints.
Running a Program in Debugging Mode
You can start the Debugger without previously having set breakpoints. This is the best procedure to use when you want to test a program right from the beginning. It is also useful if you do not know the program very well and therefore are not sure where best to set breakpoints. You can start the Debugger as follows:
From the Object Navigator     Select a report or transaction and program and choose Program &#61614;&#61472;Test &#61614;&#61472;Debugging.
From the ABAP Editor     Choose Program &#61614; Execute &#61614; Debugging (or the Debugging pushbutton).
From any screen     Choose System &#61614; Utilities &#61614; Debug ABAP.
From any screen     Enter " /h " in the command field.
<b>Checking System Programs for Errors</b>
To check a program or program component that is part of the ABAP Workbench (for example, the Screen Painter), you must use the system Debugger. To start the system Debugger, choose System &#61614; Utilities &#61614; Debug system from any screen. To stop the system Debugger, choose Debugger &#61614; Debugging off.
<b>
Displaying Program Attributes</b>
You can display the attributes Fixed point arithmetic, System program and Unicode checks active of the program that has just been executed by choosing Goto &#61614; Further Information &#61614; Program Attributes.
<b>
Display Modes in the Debugger</b>
When you are debugging a program, there are various display modes that you can use. All of the display modes have the same structure. The top part of the screen displays an extract of the program source code. The bottom part displays the information specifically available in that display mode. There are also pushbuttons on the screen allowing you to switch to the most frequently-used display modes. 
go to se38->give ur program name-.execute->give /h at command prompt->execute->now debugging will start->
f5-used for line by line debugging
f6-used for directly executing function modules or performs i.e. control won't go into that block.
f7-run to cursor
f8-direct executing.
fileds: here we can check fild values.
click fileds option and double click on the filed or type the filen name beside filed
tables : here we can check the data in the internal table.
click tables option and double click on the internal table.
Break points:
if you want to debug a particulr part you can use this.
place the cursor at any perform click breakpoint or double click on that line.it will be set.
if /h from report statement it will debug,so for debugging from particular point we will use break points.use f7 to traverse between multiple break points.
Watch-points: In some cases we need to check the data populated in the internal table for eample if we want to check the data of internal table record belongs to 100th vendor we will create watch point for this goto->breakpoints->create watch points->give filed itab-lifnr->=->100.
debugging procedure:
Use '/H' in the command line and execute the report/program, so that it goes to debugging mode
2. keep a hard coded break point in the code like BREAK-POINT and it stops there.
3.From the program Menu, Keep the Soft Break-points and do the debugging.
see the links
Refer to this thread
http://help.sap.com/saphelp_47x200/helpdata/en/c6/617ca9e68c11d2b2ab080009b43351/content.htm
http://www.sappro.com/downloads/Settings&SystemAreas.pdf
http://help.sap.com/saphelp_47x200/helpdata/en/c6/617ca9e68c11d2b2ab080009b43351/frameset.htm
https://forums.sdn.sap.com/click.jspa?searchID=2673672&messageID=3187106
https://forums.sdn.sap.com/click.jspa?searchID=2673672&messageID=850453
https://forums.sdn.sap.com/click.jspa?searchID=2673672&messageID=1546485
https://forums.sdn.sap.com/click.jspa?searchID=2673628&messageID=2048883
http://www.saplinks.net/index.php?option=com_content&task=view&id=24&Itemid=34
http://www.sap-img.com/abap/testing-and-debugging-abap-codes-functions.htm
Reward points if useful