‎2010 Sep 17 2:21 PM
Hi,
I there any way how to debug subroutine called in sapscript by "perform form in program ZXYZ"? Setting (only session) breakpoint in that subroutine doesn't work....
Thanks for any reply.
Regards Jiri
‎2010 Sep 17 2:23 PM
First screen of teransaction SE71 there is a menu option to enable debugging. Try that and see if it works.
‎2010 Sep 17 4:48 PM
The not so clean solution is to put
DATA: x_out.
DO.
IF x_out IS NOT INITIAL.
EXIT.
ENDIF.
ENDDO.
At the start of your subroutine.
When you execute the print, go to SM50 and you'll see your subroutine running.
Select the row and then "Program/session -> Program -> Debug".
‎2010 Sep 17 6:40 PM
Place a break point in your subroutine, now activate the sap script debugger.
Press F5 and continue debugging in sap script once it reaches the statement where the routine is called it will take you to the code.
‎2010 Sep 18 12:48 AM
Hi,
How are you triggering the print program? Are you generating an immediate print or doing a print preview? An immediate print may be triggering a separate update call, hence breakpoint not triggered - either that or your ABAP code isn;t even being triggered.
If you're triggering an immediate print to a printer, I'd advise changing that to a print in scheduled job then running RSNAST00 in SE38 (if you're triggering from an output type).
Running RSNAST00, for your particular output, in SE38 should then cause your breakpoint to trigger, provided that code is being executed.
If you're running a print directly or a print preview then try one of the earlier suggestions in this post.
Regards, Andy
‎2010 Sep 18 8:16 PM
Hi Yuri55,
if the session breakpoint does not work although you start from the logon menu, then the form is not called properly, probably due to incorrect parameter transfer.
Anyway, switch on sapscript debugger from se71, set breakpoint on PERFORM or step through to perform. At perform statement, enter /h and see where you get and what happens.
Regards,
Clemens