<?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 General in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/general/m-p/2608408#M598103</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;hi to all viewers,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;what is commit work, what task performed and how. please give me example.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;thanks in advance and reward also.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;regard : deep&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 31 Jul 2007 04:52:38 GMT</pubDate>
    <dc:creator>Former Member</dc:creator>
    <dc:date>2007-07-31T04:52:38Z</dc:date>
    <item>
      <title>General</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/general/m-p/2608408#M598103</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;hi to all viewers,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;what is commit work, what task performed and how. please give me example.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;thanks in advance and reward also.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;regard : deep&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 31 Jul 2007 04:52:38 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/general/m-p/2608408#M598103</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-07-31T04:52:38Z</dc:date>
    </item>
    <item>
      <title>Re: General</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/general/m-p/2608409#M598104</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;To apply the changes made to the runtime objects of persistent classes to the actual persistent objects in the database, execute the COMMIT WORK statement&lt;/P&gt;&lt;P&gt;Commit work is used when you code directly in ABAP and make changes in the database and want to commit the database.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Commit work can be used when you trigger a workflow event by using Function module (swe_event_create) in your program.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 31 Jul 2007 04:54:55 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/general/m-p/2608409#M598104</guid>
      <dc:creator>former_member189059</dc:creator>
      <dc:date>2007-07-31T04:54:55Z</dc:date>
    </item>
    <item>
      <title>Re: General</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/general/m-p/2608410#M598105</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;commit work we will use in case of update tasks&lt;/P&gt;&lt;P&gt;see this simple example&lt;/P&gt;&lt;P&gt;REPORT ZTESTYD01. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;TABLES : ZYDTABLE01. &lt;/P&gt;&lt;P&gt;DATA: IT_TAB01 LIKE ZYDTABLE01 &lt;/P&gt;&lt;P&gt;OCCURS 0 WITH HEADER LINE. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;IT_TAB01-ZTEXT01 = 'DAVID'. &lt;/P&gt;&lt;P&gt;IT_TAB01-ZTEXT02 = 'VVVVV'. &lt;/P&gt;&lt;P&gt;APPEND IT_TAB01. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;*MODIFY ZYDTABLE01 FROM IT_TAB01. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;UPDATE ZYDTABLE01 &lt;/P&gt;&lt;P&gt;SET: ZTEXT02 = 'UPDATEDONE' &lt;/P&gt;&lt;P&gt;WHERE ZTEXT01 LIKE 'BG1'. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;INSERT INTO ZYDTABLE01 VALUES IT_TAB01. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;IF SY-SUBRC = 0. &lt;/P&gt;&lt;P&gt;COMMIT WORK. &lt;/P&gt;&lt;P&gt;ELSE. &lt;/P&gt;&lt;P&gt;ROLLBACK WORK. &lt;/P&gt;&lt;P&gt;ENDIF.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;see this link for more help.&lt;/P&gt;&lt;P&gt;&lt;A href="http://help.sap.com/saphelp_nw2004s/helpdata/en/d2/7849b8bec911d4b2e80050dadfb92b/content.htm" target="test_blank"&gt;http://help.sap.com/saphelp_nw2004s/helpdata/en/d2/7849b8bec911d4b2e80050dadfb92b/content.htm&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;lt;b&amp;gt;reward if helpful&amp;lt;/b&amp;gt;&lt;/P&gt;&lt;P&gt;rgds,&lt;/P&gt;&lt;P&gt;bharat.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 31 Jul 2007 04:55:51 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/general/m-p/2608410#M598105</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-07-31T04:55:51Z</dc:date>
    </item>
    <item>
      <title>Re: General</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/general/m-p/2608411#M598106</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;u&amp;gt;&lt;/P&gt;&lt;P&gt;COMMIT WORK&amp;lt;/u&amp;gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This is the standard form, which specifies asynchronous processing. &lt;/P&gt;&lt;P&gt;Your program does not wait for the requested functions to finish processing.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Rgds&lt;/P&gt;&lt;P&gt;Reshma&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 31 Jul 2007 04:55:55 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/general/m-p/2608411#M598106</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-07-31T04:55:55Z</dc:date>
    </item>
    <item>
      <title>Re: General</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/general/m-p/2608412#M598107</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi deep,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Commit Work - Executes a database commit and thus closes a logical processing unit or Logical Unit of Work ( LUW ) . &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This means that all database changes are made irrevocable and cannot be reversed with ROLLBACK WORK and all database locks are released. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hope this helps.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 31 Jul 2007 04:56:11 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/general/m-p/2608412#M598107</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-07-31T04:56:11Z</dc:date>
    </item>
    <item>
      <title>Re: General</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/general/m-p/2608413#M598108</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;working with BAPIS I usually have the same problem, when the BAPI generates a SAP document and after calling BAPI COMMIT WORK, with parameter WAIT set to X.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;update database.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 31 Jul 2007 04:57:05 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/general/m-p/2608413#M598108</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-07-31T04:57:05Z</dc:date>
    </item>
    <item>
      <title>Re: General</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/general/m-p/2608414#M598109</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;After performing the database updates(SAP LUW) You could use the ABAP Statement COMMIT WORK to confirm your database updates.This statement will apply any outstanding database updates and wait until they have actually been put on the database before proceeding to the next statement. &lt;/P&gt;&lt;P&gt;This means that&lt;/P&gt;&lt;UL&gt;&lt;LI level="1" type="ul"&gt;&lt;P&gt;all database changes are made irrevocable and cannot be reversed with ROLLBACK WORK and&lt;/P&gt;&lt;/LI&gt;&lt;LI level="1" type="ul"&gt;&lt;P&gt;all database locks are released. &lt;/P&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;COMMIT WORK also&lt;/P&gt;&lt;UL&gt;&lt;LI level="1" type="ul"&gt;&lt;P&gt;calls the subroutines specified by PERFORM ... ON COMMIT * executes asynchronously any update requests (see CALL FUNCTION ... IN UPDATE TASK ) specified in these subroutines or started just before,&lt;/P&gt;&lt;/LI&gt;&lt;LI level="1" type="ul"&gt;&lt;P&gt;processes the function modules specified in CALL FUNCTION ... IN BACKGROUND TASK ,&lt;/P&gt;&lt;/LI&gt;&lt;LI level="1" type="ul"&gt;&lt;P&gt;cancels all existing locks (see SAP locking concept ) if no update requests exist,&lt;/P&gt;&lt;/LI&gt;&lt;LI level="1" type="ul"&gt;&lt;P&gt;closes all open database cursors (see OPEN CURSOR ) and&lt;/P&gt;&lt;/LI&gt;&lt;LI level="1" type="ul"&gt;&lt;P&gt;resets the time slice counter to 0. &lt;/P&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Also refer to these threads&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A class="jive_macro jive_macro_message" href="https://community.sap.com/" __jive_macro_name="message" modifiedtitle="true" __default_attr="3444128"&gt;&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A class="jive_macro jive_macro_message" href="https://community.sap.com/" __jive_macro_name="message" modifiedtitle="true" __default_attr="3673995"&gt;&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hope these are helpful&lt;/P&gt;&lt;P&gt;Neerja&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 31 Jul 2007 04:57:43 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/general/m-p/2608414#M598109</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-07-31T04:57:43Z</dc:date>
    </item>
    <item>
      <title>Re: General</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/general/m-p/2608415#M598110</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;When ever you execute any database statement like  UPDATE or MODIFY or DELETE &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;the changes are not written to Database until you cimmit the cnages, this is due to the fact the there will be generally 2 or more steps when you do changes to Database, and all of the make sense only when all are a success so you wait untill all the statements are done and then say COMMIT WORK so that all the changes are done in Database if some failure occurs you will do ROLL BACK so that you go back to the status how it was before you have executed these DB statements.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Sesh&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 31 Jul 2007 04:59:22 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/general/m-p/2608415#M598110</guid>
      <dc:creator>seshatalpasai_madala</dc:creator>
      <dc:date>2007-07-31T04:59:22Z</dc:date>
    </item>
  </channel>
</rss>

