Show TOC

 Forward Error Handling

Forward Error Handling (FEH) is a concept that enables errors, detected during the execution of asynchronous services to be processed on the provider side. This concept is implemented using the Error and Conflict Handler (ECH).

Asynchronous communication implies that the service consumer cannot react immediately to error messages returned by the provider. Delegating error removal back to the consumer is often inefficient or inappropriate.

  • If the service is uni-directional (inbound notification and information services), no response message is foreseen in the consumer-provider interaction.

  • If the service is bi-directional (request-confirmation or query-response pattern) it often makes sense for the provider to resolve errors and conflicts on the provider side, without returning an error message to the consumer.

Examples :

The error is temporary and would disappear automatically if the message were to be processed again at a later point in time. For example, the object to be changed is temporarily locked by another user, or another message needs to be processed first.

If a product is not available, the service provider might want to respond with an alternative offer in order to retain the customer.

Using the standard messaging channel to communicate errors back to the sender and ask for clarification would take too long – it would be more helpful to use the phone or another synchronous medium.

The ECH Framework is available in the SAP back-end system.

Errors that are handed over to the ECH Framework typically occur during data conversion or business logic processing. ECH enables administrators or even business users on the provider side to follow up on error messages. In SAP Business Suite 7, you can usetransaction ECH_MONI_SEL to search for and access error cases. You can also access this transaction from the SAP Easy Access menu by choosing Cross-Application Components --> Error and Conflict Handler .

The resolution process depends on the type of error. An error may be resolved automatically, resolved manually, or rejected and delegated back to the consumer.

  • Automatic Resolution : The system retries processing or automatically rejects the request .

  • Manual Resolution : An administrator or business user corrects the error (for example, by correcting the request, correcting Customizing settings, or entering transaction data), and restarts processing. If an error cannot be resolved by the provider, the user can call the sender and ask for the request to be corrected.

The ECH Framework classifies errors into error categories. Examples include:

  • Conflict, restart not possible

  • Authorization error; manual restart possible

  • Lock request error; automatic or manual restart possible

  • Value error; manual restart possible

  • Internal term error; manual restart possible

You can define a resolution strategy individually for each error category.

To make use of the ECH capabilities, you must first activate and configure the ECH Framework in Customizing:

SAP Reference Implementation Guide -> Cross-Application Components -> Processes and Tools for Enterprise Applications -> Enterprise Services -> Error and Conflict Handling .