SOAP to Proxy Scenario -> Payload not generating and msg failing in SXMB_MONI

[Former Member]

Hello experts,

We have created a SOAP to proxy scenario.

Done with IR development as well as ID development.

tested our mapping via mapping tool.. tested the ID configuration via test tool in ID all sucessful.

tested the message from RWB integration engine... every thing is smooth message is received in ECC system.

When i generated the WSDL file and tested the message from SOAP UI i am facing the below error in SAP PI.

The payload node is not generating in SXMB_MONI thus message is failing with below error.

<SAP:Category>Application</SAP:Category>

  <SAP:Code area="MAPPING">EXCEPTION_DURING_EXECUTE</SAP:Code>

  <SAP:P1>com/sap/xi/tf/_MM_Available_Budget_</SAP:P1>

  <SAP:P2>com.sap.aii.utilxi.misc.api.BaseRuntimeException</SAP:P2>

  <SAP:P3>Parsing an empty source. Root element expected!</SAP:P3>

  <SAP:P4 />

  <SAP:AdditionalText />

  <SAP:ApplicationFaultMessage namespace="" />

  <SAP:Stack>com.sap.aii.utilxi.misc.api.BaseRuntimeException thrown during application mapping com/sap/xi/tf/_MM_Available_Budget_: Parsing an empty source. Root element expected!</SAP:Stack>

PS. we are on SAP PI 7.0

Any help and inputs will be appreciated.

Regards,

Ankit

[iaki_vila · Accepted solution]

Hi Ankit,

Compare the XML generated in the monitoring between the two cases. The problem could be in the namespace that it can be different. If you use SOAPui, compare the XML request with you message mapping source XML.

Regards.

[Former Member · Accepted solution]

Hi Inaki,

I could have done that.. but the main issue i am facing is the payload node is not generating in inbound message.

Regards,

[vishnu_pallamreddy · Accepted solution]

Hi Ankit,

Please take WSDL(or File) link from Sender Agreement then try.

[former_member186851 · Accepted solution]

Hello Ankit,

When the message is successful from RWB it should be fine from SOAP Ui.

can you ensure ur WSDL and structure are fine and can you try following the steps I mentioned.

[Former Member · Accepted solution]

Hi Vishnu,

We are on SAP PI 7.0 and it doesn't support direct WSDL extraction from sender agreement .

So we have created the WSDL File from create webservice tool.

Regards,

[iaki_vila · Accepted solution]

Hi Ankit,

Take it easy . Please share the XML request generated in SOAPui request and the XML that you use in the mapping test and we can help you better. A thousand of eyes are better than two.

Regards.

[Former Member · Accepted solution]

Hi Inaki,

Completely agree with you

**********This is used while testing from RWB and the message was successful************

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

<ns0:MT_Available_Budget_OB xmlns:ns0="usr:http://**************/ERMS/PM/RetriveAvailableBudget">

   <ReqHeader>

      <RequestId>1</RequestId>

      <ReqTransactionId>2</ReqTransactionId>

      <ProviderId>3</ProviderId>

      <ConsumerId>4</ConsumerId>

      <ReqTimestamp>5</ReqTimestamp>

   </ReqHeader>

   <ReqData>

      <CostFundCenter>

         <FundCenter>11</FundCenter>

         <CommitmentItem>22</CommitmentItem>

         <FMArea>33</FMArea>

         <FiscalYear>44</FiscalYear>

         <Period>55</Period>

      </CostFundCenter>

      <CostFundCenter>

         <FundCenter>11</FundCenter>

         <CommitmentItem>22</CommitmentItem>

         <FMArea>33</FMArea>

         <FiscalYear>44</FiscalYear>

         <Period>55</Period>

      </CostFundCenter>

      <Order>

         <OrderId>111</OrderId>

         <FundCenter>222</FundCenter>

         <CommitmentItem>333</CommitmentItem>

         <FMArea>444</FMArea>

         <FiscalYear>555</FiscalYear>

         <Period>666</Period>

      </Order>

      <Project>

         <ProjectId>1111</ProjectId>

         <FinancialYear>2222</FinancialYear>

      </Project>

      <Project>

         <ProjectId>1111</ProjectId>

         <FinancialYear>2222</FinancialYear>

      </Project>

   </ReqData>

