‎2010 Dec 14 12:06 AM
Hello gurus!
I'm trying to debug a Z code which is responsability to generate a SAPScript form, but when I'm in the VL02N, I send the form to printing but I can't debug the code which really generates the data of the form After a few seconds the form will be on my spool (SP01)
Please, could someone tell if there's some way to debug or even find the Z code that fill that form?
Thanks in advance!
‎2010 Dec 14 10:07 AM
Hi ,
Update Debugging: turn on this setting if you need to analyze asynchronous updates, which are functions that are called as follows: CALL FUNCTION u2018...' IN UPDATE TASK. These functions are executed asynchronously in a special update work process (after the next COMMIT WORK statement). The debugger can't follow them since it is attached to a single process. Set a breakpoint in the function that is called IN UPDATE TASK, start debugging, turn on this setting, and the debugger will reach the breakpoint in your update function.
Please check the below link for more info.
[New ABAP Debugger u2013 Tips and Tricks|http://www.sdn.sap.com/irj/scn/weblogs?blog=/pub/wlg/21986] [original link is broken] [original link is broken] [original link is broken];
Cheers !!
Soumya Ranjan
‎2010 Dec 14 2:11 AM
Hi,
You need to activate the SAPScript debugger. Then perform the task (VL02N),.To activate the debugger use the below path.
Go to SE71. Give the formname. then Utilities->Activate Debugger.
Thanks
Subhankar
‎2010 Dec 14 1:09 PM
HI!
Actually I use this way, but I can't debug by this way because the form isn't generate on my save action, but in a separated process, so the sapscript debugger doesn't starts...
‎2010 Dec 14 10:07 AM
Hi ,
Update Debugging: turn on this setting if you need to analyze asynchronous updates, which are functions that are called as follows: CALL FUNCTION u2018...' IN UPDATE TASK. These functions are executed asynchronously in a special update work process (after the next COMMIT WORK statement). The debugger can't follow them since it is attached to a single process. Set a breakpoint in the function that is called IN UPDATE TASK, start debugging, turn on this setting, and the debugger will reach the breakpoint in your update function.
Please check the below link for more info.
[New ABAP Debugger u2013 Tips and Tricks|http://www.sdn.sap.com/irj/scn/weblogs?blog=/pub/wlg/21986] [original link is broken] [original link is broken] [original link is broken];
Cheers !!
Soumya Ranjan
‎2010 Dec 14 1:11 PM
Thanks, very useful answer!
I'll check this way, seems it will work!
I saw that article on SDN main page, but I didn't read yet. It is a very, very useful article!
Thanks so much!