<?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: need of commit work  statement in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/need-of-commit-work-statement/m-p/11760159#M1951080</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;From the Keyword Documentation:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;PRE&gt;&lt;CODE&gt;The &lt;SPAN class="qtext"&gt;COMMIT WORK&lt;/SPAN&gt; statement closes the current &lt;A class="grey" title="Glossary Entry"&gt;SAP LUW&lt;/A&gt; and opens a new one&lt;/CODE&gt;&lt;/PRE&gt;&lt;P&gt;This is very important if you have&amp;nbsp; Situations where multiple datasets have to be modified. If one of the modifications fail, you want to do a ROLLBACK.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;But If you made other changes to the database those would be rolled back as well. So COMMIT WORK is basically just doing what the Documentation says:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;Closing the current SAP LUW&lt;/LI&gt;&lt;LI&gt;Opening a new SAP LUW&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This helps you to keep databse changes that have to be executed together to be in line even when there is a lock on the table or techical issues appear.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 08 Jun 2016 07:38:48 GMT</pubDate>
    <dc:creator>Former Member</dc:creator>
    <dc:date>2016-06-08T07:38:48Z</dc:date>
    <item>
      <title>need of commit work  statement</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/need-of-commit-work-statement/m-p/11760157#M1951078</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi everyone,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Can you please guide me know when we need to use &lt;STRONG&gt;Commit work &lt;/STRONG&gt;statement in SAP-ABAP, and when can we avoid&amp;nbsp; &lt;STRONG style="font-size: 13.3333px;"&gt;Commit work &lt;/STRONG&gt;&lt;SPAN style="font-size: 13.3333px;"&gt;statement.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 13.3333px;"&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 13.3333px;"&gt;Thanks &amp;amp; regards,&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 13.3333px;"&gt;Shravan&lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 08 Jun 2016 07:01:03 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/need-of-commit-work-statement/m-p/11760157#M1951078</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2016-06-08T07:01:03Z</dc:date>
    </item>
    <item>
      <title>Re: need of commit work  statement</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/need-of-commit-work-statement/m-p/11760158#M1951079</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;Check the below link, it will help u.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://help.sap.com/abapdocu_702/en/abapcommit.htm" title="http://help.sap.com/abapdocu_702/en/abapcommit.htm"&gt;ABAP Keyword Documentation&lt;/A&gt;&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, 08 Jun 2016 07:05:44 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/need-of-commit-work-statement/m-p/11760158#M1951079</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2016-06-08T07:05:44Z</dc:date>
    </item>
    <item>
      <title>Re: need of commit work  statement</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/need-of-commit-work-statement/m-p/11760159#M1951080</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;From the Keyword Documentation:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;PRE&gt;&lt;CODE&gt;The &lt;SPAN class="qtext"&gt;COMMIT WORK&lt;/SPAN&gt; statement closes the current &lt;A class="grey" title="Glossary Entry"&gt;SAP LUW&lt;/A&gt; and opens a new one&lt;/CODE&gt;&lt;/PRE&gt;&lt;P&gt;This is very important if you have&amp;nbsp; Situations where multiple datasets have to be modified. If one of the modifications fail, you want to do a ROLLBACK.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;But If you made other changes to the database those would be rolled back as well. So COMMIT WORK is basically just doing what the Documentation says:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;Closing the current SAP LUW&lt;/LI&gt;&lt;LI&gt;Opening a new SAP LUW&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This helps you to keep databse changes that have to be executed together to be in line even when there is a lock on the table or techical issues appear.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 08 Jun 2016 07:38:48 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/need-of-commit-work-statement/m-p/11760159#M1951080</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2016-06-08T07:38:48Z</dc:date>
    </item>
  </channel>
</rss>

