<?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: LUW in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/luw/m-p/1816696#M349585</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&amp;lt;b&amp;gt;LUW&amp;lt;/b&amp;gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Period of time between two consistent states on the database.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;lt;b&amp;gt;SAPLUW&amp;lt;/b&amp;gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Indivisible business process, which is performed either completely or not at all.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Related sequence of programming units which when executed can be distributed across several work processes (several database LUWs) as with, for example, dialog steps or remote function calls. However, database changes are made within one single database LUW. SAP LUWs are carried out by grouping techniques in which update function modules or subroutines, among other things, are registered in various work processes and executed by one single work process. An SAP LUW is completed by the open SQL statement COMMIT WORK. Changes within an SAP LUW can be undone with the open SQL statement ROLLBACK WORK.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;An SAP LUW usually has the same function as a dialog transaction (which maps a business process) and maps database changes made in dialog transactions to an update. A dialog transaction can, however, also include several SAP LUWs.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;lt;b&amp;gt;DBLUW&amp;lt;/b&amp;gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;see this link&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://help.sap.com/saphelp_nw2004s/helpdata/en/41/7af4bca79e11d1950f0000e82de14a/frameset.htm" target="test_blank"&gt;http://help.sap.com/saphelp_nw2004s/helpdata/en/41/7af4bca79e11d1950f0000e82de14a/frameset.htm&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Reward points if helpful.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;U. Uma&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 31 Jan 2007 05:54:56 GMT</pubDate>
    <dc:creator>Former Member</dc:creator>
    <dc:date>2007-01-31T05:54:56Z</dc:date>
    <item>
      <title>LUW</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/luw/m-p/1816691#M349580</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi experts what is LUW, DBLUW and SAPLUW can any one spot light on this..&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;Balu&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 31 Jan 2007 05:05:40 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/luw/m-p/1816691#M349580</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-01-31T05:05:40Z</dc:date>
    </item>
    <item>
      <title>Re: LUW</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/luw/m-p/1816692#M349581</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;got htru this URL:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://help.sap.com/saphelp_nw2004s/helpdata/en/41/7af4b9a79e11d1950f0000e82de14a/content.htm" target="test_blank"&gt;http://help.sap.com/saphelp_nw2004s/helpdata/en/41/7af4b9a79e11d1950f0000e82de14a/content.htm&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;Shiva&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 31 Jan 2007 05:13:07 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/luw/m-p/1816692#M349581</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-01-31T05:13:07Z</dc:date>
    </item>
    <item>
      <title>Re: LUW</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/luw/m-p/1816693#M349582</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Balu,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://www.allsaplinks.com/luw.html" target="test_blank"&gt;http://www.allsaplinks.com/luw.html&lt;/A&gt;&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;A href="http://help.sap.com/saphelp_sm32/helpdata/en/41/7af4bca79e11d1950f0000e82de14a/content.htm" target="test_blank"&gt;http://help.sap.com/saphelp_sm32/helpdata/en/41/7af4bca79e11d1950f0000e82de14a/content.htm&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="2816627"&gt;&lt;/A&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 31 Jan 2007 05:20:13 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/luw/m-p/1816693#M349582</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-01-31T05:20:13Z</dc:date>
    </item>
    <item>
      <title>Re: LUW</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/luw/m-p/1816694#M349583</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;LUW are twp types.&lt;/P&gt;&lt;P&gt;1.SAP LUW----COMMIT AT THE END OF TRANSACTION&lt;/P&gt;&lt;P&gt;2.DB LUW------COMMIT AFTER EVERY SCREEN&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Database LUW and SAP LUW&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;In the case of the database, an LUW is a sequence of data operations that cannot be divided up . The operations are either carried out in full or not at all. Database LUWs are modules which go to make up the database procedures for consistent data processing. An R/3 transaction can include several database LUWs (see example above), each of which can be terminated with a database COMMIT, which is generated automatically.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;By way of contrast, an LUW for the R/3 System is a business process, which cannot be divided up. The process is either executed in full or not at all. The SAP LUW of an R/3 transaction usually has to contain several database LUWs. Under normal circumstances, it contains a dialog transaction (which maps a business process), and the command for writing the data to the database (update).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;In each database LUW, data is written to the database to special update tables (and not to the application tables). Once the dialog area has been completed, all of the data in a database LUW is copied to the application tables: the update request is then performed&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Check these links.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://help.sap.com/saphelp_erp2005vp/helpdata/en/41/7af4c2a79e11d1950f0000e82de14a/frameset.htm" target="test_blank"&gt;http://help.sap.com/saphelp_erp2005vp/helpdata/en/41/7af4c2a79e11d1950f0000e82de14a/frameset.htm&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://help.sap.com/saphelp_erp2005vp/helpdata/en/41/7af4bca79e11d1950f0000e82de14a/frameset.htm" target="test_blank"&gt;http://help.sap.com/saphelp_erp2005vp/helpdata/en/41/7af4bca79e11d1950f0000e82de14a/frameset.htm&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://help.sap.com/saphelp_erp2005vp/helpdata/en/41/7af4b9a79e11d1950f0000e82de14a/frameset.htm" target="test_blank"&gt;http://help.sap.com/saphelp_erp2005vp/helpdata/en/41/7af4b9a79e11d1950f0000e82de14a/frameset.htm&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Priyanka.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 31 Jan 2007 05:26:05 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/luw/m-p/1816694#M349583</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-01-31T05:26:05Z</dc:date>
    </item>
    <item>
      <title>Re: LUW</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/luw/m-p/1816695#M349584</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;In my knowledge LUW IS nothing but LOGICAL UNIT OF WORK.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;thanks,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Shankar&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 31 Jan 2007 05:40:48 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/luw/m-p/1816695#M349584</guid>
      <dc:creator>p291102</dc:creator>
      <dc:date>2007-01-31T05:40:48Z</dc:date>
    </item>
    <item>
      <title>Re: LUW</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/luw/m-p/1816696#M349585</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&amp;lt;b&amp;gt;LUW&amp;lt;/b&amp;gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Period of time between two consistent states on the database.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;lt;b&amp;gt;SAPLUW&amp;lt;/b&amp;gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Indivisible business process, which is performed either completely or not at all.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Related sequence of programming units which when executed can be distributed across several work processes (several database LUWs) as with, for example, dialog steps or remote function calls. However, database changes are made within one single database LUW. SAP LUWs are carried out by grouping techniques in which update function modules or subroutines, among other things, are registered in various work processes and executed by one single work process. An SAP LUW is completed by the open SQL statement COMMIT WORK. Changes within an SAP LUW can be undone with the open SQL statement ROLLBACK WORK.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;An SAP LUW usually has the same function as a dialog transaction (which maps a business process) and maps database changes made in dialog transactions to an update. A dialog transaction can, however, also include several SAP LUWs.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;lt;b&amp;gt;DBLUW&amp;lt;/b&amp;gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;see this link&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://help.sap.com/saphelp_nw2004s/helpdata/en/41/7af4bca79e11d1950f0000e82de14a/frameset.htm" target="test_blank"&gt;http://help.sap.com/saphelp_nw2004s/helpdata/en/41/7af4bca79e11d1950f0000e82de14a/frameset.htm&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Reward points if helpful.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;U. Uma&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 31 Jan 2007 05:54:56 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/luw/m-p/1816696#M349585</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-01-31T05:54:56Z</dc:date>
    </item>
  </channel>
</rss>

