Wednesday, July 15, 2020

Cross Validation Rules in Fusion/Cloud

Cross validation Rules(CVR)

Cross Validation Rules are used to restrict the combination between the segments of a particular Chart of Accounts

You can use cross-validation rules to determine the valid account combinations that can be dynamically created as users enter transactions or journal entries. Once enabled, a cross-validation rule determines whether a selected value for a particular segment of an account combination can be combined with specific values in other segments to form a new account combination.

Use the Create Cross Validation Rules in Spreadsheet task to quickly enter large volumes of rules during implementation. Use the Manage Cross-Validation Rules task to add a one-off rule or to edit existing rules

Existing Account Combinations

If account combinations already exist that violate newly enabled cross-validation rules, those account combinations continue to be valid. Before disabling existing account combinations that violate your rules and that you no longer use, move the balances in those accounts to the correct accounts. Then disable the account combinations manually to prevent further posting. Best practice is to define and enable cross-validation rules before: account combinations are created, transactions or journal entries are imported or entered, balances are loaded.

Setups

·        Create Cross Validation Rules

·        Deploy Accounting Flexfield

Rule: Dept 2000 with Company 1000 is invalid

Task: Manage Cross-Validation Rules -->Go to Task

Select Chart of Accounts --> Click +

Save and Close

Points to consider

Once we created CVR against Chart of Accounts, system will update the Flexfield status to “Edited”. We have to go and submit Accounting Flexfield to Deployment (Chart of Accounts Structure).

Go to Chart of Account Structures

Task: Manage Chart of Accounts Structure àGo to Task icon à Key Flexfield Name: Accounting –click Search

Reason: We created Cross Validation Rules against one of Chart of Accounts Structure which is part of this Accounting Flexfield

Click on Deploy Flexfield

After deployment if we try to create transaction with dept 2000 with company 1000, system should not allow because of CVR

Once status becomes Deployed, logout of the application and login again

Create Journal Entry

Go to JournalàCreate Journal

Note: This is not only applicable to GL, but also applicable to all sub ledger which are using this COA
Check if the rule is working

No comments:

Post a Comment

JS

RC