Manage Data Validation Tasks
Application component: Validation Engine Framework
App type: Transactional
Description:  With this app, you can validate the reported data in local currency (or in transaction currency and tolerance currency, and quantity-type data as you specified in the relevant validation rules) for your specified fiscal period and consolidation units. Also, for each consolidation unit, you can check the validation result that is broken down into the data sets verified against each validation rule, that is, if the data passed or failed the validation rule and the failure root causes. 
Key features: This app provides the following key features: Integration with Monitor When performing the Reported Data Validation task for one or more consolidation units in either a test run or an update run in Data Monitor, you are brought to this app, with the validation results displayed in a list, one row for each consolidation unit. Note Only data with the following posting levels are included in this validation task:  Blank: Reported data from universal journal of integrated companies  00: Reported data of individual consolidation units 01: Adjustments to reported data 0C: Reported data with deactivated checks For more information, see Document Types and Posting Levels.  Run New Validation You can launch a new validation run by choosing New Validation and then specify the consolidation units, consolidation version, and fiscal year/period.Note To specify your consolidation units, first select the relevant consolidation group as defined in Manage Group Structure.For information about how standard versions and extension versions are processed in data validation, see Data Validation in Multiple Group Currencies. When the validation completes, the result list then displays the following essential information: Consolidation Unit Period/Year Status: The status of the last completed validation run for the respective consolidation unit. The status can be: Success: The data passed all assigned validation rules, or failed only the validation rules that have control level Warning or Information. It updates the task status to  Task Is Error-Free in data monitor. Failed: The data failed the validation rules that have control level Error. It updates the task status to  Task Has Errors in data monitor. Not Processed: The validation run is not executed yet. Note If a new validation run is launched, it can display one of the following statuses underneath the primary status.  Processing: Your current validation is being processed and will soon return a status that overwrites the above primary status. System Error: Your current validation run fails to complete due to some technical issues. To solve the issue, you may view the job log available in Message column.  Last Run: The time stamp when the system returns the status. Commenting Status: Indicates whether comments exist for the respective validation result. It can be: Commented: The validation result has comments for all rules that require comments. Partially Missing: The validation result has comments for part of the rules that require comments. Missing: The validation result has no comments for any of the rules that require comments. Not Required: The validation result has no rules that require comments.  Note To run validation in simulation mode, you can select the Simulation Run checkbox. In this way, the validation run doesn't consider any blocking status in monitors or update task status there, and the table displays only the test run results. It is equivalent to the Test with Original List feature in the monitors. The figure below is the screen for running new validations and checking overall validation results as described above:      Revalidate You can select one or more validation result rows and run validation for them again. The result list refreshes after the validation completes.  Show Result Analysis For the displayed list of validation results, you can go to the result analysis page that uses data visualization to help you identify interesting areas within your data sets. For more information, see Validation Result Analysis - Unit View and Validation Result Analysis - Group View.  Check Result Details You can choose a validation result row for any consolidation unit and open the detail page. The row layout of the Result Detail table follows the structure of the assigned validation method and rules, that is: Method Rule Group 1 Rule 1 (Basic Rule)  Value 1 of Group-By Field 1   Value 1 of Group-By Field 2   Value 1 of Group-By Field 3  Value  of Group-By Field 3   Value  of Group-By Field 2   Value  of Group-By Field 1  Rule  (Compound Rule)  Basic Rule 1  Basic Rule    Rule Group   Note If transaction currency (TC) amount is used when defining sum-type operands of a validation rule, data is first grouped by TC and then by the grouping fields you specified for the rule. The table contains the following columns:  Result: The result of the last completed validation run at method, rule group, and rule levels. The result is determined as the following:  Level Result    Method  The worst result of all its contained rule groups.Note Only when the method-level result is Failed does the respective validation task show Error status. All other method-level results, Success, Warning, or Information, lead to a Success task status.    Rule Group The worst result of all its contained rules.   Rule Basic Rule   Success: The data meets the conditions defined in the rule expression. Failed: The data doesn't meet the rule expression and the rule has control level Error. Warning: The data doesn't meet the rule expression and the rule has control level Warning. Information: The data doesn't meet the rule expression and the rule has control level Information.  Note If the rule has multiple group-by fields defined, the validation logic only acts on the data aggregated on the lowest group-by level (e.g. 3rd group-by field), therefore, the result refers to that level of data. Based on that, the results of other higher group-by levels (e.g. 2nd and 1st group-by fields) and the rule itself are derived.    Compound Rule Result is determined in two steps: Based on results of basic rules and their relationship defined in the rule expression, an interim result Failed or Success is derived.Note At this stage, basic rules have either Failed or Success result, depending on whether the data meets the rule expression and tolerance. Control levels of these basic rules are not taken into account. Based on control level of the compound rule, the final validation result, Success, Failed, Warning, or Information is determined.   Additionally, the following exceptions may occur in a validation and display in the Result column:  Division by zero when calculating left value, right value, or difference (%). The validation result depends on the rule control level.  No data for all sum-type operands in a basic rule and the no-data processing option of the rule is set to Success with Warning. It leads to a Warning result (or Success result when the basic rule is part of a compound rule), regardless of the control level of the rule.If the no-data processing option is set to Failed or Zero for the rule, the exception won't occur and the control level is taken into account in the validation. For more information, see Create Basic Rules. Exceptions of basic rules are also carried over their compound rules.Note By default, rows with rule-level result Success are hidden. You can choose to display them by using the Result Filter. Comments: Show the number of existing comments. The asterisk symbol (*) indicates the rule is set as Comments required in its definition. Note that the existence of a comment has no effect on the validation result or monitor status.Note Comments can be entered on rule level, not down to any grouping level. Left Value: The value calculated using the left formula in the respective validation rule. It has the same currency as the source data available at runtime, that is, the local currency for reported financial data and group currency for standardized or consolidated data. Comparison Operator: The operator defined in the validation rule to compare left value or right value. It can be equal to, greater than, less than, and so on. Right Value: The value calculated using the left formula in the respective validation rule. It has the same currency as the source data available at runtime, that is, the local currency for reported financial data and the group currency for standardized or consolidated data. Drill Down: It works differently for results of basic rules and compound rules:  For basic rules, it shows the line item-level data for all operands in each formula of the respective rule, so that you can understand the root cause of any failed validation more easily. See the Drill Down part for more information.Note The drill-down capability is only available to data of the lowest grouping level.  For compound rules, it shows the rule expression, that is, which basic rules make up the compound rule and how they are connected.  Difference: The absolute difference between the left value and right value.  Difference (%): Calculated with the formula (Left Value - Right Value)/Left Value.  Tolerance: The amount within which the difference between the left-side and right-side values is ignored and the values of both sides are considered equal. It is defined in basic rules. Additional columns are also available, such as Tolerance (%), Comments, and References. For information about these columns, see Create Basic Rules. By choosing the Switch to Tolerance Currency button, you can change the displayed left values and right values to the currency of tolerance. This is useful if you explicitly specified a different tolerance currency than the source data currency when defining the relevant validation rule.Note When converting values to tolerance currency, the system uses the exchange rate type M (Standard translation at average rate) and the last day of your specified period as the reference date, or uses the current date if the last period day is in the future. You can also export the table to a spreadsheet. The figures below are the validation result examples as described above:  For basic rules:       For compound rule CR001:       Drill Down to Source Data You can check the detailed source data of each basic rule result row by choosing Drill Down ( icon). For each operand in the rule expression, you can drill through to the following levels of data granularity: Account Detail: The calculated data for individual items that are included by the respective operand in the rule. Group Journal: The original accounting documents or group journal entries that have relevant posted data. Example The consolidation unit S2001 has a Success validation result for rule SB00060 in fiscal period 007/2022.You check and find the rule is defined as year-to-date amount posted to financial statement (FS) item 172100 (Gross value of the investments in consolidation units, joint ventures, and associates) should be greater than or equal to that posted to the FS item 172190 (Impairment of the investments in consolidation units, joint ventures, and associates), while partner unit value is not empty.By choosing the Account Detail link under the left formula, which only includes FS item 172100, you find the following data posted to the respective FS items:  Financial Statement Item Partner Unit Amount    0000172100 S3000 220,000.00 USD  By choosing the Group Journal link under the left formula, you are brought to the Display Group Journal Entries - With Reporting Logic app, where the filter criteria are automatically populated according to the rule definition. In our case, the following group journal entry data for consolidation unit S2001, fiscal period 007/2022, and FS item 0000172100 is displayed: Document number Line item Subitem category and subitem Amount in transaction currency Amount in local currency Amount in group currency The FS item 172190 included in the right formula has no data posted for the consolidation unit S2001 in fiscal period 007/2022. Therefore, it shows No Data in the Drill Down window and is treated as having zero amount. 
Business roles: Group Accountant| External Auditor - Group Reporting| General Ledger Accountant - Group Reporting
Consolidation Specialist : 
Is responsible for the Consolidation setting, processing for the FI or other business data from subsidiaries. Generates the legal & management consolidated reports.

External Auditor - Group Reporting : 
Ensures adherence of group data to legal accounting standard and process governance standards.

Group Accountant : 
Executes and monitors group processing tasks, such as data adjustment, and inter-company elimination.

General Ledger Accountant - Group Reporting : 
Ensures adherence of local data to group quality standards.