cancel
Showing results for 
Search instead for 
Did you mean: 

Getting error in ECC in proxy scenario

Former Member
0 Kudos

Hi,

We are getting error in SAP ECC system while executing ABAP proxy.Error is :

<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>

- <!--

 Call Integration Server 

-->

- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">

    <SAP:Category>XIProtocol</SAP:Category>
<SAP:Code area="PARSER">ITEM_MISSING</SAP:Code>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>XML element {http://schemas.xmlsoap.org/soap/envelope/}Header missing in SOAP message header (SAP XI Extension)</SAP:Stack>
<SAP:Retry>N</SAP:Retry>
</SAP:Error>
    We are on PI 7.31 and using sender soap adapter over XI 3.0 protocol.This particular scenario is synchronous scenario-Proxy (Soap)->PI->Soap
I    It is working fine in case of async scenario but while execution for sync scenario it is failing in ECC itself.We have applied notes as per Soap req over XI protocols as per doc.
      Please let me know what i am missing.


Accepted Solutions (0)

Answers (1)

Answers (1)

nabendu_sen
Active Contributor
0 Kudos

Hi Rohit,

It seems the Response coming back from Third party does not have proper notations/structure. I think you have checked 'Do not use SOAP Envelop'. Can you please check with SOAP UI whether you are still getting this error?

Former Member
0 Kudos

Hi Nabendu,

In sender soap adapter there is no option of 'Do not use enevlope' while in rec soap adapter i tried both options. checking and unchecking 'Do not use soap envelope'.

Other thing to note is tht it is working in old classical approach where message flows via Integration engine using XI adapter.There i can see message in PI but in case of java only (ICO based) it is failing in ECC itself.

Thanks,

Rohit

nabendu_sen
Active Contributor
0 Kudos

Hi Rohit,

What I have understood that the same Response coming back of Third party is working fine with XI Adapter (XI 3.0) of Classical Configuration but failing for SOAP Adapter (XI 3.0) of ICO. Please confirm.

Former Member
0 Kudos

Yes Nabendu..

nabendu_sen
Active Contributor
0 Kudos

Hi Rohit,

Please check whether the following Path Prefix is maintained in the Sender System's RFC destination: /XISOAPAdapter/MessageServlet?ximessage=true .

Former Member
0 Kudos

Yes this is maintained Nabendu..