<?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: locking methods in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/locking-methods/m-p/2797523#M653104</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;Lock objects are use in SAP to avoid the inconsistancy at the time of data is being insert/change into database. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;SAP Provide three type of Lock objects.  &lt;/P&gt;&lt;P&gt;- &amp;lt;b&amp;gt;Read Lock(Shared Locked)&amp;lt;/b&amp;gt; &lt;/P&gt;&lt;P&gt;   protects read access to an object. The read lock allows other  transactions read access but not write access to  &lt;/P&gt;&lt;P&gt;   the locked area of  the table &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;- &amp;lt;b&amp;gt;Write Lock(exclusive lock)&amp;lt;/b&amp;gt; &lt;/P&gt;&lt;P&gt;   protects write access to an object. The write lock allows other  transactions neither read nor write access to  &lt;/P&gt;&lt;P&gt;    the locked area of the  table. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;- &amp;lt;b&amp;gt;Enhanced write lock (exclusive lock without cumulating)&amp;lt;/b&amp;gt; &lt;/P&gt;&lt;P&gt;  works like a write lock except that the enhanced write lock also  protects from further accesses from the  &lt;/P&gt;&lt;P&gt;  same transaction. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You can create a lock on a object of SAP thorugh transaction SE11 and enter any meaningful name start with EZ Example EZTEST_LOCK. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;lt;b&amp;gt;Use:&amp;lt;/b&amp;gt; you can see in almost all transaction when you are open an object in Change mode SAP could not allow to any other user to open the same object in change mode. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;lt;b&amp;gt;Example:&amp;lt;/b&amp;gt; in HR when we are enter a personal number in master data maintainance screen SAP can't allow to any other user to use same personal number for changes. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;lt;b&amp;gt;Technicaly:&amp;lt;/b&amp;gt; &lt;/P&gt;&lt;P&gt;When you create a lock object System automatically creat two function module. &lt;/P&gt;&lt;P&gt;1. ENQUEUE_&amp;lt;Lockobject name&amp;gt;. to insert the object in a queue. &lt;/P&gt;&lt;P&gt;2. DEQUEUE_&amp;lt;Lockobject name&amp;gt;. To remove the object is being queued through above FM. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You have to use these function module in your program. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hope this will give a basic idea. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Kindly go through this &amp;lt;b&amp;gt;SAP help&amp;lt;/b&amp;gt; link:&lt;/P&gt;&lt;P&gt;&lt;A href="http://help.sap.com/saphelp_47x200/helpdata/en/a2/3547360f2ea61fe10000009b38f839/frameset.htm" target="test_blank"&gt;http://help.sap.com/saphelp_47x200/helpdata/en/a2/3547360f2ea61fe10000009b38f839/frameset.htm&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Also, you can find more info in the following links:&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="3301061"&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="3337035"&gt;&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;best regards,&lt;/P&gt;&lt;P&gt;Thangesh&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 10 Sep 2007 15:00:28 GMT</pubDate>
    <dc:creator>Former Member</dc:creator>
    <dc:date>2007-09-10T15:00:28Z</dc:date>
    <item>
      <title>locking methods</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/locking-methods/m-p/2797522#M653103</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;hi &lt;/P&gt;&lt;P&gt;what are the locking tech available in SAP&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;explain each one&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 10 Sep 2007 14:53:42 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/locking-methods/m-p/2797522#M653103</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-09-10T14:53:42Z</dc:date>
    </item>
    <item>
      <title>Re: locking methods</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/locking-methods/m-p/2797523#M653104</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;Lock objects are use in SAP to avoid the inconsistancy at the time of data is being insert/change into database. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;SAP Provide three type of Lock objects.  &lt;/P&gt;&lt;P&gt;- &amp;lt;b&amp;gt;Read Lock(Shared Locked)&amp;lt;/b&amp;gt; &lt;/P&gt;&lt;P&gt;   protects read access to an object. The read lock allows other  transactions read access but not write access to  &lt;/P&gt;&lt;P&gt;   the locked area of  the table &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;- &amp;lt;b&amp;gt;Write Lock(exclusive lock)&amp;lt;/b&amp;gt; &lt;/P&gt;&lt;P&gt;   protects write access to an object. The write lock allows other  transactions neither read nor write access to  &lt;/P&gt;&lt;P&gt;    the locked area of the  table. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;- &amp;lt;b&amp;gt;Enhanced write lock (exclusive lock without cumulating)&amp;lt;/b&amp;gt; &lt;/P&gt;&lt;P&gt;  works like a write lock except that the enhanced write lock also  protects from further accesses from the  &lt;/P&gt;&lt;P&gt;  same transaction. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You can create a lock on a object of SAP thorugh transaction SE11 and enter any meaningful name start with EZ Example EZTEST_LOCK. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;lt;b&amp;gt;Use:&amp;lt;/b&amp;gt; you can see in almost all transaction when you are open an object in Change mode SAP could not allow to any other user to open the same object in change mode. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;lt;b&amp;gt;Example:&amp;lt;/b&amp;gt; in HR when we are enter a personal number in master data maintainance screen SAP can't allow to any other user to use same personal number for changes. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;lt;b&amp;gt;Technicaly:&amp;lt;/b&amp;gt; &lt;/P&gt;&lt;P&gt;When you create a lock object System automatically creat two function module. &lt;/P&gt;&lt;P&gt;1. ENQUEUE_&amp;lt;Lockobject name&amp;gt;. to insert the object in a queue. &lt;/P&gt;&lt;P&gt;2. DEQUEUE_&amp;lt;Lockobject name&amp;gt;. To remove the object is being queued through above FM. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You have to use these function module in your program. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hope this will give a basic idea. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Kindly go through this &amp;lt;b&amp;gt;SAP help&amp;lt;/b&amp;gt; link:&lt;/P&gt;&lt;P&gt;&lt;A href="http://help.sap.com/saphelp_47x200/helpdata/en/a2/3547360f2ea61fe10000009b38f839/frameset.htm" target="test_blank"&gt;http://help.sap.com/saphelp_47x200/helpdata/en/a2/3547360f2ea61fe10000009b38f839/frameset.htm&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Also, you can find more info in the following links:&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="3301061"&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="3337035"&gt;&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;best regards,&lt;/P&gt;&lt;P&gt;Thangesh&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 10 Sep 2007 15:00:28 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/locking-methods/m-p/2797523#M653104</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-09-10T15:00:28Z</dc:date>
    </item>
    <item>
      <title>Re: locking methods</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/locking-methods/m-p/2797524#M653105</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;Here is the perfect link for the SAP Locking Concept&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://help.sap.com/saphelp_nw04s/helpdata/en/c2/2d7037ecc92a7ee10000009b38f8cf/frameset.htm" target="test_blank"&gt;http://help.sap.com/saphelp_nw04s/helpdata/en/c2/2d7037ecc92a7ee10000009b38f8cf/frameset.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;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt; Sudheer&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 10 Sep 2007 15:03:54 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/locking-methods/m-p/2797524#M653105</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-09-10T15:03:54Z</dc:date>
    </item>
    <item>
      <title>Re: locking methods</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/locking-methods/m-p/2797525#M653106</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;b&amp;gt;Lock Objects&amp;lt;/b&amp;gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Lock object concept&lt;/P&gt;&lt;P&gt;Lock modes&lt;/P&gt;&lt;P&gt;Creating a lock object (example)&lt;/P&gt;&lt;P&gt;Lock object sample code&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;    SAP data dictionary provides you with a locking mechanism to synchronize simultaneous data access by different users.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Lock objects are created in SE11.&lt;/P&gt;&lt;P&gt;Customer lock objects must begin with EY or EZ .&lt;/P&gt;&lt;P&gt;Three possible lock modes exist for lock objects.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;lt;b&amp;gt;lock mode&amp;lt;/b&amp;gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Lock mode E: This sets a lock for changing data for single user. This lock can be accumulated.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Lock mode X: This mode is used like mode E  for changing data. The only technical difference from mode E is that the respective lock does not allow accumulation.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Lock mode S: This mode ensures that data displayed in your program cannot be changed by other users during the entire display time. Here you do not want to change the data yourself (allows read only access for data).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;lt;b&amp;gt;Creating Lock object&amp;lt;/b&amp;gt;&lt;/P&gt;&lt;P&gt;Enter lock object name beginning with EY or EZ&lt;/P&gt;&lt;P&gt;and hit create.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Enter  table names containing data records that should be locked and the lock mode.&lt;/P&gt;&lt;P&gt;    The primary keys of the specified tables are automatically selected as lock parameters.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;To set a lock in the application program&lt;/P&gt;&lt;P&gt;call a function module ENQUEUE_&amp;lt;LOCK_OBJECT&amp;gt;.&lt;/P&gt;&lt;P&gt;For our example, it would be ENQUEUE_EZMARA.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;To release the lock in the application program&lt;/P&gt;&lt;P&gt;call a function module DEQUEUE_&amp;lt;LOCK_OBJECT&amp;gt;.&lt;/P&gt;&lt;P&gt;For our example, it would be DEQUEUE_EZMARA.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Refer the code executed by user (say abap1) for&lt;/P&gt;&lt;P&gt;matnr = &amp;#146;000000000000000012&amp;#146;.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If another user (say abap2) tries to access the same data i.e. matnr = &amp;#145;000000000000000012&amp;#146;,via a program or a transaction it would deny him read or write access.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;reward if usefull&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 11 Sep 2007 04:34:00 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/locking-methods/m-p/2797525#M653106</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-09-11T04:34:00Z</dc:date>
    </item>
    <item>
      <title>Re: locking methods</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/locking-methods/m-p/2797526#M653107</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;please  go through this  link ... you  will learn how to  implement the  Lock Obects  for an  Table  .&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;lt;a href="http://help.sap.com/saphelp_nw04s/helpdata/en/af/22ab01dd0b11d1952000a0c929b3c3/content.htm"&amp;gt;http://help.sap.com/saphelp_nw04s/helpdata/en/af/22ab01dd0b11d1952000a0c929b3c3/content.htm&amp;lt;/a&amp;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;the  below link is  for  locking  methods  of the User  &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;lt;a href="http://www.sap-img.com/basis/different-methods-to-lock-or-unlock-sap-users.htm"&amp;gt;http://www.sap-img.com/basis/different-methods-to-lock-or-unlock-sap-users.htm&amp;lt;/a&amp;gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Reward  Points  if it is usefull .....&lt;/P&gt;&lt;P&gt;Girish&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 11 Sep 2007 06:34:51 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/locking-methods/m-p/2797526#M653107</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-09-11T06:34:51Z</dc:date>
    </item>
    <item>
      <title>Re: locking methods</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/locking-methods/m-p/2797527#M653108</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&lt;A href="http://help.sap.com/saphelp_nw04s/helpdata/en/af/22ab01dd0b11d1952000a0c929b3c3/content.htm" target="test_blank"&gt;http://help.sap.com/saphelp_nw04s/helpdata/en/af/22ab01dd0b11d1952000a0c929b3c3/content.htm&lt;/A&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 12 Sep 2007 05:29:02 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/locking-methods/m-p/2797527#M653108</guid>
      <dc:creator>former_member196517</dc:creator>
      <dc:date>2007-09-12T05:29:02Z</dc:date>
    </item>
  </channel>
</rss>

