Diagnostic Rules page

Admin

Application database > Processes tile > select process > > Process setup > (Data Processing section) Validations > Diagnostic >

Application database > Navigation Panel > Processes & Workflows > Processes > select process > > Process definition > (Data Processing section) Validations > Diagnostic >

Purpose of the page

This page allows you to customise the generic validation rules with a diagnostic check on the process and to define overrides.

Generic rules

Field	Description
Validation
Run data processing on diagnostic	Allows you to run all data processing enabled for the process (with the exception of cash flow planning and closing) when running the diagnostics.
Also include the stored procedure	Only with Run data processing on diagnostic selected. Include a stored procedure that meets CCH Tagetik’s minimum requirements in the data processing to be run when diagnostics is launched.
Diagnostic result: Show forms on row	Allows you to view, for every error on the control group or account in the diagnostic result window, the forms on which the control group accounts can be edited or the account itself. Note: (non-transactional) standard forms can be edited using Excel or online.
Categories for which to show the result	Allows you to manage the categories for which to display the validation of the year’s result, even in the absence of unbalanced amounts. Note: for control group $BS_, diagnostics will show the result, even if balanced, on the categories defined here.
Restore default values	Only if the rules have already been customised, restores the rules’ default values.
Result log
Enable detected errors trace	Allows you to log errors returned by diagnostics so you can consult, justify and authorise them. Note: only logged errors are saved and can therefore be consulted over time.
Don't propagate the authorized blocking error information	This check looks for the presence of blocking errors authorised by users responsible for the entity on which diagnostics were run. - Do not run: the check is not performed. - Blocking: the check is performed and the presence of blocking and authorised errors is reported with blocking severity. - Non-blocking: the check is performed and the presence of blocking and authorised errors is marked as being of non-blocking severity. - Only Diagnostic: the check is only performed if explicitly requested by running customisable diagnostics. When diagnostics are run automatically from the cockpit/other data processing, the check is not performed. The prerequisites for running this check are: - the traceability of errors found by diagnostics is enabled - the submission mechanism is enabled in the submission rules via authorisation of blocking errors
Journals submission validation
Diagnose Manual journals submission	The check verifies that the manual journals belonging to the entity on which the diagnostics were run have been submitted. - Do not run: the check is not performed. - Blocking: the check is performed and the non-submitted manual journals are reported with blocking severity. - Non-blocking: the check is performed and the non-submitted manual journals are marked as being of non-blocking severity. - Only Diagnostic: the check is only performed if explicitly requested by running customisable diagnostics. When diagnostics are run automatically from the cockpit/other data processing, the check is not performed.
Diagnose Automatic journals submission	The check verifies that the automatic journals belonging to the entity on which the diagnostics were run have been submitted. - Do not run: the check is not performed. - Blocking: the check is performed and the non-submitted automatic journals are reported with blocking severity. - Non-blocking: the check is performed and the non-submitted automatic journals are marked as being of non-blocking severity. - Only Diagnostic: the check is only performed if explicitly requested by running customisable diagnostics. When diagnostics are run automatically from the cockpit/other data processing, the check is not performed.
Intercompany Cockpit
IC cockpit: Balancing threshold of Compensation reconciliation accounts	Value provisionally set in the generic validation rules. The threshold, if set, is applied during the matching of relationships present in the IC Cockpit. Specifically, it will be used by the check that verifies the balancing of amounts linked to variation/detail types used on several matching rules.

Specific rules

Field	Description
Equality control groups	Opens a page to define specific rules to be applied to balancing control groups with equality operators.
“Other” control group	Opens a page to define specific rules to be applied to “other” control groups, or balancing control groups with non-equality equality operators. The rules are not applied to control groups with coherence operators.
Accounts	Opens a page to define specific control rules for accounts.

For further details on validation rules for diagnostic data, seeSpecific Rules