cancel
Showing results for 
Search instead for 
Did you mean: 

SAP PI 7.4 - Fault Message

0 Kudos

Hi guys,

i have a problem with Fault Message Type in following synchronous scenario:

Request: SAP Proxy -> PI 7.4 -> SOAP

Response: SOAP -> PI 7.4 -> SAP Proxy

My Operation Mapping has filled request, response and error tab. Request and response has a added a xslt mapping after message mapping respectively in case of response before message map step. My SOAP Adapter has parameter "use no soap envelope" and "keep header" activated. In soap modul, parameter "XMBWS.NoSOAPIgnoreStatusCode" set to "true".

In case of error i receive Fault Message in message monitoring like:

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

<soapenv:Envelope 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">

<soapenv:Body>

  <soapenv:Fault>

   <faultcode xmlns:ns1="http://xml.apache.org/axis/">ns1:Server</faultcode>

   <faultstring>unknown data</faultstring>

   <faultactor>http://xxx.com</faultactor>

   <detail>

    <FaultDetail>

     <ErrorCode>37</ErrorCode>

     <Severity>Error</Severity>

     <DetailedMessage>incorrect data</DetailedMessage>

    </FaultDetail>

   </detail>

  </soapenv:Fault>

</soapenv:Body>

</soapenv:Envelope>

Proxy is not capturing the error although try catch is correct.

Any ideas whats wrong?

Accepted Solutions (0)

Answers (3)

Answers (3)

0 Kudos

Monitoring looks also strange:

former_member186851
Active Contributor
0 Kudos

Marcus,

Did you try testing the webservice using SOAP UI.

I guess the webservice is returning fault in such a way.

0 Kudos

Yes i have tested and i get soapenv:fault message back.

iaki_vila
Active Contributor
0 Kudos

Hi Marcus,

I don't see nothing weird in your last screen-shots, you only need to prepare your mapping to deal with the fault tags.

Regards.

0 Kudos

Hi Inaki,

yes i can map also fault message in Response but i thought fault will be mapped in error part of Operation Mapping.

Regards,

Marcus

former_member186851
Active Contributor
0 Kudos

Hello Marcus,

You need to map the fault message

0 Kudos

Hi Raghuraman,

you mean i have to map fault message in Response part and than message comes to error part in operation mapping so proxy will catch?

Regards,

Marcus

iaki_vila
Active Contributor
0 Kudos

Hi Marcus,

I'd rather using fault messages as part of the payload, however may be you can catch them (i didn't try it), check Stefan Grube's answer in this blog

Regards,

former_member186851
Active Contributor
0 Kudos

Marcus,

Refer the below link

http://scn.sap.com/thread/1418627

iaki_vila
Active Contributor
0 Kudos

Hi Marcus,

That parameter and the checkbox Do Not Use SOAP Envelope is needed to avoid the SOAP adapter throws an exception. AFAIK the sender ABAP proxy won't catch the fault messages. I usually change the sender schema with Error tags and i map the fault messages if those happen.

Regards

former_member186851
Active Contributor
0 Kudos

Hello Marcus,

So the fault message is reaching PI but not properly updating in ECC?

your proxy codes are active ?

0 Kudos

Hi Raghuraman,

all Proxy codes are active. Does i have to take care something in repsonse handling in operation mapping so fault message will take effect?

Regards,

Marcus