How to debug a script?

hi
can anyone tell me how can we debug a script please?
points will be given

Hi
check with this..
can be done in two ways:
In the form Utilities->debugger / RSTXDBUG FM for debugging script
The Procedure for debugging SAP script is:
Generally SAP script contains the Layout and corresponding print program.
First go to SE71 and enter ur script name. In the same screen go to Utilities->click on activate debugger option.
Now go to SE 38 and enter ur Print Program name and execute the program.
Now you can debug the script Page wise and window wise.
Reward if hepful
With Regards
vachana

Similar Messages

How to Debug Java Script in Adobe Form

I have used an alert for empty fields . I have used Check button control for this.
But the button click is very inconsistent. Some times it triggers the event sometimes it doesnt. Is there anyway to debug the java script. I have installed Script editor for IE but I am unable to use it for Adobe Forms.
Any help is appreciated.
Thanks,
Vasu

Hi Vasu,
i think that maybe is the check sequence is not very correct.. and maybe you can try to code it one check for empty fields at a time..
example
Name.
Address.
Tel.
Hp.
Email.
so u can try to code for one item at a time then slow try to debug it... as last time i use to insert the javascript inside each component then after it i implement into a button and slowly check for the check sequence which one need to be 1st and etc.
hope it help you. if not maybe u can give more information. maybe i can help you out at myside.
Regard,
Ng Jia Jun

Debugging a script and smart form

Hi Can u explain me How to Debug a Script and Smart from in Real time

hi,
for smartforms
1. use transaction SMARTFORM_TRACE
2. in the SMARTFORMS, use utilities to show the function name. You can analyze this function in SE37 and set dynamic breakpoints as required. Lok at the SMARTFORM_TRACE to decide where to set break points.
3. BREAK-POINT can be used only in own program lines in smartform - not very helpful because it always stops until removed and generated again.
for scripts
from SE71 enter form name
from Menu Utilities->ACTIVATE DEBUGGER
then execute the script from the Application Transaction
it will stop in the script and check for the Values you need
or
Execute RSTXDBUG.
~~Guduri

How to debug BDC , Dialog program and Script

Hi all,
Please let me know, how to debug BDC , Dialog program and Script
Thanks&Regards
Devi

SCRIPT DEBUGGING
When we want to debug the SAPSCRIPT, we need to first activate the debugger, we have 2 ways to activate the Debugger.
1) Execute the program RSTXDBUG
2) Go to SE71, from the initial screen enter the form name and press Utilities --> Activate Debugger
When we are in the Debug screen,
3.1) F5 will be debug filed by field, that means if a single line is having 5 fields, if we press the F5 this will do field by field,
3.2) F6 will be line by line, that means when we press the F6, it will debug the line and it will go to the next line. F7 also do the same way
3.3) F8 will be very useful when we have any include statement in the SCRIPT, if any include is there and we press the F5 or F6 then this will go that Include (normally SO10 or any transaction text), then if we want line by line debugging then we can press the F5 or F6, or if you want to execute that in a single shot then press the F8, then the debugger will be executed that include and come back to the Script debugging.
Some times in the script, we may right lengthy lines, if we want to debug that whole line, we have an option called Left/Right, this we will find the Debug screen of the script, there is a Push button, we can make use this button to debug.
We can put the breakpoints in the SCRIPT DEBUGGER also, just press the BREAKPOINT Pushbutton from the debugging screen or press EDIT --> Breakpoint
If we want to debug the print program from the SCRIPT DEBUGGER, just press SHIFT+F7 or EDIT --> ABAP Debugging
If we want to see the Windows which are defined in the forms, just press the Go to --> Form --> Windows .if we want to see the pages go to --> Form --> pages. Here we have an option to see the page wise window also go to --> Form --> page Windows
If we want to see the paragraphs which are defined in that script, press go to --> Styles --> paragraphs.
If we want to see the Character formats which are defined in that script, press go to --> Styles --> Character Strings.
If we want to see the Page formats which are defined in that script, press go to --> OTF --> Page.
If we want to see the Elements which are used in the Script, then press go to --> Text Elements --> Form Elements.
If we want to see the commands which are used in the script, press go to --> Commands --> List
Finally, if we want to exit from the SCRIPT DEBUGING, simply press Debugger --> Exit
DEBUG BDC
ust go into debugging mode and do the BDC step by step, when it comes to the Call Transaction line, check the mode which will be 'N'....Now, overwrite this with 'A' and execute the BDC...It will run in All Screens Mode....
As suggested above the MODE 'A' will do the trick as it takes you to all screens.
Normally MODE N will be defaulted as it will be used for background processing,
Here is a simple tip,
This will be the call transaction part of the program,
CALL TRANSACTION 'IW32' USING BDCDATA MODE 'N'
MESSAGES INTO MESSTAB.
I would suggest you to make it like this,
DATA: V_MODE TYPE C VALUE 'N'.
*<In debug mode set V_MODE = 'A' for debugging>
CALL TRANSACTION 'IW32' USING BDCDATA MODE V_MODE
MESSAGES INTO MESSTAB.
This will be very useful because you just need to change the value of the V_MODE at runtime as A for debugging besides it has N which is the default to be used. (i.e. you need not change the code again and again).
This will be very useful when you have to debug some program in QA or PRD servers.
regards,
srinivas
*reward for useful answers*

