<?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: debug dunning smartform in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/debug-dunning-smartform/m-p/11735477#M1949115</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;PRE&gt;&lt;CODE&gt;
&lt;P&gt;Manivel S wrote:&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt; 3. In this function pool double click the F include. Here you can see your code and set a break-point and debug it.&lt;/P&gt;
&lt;P style="min-height: 8pt; height: 8pt; padding: 0px;"&gt;&lt;/P&gt;
&lt;/CODE&gt;&lt;/PRE&gt;&lt;P&gt;It's not much different than adding a break point in the form itself. As Sandra correctly pointed out, the issue here is not with finding a place for a breakpoint but the way the output is executed in a different process. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;@OP - kindly make sure to search in Google before posting. "debug dunning form site:sap.com" finds quite a few existing posts. &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 17 Jun 2016 16:10:11 GMT</pubDate>
    <dc:creator>Jelena_Perfiljeva</dc:creator>
    <dc:date>2016-06-17T16:10:11Z</dc:date>
    <item>
      <title>debug dunning smartform</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/debug-dunning-smartform/m-p/11735469#M1949107</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Experts,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I am trying to debug smartform attached to dunning letter , by keeping&amp;nbsp; break point in FM and hard coded breakpoint .&lt;/P&gt;&lt;P&gt;Still I am not able to debug it.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 26 May 2016 11:28:42 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/debug-dunning-smartform/m-p/11735469#M1949107</guid>
      <dc:creator>former_member249399</dc:creator>
      <dc:date>2016-05-26T11:28:42Z</dc:date>
    </item>
    <item>
      <title>Re: debug dunning smartform</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/debug-dunning-smartform/m-p/11735470#M1949108</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;If you want to debug a smartform, open the smartform and find a statement in the "program line". Goto the Fm, In the Main Program click on FIND to search the statement to place the break-point.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 26 May 2016 12:01:10 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/debug-dunning-smartform/m-p/11735470#M1949108</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2016-05-26T12:01:10Z</dc:date>
    </item>
    <item>
      <title>Re: debug dunning smartform</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/debug-dunning-smartform/m-p/11735471#M1949109</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Often, this is an issue related to the type of execution environment in which the ABAP is running, and there are different debug ways. For instance, ABAP in tRFC or in update task are to be activated via the debugger settings; for a background job, it's also different; for system programs, the system debugging must be activated, etc. etc. It's difficult to help you without being sure how your smartform is started. There are some blog posts which explain more about it.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 26 May 2016 21:06:26 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/debug-dunning-smartform/m-p/11735471#M1949109</guid>
      <dc:creator>Sandra_Rossi</dc:creator>
      <dc:date>2016-05-26T21:06:26Z</dc:date>
    </item>
    <item>
      <title>Re: debug dunning smartform</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/debug-dunning-smartform/m-p/11735472#M1949110</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Above all try using external break point in the Smart form FM code.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;regards,&lt;/P&gt;&lt;P&gt;Senthil&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 26 May 2016 21:43:27 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/debug-dunning-smartform/m-p/11735472#M1949110</guid>
      <dc:creator>senthil_kumar37</dc:creator>
      <dc:date>2016-05-26T21:43:27Z</dc:date>
    </item>
    <item>
      <title>Re: debug dunning smartform</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/debug-dunning-smartform/m-p/11735473#M1949111</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;usually not necessary to debug. Just use transaction SMARTFORM_TRACE, choose an adequate LEVEL (i.e. FIELDS) and analyze the trace.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This is great help with smartforms issues. At least you will know if or which form is called &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt;&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>Fri, 27 May 2016 08:59:07 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/debug-dunning-smartform/m-p/11735473#M1949111</guid>
      <dc:creator>Clemenss</dc:creator>
      <dc:date>2016-05-27T08:59:07Z</dc:date>
    </item>
    <item>
      <title>Re: debug dunning smartform</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/debug-dunning-smartform/m-p/11735474#M1949112</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thanks Clemens, I will try it.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 17 Jun 2016 04:32:01 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/debug-dunning-smartform/m-p/11735474#M1949112</guid>
      <dc:creator>former_member249399</dc:creator>
      <dc:date>2016-06-17T04:32:01Z</dc:date>
    </item>
    <item>
      <title>Re: debug dunning smartform</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/debug-dunning-smartform/m-p/11735475#M1949113</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;This message was moderated.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 17 Jun 2016 04:40:47 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/debug-dunning-smartform/m-p/11735475#M1949113</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2016-06-17T04:40:47Z</dc:date>
    </item>
    <item>
      <title>Re: debug dunning smartform</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/debug-dunning-smartform/m-p/11735476#M1949114</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Ranju,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Do the below steps.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;1. Execute your smart-form. You will get actual function module name like &lt;STRONG&gt;/1BCDWB/SF00000984.&amp;nbsp; &lt;/STRONG&gt;Copy this function module name.&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;&lt;BR /&gt;&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;2.Now go to SE38 and paste this function module name and add the SAPL as below&lt;/P&gt;&lt;P&gt;/1BCDWB/&lt;STRONG&gt;SAPL&lt;/STRONG&gt;SF00000984 and give display.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;3. In this function pool double click the F include. Here you can see your code and set a break-point and debug it.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Manivel S&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 17 Jun 2016 05:21:14 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/debug-dunning-smartform/m-p/11735476#M1949114</guid>
      <dc:creator>manivel</dc:creator>
      <dc:date>2016-06-17T05:21:14Z</dc:date>
    </item>
    <item>
      <title>Re: debug dunning smartform</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/debug-dunning-smartform/m-p/11735477#M1949115</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;PRE&gt;&lt;CODE&gt;
&lt;P&gt;Manivel S wrote:&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt; 3. In this function pool double click the F include. Here you can see your code and set a break-point and debug it.&lt;/P&gt;
&lt;P style="min-height: 8pt; height: 8pt; padding: 0px;"&gt;&lt;/P&gt;
&lt;/CODE&gt;&lt;/PRE&gt;&lt;P&gt;It's not much different than adding a break point in the form itself. As Sandra correctly pointed out, the issue here is not with finding a place for a breakpoint but the way the output is executed in a different process. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;@OP - kindly make sure to search in Google before posting. "debug dunning form site:sap.com" finds quite a few existing posts. &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 17 Jun 2016 16:10:11 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/debug-dunning-smartform/m-p/11735477#M1949115</guid>
      <dc:creator>Jelena_Perfiljeva</dc:creator>
      <dc:date>2016-06-17T16:10:11Z</dc:date>
    </item>
    <item>
      <title>Re: debug dunning smartform</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/debug-dunning-smartform/m-p/11735478#M1949116</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Ranju ,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Check the below link .&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://web.mit.edu/cao/www/SB2002/AR/F150.htm" title="http://web.mit.edu/cao/www/SB2002/AR/F150.htm"&gt;F150 - Print Dunning Letters&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Once the background job is scheduled . you can debug it through SM37 using the command JDBG.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If you face further difficulties I will send further screen shots how to debug.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;With Regards,&lt;/P&gt;&lt;P&gt;Sudhir S&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 17 Jun 2016 17:02:49 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/debug-dunning-smartform/m-p/11735478#M1949116</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2016-06-17T17:02:49Z</dc:date>
    </item>
  </channel>
</rss>

