Reporting and Handling Errors (SAP Library - SAP Exchange Infrastructure (BC-XI))

Reporting and Handling Errors

Purpose

The options for error handling depend on the type of communication chosen:

Asynchronous Communication: On the outbound side, the application can only handle errors that occur when the message is being sent (for example, the outbound queue is full). These errors can be caught and persisted using the exception class CX_AI_SYSTEM_FAULT. On the inbound side, as in the synchronous case, you can define fault messages, which are then only forwarded to monitoring (and not to the sender).

Synchronous Communication: Using fault messages you can handle errors that have occurred on the inbound side. To confirm an error, the Proxy Framework sends the fault message from the receiver back to the sender, which can then respond to it.

Process Flow

In the graphic below, an error from the receiver system is reported to the sender system in synchronous communication:

If an application on the inbound side triggers an error, the Proxy Framework converts the corresponding exception class to a fault message and transfers it to the sender system using the Integration Server.

The Proxy Framework in the sender system interprets the fault message and triggers the exception for the outbound interface.

In the sender system, the application can catch and handle the exception using a Try/Catch block. Using the super exception class CX_AI_APPLICATION_FAULT you can - in a similar way to the statement WHEN OTHERS in a CASE statement - catch all remaining application errors.