‎2006 Apr 27 2:30 AM
common question!! i can usually debug the sapcript by activating the debugger in SE71 and then by putting a break point in the printprogram.
Why is it sometimes though u activate the debugger as well as put a break point in the print program the debugging is not activated example i am trying to activate debugger for INVOICE run a billing doc using vf02(change ) and then create the output and save. It does not stop at break point but just goes ahead and creates a spool.
thanks in advance
DP
‎2006 Apr 27 2:38 AM
Hi DP,
This is a common problem. This happens because some times the application is programmed to trigger the spool into a different work process. Not all of the applications trigger the spool immidiately. At times it is triggered explicitly in a separate work spool work process.
Its simple. First activate the debugger in se71 and then just go into the debugging mode and SET THE OPTION UPDATE DEBUGGING.
This will allow to debugg the script once the control goes to the spool work proecess.
Hope this helps!!
Cheers
VJ
‎2006 Apr 27 2:58 AM
i just tried it. se71 activate debugger and goes into the debug mode in se71 and set the option to update and tried to run the script from vf02 but its didnt stop!!
‎2006 Apr 27 3:33 AM
Hi DP,
I am not sure then why it didnt work. I see no reason other then print getting triggered in a seprate spool workprocess.
Let me check and get back.
Rgds
VJ
‎2006 Apr 27 5:58 AM
Hi !
Some applications print in the "Update Task" (i.e. WM Transport Order - if they are so customized).
Printig in Update-Tast cannot be debugged in SE71.
If you are lucky it es possible to start the print-report or the print function via SE38 / SE37 and test it in dialog-mode.
Regards
Rainer
Some points would be fine if that helped you a bit
‎2006 Apr 27 6:24 AM
Check other setting i.e message type attach with same form or not?
and also check NACE setting.
Put hardcoded break-point in ABAP program.
regards
vinod
‎2006 Apr 27 6:32 AM
hi <b>DP</b>,
<b>You can debug a SAPScript:</b> Use Tools - Word Processing - Layout Set. Enter name of layout set and then Utilities - Activate Debugger.
It is of no consequence which layoutset you enter when selecting the SAPscript debugger. (Menu path: Tools-Wordprocessing - Forms, Utilities - Activate Debugger) The next layoutset called will invoke the debugger. This is quite handy when verifying which layoutset is being called (Verifying customizing settings).
Another way to set the SAPScript debugger is to run program <b>RSTXDBUG.</b>
Regards,
Santosh
‎2006 Apr 27 6:34 AM