Viewing Balance Validation Results and Documenting Resolutions

Objectives

After completing this lesson, you will be able to:
  • View a Balance Validation Result.
  • Analyze a Balance Validation Result.

Balance Validation Result View

After running the validation check, Max now has results ready for review. He will use the View Balance Validation Results application to access the validation results.

The list will display the data, indicating if it has passed or failed the validation rules, and show the root causes for any failures. If corrections are made to the data from a failed validation, a revalidation can be run to analyze the new data. In addition, new validations can be run from this view. Running a New Validation will be the same as described in Execute an Individual Validation Run lesson.

A screenshot displaying the results of a Balance Validation run with filtering options for company codes and fiscal periods, showing a mix of Failed, Success, and Success with Warnings outcomes. Each validation result includes details such as the rule group, description, ledger, currency, fiscal year period, log, and result percentage.

On the initial Validation Results display, you’ll see that all Validation Groups that have been executed. Basic data such as Entity, Ledger, Currency (Type), and Fiscal Year Period can also be seen. It will also display the validation result, the log, and the ratio of failed vs total rules that are in the group.

You can filter the results to specific groups that you are interested in using the filter section at the top of the screen.

The overall result statuses can be:

  • Success – the data passed all validation rules in the group or only failed those rules with control level set as Information. Remember that the control level determines a rule fails to pass is acceptable in the validation result. The control level can be set as Error, Warning, or Information
  • Success with Warnings – the data passed all rules with control level Error but failed at least one rule with the Warning level
  • Failed – the data failed at least one rule that has control level Error
  • Technical Error – the validation ran into a technical issue and couldn’t be completed. Check the log for further information

The result also comes with the failed vs total ratio, result percentage and a stacked bar chart which provides insights into the numbers of rule-specific results. For Basic Rules, the results of the lowest group-by fields are counted. For Compound Rules, only the final rule-level results are counted.

In summary, this is a process that will highlight validation rule adherence, flagging any fails and providing a visual representation of the success rate via a stacked bar chart. Let’s see what the process of viewing validation run results may look like in a real scenario.

Balance Validation Result Analysis

Max has seen the overall results for the Balance Validation but he’s curious about finding out more information. He now wants to see more detail as to which rules have passed or failed and the specific data that was analyzed.

Balance Validation Result Header

You can see the validation group detail by choosing the navigation button at the end of the desired line. This will show the rules that have been validated in the executed Validation Rule Group.

A screenshot of a Balance Validation Result header where the result status is Failed. The screenshot includes details like fiscal year period, commenting status as Missing, and the last run on date.

In the Validation Result header area, you can see the parameters that were used to validate the rules in the group as well as the overall result as explained in the previous section. In the Standard default view, rows with rule-level result Success are hidden. You can choose to display them using the Result Filter.

You can see when the last date and time this balance validation instance was executed in the Last Run field. If you Revalidate this instance, this field will be updated with the current date and time that it was executed.

The Commenting Status is also displayed. This is determined by the Comments Required setting of the rules in the group. There are 4 statuses that can be displayed:

  • Commented – The validation result has comments for all rules that require comments
  • Partially Commented – 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

The commenting status does not have any effect on the validation results.

Balance Validation Results Details

The Result Details table breaks down the overall result of a group into rule-level results. The Results are listed in the hierarchy as they placed in the Balance Validation Group.

The screenshot displays detailed results of a balance validation process, including line items, descriptions, results (success, failed, warning), and exceptions. Various metrics such as left and right values, differences, tolerances, and rule categories are shown in a tabular format.

The four possible results that may be displayed are Failed, Warning, Information, and Success. As stated before, Success results are hidden by default but can be made visible in the Result Filter field

The results displayed are determined differently depending on whether it’s a Rule Group, Group Hierarchy Node or a Rule. The following table describes how each result is calculated.

Validation Result Calculation Table

Rule GroupThe worst result of all its contained hierarchy nodes
Group Hierarchy NodeThe worst result of all its contained rules
RuleBasic 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 the control level of Error
  • Warning – The data doesn’t meet the rule expression and the rule has the control level of Warning
  • Information – The data doesn’t meet the rule expression and the rule has the control level of Information

NOTE:

If a rule has multiple group-by fields defined, the validation logic only works on the data gathered at the lowest group level. So, the result relates to that specific level of data. Accordingly, the results of other higher group-by levels and the rule are determined.

Compound Rule

The result is determined in two steps.

  1. Based on the results of the basic rules and their relationship defined in the rule expression, an interim result of Failed or Success is determined.
    • Note: At this stage, basic rules have either Failed or Success result. This depends on if the data meets the rule expression and tolerance or not. Control levels of these basic rules are not considered.
  2. Based on the control level of the compound rule, the final validation result of Success, Failed, Warning, or Information is determined.

Rule Level Result Columns

In a validation rule, defining a sum-type operand uses the Amount in Balance Transaction Currency setting. This means the data is first grouped by the currency then by the grouping fields defined in the rule.

To better understand the rule-level results and provide more information, additional columns are displayed.

Note

