Rule Dimensions Definition page (Original and Consolidation scenarios)
Data Processing tile > Basic Consolidation > Rules Engine Designer on Original Scenarios > List > select rule > 
> Dimension Definition
Data Processing tile > Basic Consolidation > Rules Engine Designer on Consolidation Scenarios > List > select rule > > Dimension Definition
Purpose of the page¶
This page allows you to map input dimensions of data to be processed and output dimensions on which to write the rows generated by the data processing. This page shows the following information, in addition to the Account dimension and the Custom dimensions enabled in the environment.
- Counterparty entity, if enabled for the rule
- Counterparty custom dimension 2, if enabled for the rule
- Se, only for Consolidation journal rules and if the Counterparty entity is enabled for the rule
- Segment Counterparty Custom Dimension 2, only for Consolidation journal rules, if the Ctp custom dimension 2 is enabled for the rule and only in processes whose relationship type is by entity/synthetic custom dimension 2.
Attributes on the page
| Tab | Description |
|---|---|
| Action | Allows you to select the action to be run on the selected mapping. |
| Input Dimension | |
| Accounts | Account or node of accounts to be used as the input |
| Custom Dimension | Other dimensions, or nodes, to be used as the input, if enabled for the environment |
| Ctp Entity | Counterparty entity to be used as the input, if included in the header |
| CTP Custom Dimension 2 | Counterparty custom dimension 2 to be used as the input, if included in the header |
| Sign | Only if Map dimensions based on sign is selected for the rule. The possible values are: - >=0 - <0 |
| Apply Markup | If selected, it allows output rows to be generated with an amount equal to the value of the input data multiplied by a percentage and/or a dynamic markup. It is possible to indicate the percentage to be applied to the amount in the entity currency, to the amount of the input data in the transaction currency and in the journal currency. The indicated percentage is also applied to the write-off row of the input data. The percentage can have a negative value. A dynamic markup can also be specified (see Dynamic Markup). Note: the amounts obtained are rounded to the same number of decimals as the currency to which they refer. An exception is made for accounts in which the Manage maximum number of decimals attribute is set. If not selected, a 100 % percentage is applied, resulting in the full amount from the input data. |
| Output Dimensions | |
| Account selection | Account dimension selection method (see Dimension selection method). |
| Accounts | Account to be used as the output |
| Custom Dimension selection | Custom dimension selection method (see Dimension selection method). |
| Custom Dimension | Other dimensions to be used as the output, if enabled for the environment |
| Ctp Entity selection | Counterparty entity dimension selection method (see Dimension selection method), if included in the header. |
| Ctp Entity | Counterparty entity to be used as the output, if included in the header. |
| Ctp Custom Dimension 2 selection | Counterparty custom dimension 2 selection method (see Dimension selection method), if included in the header. |
| CTP Custom Dimension 2 | Counterparty custom dimension 2 to be used as the output, if included in the header. |
Swap Entity with Ctp Entity (IC Amount Rules)¶
Based on an IC entry on a declaring entity, this option for IC Amount rules allows you to create an IC entry for the counterparty entity on the output dimensions specified in the Rules Engine Designer on original scenarios.
For each run entity, the system considers the rows of IC Amounts on the input dimensions whose counterparty entity is the same as the run entity, and rows are generated on the IC amounts on the output dimensions by swapping the declaring entity with the counterparty entity.
The amount of the row generated on the output dimensions, in the entity currency, is defined on the basis of the amount of the input row transaction currency.
| If... | Then... |
|---|---|
| the transaction currency is the same as the output entity currency (input Ctp entity) in the process. | the amount in the entity currency is set to be equal to the amount in the transaction currency. |
| the transaction currency is different from the output entity currency in the process. | the amount in the entity currency is defined as the amount in the transaction currency converted into the currency of the output entity in the process. The conversion is made by applying the associated FX rate to the conversion type of the input account in the list. |
The following conversion options are possible:
| Option | Description |
|---|---|
| None | The amount in the entity currency is set to be equal to the amount in the transaction currency. |
| Final FX rate | The final FX rate will be applied |
| Historical FX rate | The final FX rate will be applied |
| P&L FX rate | The chosen FX rate is applied on the basis of the conversion method for the countervalue calculation specified in the amount and IC rules: - Final FX rate - Average FX rate - Period average FX rate: the period average FX rate is applied to the cumulated amount in the transaction currency as at the processing period. The periodic conversion algorithm is not applied. - Override Period average FX rate on P&L or on Variations accounts: the final FX rate is applied. |
All other conversion types are treated as P&L FX rates.
To obtain an intercompany declaration of the opposite sign to the input sign, you must apply a negative Markup percentage (-100% for the entire amount).
The amount obtained is rounded to the same number of decimals as the output entity currency, except for accounts for which the Manage maximum number of decimals option is selected.
For rules which have the Output Ctp Entity selection option set to Account Entity Ctp Entity Swap, it is not possible to select the Write off input data option.
Example
IC amounts - input rows:¶
| Company | Account | CTP entity | Entity currency | Entity currency amount | Transaction currency | Transaction currency amount | Origin |
| A | Revenues | B | USD | -80 | EUR | -100 | INPUT_WEB |
| C | Revenues | B | USD | -220 | USD | -220 | INPUT_WEB |
Rule - Dimensions definition:¶
| Input Account | Input Ctp Entity | Markup % | Output account | Output Ctp Entity Selection |
| Revenues | $ | $ | -100% | Costs |
The rule is related to a node inserted in the execution plan of entity B for the data processing scenario/period.
Entity B’s currency is EUR. EUR FX rate = 1, USD FX rate = 1.1
IC amounts - Output rows generated by the data processing of Entity B¶
| Company | Account | CTP entity | Entity currency | Entity currency amount | Transaction currency | Transaction currency amount | Origin |
| B | Costs | A | EUR | 100 | EUR | 100 | PROC_RED |
| B | Costs | C | EUR | 200 (=220 * 1/1.1) | USD | -220 | PROC_RED |
Replace Entity with Ctp (Gross Amount Rules)¶
Based on an IC entry on a declaring entity, this option for Gross Amount rules allows you to create a Gross amount for the counterparty entity on the output dimensions specified in the Rules Engine Designer on original scenarios.
For each run Entity, the rows of IC Amounts and Entity journals on the input dimensions with Ctp Entity equal to the run Entity are considered and rows are generated on the Gross mounts on the output dimensions by replacing the declaring Entity with the Ctp Entity. The Ctp Entity is not defined because it does not exist on the Gross Amounts
The Entity currency amount of the generated row on the output dimension is defined from the transaction currency amount of the input row in the same way as for the 'Swap Entity with Ctp Entity' option of the IC Amount rules.
For rules which have the Output Ctp Entity selection option set to Replace Entity with Ctp Entity, it is not possible to select the Write off input data option.
Dynamic Markup¶
This option allows you to apply a dynamic markup to the input data amount.
The dynamic markup is a formula that can include Percentages from consolidation area, Coefficients from gross amounts, and can be composed using other markups.
The markup value is determined by calculating the indicated formula based on the data processing scenario/period and the dimensions in the input data row.
If the formula consists of more than one object or markup and the value of an object cannot be calculated (for the reasons given below) or there is a division by zero, only that part of the formula will be considered to be zero.
If the amount obtained by applying the markup has a number of integer digits greater than the output amount field (18), the output amount is considered to be zero and the row is not generated.
The following attributes can be chosen for the Percentage from consolidation area object:
-
Apply to:
-
Original scenario. For rules on original and consolidation scenarios
When this option is enabled, the Suffix field is displayed. It is appended to the code of the original data processing scenario to generate the code of the consolidation scenario - Consolidation Scenario (Default) For rules on consolidation scenarios
-
Measure:
-
Direct ownership %
- Equity ratio %
- Equity ratio % of the period
- Actual ownership %
- Period - Actual F.I. %
- Consolidation %
-
Scenario:
-
From context. It is the data processing scenario (Default)
-
Linked. It is possible to choose between the following scenarios linked to the data processing scenario:
- Previous
- Opening: is the previous scenario/open period
- Next
- Reference 1
- Reference 2
- Reference 3
- Reference 4
- Reference 5
- Period. Not visible if the scenario is 'Opening' because the open period is automatically chosen.
-
From context. It is the data processing period (Default)
- Previous. Calculated by applying the period length of the Scenario selected above / data processing period. If the period length is equal to the data processing period, the scenario/opening period related to the scenario selected above is considered. If the period length is zero, the preceding period is deemed not to exist.
-
Entity:
-
From context. It is the input data Entity. (Default)
- Ctp from context. It is the input data Ctp Entity.
- Ctp segment from context. It is the Ctp Entity for Segment of input data. Only for input data on categories of consolidation journals.
The value of the percentage is read from the Definition Result Table of the consolidation area and is automatically divided by 100.
In the following cases, the Consolidation Area Percentage is taken to be zero:
- the selected scenario/period is not defined or does not exist in the elements list
- the row is not present in the Definition result table of the consolidation area for the selected scenario/period and Entity
- the percentage definition has Entity = Ctp from context and the input data row does not have Ctp Entity
- the definition of the percentage has Entity = Ctp Segment from context and the input data row has Amount or Entity journal category.
The following attributes can be chosen for the Gross amount Coefficient object:
- Account: an account must be selected.
- Scenario and Period: same options as specified for the consolidation area percentage object. For rules on consolidation scenarios, the coefficient is read from the original scenario/period associated with the consolidation scenario specified on the object (determined using the period length of the consolidation scenarios/periods)
-
Entity:
-
From context (Default). It is the input data Entity. Exception: for rules on consolidation scenarios with the option 'Read input data from entity node', it is the Output Entity specified in the Entity definition.
- Ctp from context. It is the input data Ctp Entity.
- Ctp segment from context. It is the Ctp Entity for Segment of input data. Only for input data on categories of consolidation journals.
- Fixed. An Entity must be selected.
-
Category:
-
From context. It is the input data category.
-
Fixed (Default) An amount type category must be selected.
-
Custom dimensions. The dimensions managed on amounts in at least one process are displayed:
-
From context. It is the input data dimension.
- Fixed (Default) . A dimension must be selected.
- Not relevant. No filter is applied.
-
The following options are only visible for custom dimension 2 if there is at least one process with Entity/custom dimension 2 relationship type.
- Ctp Custom dimension 2 from context. It is the Ctp custom dimension 2 of the input data.
- Ctp Custom dimension 2 for segment from context This is the Ctp Custom dimension 2 for segment of the input data. Only for input data on categories of consolidation journals.
- Amount:
-
Entity currency
- Transaction currency. Visible if there is at least one process with the option 'Manage on gross amounts' active.
-
Entity currency:
-
From context. It is the currency of the input data:
- Entity currency for amounts and Entity journals of the original scenario and proportional amount type
- Journal currency for consolidation journals of original scenario and proportional amount type
- Consolidation currency for amounts, consolidation and entity journals of Converted and Consolidable amount type
- Fixed (Default). A currency must be selected.
- Not relevant. No filter is applied.
- Transaction currency. Visible if there is at least one process with the option 'Manage on gross amounts' active.
-
From context. It is the transaction currency of the input data.
- Fixed (Default). A currency must be selected.
- Not relevant. No filter is applied
The coefficient is read from the Gross Amounts table by filtering on the dimensions according to the specified options:
- Fixed: a filter is applied to the specified code
- From context: a filter is applied on the dimensions of the input data
- Not relevant: no filter is applied
Special cases where no filter is applied:
- Custom dimensions defined in the object and not managed in the data processing
- Transaction currency defined in the object and the data processing has 'Manage on gross amounts' option disabled
The value of the coefficient is read from the specified Amount field. If the transaction currency amount has been selected and in the data processing the transaction currency is not managed on the gross amounts, the data processing still reads the transaction currency amount (because in this case the Transaction Currency Amount is equal to the Entity Currency Amount).
In the event that, by applying the specified filters, more than one row of the Gross Amounts is read, the coefficient is given by the sum of the amount of the extracted rows.
In the following cases, the coefficient from Gross Amounts is assumed to be zero:
- the selected scenario/period is not defined or does not exist in the elements list
- the row is not present in the Gross Amounts table for the selected scenario/period and dimension
- the definition has Entity = Ctp from context and the input data row does not have Ctp Entity (Input data are either Gross Amounts or data row without Ctp Entity)
-
the definition has Entity = Ctp Segment from context and the input data row has Amount or Entity journals category.
-
the definition has Custom dimension 2 = Ctp from context, the Process relationship type is by Entity/custom dimension 2 and the input data row does not have Ctp Entity
- the definition has Custom dimension 2 = Ctp segment from context, the Process relationship type is by Entity/custom dimension 2, and the input data row is Amounts and Entity journals.
IMPORTANT: The recoding and deletion utilities for Entity, account, category, custom dimension and currency do not affect the coefficient objects from Gross Amounts, so if fixed codes are used, they must be changed manually. Coefficients with fixed codes that no longer exist are considered equal to zero.