<?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: BAPIs in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/bapis/m-p/1384161#M187196</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Do you mean BAdI?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;    &lt;/P&gt;&lt;UL&gt;&lt;LI level="1" type="ul"&gt;&lt;P&gt; Go to transaction SE80 in a client where you can experiment with the transaction that you are interested in.&lt;/P&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;    &lt;/P&gt;&lt;UL&gt;&lt;LI level="1" type="ul"&gt;&lt;P&gt;Go to class CL_EXITHANDLER. [Select Class / Interface from the drop-down, and put CL_EXITHANDLER for the class.]&lt;/P&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;    &lt;/P&gt;&lt;UL&gt;&lt;LI level="1" type="ul"&gt;&lt;P&gt;Go to method get_instance. [Press RETURN to ensure that the contents of the Object Name frame are for CL_EXITHANDLER. Expand the Methods node. Double-click on GET_INSTANCE.]&lt;/P&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;    &lt;/P&gt;&lt;UL&gt;&lt;LI level="1" type="ul"&gt;&lt;P&gt;Insert a breakpoint just after the call to the method cl_exithandler=&amp;gt;get_class_name_by_interface.&lt;/P&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;    &lt;/P&gt;&lt;UL&gt;&lt;LI level="1" type="ul"&gt;&lt;P&gt;Use the transaction in which you are BAdI-hunting.&lt;/P&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;    &lt;/P&gt;&lt;UL&gt;&lt;LI level="1" type="ul"&gt;&lt;P&gt;Examine the contents of the field exit_name whenever the processing stops at the breakpoint. I have found a case where exit_name was an unknown field. Then class_name gave a good clue to the name of the BAdI.&lt;/P&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 23 Aug 2006 14:57:30 GMT</pubDate>
    <dc:creator>Former Member</dc:creator>
    <dc:date>2006-08-23T14:57:30Z</dc:date>
    <item>
      <title>BAPIs</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/bapis/m-p/1384160#M187195</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi guys.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I need to know which BAPI is called when traansaction fp50 is enterd and which BAPI is called when transaction fpcg is called?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thank you guys in advance&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;will&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 20 Jul 2006 17:21:19 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/bapis/m-p/1384160#M187195</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2006-07-20T17:21:19Z</dc:date>
    </item>
    <item>
      <title>Re: BAPIs</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/bapis/m-p/1384161#M187196</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Do you mean BAdI?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;    &lt;/P&gt;&lt;UL&gt;&lt;LI level="1" type="ul"&gt;&lt;P&gt; Go to transaction SE80 in a client where you can experiment with the transaction that you are interested in.&lt;/P&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;    &lt;/P&gt;&lt;UL&gt;&lt;LI level="1" type="ul"&gt;&lt;P&gt;Go to class CL_EXITHANDLER. [Select Class / Interface from the drop-down, and put CL_EXITHANDLER for the class.]&lt;/P&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;    &lt;/P&gt;&lt;UL&gt;&lt;LI level="1" type="ul"&gt;&lt;P&gt;Go to method get_instance. [Press RETURN to ensure that the contents of the Object Name frame are for CL_EXITHANDLER. Expand the Methods node. Double-click on GET_INSTANCE.]&lt;/P&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;    &lt;/P&gt;&lt;UL&gt;&lt;LI level="1" type="ul"&gt;&lt;P&gt;Insert a breakpoint just after the call to the method cl_exithandler=&amp;gt;get_class_name_by_interface.&lt;/P&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;    &lt;/P&gt;&lt;UL&gt;&lt;LI level="1" type="ul"&gt;&lt;P&gt;Use the transaction in which you are BAdI-hunting.&lt;/P&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;    &lt;/P&gt;&lt;UL&gt;&lt;LI level="1" type="ul"&gt;&lt;P&gt;Examine the contents of the field exit_name whenever the processing stops at the breakpoint. I have found a case where exit_name was an unknown field. Then class_name gave a good clue to the name of the BAdI.&lt;/P&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 23 Aug 2006 14:57:30 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/bapis/m-p/1384161#M187196</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2006-08-23T14:57:30Z</dc:date>
    </item>
  </channel>
</rss>

