Skip to Content

Archived discussions are read-only. Learn more about SAP Q&A

payload missing in Soap document

We use XI 3.0, R3->XI->WebService scenario

From my SoapDocument, i don't see the payload being part of the <Body>.

Hence we get the "Object reference not set to an instance of an object" exception, from the WS

- <SOAP:Envelope xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">

- <SOAP:Header xmlns:xlink="http://www.w3.org/1999/xlink" xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:wsse="http://www.docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd">

+ <SAP:Main versionMajor="3" versionMinor="0" SOAP:mustUnderstand="1" xmlns:wsu="http://www.docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" wsu:Id="wsuid-main-92ABE13F5C59AB7FE10000000A1551F7">

<SAP:MessageClass>ApplicationMessage</SAP:MessageClass>

<SAP:ProcessingMode>synchronous</SAP:ProcessingMode>

<SAP:MessageId>6c6d4f1d-922c-bb4c-a530-565d72af968a</SAP:MessageId>

<SAP:TimeSent>2010-07-09T23:27:07Z</SAP:TimeSent>

- <SAP:Sender>

<SAP:Party agency="" scheme="" />

<SAP:Service>IP_Centura</SAP:Service>

</SAP:Sender>

- <SAP:Receiver>

<SAP:Party agency="" scheme="" />

<SAP:Service>Centura</SAP:Service>

</SAP:Receiver>

<SAP:Interface namespace="http://bancousa.com/sapr3/fi/transdata/Centura">MI_CenturaReq_Inbound</SAP:Interface>

</SAP:Main>

+ <SAP:ReliableMessaging SOAP:mustUnderstand="1">

<SAP:QualityOfService>BestEffort</SAP:QualityOfService>

</SAP:ReliableMessaging>

+ <SAP:Diagnostic SOAP:mustUnderstand="1">

<SAP:TraceLevel>Information</SAP:TraceLevel>

<SAP:Logging>Off</SAP:Logging>

</SAP:Diagnostic>

- <SAP:HopList SOAP:mustUnderstand="1">

- <SAP:Hop timeStamp="2010-07-09T23:27:07Z" wasRead="false">

<SAP:Engine type="PE" />

<SAP:Adapter namespace="http://sap.com/xi/XI/System">PE</SAP:Adapter>

<SAP:MessageId>6c6d4f1d-922c-bb4c-a530-565d72af968a</SAP:MessageId>

<SAP:Info />

</SAP:Hop>

- <SAP:Hop timeStamp="2010-07-09T23:27:08Z" wasRead="false">

<SAP:Engine type="IS">is.01.m2sapxqsc</SAP:Engine>

<SAP:Adapter namespace="http://sap.com/xi/XI/System">XI</SAP:Adapter>

<SAP:MessageId>6c6d4f1d-922c-bb4c-a530-565d72af968a</SAP:MessageId>

<SAP:Info>3.0</SAP:Info>

</SAP:Hop>

- <SAP:Hop timeStamp="2010-07-09T23:27:08Z" wasRead="false">

<SAP:Engine type="AE">af.xqs.m2sapxqsc</SAP:Engine>

<SAP:Adapter namespace="http://sap.com/xi/XI/System">XIRA</SAP:Adapter>

<SAP:MessageId>6c6d4f1d-922c-bb4c-a530-565d72af968a</SAP:MessageId>

</SAP:Hop>

</SAP:HopList>

</SOAP:Header>

- <SOAP:Body>

<sap:Manifest xmlns:sap="http://sap.com/xi/XI/Message/30" xmlns:xlink="http://www.w3.org/1999/xlink" xmlns:wsu="http://www.docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" wsu:Id="wsuid-manifest-5CABE13F5C59AB7FE10000000A1551F7" />

</SOAP:Body>

</SOAP:Envelope>

Former Member
Not what you were looking for? View more on this topic or Ask a question