Synchronous Webservice Exception not being read ABAP Method

[Former Member]

Hi,

We have synchronous PROXY - HTTP scenario. Our response is OK and working fine but we have problem when we want to return error message. Receiver system sends back fault message when there is error. This is then read by sender system. We have 5 different fault types, all these are generated by proxy correctly. However, ABAP method:

IF_MESSAGE~GET_LONGTEXT cannot get error message.

IF_MESSAGE~GET_TEXT can get message but only two words, and it is getting error from the 'ERROR' segment of the SOAP payload rather than the response.

Any thoughts on this?

Regards,

Raye

[iaki_vila · Accepted solution]

Hi Raye,

It is an exception or a fault message?. In SOAP adapter you can control the fault messages with the check Do Not Use SOAP Envelope and the parameter XMBWS.NoSOAPIgnoreStatusCode = true on the module tab. Have you thought to change the HTTP adapter by SOAP adapter?

Regards.

[Former Member · Accepted solution]

Hi Inaki,

Thanks. It is fault message. Receiver sends a fault message which contains the error.

Sorry, we are using SOAP instead of HTTP. Sorry bout that.

Regards,

Raye

[iaki_vila · Accepted solution]

Hi Raye,

If you use the parameter that i mentioned you can catch the fault message properly and to map it to tag in your response schema. You won't have any exception, check how to use this parameter in Ambuj's answer SOAP faults with "Do not use SOAP envelope" | SCN

Regards.

[Former Member · Accepted solution]

Hi Inaki,

We are using SOAP Axis. We do not have SOAP modules. We only have AF_Adapter/axis/ modules.

[iaki_vila · Accepted solution]

Hi Raye,

With SOAP-Axis adapter you can handle the fault messages. You can use for example a first XSLT to map the fault messages, if you find that tag. Is PI processing correctly the message at adapter level? or you are getting and exception like com.sap.engine.interfaces.messaging.api.exception.MessagingException: FaultMsg?

Regards.

[Former Member · Accepted solution]

Hi Inaki,

No error. It is processed correctly. Fault message is sent back to sender system correctly. When I look at SXI_Monitor, the fault is there. But sender system cannot get the error to pop out in WebUI.

Abap team used:

IF_MESSAGE~GET_LONGTEXT cannot get error message.

IF_MESSAGE~GET_TEXT can get message but only two words, and it is getting error from the 'ERROR' segment of the SOAP payload rather than the response.

Edit: We are also using custom fault provided by webservice. We do not have mapping for fault, it is pass through (same structure sender -> receiver).

Regards,

Raye

[iaki_vila · Accepted solution]

Hi Raye,

I catch your isse now. Talk with your ABAP team if they have tried this Eng Swee Yeoh suggestion

Capturing SOAP fault message in ECC client proxy | SCN

Regards.

[Former Member · Accepted solution]

Hi Inaki,

Thanks, we are trying it right now.

Regards,

Raye

[Former Member · Accepted solution]

Hi Inaki,

Suggestion solution worked.

Can you explain why ABAP has to create custom exception for Custom Fault Types?

Regards,

Raye