Oracle Fusion · Quarterly Readiness
A curated practitioner’s briefing on the Oracle Fusion 26A changes most likely to affect procurement, contracts, requisitions, healthcare supply chain, inventory, and receiving.
Each quarter, I review Oracle’s readiness material and select the changes most relevant to real implementations. This is a curated interpretation, not a replacement for the complete Oracle documentation.
This briefing reflects information available when it was published in December 2025. Roadmap dates, opt-in status, licensing, and product behavior can change. Confirm current requirements in Oracle’s readiness documentation before planning production changes.
At publication, Oracle’s direction indicated that SCM pages across Inventory, Procurement, Manufacturing, and related areas should target Redwood adoption by 27A. The exact post-deadline support model was not yet confirmed in writing, so the prudent planning assumption was to complete migration rather than depend on Classic availability.
Inventory every Classic page still used, identify Redwood replacements and gaps, test extensions and roles, update training, and give high-volume warehouse and procurement users adequate practice time.
This Oracle-provided agent helps explain and resolve External Purchase Price import and processing issues and assists with mappings. It can make EPP operations more approachable for teams concerned about data setup and troubleshooting.
Contracts received a major update: Redwood search and creation, Access Groups as a more manageable security concept, and a requisition-to-contract-to-PO flow that closes an important process gap. The Contract AI Advisor adds conversational questions about contract content and terms.
The remaining integration opportunity noted in the original review was BPA updating comparable to EPP.
Read the related Oracle 26A procurement documentationREST is increasingly relevant beyond technical integration teams:
New or expanded 26A service areas included purchase agreement acknowledgements, supplier configuration, contract-type lists of values, negotiation awards, and requisition-line replacement.
Additional notifications moved to Redwood-style output. These are generally easier to modify and may expose notifications that were not previously editable.
Review Oracle’s 26A Self Service Procurement updatesOracle uses historical BPA and PO lines to recommend the most likely purchasing category for a requisition description. This can reduce the category-selection burden on requesters, but recommendation quality depends on historical data quality.
Classic Self Service Procurement exposed budget details when a funds check failed. 26A restores this visibility in Redwood, helping requesters and support teams understand the failure rather than seeing only a generic result.
A requisition line can move into contracting and show that status. Requisition users also gain better visibility into purchase-order approvers, reducing uncertainty and routine status questions.
Healthcare organizations can connect directly to GHX Marketplace. Requesters can begin with guided buying in the local catalog and also see enriched GHX catalog results.
The advisor focuses attention on items with accuracy problems rather than only high dollar value. It supports a healthier cycle-count culture by helping teams identify recurring inaccuracies.
Reports still have an important place for broad analysis across many organizations or long time periods. A useful future extension would be letting the agent implement recommended cycle-count changes, update classes, or create schedules.
This agent provides conversational views of slow-moving inventory and allows follow-up questions. Its “scrapping” path creates an interorganization movement request and pick ticket; the receiving organization still needs an operating procedure to disposition and adjust the material after delivery.
That handoff makes the feature a good candidate for organization-specific agent extensions aligned to the actual disposal process.
The advisor can locate an item in other stock locations when it is missing for a pick. From the same conversational experience, an operator can create a cycle count or initiate an adjustment, replacing several navigation steps.
| Capability | Operational impact | Implementation focus |
|---|---|---|
| Lot and serial counting in quantity-tracked PAR | Extends the newer quantity-tracked PAR process with controlled-item detail. | Validate scanning, count entry, and downstream lot/serial handling. |
| Review Min-Max and PAR recommendations | Compare Oracle’s suggested levels with current values and override before publishing. | Define review ownership and exception thresholds. |
| Lot-specific UOM conversions | Supports more accurate dual-UOM behavior when conversion varies by lot. | Test item, lot, transaction, costing, and reporting impacts. |
| Capture lot/serial during receiving | Two-step receiving can capture control values at receipt instead of waiting for putaway. | Update receiving procedures and device flows. |
| Document Output Preferences | Route paper documents and labels to preferred destinations without selecting a printer each time. | Configure and test paper and label output separately. |
| Receipt Creation AI Agent | Parse a pasted list—including email content—and create receipts through a conversational path. | Test parsing, transaction validation, roles, and exception handling. |
26A is less about one headline feature than a pattern: Redwood becomes the operating model, REST becomes part of functional design, contracts reconnect to upstream procurement, and AI agents begin collapsing multi-step inventory tasks into guided conversations. The strongest implementations will pair those capabilities with clean history, explicit controls, and redesigned operating procedures.