CROSS VALIDATION RULES

CROSS VALIDATION RULESBusiness Case:

In ERP, some of the GL accounts or code combinations ie., segments are not be used, because it may have some reversal effect on the books of accounts. The concept of ERP is with the frame work of Sub-Ledger and General Ledger. So sub-ledger related GL accounts or code combinations should not be used in irrelevant areas of operations.

In Oracle EBS R12 such concept is called Cross-Validation Rule, which validates on the Accounting Flex filed code combinations in global. This will restrict the user in selection of code combinations and provides custom error message.Note: Cross validation rule will not have any impact on the Code Combination which are already used. Only it works on the new Code Combination where no transaction has been effected.Pre-Requisites:a) Clear Define COA

b) Determine of account combination restriction

Define of Cross Validation Rule:Define of CVR must be with valid code combinations, by defining the rule. Low and high value is used, in-order to allow access and restrict of code combinations. Each of the rule can contain include or exclude. Include contains all the values which are valid combinations and Exclude contains all the values of invalid combinations.Navigation: Oracle General Ledger >> Setup >> Financials >> Flex Fileds >> Key >> Rules

For Example

CompanyDepartmentNatural AccountDivisionFuture1

1- Company 1000 Common10000 - ABC0000 Divison1000-Common

2- Company 2001 Finance20000 - XYZ0001 Divison1

002 HR30000 - YYY0002 Divison1

Example 1:

Suppose the Natural Account 20000 to 30000 should not to be used with Department 0001 Department across the modules, the following setup to be made

IncludeLOW VALUEHIGH VALUE

Company0102

Department0000002

Natural Account1000040000

Division000000002

Future000000

ExcludeLOW VALUEHIGH VALUE

Company0102

Department001001

Natural Account2000030000

Division000000002

Future000000

The above will restrict the user who selects the department 001 and the account values ranges from 2000 to 3000.Example 2:

Suppose the Natural Account 25000 to 29000 is to be used with Department 0002 Department across the modules, the following setup to be made

IncludeLOW VALUEHIGH VALUE

Company0102

Department0000002

Natural Account1000040000

Division000000002

Future000000

Exclude

LOW VALUEHIGH VALUE

Company0102

Department000001

Natural Account2500029000

Division000000002

Future000000

The above will restrict the User in selecting in the department 000 and 001 & the account range from 2500 to 3000. i.e, only Department 002 can access only 25000 to 29000

Example 3:

Suppose the Company 01, should be accessed only Department 001 and Department 0001 should not allow to access Natural Account such as 25123, 28456, 34567 the following setup to be madeIncludeLOW VALUEHIGH VALUE

Company0102

Department000002

Natural Account1000040000

Division000000002

Future000000

Exclude

LOW VALUEHIGH VALUE

Company0101

Department000000

Natural Account1000040000

Division000000002

Future000000

The above only 01 company doesnt have right to access the department 000. ExcludeLOW VALUEHIGH VALUE

Company0101

Department002002

Natural Account1000040000

Division000000002

Future000000

The above only 01 company doesnt have right to access the department 002.ExcludeLOW VALUEHIGH VALUE

Company0101

Department001001

Natural Account2845628456

Division000000002

Future000000

Company 01, Department 001 will not have access to 28456ExcludeLOW VALUEHIGH VALUE

Company0101

Department001001

Natural Account2845628456

Division000000002

Future000000

Company 01, Department 001 will not have access to 28456ExcludeLOW VALUEHIGH VALUE

Company0101

Department001001

Natural Account3456734567

Division000000002

Future000000

Company 01, Department 001 will not have access to 34567

Note:

Limit of each rule to be only 2 segments.

Start each rule with the include and exclude the invalid account combination

Only to new account combination, CVR Works ie., no transactions should have been done for the same