Show TOC

Object documentationRule Locate this document in the navigation structure

 

A rule is a tripel, consisting of the

  • ID of an event

  • ID of a Boolean expression

  • ID of an action

When the rule is called in the corresponding event, the rule behaves according to the following pattern: if <Expression>=TRUE then <Actions>.

For this reason, rules in the BRF do not have an independent ID.

 

The purpose of a rule is to execute one or several actions dependent on a condition. Only if the condition is true does the system execute the action.

A rule is always assigned to an event. Each BRF event can contain any number of rules.

You can group rules together in rule sets.

SAP provides rule type 1RULES in the standard delivery. You can use this rule type as the starting point for your own implementation. It comprises all the properties of rules that are described below.

Structure

Usually, a rule comprises an expression that is Boolean and an (abstract)

action (this is the 'real rule'). In this context, an abstract action stands for any number of specific actions.

However, there are adaptations of the 'real' rule. Here is a list of all the rules supported by the BRF:

  • Rule consisting of an expression and an (abstract) action ('real rule')

    This 'real rule' is the most common one.

    It is as follows: if <expression> = TRUE then <action>. In other words, if a condition defined by the <expression> delivers the result TRUE, the system executes the assigned <action>.

  • Rule that does not contain an expression, but an action ('mock rule')

    If you do not define an expression, the system always executes the action as soon as the event is triggered.

  • Rule that contains an expression, but not an action ('mock rule')

    The system always calculates the expression, but no action is executed.

    This rule only makes sense in the following case:

    If the application that calls the event expects a result to be returned.