Get Started with Redwood: Oracle Cloud SCM and Purchasing
Oracle Fusion Blanket PO
Summary:
Hello experts,
We are seeking the best configuration solution to achieve the following mandatory Blanket PO requirements in Oracle Fusion Cloud Procurement:
- Budgeting: Can Fusion be configured to reserve the budget ONLY at Blanket PO header creation and SKIP the budget consumption check on subsequent Releases? What is the exact configuration path?
- Release Auto-Approval: What is the best practice to enforce Auto-Approval for all Blanket PO Releases, bypassing the standard workflow?
- Release Numbering: Can the custom numbering scheme (PO 12345-1, 12345-2) be achieved for each release from this Blanket PO? (it will be the same number as the Blanket PO with -1,-2, ...)
0