Costing Cross-Validation Rules

Cross-validation rules are used to validate payroll cost account combinations during the costing process.

If the rule determines the selected values not to be a valid combination, the combination isn't created and doesn't go to general ledger. A cross-validation rule includes both a condition filter and a validation filter. If the condition filter, which describes the event when the application evaluates the rule, is satisfied, then the validation filter is applied. If the condition filter isn't satisfied, then the validation filter isn't applied. The validation filter condition must also be satisfied before the combination is created and is sent to general ledger.

Define the cross-validation rules for the payroll costing key flexfield segments using HCM Data Loader. Remember to set the end date or disable the existing cost account combinations that violates the new cross-validation rule. Otherwise, the new rule is not applied.

Creating Cross-Validation Rules

Decide what combinations of values within the payroll costing key flexfield you want to allow or not allow and use these qualifiers to build the condition filters.

This table provides qualifiers you can use to create cross-validation rule condition filters.

Operator

Description

STARTSWITH

Starts with

ENDSWITH

Ends with

=

Equals

<>

Doesn't equal

<

Less than

>

Greater than

<=

Less than or equal to

=

Greater than or equal to

BETWEEN (Using '-' to separate two values)

Between

NOTBETWEEN

Not Between

CONTAINS

Contains

DOESNOTCONTAIN

Doesn't contain

ISBLANK

Is blank

ISNOTBLANK

Isn't blank

For example, you determine the company named Operations isn't allowed to use a specific cost center named Marketing and you define a cross-validation rule to prevent this combination. When the rule evaluates the company condition filter and determines it's equal to Operations, the rule then evaluates the cost center validation filter. If the validation filter determines the cost center is equal to Marketing, the rule prevents this combination from being created. This rule doesn't affect combinations other than the Operations company with the Marketing cost center.

Note: The OR operator is used when you have multiple values in the filter, such as Company = Operations OR Company = Production.Use the AND operator when you have multiple conditions to filter before applying the validation filter, such as Company = Operation AND Albany = Business Unit.