<?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: Regarding BAPI in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/regarding-bapi/m-p/1772588#M333481</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Diffrence between BAPI and BDC:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;BAPI is used only when it is available for the particular  transaction like Delivery Sales order. but BDC can be used for any  transaction which have screen and fields. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;BAPI is directly updated the database instead BDC run through the screen flow. So BAPI can't handle all the flow logic checking and enhancement put by programmer to faciliate the user requirement. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;BAPI is a higher end usage for tranfering the data from SAP to non-SAP and vice-versa. for ex: if we are using VB application,where in that we want to connect to SAP and retireve the data,and then change and update the data in SAP for that purpose we can use that. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Apart from that, we can also use it for Uploading/Downloading the data from SAP to Non-SAP like BDC, provided we have an existing  BAPI for that.  &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;BAPI function modules will also do all the checks required for data integrity like Transactions for BDC. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;There is one more advantage using BAPI instead of BDC. When we go for upgradation, there might be pozzibility to change the screen elements for transactions depending on the requirement. In that case,our BDC pgm may or may not work (depending on the screen changes they have made). Unless and until we prepare new BDC we cant use the old BDC pgm. But in BAPI, SAP promises that they are going to keep the old BAPI and for new functionality they will provide an upgraded BAPI. Until we write a new BAPI pgm, we can use the exisitng BAPI pgm. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I hope it helps.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Best Regards,&lt;/P&gt;&lt;P&gt;Vibha &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;*Please mark all the helpful answers&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 13 Dec 2006 06:11:00 GMT</pubDate>
    <dc:creator>Former Member</dc:creator>
    <dc:date>2006-12-13T06:11:00Z</dc:date>
    <item>
      <title>Regarding BAPI</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/regarding-bapi/m-p/1772587#M333480</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;How BAPI is different from call transaction/session?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 13 Dec 2006 06:08:31 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/regarding-bapi/m-p/1772587#M333480</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2006-12-13T06:08:31Z</dc:date>
    </item>
    <item>
      <title>Re: Regarding BAPI</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/regarding-bapi/m-p/1772588#M333481</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Diffrence between BAPI and BDC:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;BAPI is used only when it is available for the particular  transaction like Delivery Sales order. but BDC can be used for any  transaction which have screen and fields. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;BAPI is directly updated the database instead BDC run through the screen flow. So BAPI can't handle all the flow logic checking and enhancement put by programmer to faciliate the user requirement. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;BAPI is a higher end usage for tranfering the data from SAP to non-SAP and vice-versa. for ex: if we are using VB application,where in that we want to connect to SAP and retireve the data,and then change and update the data in SAP for that purpose we can use that. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Apart from that, we can also use it for Uploading/Downloading the data from SAP to Non-SAP like BDC, provided we have an existing  BAPI for that.  &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;BAPI function modules will also do all the checks required for data integrity like Transactions for BDC. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;There is one more advantage using BAPI instead of BDC. When we go for upgradation, there might be pozzibility to change the screen elements for transactions depending on the requirement. In that case,our BDC pgm may or may not work (depending on the screen changes they have made). Unless and until we prepare new BDC we cant use the old BDC pgm. But in BAPI, SAP promises that they are going to keep the old BAPI and for new functionality they will provide an upgraded BAPI. Until we write a new BAPI pgm, we can use the exisitng BAPI pgm. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I hope it helps.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Best Regards,&lt;/P&gt;&lt;P&gt;Vibha &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;*Please mark all the helpful answers&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 13 Dec 2006 06:11:00 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/regarding-bapi/m-p/1772588#M333481</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2006-12-13T06:11:00Z</dc:date>
    </item>
    <item>
      <title>Re: Regarding BAPI</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/regarding-bapi/m-p/1772589#M333482</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;&amp;lt;b&amp;gt;&amp;lt;i&amp;gt;BAPI&amp;lt;/i&amp;gt;&amp;lt;/b&amp;gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;BAPI stands for Business API(Application Program Interface).&lt;/P&gt;&lt;P&gt;A BAPI is remotely enabled function module &lt;/P&gt;&lt;P&gt;ie it can be invoked from remote programs like standalone JAVA programs, web interface etc..&lt;/P&gt;&lt;P&gt;You can make your function module remotely enabled in attributes of Function module but&lt;/P&gt;&lt;P&gt;A BAPI are standard SAP function modules provided by SAP for remote access.&lt;/P&gt;&lt;P&gt;Also they are part of Businees Objest Repository(BOR).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;BAPI are RFC enabled function modules. the difference between RFc and BAPI are business objects. &lt;/P&gt;&lt;P&gt;You create business objects and those are then registered in your BOR (Business Object Repository) &lt;/P&gt;&lt;P&gt;which can be accessed outside the SAP system by using some other applications (Non-SAP) such as VB or JAVA.&lt;/P&gt;&lt;P&gt; In this case u only specify the business object and its method from external system &lt;/P&gt;&lt;P&gt;in BAPI there is no direct system call. while RFC are direct system call. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Some BAPIs provide basic functions and can be used for most SAP business object types. &lt;/P&gt;&lt;P&gt;These BAPIs should be implemented the same for all business object types. &lt;/P&gt;&lt;P&gt;Standardized BAPIs are easier to use and prevent users having to deal with a number of different BAPIs. &lt;/P&gt;&lt;P&gt;Whenever possible, a standardized BAPI must be used in preference to an individual BAPI. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;lt;b&amp;gt;&amp;lt;i&amp;gt;Session method.&amp;lt;/i&amp;gt;&amp;lt;/b&amp;gt; &lt;/P&gt;&lt;P&gt;1) synchronous processing. &lt;/P&gt;&lt;P&gt;2) can tranfer large amount of data. &lt;/P&gt;&lt;P&gt;3) processing is slower. &lt;/P&gt;&lt;P&gt;4) error log is created &lt;/P&gt;&lt;P&gt;5) data is not updated until session is processed. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;lt;b&amp;gt;&amp;lt;i&amp;gt;Call transaction.&amp;lt;/i&amp;gt;&amp;lt;/b&amp;gt; &lt;/P&gt;&lt;P&gt;1) asynchronous processing &lt;/P&gt;&lt;P&gt;2) can transfer small amount of data &lt;/P&gt;&lt;P&gt;3) processing is faster. &lt;/P&gt;&lt;P&gt;4) errors need to be handled explicitly &lt;/P&gt;&lt;P&gt;5) data is updated automatically &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Session method is to populate the data by filling BDC structure &lt;/P&gt;&lt;P&gt;and keep as session to process from SM37 to post in appropriate Transaction.&lt;/P&gt;&lt;P&gt;Call transaction method is to post the data directly into the Transaction from an Executable program.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Session method SAP defined Function modules.&lt;/P&gt;&lt;P&gt;U can see more help on the differences in the SAP help.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;rgds&lt;/P&gt;&lt;P&gt;Anver&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 13 Dec 2006 06:11:49 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/regarding-bapi/m-p/1772589#M333482</guid>
      <dc:creator>anversha_s</dc:creator>
      <dc:date>2006-12-13T06:11:49Z</dc:date>
    </item>
  </channel>
</rss>