</ns0:MT_Available_Budget_OB>

********************************************END*************************************************8

*********************Automatic request generated in SOAP UI *********************************

************No payload is received in PI and thus message failing ***********************

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:ret="usr:http://**************/ERMS/PM/RetriveAvailableBudget">

   <soapenv:Header/>

   <soapenv:Body>

      <ret:MT_Available_Budget_OB>

         <!--Optional:-->

         <ReqHeader>

            <!--Optional:-->

            <RequestId>?</RequestId>

            <!--Optional:-->

            <ReqTransactionId>?</ReqTransactionId>

            <!--Optional:-->

            <ProviderId>?</ProviderId>

            <!--Optional:-->

            <ConsumerId>?</ConsumerId>

            <!--Optional:-->

            <ReqTimestamp>?</ReqTimestamp>

         </ReqHeader>

         <!--Optional:-->

         <ReqData>

            <!--Zero or more repetitions:-->

            <CostFundCenter>

               <!--Optional:-->

               <FundCenter>?</FundCenter>

               <!--Optional:-->

               <CommitmentItem>?</CommitmentItem>

               <!--Optional:-->

               <FMArea>?</FMArea>

               <!--Optional:-->

               <FiscalYear>?</FiscalYear>

               <!--Optional:-->

               <Period>?</Period>

            </CostFundCenter>

            <!--Zero or more repetitions:-->

            <Order>

               <!--Optional:-->

               <OrderId>?</OrderId>

               <!--Optional:-->

               <FundCenter>?</FundCenter>

               <!--Optional:-->

               <CommitmentItem>?</CommitmentItem>

               <!--Optional:-->

               <FMArea>?</FMArea>

               <!--Optional:-->

               <FiscalYear>?</FiscalYear>

               <!--Optional:-->

               <Period>?</Period>

            </Order>

            <!--Zero or more repetitions:-->

            <Project>

               <!--Optional:-->

               <ProjectId>?</ProjectId>

               <!--Optional:-->

               <FinancialYear>?</FinancialYear>

            </Project>

         </ReqData>

      </ret:MT_Available_Budget_OB>

   </soapenv:Body>

</soapenv:Envelope>

[Former Member · Accepted solution]

can u check? i have attached both the structures..

[former_member186851 · Accepted solution]

Hello Ankit,

why the field values are empty in soap request used in SOAP UI.

have you posted the Raw XML.?

[Former Member · Accepted solution]

This is just for testing purpose.. at least blank tags should come in SAP PI. but i am receiving this message as below. no payload!!

[former_member186851 · Accepted solution]

Hello Ankit,

Expand inbound message soap body you should see the message payload.

can you once run with actual data and see if the mapping is successful.

[former_member182412 · Accepted solution]

Hi Ankit,

I think you accidentally select the checkbox Use No SOAP Envelope in sender soap channel.

Regards,

Praveen.

[former_member182412 · Accepted solution]

Hi Raghu,

Under the soap body contains Manifest not the payload, payload contain under Payloads node not soap body.

Regards,

Praveen.

[Former Member · Accepted solution]

Hello Praveen,

Thanks you very much for ur pointer..    it was indeed due to mistaken check for SOAP Envelope.

Now the payload is generated,,, and the message is successful..

[former_member182412 · Accepted solution]

Thats Great Ankit

[former_member186851 · Accepted solution]

Rocking Ankit..

[former_member186851]

Hello Ankit,

Generate the structure in SOAP UI using WSDL of service interface or endpoint from service agreement .Then you should not get this error.This seems like some field is missed out.

[Former Member]

Hi Raghuraman,

Thats the same thing i have done.. generated the WSDL from create service tool.

Regards,

[former_member186851]

Hello Ankit,

Can you compare the XMLs used then,There should some mismatch.

Or just copy the successful message from message monitoring and paste the same.