MAPPING">EXCEPTION_DURING_EXECUTE

[Former Member]

Hello Experts ,

We have RFC<--> PI<--->  SOAP scenario . We are getting the error

EXCEPTION_DURING_EXECUTE . The detailed error message in SXMB_MONI is as below :

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

- <!--  Request Message Mapping

  -->

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

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

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

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

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

  <SAP:P3>Fatal Error: com.sap.engine.lib.xml.parser.ParserE</SAP:P3>

  <SAP:P4>xception: XMLParser: Attribute prefix 'soapenv' i~</SAP:P4>

  <SAP:AdditionalText />

  <SAP:Stack>Runtime exception occurred during application mapping com/sap/xi/tf/_MM_MTRX_RESPONSE_; com.sap.aii.utilxi.misc.api.BaseRuntimeException:Fatal Error: com.sap.engine.lib.xml.parser.ParserException: XMLParser: Attribute prefix &#39;soapenv&#39; i~</SAP:Stack>

  <SAP:Retry>N</SAP:Retry>

  </SAP:Error>

This interface is working fine in production but faliling in Q system . We are implementing support packs in our R/3 system . Not sure is it due

to support packs or something else is causing this issue .

Please let me know if you have any inputs to this error .

[baskar_gopalakrishnan2 · Accepted solution]

Looks like some invalid syntax error in message or data values causing this.  Please check whether any thing difference in terms of data values between Q system and prod.

[Former Member · Accepted solution]

Hi Bhaskar,

I observed that some xml definition is missing in R3Q as compared to PRD . Below is the response message I am able to see in SXMB_MONI .

*****

xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">

*****

The above lines are missing in Q system . This is happening after support pack upgrade in R/3 .

PI Q is not upgraded .

Response in Production  :

- <ns1:updateResponse xmlns:ns1="http://hemxwebui5-d:8580/ematrix/services/MatrixAxisUpdJCO" soapenv:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">

<updateReturn
xsi:type="xsd:string">hasError|false|message|</updateReturn>

  </ns1:updateResponse>

Response in Q system :

  <ns1:updateResponse
xmlns:ns1='http://hemxwebui5-d:8580/ematrix/services/MatrixAxisUpdJCO'
soapenv:encodingStyle='http://schemas.xmlsoap.org/soap/encoding/'><updateReturn
xsi:type='xsd:string'>hasError|false|message|</updateReturn></ns

1:updateResponse>

Please let me know if you have any inputs for this error .

Thanks,

Kiran.

[former_member193386]

Hi

Can you try to turn on the option for do not use a SOAP Envelop, or create a javamaping to remove the soap envelop before the mapping to transform the message

[iaki_vila]

Hi Kiran,

A first view, i notice that you probabbly don't need the SOAP namepaces, it seems that the XMLParser is throwing an exception " XMLParser: Attribute prefix &#39;soapenv&#39; " ought to these namespaces. May be, you could try  to use the XMLAnonymizerBean to leave only the ns1 namespace in the SOAP receiver adapter. Check this Nageshwar Reddy's blog:
http://scn.sap.com/community/pi-and-soa-middleware/blog/2012/07/10/handling-namespaces-in-pi-using-x...

Regards.

[Former Member]

Hi Kiran,

Did you get a response to your issue. I see a similar behavior in my sender SOAP adapter where it is stripping the xml namespace from my xml payload.

I am currently on SAP PI 7.31 service pack 5.

Thanks

Ravijeet

[Former Member]

Hi Ravijeet,

The issue was caused in our system due to the implementation of OSS note 0001740810. This was a part support pack upgrade . SAP has given a solution under the note 1786611.

In my case,our system is of 7.1 SP10 . The solution provided in 1786611 was not available for our system so we raised a OSS message and SAP downgraded the solution to 7.1 SP10 .

After implementing the note 1786611, our issue was resolved . I hope this information would be helpful .

Thanks,

Kiran.

[Former Member]

Hi Kiran,

Take the payload from sxmb_moni and check the mapping in Repository, so that you can find out the mapping error for particular field.

Thanks,

Satish.