How to map system error message response from webservice

[Former Member]

Hello All,

We are having a typical synchronous proxy to soap scenario via PI.

In the case of faulty request , the response message which webservice sends contains only system error message like below:

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

- <!-- Inbound Message

-->

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

<faultcode>SOAP:Server</faultcode>

<faultstring>The system could not log you on. Make sure your User name and server are correct, then type your password again. Letters in passwords must be typed using the correct case. Make sure that Caps Lock is not accidentally on.</faultstring>

<faultactor>RPCRouterServletSession</faultactor>

</SOAP:Fault>

It is not sending the application error message.

Is there any possible way to map this system error message in PI and send the same back to R/3 system.

Regards

Naveen Tripathi

[Former Member]

Hi Naveen,

As your SOAP fault message does not contain <details> node , this is system error message.

About sending it back to ECC, I believe you have to add fault message interface in both(outbound and inbound sync) interfaces.

And you need to define SOAP fault message mapping for both interface mapping(Request and response).

I am not sure how this can be handled in Proxy side.

---Divyesh Vasani

[markangelo_dihiansan]

Hello,

In your SOAP Receiver adapter, add the following module configuration

ModuleKey              ParameterName                 ParameterValue
soap              XMBWS.NoSOAPIgnoreStatusCode          true

Doing so, it will make the

<?xml version="1.0" encoding="UTF-8" standalone="yes" ?> 
- <!-- Inbound Message 
--> 
- <SOAP:Fault xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
<faultcode>SOAP:Server</faultcode> 
<faultstring>The system could not log you on. Make sure your User name and server are correct, then type your password again. Letters in passwords must be typed using the correct case. Make sure that Caps Lock is not accidentally on.</faultstring> 
<faultactor>RPCRouterServletSession</faultactor> 
</SOAP:Fault>

as part of your inbound payload which you can parse via xslt or java mapping.

PS: I think using FaultMessageTypes are for application errors only.

Hope this helps,

Mark

Edited by: Mark Dihiansan on Aug 9, 2011 8:17 AM

[Former Member]

Hello Mark,

Thanks for your reply,i have changed the setings in my receiver channel as suggested but it does not seem to make any change and i am still getting the same response.

Do i need to do any other changes in settings.

Regards

Naveen

[markangelo_dihiansan]

Hello,

The error xml should now be a part of the inbound payload. You still need to parse via xslt or java mapping to make it readable by the proxy.

Hope this helps,

Mark