Rules

You can check transaction data when processing tasks using predefined rules and then carry out a specific activity depending on the result. You use rules in cases where you only wish to process tasks if certain conditions are fulfilled.

Prerequisites

You have ensured that the rule used in the PIPE Customizing is properly set under Start of the navigation path Tasks Next navigation step Define Rules End of the navigation path and that the rule that is to be used for the relevant task is assigned under Task One-Step Processing Define Tasks or Tasks Two-Step Processing Define Aggregation Task .

Activities

A rule consists of a condition and actions that are be performed if the condition is, or is not, fulfilled.

In contrast to task processing, which is performed package by package for multiple POS transaction, the system performs rules individually for each POS translation within task processing. In doing so, each individual POS transaction can be excepted from task processing if the rule that is assigned is not fulfilled. An assigned rule is normally checked while a task is processed.

The system offers you the following rule types:

Task Complete:
The system only performs the task processing, to which the rule is assigned, when another task in rule Customizing has already been successfully processed.
BAdI:
The system performs a check of the POS transaction with a BAdI implementation. Only when the check has been successful does the system perform task processing.
Link rules AND, OR, NOT as well as Perform all Linked Rules:
The system gives you the chance to link rules together logically. This means you can perform multiple rules for one task processing. The link rules mean:
- AND Link:
  All linked rules must be fulfilled.
- OR Link:
  At least one of the linked rules must be fulfilled.
- NOT Link:
  None of the linked rules are to be fulfilled.
- Perform all Linked Rules:
  The system processes all linked rules, irrespective of whether errors have occurred in the meantime so that a rule is not fulfilled. This behavior highlights the difference from the AND link because there the system ends the execution with the first error.
Create the required link rule in Customizing in which you set out the required type and save it. Create the linking rule in Customizing. Then enter the link rule into the Link Rule field for the each other rules that are to be processed.

This behavior can be used on multiple levels so that you can construct conditions that are as complex as you wish.

The following are possible actions from a result of a rule check in the standard:

The system performs the task processing because the rule is fulfilled. The status of the task processing of the POS transaction under consideration is therefore dependent on the processing result.
Postpone the POS transaction: The task keeps the status Ready or Ready for Cancellation, but is excluded from further processing. This action is used when the POS transaction does not fulfill a precondition, such as a previously processed task, for example.
The system changes the status to Error, Error During Cancellation or Rejected. In this case the POS transaction does not participate further in the processing.

You can complete the named actions with actions of your own for fulfilled or not fulfilled rules as you wish and that way you can react according to your own individual needs to the results of a rule check.

Rules are executed according to their priority. If priorities are equal then the alphabetical series of the rule code is followed.

The system provides the following rules in the standard:

0001: Balanced Transaction
0002: Check Credit Card Data
0003: Sales Audit Performed
0004: Check Balancing of Totals Transactions
0005: Calculation for Short/Over Balancing Performed