<?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: lock object in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/lock-object/m-p/1812644#M348274</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello Mahya&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If your application will change value in a DB table then you must lock the table (or at least the modified entry) against concurrent changes. If you do not lock and two user concurrently change the same table entry then the table entry will contain only the changes of the user that saved the data last.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If, for example, you change a debitor (XD02) and call a second screen and want to change the same debitor again the system will tell you that this debitor is already locked.&lt;/P&gt;&lt;P&gt;Therefore, locking is a crucial part of any application that changes DB table entries.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;  Uwe&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 01 Dec 2006 07:58:24 GMT</pubDate>
    <dc:creator>uwe_schieferstein</dc:creator>
    <dc:date>2006-12-01T07:58:24Z</dc:date>
    <item>
      <title>lock object</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/lock-object/m-p/1812642#M348272</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;what is a lock object ?&lt;/P&gt;&lt;P&gt;and what is it's use in real time ?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;thanks&lt;/P&gt;&lt;P&gt;mahya&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 01 Dec 2006 07:54:25 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/lock-object/m-p/1812642#M348272</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2006-12-01T07:54:25Z</dc:date>
    </item>
    <item>
      <title>Re: lock object</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/lock-object/m-p/1812643#M348273</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;The R/3 System synchronizes simultaneous access of several users to the same data records with a lock mechanism. When interactive transactions are programmed, locks are set and released by calling function modules. These function modules are automatically generated from the definition of lock objects in the ABAP Dictionary.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The tables in which data records should be locked with a lock request are defined in a lock object together with their key fields. When tables are selected, one table (the primary table) is first selected. Further tables (secondary tables) can also be added using foreign key relationships.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://help.sap.com/saphelp_nw2004s/helpdata/en/cf/21eea5446011d189700000e8322d00/content.htm" target="test_blank"&gt;http://help.sap.com/saphelp_nw2004s/helpdata/en/cf/21eea5446011d189700000e8322d00/content.htm&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://help.sap.com/saphelp_nw04/helpdata/en/7b/f9813712f7434be10000009b38f8cf/content.htm" target="test_blank"&gt;http://help.sap.com/saphelp_nw04/helpdata/en/7b/f9813712f7434be10000009b38f8cf/content.htm&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://www.sap-img.com/abap/type-and-uses-of-lock-objects-in-sap.htm" target="test_blank"&gt;http://www.sap-img.com/abap/type-and-uses-of-lock-objects-in-sap.htm&lt;/A&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 01 Dec 2006 07:57:36 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/lock-object/m-p/1812643#M348273</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2006-12-01T07:57:36Z</dc:date>
    </item>
    <item>
      <title>Re: lock object</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/lock-object/m-p/1812644#M348274</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello Mahya&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If your application will change value in a DB table then you must lock the table (or at least the modified entry) against concurrent changes. If you do not lock and two user concurrently change the same table entry then the table entry will contain only the changes of the user that saved the data last.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If, for example, you change a debitor (XD02) and call a second screen and want to change the same debitor again the system will tell you that this debitor is already locked.&lt;/P&gt;&lt;P&gt;Therefore, locking is a crucial part of any application that changes DB table entries.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;  Uwe&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 01 Dec 2006 07:58:24 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/lock-object/m-p/1812644#M348274</guid>
      <dc:creator>uwe_schieferstein</dc:creator>
      <dc:date>2006-12-01T07:58:24Z</dc:date>
    </item>
    <item>
      <title>Re: lock object</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/lock-object/m-p/1812645#M348275</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;The R/3 System synchronizes simultaneous access of several users to the same data records with a lock mechanism. When interactive transactions are programmed, locks are set and released by calling function modules . These function modules are automatically generated from the definition of lock objects in the ABAP Dictionary.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;chk this for the function modules&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://help.sap.com/saphelp_nw2004s/helpdata/en/af/22ab01dd0b11d1952000a0c929b3c3/content.htm" target="test_blank"&gt;http://help.sap.com/saphelp_nw2004s/helpdata/en/af/22ab01dd0b11d1952000a0c929b3c3/content.htm&lt;/A&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 01 Dec 2006 08:02:04 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/lock-object/m-p/1812645#M348275</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2006-12-01T08:02:04Z</dc:date>
    </item>
    <item>
      <title>Re: lock object</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/lock-object/m-p/1812646#M348276</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;   As generally i will explain what's the use of Lock objects in Real time.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;LOCK OBJECT : The R/3 System synchronizes simultaneous access of several users to the same data records with a lock mechanism. When interactive transactions are programmed, locks are set and released by calling function modules (see Function Modules for Lock Requests). These function modules are automatically generated from the definition of lock objects in the ABAP Dictionary.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;    &lt;/P&gt;&lt;P&gt;&amp;lt;b&amp;gt;Actually, when ever you want to update database tables, at that point of time, no other person should do any operation on that DB table. To do this , we will lock the DB object untill our operation is completed. To do this we will use LOCK OBJECTS.&amp;lt;/b&amp;gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;P&gt;Manju&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 01 Dec 2006 08:51:04 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/lock-object/m-p/1812646#M348276</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2006-12-01T08:51:04Z</dc:date>
    </item>
    <item>
      <title>Re: lock object</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/lock-object/m-p/1812647#M348277</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;The R/3 System synchronizes simultaneous access of several users to the same data records with a LOCK MECHANISM.Two owners, who can set locks, are created at the beginning of an R/3 transaction.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt; When interactive transactions are programmed, locks are set and released by calling function modules .These function modules are automatically generated from the definition of lock objects in the ABAP Dictionary.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;STRUCTURE:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The tables in which data records should be locked with a lock request are defined in a lock object together with their key fields. When tables are selected, one table (the primary table) is first selected. Further tables (secondary tables) can also be added using foreign key relationships &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;USE:&lt;/P&gt;&lt;P&gt;The main use of locks is to secure the information created,so that the lock owners will have the permission to modify.We have two functions ENQUEUE and DEQUEUE to set and release locks.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Gunasree.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 07 Dec 2006 08:39:05 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/lock-object/m-p/1812647#M348277</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2006-12-07T08:39:05Z</dc:date>
    </item>
  </channel>
</rss>

