Define Cross Validation Rules (Required) in R12

Cross Validation Rules determine which combinations of valid segment values are invalid, regardless of the user's responsibility. It is a good idea to use combinations of several simple rules rather than a few "all encompassing" rules. Keep in mind that Cross Validation rules are linked to a flexfield structure; security rules are linked to a responsibility. In this practice, you will define cross validation rules.

Example:

You will implement three rules as a test to the system:

Rule	Purpose
Commission Rule	Prevent the Administration (100) and Finance (150) departments from receiving commission payments (Account 5150)
Balance Sheet Rule	Prevent balance sheet account codes from being used with anything but balance sheet departments (and similarly with P&L account codes and departments)
Revenue Rule	Allow only sales departments (300 to 3ZZ) to be used with revenue account codes (4000 range)

Assumptions

• Replace XX with your terminal number or unique number.

• You must have access to an Oracle Application Vision database or comparable training or test instance at your site on which to complete this practice.

Tasks

Query Your Flexfield Structure

1. Responsibility = XXGeneral Ledger Super User, XXLEDGER

2. Navigate to the Key Rules window

• (N) Setup > Financials > Flexfields > Key > Rules

3. Query your flexfield structure

Define the Commission Rule

4. Define the commission rule

• Rule = XXCVR01

• Description = Account 5150 is not valid with Administration (100) and Finance (150)

• Error Message = XXCVR01 - Account 5150 is not valid with the Administration (100) and Finance (150) departments

• Error Segment = Account

• From = 31-JAN-2001

Include/Exclude	From	To
Include	00.000.0000.00	ZZ.ZZZ.ZZZZ.ZZ
Exclude	00.100.5150.00	ZZ.100.5150.ZZ
Exclude	00.150.5150.00	ZZ.150.5150.ZZ

Define the Balance Sheet Rule

5. Create Rule XXCVR02 for the Balance Sheet Rule. Remember to include a description, error message, identify the segment name, start date, and use the following information.

• Rule = XXCVR02

• Description = Balance sheet accounts and income statement accounts must be used with appropriate departments

• Error Message = XXCVR02 - Balance sheet and income statement accounts must be used with appropriate departments.

• Error Segment Name = Department

• From = 31-JAN-2001

Include/Exclude	From	To
Include	00.000.0000.00	ZZ.ZZZ.ZZZZ.ZZ
Exclude	00.000.4000.00	ZZ.000.9929.ZZ
Exclude	00.000.9941.00	ZZ.000.ZZZZ.ZZ
Exclude	00.001.0000.00	ZZ.ZZZ.3ZZZ.ZZ

Note: 9930 is not being excluded as it will be used with department 000 for the default balancing account.

Define the Revenue Rule

6. Create Rule XXCVR03 for the Revenue Rule. Remember to include a description, error message, identify the segment name, start date, and use the following information.

• Rule = XXCVR03

• Description = Allow only sales departments (300 to 3ZZ) to be used with revenue account codes (4000 range)

• Error Message = XXCVR03 - Only sales departments (300 to 3ZZ) may be used with revenue account codes (4000 range)

• Error Segment Name = Department

• From = 31-JAN-2001

Include/Exclude	From	To
Include	00.000.0000.00	ZZ.ZZZ.ZZZZ.ZZ
Exclude	00.000.4000.00	ZZ.299.4ZZZ.ZZ
Exclude	00.400.4000.00	ZZ.ZZZ.4ZZZ.ZZ

7. Save

8. Close windows until you are back at the Navigator

Note: In 11i10 and prior, it was necessary to re-choose the responsibility to activate the cross validation rule. That is no longer necessary in R12.

Test the Cross Validation Rules

9. Navigate to the Account Combinations window

• (N) Setup > Accounts > Combinations

10. To test your rule, attempt to add accounts according to the following table:

Account	Description
01.100.1110.00	Co 01.Administration.Cash.Default
01.000.4110.00	Co 01.Balance Sheet.Hardware Revenue.Default
01.150.4120.00	Co 01.Finance.Support Revenue.Default
01.310.4130.00	Co 01.Sales & Marketing.Training Revenue.Default

11. Disable your rules