Preparing for Oracle’s EBS Next Gen Tech Stack Upgrade: A Readiness Guide

If your team runs Oracle E-Business Suite 12.2, a new My Oracle Support article has probably crossed your radar this year: the FAQ on the EBS Next Generation Technology Stack. It’s the first real change to the EBS technology foundation since the move to Fusion Middleware 11g and Java 7, and it’s worth understanding now, well before Oracle sets a hard deadline for the Classic Technology Stack.

Here’s the short version: Oracle is moving EBS 12.2 off its current foundation layer (Fusion Middleware 11g, WebLogic 11g, Forms and Reports 11g, and Java 7) onto updated versions of those same components, most notably Java 17. Oracle calls the current foundation the Classic Technology Stack and the updated one the Next Generation Technology Stack, or Next Gen Tech Stack. The update is not an EBS version upgrade. Your modules, customizations, and database connections stay in place. What changes is the technology underneath them, and that means a new round of testing and validation before you get there.

What Changes, and What Stays the Same

The table below summarizes the shift at the component level.

Two things worth underlining. First, your EBS release itself does not change, you stay on 12.2. Second, Oracle has confirmed the update is designed to run through EBS Online Patching, so you won’t need to take a separate outage window just to get to the new stack. What does change, beyond the components in the table, is everything downstream of them: integrations, interfaces, and any custom code that touches the application or web tier needs to be revalidated against the new foundation.

Are You Ready? Prerequisites to Check Today

Oracle has published a Next Gen Tech Stack Readiness Checker that evaluates your environment against the current prerequisites. Before you run it, here’s what it’s checking for:

• Oracle E-Business Suite Release 12.2.7 or later
• Oracle Linux 8 (8.7 or later; 8.10 recommended)
• The R12.ATG_PF.C.Delta.14 Release Update Pack or later
• Completed system schema migration
• Oracle Database 19c (19.31 or later)
• The latest available Critical Patch Update

None of these require a database version upgrade specifically for this update. If you’re already on 19c or 26ai, that box is checked. Where most organizations find gaps is Linux 8 and the EBS release baseline, both of which can take real lead time to close.

How the Update Works

Oracle has structured the update process into four stages:

1. Prepare: Run the Readiness Checker and complete environment prerequisites. This can be done in any order, on the Classic stack, with no impact to production.
2. Generate: Create and upload your environment manifest file to My Oracle Support once prerequisites are met.
3. Stage: Set up the stage area and download your migration patch and corequisite patches from My Oracle Support.
4. Update: Apply the update using EBS Online Patching and the Technology Stack Update Assistant (TSUA), performed online with minimal downtime.

As of this writing, the Next Gen Tech Stack update is not yet generally available. If you want to update ahead of general availability, Oracle requires a special Service Request and a manifest file specific to your environment. For most organizations, the more practical move right now is the Prepare stage, since it can be completed entirely on the current Classic stack.

Is This Mandatory? Hype vs. Reality

The hype

Headlines around this update tend to frame it as an urgent, sweeping overhaul, understandably, since moving from Java 7 to Java 17 and from 11g to 14c across the entire technology stack is a significant engineering shift.

The reality

The update is not mandatory today, and Oracle has not published a general availability date or a retirement date for the Classic stack. What is confirmed is the direction: Oracle has committed to supporting EBS 12.2 through 2037 under continuous innovation, and future feature releases are expected to target the Next Gen stack rather than the Classic one. In practical terms, this is a “prepare now, act when it’s available” situation rather than a fire drill. Organizations that complete the Prepare stage early will be in a far better position once Oracle publishes a firm timeline and demand for upgrade support increases.

Getting Ahead of the Update

Oracle has been clear that this isn’t a today problem, it’s a soon problem. The organizations that will move fastest once the Next Gen Tech Stack reaches general availability are the ones who’ve already closed their prerequisite gaps: EBS 12.2.7 or later, Linux 8, database 19c or higher, and a completed schema migration. If any of those are open questions for your environment, now is the time to close them, not after Oracle sets a deadline.

Frequently Asked Questions (FAQs)

1. Do I need to upgrade my EBS version to get the Next Gen Tech Stack?
   No. The update applies to the technology stack underneath EBS 12.2, not to the EBS release itself, and it’s delivered through EBS Online Patching.
2. Will my customizations still work?
   Your modules, customizations, and database connectivity remain intact. What changes is the underlying technology layer, so integrations, interfaces, and custom code need to be tested and validated against the new stack before you go live.
3. Do I need to upgrade my database first?
   Not specifically for this update. Oracle Database 19c (19.31+) and 26ai are both supported, so if you’re already on one of those versions, the database is not a blocker.
4. When will the Next Gen Tech Stack be generally available?
   Oracle has not published a general availability date. Until it does, updating requires a special Service Request and an environment-specific manifest file through My Oracle Support.
5. Where can I find the official documentation?
   Oracle’s primary references are:
   1. FAQ: Oracle E-Business Suite Next Generation Technology Stack (KA1014)
   2. Preparing Oracle E-Business Suite Release 12.2 for the Update to the Next Generation Technology Stack (KA1357)
   3. EBS 12.2 Application Technology Stack Roadmap