| # Rules (tgbrg7500m000) These four rules configure part of the business functions and business processes: Consistency rule Parameter setting rule Transformation rule Static condition setting rule Rules (tgbrg7500m000) To list and maintain all four rules, use the Rules (tgbrg7500m000) session. To create a rule, complete the following steps: Click New In the Rule Type field, select the type of rule that you want to create. In the Rule field, specify a name or code for the Rule. Start the text editor and create the IF-part of the rule, click Rule Condition. After the IF logical operator, in the text editor, specify one or more business functions. Note You must leave a space between the operators and the operands, such as: `BF, 1`. Click Save To zoom to lists of business functions, business processes, and static conditions you can include in the rule condition, on the Options menu in the text editor, click Start Zoomsession. This zoom session can also be used to automatically insert statements. Note If the `IF`-part of an expression is empty, the rule is always valid. After you have defined the IF-part of a rule, you must define the `THEN`-part. To do this, complete the following step: To create the `THEN` part of the expression in one of the following Baan sessions, click `THEN`-part: The Set Parameters by Rule (tgbrg7117m000) session. The Select Business Processes by Rule (tgbrg7127m000) session. The Set Static Conditions by Rule (tgbrg7137m000) session. It depends on the type of rule as to which of the LN sessions is started. In the case of consistency rules, you cannot specify the THEN part in a separate LN session. Instead, you must specify the THEN part in the text editor. Types of rules This section explains the different kinds of rules, and includes examples of how to illustrate the syntax that must be used. Consistency rule This type of rule is an expression that contains a combination of business functions on the basis of which one or more business functions must be included in the business model. Example `IF <BF, BF5, Sales>` `THEN <BF, BF12, Sales Order Management>` If the Sales business function is part of the Business Function Model, then the Sales Order Management business function must be part of the Business Function Model. Parameter setting rule This type of rule determines the value of parameters. The value is determined on the basis of a combination of business functions, business processes/static conditions. Example `IF <BF, BF3, Inventory Location Control>` `THEN` `Parameter` `Use ILC Yes` When the Inventory Location Control business function is in the Business Function Model, then the Use ILC parameter must receive the value `Yes`. Transformation rule A transformation rule is an expression that imposes a unilateral dependency on business processes in relation to business functions. If specific business functions are present in a business model, the business processes related to these business functions through the transformation rules you created are automatically incorporated in these business models. This rule is used to select certain business processes from the repository and copy them to the Business Process Model of the business model if the rule condition is true. Example `If <BF, BF5, Sales>` `THEN` `SBP 033 Sales` If the Sales business function is in the Business Function Model, then the Sales business process must be incorporated in the Business Process Model. Static Condition Setting rule This rule determines the value of static conditions depending on the business functions used in the business model. The values of the static conditions are used to choose between the arrows leaving control activities in business processes. If the defined rule evaluates to true, the static conditions based on this rule are set to Yes. When leaving a control activity, some arrow(s) must be followed if the static condition is set to Yes; the other arrow(s) must be followed if the static condition is set to No. The conditions are static because the rules relate to implementation decisions, which are usually only made when a new implementation/optimization phase is started. They do not relate to operational decisions, which are made each time a process is carried out. Example If `<BF, BF7, Special Pricing>` `THEN` Use Special Pricing `Yes` If the Special Pricing business function is in the Business Function Model, then the Use Special Pricing static condition should have the value Yes. If you want to create a static condition setting rule, the static conditions must first have been defined in the Static Conditions (tgbrg5580m000) session. To define static conditions and static condition setting rules, use one of the following ways. Both are possible if one of them is used consistently: A static condition is set to No by default. If a rule related to that static condition is met, the static condition is set to Yes. Because this method has been used for the models in Baan IVc, the default values of the static conditions is always No. The Set Static Conditions by Rule (tgbrg7137m000) session only includes the conditions that must be set to Yes. A static condition is set to Yes by default. If a rule is met, the static condition is set to No. In this case the default values of the static conditions are always Yes, and the Set Static Conditions by Rule (tgbrg7137m000) session only includes the conditions that must be set to No. Although this is a possible option, the first possibility is used as a standard. |