<?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: Weird lock concept in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/weird-lock-concept/m-p/11801385#M1954134</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;When do you know if something is inactive?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I had to create my own locking concept for a Fiori app since that does not support a pessimistic lock.&lt;/P&gt;&lt;P&gt;I investigated how long the process usually takes, then doubled that duration, in this case 5 minutes.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Basically when a user want to change something I add an entry in a table with a timestamp and its key and I give back the timestamp to the user.&lt;/P&gt;&lt;P&gt;Then when they save the change I check if the timestamp is the same and if so, the change is done.&lt;/P&gt;&lt;P&gt;If someone else wants to change the same object I check if their timestamp minus the one in the table is &amp;gt; 5 minutes if so, I overwrite the timestamp with theirs and if not I show them a message.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Kind regards, Rob Dielemans&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 16 Aug 2016 10:13:04 GMT</pubDate>
    <dc:creator>Former Member</dc:creator>
    <dc:date>2016-08-16T10:13:04Z</dc:date>
    <item>
      <title>Weird lock concept</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/weird-lock-concept/m-p/11801381#M1954130</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi guys,&lt;/P&gt;&lt;P&gt;I have to create a solution of some problem and I'm not sure if is that even possible.&lt;BR /&gt;There is Z-report which should lock some objects (Z-objects), but users quite often are disconnected from SAP and they want those locks to be dying with their's connection to SAP. Standard locks still exist, so what could help me? In other words: what is cleaned out when connection breaks down?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 15 Aug 2016 12:08:11 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/weird-lock-concept/m-p/11801381#M1954130</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2016-08-15T12:08:11Z</dc:date>
    </item>
    <item>
      <title>Re: Weird lock concept</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/weird-lock-concept/m-p/11801382#M1954131</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;When an internal mode is left at ABAP side, whatever it's left normally or abruptly stopped, the SAP locks are automatically removed.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;So, I guess your case is that the ABAP session is still there (it's just the frontend which had an error), and the user can see that when he logs in again, as the system will ask for logging out of the existing session.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Otherwise, it's abnormal, and you should contact the SAP support.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 15 Aug 2016 12:14:26 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/weird-lock-concept/m-p/11801382#M1954131</guid>
      <dc:creator>Sandra_Rossi</dc:creator>
      <dc:date>2016-08-15T12:14:26Z</dc:date>
    </item>
    <item>
      <title>Re: Weird lock concept</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/weird-lock-concept/m-p/11801383#M1954132</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Yes, I mean session still exists (and user is asked to kill it when is logging in) and they want to check somehow from another user if session which has to lock something is existing but "inactive" (connection has been broken down).&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 15 Aug 2016 12:30:41 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/weird-lock-concept/m-p/11801383#M1954132</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2016-08-15T12:30:41Z</dc:date>
    </item>
    <item>
      <title>Re: Weird lock concept</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/weird-lock-concept/m-p/11801384#M1954133</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Absolutely no idea whether it's possible automatically but I would think no (as the SAP solution, via SAP GUI, is to ask the user).&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 15 Aug 2016 17:39:23 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/weird-lock-concept/m-p/11801384#M1954133</guid>
      <dc:creator>Sandra_Rossi</dc:creator>
      <dc:date>2016-08-15T17:39:23Z</dc:date>
    </item>
    <item>
      <title>Re: Weird lock concept</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/weird-lock-concept/m-p/11801385#M1954134</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;When do you know if something is inactive?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I had to create my own locking concept for a Fiori app since that does not support a pessimistic lock.&lt;/P&gt;&lt;P&gt;I investigated how long the process usually takes, then doubled that duration, in this case 5 minutes.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Basically when a user want to change something I add an entry in a table with a timestamp and its key and I give back the timestamp to the user.&lt;/P&gt;&lt;P&gt;Then when they save the change I check if the timestamp is the same and if so, the change is done.&lt;/P&gt;&lt;P&gt;If someone else wants to change the same object I check if their timestamp minus the one in the table is &amp;gt; 5 minutes if so, I overwrite the timestamp with theirs and if not I show them a message.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Kind regards, Rob Dielemans&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 16 Aug 2016 10:13:04 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/weird-lock-concept/m-p/11801385#M1954134</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2016-08-16T10:13:04Z</dc:date>
    </item>
  </channel>
</rss>

