‎2007 Nov 19 7:16 AM
Hi,
I have created a output type for the packing list inside vl02n i.e.
vl02n->pack->Extra->Output. Then, i also tried to debug my print program by placing a break point in it. But, the system did not stop in the breakpoint during the execution. Is there any alternative to debug it??
Regards,
Kit
‎2007 Nov 19 7:19 AM
Hi
Keep a Break point in the driver program and debug it.
It's similar to the debugging of a ordinary report.
Keep some break points in the program code and execute the SF output using MB02 then it will stop at the break point.
SCRIPT
There are 2 separate kinds of debugging available when you try to debug scripts.
1. Debugging the print program : This is the normal debugging we do for our report programs.
2. Debugging the script itself : You Can debug a SAP Script by activating debugger in two ways:
a .In SE71->Menu->Utilities->Activate Debugger, then debugger will be get activated and when your print program is executing Script Debugger will be in active and you can proceed with your debugging.
b. Goto se38-> RSTXDBUG ->Execute this same as going thru in se71-> Menu, now debugger will be activated.
refer to the link below
‎2007 Nov 19 7:20 AM
before saving output, put /H and from ur system menu switch on 'Update debugging and system debugging.
This will work.. if not, when control comes to SY_INIT subroutine, set a break point at any subroutine/FM in print program by choosing from menu bar.
reward if answered
‎2007 Nov 19 7:21 AM
Hi,
Check TCODE NACE for getting correct driver program and routine name for your output type then only u can debug your program.
Actually standard program have many routines in it and same program used for diffrent outputtype so first u have to specifyfy routinename and then put breakpoint to than routine only.
Please Rewards if helpful.
Regards
gagan
‎2010 Oct 04 12:14 PM
the best way to check your print programm & smartform/sap script go to se 38 ...rsnast00 ... and debug you will find all fuctionality for program etc...
‎2010 Oct 04 12:29 PM
Place a breakpoint in ur Routine which u have configured for output type.
and try debugging placing the break point at that routine in ur driver program.
it definatrely works.