Process Data Model definition
Introduction¶
To set up the PDM, the following elements must be defined:
- accounts/categories and measures (or custom dataset fields of Analytical Workspaces) involved in the process
- any overrides and/or exceptions on accounts/categories and measures
The order in which the records are inserted in the setup tables is important because deployment processes the rows in the order in which they were inserted.
- Define the CCH Tagetik accounts to be included in/excluded from specific steps of the process.
- Define the forms, and therefore the accounts contained in them, to be included in/excluded from specific steps of the process.
- Define the type of data to be collected on the process, the categories, if required, and the editability properties of the accounts.
- Define the process steps on which to set, remove or move the block of intercompany declarations for specific accounts or accounts/categories.
- Define the control groups from among those to be included in/excluded from the process and the types of data checked by them.
- Define the Analytical Workspace measures to be included in/excluded from the data model and/or specific steps of the process.
Customisation of the PDM¶
For processes with dimension by step and at least one step on the Entity dimension, if the default PDM does not fully meet the functional needs of the project, custom PDMs can be created. In particular, this is useful for associating subgroups of accounts with specific entities/companies and consolidation scenarios/periods.
You can also exclude one or more control groups from a specific step.
You must consider the type of step defined on the Business Workflow (Steps of the Business Workflow).
| If... | Then... | AND... |
|---|---|---|
| the Process Data Model is managed by account/step | the accounts/forms can be assigned only via the steps. Note: this operation allows you to distinguish the management of data between the contributor and the consolidator, without having to provide details of the process by category. | The relations between the accounts/forms/control groups are set as follows: - For the contributor, they are related to the step selected in the setup. - For the consolidator, they are related to the consolidator step immediately after the contributor step on which the accounts and forms are positioned. |
| the Process Data Model is managed by account/category/step | the specific categories are related to the contributor and consolidator steps of the process. In other words, contributor categories for the contributor steps and consolidator categories for the consolidator steps. Note: this operation gives a clear separation of timing between the operations carried out by the contributor and those carried out by the consolidator. | the category-step relations are set as follows: - The contributor categories are related to the contributor steps. - The consolidator categories are related to the consolidator steps. - The category groupings can be related to all the steps. The accounts/forms/control groups are then attributed to contributor steps if the categories are contributor categories, and to consolidator steps if the categories are consolidator categories. Pairs that do not comply with the rule described for assignment are discarded. |
Exceptions on forms¶
By default, CCH Tagetik automatically associates a form with a step of the process when at least one account associated with the step is also contained in the forms and editable. However, a form or a node of the grouping of forms can be excluded or added manually.
Example of excluded forms
Two different processes, statutory and management, can manage the same accounts via different forms, in different data entry steps. In the statutory process, the node that groups management data forms can be excluded from the desired step in order to view only the forms involved in the entry of statutory data.
Exceptions for account editability¶
The setting of exceptions for account editability defines the changes that users can make on the accounts.
Accounts can be made editable, non-editable, only importable (e.g. via ETL import), or be set to follow the editability condition defined in the table on the individual account (automatic behaviour).
It is possible to set exceptions on the editability of specific types of account data (all data, gross data, intercompany data) and/or certain categories of account data (all categories, amounts, journals).
The overrides set on intercompany data do not change the account settings in the table. For example, the “Editable on intercompany values” override has no effect on an account that does not allow intercompany declarations. Vice versa, on an account that allows intercompany declarations, setting a non-editable override makes the account’s intercompany data non-editable in the specific process.
Example of editable accounts
When a calculated revenue account is defined as the product of price and quantity, that configuration makes the account non-editable. For it to be editable, an editability exception needs to be created on the account, to allow the user to edit the data.
Exceptions for intercompany steps¶
By default, for accounts belonging to an intercompany matching cockpit, the insertion of intercompany declarations is blocked when submitting the step to which the cockpit is related.
For accounts not belonging to an intercompany matching cockpit, intercompany declarations are blocked by default when submitting the gross step to which the accounts are related. However, exceptions can be defined for the step in which to block intercompany declarations, or:
- Remove the intercompany account from the gross step to which it belongs, so that the declaration is never blocked.
- Move the blocking of intercompany declarations to a different intercompany step
- Set the blocking of intercompany declarations on the gross step to which said declarations belong (Automatic behaviour).
Exceptions for control groups¶
By default, CCH Tagetik includes all control groups that contain at least one account involved in the process, with the exception of control groups on which the “Include in the process if all parent accounts belong to the process” or “Include in the process if all child accounts belong to the process” option is active.
To exclude individual control groups or specific nodes of a grouping of control groups from the PDM, exceptions can be set to remove control groups.
When an exception is set to remove one or several control groups, this may have an impact on all data entered, on gross data only, or on intercompany data only.
Analytical Workspace measures¶
The setting of Measures allows you to define which measures belonging to the Analytical Workspace, and its selected datasets, to associate with the chosen step of the process.
When each association is saved, CCH Tagetik checks that every measure is associated with one step, and one step only.