how can we debug a script???

[Former Member]

hey!!

1. how can we debug a script??

2.How to change the package of a SAP Script

[Former Member]

put "/h" in the ok_code field (the white box at your top-left) where you write the transaction codes.), then press enter. Now you are in debug mode.

or put a break-point to your source.

[Former Member]

Hi,

They are two ways to debug the SAPScript.

1). Use Tools - Word Processing - Layout Set (SE71). 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.

2). Another way to set the SAPScript debugger is to run program RSTXDBUG.

When you debug Print program it is same as you debug any other ABAP program.

While when you debug SAPScript, you actually debug the code ( scripting) you have written SAPScript Form.

Use program RSWBO052 to change development class of a sapscript

Enter R3TR and FORM in the input values, this is for SAPSCRIPT, enter your Script and Press the Object Directory Entry push button and change the Development class for SAP SCRIPT ....

Regards,

Ferry Lianto

[Former Member]

Hi Ziden,

1. how can we debug a script??

Goto SE71, Give your Form name. <b>Goto Utilities->Activate Debugger.</b>

2.How to change the package of a SAP Script

To change Package for a script,<b>Excute report RSWBO052 and FORM in blank field,</b> check it and give script name and execute it.Double click on sapscript name <b>and change development class.</b>

Thanks,

Vinay

[Former Member]

Hello,

Check this,

How can I debug my SAPScript?

Go to the transaction SE71.

Enter the form name.

Choose the menu Utilities->Activate Debugger to enable debugging.

To cahnge Package

GO to SE03>Select Change Object Directories Entries>Press F8>Type FORM->Check the checkbox and give the message class name and press F8.

Here a window will appear and give the Dev.Class and save.

That's All.

Vasanth

[Former Member]

chk this blog

/people/sudheer.junnuthula2/blog/2007/01/09/script-debugging