cancel
Showing results for 
Search instead for 
Did you mean: 

Unable to convert sender XI party

Former Member
0 Kudos

Hi All,
       We recently upgraded the PI systems to version 7.3
    For a particular interface, PI system receives IDOCs from two different SAP systems. Everything works fine except this strange issue.
    I'm aware the PI generates ALEAUD01 idoc and sends back to SAP system for each idoc it receives from SAP.
    After the upgrade, I see this issue that from one SAP system PI receives IDOc but while sending back the ALEAUD01 IDOc back to that SAP system I see below error. With the another SAP system for the same interface I'm NOT seeing this error even after the upgrade. It works fine the ALEAUD01 IDoc is going back to that SAP system.
           
  - <!--  Call Adapter   -->
- <SAP:Error SOAP:mustUnderstand="" xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
  <SAP:Category>XIAdapter</SAP:Category>
  <SAP:Code area="IDOC_ADAPTER">ATTRIBUTE_INV_SND_PARTY</SAP:Code>
  <SAP:P1>http://sap.com/xi/XI</SAP:P1>
  <SAP:P2>XIParty</SAP:P2>
  <SAP:P3>XXXXX</SAP:P3>
  <SAP:P4 />
  <SAP:AdditionalText />
  <SAP:Stack>Unable to convert sender XI party http://sap.com/xi/XI/XIParty/XXXXX to an IDoc partner</SAP:Stack>
  <SAP:Retry>M</SAP:Retry>
  </SAP:Error>
 
 
  When searched for the error log below is what I see..
 
################################################################################################
  Trace level="1" type="T">---------------------------------------------</Trace>
  <Trace level="1" type="T">---- Outbound IDoc-Adapter ----</Trace>
  <Trace level="1" type="T">---------------------------------------------</Trace>
- <Trace level="1" type="B" name="CL_IDX_IDOC_SERVICE-ENTER_PLSRV">
  <Trace level="1" type="T">Pipeline Service ID: PLSRV_CALL_ADAPTER</Trace>
  <Trace level="1" type="T">Get Information from IS-Header Objekt</Trace>
  <Trace level="1" type="T">Get Information from SD-IDoc-Endpoint</Trace>
  <Trace level="2" type="T">---------------------------------------------</Trace>
  <Trace level="2" type="T">IDoc-Endpoint Channel :</Trace>
  <Trace level="2" type="T">RFCDEST : XXXX</Trace>
  <Trace level="2" type="T">Port : XXXXX</Trace>
  <Trace level="2" type="T">Docrel :</Trace>
  <Trace level="2" type="T">Version : 3</Trace>
  <Trace level="2" type="T">Saprel : 450</Trace>
  <Trace level="2" type="T">Queue-ID:</Trace>
  <Trace level="2" type="T">---------------------------------------------</Trace>
  <Trace level="1" type="T">Sender and Receiver after Header-Mapping</Trace>
  <Trace level="1" type="T">Sender service BS_XXX</Trace>
  <Trace level="1" type="T">Receiver service XXXXX</Trace>
  <Trace level="1" type="T">Sender party XXXXX</Trace>
  <Trace level="1" type="T">Sender agency http://sap.com/xi/XI</Trace>
  <Trace level="1" type="T">Sender scheme XIParty</Trace>
  </Trace>
  </Trace>
  <Trace level="3" type="System_Error">Error exception return from pipeline processing!</Trace>
  <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
- <!--  ************************************
  -->
  <Trace level="3" type="T">Persisting message Status = 014</Trace>
  <Trace level="3" type="T">Message version 004</Trace>
  <Trace level="3" type="T">Pipeline CENTRAL_BACK</Trace>
  </SAP:Trace>
################################################################################################
 
But before the upgrade for the same SAP system(which is giving error now) I see log as below and it was working. There was no issue in sending back the ALEAUD01 to the SAP system.


  <Trace level="1" type="T">---- Outbound IDoc-Adapter ----</Trace>
  <Trace level="1" type="T">---------------------------------------------</Trace>
- <Trace level="1" type="B" name="CL_IDX_IDOC_SERVICE-ENTER_PLSRV">
  <Trace level="1" type="T">Pipeline Service ID: PLSRV_CALL_ADAPTER</Trace>
  <Trace level="1" type="T">Get Information from IS-Header Objekt</Trace>
  <Trace level="1" type="T">Get Information from SD-IDoc-Endpoint</Trace>
  <Trace level="2" type="T">---------------------------------------------</Trace>
  <Trace level="2" type="T">IDoc-Endpoint Channel :</Trace>
  <Trace level="2" type="T">RFCDEST : XXXX</Trace>
  <Trace level="2" type="T">Port : XXXXX</Trace>
  <Trace level="2" type="T">Docrel :</Trace>
  <Trace level="2" type="T">Version : 3</Trace>
  <Trace level="2" type="T">Saprel : 450</Trace>
  <Trace level="2" type="T">Queue-ID:</Trace>
  <Trace level="2" type="T">---------------------------------------------</Trace>
  <Trace level="1" type="T">Sender and Receiver after Header-Mapping</Trace>
  <Trace level="1" type="T">Sender service BS_XXX</Trace>
  <Trace level="1" type="T">Receiver service XXXXX</Trace>
  <Trace level="1" type="T">Get IDoc-XML from the Resource Objekt</Trace>
  <Trace level="1" type="T">Call Outbound IDoc-Adapter</Trace>
  <Trace level="1" type="T">Call Outbound IDoc-Adapter</Trace>
- <Trace level="1" type="B" name="IDX_OUTBOUND_XMB">
  <Trace level="1" type="T">FM IDOC_INBOUND_ASYNCHRONOUS with RFCDEST= XXXXX</Trace>
  <Trace level="2" type="T">Used TID = 9974E14F008A4F3CE1D96364</Trace>
  </Trace>
  <Trace level="2" type="T">TID : 9974E14F008A4F3CE1D96364</Trace>
  </Trace>
  </Trace>
  </Trace>
 

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

Please have a look on the below file which guides you to deal with the IDOC Acknowledgments -

http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/903a0abc-e56e-2910-51a8-9dc616df56eb&override...

Former Member
0 Kudos

Hi Jyoti, Thanks for your reply. I'm already aware of suppressing ALEAUD01 idoc type.  In this case, as I mentioned it was working earlier. Now the question is why it is giving this error.  So without finding a answer for this I finally decided not to send ALEAUD01 idoc back to that particular SAP system.

Answers (0)