debugging

[Former Member]

HI ALL,

Can anyone guide me to use ABAP debugging , like the purpose of that , and how to use fields, tables, watchpoints, breakpoints... with some examples.

thanks in advance

[Former Member]

Debugging Document.

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

[Former Member]

Hi Kumaran

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.

more at

http://help.sap.com/saphelp_nw04/helpdata/en/c6/617cdce68c11d2b2ab080009b43351/content.htm

Regards Rk

[Former Member]

hi,

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.

field's: here we can check field values.

click filed's option and double click on the filed or type the field 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 particular 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 example 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.

if helpful reward points.

[Former Member]

Hi Kumaran,

Check this info.

There are 3 types of debugging:

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 debugging 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.

MORE INFO:

http://help.sap.com/saphelp_nw04/helpdata/en/c6/617cdce68c11d2b2ab080009b43351/content.htm

http://help.sap.com/saphelp_nw2004s/helpdata/en/c6/617ca9e68c11d2b2ab080009b43351/frameset.htm

https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/9cbb7716-0a01-0010-58b1-a2d...

In sap library you will have lot of information about debugging.

http://help.sap.com/saphelp_47x200/helpdata/en/c6/617ca9e68c11d2b2ab080009b43351/content.htm

http://help.sap.com/saphelp_nw2004s/helpdata/en/c6/617ca9e68c11d2b2ab080009b43351/content.htm

In sap library you will have lot of information about debugging.

http://help.sap.com/saphelp_47x200/helpdata/en/c6/617ca9e68c11d2b2ab080009b43351/content.htm

http://help.sap.com/saphelp_nw2004s/helpdata/en/c6/617ca9e68c11d2b2ab080009b43351/content.htm

Hope this resolves your query.

<b>Reward all the helpful answers.</b>

Regards

[Former Member]

thanks a lot , great effort