<?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: Tips on Debugging in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/tips-on-debugging/m-p/1899169#M375679</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;hi,&lt;/P&gt;&lt;P&gt;1) Goto se24 (Display class cl_exithandler)&lt;/P&gt;&lt;P&gt;2) Double click on the method GET_INSTANCE.&lt;/P&gt;&lt;P&gt;3) Put a break point at Line no.25 (CASE sy-subrc).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Now&lt;/P&gt;&lt;P&gt;4) Execute SAP standard transaction &lt;/P&gt;&lt;P&gt;5) Press the required button for which you need to write an exit logic, the execution will stop at the break point.&lt;/P&gt;&lt;P&gt;6) Check the values of variable 'exit_name', it will give you the BADI name called at that time.&lt;/P&gt;&lt;P&gt;7) This way you will find all the BADIs called on click of any button in any transaction&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;if you follow this 7 steps, you will find a suitable BADI&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Go to Se19 -&amp;gt; Badi Implementation and put a break point over there and run your transaction, there the cursor will be stoped and you will there in the debugger, and that will be a normal debugging, you can see the filed values and every thing.&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>Sat, 20 Jan 2007 12:44:30 GMT</pubDate>
    <dc:creator>Former Member</dc:creator>
    <dc:date>2007-01-20T12:44:30Z</dc:date>
    <item>
      <title>Tips on Debugging</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/tips-on-debugging/m-p/1899167#M375677</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello frnds,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Kindly suggest me tips over debugging BADIs&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;and some helpful sites too&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks &amp;amp; Regards.&lt;/P&gt;&lt;P&gt;Manmeet&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 20 Jan 2007 12:17:35 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/tips-on-debugging/m-p/1899167#M375677</guid>
      <dc:creator>former_member191391</dc:creator>
      <dc:date>2007-01-20T12:17:35Z</dc:date>
    </item>
    <item>
      <title>Re: Tips on Debugging</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/tips-on-debugging/m-p/1899168#M375678</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;hi Manmeet,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;you can do the following steps to debug the BAdI.&lt;/P&gt;&lt;P&gt;&amp;lt;b&amp;gt;&lt;/P&gt;&lt;P&gt;step1: Goto sE19 and enter the BAPI implementation name-&amp;gt;display&lt;/P&gt;&lt;P&gt;step2: choose the interface tab-&amp;gt;double click on the method which &lt;/P&gt;&lt;P&gt;          is under consideration&lt;/P&gt;&lt;P&gt;step3: code as below&amp;lt;/b&amp;gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;PRE&gt;&lt;CODE&gt;data lv_flag.
        while flag is initial.

         endwhile.&lt;/CODE&gt;&lt;/PRE&gt;&lt;P&gt;.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;lt;b&amp;gt;step4: Now activate the BAdI and execute the transaction, and do the necessary actions(save/delete etc)&lt;/P&gt;&lt;P&gt;step5: goto transaction sm50-&amp;gt;you can see your program there&lt;/P&gt;&lt;P&gt;step6: select your program from the list-&amp;gt;choose PROGRAM/SESSION from the &lt;/P&gt;&lt;P&gt;          menu-&amp;gt;Select PROGRAM-&amp;gt;DEBUGGING&amp;lt;/b&amp;gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;you are now in the debugger with the BAdI.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hope this helps.&lt;/P&gt;&lt;P&gt;Sajan Joseph.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Message was edited by: &lt;/P&gt;&lt;P&gt;&amp;lt;b&amp;gt;This is an infinite loop inside the BAdI; You should take this out, and re-activate the BAdI, once you are done with the debugging&amp;lt;/b&amp;gt;&lt;/P&gt;&lt;P&gt;        Sajan Joseph&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 20 Jan 2007 12:26:04 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/tips-on-debugging/m-p/1899168#M375678</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-01-20T12:26:04Z</dc:date>
    </item>
    <item>
      <title>Re: Tips on Debugging</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/tips-on-debugging/m-p/1899169#M375679</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;hi,&lt;/P&gt;&lt;P&gt;1) Goto se24 (Display class cl_exithandler)&lt;/P&gt;&lt;P&gt;2) Double click on the method GET_INSTANCE.&lt;/P&gt;&lt;P&gt;3) Put a break point at Line no.25 (CASE sy-subrc).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Now&lt;/P&gt;&lt;P&gt;4) Execute SAP standard transaction &lt;/P&gt;&lt;P&gt;5) Press the required button for which you need to write an exit logic, the execution will stop at the break point.&lt;/P&gt;&lt;P&gt;6) Check the values of variable 'exit_name', it will give you the BADI name called at that time.&lt;/P&gt;&lt;P&gt;7) This way you will find all the BADIs called on click of any button in any transaction&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;if you follow this 7 steps, you will find a suitable BADI&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Go to Se19 -&amp;gt; Badi Implementation and put a break point over there and run your transaction, there the cursor will be stoped and you will there in the debugger, and that will be a normal debugging, you can see the filed values and every thing.&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>Sat, 20 Jan 2007 12:44:30 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/tips-on-debugging/m-p/1899169#M375679</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-01-20T12:44:30Z</dc:date>
    </item>
    <item>
      <title>Re: Tips on Debugging</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/tips-on-debugging/m-p/1899170#M375680</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;First thing you may want to know is whether the BADI triggers or not by putting &lt;/P&gt;&lt;P&gt;1. break_point command.&lt;/P&gt;&lt;P&gt;2. or writing some endless loop in its implementation (SE19).&lt;/P&gt;&lt;P&gt;3. Referring its documentation to know its functional purpose.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;Santosh&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sun, 21 Jan 2007 04:26:11 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/tips-on-debugging/m-p/1899170#M375680</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-01-21T04:26:11Z</dc:date>
    </item>
  </channel>
</rss>

