<?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 mode in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/lock-mode/m-p/6543858#M1428491</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;S : Shared lock &lt;/P&gt;&lt;P&gt;E: Exclusive lock .&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The issue reported  should not happen because an exclusive lock set on an object that already has a shared lock will be rejected.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hence , there are chances that your S lock is released and then new lock in E mode happens.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Check this link &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://help.sap.com/saphelp_nw70/helpdata/en/12/038337fb02735ce10000009b38f8cf/frameset.htm" target="test_blank"&gt;http://help.sap.com/saphelp_nw70/helpdata/en/12/038337fb02735ce10000009b38f8cf/frameset.htm&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Edited by: Harsh Bhalla on Dec 20, 2009 7:53 PM&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Sun, 20 Dec 2009 14:22:30 GMT</pubDate>
    <dc:creator>Former Member</dc:creator>
    <dc:date>2009-12-20T14:22:30Z</dc:date>
    <item>
      <title>Lock mode</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/lock-mode/m-p/6543857#M1428490</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi all&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;when i locked a table with mode 'S', another user attemp for mode 'E'.&lt;/P&gt;&lt;P&gt;and my mode 'S' was cancelled.&lt;/P&gt;&lt;P&gt;Kindly explain what has actually happened ?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sun, 20 Dec 2009 14:18:18 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/lock-mode/m-p/6543857#M1428490</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2009-12-20T14:18:18Z</dc:date>
    </item>
    <item>
      <title>Re: Lock mode</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/lock-mode/m-p/6543858#M1428491</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;S : Shared lock &lt;/P&gt;&lt;P&gt;E: Exclusive lock .&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The issue reported  should not happen because an exclusive lock set on an object that already has a shared lock will be rejected.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hence , there are chances that your S lock is released and then new lock in E mode happens.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Check this link &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://help.sap.com/saphelp_nw70/helpdata/en/12/038337fb02735ce10000009b38f8cf/frameset.htm" target="test_blank"&gt;http://help.sap.com/saphelp_nw70/helpdata/en/12/038337fb02735ce10000009b38f8cf/frameset.htm&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Edited by: Harsh Bhalla on Dec 20, 2009 7:53 PM&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sun, 20 Dec 2009 14:22:30 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/lock-mode/m-p/6543858#M1428491</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2009-12-20T14:22:30Z</dc:date>
    </item>
    <item>
      <title>Re: Lock mode</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/lock-mode/m-p/6543859#M1428492</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;If a data record is locked in Mode 'S' and no further read locks are set by other users,&lt;/P&gt;&lt;P&gt;a lock attemp in Mode 'E' is possible.This generates a second entry in the lock table.&lt;/P&gt;&lt;P&gt;This is what has happened in your case.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sun, 20 Dec 2009 15:25:32 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/lock-mode/m-p/6543859#M1428492</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2009-12-20T15:25:32Z</dc:date>
    </item>
    <item>
      <title>Re: Lock mode</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/lock-mode/m-p/6543860#M1428493</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Vicky, Subin.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Your behaviour has been noticed.  Bye bye.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;matt&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sun, 20 Dec 2009 21:20:00 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/lock-mode/m-p/6543860#M1428493</guid>
      <dc:creator>matt</dc:creator>
      <dc:date>2009-12-20T21:20:00Z</dc:date>
    </item>
  </channel>
</rss>

