Specific dimensions for reporting
What they are for¶
With the reporting module, data can be fine tuned using the module's specific Amount Type and Period Length dimensions.
Amount type¶
This dimension specifies the type of data displayed by the matrix and, for data entry forms, the type of data that the user can insert. This dimension is not mandatory.
The dimension's attributes are provided below.
| Element | Description |
|---|---|
| Original in Entity currency | Indicates an amount expressed in the entity currency. This is the value indicated in the process for the entity and, if data are gathered outside of Tagetik, corresponds to the currency inserted by the user in their own system (ERP or Data Warehouse). Default value. |
| Original amount in transaction currency | Indicates an amount expressed in the currency with which the transaction is carried out (may be different from the entity's default currency). |
| Description | Allows you to insert notes or comments. |
| Proportional in Entity currency | Indicates amount types calculated by the system during the consolidation process and allows you to see the corresponding amount for each step. To generate the proportional data, the data processing applies the entity's proportionality percentage, as deployed in the consolidation area, to the original data (expressed in the entity currency). The amount converted into consolidation currency is generated on the basis of the proportional amount type by multiplying the values by the consolidation currency FX rate. The consolidable amount type is calculated by copying the converted amount, as is the case with consolidated entities using the integrated or proportional method, or by generating the equity evaluation journals for consolidated entities using the equity method. |
| Converted into Consolidation currency | |
| Consolidable in Consolidation currency | |
| Converted in Transaction currency | Indicates the amount types calculated by the system during the consolidation process and allows you to see the corresponding amount in the transaction currency for each step. |
| Proportional in Transaction currency | |
| Consolidable in Transaction currency |
The Period Length dimension¶
By default, CCH Tagetik saves data entered by the user on a cumulative basis, i.e. through the cumulative addition of amounts. However, data may be available to the user by period (monthly, bimonthly, etc.). In such cases, the user can calculate and then enter the cumulative data. However, this method is also liable to possible calculation or data entry errors. To prevent this situation, the specific Report dimension can be used, namely the Period Length dimension. The user inserts the period data in the data entry forms and CCH Tagetik calculates the corresponding cumulative values.
Example
This example shows the conversion of period data into cumulative data.
| Period data | Cumulative data |
|---|---|
| - Q1 (January - March) = 100 - Q2 (April - June) = 150 - Q3 (July - September) = 250 - Q4 (October - December) = 300 | - March = Q1 = 100 - June = Q1 + Q2 = 250 - September = Q1 + Q2 + Q3 = 500 - December = Q1 + Q2 + Q3 + Q4 = 800 |
To use the Period Length dimension, it is necessary to use length LUN_3 - Quarter.
Period Length values¶
The values for this dimension are as follows:
| Element | Description |
|---|---|
| Cumulative (LUN_0 ) | Default value in the CPM (Corporate Performance Management). The system does not carry out any calculation and the amount shown coincides with the amount in the database. In both the CPM and Analytical Workspace multidimensional matrices, the cumulative data are calculated based on the figures from the end of the previous period to the current period. |
| Monthly (LUN_1) | The cumulative data are calculated taking into account the amount of period n (the period set as a filter in the template) and the amount of period n-1. Generally used for scenarios whose open periods are 01, 02, 03, ... 12. |
| Bimonthly (LUN_2) | The cumulative data are calculated taking into account the amount of period n and the amount of period n-2. Generally used for scenarios whose open periods are 02, 04, 06, 08, 10 and 12. |
| Quarterly (LUN_3) | The cumulative data are calculated taking into account the amount of period n and the amount of period n-3. Used for scenarios whose open periods are from 03, 06, 09 and 12. |
| Every four months (LUN_4) | The cumulative data are calculated taking into account the amount of period n and the amount of period n-4. Generally used when weeks are managed as part of the periods. |
| Every five months (LUN_5) | The cumulative data are calculated taking into account the amount of period n and the amount of period n-5. Generally used when weeks are managed as part of the periods. |
| Half Year (LUN_6) | The cumulative data are calculated taking into account the amount of period n and the amount of period n-6. Generally used for scenarios whose open periods are 06 and 12. |
| Annual (LUN_12) | The cumulative data are calculated taking into account the amount of period n and the amount of period n-12. Generally used for scenarios that only have period 12. |
| Quarter to date (LUN_QTD) | The cumulative data are calculated from the end of the previous quarter to the current period. |
| Semester to date (LUN_STD) | The cumulative data are calculated from the end of the previous half-year period to the current period. |
| Life to date (LUN_YTD) | The cumulative data are calculated from minus infinity to the current period. Useful for multi-year projects. |
Period Length is not an obligatory dimension. If not specified, by default the system uses cumulative (LUN_0) in the CPM and monthly (LUN_1) in Analytical Workspaces.