The values greater than one million are displayed in short number format with the units shown as an abbreviation, such as M (million) and B (billion). To view the exact values, hover your pointer over the short-form numbers.

  • Exception – This column will be discussed at the end of this lesson
  • Left Value – The value calculated using the left formula in the respective validation rule
  • Operator – The comparison operator defined in the rule to compare the left and right values
  • Right Value – The value calculated using the right formula in the respective validation rule
  • Difference – The absolute difference between the left and right values
  • Difference (%) – The difference percentage calculated with the formula [(Left Value – Right Value)/Left Value]
  • Tolerance – The amount within which the difference between the Left and Right values that is ignored and both sides are considered equal. This is defined in Basic Rules.
  • Tolerance (%) – The tolerance percentage as defined in Basic Rules. In the validation execution, the system compares the calculated Difference (%) with the specified Tolerance (%)
    • If in the rule definition, Tolerance value and Tolerance (%) have an OR relationship, and in a validation, the calculated Difference value doesn’t exceed the Tolerance value, the system skips comparing Difference (%) and Tolerance (%) to avoid a Divided by 0 error as the calculation involved division.
  • Comments – Shows the number of existing comments. Adding comments can further explain the results or can request follow-up activities for the person responsible. If no comments have been added, the column show the Add (+) icon or Missing. Remember, if the comments column states Missing, then the rule definition states that comments are mandatory. Comments can be added at the Rule Group level, but has no effect on the Commenting Status listed.
  • Reference Links – The web links added in the rule definition providing additional information.

By choosing Switch to Tolerance Currency, you can convert the displayed Left and Right values to the currency of tolerance if you have explicitly defined this in the rule. The system uses the M (Standard translation at average rate) Type exchange rate.

Rule Result Details

To drill-down even deeper into the data, for each rule level or group-by field level, you can choose the Details icon at the end of the row.

A screen-shot showing the Balance Validation results for a basic rule. The left side displayed the hierarchy of the rule. The right side shows the result success showing that the data has passed the checks performed in the validation run.

For a Basic Rule or any of the Group-By fields, the detail page displays the amounts of all operands in the rule formula. You can click the amounts on the Left or Right value to display the formula details, the actual amounts, and then choose to navigate to either Account Details or Journal Entry Line Items. The Journal Entry Line Items starts the Display Line Items in the General Ledger application. The user would need to have access to that application to use this link. The Account Details screen displays the amounts aggregated by G/L Account. The filter fields that were used to define the amount are displayed as columns. It’s also possible to navigate to the Display Line Items in the General Ledger application from this screen.

A screen-shot showing the Balance Validation results for a basic rule. The left side displayed the hierarchy of the compound rule CJ003. The right side shows the result failed showing that the data has not passed the checks performed in the validation run. In the details section, we can see that the data successfully met the criteria for the second rule, but failed to pass the first rule.

For a Compound Rule, the detail page displays the Details of the formula displaying the included Basic Rules. Additionally, each Basic Rule is displayed as noted above.

You can export the overall result table or any detail table to a spreadsheet.

Balance Validation Exceptions

As with any process, exception can occur in the Balance Validation run. There are five possible exception that can arise. The following table describes the exception, how it affects the Rule-Level Result, the Reason the exception occurred, and the possible Solution.

ExceptionRule Level ResultReasonSolution
Rule DeactivatedFailedRule was active when being assigned to the Rule Group, but has been subsequently deactivated.Activate the rule or remove the rule from the group structure, then Revalidate
Currency Translation (C/T) FailedFailed, Warning, or Information depending upon control levelA currency was specified for the tolerance or any amount-type operands when defining the rule, which requires currency translation during the validation execution. However, C/T couldn’t be executed, for example due to a missing exchange rate.Check the relevant exchange rate maintenance in the Currency Exchange Rates application. Note that exchange rate type M is used.
Divided by 0Failed, Warning, or Information depending upon control levelIn the rule definition, tolerance percentage was specified, or the rule formulas involve division. When calculating the values of Difference Percentage or the rule formula in the validation, the division is evaluated to be zero.Adjust the rule setting. Remember, the Difference Percentage is calculated with the formula [(Left Value – Right Value)/Left Value].
No DataFailed, Warning, or Information

No data for all sum-type operands of the rule and you’ve selected one of the following no-data processing options in the rule definition.

Process no data as Failed – the actual rule-level result can be Failed, Warning, or Information depending on the control level of the rule.

Process no data as Success with Warning – the rule-level result is Warning (or Success when the basic rule is part of a Compound rule) regardless of the control level of the rule.

Resolve the no-data issue or adjust the rule setting. If the no-data processing option is set to Zero, the exception doesn’t occur and the control level is taken into account in the validation.
Technical ErrorFailedA system error occurs.Revalidate. If the error persists, contact SAP support by reporting an incident on component FI-FI0-VE

Key Takeaways:

  • The Balance Validation Result can convey various statuses such as Success, Success with Warnings, Failed, and Technical Error.
  • The overall Balance Validation Result status indicates whether the data has passed or failed based on the validation rules, and includes indicators for rule-level results and any technical issues that may have occurred during the run.
  • Exceptions can occur during the validation run. Knowing what to look for and how to resolve these exceptions is an essential part of managing your validation processes effectively.
  • It's possible to export the overall result table or any detail table to a spreadsheet for offline analysis or reporting needs.

Analyze Balance Validation Run Results

Balance Validation have been run. These runs could have been individual or scheduled runs. Max now needs to view the data and determine if the validation was successful or has failed. At this point, he only wants to see the status and values that the validation has produced. Once he has reviewed these items, he will analyze the data. If changes are made, Max can revalidate the run group to include the new data. Some rules require comments. Max will enter a comment into one of the rules he is responsible for.

Log in to track your progress & complete quizzes