Home › Prepare for a quarterly update

Prepare for an Oracle Fusion Cloud quarterly update

A repeatable playbook for each Fusion Cloud quarterly update: when it lands, what changed, and what to test before production.

In short: Plan Fusion Cloud quarterly updates in three layers: (1) when your cohort's test and production Fridays fall, (2) what changed — on by default, opt-in, and opt-ins that are now standard — and (3) what to test in the roughly two-week pod window. For 26D, start with the dates page (Cohort A Fri 6 Nov 2026 / Fri 20 Nov 2026), the 26D hub (768 features in modules we cover), and the what-to-test checklist. Tick Financials, HCM, SCM, Procurement, Logistics and Projects pages that match your offerings; confirm every opt-in decision before production.

Source for the cohort rule: Oracle Fusion Insider, "Quarterly updates made easy" (published 10 Dec 2025). Oracle publishes the rule rather than a public list of dates for every environment. Confirm your own dates in the Oracle Cloud Console. Middle East regions update on the Thursday before each Friday.

1. When: your cohort's Fridays

Find your cohort in the Oracle Cloud Console. Typical 26D Fridays:

Cohort A — test Fri 6 Nov 2026, production Fri 20 Nov 2026
Cohort B — test Fri 4 Dec 2026, production Fri 18 Dec 2026
Cohort C — test Fri 1 Jan 2027, production Fri 15 Jan 2027 — This date is New Year's Day. Oracle may schedule this cohort differently, so confirm yours in the Oracle Cloud Console.

Full 26D dates page → · Download the .ics calendar →

2. What: on by default, opt-in, now standard

For 26D across the modules we cover:

On by default — users may see these when the update lands
Opt-in features — stay off until you choose them
Former opt-ins now standard (23) — 9 switch on for everyone, 14 need setup
How opt-in and enablement work (evergreen glossary)

3. What to test

Baseline items follow Oracle's published guidance: What Should I Test After a Quarterly Update?

Validate your current configuration first; don't enable new features yet
Key end-to-end business flows for each role (e.g. procure-to-pay, order-to-cash, plan-to-produce, hire-to-retire)
Integrations: REST/SOAP APIs, FBDI/HDL imports, and third-party systems
Critical custom reports and analytics (BI Publisher, OTBI)
Custom workflows, approvals, extensions, and personalizations
Security: roles and privileges for new or changed pages
Features delivered automatically on (section 2) and former opt-ins that are now standard (section 3)
Performance of key flows with production-like volumes
Features delivered switched on (see the release checklist)
Former opt-ins that are now standard
Refresh your test environment from production before the test-environment update, as Oracle recommends

Open the 26D what-to-test checklist → Get the printable PDF →

Module hubs for 26D

Financials · Procurement · Supply Chain & Manufacturing · Logistics (OTM, GTM, WMS) · Project Management · HCM

26D hub · Redwood defaults calendar · AI and agentic features in 26D

Frequently asked questions

How long is the test window?

About two weeks: Oracle updates test environments on the first Friday of the cohort month and production on the third Friday. Source: Oracle Fusion Insider.

What should I test first?

Baseline regression (current configuration, key end-to-end flows, integrations, reports, custom workflows, security), then features delivered switched on, then former opt-ins that are now standard. Our checklists follow that order.

Where do I get 26D dates?

26D release dates and cohorts applies Oracle's published rule. Confirm your own dates in the Oracle Cloud Console.

Is this the same as the old /guides/how-oracle-fusion-updates-work/ URL?

That path returned 404. This page is the replacement; requests to the old path redirect here.