WHAT IS THE USE DEBUGGING

[Former Member]

IS IT MANDATORY TO USE DEBUGGING IN A PRROGRAM........

[Former Member]

hi,

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

[Former Member]

Hi,

It depends on program functioning or not!

If your report is not giving desired output, you have to check where we went wrong.

You can keep watchpoints to trace the values.

Reward if useful!

[Former Member]

Hi Guru,

DEBUGGING - is not MANDATORY.

But to know exactly what is happening when a program is getting executed, DEBUGGING would help/ allow you.

If you DEBUG a program, you will be able to understand clearly what is happening out there.......

<i><b>Reward points for informatory answers.</b></i>

Best Regards,

Ram.

[Former Member]

Hi,

No it is not but the debugger shows the flow of the program and is use to remove any flaws that may be there causing wrong out put so we use debugger to see the reason for the same in program and data flow.

Regards,

Himanshu

[Former Member]

Hi,

It is not mandatory to use debugging in a program.

F5 - Step by Step debugging

F6 - Skips loops and Subroutines

F7 - Skips the loop or subroutine and returns to the last cursor point.

F8 - Execute and come out of debugging

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.

Regards,

Priyanka.

[Former Member]

hi..

its <b>not a mandatory one</b>.. if ur program runs fine and if it gives u the desired answer then no need of debugging..if u find some errors and if the code is not giving the correct answer then u can debug and u can resolve..

<b>Reward points if useful</b>

Regards

Ashu

[Former Member]

hi,

Debugging is not mandatory, but when ur program doesn't give appropriate results then it is mandatory. for debugging u should palce a break point in source code. it can be done in following ways

1. using keyword BREAK-POINT

2. just by clicking on break point button which is available in application tool bar

3. using /H in command box.

if helpful reward some points.

with regards,

Suresh Aluri.

[former_member196299]

HI GURU ,

You do debugging when your program doesnt function the way you want it, and then by debugging your program code you can find out the point where the bug is present .

So , it completely depends on your program's function and performance , and whether you need to debug or not .

You have already got informations about debugging in the previous answers , please go through them .

Regards,

Ranjita

[Former Member]

hi guru,

if u want to know the functionality of the program u have to debug the program...in future there is one defect came... without debugging how u can fix the issue....

according my point of view debugging is the best thing to learn and to fix the problem....

thanks,

maheedhar.t