Rules Engine Designer Groupings - Consolidation

Tile Data Processing > Basic Consolidation > Rules Engine Designer on Consolidation Scenarios > Groupings

Purpose of the page

This page allows the creation of groupings between rules to be applied to consolidation scenarios. It also allows you to drag a rule from one node to another.

Fields of the Attributes Tab

Field	Description
Cod.	Rule Grouping Code
Description	Description of the grouping in set languages
Dimensions management	List of custom dimensions to be processed in addition to the Account dimension.
Enable carry forward	Indicates that the journal must be carried forward into the subsequent scenario.
Advanced
Enable writing off	Allows you to choose whether to generate the input tuple reversal row. This is active by default, because the data processing’s standard behaviour is the reclassification that reverses the data present on the input dimensions and sets the same value on the output dimensions. Deactivate to use the value present on an input account/dimensions to generate rows on other output dimensions only. In this case, an input data reversal row is not generated, but only the rows on the output dimensions based on the value present on the input dimension data.
Multiple input dimensions	Indicates whether to deploy and then generate the same tuple of input dimensions several times within a rule (see Allow Multiple Relationships).
Map dimensions based on the sign	Indicates whether you want to manage a rule based on the sign of the sum of the input data (see Map dimensions based on sign).
First application of the rule	For the entity journal and consolidation journal rules, this defines whether and how to manage the change in the application of the rule compared with the carry forward scenario. Rule which, for a given entity, is present in the execution plan for the first time in the data processing scenario/period. Rule which has Map dimensions based on sign active and the sum of the rule’s input data changes sign between the carry forward scenario/period and the data processing scenario/period (see Change rule application from carry forward scenario).
Variation type - First application	Only if First application of the rule = Specific variation/detail type. Code of a variation type variation/detail type to be used to identify the control group variation.
Rule no longer applied	Rule which, for a given entity, is no longer present in the execution plan associated with the data processing scenario/period. Rule which has Map dimensions based on sign active and the sum of the rule’s input data changes sign between the carry forward scenario/period and the data processing scenario/period (see Change rule application from carry forward scenario).
Variation type - Termination of the application	Only if Rule no longer applied = Specific variation/detail type. Code of a variation type variation/detail type to be used to identify the control group variation.

Fields of the Relationships tab

Field	Description
Nodes	Node of rules to which the rule is matched in order to be used.