topic Re: debugging in Application Development and Automation Discussions

debugging

Former Member — Tue, 18 Apr 2006 12:11:18 GMT

when doing function module debugging how to trace where the exact error is getting..

i need not no some important points while doing the debugging.

Re: debugging

Former Member — Tue, 18 Apr 2006 12:16:06 GMT

while in debugging mode,goto breakpoints~~>Breakpoint at~~>Statement--- here write 'message' and press enter.. then press F8..it ll stop at the point of error..

Hope it helps,

Regards,

Bikash

Re: debugging

Former Member — Tue, 18 Apr 2006 12:17:48 GMT

Hi,

You will have to F5, F6, F7 and F8 carefully.

F5 - Debugs and executes every statement of your code.

F6 - completes the execution of the current subroutine / function, without getting into it.

F7 - If you inside a sub routine / function, you want to get back to the place where you came from without continuing further, then use this.

F8 - Continue execution, without anymore debugging.

You can even set a Break point at a specific statement like MESSAGE.

Regards,

Ravi

Note : Please mark the helpful answers, and close your previous threads if the issues are resolved.

Message was edited by: Ravikumar Allampallam

Re: debugging

Former Member — Tue, 18 Apr 2006 12:21:43 GMT

HI franklin,

define an exception in the EXCEPTION tab

use the RAISE statement..

put a breakpoint in this RAISE statement..

eg.

 if sy-subrc NE 0.
   RAISE not_found.
 ENDIF.

when you test it

this exception will be displayed in the output..

regards

satesh

Re: debugging

nishanthbhandar — Tue, 18 Apr 2006 12:31:03 GMT

Common tips for debugging specific errors:

-- Type /H in the command to set debugging mode before executing your function module.

~~- Execute the function module.In the Breakpoints tab in the menu choose Breakpoint at~~>statement

set breakpoint for statement message.

--- If the function module is raising an exception then you have to copy all exception statements as declared in the FM and enter these through the above step

--- If you still cannot figure out then in the debugging mode set the dump on warning in the settings.Read through the dump analysis and you will get the exact place of error ..

There's always the step-by-step execution i.e pressing F5 ..but if you want to save time then try the above

Hope this helps

Cheers

Nishanth

Re: debugging

Former Member — Tue, 18 Apr 2006 12:31:11 GMT

Hi Franklin,

While debugging the FM use F5 for a step-by-step

debugging of the statements.

Like this U can trace where UR getting out of the

FM , I mean the exact error.

REgards,

GSR.