<?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>Question Re: SOAP Timeout requirement using SAP PI in Technology Q&amp;A</title>
    <link>https://community.sap.com/t5/technology-q-a/soap-timeout-requirement-using-sap-pi/qaa-p/7941853#M2838121</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;PRE&gt;&lt;CODE&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt; Now the question is&lt;/P&gt;&lt;P&gt;&amp;gt; - Will SAP CRM be able to read/parse that technical error message in their system (since it is not in the expected response format)?&lt;/P&gt;&lt;/CODE&gt;&lt;/PRE&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;the proxy will go into a system fault/application fault.&lt;/P&gt;&lt;P&gt;you will need to handle this and then throw a readable message back to CRM user.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;PRE&gt;&lt;CODE&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;gt; - Does SAP CRM have the ability to set a time-out parameter at their end itself instead of depending on the web-service response or SAP PI's technical response?&lt;/P&gt;&lt;P&gt;&amp;gt; &lt;/P&gt;&lt;P&gt;&amp;gt; Need you inputs in the 2nd case. And also any suggestion to achieve the requirement is welcome.&lt;/P&gt;&lt;P&gt;&amp;gt; &lt;/P&gt;&lt;P&gt;&amp;gt; Regards,&lt;/P&gt;&lt;P&gt;&amp;gt; Prajeet&lt;/P&gt;&lt;/CODE&gt;&lt;/PRE&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;you can set a timeout at SOAP adapter. Check the SOAP FAQ OSS note for the parameter. this will again raise an exception in ABAP proxy which you should be able to handle&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Sun, 19 Jun 2011 15:42:05 GMT</pubDate>
    <dc:creator>Shabarish_Nair</dc:creator>
    <dc:date>2011-06-19T15:42:05Z</dc:date>
    <item>
      <title>SOAP Timeout requirement using SAP PI</title>
      <link>https://community.sap.com/t5/technology-q-a/soap-timeout-requirement-using-sap-pi/qaq-p/7941850</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;The *synchronous* scenario is as shown below&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;SAP CRM - &lt;EM&gt;ABAP Proxy&lt;/EM&gt; -&amp;gt; SAP PI -- &lt;EM&gt;webservice-call&lt;/EM&gt; --&amp;gt; External Partner &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The requirement is that, SAP CRM needs to set a time-out in one of the screen incase the synchronous call takes more than 'n' seconds.&lt;/P&gt;&lt;P&gt;1st case: What if the web-service takes 'n' seconds to return a response&lt;/P&gt;&lt;P&gt;Resolution: The external partner has agreed that if the web-service takes 'n' seconds, then they would set a generic status and send a response message back to SAP PI&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;2nd case: What if the web service URL is not reachable. How do we achieve the time-out requirement at SAP CRM.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;In this case, since this is a synchronous scenario, a auto-generated technical error message would be sent back by SAP PI to SAP CRM. Now the question is&lt;/P&gt;&lt;P&gt;- Will SAP CRM be able to read/parse that technical error message in their system (since it is not in the expected response format)?&lt;/P&gt;&lt;P&gt;- Does SAP CRM have the ability to set a time-out parameter at their end itself instead of depending on the web-service response or SAP PI's technical response?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Need you inputs in the 2nd case. And also any suggestion to achieve the requirement is welcome.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Prajeet&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 17 Jun 2011 19:08:15 GMT</pubDate>
      <guid>https://community.sap.com/t5/technology-q-a/soap-timeout-requirement-using-sap-pi/qaq-p/7941850</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2011-06-17T19:08:15Z</dc:date>
    </item>
    <item>
      <title>Re: SOAP Timeout requirement using SAP PI</title>
      <link>https://community.sap.com/t5/technology-q-a/soap-timeout-requirement-using-sap-pi/qaa-p/7941851#M2838119</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Regarding the technical response from PI, you can customize the error messages by creating a Fault Message Type. Please check the help page below.&lt;/P&gt;&lt;P&gt;&lt;A href="http://help.sap.com/saphelp_nwpi71/helpdata/en/dd/b7623c6369f454e10000000a114084/content.htm" target="test_blank"&gt;http://help.sap.com/saphelp_nwpi71/helpdata/en/dd/b7623c6369f454e10000000a114084/content.htm&lt;/A&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 17 Jun 2011 21:05:10 GMT</pubDate>
      <guid>https://community.sap.com/t5/technology-q-a/soap-timeout-requirement-using-sap-pi/qaa-p/7941851#M2838119</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2011-06-17T21:05:10Z</dc:date>
    </item>
    <item>
      <title>Re: SOAP Timeout requirement using SAP PI</title>
      <link>https://community.sap.com/t5/technology-q-a/soap-timeout-requirement-using-sap-pi/qaa-p/7941852#M2838120</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Prajeeth,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;   go through the note #1593920 which would help for your query.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Naveen.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 18 Jun 2011 13:16:10 GMT</pubDate>
      <guid>https://community.sap.com/t5/technology-q-a/soap-timeout-requirement-using-sap-pi/qaa-p/7941852#M2838120</guid>
      <dc:creator>naveen_chichili</dc:creator>
      <dc:date>2011-06-18T13:16:10Z</dc:date>
    </item>
    <item>
      <title>Re: SOAP Timeout requirement using SAP PI</title>
      <link>https://community.sap.com/t5/technology-q-a/soap-timeout-requirement-using-sap-pi/qaa-p/7941853#M2838121</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;PRE&gt;&lt;CODE&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt; Now the question is&lt;/P&gt;&lt;P&gt;&amp;gt; - Will SAP CRM be able to read/parse that technical error message in their system (since it is not in the expected response format)?&lt;/P&gt;&lt;/CODE&gt;&lt;/PRE&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;the proxy will go into a system fault/application fault.&lt;/P&gt;&lt;P&gt;you will need to handle this and then throw a readable message back to CRM user.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;PRE&gt;&lt;CODE&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;gt; - Does SAP CRM have the ability to set a time-out parameter at their end itself instead of depending on the web-service response or SAP PI's technical response?&lt;/P&gt;&lt;P&gt;&amp;gt; &lt;/P&gt;&lt;P&gt;&amp;gt; Need you inputs in the 2nd case. And also any suggestion to achieve the requirement is welcome.&lt;/P&gt;&lt;P&gt;&amp;gt; &lt;/P&gt;&lt;P&gt;&amp;gt; Regards,&lt;/P&gt;&lt;P&gt;&amp;gt; Prajeet&lt;/P&gt;&lt;/CODE&gt;&lt;/PRE&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;you can set a timeout at SOAP adapter. Check the SOAP FAQ OSS note for the parameter. this will again raise an exception in ABAP proxy which you should be able to handle&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sun, 19 Jun 2011 15:42:05 GMT</pubDate>
      <guid>https://community.sap.com/t5/technology-q-a/soap-timeout-requirement-using-sap-pi/qaa-p/7941853#M2838121</guid>
      <dc:creator>Shabarish_Nair</dc:creator>
      <dc:date>2011-06-19T15:42:05Z</dc:date>
    </item>
    <item>
      <title>Re: SOAP Timeout requirement using SAP PI</title>
      <link>https://community.sap.com/t5/technology-q-a/soap-timeout-requirement-using-sap-pi/qaa-p/7941854#M2838122</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Lucas,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Please help me out here.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;My understanding of using fault message type is that this message has to be triggered by the receiver system, right?&lt;/P&gt;&lt;P&gt;But in my scenario, if the recevier URL is not reachable, then receiver would not be sending the message, in that case, how do we populate the fault message to SAP CRM?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Prajeet&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 21 Jun 2011 16:09:20 GMT</pubDate>
      <guid>https://community.sap.com/t5/technology-q-a/soap-timeout-requirement-using-sap-pi/qaa-p/7941854#M2838122</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2011-06-21T16:09:20Z</dc:date>
    </item>
    <item>
      <title>Re: SOAP Timeout requirement using SAP PI</title>
      <link>https://community.sap.com/t5/technology-q-a/soap-timeout-requirement-using-sap-pi/qaa-p/7941855#M2838123</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;The issue was resolved. We did it in 2 steps&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;U&gt;&lt;STRONG&gt;Step-1&lt;/STRONG&gt;&lt;/U&gt;: A time-out parameter was set in the SOAP receiver channel in SAP PI&lt;/P&gt;&lt;P&gt;Parameter Name : &lt;STRONG&gt;XMBWS.Timeout&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;U&gt;&lt;STRONG&gt;Step-2&lt;/STRONG&gt;&lt;/U&gt;: SAP CRM system handled the standard exception message generated by SAP PI using &lt;STRONG&gt;cx_ai_system_fault&lt;/STRONG&gt; class. Based on the exception text in the message, CRM proceeded with the next steps of processing&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Just to give more information on the scenarios I was looking at&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;1st case&lt;/STRONG&gt;: What if the web-service takes 'n' seconds to return a response&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Resolution&lt;/STRONG&gt; : Due to the time-out parameter set to 'n' seconds in the SOAP receiver channel, SAP PI would generate a standard exception message after 'n' seconds and sends it to SAP CRM.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;U&gt;&lt;EM&gt;SAP PI Standard Exception Message&lt;/EM&gt;&lt;/U&gt;&lt;/P&gt;&lt;P&gt;&amp;lt;SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1"&amp;gt;&lt;/P&gt;&lt;P&gt;  &amp;lt;SAP:Category&amp;gt;XIAdapterFramework&amp;lt;/SAP:Category&amp;gt; &lt;/P&gt;&lt;P&gt;  &amp;lt;SAP:Code area="MESSAGE"&amp;gt;GENERAL&amp;lt;/SAP:Code&amp;gt; &lt;/P&gt;&lt;P&gt;  &amp;lt;SAP:P1 /&amp;gt; &lt;/P&gt;&lt;P&gt;  &amp;lt;SAP:P2 /&amp;gt; &lt;/P&gt;&lt;P&gt;  &amp;lt;SAP:P3 /&amp;gt; &lt;/P&gt;&lt;P&gt;  &amp;lt;SAP:P4 /&amp;gt; &lt;/P&gt;&lt;P&gt;  &amp;lt;SAP:AdditionalText&amp;gt;com.sap.aii.af.ra.ms.api.DeliveryException: Read timed out&amp;lt;/SAP:AdditionalText&amp;gt; &lt;/P&gt;&lt;P&gt;  &amp;lt;SAP:ApplicationFaultMessage namespace="" /&amp;gt; &lt;/P&gt;&lt;P&gt;  &amp;lt;SAP:Stack /&amp;gt; &lt;/P&gt;&lt;P&gt;  &amp;lt;SAP:Retry&amp;gt;M&amp;lt;/SAP:Retry&amp;gt; &lt;/P&gt;&lt;P&gt;&amp;lt;/SAP:Error&amp;gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;2nd case&lt;/STRONG&gt;: What if the web service URL is not reachable. How do we achieve the time-out requirement at SAP CRM.&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Resolution&lt;/STRONG&gt;: If the web-service is not accessible, SAP PI immediately generates the standard exception message to SAP CRM.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;U&gt;&lt;EM&gt;SAP PI Standard Exception Message&lt;/EM&gt;&lt;/U&gt;&lt;/P&gt;&lt;P&gt;&amp;lt;SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1"&amp;gt;&lt;/P&gt;&lt;P&gt;  &amp;lt;SAP:Category&amp;gt;XIAdapterFramework&amp;lt;/SAP:Category&amp;gt; &lt;/P&gt;&lt;P&gt;  &amp;lt;SAP:Code area="MESSAGE"&amp;gt;GENERAL&amp;lt;/SAP:Code&amp;gt; &lt;/P&gt;&lt;P&gt;  &amp;lt;SAP:P1 /&amp;gt; &lt;/P&gt;&lt;P&gt;  &amp;lt;SAP:P2 /&amp;gt; &lt;/P&gt;&lt;P&gt;  &amp;lt;SAP:P3 /&amp;gt; &lt;/P&gt;&lt;P&gt;  &amp;lt;SAP:P4 /&amp;gt; &lt;/P&gt;&lt;P&gt;  &amp;lt;SAP:AdditionalText&amp;gt;com.sap.aii.af.ra.ms.api.DeliveryException: &lt;EM&gt;Message&lt;/EM&gt; &amp;lt;/SAP:AdditionalText&amp;gt; &lt;/P&gt;&lt;P&gt;  &amp;lt;SAP:ApplicationFaultMessage namespace="" /&amp;gt; &lt;/P&gt;&lt;P&gt;  &amp;lt;SAP:Stack /&amp;gt; &lt;/P&gt;&lt;P&gt;  &amp;lt;SAP:Retry&amp;gt;M&amp;lt;/SAP:Retry&amp;gt; &lt;/P&gt;&lt;P&gt;&amp;lt;/SAP:Error&amp;gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks for helping me. Rewarded points as well &lt;SPAN __jive_emoticon_name="happy"&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Prajeet&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 18 Oct 2011 16:08:25 GMT</pubDate>
      <guid>https://community.sap.com/t5/technology-q-a/soap-timeout-requirement-using-sap-pi/qaa-p/7941855#M2838123</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2011-10-18T16:08:25Z</dc:date>
    </item>
    <item>
      <title>Re: SOAP Timeout requirement using SAP PI</title>
      <link>https://community.sap.com/t5/technology-q-a/soap-timeout-requirement-using-sap-pi/qaa-p/7941856#M2838124</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Prajeet,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I am facing same problem.&lt;/P&gt;&lt;P&gt;I am able to retrieve node &lt;SPAN style="color: #333333; font-size: 12px;"&gt;&amp;lt;SAP:Code area="MESSAGE"&amp;gt;GENERAL&amp;lt;/SAP:Code&amp;gt;&lt;/SPAN&gt; from class &lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; cx_ai_system_fault &lt;/P&gt;&lt;TABLE width="550px"&gt;&lt;/TABLE&gt;&lt;P&gt;But how to retrieve node &lt;SPAN style="color: #333333; font-size: 12px;"&gt;&amp;lt;SAP:AdditionalText&amp;gt;com.sap.aii.af.ra.ms.api.DeliveryException: Read timed out&amp;lt;/SAP:AdditionalText&amp;gt;&lt;/SPAN&gt; so that based on error we can resend the data.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 12 Dec 2013 09:56:26 GMT</pubDate>
      <guid>https://community.sap.com/t5/technology-q-a/soap-timeout-requirement-using-sap-pi/qaa-p/7941856#M2838124</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2013-12-12T09:56:26Z</dc:date>
    </item>
  </channel>
</rss>

