<?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: SRM-PI-ECC Integration issue in Technology Q&amp;A</title>
    <link>https://community.sap.com/t5/technology-q-a/srm-pi-ecc-integration-issue/qaa-p/7674888#M2750328</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Aashish,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;After implemnenting above notes is it mandatory to use the AAE features or can I continue using the classic configuration in PI?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Does AAE setting suggest any modification at Application level (SRM or ECC) apart from PI ?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Please suggest.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;Venu.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 09 Mar 2011 23:20:28 GMT</pubDate>
    <dc:creator>Former Member</dc:creator>
    <dc:date>2011-03-09T23:20:28Z</dc:date>
    <item>
      <title>SRM-PI-ECC Integration issue</title>
      <link>https://community.sap.com/t5/technology-q-a/srm-pi-ecc-integration-issue/qaq-p/7674868</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hey All&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;There is some issue coming in Central Contact management scenario.&lt;/P&gt;&lt;P&gt;SRM 7.0&lt;/P&gt;&lt;P&gt;ECC 6.0 EHP 4&lt;/P&gt;&lt;P&gt;PI&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;*below is the error details we get in SXMB_MONI of SRM Sytem*  &lt;SPAN __default_attr="red" __jive_macro_name="color"&gt;&amp;lt;REMOVED BY MODERATOR&amp;gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;  &amp;lt;?xml version="1.0" encoding="UTF-8" standalone="yes" ?&amp;gt; &lt;/P&gt;&lt;P&gt;- &amp;lt;!--  Call Integration Server &lt;/P&gt;&lt;P&gt;  --&amp;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=""&amp;gt;&lt;/P&gt;&lt;P&gt;  &amp;lt;SAP:Category&amp;gt;XIProtocol&amp;lt;/SAP:Category&amp;gt; &lt;/P&gt;&lt;P&gt;  &amp;lt;SAP:Code area="PARSER"&amp;gt;ITEM_UNEXPECTED&amp;lt;/SAP:Code&amp;gt; &lt;/P&gt;&lt;P&gt;  &amp;lt;SAP:P1&amp;gt;&amp;lt;&amp;gt;&amp;lt;/SAP:P1&amp;gt; &lt;/P&gt;&lt;P&gt;  &amp;lt;SAP:P2&amp;gt;&amp;lt;&lt;SPAN __jive_macro_name="http"&gt;&lt;/SPAN&gt;Fault&amp;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;ST: ST_XMS_MSGHDR30_SOAP_FAULT&amp;lt;/SAP:P4&amp;gt; &lt;/P&gt;&lt;P&gt;  &amp;lt;SAP:AdditionalText&amp;gt;System expected the element '&lt;SPAN __jive_macro_name="http"&gt;&lt;/SPAN&gt;Fault'&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;Unexpected XML element &amp;lt;&amp;gt;; &amp;lt;&lt;SPAN __jive_macro_name="http"&gt;&lt;/SPAN&gt;Fault&amp;gt; was expected System expected the element '&lt;SPAN __jive_macro_name="http"&gt;&lt;/SPAN&gt;Fault'&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 &lt;/P&gt;&lt;P&gt;Narender&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Edited by: Prateek Raj Srivastava on Mar 5, 2011 4:49 PM&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 04 Mar 2011 03:03:26 GMT</pubDate>
      <guid>https://community.sap.com/t5/technology-q-a/srm-pi-ecc-integration-issue/qaq-p/7674868</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2011-03-04T03:03:26Z</dc:date>
    </item>
    <item>
      <title>Re: SRM-PI-ECC Integration issue</title>
      <link>https://community.sap.com/t5/technology-q-a/srm-pi-ecc-integration-issue/qaa-p/7674869#M2750309</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;At what level interface failed in MONI(check pipe line steps),i think SRP data not matiching with your structure what you have defined.might be XSD wrong.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Raj&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 04 Mar 2011 04:00:45 GMT</pubDate>
      <guid>https://community.sap.com/t5/technology-q-a/srm-pi-ecc-integration-issue/qaa-p/7674869#M2750309</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2011-03-04T04:00:45Z</dc:date>
    </item>
    <item>
      <title>Re: SRM-PI-ECC Integration issue</title>
      <link>https://community.sap.com/t5/technology-q-a/srm-pi-ecc-integration-issue/qaa-p/7674870#M2750310</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hey Raja&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;It is pre-configured scenario..every thing is standard including Function Module also ...&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Problem is whe we check the SXMB_mONI message ststus ..the below mention message we are getting...&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;sender Adapter is XI Adapter (Proxy).  Message are Getting failed in SRM Box only .....&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks &lt;/P&gt;&lt;P&gt;Abhishek Agrahari&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 04 Mar 2011 04:35:03 GMT</pubDate>
      <guid>https://community.sap.com/t5/technology-q-a/srm-pi-ecc-integration-issue/qaa-p/7674870#M2750310</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2011-03-04T04:35:03Z</dc:date>
    </item>
    <item>
      <title>Re: SRM-PI-ECC Integration issue</title>
      <link>https://community.sap.com/t5/technology-q-a/srm-pi-ecc-integration-issue/qaa-p/7674871#M2750311</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;you're probably missing the fault message type in your service interface definition. go to the esr to the SI definition and add a fault message and try again&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 04 Mar 2011 11:05:20 GMT</pubDate>
      <guid>https://community.sap.com/t5/technology-q-a/srm-pi-ecc-integration-issue/qaa-p/7674871#M2750311</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2011-03-04T11:05:20Z</dc:date>
    </item>
    <item>
      <title>Re: SRM-PI-ECC Integration issue</title>
      <link>https://community.sap.com/t5/technology-q-a/srm-pi-ecc-integration-issue/qaa-p/7674872#M2750312</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Narendra,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I Understand that you scenario is SRM(Proxy)--&amp;gt; PI --&amp;gt; ECC 6.0 EHP 4,  if this is the case you actually don't require any XI Sender Adapter when using a  client Proxy. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Nipun&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 04 Mar 2011 11:24:07 GMT</pubDate>
      <guid>https://community.sap.com/t5/technology-q-a/srm-pi-ecc-integration-issue/qaa-p/7674872#M2750312</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2011-03-04T11:24:07Z</dc:date>
    </item>
    <item>
      <title>Re: SRM-PI-ECC Integration issue</title>
      <link>https://community.sap.com/t5/technology-q-a/srm-pi-ecc-integration-issue/qaa-p/7674873#M2750313</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&amp;gt;&amp;gt; sender Adapter is XI Adapter (Proxy). Message are Getting failed in SRM Box only .....&lt;/P&gt;&lt;P&gt;Hope below steps might help...&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;a) Sender side proxy then you dont need cllient proxy adapter.&lt;/P&gt;&lt;P&gt;b) Check proxy configuration between SRM and PI.  (if messges are getting failed in SRM Box only...)&lt;/P&gt;&lt;P&gt;c) Also make sure ID objects are properly configured with sender business system (ABAP type) in Receiver determination, Interface determination, Receiver agreement etc&lt;/P&gt;&lt;P&gt;d) in your case you dont need sender comm channel and sender agreement.&lt;/P&gt;&lt;P&gt;e) Check proxy structure on the client side matches with PI source data structure. If there is mismatch , regenerate outbound proxy side in SRM and do the coding...&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 04 Mar 2011 14:58:04 GMT</pubDate>
      <guid>https://community.sap.com/t5/technology-q-a/srm-pi-ecc-integration-issue/qaa-p/7674873#M2750313</guid>
      <dc:creator>baskar_gopalakrishnan2</dc:creator>
      <dc:date>2011-03-04T14:58:04Z</dc:date>
    </item>
    <item>
      <title>Re: SRM-PI-ECC Integration issue</title>
      <link>https://community.sap.com/t5/technology-q-a/srm-pi-ecc-integration-issue/qaa-p/7674874#M2750314</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;Look out for the log in SLG1 of SRM System. Probably it will give you some idea. Check if some settings are missing in SRM.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Are you using XI proxy in sender side? if yes, no need to use it.. No sender com channel and sender agreement needed. Create an XI Proxy receiver Communication channel for ECC.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I hope you already create the SM59 RFC destination for SRM system in PI and vice versa.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;Aashish Sinha&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 04 Mar 2011 20:13:28 GMT</pubDate>
      <guid>https://community.sap.com/t5/technology-q-a/srm-pi-ecc-integration-issue/qaa-p/7674874#M2750314</guid>
      <dc:creator>aashish_sinha</dc:creator>
      <dc:date>2011-03-04T20:13:28Z</dc:date>
    </item>
    <item>
      <title>Re: SRM-PI-ECC Integration issue</title>
      <link>https://community.sap.com/t5/technology-q-a/srm-pi-ecc-integration-issue/qaa-p/7674875#M2750315</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thanks Aashish .&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I checked SLG1 and error message for my Contract as below&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Recipient not found&lt;/P&gt;&lt;P&gt;Message no. BBP_EXC004&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The error ocurred by processing event RELEASED_NEWLY with GUID E0460004EF852FF182AD005056A12FA9 and object_id= 4400000037&lt;/P&gt;&lt;P&gt;Message no. BBP_EXC000&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;What could be the reason ?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;P&gt;NAP&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sun, 06 Mar 2011 22:56:20 GMT</pubDate>
      <guid>https://community.sap.com/t5/technology-q-a/srm-pi-ecc-integration-issue/qaa-p/7674875#M2750315</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2011-03-06T22:56:20Z</dc:date>
    </item>
    <item>
      <title>Re: SRM-PI-ECC Integration issue</title>
      <link>https://community.sap.com/t5/technology-q-a/srm-pi-ecc-integration-issue/qaa-p/7674876#M2750316</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;I'm working on this scenarion from PI side with Narendra,&lt;/P&gt;&lt;P&gt;we have done all the setting suggested in this thread.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;We are now getting following error,&lt;/P&gt;&lt;P&gt;XML tag Main/@versionMajor has incorrect value 002; expected value is 003.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;Venu and Narendra.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 07 Mar 2011 01:32:47 GMT</pubDate>
      <guid>https://community.sap.com/t5/technology-q-a/srm-pi-ecc-integration-issue/qaa-p/7674876#M2750316</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2011-03-07T01:32:47Z</dc:date>
    </item>
    <item>
      <title>Re: SRM-PI-ECC Integration issue</title>
      <link>https://community.sap.com/t5/technology-q-a/srm-pi-ecc-integration-issue/qaa-p/7674877#M2750317</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Venu &amp;amp; Narendra,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;@ Narendra : You probably be getting this error because of some missing settings in SRM side. Can you please look out or ask your functional consultant.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;@Venu :  Please post the detailed error, that where are you getting this error. if in SRM - SXMB_MONI, please let me know the exact text as well as if you getting it in PI.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;Aashish Sinha&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 07 Mar 2011 04:19:53 GMT</pubDate>
      <guid>https://community.sap.com/t5/technology-q-a/srm-pi-ecc-integration-issue/qaa-p/7674877#M2750317</guid>
      <dc:creator>aashish_sinha</dc:creator>
      <dc:date>2011-03-07T04:19:53Z</dc:date>
    </item>
    <item>
      <title>Re: SRM-PI-ECC Integration issue</title>
      <link>https://community.sap.com/t5/technology-q-a/srm-pi-ecc-integration-issue/qaa-p/7674878#M2750318</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Venu,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;For this error, Regenerate the proxy, the error has occured due to proxy incorrect version (there might have been some modifications in data structure and configuration.)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Cheers,&lt;/P&gt;&lt;P&gt;Nipun&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 07 Mar 2011 06:01:05 GMT</pubDate>
      <guid>https://community.sap.com/t5/technology-q-a/srm-pi-ecc-integration-issue/qaa-p/7674878#M2750318</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2011-03-07T06:01:05Z</dc:date>
    </item>
    <item>
      <title>Re: SRM-PI-ECC Integration issue</title>
      <link>https://community.sap.com/t5/technology-q-a/srm-pi-ecc-integration-issue/qaa-p/7674879#M2750319</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Ashish &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This is Venu ......&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;When the SRM scenario has been triggered, the  message got stuck in SRM queue(SMQ2), after excuting the queue we are gettting following error,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;*XI error ITEM_UNEXPECTED.PARSER: Queue Stopped*&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;*and after thgis when we check the SRM SXMB_MONI ,,,,,,we are getting the following error*&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;lt;?xml version="1.0" encoding="UTF-8" standalone="yes" ?&amp;gt; &lt;/P&gt;&lt;P&gt;- &amp;lt;!--  Call Integration Server &lt;/P&gt;&lt;P&gt;  --&amp;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=""&amp;gt;&lt;/P&gt;&lt;P&gt;  &amp;lt;SAP:Category&amp;gt;XIProtocol&amp;lt;/SAP:Category&amp;gt; &lt;/P&gt;&lt;P&gt;  &amp;lt;SAP:Code area="PARSER"&amp;gt;ITEM_UNEXPECTED&amp;lt;/SAP:Code&amp;gt; &lt;/P&gt;&lt;P&gt;  &amp;lt;SAP:P1&amp;gt;&amp;lt;&amp;gt;&amp;lt;/SAP:P1&amp;gt; &lt;/P&gt;&lt;P&gt;  &amp;lt;SAP:P2&amp;gt;&amp;lt;&lt;SPAN __jive_macro_name="http"&gt;&lt;/SPAN&gt;Fault&amp;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;ST: ST_XMS_MSGHDR30_SOAP_FAULT&amp;lt;/SAP:P4&amp;gt; &lt;/P&gt;&lt;P&gt;  &amp;lt;SAP:AdditionalText&amp;gt;System expected the element '&lt;SPAN __jive_macro_name="http"&gt;&lt;/SPAN&gt;Fault'&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;Unexpected XML element &amp;lt;&amp;gt;; &amp;lt;&lt;SPAN __jive_macro_name="http"&gt;&lt;/SPAN&gt;Fault&amp;gt; was expected System expected the element '&lt;SPAN __jive_macro_name="http"&gt;&lt;/SPAN&gt;Fault'&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 &lt;/P&gt;&lt;P&gt;Venu  &amp;amp;  Abhishek&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 07 Mar 2011 06:44:01 GMT</pubDate>
      <guid>https://community.sap.com/t5/technology-q-a/srm-pi-ecc-integration-issue/qaa-p/7674879#M2750319</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2011-03-07T06:44:01Z</dc:date>
    </item>
    <item>
      <title>Re: SRM-PI-ECC Integration issue</title>
      <link>https://community.sap.com/t5/technology-q-a/srm-pi-ecc-integration-issue/qaa-p/7674880#M2750320</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Aashish ,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;1.CCR Document is okay in SRM and it do not shows any error log in the SRM Application Monitor, in the RZ20 as well as in the  BBP_PD. Even I am craeting Contract independently in ECC woth same data to that of CCR in SRM and it don;t have issue.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;NAP&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 07 Mar 2011 06:50:00 GMT</pubDate>
      <guid>https://community.sap.com/t5/technology-q-a/srm-pi-ecc-integration-issue/qaa-p/7674880#M2750320</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2011-03-07T06:50:00Z</dc:date>
    </item>
    <item>
      <title>Re: SRM-PI-ECC Integration issue</title>
      <link>https://community.sap.com/t5/technology-q-a/srm-pi-ecc-integration-issue/qaa-p/7674881#M2750321</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Venu/Abhishek,&lt;/P&gt;&lt;P&gt;As per the conversations, I beleive the config in ECC and PI is absolutely OK (even if you create a comm channel and agreement for sender, which are not required, that should not have any impact on the error). Since the processing is successful in ECC system, I would recommend doing a simple test in the ID of PI using Test Configuration tool. Use the data which is passed as input. This will second the fact that everything is OK from PI side also.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Then, you can check whether the data sent from SRM is as per expectations. I think the problem might be due to missing mapping or wrong conditions for key fields etc.&lt;/P&gt;&lt;P&gt;Check the link:  &lt;A href="http://forums.sdn.sap.com/click.jspa?searchID=70621600&amp;amp;messageID=4708465" target="test_blank"&gt;http://forums.sdn.sap.com/click.jspa?searchID=70621600&amp;amp;messageID=4708465&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hope this helps.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Souvik&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 07 Mar 2011 11:08:02 GMT</pubDate>
      <guid>https://community.sap.com/t5/technology-q-a/srm-pi-ecc-integration-issue/qaa-p/7674881#M2750321</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2011-03-07T11:08:02Z</dc:date>
    </item>
    <item>
      <title>Re: SRM-PI-ECC Integration issue</title>
      <link>https://community.sap.com/t5/technology-q-a/srm-pi-ecc-integration-issue/qaa-p/7674882#M2750322</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Abhishek/Venu&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This error is coming because SRM Application using ABAP Proxies tries to communicate with AAE using SOAP Adapter with XI Protocol. But this communication results in error. This exception is  thrown by AAE SOAP Adapter used with XI protocol. &lt;/P&gt;&lt;P&gt;The error message could also be similar to the following: XML tag Main/@versionMajor has incorrect value 002; expected value is 003. As you were getting this error message earlier also.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Have a look into below SAP Notes. It will fix your problem.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="https://websmp230.sap-ag.de/sap(bD1lbiZjPTAwMQ==)/bc/bsp/spn/sapnotes/index2.htm?numm=1349125" target="test_blank"&gt;https://websmp230.sap-ag.de/sap(bD1lbiZjPTAwMQ==)/bc/bsp/spn/sapnotes/index2.htm?numm=1349125&lt;/A&gt; (SMP Login required)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;SAP note number : 1349125&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;Aashish Sinha&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 07 Mar 2011 11:44:29 GMT</pubDate>
      <guid>https://community.sap.com/t5/technology-q-a/srm-pi-ecc-integration-issue/qaa-p/7674882#M2750322</guid>
      <dc:creator>aashish_sinha</dc:creator>
      <dc:date>2011-03-07T11:44:29Z</dc:date>
    </item>
    <item>
      <title>Re: SRM-PI-ECC Integration issue</title>
      <link>https://community.sap.com/t5/technology-q-a/srm-pi-ecc-integration-issue/qaa-p/7674883#M2750323</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Narendra,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt; I too agree with Aashish the problem you are facing is of incorrect Transport Protocol, correct the transport ptrocol and regrenerate the proxy, the problem should go this time.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Nipun&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 07 Mar 2011 12:10:30 GMT</pubDate>
      <guid>https://community.sap.com/t5/technology-q-a/srm-pi-ecc-integration-issue/qaa-p/7674883#M2750323</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2011-03-07T12:10:30Z</dc:date>
    </item>
    <item>
      <title>Re: SRM-PI-ECC Integration issue</title>
      <link>https://community.sap.com/t5/technology-q-a/srm-pi-ecc-integration-issue/qaa-p/7674884#M2750324</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;HI Aashish,&lt;/P&gt;&lt;P&gt;Thanks for the useful information, will try applying the note.&lt;/P&gt;&lt;P&gt;Do you recommend using the SOAP sender adapter in this case?&lt;/P&gt;&lt;P&gt;I have tried initially with the SOAP adapter, but since it was not working, I have deleted the sender agreement and from the receiver side I have used the XI receiver adapter.&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;Venu.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 07 Mar 2011 23:01:04 GMT</pubDate>
      <guid>https://community.sap.com/t5/technology-q-a/srm-pi-ecc-integration-issue/qaa-p/7674884#M2750324</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2011-03-07T23:01:04Z</dc:date>
    </item>
    <item>
      <title>Re: SRM-PI-ECC Integration issue</title>
      <link>https://community.sap.com/t5/technology-q-a/srm-pi-ecc-integration-issue/qaa-p/7674885#M2750325</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi venu &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If you have check the SRM generated XML messgages in XI -&amp;gt;ID-&amp;gt;Test scenario...and if that is working fine ....&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;then there is problem with SRM ....which is not able to push the XML data to XI (as is it using push mechanish (not pulled by XI))&lt;/P&gt;&lt;P&gt;using proxy ...&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Check all the settind done by SRM-PI conectivity , seems like a proble there ...&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;try to troubleshoot to release the queue fro SRM&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 08 Mar 2011 00:26:45 GMT</pubDate>
      <guid>https://community.sap.com/t5/technology-q-a/srm-pi-ecc-integration-issue/qaa-p/7674885#M2750325</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2011-03-08T00:26:45Z</dc:date>
    </item>
    <item>
      <title>Re: SRM-PI-ECC Integration issue</title>
      <link>https://community.sap.com/t5/technology-q-a/srm-pi-ecc-integration-issue/qaa-p/7674886#M2750326</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;No, the way you sending data from SRM to SAP PI is looks fine to me, no need to use SOAP Adapter in between. Please apply the note, and i hope it will fix the problem.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;Aashish Sinha&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 08 Mar 2011 04:33:02 GMT</pubDate>
      <guid>https://community.sap.com/t5/technology-q-a/srm-pi-ecc-integration-issue/qaa-p/7674886#M2750326</guid>
      <dc:creator>aashish_sinha</dc:creator>
      <dc:date>2011-03-08T04:33:02Z</dc:date>
    </item>
    <item>
      <title>Re: SRM-PI-ECC Integration issue</title>
      <link>https://community.sap.com/t5/technology-q-a/srm-pi-ecc-integration-issue/qaa-p/7674887#M2750327</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;HI Aashish&lt;/P&gt;&lt;P&gt;The note suggests doing following things,&lt;/P&gt;&lt;P&gt;u2022	Changes in SOAP adapter&lt;/P&gt;&lt;P&gt;u2022	Apply further notes: 1334174, 1332856&lt;/P&gt;&lt;P&gt;u2022	Applying SP patches&lt;/P&gt;&lt;P&gt;I understood from your mail that it will not be required to use the soap adapter.&lt;/P&gt;&lt;P&gt;Could you please suggest just applying notes and apply SP patches are enough from this point of time?&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;Venu.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 08 Mar 2011 06:30:39 GMT</pubDate>
      <guid>https://community.sap.com/t5/technology-q-a/srm-pi-ecc-integration-issue/qaa-p/7674887#M2750327</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2011-03-08T06:30:39Z</dc:date>
    </item>
  </channel>
</rss>

