Defining Cross Validation Rules in Fusion General Ledger  

Overview of Cross Validation Rules

In Oracle Fusion General Ledger, cross validation rules are used to determine the account combinations that users can create dynamically when they enter transactions or journal entries. Once enabled, cross validation rule determines whether a selected value for a particular segment of the account combination can be combined with specific values in the other segments to form a new account combination.

If account combinations already exist and violate the newly enabled cross validation rules, these account combinations continue to be valid. Before disabling any existing account combinations that violate cross validation rules and that are no longer in use, we must move the balances in those accounts to the correct accounts. Then disable the account combinations manually to prevent further posting.

We should define and enable cross validation rules before-

• Balances are loaded

• Transactions or journal entries are imported or entered

• Account combinations are created

The standard functionality in Oracle Fusion Application does not provides a central place to enable and disable all CVRs. Let us now understand how Cross Validation Rules work in Fusion Applications with examples.

Companies may have requirements to prevent certain combinations of segment values to be used in their account combinations, for example a particular cost center may not be combined with a specific company value. Once enabled, cross validation rules determine what segment values may be combined with other segment values across the different segments of chart of accounts. Cross validation rules only affect the creation of new account combinations. When creating a new account combination in user interfaces and processes, the values for each Chart of Accounts (COA) segment are cross checked to make sure they do not violate the validation rules.

A cross validation rule is now defined in terms of a condition filter and a validation filter. The condition filter describes the event under which the rule will be evaluated. If the event specified in the condition filter is not applicable, then the rule will not be evaluated even if it is enabled. The validation filter contains the condition that any account combination must satisfy (when the event specified in the condition filter is applicable) before it can be created. To summarize, a cross validation rule is now defined in terms of a condition filter and a validation filter. The rule is evaluated using the following logic-

If condition is satisfied, then perform specified validations.

If a Company has decided that a certain company value (e.g. Operations) cannot use a specific cost center (e.g. Marketing), then we can define the following cross validation rule to validate  accounts accordingly: If Company is equal to 'Operations', then validate that Cost Center is not equal to 'Marketing'.

Setup of Cross Validation Rules in Fusion Applications

While implementation of Fusion General Ledger, set up of CVR is an important step. Cross validation rules should be created at implementation time not after few transactions are entered as undesired account combinations can get created in the interim. Updating and deleting existing rules takes place after the fact but it should not occur very often under normal circumstances.

The cross validation rules user interface (UI) is available from Functional Setup Manager (FSM) and below are the steps to define rules-

1. Navigate to 'Setup and Maintenance’

2. Create or Select an implementation project that includes the task 'Manage Cross-Validation Rules'

3. Click on the Go to Task icon for the task 'Manage Cross-Validation Rules'

4. Select the chart of accounts for which you want to define cross validation rules.

5. Add a cross validation rule by clicking on the green plus sign and enter a Name for the rule, a Condition filter, a Validation filter and an error message to be displayed when the cross validation rule applies. Always enable the cross validation rule once it's defined.

In this example we have successfully created CVR-1 for company Apps2fusion where company 01 can not be combined with cost center 1010 with error message.

Though there is no seeded report to get listing of the existing cross validation rules. However Export to Excel functionality in the Manage Cross-Validation Rules user interface can be used to save in Excel a listing of all of the cross-validation rules (name, description and enabled status) defined for a particular chart of accounts.

Add comment