<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Debugging in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/debugging/m-p/1577279#M260608</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;1) DEBUG Smartform:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;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.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;2). DEBUG SAPScript&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;They are two ways to debug the SAPScript.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;1). Use Tools - Word Processing - Layout Set (SE71). Enter name of layout set and then Utilities - Activate Debugger.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;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.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;2). Another way to set the SAPScript debugger is to run program RSTXDBUG.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;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.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 26 Sep 2006 07:00:20 GMT</pubDate>
    <dc:creator>Former Member</dc:creator>
    <dc:date>2006-09-26T07:00:20Z</dc:date>
    <item>
      <title>Debugging</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/debugging/m-p/1577278#M260607</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;can any one tell me how do we need to do debugging in realtime process on things like script,reports,ca,&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 26 Sep 2006 06:57:38 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/debugging/m-p/1577278#M260607</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2006-09-26T06:57:38Z</dc:date>
    </item>
    <item>
      <title>Re: Debugging</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/debugging/m-p/1577279#M260608</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;1) DEBUG Smartform:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;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.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;2). DEBUG SAPScript&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;They are two ways to debug the SAPScript.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;1). Use Tools - Word Processing - Layout Set (SE71). Enter name of layout set and then Utilities - Activate Debugger.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;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.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;2). Another way to set the SAPScript debugger is to run program RSTXDBUG.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;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.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 26 Sep 2006 07:00:20 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/debugging/m-p/1577279#M260608</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2006-09-26T07:00:20Z</dc:date>
    </item>
    <item>
      <title>Re: Debugging</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/debugging/m-p/1577280#M260609</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;hi&lt;/P&gt;&lt;P&gt;good&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;DEBUG SAPSCRIPT-&amp;gt;&lt;/P&gt;&lt;P&gt;You can debug a SAPScript: Use Tools - Word Processing - Layout Set. Enter name of layout set and then Utilities - Activate Debugger.&lt;/P&gt;&lt;P&gt; &lt;/P&gt;&lt;P&gt;A further note to the tip above was provided by John Verbestel: 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).&lt;/P&gt;&lt;P&gt; &lt;/P&gt;&lt;P&gt;Another way to set the SAPScript debugger is to run program RSTXDBUG. Thanks to Amanda for this tip.&lt;/P&gt;&lt;P&gt; &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;REPORTS-&amp;gt;You can execute the report using the /h ,putting breakpoint at a particular line or, write the BREAK POINT statement at any point of your program.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;thanks&lt;/P&gt;&lt;P&gt;mrutyun^&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 26 Sep 2006 07:08:16 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/debugging/m-p/1577280#M260609</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2006-09-26T07:08:16Z</dc:date>
    </item>
    <item>
      <title>Re: Debugging</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/debugging/m-p/1577281#M260610</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;You have lot ways to debug,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;SAPSCRIPT:- you can execute Program RSTXDUBG or you can activate the debugger utilities --&amp;gt; Activae Debugger&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;SAMRTFORMS: you can debug the Function module or you can put the break-point in the SMARTFORM itself and do the debug&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;REPORTS: you can put the break-point where you need to start the Debug, while executing the screen will go into debug mode&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;MODULEPOOL: you can do the same as REPORTS&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;BACKGROND PROGRAMS:you can debug the background jobs, use the command BDUG&lt;/P&gt;&lt;P&gt;One way of debuging programs which are already running in background is via transaction SM50. This displays a   &lt;/P&gt;&lt;P&gt;list of process running in the server. In order to debug the program go to Menu option:&lt;/P&gt;&lt;P&gt; Program/Mode&lt;DEL&gt;&amp;gt;Program&lt;/DEL&gt;&amp;gt;Debugging.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;Sudheer&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 26 Sep 2006 07:22:45 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/debugging/m-p/1577281#M260610</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2006-09-26T07:22:45Z</dc:date>
    </item>
    <item>
      <title>Re: Debugging</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/debugging/m-p/1577282#M260611</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;lt;b&amp;gt;debigging script&amp;lt;/b&amp;gt; &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;goto UTILITIES-&amp;gt;ACTIVATE DEBUGGER for debuging the scripts&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;lt;b&amp;gt;Debug program running in background  &amp;lt;/b&amp;gt; &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;One way of debuging programs which are already running in background is via transaction SM50. This displays a   &lt;/P&gt;&lt;P&gt;list of process running in the server. In order to debug the program &lt;/P&gt;&lt;P&gt;go to Menu option :Program/Mode&lt;DEL&gt;&amp;gt;Program&lt;/DEL&gt;&amp;gt;Debugging.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;lt;b&amp;gt;REPORTS&amp;lt;/b&amp;gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;either use /h option during runtime or put break points.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;lt;b&amp;gt;smart forms&amp;lt;/b&amp;gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;put break points.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;anver&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;pls mark hlpful answers&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 26 Sep 2006 07:32:11 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/debugging/m-p/1577282#M260611</guid>
      <dc:creator>anversha_s</dc:creator>
      <dc:date>2006-09-26T07:32:11Z</dc:date>
    </item>
  </channel>
</rss>

