Validations
Validations option function¶
The Validations option enables, in the process, the validation of data using a standard diagnostic check or plausibility diagnostics. It also allows you to change the validation rules for the specific process.
Characteristics of the diagnostics¶
Diagnostics, defined using the validation rules, allow you to run diagnostics for entities and, from the relative data entry activities, diagnostics for amounts and journals. Allows you to define the checks to be carried out with the diagnostics and therefore, indirectly, to define how automatic data balancing and data submission works.
Stored procedure and diagnostic parameters¶
Allows you to run, together with the other data processing to be launched with the diagnostics, a stored procedure that responds to CCH Tagetik’s minimum requirements. This only makes sense if you have chosen to run data processing on diagnostics.
The name of the stored procedures that can be run directly from CCH Tagetik must start with CPM_SP_, regardless of any schemes. In order for the stored procedures to be able to read the diagnostic parameters, the files of those parameters must be named as follows, based on their content:
| Name | File contents |
|---|---|
| PROCESS | Data collection process |
| ENTITY_HIERARCHY | The process’s organisational hierarchy |
| STEP_LIST | List of steps |
| ORIGINAL_SCENARIO_PERIOD_LIST | List of original scenarios/periods |
| ENTITY_LIST | List of entities |
| CONTRIBUTOR_NODE_LIST | List of contributor nodes |
| CONSOLIDATOR_NODE_LIST | List of consolidator nodes |
Stored procedures are only run on the original scenarios/periods.
Validation of annual results¶
The validation of the annual results consists of running diagnostics on the control group $BS_
Tracking of errors found by diagnostics¶
Errors found by diagnostics are only saved and added/updated on every submission or running of the diagnostic tool if the “update log” option has been activated.
Errors can only be logged for the original scenarios. It is always possible to justify errors and attach explanatory/justifying files, for scenarios that are not stored offline, by accessing the log management window. The authorisation of an error can only be added/removed if the With authorization of blocking errors option has been selected from among the submission override modes in the submission rules.
Reporting failed journal submission¶
CCH Tagetik allows you to configure the severity (severity) with which the failure to submit a journal is reported. To do this, journal submission needs to have been enabled. Journal submission is active on the entities/steps on which a task workflow was entered for the submission of journals in the Processes tile > Process setup > Mapping.
Submission error severity (Severity)¶
Severity levels are used by the submission to assess the correctness of an entity’s data. If diagnostics return results with blocking severity, then the submission of an entity’s data cannot be completed.
Characteristics of plausibility diagnostics¶
This type of diagnostics compares the amounts of one scenario/period with the amounts of the same collection of data from another different scenario/period. It therefore shows the results of the comparison via various error messages or warning messages.
Functioning of plausibility diagnostics¶
When a definition row is added or edited in plausibility diagnostics, a deployment data process is automatically run when saving, allowing you to obtain all the entities deriving from this synthetic definition. In particular, the following will happen:
- For entities: if a node of entities is selected, it is deployed in the nodes’ individual entities.
Note: the system only considers those which belong to the process. - For contributor nodes: nodes are deployed based on the selected node type.
Note: the system only considers nodes that are significant in the data collection process, or nodes in the entity hierarchy which, in the data collection process, are To Approve or To Submit. - For consolidator nodes: nodes are deployed based on the selected node type.
Note: the system only considers nodes that are significant in the consolidation process, or nodes in the entity hierarchy which, in the consolidation process, are To consolidate.
Where to define the generic validation rules and the plausibility check logics¶
The generic validation rules and plausibility check logics are defined in the following sections, respectively:
Setup & Admin > Data processing > Diagnostic > Validation
Navigation panel > Data Processing > Diagnostic > Validation
See .
Setup & Admin > Data processing > Diagnostic > Plausibility check logics
Navigation panel > Data Processing > Diagnostic > Plausibility check logics
See .