<?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: Short Dump (BAPI_TRANSACTION_COMMIT) in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/short-dump-bapi-transaction-commit/m-p/2608365#M598081</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;   It is not advisable to use the COMMIT WORK statement inside a User exit as it can lead to errors and/or inconsistencies.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You should NOT use Commit work &amp;amp; wait in a user exit as it can cause data integrity issues within the transaction.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;what you can do is use PERFORM &amp;lt;name&amp;gt; ON COMMIT&lt;/P&gt;&lt;P&gt;or call a function module in UPDATE TASK &lt;/P&gt;&lt;P&gt;this way your commit will happen when the transaction decides to commit the data.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;if you call a commit work , all the data will be commited to the db , both what you want to &amp;amp; what the standard code may/may not want to.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 25 Jul 2007 11:23:15 GMT</pubDate>
    <dc:creator>Former Member</dc:creator>
    <dc:date>2007-07-25T11:23:15Z</dc:date>
    <item>
      <title>Short Dump (BAPI_TRANSACTION_COMMIT)</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/short-dump-bapi-transaction-commit/m-p/2608364#M598080</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;i'm  trying to create a notification(IW22) in a userexit depending on some condition. i'm calling the BAPI 'BAPI_ALM_NOTIF_CREATE'. Everything works fine and i'm getting the notification no in the BAPI. But when i'm doing commit calling the BAPI 'BAPI_TRANSACTION_COMMIT'. Its giving dump&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Pls let me know if anyone has any suggestions how to overcome this&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks a lot&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 25 Jul 2007 11:18:54 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/short-dump-bapi-transaction-commit/m-p/2608364#M598080</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-07-25T11:18:54Z</dc:date>
    </item>
    <item>
      <title>Re: Short Dump (BAPI_TRANSACTION_COMMIT)</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/short-dump-bapi-transaction-commit/m-p/2608365#M598081</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;   It is not advisable to use the COMMIT WORK statement inside a User exit as it can lead to errors and/or inconsistencies.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You should NOT use Commit work &amp;amp; wait in a user exit as it can cause data integrity issues within the transaction.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;what you can do is use PERFORM &amp;lt;name&amp;gt; ON COMMIT&lt;/P&gt;&lt;P&gt;or call a function module in UPDATE TASK &lt;/P&gt;&lt;P&gt;this way your commit will happen when the transaction decides to commit the data.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;if you call a commit work , all the data will be commited to the db , both what you want to &amp;amp; what the standard code may/may not want to.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 25 Jul 2007 11:23:15 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/short-dump-bapi-transaction-commit/m-p/2608365#M598081</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-07-25T11:23:15Z</dc:date>
    </item>
    <item>
      <title>Re: Short Dump (BAPI_TRANSACTION_COMMIT)</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/short-dump-bapi-transaction-commit/m-p/2608366#M598082</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Kiran,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You mean i should put all the code related to calling the BAPI's inside the Perform.. on Commit?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Can i create another program and copy all the code in the program including COMMIT WORK and call that program using 'SUBMIT' from the user exit point.. will it work?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 25 Jul 2007 11:59:46 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/short-dump-bapi-transaction-commit/m-p/2608366#M598082</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-07-25T11:59:46Z</dc:date>
    </item>
    <item>
      <title>Re: Short Dump (BAPI_TRANSACTION_COMMIT)</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/short-dump-bapi-transaction-commit/m-p/2608367#M598083</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Guys,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;waiting for the suggestions&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 25 Jul 2007 12:35:43 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/short-dump-bapi-transaction-commit/m-p/2608367#M598083</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-07-25T12:35:43Z</dc:date>
    </item>
  </channel>
</rss>

