Show TOC

Component documentationException Control (FS-PE-EH) Locate this document in the navigation structure


You use this component to define business rules that determine suitable response types for errors that occur during straight-through processing (STP) and file handling. End-to-end payment processing is divided into a sequence of logical processing steps. If the system finds errors in one of these steps that would prevent further processing of a payment, then a suitable response is required. Payment Engine provides flexible functions for exception handling, thus enabling financial institutions to configure control over the possible responses to exceptions.


Exception Control handles all situations in payment order processing and payment item processing that diverge from straight-through processing. Likewise, this component handles errors in File Handler that may result in the creation of a dummy order. Furthermore, errors occurring during transfer by feeder systems and outbound conversion are processed in exception handling.

The following components of Payment Engine are linked to Exception Control:

Payment Engine directly handles exceptions during payment processing using the payment order management transaction:

On the SAP Easy Access screen, choose   Payment Engine   Payment Order Management   Edit Payment Orders (Expert)   (transaction /PE1/PO_EXPERT).

When you process a payment order, you can define whether Exception Control is to be used if an error occurs. If Exception Control is used, exceptions related to processed payment orders and items are listed on tab pages in the payment order management transaction. The exceptions are grouped on the Exception tab page of the payment order or the Exception tab page of its payment items as an error vector. For more information, see Payment Order and Payment Item Overview.


If an error occurs in any of the Payment Engine components that are linked to Exception Control, the system stops the process that was being executed at that moment and transfers the error to Exception Control.

Exception Control recognizes the position where the process was stopped by the following parameters:

  • Process identifier that specifies the stopped process

  • Object category that was being processed

  • Exception Control phase within the process

  • Error check that specifies the failed Exception Control phase with accuracy

Exception Control is based on user-definable rule sets that identify which response is preferred in a certain error situation. These rule sets can be based on attributes of the Payment Engine metaformat available in rule maintenance. According to their assigned response type, the rules determine whether a check result leads to termination of processing and whether follow-up actions need to be carried out on the payment order or a payment item. You can define response types in Customizing based on predefined response categories. For more information, see Response Category and Response Type.

If the system has posted the ordering party item of a payment order, but the recipient items have to be returned, a response type defined in Customizing can initiate the return of the payment. This type of payment return is called an active return. For more information, see Processing of Active Returns.

A plausibility function in Exception Control ensures that only relevant responses can be defined for a specific error situation. This means that certain error situations can only be linked to certain responses depending on the process in question, the object category, and the Exception Control phase. You can set any permitted response depending on these parameters. For more information, see Exception Control Rule Set and Managing Exception Control Rule Sets.

If the response type causes the process in end-to-end payment processing to be continued, Exception Control ensures that the process continues from the correct position with the correct parameters. Depending on the response type, the object in question (payment order or payment item) can be resubmitted to end-to-end payment processing at different positions: Either directly from the position where the transfer took place or at the beginning of the process during end-to-end payment processing from which the transfer took place, for example, payment processing or clearing and settlement.

After the system performs the response, the system checks and determines the following:

  • If the response has been performed successfully, processing within Exception Control ends for the business object in question.

  • If it is not possible to perform a response, the system triggers an end response type to be carried out.