topic Re: Debugging skips breakpoints ? in Application Development and Automation Discussions

Debugging skips breakpoints ?

Former Member — Wed, 19 Dec 2007 23:21:57 GMT

I am running Change Material Doc (tcode MB02) and creating a message output. I entered the output type (WA03) and language (EN) it run a Sapscript form (WASCHEIN) using driver program SAPM07DR. I have put breakpoints in SAPM07DR in all open forms and also in the form routine entry_wa03 and the execution does not stop at any of the breakpoints but still generates an output spool.

How do I debug this code ?

Desparately seeking help.

TIA.

Edited by: NewComer on Dec 20, 2007 12:22 AM

Re: Debugging skips breakpoints ?

Former Member — Wed, 19 Dec 2007 23:36:54 GMT

Hi,

Wecome to SDN.

The driver program for the output gets triiggered in background and hence you do not see the control stopping at the output.

What you can do is to go to the output screen.

Go to further options.

Chose the dispatch option as send with periodically scheduled job.

Then save the document.

Put the break point in your driver programs.

Go to se38 and run the RSNAST00 program.

GIve the Material Document number in the Object value.

Then it will stop at the breakpoint.

Alternatively, you can try to toggle the check box for system debugging in debugger to ON. and try issue the output. I haven't tried this but it may worth a try.

Regards,

Ravi Kanth Talagana

Re: Debugging skips breakpoints ?

RichHeilman — Wed, 19 Dec 2007 23:38:15 GMT

Most likely the output is being fired in an update task, hence the reason why your breakpoints are not working. I would suggest trying to use the "Print Preview" button(if it is available) to force the output to fire in your dialog session.

Regards,

Rich Heilman

Re: Debugging skips breakpoints ?

Former Member — Thu, 20 Dec 2007 02:21:06 GMT

Thanks Ravi. I was able to debug the message output using RSNAST00 program.