Skip to main content
insightsoftware Documentation insightsoftware Documentation
{%article.title%}
Published:
Was this article helpful?
0 out of 0 found this helpful

Check Rule Results

Table of Contents

1 Calculate Check Rule Results

Calculating the check rule result for a company or group requires the user to be authorized to modify the data of the company or group.

The test rule results can be calculated in the company financial statements + monitor (Action -Processing + 'Calculating the test rule result'), in the group companies + monitor (within the final processing) and also in the applications 'PRFERG' / 'PRFERGK'.

The two German sentences in the image above are translated as follows:

in Monitor results can be generated for all companies in one step

In Application, Check Rule Results, Only For Each company

An audit result is calculated from the check rules for each company, period, and fact. The overall result is written as a data record in the Processing control (VERARB/KVERARB).

If, when using accounts in the check rules, the associated chart of accounts is not valid for the fact or company being checked, a specific message is set for the check rule. However, this then has no influence on the overall result of the audit. (The check rule is considered non-existent.)

Since positions and accounts might occur mixed in a check rule, only the S/H indicator is taken into account for the sign determination of a value, since for the sign determination in the report the Bil/GuV indicator of the positions is always used, which is not known or not unique when stating individual accounts in the check rule. In addition, there may be misunderstandings in a comparison with a report with position structure, in which the top position always determines the Bil/Income statement indicator of the underlying positions.

The test result for a single check rule is determined per currency (depending on the WUM switch in FAC). For the overall result, only one set of data is written into the Processing control, which is only fulfilled if the check rules for all the currencies checked were free of errors.

The company financial statement or group financial statement overview for test rule results (PRFERG/PRFERGK) contains a delete function. The "delete of test rule results" action always records all results of the individual or group financial statements deleted as if the check rules had never been calculated. However, the processing control record (VERARB/KVERARB) is not deleted, but instead is provided with the KON1894W message (test rule result not current), which leads to the state 'yellow' in the individual or group financial statement monitor.

For locked individual or group financial statements, no new check rule results can be calculated (to prevent the check rule status from "green" to "red" if new check rules have been defined or because data has changed in a comparison period or data type while the data of the current closing is unchanged).

1.1 Actions and Branching Possibilities

Branch in 'PRFDEF' or 'PRFPOS': By double-clicking or by using the context menu (right mouse button), the system will branch into either the 'PRFDEF' or 'PRFPOS' application.

Branching in Verifier rule analysis: via the context menu (right mouse button) or by double-clicking in the column 'check rule status', you can branch into the Verification rule result analysis. The 'check rule analysis' application cannot be called directly otherwise the necessary parameters for the analysis are not available. For next explanations, see the section 3 Check Rule Result Analysis

Delete of check rule results: The context menu (right mouse button) allows you to launch the delete for one or all check rule results.

Manual release of faulty check rules: There is the option to manually release failed check rule results, i.e. to put them in the state "fulfilled". This is particularly helpful if there are justified exceptions when fulfilling a check rule, e.g. in the case of a company’s carry-forward reconciliation that is new to the group companies and therefore does not have prior period values. The manual release is issued by a correspondingly named action in the context menu of the verification rule results overviews (PRFERG and PRFERGK). All selected check rules will be released. There is also a feature to cancel a manual release. By re-calculating the check rule results, the manual release is overwritten with the real state. The state "manual release" is retained if the calculation confirms the values for the left and right sides of the check rule as set out in the test rule result. [The corresponding menu IDs PRFERGREL and PRFERGREV can be authorized separately. By default, the authorization for the user groups IDLADMIN and IDLKON is available.]

1.2 State Display 'Check Rule Result' in the Single and Group Monitor

The 'Test rule result' column displays the overall result of the test across all rules of a company on the company financial statements + monitor/group monitor per company. If there are both hard and soft check rules, the monitor applications (EA, KTKGES) display two columns for the test rule results. Each column itself indicates whether the respective check rules are all fulfilled ([green]) or not ([red]) or whether one or all check rules have been manually released ([hand]). The soft check rule state has no effect on the overall status of a company as displayed on the front. The state [amber] indicates that report data has changed and the test rule result needs to be recalculated.

Double-clicking on a checklist status branches into the check rule result overview (PRFERG or PRFERGK), where the check rule class is passed as a parameter, so that only the results of the hard or soft check rules are displayed. When the application PRFERG or PRFERGK is called directly, all results are shown, without limitation on test rule class.

The statuses displayed in the monitor applications are derived from the data of the Processing control (VERARB or KVERARB), whereby there are two check point IDs 'PRFERG-H' and 'PRFERG-S' for the check rules.

