<?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: : bapi in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/bapi/m-p/2381998#M528813</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;Each dialog transaction that uses BAPIs to change data in one or more objects must directly&lt;/P&gt;&lt;P&gt;execute the COMMIT WORK command to save the data. The BAPI&lt;/P&gt;&lt;P&gt;BapiService.TransactionCommit() is used for this and it writes the changes to the database.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If data is not to be written to the database, the BAPI BapiService.TransactionRollback() can reset&lt;/P&gt;&lt;P&gt;the changes, provided that the changes have not already been passed to the database with the&lt;/P&gt;&lt;P&gt;BAPI. This works provided that the BAPI BapiService.TransactionCommit has not already&lt;/P&gt;&lt;P&gt;passed the changes to the database.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Reward useful points&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Siva&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 01 Jun 2007 11:47:36 GMT</pubDate>
    <dc:creator>Former Member</dc:creator>
    <dc:date>2007-06-01T11:47:36Z</dc:date>
    <item>
      <title>: bapi</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/bapi/m-p/2381997#M528812</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;hi  to all ,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;why should we use bapi_ transaction_commit in bapi instead of commit work.&lt;/P&gt;&lt;P&gt;also can we use the bapi_transaction_commit in user-exit.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards ,&lt;/P&gt;&lt;P&gt;Kiran.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 01 Jun 2007 11:31:26 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/bapi/m-p/2381997#M528812</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-06-01T11:31:26Z</dc:date>
    </item>
    <item>
      <title>Re: : bapi</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/bapi/m-p/2381998#M528813</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;Each dialog transaction that uses BAPIs to change data in one or more objects must directly&lt;/P&gt;&lt;P&gt;execute the COMMIT WORK command to save the data. The BAPI&lt;/P&gt;&lt;P&gt;BapiService.TransactionCommit() is used for this and it writes the changes to the database.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If data is not to be written to the database, the BAPI BapiService.TransactionRollback() can reset&lt;/P&gt;&lt;P&gt;the changes, provided that the changes have not already been passed to the database with the&lt;/P&gt;&lt;P&gt;BAPI. This works provided that the BAPI BapiService.TransactionCommit has not already&lt;/P&gt;&lt;P&gt;passed the changes to the database.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Reward useful points&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Siva&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 01 Jun 2007 11:47:36 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/bapi/m-p/2381998#M528813</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-06-01T11:47:36Z</dc:date>
    </item>
  </channel>
</rss>

