debugging

[Former Member]

hi to all experts,

how many ways of deugging.

and how debug the program at background.

please give me the process from scheduling.

thanks in advance and reward also.

regard : deep.

[Former Member]

Hi Deep,

You can find a very good documentation on debugging in the below link. It explains you the process & ways of debugging.

http://help.sap.com/saphelp_nw2004s/helpdata/en/17/00ab3b72d5df3be10000000a11402f/content.htm

Reward if useful.

Regards

Sayee

[Former Member]

Hello,

gothrough this link this will helps u . if want still more give u r mail id i ill send some documents regarding Debugging.

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

reward is useful

Thanks.

Patil

[Former Member]

Useful for background

http://www.sappoint.com/basis/bckprsng.pdf

http://help.sap.com/saphelp_nw04/helpdata/en/6f/08703713bf277ee10000009b38f8cf/frameset.htm

Debugger

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

Regards,

[Former Member]

Hi Deep,

<u>Debugging in foreground</u>

You can initiate a transaction in debugging mode by typing /h.

You can use F5,F6,F7,F8 Keys to proceed through the line of code , each function key having a different function.

You can also stop the program/transaction at a particular line of code in the program by setting breakpoints.

You can use watchpoints to stop the program execution depending of the value of any variable.

<u>Debugging in background</u>

You can schedule a program in background using SM36.

Now if you go to SM37 to view the job , it will be scheduled status.

Now select the job and type <b>jdbg</b>

Now it will go to debugging mode and continue with debugging.

Hope this is of some help to you.

Regards,

SP.

[Former Member]

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>Breakpoints</b>

Instead of starting an ABAP program directly in the Debugger, you can also debug a program by creating one or more breakpoints in the program. A breakpoint is a signal at a particular point in the program that tells the ABAP runtime processor to interrupt processing and start the Debugger. The program runs normally until the breakpoint is reached.

There is also a special kind of breakpoint called a watchpoint. When you use watchpoints, the Debugger is not activated until the contents of a particular field change. For further information, refer to Watchpoints.

Breakpoint Variants

The Debugger contains different breakpoint variants:

Static The BREAK-POINT statement in an ABAP program. Static breakpoints are not normally user-specific. However, you can make them user-specific.

Directly-set

dynamic breakpoints Can be set in the ABAP Editor or the Debugger. Dynamic breakpoints are always user-specific, and are deleted when you log off from the R/3 System.

Breakpoint

at statement The Debugger stops the program directly before the specified statement is executed.

Breakpoint

at subroutine The Debugger stops the program directly before the specified subroutine is called.

Breakpoint at function module The Debugger stops the program directly before the specified function module is called.

Breakpoint at method The Debugger stops the program directly before the specified method is called.

Breakpoints at system exceptions The Debugger stops the program directly after a system exception, that is, after a runtime error has been intercepted.

reward if usefull

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

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

Regards