cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 

payload missing in Soap document

Former Member

on ‎07-12-2010 5:28 PM

0 Kudos

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>

Show replies
Show replies
Answer

Accepted Solutions (0)

Answers (2)

Answers (2)

Former Member
‎07-13-2010 10:20 AM
0 Kudos

Check the soap action you have specified in the receiver soap communication channel.

If the SOAP action in the receiver SOAP channel is wrong then the responce coming back is not match to the responce message definition and you may get this error.

Show replies
Show replies
VijayKonam
Active Contributor
‎07-12-2010 7:33 PM
0 Kudos

That is not because of what you think. Ask you WS providing team to debug their code for proper object associations. In PI RWB, you would not see the payload along with the main document. If you are finding the payload in SXMB_MONI, it is good.

VJ

Show replies
Show replies
Former Member
‎07-12-2010 8:36 PM
0 Kudos

@ VJ,

In PI RWB, you would not see the payload along with the main document. If you are finding the payload in SXMB_MONI, it is good.

Are you sure about this? I don't think this is correct.

-- Abhi

stefan_grube
Active Contributor
‎07-13-2010 7:41 AM
0 Kudos

> Are you sure about this? I don't think this is correct.

VijayaShankar is right. The XI message does not hold the payload in the body.

The SOAP adapter converts the XI message into a real SOAP message, which you cannot see inside PI.

Ask a Question