Example of a Matrix Validation
The data records are checked in their entirety with the matrix validation. Two rules are used in this example. A check is made as to whether the plan data for 1998 does not deviate by more than 20% from the actual data for 1997. There is no prerequisite in this example.
The formulas are written here with the technical names of the expert mode. For more information on creating formulas in the expert mode or on the formula builder, see Customizing.
Rule ACT97:
CF001-PLACTI = ‘0’
"Actual" AND CF001-YEARB = ‘1997’ "Year""Plan/Actual indicator actual and year 1997"
Rule PLAN98:
CF001-PLACTI = ‘1’
"Plan" AND CF001-YEARB = ‘1998’ AND CF001-VERSIO = ‘001’ " Version 001 ""Plan / Actual indicator plan and year 1998 and version 001"
Check:
SUM ( CF001-REVEN) WHERE ACT97
"Application of the rule ACT97"
GROUP_BY CF001-PERIO CF001-DIVSN
<= 1.20 * SUM ( CF001-REVEN) WHERE PLAN98
"Application of the rule PLAN98"
GROUP_BY CF001-PERIO CF001-DIVSN
AND
SUM ( CF001-REVEN) WHERE ACT97
GROUP_BY CF001-PERIO CF001-DIVSN
>
= 0.8 * SUM ( CF001-REVEN) WHERE PLAN98GROUP_BY CF001-PERIO CF001-DIVSN
The entire quantity of the records is limited by the where condition to the actual values 1997 or to the plan values 1998. The group statement ensures that the revenues are summed and the variance checked for each combination of division and period. The group statement must be identical on both sides of the comparison operator. As soon as the check for one combination of division and period is not fulfilled, the entire check becomes invalid.
No data is read for the validation. The data that the validation is supposed to check must be selected using the sender program or the data entry layout. In this case, you must ensure that both the actual values for 1997 and the plan data for 1998 are available for the validation.