<?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: Local database update in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/local-database-update/m-p/3259602#M778666</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Do you mean&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;SET UPDATE TASK LOCAL. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This statement affects the execution of the update function modules (V1-posting). Without that statement the update is done asynchronously meaning that at the commit work the main process is ended and the user can continue to work in his session while the update is still running in the update work processes.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;In case the user needs to wait until all the V1-update modules are processed you can achieve this synchronous behavior by using the above statement which will return the control to the user only at the point where all the update tasks are processed.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;It has the same effect as COMMIT WORK AND WAIT.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hope that explains it,&lt;/P&gt;&lt;P&gt;Michael&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 17 Jan 2008 13:28:20 GMT</pubDate>
    <dc:creator>Former Member</dc:creator>
    <dc:date>2008-01-17T13:28:20Z</dc:date>
    <item>
      <title>Local database update</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/local-database-update/m-p/3259601#M778665</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;What is local database update mode?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 17 Jan 2008 12:49:54 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/local-database-update/m-p/3259601#M778665</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-01-17T12:49:54Z</dc:date>
    </item>
    <item>
      <title>Re: Local database update</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/local-database-update/m-p/3259602#M778666</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Do you mean&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;SET UPDATE TASK LOCAL. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This statement affects the execution of the update function modules (V1-posting). Without that statement the update is done asynchronously meaning that at the commit work the main process is ended and the user can continue to work in his session while the update is still running in the update work processes.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;In case the user needs to wait until all the V1-update modules are processed you can achieve this synchronous behavior by using the above statement which will return the control to the user only at the point where all the update tasks are processed.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;It has the same effect as COMMIT WORK AND WAIT.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hope that explains it,&lt;/P&gt;&lt;P&gt;Michael&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 17 Jan 2008 13:28:20 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/local-database-update/m-p/3259602#M778666</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-01-17T13:28:20Z</dc:date>
    </item>
  </channel>
</rss>

