Show TOC

Object documentationException Control Rule Set Locate this document in the navigation structure

 

A framework used to manage a collection of rules for response determination in exception control.

 

The use and behavior of rule sets for exception control are similar to those of other rule sets that you can define in Payment Engine, such as rule sets used in Routing Control for business objects (for example, routes and clearing agreements). For more information, see Rule Set.

Several Payment Engine components, such as Payment Processing, Routing Control, and Clearing Processing, are linked to Exception Control. To find a response type, a rule-determination process is performed. For more information, see Response Type Determination Using Rule Sets.

If you do not want to differentiate a response-type assignment, you can specify a standard response type. This standard response type is a general response for a specific combination of process, object category, and Exception Control phase. For example, you can define a standard response to every error situation along with one or more deviant rule sets that define different responses for specific payments.

You can manage rule sets for exception control and their rules as follows:

On the SAP Easy Access screen, choose   Payment Engine   Master Data   Exception Control   Define Exception Control   (transaction /PE1/EH).

For more information about the procedures, see Managing Rule Sets for Exception Control and Managing Exception Control Rules.

Structure

Exception Control Screen

The screen is divided into the following screen areas:

  • Search area

    You can enter a text to search for processes, object categories, or Exception Control phases currently loaded in the navigation tree by means of any text criteria. When you run a search, a new node with the result is created in the tree.

  • Navigation tree

    Displays the following levels of nodes in a hierarchical structure:

    • Process

      Identifies a process category in Payment Engine, which represents the different steps that payment orders or payment items go through during processing. Payment Engine supports many processes; however, not all processes are available on the graphical user interface (GUI).

    • Object category

      Identifies the type of transaction that should be checked. For example, you can classify error checks for ordering party items or for recipient items.

    • Exception Control phase

      Specifies the phase in which the error check occurs, for example, enrichment and validation for payment order or preparations for posting.

    Exception Control is divided into different phases. In the navigation tree, you can display the available combinations of processes, object categories, and Exception Control phases.

  • Business object

    Displays details about the selected process, object category, and Exception Control phase organized on the following tab pages:

    • Basic Data

      Defines a standard response type that is used if a rule set does not contain any rules or if none of the rule attributes match the error check, payment order attributes, or payment item attributes.

    • Executed Checks

      Displays the possible error checks. These checks are available as a characteristic of the rule when you add the rule to a rule set.

      Note Note

      You can enhance the predefined error checks in your customer name space.

      End of the note.

    • Possible Responses

      Displays the possible response categories. These response categories limit the response types available for selection when you add a rule to the rule set.

  • Rules

    Displays the rules in a rule set associated with the selected process, object category, and Exception Control phase.

This graphic is explained in the accompanying text.

Exception Control Screen

Details of Exception Control Rule Set

A rule set consists of one or more rules. One rule refers to exactly one response type. The same response type can occur in one or more rules.

Each rule consists of a set of characteristics based on the payment order or payment item attributes. These attributes are rule-set specific. A rule matches if the attributes of a payment order or payment item match the attributes of the rule.

You can display all available attributes depending on the object category in the rule maintenance. For more information, see Managing Exception Control Rules.

If the object category of the related rule set is a payment order type, the payment order attributes available include format, payment order priority, and payment order type. Furthermore, several ordering party item attributes are available, for example, bank key, amount, and currency.

If the object category of the related rule set is a payment item type, the payment item attributes available include such as account number, bank country, and payment item type.

The parameters process, object category, and Exception Control phase uniquely determine an exception control rule set. Exception control rules are uniquely identified by the sequence, which determines the order of the rules in a rule set. This number is used as the first search criterion during rule determination.

Integration

You can use a release workflow to supervise certain business-related transactions, such as the creation or change of a standard response type for a defined process, object category, and Exception Control phase or its related rule set. You can define these specific settings in Customizing for Payment Engine under   Exception Control   Exception Handling   Release for Exception Handling  . For more information, see Release Workflow and Release Object EH (Exception Control Rule Set).

Change documents are available when rules or rule sets are changed. You can access change documents by choosing   Extras   Change Document  .