Key Takeaways
- Oracle delivers four Oracle Fusion quarterly updates a year, and they can’t be skipped or delayed.
- Each update reaches your test environment on the first Friday of your update month and production two weeks later, on the third Friday.
- Depending on your cohort, 26D reaches production between November 2026 and January 2027, and 27A follows between February and April 2027.
- Updates change more than screens. Deprecations, removals and opt-in features that expire can affect reports, data extracts and the integrations that connect Fusion to the rest of the business.
- A workable plan covers three stages: assess the impact before the update, test business processes and integrations inside the two-week window, and monitor production afterward.
|
Every Oracle Fusion quarterly update brings new features, fixes and, occasionally, changes your team didn’t ask for. Oracle says plainly that “quarterly updates are mandatory and cannot be skipped,” so the question for most organizations is how to prepare.
With 26D rolling out now and 27A next on the calendar, this piece covers how the cycle works, where your organization sits on it, what can break, and how to use the two weeks Oracle gives you.
How the Oracle Fusion Quarterly Update Cycle Works
Oracle releases four updates a year, named with the last two digits of the year and a letter: 26A, 26B, 26C and 26D for 2026. Each customer belongs to one of three cohorts, and the cohort sets the months in which updates arrive: February, May, August and November; March, June, September and December; or April, July, October and January.
Within your update month, Oracle applies the release to test environments on the first Friday and to production on the third Friday. Oracle describes the gap as time for testing and for opting in to new functionality (Oracle Fusion Insider).
Not every change behaves the same way:
- Fixes and minor changes that are ready for end users arrive enabled.
- New functionality that materially affects the user experience arrives disabled, so teams can test it before switching it on.
- Some opt-ins expire and are then enabled automatically. Oracle gives customers at least two quarters for changes that require setup.
The volume adds up. In Cloud ERP alone, Oracle says it delivers “more than one hundred new features each quarter.”
When Oracle Fusion 26D and 27A Arrive
The table below applies Oracle’s standard schedule (first Friday for test, third Friday for production) to each cohort. Confirm your exact dates in the Oracle Cloud Console, especially around holidays.
| Cohort |
26D test |
26D production |
27A test |
27A production |
| Feb, May, Aug, Nov |
Nov. 6, 2026 |
Nov. 20, 2026 |
Feb. 5, 2027 |
Feb. 19, 2027 |
| Mar, Jun, Sep, Dec |
Dec. 4, 2026 |
Dec. 18, 2026 |
Mar. 5, 2027 |
Mar. 19, 2027 |
| Apr, Jul, Oct, Jan |
January 2027 (first Friday is Jan. 1; confirm in the Cloud Console) |
Jan. 15, 2027 |
Apr. 2, 2027 |
Apr. 16, 2027 |
Oracle publishes its three update cohorts and the rule that test environments are updated on the first Friday of the update month and production on the third Friday. Oracle does not publish one table that maps each release to each cohort, so the dates above apply those published rules and should be treated as estimates. Holidays can move dates, which is why the January 2027 row shows no exact test date. Confirm your organization’s schedule in the Oracle Cloud Console or with Oracle Support.
Feature details for each release are published on the Oracle Cloud Applications Readiness site, which listed its first 26D content in October 2026.
What Could Break After an Oracle Fusion Release Update
Most of the impact of a quarterly update is planned and documented. The risk sits in what a team doesn’t check. Four kinds of change deserve attention every quarter.
Deprecations and removals
Oracle’s “Important Actions and Considerations” notes list features scheduled to change or disappear. The 26C notes, for example, state that “Business Intelligence View Objects (BIVOs) that are deprecated are no longer available for extraction using BI Cloud Connector (BICC).” For a team that feeds a data warehouse through BICC, that’s a data pipeline to review, not a footnote.
The same 26C notes announce that the prepackaged Oracle Digital Assistant skills for Fusion Applications “will be discontinued on November 21, 2026.” Oracle recommends moving toOracle AI Agent Studio as the primary tool for conversational and generative experiences. The 26C notes also describe the upgrade of identity and access management for Fusion environments to OCI Identity and Access Management.
Opt-in features that expire
A feature your team deferred two quarters ago can become active by default in a later update. If nobody tracked it, its first appearance may be in production.
Integrations
Oracle says changes to its integration tools are “backward compatible and hence, upgrade safe,” and still advises that “it is prudent to confirm that they continue to work as expected.” Only your team can see how your banks, payroll providers, warehouses and CRM depend on those tools.
When something does break, the first sign often appears outside Fusion: a payment file that doesn’t reach the bank, a payroll file that goes out late, orders that stop reaching the warehouse. That’s why Oracle Fusion testing has to follow the business process from end to end, not stop at the Fusion screen.
A Two-Week Plan for Oracle Fusion 26D and 27A Release Testing
Oracle recommends an interdisciplinary team that reviews release details, validates key business processes, tests customizations and evaluates new features (Oracle Fusion Insider). Here’s how that work fits around the update dates.
Before the test update: assess the impact
- Review the What’s New and Important Actions and Considerations notes for every module you run.
- Map each relevant change to the reports, extensions, extracts and integrations it touches, and to the business processes that depend on them.
- Refresh your test environment from production before the update. Oracle notes that P2T refreshes can’t run while test and production are on different releases, so this has to happen early.
- Agree on who signs off on each business process.
Week 1: release testing
- Run regression tests for the processes the business can’t afford to lose: period close, payables and receivables, payroll, procurement and order management.
- Test reports, extensions and workflows.
- Evaluate opt-in features, including any whose opt-in window is about to close.
Week 2: integration testing and sign-off
- Run the integration suite end to end: inbound loads, outbound files, REST and SOAP calls, BICC extracts and business events.
- Reconcile what was sent with what was received for each critical flow.
- Log open issues, agree on workarounds and confirm go or no-go for production.
After production: monitor
- Watch integration errors and business process exceptions daily for the first weeks after the update.
- Plan for failed messages. Oracle’s documentation for Oracle Integration 3 states that “Oracle Integration does not automatically resubmit failed messages.” Failed instances in asynchronous flows can be resubmitted manually, up to ten times and within a recovery window, while synchronous flows can’t be resubmitted at all. Someone, or an automated process, has to catch each failure and act on it in time.
Where Oracle Fusion Test Automation Fits
Two weeks is tight for manual testing, and the scope grows every quarter. Oracle’s own guidance is to invest in test automation, and it names open-source frameworks such as Selenium and TestNG as starting points (Oracle Fusion Insider).
Automation pays off fastest in three places:
- Regression suites for business processes that run every quarter without change
- Integration tests that need to run on each update and again whenever an integration, endpoint or connected system changes
- Post-update health checks that confirm critical flows ran and reconciled
Automation doesn’t replace judgment. Opt-in decisions, new feature evaluation and business sign-off still need people who know the processes.
How IT Convergence Helps
IT Convergence’s Testing as a Service covers both quarterly release testing and integration testing across the systems connected to Fusion. It works alongside ITC’s Smart Integration Automation framework, which connects release review and dependency mapping to the integrations and business processes each change affects. The framework then supports staged promotion from development to production with review and sign-off, and monitors integrations once the update is live.
Prepare for 27A With Us on Dec. 10
Join Achutha Shivashankar, Head of Cloud Practice at IT Convergence, for Oracle Fusion Updates: What Could Break and How to Prepare on Wednesday, Dec. 10, at 12 p.m. CT / 1 p.m. ET. In 45 minutes, he’ll cover what to assess before an update, how to test connected processes, and what to monitor afterward, then take your questions live.
Register for the webinar →
Frequently Asked Questions (FAQs)
- How often does Oracle update Fusion Cloud Applications?
Four times a year. Each update is named by year and letter, such as 26D or 27A.
- Can we skip or delay an Oracle Fusion quarterly update?
No. Oracle states that quarterly updates are mandatory and cannot be skipped.
- When does Oracle Fusion 27A arrive?
It depends on your cohort. Under Oracle’s standard schedule, 27A reaches production in February, March or April 2027. Check your Oracle Cloud Console for your exact dates.
- How long is the testing window for an Oracle Fusion release update?
About two weeks. Test environments are updated on the first Friday of your update month and production on the third Friday.
- What’s the difference between release testing and integration testing?
Release testing confirms that Fusion processes, reports and extensions still work after Oracle’s update. Integration testing confirms that data still moves correctly between Fusion and connected systems, including when integrations, endpoints or connected applications change between releases.
- Can we receive fixes more often than once a quarter?
Oracle says the Oracle Cloud Console offers the option to get fixes on a monthly schedule (Oracle Fusion Insider).