Hi, how to debug forms of script

hi
could anybody tell me how to debug script forms.
i am using /h in se71, but it is not going inside form.
pl guide me fast.
thanx
robo

Hi Rocky,
Go through the following two ways
SAP Script:
YOu Can debug a SAP Script by activating debugger in two ways 1.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.
2. Goto se38-> RSTXDBUG ->Execute this same as going thru in se71-> Menu, now debugger will be activated.
Smartform:I am afraid , we dont have any direct commands or direct procedure to debug a script. But in indirect ways we can do it.
1.Put a command line before where you want check the value of smartform and write the code "BREAK-POINT"->hardcoded debugging.
2.You can debug the function module which generates the smartform.
Regards
Sreeni

How 2 debug a Perform subroutine in sap script

Hi,
I have a perform endperform in Script. But tht is not working in some case. i m trying to debug but i m not able to go inside the routine and see wht it is doing? . can any one help me how to debug a subroutine in sap script.

Hi Panigrahi,
1) Put a break point in your perform.
2) YOu should change the dispatch option in your Output screen of the transaction which triggers your sap script. The dispatch option should be 1 (Send with a periodically scheduled job).
Then save your transaction.
3) Go to se38 and run the program RSNAST00.
Give the Object Key as the Document Number for which you are triggering the script output.
The control will stop in your perform.
Regards,
Ravi

How to debug zrffous_c payment advice script program?

Hi experts,
Payment advice is printing through (ZRFFOUS_C) this program. I want to debug this program .I tried in this way.
Put the break-point in the program and execute then enter the input data and execute then the following message is displayed.
"A:FO:098 29.01.2009 PNB" after this stopped the program .How to debug this program? I want to find these values (REGUP-BELNR, REGUP-XBLNR) in the program .The location where these values selecting in the program?I tried but i didn't get.
please give me the details or give me form name?
please help me in this?

Hi,
Your procedure of debugging is correct.
when you getting the error message , double click on the message on status bar and see wheather it is standard message or
custome message.
you are getting that error because of invalid data so get the valid data from respective Functional consultant
and try to debug again.
You ll not get that error after giving valid data.
Regards,
Pravin

How to debug script

1) i heard that we have to put layout in debug mode and then go to print program and execute it also in debug mode.
am i right?
2)where do we check like compilation errors in layoutset.