Status '-':
If there are no applicable check rules for a company or group, the state displayed in the monitors is set to [-]. In the test rule results display (PRFERG or PRFERGK), results are no longer displayed. Reasons for non-applicability are e.g. the check rule is excluded by an audit rule group or the check rule only references account or controlling plans that are not assigned to the respective fact or company or the check rule is invalid or has no position in the current period.
Status 'green':
All predictable check rules of the company are fulfilled.
Status 'amber':
For the existing check rules the data has changed, the check rule result has to be calculated again (KON1894W test rule results not up to date - data has changed). The state turns yellow with each data change.
Status 'rot':
At least one of the defined check rules is not fulfilled.
Status 'Hand':
This is a manually released check rule.

1.3 Comments on Check Rule Results (PRFERG/PRFERGK)

Test rule results can be annotated with comments, e.g. for documenting a state. The "Edit comment" action is available for this in the test rule results overviews (PRFERG and PRFERGK). As with the report data, these texts are not possible in different languages at the same time.

As in other overviews, the presence of a comment is visualized by a column ("K"/"Comment") displaying a book symbol. Double-clicking on this column branches into the comment display. Please note that these texts for machine-generated data (comment) do not remain unchanged when the machine application is repeated, but must be newly recorded.

When regenerating retest rule results, the previous check rule results are first deleted. This also deletes the associated comments. They are therefore no longer present, even if the test rule result has not changed.

When using individual authorization groups without reference to the standard IDL authorization groups, it should be noted that changing comments requires the change authorization for the respective overview application.

2 Overview of Check Rule Result (PRFERG/PRFERGK)

The test rule overview for a company (PRFERG) or a group (PRFERGK) shows the results of the individual check rules. The overview can be used to select between the tree and the list view. To display in nested/clustered tree structure, the check rules must be assigned to the rule groups.

If the calculation of the check rule results has been initiated once before, the current state of the check rule results appears in the bottom line. If only the results of individual check rules are recalculated, it is not possible to assign an overall status for all check rules. Therefore, in this case the state will be labeled with the message "Test rule results not up-to-date - data has changed" (EA status display [yellow]).

3 Check Rule Result Analysis (PRFERGANA)

This overview is used to analyze the test rule results. This overview cannot be called up directly, but only as a line action from the Verification rule results overview (PRFERG or PRFERGK). The display is always only for one test rule result in each case.

All individual records that have contributed to the calculation of the values for the left and right sides of the check rule are displayed. The parameters for the previous period and the type of comparison data are also evaluated, and it is therefore necessary to ensure that they are entered correctly. The display is in a three-level tree structure:

  • 1. Page (left/right)
  • 2. Checking rule position
  • 3. Single data line

Test rule result analysis always shows the data on accounts for statistical quantities as well as calculated key figures without debit/credit indicator. This prevents apparent differences due to different debit/credit indicators.

If a check rule on both sides of the rule specifies the value type 'S+B' (balances + postings), then balances and postings are shown separately and compared in the "Test rule result analysis overview" (PRFERGANA). This makes it easier to analyze whether any existing difference originates from the balances or from the postings. However, the totals from balances and postings will continue to be compared for the test rule result.

The nodes on the left and right sides are set off in color from other lines. The key business unit, document number and IC-company are additionally displayed. In addition to the keys of the data rows, the data source is also defined in each data row by the associated overview short word (e.g. 'KTOSAL', 'BOOK', 'SPIBEW'). The values (in country (for company financial statement only), group and parallel currency) are netted using the tree structure.

If the data from the previous period and/or comparative data type have been checked, they are marked "X’ in the columns on the right. If a check rule contains accounts that are no longer valid in the preceding period, these are taken into account when determining the test rule result, and presented correctly in the analysis overview.

When calculating the check rule results, all extensions in the check rule definitions are evaluated accordingly. Especially with the information "check rule per ..." the result is calculated per object or present object combination. If an error is detected for an object, the state of the entire check rule failed. The display of a check rule in the test rule result analysis (both in individual and group financial statement) with information for "check rule per ..." is sorted at the top level according to the respective objects. Only below this is the data divided by left and right sides, etc.

Displaying the data source is enabled only for captured amounts. If the account/transaction was not entered at all in the period and fact to be audited, a non-collapsible total row of EUR 0.00 appears in the overview.

In addition to the display of the data source, the source group (for KONBUCH) and source company (for EA processes: Development transactions, account balances).

For further analysis, you can view the detail view (right-hand mouse button view or double-click on column of data source or amounts). Views are limited to check rule restrictions. The detailed view for BOOK/CONBOOK is limited to the book record number.
Published:

