You use cross-validation rules to prevent the creation of combinations that should never exist (combinations with values that should not coexist in the same combination). For example, you can assign rules to prevent the combination of a product with administrative departments.
Example
Points to Remember
-Because cross-validation rules validate only new accounts, you should define and enable them prior to entering accounts.
-You can revise cross-validation rules at any time, but remember that they only prevent the creation of new invalid account combinations.
Available reports to check Cross-Validation Rules
Cross-Validation Rule Violation Report: This report provides a listing of all the previously-created flexfield combinations that violate your cross-validation rules. You can also choose to have the report program actually disable the existing combinations that violate your new rules.
Cross-Validation Rules Listing Report: This report lists all the cross-validation rules that exist for a particular flexfield structure. This is the information you define using the Define Cross-Validation Rules form, presented in a multiple-rule format you can review and keep for your records for a given flexfield structure.
