Cross Validation Rule in Oracle Fusion General Ledger

There are two ways to create a Cross Validation Rule (CVR):

1. Manual Creation (as demonstrated in this blog)

2. Spreadsheet Upload (using ADFdi / FBDI methods)

Cross Validation Rules operate at the account combination level, whereas Security Rules function at the individual segment value level.

This highlights a fundamental distinction between Cross Validation Rules and Segment Security configuration in Oracle Fusion.

Setup Cross-Validation Rule:

Manage Cross Validation Rules:

Select your COA > Search and click Create

In the Condition Filter, select the Asset natural account range

In the Validation Filter, restrict the allowed Cost Center to (00 – None / General)

This ensures that Asset accounts can only be used with Cost Center 00

Error Message: In the Error Message field, define a clear and user-friendly validation message that will be displayed when an invalid Cost Center is selected in combination with an Asset account.

Click Save and Done.

Cross Validation Rules are applied during the entry of account combinations.

If Dynamic Combination Creation is enabled, the system validates the rules before allowing the combination to be created and saved.

Test Rule:

Home > General Accounting > Journals > Create Journal

Create a journal line using:

• Asset Account
• Cost Center 00

The journal should post successfully.

Check Status: Posted

Then attempt:

• Asset Account
• Different Cost Center

The system should trigger the defined error message and prevent saving the combination.

Important Implementation Note:

• Cross Validation Rules should be configured before users begin creating account combinations.
• If combinations are already in place, applying CVRs later will not automatically remove existing invalid combinations.

Therefore, it is essential to ensure proper Chart of Accounts (COA) design and validation setup during the initial design and implementation phase.