Application Development and Automation Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Showing results for 
Search instead for 
Did you mean: 
Read only

sapscript debugging

Former Member
0 Likes
1,593

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

7 REPLIES 7
Read only

Former Member
0 Likes
1,110

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

Read only

Former Member
0 Likes
1,110

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!!

Read only

0 Likes
1,110

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

Read only

Former Member
0 Likes
1,110

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

Read only

vinod_gunaware2
Active Contributor
0 Likes
1,110

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

Read only

Former Member
0 Likes
1,110

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

Read only

Former Member
0 Likes
1,110

Hai DP go through the following Links

Refer the following links:

To Debugg the SAP-script execute transaction SE71 and click on Utilities Menu and then click on activate debugger. Then you can execute your drive program.

Thanks & Regards

Sreenivasulu P