Overview of Cross-Validation Rules and Combination Sets
Use cross-validation rules and cross-validation combination sets to determine the valid account combinations that can be dynamically created as users enter transactions through the user interface, processes, or REST services in Oracle Fusion Cloud Financials.
Cross-validation rules are based on condition and validation filters. Cross-validation combination sets are based on lists of child segment value combinations between two or more chart of account segments, up to a maximum of five segments.
Consider using cross-validation rules when the rules are fewer in number and the check for valid account combinations is more pattern-based and more readily captured using filters with the available operators, especially the tree operators. Cross-validation combination sets can be useful if your criteria are more ad hoc and you need a definitive list of child segment value combinations for the segments you're validating account combinations against.
When users attempt to create a new account combination, the application checks for any account combination validation rules that are active and in effect. If you use different types of account combination validation rules for your chart of accounts, that is, cross-validation rules, cross-validation combination sets, and related value sets, then the account entered on the transaction or setup pages must pass all validation rules to be considered a valid account.
You can manage both cross-validation rules and cross-validation combination sets from the Manage Cross-Validations page. From the centralized user interface, you can download and upload cross-validation rules and combination sets, as well as validate account combinations and manage violations.