<?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 PO print program in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/debug-po-print-program/m-p/1272191#M150588</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Lakhbir,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;There are several ways to keep breakpoints.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;1. Get the Layout name. Go in SE71, give layout/form name and enter in display mode. Use menu path Form Check --&amp;gt; Texts. It will display all associated driver programs. If you know your driver program name, place a breakpoint from SE38. Usually there should be a FORM ENTRY routine call. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;2. Go to program RSNAST00 -search for&lt;/P&gt;&lt;P&gt;    PERFORM (TNAPR-RONAM) IN PROGRAM (TNAPR-PGNAM) USING RETURNCODE&lt;/P&gt;&lt;P&gt;                                                         US_SCREEN&lt;/P&gt;&lt;P&gt;                                                         IF FOUND.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;PGNAM is program name, RONAM is Name of routine to be called up in the processing program.&lt;/P&gt;&lt;P&gt;Keep a break point. When you print from ME23N, control will come to this place in debugging mode.&lt;/P&gt;&lt;P&gt;Check form name, program name. Go to program and associated form and keep breakpoint.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hope this will help you.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 16 Mar 2006 17:12:39 GMT</pubDate>
    <dc:creator>Former Member</dc:creator>
    <dc:date>2006-03-16T17:12:39Z</dc:date>
    <item>
      <title>debug PO print program</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/debug-po-print-program/m-p/1272185#M150582</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi friends.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I am trying to debug PO print program, even after putting an endless loop.. it's not going to debug mode. Please help&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;P&gt;Lakhbir&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 16 Mar 2006 16:51:12 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/debug-po-print-program/m-p/1272185#M150582</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2006-03-16T16:51:12Z</dc:date>
    </item>
    <item>
      <title>Re: debug PO print program</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/debug-po-print-program/m-p/1272186#M150583</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Lakhbir,&lt;/P&gt;&lt;P&gt;  My suggestion is try to debug the SAP-layout form first(activate debugger),then find the elements which are getting triggered,then put a break-point in the print program at that write_form of the element &amp;amp; see.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 16 Mar 2006 16:53:46 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/debug-po-print-program/m-p/1272186#M150583</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2006-03-16T16:53:46Z</dc:date>
    </item>
    <item>
      <title>Re: debug PO print program</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/debug-po-print-program/m-p/1272187#M150584</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I would suggest putting a break point in the print program, then go to ME23N and click the print preview button, this will make the printing fire in dialog.  The debugger should show up.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Rich Heilman&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 16 Mar 2006 16:55:24 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/debug-po-print-program/m-p/1272187#M150584</guid>
      <dc:creator>RichHeilman</dc:creator>
      <dc:date>2006-03-16T16:55:24Z</dc:date>
    </item>
    <item>
      <title>Re: debug PO print program</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/debug-po-print-program/m-p/1272188#M150585</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Do you have "debug authorization" in your system?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 16 Mar 2006 16:55:43 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/debug-po-print-program/m-p/1272188#M150585</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2006-03-16T16:55:43Z</dc:date>
    </item>
    <item>
      <title>Re: debug PO print program</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/debug-po-print-program/m-p/1272189#M150586</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Lakhbir,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I am not sure putting an endless loop will help you in debugging. Why don't you put a hard BREAK-POINT in the program?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Ravi&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 16 Mar 2006 16:56:06 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/debug-po-print-program/m-p/1272189#M150586</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2006-03-16T16:56:06Z</dc:date>
    </item>
    <item>
      <title>Re: debug PO print program</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/debug-po-print-program/m-p/1272190#M150587</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi friends .&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I had tried all the options before posting the message.we are using Sap standard program SAPFM06P...the problem is i am not getting certain pricing conditions printed.. even they have Print indicator marked "X". &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;really don't know why?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 16 Mar 2006 17:12:17 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/debug-po-print-program/m-p/1272190#M150587</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2006-03-16T17:12:17Z</dc:date>
    </item>
    <item>
      <title>Re: debug PO print program</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/debug-po-print-program/m-p/1272191#M150588</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Lakhbir,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;There are several ways to keep breakpoints.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;1. Get the Layout name. Go in SE71, give layout/form name and enter in display mode. Use menu path Form Check --&amp;gt; Texts. It will display all associated driver programs. If you know your driver program name, place a breakpoint from SE38. Usually there should be a FORM ENTRY routine call. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;2. Go to program RSNAST00 -search for&lt;/P&gt;&lt;P&gt;    PERFORM (TNAPR-RONAM) IN PROGRAM (TNAPR-PGNAM) USING RETURNCODE&lt;/P&gt;&lt;P&gt;                                                         US_SCREEN&lt;/P&gt;&lt;P&gt;                                                         IF FOUND.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;PGNAM is program name, RONAM is Name of routine to be called up in the processing program.&lt;/P&gt;&lt;P&gt;Keep a break point. When you print from ME23N, control will come to this place in debugging mode.&lt;/P&gt;&lt;P&gt;Check form name, program name. Go to program and associated form and keep breakpoint.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hope this will help you.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 16 Mar 2006 17:12:39 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/debug-po-print-program/m-p/1272191#M150588</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2006-03-16T17:12:39Z</dc:date>
    </item>
    <item>
      <title>Re: debug PO print program</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/debug-po-print-program/m-p/1272192#M150589</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Lakhbir,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Did you look at the conditions on which the Pricing conditions get printed?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;regards,&lt;/P&gt;&lt;P&gt;Ravi&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 16 Mar 2006 17:13:38 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/debug-po-print-program/m-p/1272192#M150589</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2006-03-16T17:13:38Z</dc:date>
    </item>
    <item>
      <title>Re: debug PO print program</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/debug-po-print-program/m-p/1272193#M150590</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Lakhbir,&lt;/P&gt;&lt;P&gt;  First check whether the driver program attached is the SAP standard SAPFM06P or copied into a z program.&lt;/P&gt;&lt;P&gt;Go to NACE transaction &amp;amp; see this.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 16 Mar 2006 17:14:36 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/debug-po-print-program/m-p/1272193#M150590</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2006-03-16T17:14:36Z</dc:date>
    </item>
    <item>
      <title>Re: debug PO print program</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/debug-po-print-program/m-p/1272194#M150591</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;chk the print configuration in transaction NACE&lt;DEL&gt;&amp;gt; EF&lt;/DEL&gt;&amp;gt;Output types&lt;DEL&gt;&amp;gt;Processing routines&lt;/DEL&gt;&amp;gt; c the print program..if it is SAPFM06P, then goto function group MEDRUCK ( in SE80 )--&amp;gt; put a breakpoint in any of the function modules and try out..&lt;/P&gt;&lt;P&gt;Hope it helps,&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Bikash&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 16 Mar 2006 18:10:14 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/debug-po-print-program/m-p/1272194#M150591</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2006-03-16T18:10:14Z</dc:date>
    </item>
  </channel>
</rss>

