<?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 LUW in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/luw/m-p/3107329#M737686</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;what is this ? and explain me the concept&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 23 Nov 2007 08:54:07 GMT</pubDate>
    <dc:creator>Former Member</dc:creator>
    <dc:date>2007-11-23T08:54:07Z</dc:date>
    <item>
      <title>LUW</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/luw/m-p/3107329#M737686</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;what is this ? and explain me the concept&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 23 Nov 2007 08:54:07 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/luw/m-p/3107329#M737686</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-11-23T08:54:07Z</dc:date>
    </item>
    <item>
      <title>Re: LUW</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/luw/m-p/3107330#M737687</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Logical Unit of Work (LUW) &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;A Logical Unit of Work (LUW or database transaction) is an inseparable sequence of database operations which must be executed either in its entirety or not at all. For the database system, it thus constitutes a unit. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;LUWs help to guarantee database integrity. When an LUW has been successfully concluded, the database is once again in a correct state. If, however, an error occurs within an LUW, all database changes made since the beginning of the LUW are canceled and the database is then in the same state as before the LUW started. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;An LUW begins &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;each time you start a transaction &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;when the database changes of the previous LUW have been confirmed (database commit) or &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;when the database changes of the previous LUW have been cancelled (database rollback) &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;An LUW ends &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;when the database changes have been confirmed (database commit) or &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;when the database changes have been canceled (database rollback)&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 23 Nov 2007 08:55:46 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/luw/m-p/3107330#M737687</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-11-23T08:55:46Z</dc:date>
    </item>
    <item>
      <title>Re: LUW</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/luw/m-p/3107331#M737688</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;&lt;/P&gt;&lt;P&gt;   LUW ( Logical unit of work ) is spam of time during which any database must update performed.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Prashant&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Message was edited by: &lt;/P&gt;&lt;P&gt;        Prashant Patil&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 23 Nov 2007 08:56:09 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/luw/m-p/3107331#M737688</guid>
      <dc:creator>former_member386202</dc:creator>
      <dc:date>2007-11-23T08:56:09Z</dc:date>
    </item>
    <item>
      <title>Re: LUW</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/luw/m-p/3107332#M737689</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi sandhya mehar, &lt;/P&gt;&lt;P&gt; &lt;/P&gt;&lt;P&gt;What is LUW?&lt;/P&gt;&lt;P&gt;Logical Unit of Work &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Different types of LUWs. What r they?&lt;/P&gt;&lt;P&gt;Two types of LUW are:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;1)DB LUW - A database LUW is the mechanism used by the database to ensure that its data is always consistent. A database LUW &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;is an inseparable sequence of database operations that ends with a database commit. The database LUW is either fully executed &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;by the database system or not at all. Once a database LUW has been successfully executed, the database will be in a &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;consistent state. If an error occurs within a database LUW, all of the database changes since the beginning of the database &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;LUW are reversed. This leaves the database in the state it had before the transaction started.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;2)SAP LUW - A logical unit consisting of dialog steps, whose changes are written to the database in a single database LUW is &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;called an SAP LUW. Unlike a database LUW, an SAP LUW can span several dialog steps, and be executed using a series of &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;different work processes.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;What is LUW  or Data base Transaction ?&lt;/P&gt;&lt;P&gt;A &amp;#147;LUW&amp;#148;(logical unit of work) is the span of time during which any database updates must be performed in an &amp;#147;all or nothing&amp;#148; &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;manner .Either they are all performed (committed),or they are all thrown  away (rolled back).In the ABAP/4 world , LUWs and &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Transactions can have several meanings:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;LUW (or &amp;#147;database LUW&amp;#148; or &amp;#147;database transaction&amp;#148;)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This is the set of updates terminated by a database commit. A LUW lasts, at most, from one screen change to the next (because &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;the SAP system triggers database commits automatically at every screen change).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;What is SAP LUW or Update Transaction?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Update transaction (or &amp;#147;SAP LUW&amp;#148;)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This is a set of updates terminated by an ABAP/4 commit.  A SAP LUW may last much longer than a database LUW, since most &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;update processing extends over multiple transaction screens.  The programmer terminates an update transaction by issuing a &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;COMMIT WORK statement.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;-Transactions run with a separate SAP LUW&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;-Reports run with a separate SAP LUW.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;-Dialog modules run in the same SAP LUW as the caller&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;-Function modules run in the same SAP LUW as the caller.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The only exceptions to the above rules are function modules called with IN UPDATE TASK (V2 function only) or IN BACKGROUND &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;TASK (ALE applications).  These always run in their own (separate) update transactions.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;SAP LUW &lt;/P&gt;&lt;P&gt;&lt;A href="http://help.sap.com/saphelp_nw04/helpdata/en/41/7af4bfa79e11d1950f0000e82de14a/content.htm" target="test_blank"&gt;http://help.sap.com/saphelp_nw04/helpdata/en/41/7af4bfa79e11d1950f0000e82de14a/content.htm&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Features of the Update &lt;/P&gt;&lt;P&gt;&lt;A href="http://help.sap.com/saphelp_nw04s/helpdata/en/e5/de86d835cd11d3acb00000e83539c3/content.htm" target="test_blank"&gt;http://help.sap.com/saphelp_nw04s/helpdata/en/e5/de86d835cd11d3acb00000e83539c3/content.htm&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Check this thread for further details on LUW&lt;/P&gt;&lt;P&gt;&lt;A class="jive_macro jive_macro_thread" href="https://community.sap.com/" __jive_macro_name="thread" modifiedtitle="true" __default_attr="46301"&gt;&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;cheers!&lt;/P&gt;&lt;P&gt;gyanaraj&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;****Pls reward points if u find this helpful&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 23 Nov 2007 09:24:37 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/luw/m-p/3107332#M737689</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-11-23T09:24:37Z</dc:date>
    </item>
  </channel>
</rss>

