Documenti di Didattica
Documenti di Professioni
Documenti di Cultura
Give Feedback...
Copyright (c) 2019, Oracle. All rights reserved. Oracle Confidential.
XVAL General Ledger FAQ for Cross Validation Rules (Doc ID 136357.1) To Bottom
Purpose Yes
No
Questions and Answers
How do I enable cross validation?
Document Details
Do Cross Validation rules have any impact if the account has already been created?
Why are my cross validation rules not working?
Type:
FAQ
May I use parent values in cross-validation rules? Status:
PUBLISHED
How are cross validation rules evaluated? Last Major
22-May-2018
Update:
Where is the Cross-Validation Report and Cross-Validation Rules Listing Report located? 22-May-2018
Last Update:
May the Cross-Validation Rules Violation Report Disable Account Code Combinations?
May I define cross validation rules for a set of books/ledger? Related Products
Why are code combinations only validated when they are created ? Oracle General Ledger
How do cross validation rules work with Multiple Organization Access Control (MOAC) in release 12?
Can multiple Cross Validation Rules exist on a single segment? Information Centers
How may I check if a code combination violates cross validation rules ? Information Center: Oracle
General Ledger [1489229.2]
Community Discussions
References
Document References
How are Cross Validation Rules
APPLIES TO: Evaluated? [1012616.102]
Do Cross Validation rules have any impact if the account has already been created?
No, cross validation rules prevent the creation of new account combinations.
They have no impact on accounts that have already been created.
Reference: Note 1078004.6 - How To Setup Security Rules for An Accounting Flexfield Segment?
After turning on the cross validation rules, they are not taking effect and some accounts that should be rejected are still valid.
Possibly the account code combinations were created before your rules were established.
You may have to disable these code combinations, if they are no longer considered valid, via Setup > Account > Combinations
or by running the Cross-Validation Rule Violation Report.
This is the way the system works - Rules are not retroactive. They apply only to new code combinations created after the
rules are defined and enabled.
https://support.oracle.com/epmos/faces/DocumentDisplay?_afrLoop=81817682852967&parent=DOCUMENT&sourceId=134006.1&id=136357.1&_afrWindowMode=0&_adf.ctrl-state=jldvk1c9a_722#ar… 2/6
1/29/2019 Document 136357.1
To pass a rule, a combination must be included in at least one Include element and must not be included in any Exclude
element.
The combination is considered to be included in an element if all of the segment values fall within the low and high range of
that include or exclude element.
The Cross Validation Rules are evaluated alphabetically.
The Exclude elements are looked at first.
Where is the Cross-Validation Report and Cross-Validation Rules Listing Report located?
May the Cross-Validation Rules Violation Report Disable Account Code Combinations?
Yes. The Cross Validation Rule Violation Report allows users to disable existing combinations that violate a cross validation
rule. This is the normal functionality of this report.
Why are code combinations only validated when they are created ?
The main reason is related to the performance for Journal Import, Posting and many other GL or sub-ledger programs. It just
would not be acceptable in most of the cases to validate all the cross-validation rules for all the account code combinations
involved.
So this is the current option: the validation is only performed at creation time and this is not expected to change.
If an account becomes invalid due to a validation rule defined by the users, it should just be disabled (using the Cross-
Validation Rule Violation Report) and the sub-ledgers that are using it should be setup accordingly so that they do not try to
create transactions on incorrect accounts.
GL expects that only enabled and valid accounts are used by the sub-ledgers. This is referred to in the General Ledger User's
Guide: Journal Entry: Importing Journals: About Journal Import Validation: Account Validation:
"Account Validation
Journal Import validates your account code combinations in a number of ways. JournalImport will successfully import your
accounting data if your code combinations meet the following validation requirements:
You allow detail posting to segment combinations.
https://support.oracle.com/epmos/faces/DocumentDisplay?_afrLoop=81817682852967&parent=DOCUMENT&sourceId=134006.1&id=136357.1&_afrWindowMode=0&_adf.ctrl-state=jldvk1c9a_722#ar… 3/6
1/29/2019 Document 136357.1
You have enabled your code combinations for the accounting date you specify.
Your code combinations do not include summary accounts."
Note that since R12, you may define a substitute account for the disabled combinations. In this case the journal import will
replace one by the other and will not cause errors.
How do cross validation rules work with Multiple Organization Access Control (MOAC) in release 12?
Multiple Operating Units may be accessed through a single responsibility by defining a security profile and assigning it to the
responsibility via the 'MO: Security Profile' profile option.
However, within the same responsibility, Balancing Segment Values (BSVs) may not be restricted based on the Operating Unit
(OU) because security rules are assigned to and work at Responsibility level, not at Operating Unit level.
Yes, this is unusual as determining the evaluation order is quite complex and will require the assistance of the FND team to
evaluate a Trace file of the code being called.
Run the Cross Validation Violation Report from System Administrator Responsibility, or use the SQL in Document 134006.1.
Community Discussions
https://support.oracle.com/epmos/faces/DocumentDisplay?_afrLoop=81817682852967&parent=DOCUMENT&sourceId=134006.1&id=136357.1&_afrWindowMode=0&_adf.ctrl-state=jldvk1c9a_722#ar… 4/6
1/29/2019 Document 136357.1
To provide feedback on this note, click on the Rate this document link.
REFERENCES
https://support.oracle.com/epmos/faces/DocumentDisplay?_afrLoop=81817682852967&parent=DOCUMENT&sourceId=134006.1&id=136357.1&_afrWindowMode=0&_adf.ctrl-state=jldvk1c9a_722#ar… 5/6
1/29/2019 Document 136357.1
Related
Products
Oracle E-Business Suite > Financial Management > Financial Control and Reporting > Oracle General Ledger > Setup forms and programs > Cross Validation
Keywords
ACCOUNT CODE COMBINATIONS; ACCOUNTING FLEXFIELD; CODE COMBINATIONS; CROSS VALIDATION; CROSS-VALIDATION RULE; DISABLED ACCOUNTS; FLEXFIELD; FNDFFMCV.FMB;
FNDRXR; INCLUDE; R12; REPORT; RESTRICTED; SECURITY; SEGMENT VALUES; SETUP; VIOLATION
Back to Top
Copyright (c) 2019, Oracle. All rights reserved. Legal Notices and Terms of Use Privacy Statement
https://support.oracle.com/epmos/faces/DocumentDisplay?_afrLoop=81817682852967&parent=DOCUMENT&sourceId=134006.1&id=136357.1&_afrWindowMode=0&_adf.ctrl-state=jldvk1c9a_722#ar… 6/6