<?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: How to debug subroutine called in sapscript in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/how-to-debug-subroutine-called-in-sapscript/m-p/7240854#M1526305</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Place a break point in your subroutine, now activate the sap script debugger.&lt;/P&gt;&lt;P&gt;Press F5 and continue debugging in sap script once it reaches the statement where the routine is called it will take you to the code.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 17 Sep 2010 17:40:08 GMT</pubDate>
    <dc:creator>kesavadas_thekkillath</dc:creator>
    <dc:date>2010-09-17T17:40:08Z</dc:date>
    <item>
      <title>How to debug subroutine called in sapscript</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/how-to-debug-subroutine-called-in-sapscript/m-p/7240851#M1526302</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi, &lt;/P&gt;&lt;P&gt;I there any way how to debug subroutine called in sapscript by "perform form in program ZXYZ"? Setting (only session) breakpoint in that subroutine doesn't work....&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks for any reply.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards Jiri&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 17 Sep 2010 13:21:55 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/how-to-debug-subroutine-called-in-sapscript/m-p/7240851#M1526302</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2010-09-17T13:21:55Z</dc:date>
    </item>
    <item>
      <title>Re: How to debug subroutine called in sapscript</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/how-to-debug-subroutine-called-in-sapscript/m-p/7240852#M1526303</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;First screen of teransaction SE71 there is a menu option to enable debugging. Try that and see if it works.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 17 Sep 2010 13:23:08 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/how-to-debug-subroutine-called-in-sapscript/m-p/7240852#M1526303</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2010-09-17T13:23:08Z</dc:date>
    </item>
    <item>
      <title>Re: How to debug subroutine called in sapscript</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/how-to-debug-subroutine-called-in-sapscript/m-p/7240853#M1526304</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;The not so clean solution is to put &lt;/P&gt;&lt;PRE&gt;&lt;CODE&gt;
DATA: x_out.
DO.
   IF x_out IS NOT INITIAL.
     EXIT.
   ENDIF.
ENDDO.
&lt;/CODE&gt;&lt;/PRE&gt;&lt;P&gt;At the start of your subroutine.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;When you execute the print, go to SM50 and you'll see your subroutine running.&lt;/P&gt;&lt;P&gt;Select the row and then "Program/session -&amp;gt; Program -&amp;gt; Debug".&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 17 Sep 2010 15:48:20 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/how-to-debug-subroutine-called-in-sapscript/m-p/7240853#M1526304</guid>
      <dc:creator>SimoneMilesi</dc:creator>
      <dc:date>2010-09-17T15:48:20Z</dc:date>
    </item>
    <item>
      <title>Re: How to debug subroutine called in sapscript</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/how-to-debug-subroutine-called-in-sapscript/m-p/7240854#M1526305</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Place a break point in your subroutine, now activate the sap script debugger.&lt;/P&gt;&lt;P&gt;Press F5 and continue debugging in sap script once it reaches the statement where the routine is called it will take you to the code.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 17 Sep 2010 17:40:08 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/how-to-debug-subroutine-called-in-sapscript/m-p/7240854#M1526305</guid>
      <dc:creator>kesavadas_thekkillath</dc:creator>
      <dc:date>2010-09-17T17:40:08Z</dc:date>
    </item>
    <item>
      <title>Re: How to debug subroutine called in sapscript</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/how-to-debug-subroutine-called-in-sapscript/m-p/7240855#M1526306</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;How are you triggering the print program?  Are you generating an immediate print or doing a print preview?  An immediate print may be triggering a separate update call, hence breakpoint not triggered - either that or your ABAP code isn;t even being triggered.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If you're triggering an immediate print to a printer, I'd advise changing that to a print in scheduled job then running RSNAST00 in SE38 (if you're triggering from an output type).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Running RSNAST00, for your particular output, in SE38 should then cause your breakpoint to trigger, provided that code is being executed.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If you're running a print directly or a print preview then try one of the earlier suggestions in this post.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,    Andy&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 17 Sep 2010 23:48:10 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/how-to-debug-subroutine-called-in-sapscript/m-p/7240855#M1526306</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2010-09-17T23:48:10Z</dc:date>
    </item>
    <item>
      <title>Re: How to debug subroutine called in sapscript</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/how-to-debug-subroutine-called-in-sapscript/m-p/7240856#M1526307</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Yuri55,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;if the session breakpoint does not work although you start from the logon menu, then the form is not called properly, probably due to incorrect parameter transfer.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Anyway, switch on  sapscript debugger from se71, set breakpoint on PERFORM or step through to perform. At perform statement, enter /h and see where you get and what happens.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Clemens&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 18 Sep 2010 19:16:27 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/how-to-debug-subroutine-called-in-sapscript/m-p/7240856#M1526307</guid>
      <dc:creator>Clemenss</dc:creator>
      <dc:date>2010-09-18T19:16:27Z</dc:date>
    </item>
  </channel>
</rss>

