<?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: Prob in debugging code in exit EXIT_SAPLF050_004 in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/prob-in-debugging-code-in-exit-exit-saplf050-004/m-p/4323820#M1030291</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; It is always good to put a break point on the first line of the include and at the point where exit is called in the Standard SAP program.Also please check if the condition is satisfied to trigger your exit. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thnx!&lt;/P&gt;&lt;P&gt;Harry&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 25 Aug 2008 11:55:23 GMT</pubDate>
    <dc:creator>Former Member</dc:creator>
    <dc:date>2008-08-25T11:55:23Z</dc:date>
    <item>
      <title>Prob in debugging code in exit EXIT_SAPLF050_004</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/prob-in-debugging-code-in-exit-exit-saplf050-004/m-p/4323818#M1030289</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; In exit func mod EXIT_SAPLF050_004 in include ZX050U05 I've written my code. In the includ before executing my logic I've written break &amp;lt;userid&amp;gt;. But while debugging it's not working. But the include isactivated. &lt;/P&gt;&lt;P&gt;I'm testing it through idoc processing. In WE19. Idoc type FIDCCP02, message type FIDCC1, inbound func mod : IDOC_INPUT_FIDCC1. In this func md the exit is called.&lt;/P&gt;&lt;P&gt;Please help me in debugging the code in the exit.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;P&gt;Moumita&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 25 Aug 2008 08:27:21 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/prob-in-debugging-code-in-exit-exit-saplf050-004/m-p/4323818#M1030289</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-08-25T08:27:21Z</dc:date>
    </item>
    <item>
      <title>Re: Prob in debugging code in exit EXIT_SAPLF050_004</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/prob-in-debugging-code-in-exit-exit-saplf050-004/m-p/4323819#M1030290</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;Keep a break point in FM IDOC_INPUT_FIDCC1 at following perform.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;    PERFORM USER_EXIT_004 TABLES IDOC_DATA&lt;/P&gt;&lt;P&gt;                          USING  K_MESTYP_C1                "FIDCC1&lt;/P&gt;&lt;P&gt;                                 IDOC_CONTRL-DOCNUM&lt;/P&gt;&lt;P&gt;                                 IDOC_CONTRL   "für Basis-Idoctyp&lt;/P&gt;&lt;P&gt;                        CHANGING X-SEND_C1&lt;/P&gt;&lt;P&gt;                                 IDOC_STATUS.&lt;/P&gt;&lt;P&gt;then check whether its getting triggered or not.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Raju.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 25 Aug 2008 11:27:16 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/prob-in-debugging-code-in-exit-exit-saplf050-004/m-p/4323819#M1030290</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-08-25T11:27:16Z</dc:date>
    </item>
    <item>
      <title>Re: Prob in debugging code in exit EXIT_SAPLF050_004</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/prob-in-debugging-code-in-exit-exit-saplf050-004/m-p/4323820#M1030291</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; It is always good to put a break point on the first line of the include and at the point where exit is called in the Standard SAP program.Also please check if the condition is satisfied to trigger your exit. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thnx!&lt;/P&gt;&lt;P&gt;Harry&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 25 Aug 2008 11:55:23 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/prob-in-debugging-code-in-exit-exit-saplf050-004/m-p/4323820#M1030291</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-08-25T11:55:23Z</dc:date>
    </item>
  </channel>
</rss>