Check Rule Results

Table of Contents

1 Calculate Check Rule Results

Calculating the check rule result for a company or group requires the user to be authorized to modify the data of the company or group.

The test rule results can be calculated in the company financial statements + monitor (Action -Processing + 'Calculating the test rule result'), in the group companies + monitor (within the final processing) and also in the applications 'PRFERG' / 'PRFERGK'.

The two German sentences in the image above are translated as follows:

in Monitor results can be generated for all companies in one step

In Application, Check Rule Results, Only For Each company

An audit result is calculated from the check rules for each company, period, and fact. The overall result is written as a data record in the Processing control (VERARB/KVERARB).

If, when using accounts in the check rules, the associated chart of accounts is not valid for the fact or company being checked, a specific message is set for the check rule. However, this then has no influence on the overall result of the audit. (The check rule is considered non-existent.)

Since positions and accounts might occur mixed in a check rule, only the S/H indicator is taken into account for the sign determination of a value, since for the sign determination in the report the Bil/GuV indicator of the positions is always used, which is not known or not unique when stating individual accounts in the check rule. In addition, there may be misunderstandings in a comparison with a report with position structure, in which the top position always determines the Bil/Income statement indicator of the underlying positions.

The test result for a single check rule is determined per currency (depending on the WUM switch in FAC). For the overall result, only one set of data is written into the Processing control, which is only fulfilled if the check rules for all the currencies checked were free of errors.

The company financial statement or group financial statement overview for test rule results (PRFERG/PRFERGK) contains a delete function. The "delete of test rule results" action always records all results of the individual or group financial statements deleted as if the check rules had never been calculated. However, the processing control record (VERARB/KVERARB) is not deleted, but instead is provided with the KON1894W message (test rule result not current), which leads to the state 'yellow' in the individual or group financial statement monitor.

For locked individual or group financial statements, no new check rule results can be calculated (to prevent the check rule status from "green" to "red" if new check rules have been defined or because data has changed in a comparison period or data type while the data of the current closing is unchanged).

1.1 Actions and Branching Possibilities

Branch in 'PRFDEF' or 'PRFPOS': By double-clicking or by using the context menu (right mouse button), the system will branch into either the 'PRFDEF' or 'PRFPOS' application.

Branching in Verifier rule analysis: via the context menu (right mouse button) or by double-clicking in the column 'check rule status', you can branch into the Verification rule result analysis. The 'check rule analysis' application cannot be called directly otherwise the necessary parameters for the analysis are not available. For next explanations, see the section 3 Check Rule Result Analysis

Delete of check rule results: The context menu (right mouse button) allows you to launch the delete for one or all check rule results.

Manual release of faulty check rules: There is the option to manually release failed check rule results, i.e. to put them in the state "fulfilled". This is particularly helpful if there are justified exceptions when fulfilling a check rule, e.g. in the case of a company’s carry-forward reconciliation that is new to the group companies and therefore does not have prior period values. The manual release is issued by a correspondingly named action in the context menu of the verification rule results overviews (PRFERG and PRFERGK). All selected check rules will be released. There is also a feature to cancel a manual release. By re-calculating the check rule results, the manual release is overwritten with the real state. The state "manual release" is retained if the calculation confirms the values for the left and right sides of the check rule as set out in the test rule result. [The corresponding menu IDs PRFERGREL and PRFERGREV can be authorized separately. By default, the authorization for the user groups IDLADMIN and IDLKON is available.]

1.2 State Display 'Check Rule Result' in the Single and Group Monitor

The 'Test rule result' column displays the overall result of the test across all rules of a company on the company financial statements + monitor/group monitor per company. If there are both hard and soft check rules, the monitor applications (EA, KTKGES) display two columns for the test rule results. Each column itself indicates whether the respective check rules are all fulfilled ([green]) or not ([red]) or whether one or all check rules have been manually released ([hand]). The soft check rule state has no effect on the overall status of a company as displayed on the front. The state [amber] indicates that report data has changed and the test rule result needs to be recalculated.

Double-clicking on a checklist status branches into the check rule result overview (PRFERG or PRFERGK), where the check rule class is passed as a parameter, so that only the results of the hard or soft check rules are displayed. When the application PRFERG or PRFERGK is called directly, all results are shown, without limitation on test rule class.

The statuses displayed in the monitor applications are derived from the data of the Processing control (VERARB or KVERARB), whereby there are two check point IDs 'PRFERG-H' and 'PRFERG-S' for the check rules.

