Cross-validation rules stop creation of new invalid combinations at entry time. Existing combinations that already violate a rule remain unless you execute the “Cross-Validation Rule Violations” scheduled process, which lists and can disable them. Thus you must run that process (B), and the rule can then be made effective for both new and existing combinations (E).

A. No scheduled process named “Cross-Validation Rules”; mis-named, therefore incorrect.

C. Dynamic Combination Creation setting is unrelated; CVRs still control manual entry.

D. After running the violation process, existing accounts can also be disabled, so not limited to new.

1. Oracle Fusion Cloud Financials, Implementing General Ledger (23C), “Define Cross-Validation Rules”, pp. 53-55.

2. Oracle Fusion Cloud Financials, Scheduled Processes Guide (23C), “Cross-Validation Rule Violations”, pp. 241-242.