<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>SAP Flow &#187; SAP Logon</title>
	<atom:link href="http://www.sapflow.cz/archives/tag/sap-logon/feed" rel="self" type="application/rss+xml" />
	<link>http://www.sapflow.cz</link>
	<description>Anything can be done, it&#039;s just a matter of time and money...</description>
	<lastBuildDate>Thu, 02 Feb 2012 01:18:28 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	
		<item>
		<title>Override time-out limit in the SAP GUI !</title>
		<link>http://www.sapflow.cz/archives/85</link>
		<comments>http://www.sapflow.cz/archives/85#comments</comments>
		<pubDate>Wed, 15 Apr 2009 13:30:49 +0000</pubDate>
		<dc:creator>Pavel</dc:creator>
				<category><![CDATA[ABAP tips]]></category>
		<category><![CDATA[SAP]]></category>
		<category><![CDATA[SAP inactivity timeout]]></category>
		<category><![CDATA[SAP Logon]]></category>
		<category><![CDATA[SAP Tips & Tricks]]></category>

		<guid isPermaLink="false">http://www.sapflow.cz/?p=85</guid>
		<description><![CDATA[I guess most of SAP developers went through this case. You are remotely connected to SAP system through SAP Logon working on code, when your colleague comes/phone rings/bladder burns. So you interrupt your work for a couple of minutes and &#8230; SAP Logon automatically quits the session after some time with error-message saying that it [...]]]></description>
			<content:encoded><![CDATA[<p><img class="alignleft size-medium wp-image-139" title="sapgui-conn-aborted-fullscreen1" src="http://www.sapflow.cz/wp-content/uploads/2009/04/sapgui-conn-aborted-fullscreen1-300x184.jpg" alt="sapgui-conn-aborted-fullscreen1" width="300" height="184" />I guess most of SAP developers went through this case. You are remotely connected to SAP system through SAP Logon working on code, when your colleague comes/phone rings/bladder burns. So you interrupt your work for a couple of minutes and &#8230; SAP Logon automatically quits the session after some time with error-message saying that it has been closed due to time-out.</p>
<p>Solution: Keep on-line with ABAP programm running in background.</p>
<p>Step by step:</p>
<ol>
<li>Go to transaction SE38.</li>
<li>Type &#8220;ZKEEP&#8221; into the input field.</li>
<li>Click on &#8220;Create&#8221;.</li>
<li>Paste the following code.</li>
<li>Activate!</li>
</ol>
<pre style="text-align: justify;"><code>*&amp;---------------------------------------------------------------------*
*&amp;                              Report  ZKEEP                          *
*&amp;---------------------------------------------------------------------*
REPORT  ZKEEP                                  .
start-of-selection.
do.
wait up to 15 seconds.
CALL FUNCTION 'PROGRESS_INDICATOR'
EXPORTING
I_TEXT = 'Keeping...'.
enddo.</code></pre>
<p>Next time you log in to SAP, just open two sessions and in one go to SE38 and run this programm. You can than work in the other session (first one will be taken by the ZKEEP report).</p>
<p>That&#8217;s it for today.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.sapflow.cz/archives/85/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

