OracleFree checklistPDF, Excel, Word exportOracle E-Business SuiteAll Oracle E-Business Suite tools

Oracle EBS 12.2.x Release Update Pack (RUP) Upgrade Checklist

This checklist plans a move between Oracle E-Business Suite 12.2 code levels, for example 12.2.6 or 12.2.10 to 12.2.14 or a later RUP, using online patching (adop). It covers the technology stack, custom code compliance, the adop cycle and the post-steps that most projects underestimate.

0%

0 of 27 items complete

8 critical items still open - these are the highest-risk gaps.

Download checklist:

1. Plan the target code level

2. Technology stack first

3. Custom code readiness

4. Execute with adop

5. Post-upgrade steps

6. Test and sign off

The readme for your target RUP overrides any item here. Keep the AD/TXK cycle separate from the RUP cycle.

Get your RUP plan checked

Send your current and target code levels, ETCC output and custom object count, and we will review the sequence and outage estimate.

Optional. The tool and every export work without this. No spam.

Was this tool useful?

How to use it

Treat the target RUP as a variable. Oracle publishes a readme for each 12.2.x release update pack and a suite-wide note listing RUPs with their AD/TXK requirements; read both before committing to a level. Then run the groups on a full-size clone, record timings and issues, and reuse the list for production. Critical items are the ones that, if skipped, stop the RUP from applying or leave the system unsupported.

  • Rehearsal on a clone with production volumes
  • Separate adop cycle for AD/TXK Delta
  • Keep ETCC reports before and after

Where code levels live in EBS

The current release shows in FND_PRODUCT_GROUPS.RELEASE_NAME, for example 12.2.10. Individual technology and product code levels are tracked in AD_TRACKABLE_ENTITIES, where ABBREVIATION identifies the entity (ad, txk, fnd and so on) and CODELEVEL holds the level such as C.13. Query both before and after the upgrade and keep the output with your change record. Applied patches are recorded in AD_APPLIED_PATCHES and AD_BUGS, which is how you confirm a prerequisite is present rather than trusting a spreadsheet.

  • select release_name from apps.fnd_product_groups;
  • select abbreviation, codelevel from apps.ad_trackable_entities where abbreviation in ('ad','txk','fnd');

Online or downtime mode

adop normally applies patches to the patch file system while users work, then switches at cutover. For a RUP, the readme states whether online mode, downtime mode (adop phase=apply apply_mode=downtime) or both are supported. Downtime mode skips the online patching overhead and can shorten total elapsed time when you are already taking an outage, but users cannot work during the apply. Decide using rehearsal timings, not guesses, and check that your previous adop cycle is fully cleaned up before you start.

Common mistakes

The usual failures are skipping the AD/TXK delta cycle, applying the RUP before ETCC is clean, and discovering custom objects that violate online patching rules halfway through. Post-install steps in the readme are also easy to miss because the patch itself completes successfully without them. Finally, teams often test seeded flows but not personalizations and custom extensions on replaced pages, which is where users notice the change first.

Frequently Asked Questions

How do I upgrade EBS from 12.2.6 to 12.2.14?

Apply ETCC-required database and middleware fixes, then the latest AD and TXK Delta packs in their own adop cycle, then the 12.2.14 RUP with the mode its readme states, followed by the readme post-steps, cutover, cleanup and fs_clone. Rehearse on a full clone and regression test custom code before production.

How do I find my current EBS 12.2 version?

Query RELEASE_NAME from APPS.FND_PRODUCT_GROUPS. For technology code levels, query ABBREVIATION and CODELEVEL from AD_TRACKABLE_ENTITIES, for example for ad and txk. The Oracle Applications Manager pages also show the release, but the tables are the definitive source.

Should the RUP be applied in downtime mode?

Check the readme of the specific RUP: it states the supported modes. Downtime mode (apply_mode=downtime) avoids online patching overhead and is often faster when an outage is planned anyway, but the system is unavailable throughout. Online mode keeps users working until cutover at the cost of a longer total cycle.

What is ETCC and why run it before a RUP?

The EBS Technology Codelevel Checker (Doc ID 1594274.1) compares your database and middleware homes with the bug fixes EBS requires. checkDBpatch.sh runs on the database tier and checkMTpatch.sh on the application tier. Missing fixes can cause RUP failures or unsupported configurations, so clear them first.

After a RUP, we can add an on-prem AI assistant that answers questions over your upgraded EBS data and documents, without sending anything outside your network.

ArchRay builder
Design the on-prem AI stack for Oracle E-Business Suite: model, GPUs, RAG pipeline, guardrails
See memory, speed and cost as you swap parts, then export the diagram. Free, in your browser.
Open the builder

Keep exploring

Free tools

ERP fixes and how-tos

Runs with your ERP

AI on your ERP

Integrations

Software