<?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 asynchronous processsing in eCatt in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/asynchronous-processsing-in-ecatt/m-p/4812986#M1126466</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;In the scenario that we are trying to automate, the processed that is triggered in the test system spawns an asynchronous process using QRFC. We do not want to proceed with the subsequent scripts (nodes in eCatt) unless these asynchronous processes are complete.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If we try to monitor the status of the queue from the eCatt system, losing the SAP GUI session will terminate the script that is monitoring the queue.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Is there a way in which we can allow the eCatt catalog to execute even if the GUI session is lost? Some kind of asynchronous processing?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Any help will be deeply appreciated. Thanks in advance.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;Ram&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 18 Nov 2008 12:46:55 GMT</pubDate>
    <dc:creator>Former Member</dc:creator>
    <dc:date>2008-11-18T12:46:55Z</dc:date>
    <item>
      <title>asynchronous processsing in eCatt</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/asynchronous-processsing-in-ecatt/m-p/4812986#M1126466</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;In the scenario that we are trying to automate, the processed that is triggered in the test system spawns an asynchronous process using QRFC. We do not want to proceed with the subsequent scripts (nodes in eCatt) unless these asynchronous processes are complete.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If we try to monitor the status of the queue from the eCatt system, losing the SAP GUI session will terminate the script that is monitoring the queue.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Is there a way in which we can allow the eCatt catalog to execute even if the GUI session is lost? Some kind of asynchronous processing?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Any help will be deeply appreciated. Thanks in advance.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;Ram&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 18 Nov 2008 12:46:55 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/asynchronous-processsing-in-ecatt/m-p/4812986#M1126466</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-11-18T12:46:55Z</dc:date>
    </item>
    <item>
      <title>Re: asynchronous processsing in eCatt</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/asynchronous-processsing-in-ecatt/m-p/4812987#M1126467</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;please introduce wait after the SAPGUI session close or&lt;/P&gt;&lt;P&gt;please check the database in case the ASYNC performs some database changes, once you are sure that database changes are done you can go further otherwise keep waiting in loop and check every 5 seconds.&lt;/P&gt;&lt;P&gt;best regards&lt;/P&gt;&lt;P&gt;vinay&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 19 Jun 2009 10:23:02 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/asynchronous-processsing-in-ecatt/m-p/4812987#M1126467</guid>
      <dc:creator>Vny12</dc:creator>
      <dc:date>2009-06-19T10:23:02Z</dc:date>
    </item>
    <item>
      <title>Re: asynchronous processsing in eCatt</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/asynchronous-processsing-in-ecatt/m-p/4812988#M1126468</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;As I understand there is an executed system and a  test system in your landscape connected by a RFC. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;eCATT provides a check box under RFC during start options under shared tab for asynchronous RFC.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You can also refer to this link : (Start modes for TCD)http://help.sap.com/saphelp_470/helpdata/EN/20/e81c3b84e65e7be10000000a11402f/frameset.htm&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Use 'X' mode if the recording is TCD for background processing (with asynchronous update). &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hope this helps ...&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 28 Aug 2009 08:48:15 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/asynchronous-processsing-in-ecatt/m-p/4812988#M1126468</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2009-08-28T08:48:15Z</dc:date>
    </item>
  </channel>
</rss>

