‎2007 Mar 26 8:41 AM
Hi All,
Can any body guide me how to debug the smart forms.
Thanks & Regards,
Satish.
‎2007 Mar 26 8:47 AM
Follow these steps.
1. Execute the smartform.It will open a FM in se37 screen.
2. Press Display.
3. Press find(CTRL+F).
4. Enter command here at which you want to put the break point.
5. Select the radio button 'in main program'.It will open the point at which you want to put the breakpoint.
6. Put the breakpoint here and execute the smartform again.It will stop at the point where you put the breakpoint.
Use SMARTFORM_TRACE to trace smart forms.
Regards,
Santosh
‎2007 Mar 26 8:51 AM
Hi,
Hi.
In the Smartform, create a Code Node and within the Code Node you can hardcode a normal abap Break Point.
In the Generated Fucntion module, You can put the Break point
Regards
Sudheer
‎2007 Mar 26 9:31 AM
Hi Satish,
Check this matter.
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
Hope this resolves your query.
Reward all the helpful answers.
Regards
‎2007 Mar 26 12:30 PM
hi
good
In the Smartform, create a Code Node and within the Code Node you can hardcode a normal abap
Break Point.
thanks
mrutyun^
‎2008 Jan 14 2:09 PM
Hi,
The the best way to debug the form is to put a breakpoint in the function module generated by the smartform.
Procedure:
Open the smartform we want to debug.
Goto Environment -> Function module name.
Open the function module in SE37. From the menu GOTO -> main program. Open the last include.
This incude contains the entire code ie the code we have written in initalization + form routines + program lines + sap generated code.
Even we can search for the text nodes, folders, templates, tables, graphics, address nodes etc with their names.
Put a breakpoint at any point you want.
If we issue any doc which triggers this form, when the control reaches the break point it will stop.
Please note that hard-coding the break points in the code ( Program lines ) is not recommended and it can´t be done unless if it is development server.
So, always put a session break point in the related function module.
We can use SFTRACE transaction to know the sequence of the control flow.
If you want to break at each and every text that is printed on the output form put the break points in the forms.
1. %write_text to break at text element.
2. %WRITE_TEXT_MODULE to break at text module.
3. %WRITE_INCLUDE_TEXT to break at include text.
Please put a break point at the first sy-subrc check.
If the control reaches this point, you can find the name of the element in the varible NAME and the content in the text node in %TEXT.
Its easy to understand the sequence of the printing if we put a breakpoint as stated above.
Regards,
Satish.
‎2008 Jan 15 5:29 AM
Hi,
just right click on the window of smartfrom(where exactly do u want to debug the samrtform),
select create,
->flow logic,
->program lines,
here u can write as 'BREAK-POINT' in progarm lines,
while excuting the driver progarm or smartform then cursore come to here(break-point)stops then u can dubug...
reward points if useful,
seshu.