Application Exception Not Routed to the Exception Handler Defined in the Integration
If the exception coming from Oracle Fusion Applications is not routed to the
appropriate exception handler that you defined in the integration, this is because the
Oracle Fusion Applications web service returned the fault code in the reply SOAP message as
env:Server
. This means it was returned as a generic SOAP exception and
not as a business fault.
For this reason, the exception is not caught by the exception handler. When you receive
the fault code under the SOAP message as env:Server
, this is expected
behavior and the message is not routed to the specific exception handler.