Rows (Consolidation journals) page
User
Processes tile > select process > Consolidator > Overview tab or Step tab > (Actions) Edit windows > Edit Consolidation journals > select header > 
> Rows
Processes tile > select process > Step tab > from a workflow task > select a consolidation journals task > Run > select header > > Rows
Navigation panel > Processes > select process > Consolidator > Overview tab or Step tab > (Actions) Edit windows > Edit Consolidation journals > select header > > Rows
Navigation panel > Processes > select process > Step tab > from a workflow task > select a consolidation journals task > Run > select header > > Rows
Purpose of the page¶
This page allows you to insert the entries that comprise the individual journal. It also shows the origin for every entry.
Entries inserted manually have “INPUT_WEB” indicated as their Origin.
Note: you can configure CCH Tagetik so that entries with different origins are different colours. See Colours by origin option in the .
The page may show a subset of journal rows depending on the filters set by default in the journal rules (Journal rules and settings page) or set specifically for the page (
).
Filters on the page
The most significant filters for the page and the results that they give you are described below.
| Element | Description |
|---|---|
| Show only main accounts | Allows you to view only accounts that are defined in the process data model as “main accounts on journals” (). This hides the accounts that are less significant for the journal. |
| Exclude Result accounts and their variations | This allows you to exclude accounts belonging to the set of result accounts specified from among the requirements of the process’s calculation logics (). In particular, the Profit & Loss result account, the Balance Sheet result account and their variations, determined taking account only of control groups belonging to the process, are excluded. |
| Account type | Allows you to view only accounts of the type indicated by the Journals data entry: account type option, unless “Any” is selected (Default settings window). |
| Account nature | Allows you to view only accounts of the selected nature. |
Icons on this page
| Element | Description |
|---|---|
| Row just added but not yet saved | |
| Row being deleted but not yet saved | |
| The rows cannot be edited. The reason for the lock is reported, e.g. “Row already posted” if the user has tried to assign the journal draft status. | |
| Draft Journal. |
Actions on this page
| Element | Description |
|---|---|
| Spreadsheet view: shows the data in a spreadsheet. | |
| List view: shows the data in a table. Default view. | |
| Allows you to access specific actions for the rows, see Actions from the journal rows. |
Attributes on the page
Not all attributes are editable.
| Field | Description |
|---|---|
| Scenario | Scenario set in the header. Not editable. |
| Period | Period set in the header. Not editable. |
| Journal number | Journal number in the header. Not editable. |
| Entity | If the journal type is not “many to many relationship”, you can choose one of the two header entities. The other is automatically set as “Segment CTP Entity”. If the journal type is “many to many relationship”, the chosen entity must meet the following requirements: - Editable by the user. - Belong to the selected process. - Belong to the selected scenario/period and, on that scenario/period, cannot be an “Only CTP” entity. - Start date and end date, if present, must be between the start date and end date of the selected scenario/period. - Must belong to aùconsolidation node that is editable for the user. |
| Category | Category set in the header. Not editable. |
| Account | Account on which a value is entered. The chosen account must meet the following requirements: - Editable for the user. - Linked to the data model process associated with the entity to which the journal belongs. - Start date and end date, if set, must be between the start date and end date of the scenario/period to which the journal belongs. |
| Custom dimension | For every custom dimension that is managed and enabled in the process’s journal rules, you can select an element of the custom dimension which meets the following requirements: - Editable for the user. - Visible from the selected entity. - Visible from the selected account. If no value is selected, the custom dimension will be shown as the entity’s default custom dimension or the custom dimension with the lowest code from among those which meet the above requirements. IMPORTANT: the custom dimension 2 is managed even if it is not enabled in the process’s journal rules, but the process’s relationship type is “entity - custom dimension 2” or “entity - synthetic custom dimension 2”. If the relationship type is “entity - custom dimension 2” and the journal type is “many to many relationship”, the system will behave as follows: |
| CTP entity | Typically inserted if the journal is used to eliminate an entry that had been declared with a counterparty in the financial statements of the individual entity. If the journal type is not “many to many relationship” and the Manage CTP entity and CTP custom dimension 2 independently of the header relationship option is not enabled in the process’s journal rules, if defined it must be the same as the segment CTP entity. If the journal type is “many to many relationship” or the Manage CTP entity and CTP custom dimension 2 independently of the header relationship option is enabled in the process’s journal rules, the chosen entity must meet the following requirements: - Belong to the selected process. - Must belong to the selected scenario/period. - Start date and end date, if present, must be between the start date and end date of the selected scenario/period. You can define a list of most frequently used counterparty entities, see . To use a subset of entities as counterparties, it may be useful to create a group of counterparties (Dynamic counterparty groups). |
| Counterparty custom dimension 2 | Only present under the following conditions: - Custom dimension 2 is managed. - The process’ relationship type is “entity - custom dimension 2” or “entity - synthetic custom dimension 2”. It is only mandatory if a CTP entity has been specified. If the process relationship type is “entity - custom dimension 2”, the journal type is not “many to many relationship” and the Manage CTP entity and CTP custom dimension 2 independently of the header relationship option is not enabled in the process’s journal rules, if defined it must be the same as the segment CTP custom dimension 2. In other cases, you can select an element of the custom dimension 2 and, if no value is selected but the field is mandatory, the counterparty custom dimension 2 is automatically set as the CTP entity’s default custom dimension. |
| Segment CTP Entity | If the journal type is not “many to many relationship”, it is possible to choose one of the two header entities (the one not selected as “Entity”). If the journal type is “many to many relationship”, the chosen entity must meet the following requirements: - Editable for the user. - Belong to the selected process. - Belong to the selected scenario/period and, on that scenario/period, cannot be an “Only CTP” entity. - Start date and end date, if present, must be between the start date and end date of the selected scenario/period. - Must belong to aùconsolidation node that is editable for the user. |
| Segment CTP custom dimension 2 | - Only shown if custom dimension 2 is managed and the process’s relationship type is “entity - custom dimension 2” or “entity - synthetic custom dimension 2”. If the relationship type is “entity - custom dimension 2” and the journal type is “many to many relationship”, the system will behave as follows: |
| Journal currency | Header currency. Not editable. |
| Journal currency amount | Amounts are indicated with the sign defined in the account list settings. Alternatively, you can show the debit and credit in two different columns: Journal currency amount - Debit and Journal currency amount - Credit. This happens if the Amounts option is set to Write amounts in Debit & Credit columns in absolute value in the journal rules definition (Default Settings window). Regardless of the number of decimals inserted, amounts are shown with a number that is consistent with those assigned to the currency they are expressed in, with the exception of “Other stocks” and “Other variations” accounts where the Manage maximum number of decimals option is active (see ). For these accounts, it is possible to insert up to 9 decimals. |
| Override FX rate | If selected, it is possible to edit all the amounts in the current row, thereby indirectly overriding the field applied to change from the journal currency amount to the entity currency amount or transaction currency amount. Otherwise, only the entity currency and transaction currency will be editable, but the amount will not be. On saving, it automatically defines the row amount in the entity currency and the transaction currency based on the account’s conversion type. |
| Company currency | If not entered, it will be defined as the selected entity’s currency. |
| Entity currency amount | If the entity currency is not entered, or is the same as the journal currency, it will be defined as the journal currency amount. Otherwise, if the Override FX rate option is not selected, the entity currency will be defined automatically based on the account’s conversion type. For the rest, the considerations made for the Journal currency amount will be valid. |
| Transaction currency | Only present if the transaction currency is managed on consolidation journals in the process’s journal rules. If not entered, it will be defined as the journal currency. |
| Transaction currency amount | Only present if the transaction currency is managed on consolidation journals in the process’s journal rules. If the transaction currency is not entered, or is the same as the journal currency, it will be defined as the journal currency amount. Otherwise, if the Override FX rate option is not selected, the entity currency will be defined automatically based on the account’s conversion type. For the rest, the considerations made for the Journal currency amount will be valid. |
| Notes | Any explanatory notes |
| Additional notes | Any additional notes |
| Financial investments event | Number of the financial investment event existing between the various pairs of entities in the group. Defined automatically by the financial investment elimination data processing. Information used in conversion step: if this field is defined, CCH Tagetik applies the FX rates of the structure linked to the event. |