Oracle Fusion · Quarterly Readiness
A practical look at the 25C changes that can improve AI-assisted work, requester shopping, purchasing, sourcing, suppliers, contracts, and healthcare procurement.
Quarterly release notes can be difficult to translate into an improvement plan. This briefing highlights the Oracle Fusion 25C procurement features most likely to solve real operating pain points or deserve a controlled pilot.
This article reflects information available in July 2025. Confirm current opt-ins, prerequisites, licensing, feature maturity, and later changes in Oracle documentation before using it as a production plan.
AI Agent Studio was the major 2025 development, expanding on the 24D retrieval-augmented generation experience. Instead of only answering questions from documents, agents can combine multiple tools and take action.
| Capability | Practical use | Control point |
|---|---|---|
| Outbound email | Send messages based on what an agent discovers or completes. | Review recipients, content, and approval expectations. |
| Deep links | Answer a question and link the user directly to the related Oracle document. | The user still needs appropriate application access. |
| Oracle business objects | Use REST resources to retrieve information or perform supported actions such as creating or changing transactions. | The agent acts within the human user’s privileges and can be restricted to selected fields. |
| Documents | Use reference material both to answer questions and guide actions. | Curate authoritative, current source content. |
| External REST | Read or update external services with more flexible, conversational orchestration. | Apply integration security, error handling, and governance. |
Agents complement existing automation rather than immediately replacing it. At publication they could not output flat files such as FBDI, and some Oracle tasks did not have a supporting REST resource. Oracle also delivered selected native agents, including requisition lookup and deep-link assistance, while custom agents involved separate licensing choices.
Requesters who know an exact part number no longer need to sift through large fuzzy-match result sets. You can enforce exact matching for number-based attributes such as MPN, supplier part number, and GTIN.
Oracle: Specific search results for number-based attributesRequested delivery dates can use lead times from Product Information Management or a blanket purchase agreement. This gives requesters a more realistic expectation and can reduce date-related purchase-order changes.
Oracle: Use lead times to determine delivery datesRequesters can confirm receipts from the My Requisitions page to help resolve invoices held for pending receipts. This was enabled by default when the earlier “Review requisition lines with invoice holds in RSSP” feature was enabled.
Location preferences can be searched with a single character and across more attributes. Results are also constrained by the managing business unit relationship to the inventory organization. Enable the enhanced search view through Visual Builder Studio.
The Redwood page gained much more of the buyer’s daily toolset:
| Feature | Value | Evaluation note |
|---|---|---|
| Review PO change orders | Buyers can review purchase-order changes in the Redwood experience. | Test the change scenarios and attachments used by your organization. |
| Search agreements and lines | Search across purchase agreements and agreement-line details. | Confirm indexing and field coverage before moving teams. |
External Purchase Prices can assign buyers according to source-contract values instead of relying only on the default buyer. The new mapping page requires the Create BPA by Source Contract opt-in.
The landing page adopts a pattern similar to purchase-order and requisition processing, including KPIs at the top. This change was automatic.
Oracle: Improved External Purchase Prices landing pageOracle can validate that a U.S. bank account is valid and that its owner matches the supplier, addressing a significant fraud and data-quality concern.
The feature used JPMorgan’s paid Bank Account Validation Service, required a JPMorgan account opened in the United States, and validated only U.S. bank accounts—although the supplier’s account could be at another U.S. bank. Setup required an Oracle service request and the documented onboarding steps.
25C introduced Redwood negotiation management. Enablement was primarily profile-driven, with supporting jobs for search indexing. There was no known required-migration date at publication.
Move when the pages are stable and have parity for your required business functions. If a pre-go-live project has fewer than three test cycles remaining, introducing a voluntary user-interface migration may add unnecessary risk. Evaluate each client’s functional patterns rather than treating Redwood adoption as a purely visual change.
The Extract Key Terms and Classify features use AI to normalize important provisions from differently structured contract documents. A new OTBI subject area makes those outputs reportable without building a BI Publisher report. At publication, bringing key-term extraction to draft contracts was on the roadmap with timing still to be determined.
Oracle: Report on contract requests and key termsVersion 4.5 added the current Oracle instance URL to the bottom of the Status window, making it easier to confirm that a download or update is targeting the intended environment. The preceding 4.4 release also made it easier to copy or reference a full column from another worksheet—for example, pasting a BI Publisher list of purchase orders into a download filter.
25C combined several immediately useful requester improvements with larger strategic moves in AI and Redwood. Exact search, lead-time dates, receipt confirmation, and buyer mappings can remove familiar friction. Agent Studio and Redwood negotiations deserve deliberate pilots that account for licensing, security, REST coverage, functional parity, and project timing.