Validation Log

Definition

Hierarchical list you can use to analyze the results of the validation task.

Structure

Header

The header consists of the following elements:

  • Permanent parameters

  • Whether the task was run in test mode or update mode

  • Task settings

  • Method settings, if they apply equally to all organizational units

Body

The body consists of a hierarchical list that has the following structure for each validated consolidation unit or consolidation group:

  • Consolidation unit or consolidation group with the number of errors and warnings, and the overall result of the validation task

    • Validation rule and the hierarchy level on which the rule was executed within the validation rule hierarchy, and the number of errors and warnings issued

      • Details about the check

      • Messages issued by the system

    • Other messages regarding the consolidation unit or the consolidation group

The number of errors and warnings is aggregated over the entire check hierarchy. The system also adds the number of errors and warnings issued by the validation of additional financial data, and displays the total at the top log level of the consolidation unit or consolidation group.

Relationship Between Messages and Validation Result

The check results for single formulas defined as validation rules in validation methods do not necessarily have an immediate effect on the overall validation result in the log. More important is whether a message was assigned to a single check result and whether it was output because of the achieved result. The following table illustrates the relationship between the types of messages, the number of messages issued, and the validation result disclosed in the log.

Number of Warnings

Number of Errors

Result

0

0

OK (green)

> 0

0

OK with warnings (yellow)

Any number

> 0

Errors (red)

Recommendation Recommendation

When executing a validation, you can have the log show only the check results in which errors occurred and, therefore, need to be examined more closely. To do this, select Checks with Errors Only on the selection screen. Doing this can often greatly accelerate the execution of the validation task. This depends on the volume of data being processed and the number of messages incurred.

End of the recommendation.
Details of Validation Checks

The detailed information of validation checks portrays the formulas – which describe the conditions that are checked – as a hierarchical list, and also shows the values used in those formulas in each individual check. This list is structured as follows:

  • Function or operator with the result of the check

    • Parameter name and value

      Example Example

      You want to check whether the sales revenue shown in segment reporting equals the revenue recorded without the segment information. The following figure shows how the validation rule VAL_PER(Segmented Sales) = VAL_PER(Non-segmented Sales) is portrayed in the log.

      The reader of the log interprets this as follows: The two parameters (each of which is a “period value” function) are linked by the Equal-to operator (“=”). Which value the two operand functions contain depends on which parameter is used for calling them. Here the call parameter is a selection condition that selects the segmented sales in one case and the non-segmented sales in the other case. Since the two function values differ, the rule returns the value “false”.

      End of the example.

The portrayal as a hierarchy is useful because the parameters of the operators and functions can themselves be operators or functions, as shown in the example. The log then visually portrays the hierarchical nesting of the rule.

Note Note

Technically, the portrayal of validation rule hierarchies is limited to nine levels. Therefore, in some cases, rules with very complex formulas might not be completely displayed in the log. However, the result of the check is always displayed correctly.

End of the note.