Cross Validation Rules

Cross-validation rules (CVRs) are used within the Harvard General Ledger (GL) to prevent the creation of invalid GL accounts. Each cross-validation rule specifies ranges of values that are permissible to use together, and ranges that are not permissible to use together. For example, a rule might specify that only Org values 23200 through 24499 may be used with Tub 275 (SPH).

Rules are defined system wide and apply to all system users. Whenever any component of the Oracle Applications attempts to create a new 33-digit value (a combination of segment values that has not previously been used), Oracle checks all the cross-validation rules to ensure that the combination is valid.

If the combination fails to pass any rule, the error message associated with that rule is presented. The transaction in process is not allowed to continue until it has a valid 33-digit combination. When there is a valid reason for an exception to the CVR, the rules may be relaxed. Example:

An award is issued to Harvard University and both Harvard Medical School (HMS) and School of Engineering and Applied Sciences (SEAS) will work on a portion of the project. One school "owns" the award, in this case it is HMS. The Main account is created with an HMS Tub and Org as follows: M 520-46530-112332-256437-0001-65007 (Root of HMS PI). An account is also requested for the SEAS portion as a Part-of account: P 325-28630-112332-256437-0002-45200 (Root of SEAS PI)

Please note that in this example, the owning Tub (HMS) must notify the school (SEAS) local chart administrator to "relax" their CVRs.

You can locate the local chart administrator by selecting the Organization tab from the GMAS homepage. Enter the school org value in the search field (of the part of account) and from there, the local chart administrator email address will populate. The Local chart administrator will request cross validation rules to be relaxed by Client Services/HUIT.