ABAP proxy exception to SOAP fault and vice versa not getting mapped

[Former Member]

Hi there,

I have these scenario's: ABAP proxy to SOAP (AXIS framework) and the other way around, synchronous, using AAE.

When declaring the Synchronous Service interfaces we also defined error message types in order to pass system and application exceptions back to the service consumers.

The behavior we are observing is as follows;

When an exception is generated on the ABAP proxy, the error message type is correct generated and filled with the corresponding values in the ABAP proxy runtime. However, when the response arrives at the service consumer, it only contains a SOAP fault filled with some kind of generic PI mapping exception information.

1. Why is the original ABAP proxy exception not mapped/passed into the SOAP response?

2. What can we do in order to change that situation?

3. Does it has to do with the use of the AAE - Advanced Adapter Engine or the AXIS framework?

PS: We have performed a test of the Operation Mapping - OM using the ABAP exception as input and it did work correctly, so the error structure seems to be Ok.

Many thanks for your replies.

Edited by: Roberto Viana on Jul 26, 2010 8:30 PM

[Former Member]

Problem was caused by some differences in namespaces between source and target.