Status '-':
If there are no applicable check rules for a company or group, the state displayed in the monitors is set to [-]. In the test rule results display (PRFERG or PRFERGK), results are no longer displayed. Reasons for non-applicability are e.g. the check rule is excluded by an audit rule group or the check rule only references account or controlling plans that are not assigned to the respective fact or company or the check rule is invalid or has no position in the current period.
Status 'green':
All predictable check rules of the company are fulfilled.
Status 'amber':
For the existing check rules the data has changed, the check rule result has to be calculated again (KON1894W test rule results not up to date - data has changed). The state turns yellow with each data change.
Status 'rot':
At least one of the defined check rules is not fulfilled.
Status 'Hand':
This is a manually released check rule.

1.3 Comments on Check Rule Results (PRFERG/PRFERGK)

Test rule results can be annotated with comments, e.g. for documenting a state. The "Edit comment" action is available for this in the test rule results overviews (PRFERG and PRFERGK). As with the report data, these texts are not possible in different languages at the same time.

As in other overviews, the presence of a comment is visualized by a column ("K"/"Comment") displaying a book symbol. Double-clicking on this column branches into the comment display. Please note that these texts for machine-generated data (comment) do not remain unchanged when the machine application is repeated, but must be newly recorded.

When regenerating retest rule results, the previous check rule results are first deleted. This also deletes the associated comments. They are therefore no longer present, even if the test rule result has not changed.

When using individual authorization groups without reference to the standard IDL authorization groups, it should be noted that changing comments requires the change authorization for the respective overview application.

2 Overview of Check Rule Result (PRFERG/PRFERGK)

The test rule overview for a company (PRFERG) or a group (PRFERGK) shows the results of the individual check rules. The overview can be used to select between the tree and the list view. To display in nested/clustered tree structure, the check rules must be assigned to the rule groups.

If the calculation of the check rule results has been initiated once before, the current state of the check rule results appears in the bottom line. If only the results of individual check rules are recalculated, it is not possible to assign an overall status for all check rules. Therefore, in this case the state will be labeled with the message "Test rule results not up-to-date - data has changed" (EA status display [yellow]).

3 Check Rule Result Analysis (PRFERGANA)

This overview is used to analyze the test rule results. This overview cannot be called up directly, but only as a line action from the Verification rule results overview (PRFERG or PRFERGK). The display is always only for one test rule result in each case.

All individual records that have contributed to the calculation of the values for the left and right sides of the check rule are displayed. The parameters for the previous period and the type of comparison data are also evaluated, and it is therefore necessary to ensure that they are entered correctly. The display is in a three-level tree structure:

  • 1. Page (left/right)
  • 2. Checking rule position
  • 3. Single data line

Test rule result analysis always shows the data on accounts for statistical quantities as well as calculated key figures without debit/credit indicator. This prevents apparent differences due to different debit/credit indicators.

If a check rule on both sides of the rule specifies the value type 'S+B' (balances + postings), then balances and postings are shown separately and compared in the "Test rule result analysis overview" (PRFERGANA). This makes it easier to analyze whether any existing difference originates from the balances or from the postings. However, the totals from balances and postings will continue to be compared for the test rule result.

The nodes on the left and right sides are set off in color from other lines. The key business unit, document number and IC-company are additionally displayed. In addition to the keys of the data rows, the data source is also defined in each data row by the associated overview short word (e.g. 'KTOSAL', 'BOOK', 'SPIBEW'). The values (in country (for company financial statement only), group and parallel currency) are netted using the tree structure.

If the data from the previous period and/or comparative data type have been checked, they are marked "X’ in the columns on the right. If a check rule contains accounts that are no longer valid in the preceding period, these are taken into account when determining the test rule result, and presented correctly in the analysis overview.

When calculating the check rule results, all extensions in the check rule definitions are evaluated accordingly. Especially with the information "check rule per ..." the result is calculated per object or present object combination. If an error is detected for an object, the state of the entire check rule failed. The display of a check rule in the test rule result analysis (both in individual and group financial statement) with information for "check rule per ..." is sorted at the top level according to the respective objects. Only below this is the data divided by left and right sides, etc.

Displaying the data source is enabled only for captured amounts. If the account/transaction was not entered at all in the period and fact to be audited, a non-collapsible total row of EUR 0.00 appears in the overview.

In addition to the display of the data source, the source group (for KONBUCH) and source company (for EA processes: Development transactions, account balances).

For further analysis, you can view the detail view (right-hand mouse button view or double-click on column of data source or amounts). Views are limited to check rule restrictions. The detailed view for BOOK/CONBOOK is limited to the book record number.
For an optimal Community experience, Please view on Desktop
Powered by Zendesk