Get Started with Redwood: Oracle Cloud SCM and Purchasing
Feasibility of CVR “by Source” and Alternatives in Oracle Fusion
Summary:
We would like to understand whether Cross-Validation Rules (CVR) in Oracle Fusion can be scoped or evaluated by transaction source (e.g., specifically for Procurement transactions), rather than globally across all modules.
Questions:
- Can CVR be applied conditionally by source (e.g., Procurement, AP, Projects), or do they always validate globally at the Chart of Accounts level?
- If CVR cannot be source-specific, what is Oracle’s recommended approach to enforce Procurement-specific account restrictions?
- Segment Value Security (role-based restrictions)?
- Subledger Accounting (SLA) account derivation rules?
- Account Rules by event class/transaction?
- Are there any limitations, performance considerations, or known impacts
Tagged:
0