One way to start the script debugger is:
Se71->utilities->activate debugger.
This may be a time-consuming process. Instead, open a session and execute the program RSTXDBUG. Even if you follow the above menu path to activate the script, it will internally execute the program RSTXDBUG. So you are saving some time in going through all of the above processes.
2. Generally SAP script contains the Layout and corresponding print program.
First go to SE71 and enter ur script name. In the same screen go to Utilities->click on activate debugger option.
Now go to SE 38 and enter ur Print Program name and execute the program.
Now you can debug the script Page wise and window wise.
RSTXDBUG - SAPScript debugger
Debug SAPScript
You can debug a SAPScript: Use Tools - Word Processing - Layout Set.
Enter name of layout set and then Utilities - Activate Debugger.
It is of no consequence which layout set you enter when selecting the SAPscript debugger. (Menu path: Tools-Word-processing - 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 RSTXDBUG.
When a Form is copied from one client to another .And If U try to display or change the form in the copied client .The possible error message cud be :
1.Form not found
Try coping again specifing the language .
2.IF IT dispalys an error message saying That the text file is inconsistent .
Then go to SE38 and Run RSTXCHKO .
It will ask for the form name ,then check all the checkboxes and then run the program.
Note : all Script related problems can be solved using Program RSTX*.
Reward points if this Helps.
sanjay

How to debug web app with weblogic?

I wrote a web app that includes jsp files and some javabeans, then I put the jsp files to directory
mydomain\applications\DefaultWebApp
then I complied javabeans and put those classes to
mydomain\applications\DefaultWebApp\WEB-INF\classes
Then I start the weblogic,it runs very well.
I modified some javabean, complie them and put classes override the old classes,
but the web app can not find the new classes.
Any one know How to debug web app(with javabeans) in weblogic?
thanks!

how to config the hot deploy?
thxSorry, for this delay in responding. I had set notify me with email option in Watch This topic; but I never did get any email notification.
I use wls6.1; I think the process may be very similar to this in wls8.x. In wls6.1 (sp5), this is done via the -
Dweblogic.ProductionModeEnabled=False or
Dweblogic.ProductionModeEnabled=True
in the startup cmd/sh script. Out of the box, wls6.1 is set to Dweblogic.ProductionModeEnabled=False which automatically enables hot deploys.

How To: Debug missing Drivers in MDT

The definitive post on missing drivers in MDT (most comprehensive list I've done so far)…
Please to NOT post questions from this thread, instead create a new thread.
How to debug Network Driver Problems
One of the earliest hurdles an MDT administrator will come across is the management of device drivers, specifically networking drivers. With most other drivers, like Audio, printer, and video drivers, a quick call to Windows Update or install over the network
will resolve the Installation. However unless the Network (and storage) Drivers are installed into Windows from the start, it will be much more difficult to install the rest of the system.
This post should help you get started if you find a machine that did not install a device driver properly, and you want to know how to find and import the correct drivers.
Installing network drivers in the
full OS
Step 1 - Try network connection again
It's possible that you might get a DHCP error from MDT, but when you try again later to connect the Deployment Share it works! This may be caused by a slow or malfunctioning DHCP server in your network. Re-check your DHCP servers, ensure that PortFast is enabled
on your routers. If all else fails get your network administrators to document the DHCP delay. A long delay in modern networks is unnecessary.
Step 2 - Verify connectivity
You may not have a driver problem but a network problem. Check the physical connection on the computer (Network installs on MDT *REQUIRE* a wired network connection, no Wi-Fi). Open a web browser. Check the IP Address (ipconfig.exe /all). Ping the Deployment
Server, manually connect to the Deployment Share. IF you can't connect to the Deployment Share, neither can MDT.
Step 3 - Find the Correct Driver Package
Before you load the driver into MDT, first verify that you have the correct driver. There are scenarios where you may *think* you have the correct driver, but the driver will never run because the package is designed for a different OS/SKU/Platform/whatever.
Install the driver package by:
  ○ Open the Device Manager (devmgmt.msc).
  ○ Find the network device in the list (ensure this is the wired device, not the wireless device)
  ○ Right click on "Properties" and click on the "Details" tab.
  ○ From the "Details" tab, select the property "Hardware Ids" select all the values, and copy to the clipboard, it would be a good idea to save for later. Should look something like:
      PCI\VEN_8086&DEV_1502&SUBSYS_21F317AA&REV_04
      PCI\VEN_8086&DEV_1502&SUBSYS_21F317AA
      PCI\VEN_8086&DEV_1502&CC_020000
      PCI\VEN_8086&DEV_1502&CC_0200
  ○ From the "Driver" tab, click on "Update Driver…", click on "Browse my computer for driver software" locate the driver package on the local machine or USB Drive, and install the package.
  ○ You should get a confirmation that the driver package was installed.
  ○ IF you do not get confirmation, MDT driver installation may not work.
Windows will install the driver starting with the *.inf install package, and will typically include a *.sys (binary) and a *.cat (digital Signature). If the driver package has been re-packaged into a *.cab, *.zip, or other compressed *.exe file, the
package must be extracted first. This is a hard requirement for any driver used by MDT and/or SCCM. All driver packages that are signed by Microsoft (WHQL) will be installed from the *.inf file, and you should only use devices that have the Microsoft WHQL
Logo as a sign of quality.
If you need a help on where to find driver packages for your devices, the 3 largest Computer OEM manufacturers supply drivers grouped by Make and Model that are easily imported into MDT and SCCM. See:
http://deploymentbunny.com/2014/07/08/back-to-basicwhere-to-find-drivers-for-servers-and-clients/
Step 4 - Load driver into MDT
If you have more than 20 driver packages, or if you anticipate you will have more than 20 drivers, you should start grouping your drivers in sub-folders for organization. One popular method is to group by Computer Make and Model. Ensure that you are using the
correct Driver Selection Profile in your task sequence. If you are unsure, disable any selection profile(s) to ensure the driver is installed correctly.
Step 5 - Run the full MDT installation
During installation MDT will perform the following:
  ○ Run the PNPEnum.exe utility and capture output to PnPEnum.xml. The VEN_Xxxx and DEV_Yyyy from the "HardwareIDs" property above must be present in this list. Otherwise we won't have a match.
  ○ Search through the %DeployRoot%\control\drivers.xml file looking for a match for the HardwareID. MDT may filter the search based on the folder search type.
  ○ MDT will copy each matching driver to the local c:\drivers directory using the xcopy.exe command. You can search (grep) for the string "xcopy" in the ZTIDrivers.log file, that will get you list of all driver packages matched by MDT.
  ○ MDT will allow the machine to boot into the NEW OS, and Driver Installation will begin in the OS. IF there are multiple drivers found and copied locally, the Windows (not MDT) will determine the best one. The c:\windows\inf\SetupAPI.*.log files
will detail which drivers copied locally were installed (or *not* installed).
Installing Network Drivers in
WinPE
Step 6 - Try the network connection again
(See above
Step 7 - Verify Connectivity from within WinPE
Verifying network connectivity will be a bit more difficult in WinPE, since we have a limited User Interface, so all investigation must be done in the debugging mode (Press F8) cmd.exe
  ○ Try connecting to the Deployment Share:
  c:\> net use * \\MDT\DeploymentShare$ /u:UserDomain\UserName *
  ○ Try pinging the Deployment Server:
  c:\> Ping.exe MDT.Corp.contoso.com
  ○ Verify that you have an IP address ( ipconfig /all ) If you have an AutoConfiguration address - Driver OK - WinPE can't reach the DHCP server. If you have "Media Disconnected" - Driver OK - Physical adapter not plugged to network. If
no devices are listed - Driver bad - Driver not installed.
  ○ Check the x:\windows\system32\WpeInit.log - This log will show the network driver (if found) being installed.
Step 8 - Verify driver packages are getting included into WinPE
Firstly, verify the correct driver package from within the full OS above. By default MDT will import *all* Storage and Networking drivers into your WinPE image. However it is possible to change the subset of files copied via "Selection Profile" or
other method. Cross check your WinPE Driver Settings.
  ○ From within the MDT console, right click on the root of your Deployment Share and select properties.
  ○ Click on the "Windows PE" tab, and the "Drivers and Patches" sub tab for both x86 and x64.
  ○ Your Network Drivers package must be in the "Selection Profile" if enabled.
Finally verify that the correct Network Driver package is being copied to WinPE. If necessary this may include setting up a debugger to watch the MDT Provider build the WinPE Image from scratch. My preference is to use the SysInternals
http://live.sysinternals.com/Dbgview.exe tool.
  ○ Open up the MDT console.
  ○ Download and run the DbgView.exe tool.
  ○ Update the deployment share in question.
  ○ The DbgView tool should show what drivers were copied to each WinPE Image.
Other
Whenever you add a driver into the MDT console, you must update the deployment share for that drivers to be added to your WinPE Image. If you are unsure, select "Completely regenerate the boot images." to ensure the drivers is imported. Additionally,
you must copy the updated LitetouchPE_x??.wim and *.iso files to the other consumers of the WinPE image like WDS/PXE and or any USB offline media.
Note that some Broadcom NetXtreme class of drivers have a multi-function driver architecture that may have difficulty loading in WinPE. Ensure that you load the "RIS" class of drivers from Broadcom in your MDT environment.
Note that by default MDT does *NOT* support the installation of Windows over Wireless network devices (Wi-Fi). The MDT installation sources must either be available through wired networking, or offline (USB Flash) media.
This post does not discuss origination of drivers within MDT ( Chaos vs. Total Control ), that is a different topic.
http://www.deploymentresearch.com/Research/tabid/62/EntryId/112/MDT-2013-Lite-Touch-Driver-Management.aspx
Further Help
If you are still having problems with drivers in via MDT, ask the experts in the MDT Technet Forum:
Include a short description of the problem. Including the Make/Mode if necessary.
Include the HardwareIDs from the Device Manager (Devmgmt.msc) into the post (from above).
Copy your known good driver package (step 3 above) to OneDrive.
Copy the following log files to a public site like OneDrive and include the link:
  ○ PnpEnum.xml (from Client)
  ○ Bdd.log (From Client) - or at least the ZTIDrivers.log file.
  ○ c:\windows\inf\SetupAPI.*.log (from client)
  ○ %DeployRoot%\control\Driver*.xml
  ○ %DeployRoot%\control\SelectionProfile*.xml
  ○ %DeployRoot%\control\settings.xml (if problems in WinPE)
  ○ x:\windows\System32\WpeInit.log (if problems in WinPE)
  ○ If the MDT server is not including your driver package in WinPE include the DBGView log.
This post is by Keith Garner - Keith was a developer on the MDT team where he developed the ZTIDrivers.wsf script, he also worked for the Windows Hardware Quality Labs as a technical PM on Driver Quality, and developed samples for the
Microsoft Device Driver Kit (DDK) specifically around the area of Device Driver installation in the OS (Windows NT 5.0, 2000 and Windows XP). (So yes, I know drivers :^).
Keith Garner - Principal Consultant [owner] -
http://DeploymentLive.com

OK. I have redone the drivers for WinPE which has reduced the image size by about 200MB. Unfortunately the problem persists.
Is there anyway to turn on some sort of boot logging so I can see what driver it is failing on?
I am also still seeing the weird behavior of it working over PXE but blue screens when booting from USB. Can anyone explain that?
JJ

Debugging SAP Scripts MR_PRINT and MR_REKL

Hi All,
Can anybody tell me if there is an easy way to debug the SAP Script Layoutsets MR_PRINT and MR_REKL, which are triggered through MRKO and MIRO transactions. Also I need to know how to repeat the print out of the above layouts, which are outputs of Invoice reductions and Invoice corrections.
I already tried SE71 -> Utilities -> Activate Debugger and also placing a break-point in one of the performs, I call, but I think the print program is a dynamic call and it is not stopping at the break-points.
Let me know what I am missing.
Thank you for your time,
yrkanth

Sorry, if it sounds dumb. But how will you put a hard breakpoint in a SAP Script? I don't hink there is a BREAK-POINT command which can be used in SAP Script? I activated the sap script debugger and am running the MRKO transaction which triggers the layoutset, but it is not stopping as it does stop for any other layouset.
The other way I tried was, to put in BREAK-POINT command in one of the performs the SAP script calls and I was able to stop at that only when I debug in Update debugging mode. This only allows me to debug the perform code but it still does not allow me to debug the script as we debug the script for PO (Purchase Order) by activating the SAP Script debugger and print previewing the PO.
Hope this helps?
I really appreciate your time.
Thank you,
yrkanth

Debug SAP script

Hi Gurus,
I need to debug SAP script. How can I do this?
Thanks,
Pavan
Moderator message - Please search before asking - post locked
Moderator message - Please see Please read "The Forum Rules of Engagement" before posting! HOT NEWS!! before posting - post locked
Edited by: Rob Burbank on Oct 13, 2009 5:00 PM

Hai Rajiv
For Debugging SAP Scripts & Smartforms as follows
SAP Script:
YOu Can debug a SAP Script by activating debugger in two ways 1.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.
2. Goto se38-> RSTXDBUG ->Execute this same as going thru in se71-> Menu, now debugger will be activated.
Smartform:I am afraid , we dont have any direct commands or direct procedure to debug a script. But in indirect ways we can do it.
1.Put a command line before where you want check the value of smartform and write the code "BREAK-POINT"->hardcoded debugging.
2.You can debug the function module which generates the smartform.
Regards
Sreeni

How to debug alchemy( i.e., c/c++) code?

Hi all,
i want to debug the alchemy code
can any one have idea how to debug,
waiting for inputs
thanks in advance

Please see my post further down these forums, "Debugging Alchemy Applications with Netcat" .
I have hacked together a perl script that functions similarly to gdb, but for alchemy applications -- they must be compiled with "-g". There is no breakpoint support. The debugger is run first, then alchemy will connect when run. http://alchemy-hacks.googlecode.com/svn/trunk/debugger/acdb

About debugging of script

hi experts,
can u plz help me how to debugg the script in general way.and i would like toknow how to debugg the transaction F150.and tell me clearly where exactly the script will be triggered and where exactly the driver program will trigger.
in detail

Hi Gupta,
There are 2 ways to debug a script.
1.Go to Se38 ,Enter the program name "RSTXDBUG' & then press Execute.
2.Go to se71,enter the form name .In the same page,go to Utilities -->Activate Debugger.
In both the cases,the debugger will b activated.Then u run the print program,automatically the form will b in debugging mode.....
Actually,while configuring,we will mention the print program & the form to a transaction,so both of them will b linked to the transaction,no need to link them explicitly again.
Reward points if useful.....
Pavan.

Debugging the scripts and smartforms

Hi,
Please Tell me How to debug the SAP SCRIPTS and SMARTFORMS.
Thank in advance
Ajay

DEBUG Smartform:
1) One way to debug smartform is to debug the Function Module of that smartforms.
If you want to debug particular smartform node that the solution would be,
insert a "Program Line" just above the node you want to debug and this program line write a normal abap breakpoint.
So whenever you call the smartforms, it will stop at this breakpoint and you can debug onwards.
2) SFTRACE can be used for debugging SMARTFORMS.
Read More here.
http://help.sap.com/saphelp_erp2004/helpdata/en/49/c3d8a4a05b11d5b6ef006094192fe3/frameset.htm
Re: How to Debug a Smartform
Debug of smartform and sapscript.
Debugging SmartForms
LOGO on Smartform
1) In Smart Forms Editor, In left pane, right Click any Page (say Page1) and select Create -> Window, Give it a name and Description (Say Window1)
2) Right Click on Window (Window 1) and select Create -> Graphics, Give it a name and description
3) In general Attributes, Select Name, get search help (F4) , you will find a list of pictures
4) Select any picture and set its Resolution in DPI
5) Press F9 to open Smart Forms Builder, Select window (Window1) and In Output options window set, size and position of the Logo
6) Set any other parameters if required, save and activate.
7) If there is only 1 Window in the forms, set it as Main Window in general attributes.
8) Use TCode SE78 to upload new pictures and logos.
look at Thread Dynamic Graph in smartforms
Refer the links also -
Re: Dinamic Graph in smartforms
How to get file perperties in Unix server
SMARTFORM-> execute->execute->pass values if require to import & table parameters ->execute-> on the pop up window give Printer name as LP01 and press print preview.
For debugging -
1. Write BREAK POINT in the code window.
2. Put a break point on the call function in the driver program
3. Put a break point in the generated Function module.
OR
1) DEBUG Smartform:
1) One way to debug smartform is to debug the Function Module of that smartforms.
If you want to debug particular smartform node that the solution would be,
insert a "Program Line" just above the node you want to debug and this program line write a normal abap breakpoint.
So whenever you call the smartforms, it will stop at this breakpoint and you can debug onwards.
2) SFTRACE can be used for debugging SMARTFORMS.
Read More here.
http://help.sap.com/saphelp_erp2004/helpdata/en/49/c3d8a4a05b11d5b6ef006094192fe3/frameset.htm
OR
Four ways you can debugging.....
1.place SFTRACE inplace where we enter T_CODE and press ENTER.
after that press F8.
2 ./H
3 /SH
4.after generating the function module there is a button DEBUGGING
Refer to these related threads
smartforms debug
Smartforms debug
How to debug Smartforms?
How to Debug the Smartforms
Re: Smartforms Debug
Smartforms
In the Smartform, within the Code Node you can hardcode a normal abap Break Point ..
Please set a break point in side the smartform:
BREAK <USERNAME>.
Then at the time of print/ preview the program stops there.
Example : If you set the break point in initializationas
BREAK <USERNAME>.
Program stops at break point. After that use Serach and set more break points.
>Search the program logic/Textelement/Address via search and set the break point at that code.
Other way to debug smartform is to debug the Function Module of that smartforms. If you want to debug particular smartform node that the solution would be, insert a "Program Line" just above the node you want to debug and this program line write a normal abap breakpoint. So whenever you call the smartforms, it will stop at this breakpoint and you can debug onwards.
or
SFTRACE can be used for debugging SMARTFORMS.
http://help.sap.com/saphelp_erp2004/helpdata/en/49/c3d8a4a05b11d5b6ef006094192fe3/frameset.htm
See the Below thread for how to debug the Smartforms
How to Debug Smartform?
Re: debug of smartfrom
Smart forms
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.

How to debug a script?

Similar Messages

Maybe you are looking for