Upgrade Path Planner

JD Edwards EnterpriseOne upgrade path planner: Xe, 8.x, 9.0 and 9.1 to 9.2

Pick the EnterpriseOne release you run and the 9.2 Tools release you are moving to. The planner lays out Oracle's documented route (Traditional or Simplified Upgrade, the required 9.1 hop from 8.9 to 8.11, the 64-bit switch and the Tools upgrade), the changes in every release you cross, and a risk score, effort range and regression test plan sized to your custom objects, integrations and reports.

Free, runs in your browser, no sign-in needed. Release data checked 2026-10 against 27 cited sources.

1Releases
Verify with vendorRelease year not verified.
CurrentRelease 26 updates published October 2025, January 2026 and April 2026.
2Landscape
What to count in JDE E1
customizations:
Modified or custom objects in OMW: interactive applications, UBEs, NERs, C business functions, tables, business views and table conversions, both custom and modified standard objects.
integrations:
Orchestrations and AIS REST clients, business services (BSSV), tax, CRM, WMS, MES, e-commerce and banking systems.
interfaces:
EDI, batch import and export jobs, flat files, scheduled UBEs feeding other systems, direct SQL readers.
reports:
Custom and copied UBEs, BI Publisher templates, One View reports and other UDO-based reports.
sites:
Separate EnterpriseOne instances or production environments to upgrade, not companies or business units.
Modules in use
Integration types
EnterpriseOne 9.19.2 Release 26 (Tools 9.2.26, current)

Direct upgrade to 9.2, Simplified or Traditional. The Impact Analysis Report (R96711) recommends the more efficient type for your environments.

Steps
15
1 to confirm
Releases crossed
6
EnterpriseOne 9.2, 64-bit
Risk
65 / 100
High
Effort
249-633 d
about 12-32 person-months
  1. 1
    PreparationDocumented

    Inventory customizations with the Customization Object Analyzer and Application Configuration Analyzer

    Oracle's upgrade resources list the Customization Object Analyzer (lists customized EnterpriseOne objects) and the Application Configuration Analyzer, whose reports compare versions (R983051N), the data dictionary (R969200N) and user defined codes (R960004N). Use the output to size the retrofit and to move tested modifications into one path code: Oracle notes that upgrading a single environment significantly shortens the process.

    Customization Object AnalyzerApplication Configuration AnalyzerR983051NR969200NR960004NSource 3Source 18
  2. 2
    PreparationDocumented

    Run the Decustomizer Analysis Report

    The Decustomizer Analysis Report identifies UI customizations that can be replaced with personalization and extensibility (form extensions, UDOs) instead of being retrofitted, which lowers the cost of every later update.

    Decustomizer Analysis ReportSource 3
  3. 3
    PreparationDocumented

    Run the Impact Analysis Report (R96711) and pick the upgrade type

    Run R96711 against the 9.0.2 or 9.1 environments to be upgraded. It analyzes the impact on all objects and advises whether a Traditional or a Simplified Upgrade is more efficient. Both end with the same 9.2 functional code base.

    R96711Source 7Source 5
  4. 4
    PreparationDocumented

    Install the latest 32-bit Tools Release, Planner Update and Tools ASI on the Deployment Server

    The DLLs delivered in the PLANNER path code are 32-bit, so the upgrade starts on the latest 32-bit Tools Release (the guide names 9.2.5.5). Install the latest Planner Update and its special instructions, the Server Manager Console and Agent, the latest Tools Rollup ESU and Tools ASI 9.2.x, which applies the application and DLL changes needed for Tools 9.2.5.x.

    Tools Release 9.2.5.x (32-bit)Planner UpdateTools ASI 9.2.xServer ManagerSource 10Source 12Source 11
  5. 5
    UpgradeDocumented

    Upgrade the Pristine (PS920) environment first

    Mandatory pre-upgrade process: create and run an upgrade plan for PS920 only (table conversions do not run for Pristine), install the same Tools Release on the Enterprise Server as on the Deployment Server, and confirm EnterpriseOne services are running. Hundreds of table conversions follow, so Oracle recommends running them on the Enterprise Server.

    Installation PlannerInstallation WorkbenchSource 17
  6. 6
    UpgradeDocumented

    Simplified Upgrade: keep Central Objects, merge only changed standard objects

    The Platform Pack does not install Central Objects for your environments; data sources point to your existing 9.0.2 or 9.1 path codes. The spec merge replaces only standard objects changed between your release and 9.2, and a summary report lists replaced objects that you modified and must retrofit. Create a standard package (for example DV920FA) in the target Central Objects for the table conversions, and align spec.ini on the Enterprise Server (path code folders changed with 9.2.6). Keep copies of modified objects in OMW so they can be overlaid instead of retrofitted.

    Platform PackSpecification MergeCustom Object AnalysisSource 7Source 12
  7. 7
    UpgradeDocumented

    Installation Planner, control table merges and table conversions

    The Installation Workbench runs the control table merges and the Table Conversion Workbench converts business data to the 9.2 layout. The plan type differs for a Simplified Upgrade. Review R984052 for table conversion results.

    Installation PlannerInstallation WorkbenchTable Conversion WorkbenchR984052Source 6Source 4
  8. 8
    ConversionDocumented

    Run the post-conversion steps for 9.1 and below

    After table conversions, run R98222UDO in proof then final mode to add converted personal UDOs to default projects (needs data in F9861W), R8931CTSX if CTSx data items hold unaccounted units (then set their display decimals to 4 in the E920 data dictionary), and R41B110 from any release before 9.1 to populate the Tank Master tag file F41500T.

    R98222UDOR8931CTSXR41B110Source 16
  9. 9
    ConversionDocumented

    Retrofit custom modifications with the Customization Workbench and compare tools

    Customized objects the upgrade replaced must be retrofitted. The Customization Workbench covers interactive applications, reports, table conversions, tables, Named Event Rules and C business functions; FDA Compare, ER Compare and Visual Compare for UDC descriptions and glossary help compare old and new versions.

    Customization WorkbenchFDA CompareER CompareVisual CompareSource 3Source 4
  10. 10
    ValidationDocumented

    Build and test full packages

    Before building the package, confirm SY920.F00942T.EMDBSRCFLG is set to 2 (never 0): One-Click images do not ship source on the Deployment Server, so the only source there is your custom business functions copied forward by the spec merge. Build, deploy and test the package per environment.

    Package BuildF00942TSource 12
  11. 11
    ConversionDocumentedlands on 9.2 Release 22 (Tools 9.2.6)

    Move the Deployment Server and path codes to 64-bit

    From Tools 9.2.6 (Release 22) new Tools releases are 64-bit only. Switch the Deployment Server only after the final spec merge on the last path code; it cannot go back to 32-bit. Then copy bin64 from PLANNER to each path code and the 64-bit glbltbl, dddict and ddtext files to each path code's spec directory, or no table conversion (including *ALTER in ESUs) can run. Custom C business functions must build cleanly for 64-bit.

    Implementing 64-bit Processing learning pathSource 10Source 13Source 2Source 19Source 20
  12. 12
    UpliftDocumented

    Upgrade the Tools Release to the target and apply the Tools Rollup

    Upgrade Server Manager, the Deployment Server, the Enterprise Server and the HTML Server to the target Tools Release. From Release 24 the Automated Tools Release Configuration (ATRC) replaces the ASI for the Tools Rollup ESU.

    Server ManagerATRCTools Rollup ESUSource 3Source 22
  13. 13
    UpliftDocumented

    Adopt the Applications Update and ESUs you need

    9.2 receives new features as updates to the same release instead of a new major release. Apply the Applications Update (UN) and ESUs in scope; from Release 24 Update Manager supports the web client, and Release 25 adds Web Planner ESU and delta-based full package builds. Rerun the impact analysis on what each update touches.

    Update ManagerWeb Planner ESUImpact Analysis DashboardSource 1Source 22Source 23
  14. 14
    CutoverDocumented

    Upgrade the Production environment

    The guide treats Production as its own pass: set up an upgrade plan for Production, run it, test the production package and bring the environment online. Time it on a copy with production-sized data first.

    Source 4
  15. 15
    CutoverVerify with vendor

    Rehearse, freeze and cut over

    Run at least one full rehearsal with production data to time table conversions, agree a freeze window that covers the UBEs that require suspended activity, then convert, validate and reconcile ledgers and inventory before users return.

Free, optional. Reopen it on any device.
Export plan:

This is a planning model. Before you commit a budget or a date, have an engineer check the path, the effort drivers and the test scope.

How to use the JDE E1 upgrade planner

  1. 1

    Pick your releases

    Choose your current applications release (Xe to 9.1, or 9.2 on an older Tools release) and the target 9.2 Tools release, on-premises or on Oracle Cloud Infrastructure.

  2. 2

    Describe your landscape

    Enter counts for custom objects, integrations, batch and EDI interfaces, custom reports, data size, users and sites, then tick the modules and integrations you use.

  3. 3

    Read the path and the drivers

    Review each step with its Oracle source, the changes in every release you cross, and the drivers behind the risk score and effort range.

  4. 4

    Export the test plan

    Download the regression plan as Excel, Word, PDF or CSV. Critical tests are flagged where your path changes that area.

  5. 5

    Save or get it reviewed

    Save the plan to your Netray account to reopen later, or send it to an engineer for a written review.

Questions

What is the latest version of JD Edwards EnterpriseOne?

Applications release 9.2. Oracle delivers new features as updates to 9.2 instead of new major releases. Since Release 26 the names match the release number: Applications Update 26 and Tools 9.2.26. Before that, Release 22 to 25 came with Tools 9.2.6, 9.2.7, 9.2.8 and 9.2.9. Oracle states Premier Support for 9.2 through at least 2037.

Can I upgrade directly from 9.1 or 9.0 to 9.2?

Yes. From 9.0 Update 2 or 9.1 you can choose a Simplified Upgrade, which keeps your Central Objects and replaces only standard objects that changed, or a Traditional Upgrade, which replaces all objects. Run the Impact Analysis Report (R96711) to see which is more efficient. From 9.0 before Update 2 only the Traditional Upgrade applies.

Is there a direct upgrade path from 8.9, 8.10 or 8.11 to 9.2?

No. Oracle's 9.2 upgrade guide says there is no upgrade path from 8.9, 8.10 and 8.11 to 9.2 because the table conversion schedule and control table merges are not available. You upgrade to 9.1 first, finish table conversions and custom objects there, then upgrade 9.1 to 9.2.

How do I upgrade from OneWorld Xe or ERP 8.0?

With a Traditional Upgrade on the latest 32-bit Tools release (9.2.5.x). 64-bit Tools cannot read Xe specifications, so complete the applications upgrade, including bringing customizations forward, before you switch to 64-bit. Xe sources also need the Unicode conversion code page for language-enabled NERs and a long list of post-install conversion UBEs.

What does the 64-bit change mean for our customizations?

From Tools 9.2.6 (Release 22) Tools releases are 64-bit only. Custom C business functions must compile and run on 64-bit, the Deployment Server cannot return to 32-bit once switched, and the 64-bit bin64 and spec files must be copied to every path code or table conversions, including *ALTER in ESUs, will not run.

Which customizations survive a JD Edwards upgrade?

The specification merge preserves your modifications where they do not conflict with the new release and keeps yours where they do. Objects the upgrade replaces must be retrofitted. The Customization Object Analyzer lists customized objects, and the Decustomizer Analysis Report finds UI changes you can replace with personalization and form extensions.

How should we test a JD Edwards upgrade, and what should we automate?

Run a full regression on a copy of production: platform tests (sign-on, security by role, control table merges, table conversion results, packages, retrofitted objects, UBEs), the modules you use, and every integration with saved production inputs. Because 9.2 updates and Tools releases repeat every year, the tests marked for automation pay back on every update. The planner generates the list and flags critical tests where your path changes that area.

Can we move to Oracle Cloud during the upgrade?

Yes. EnterpriseOne 9.2 runs the same application on Oracle Cloud Infrastructure (IaaS), so customizations carry over. One-Click provisioning is not built for upgrades: export your business data and control tables, provision 9.2, then restore your data. Oracle provides a migration utility for moving 9.0 or 9.1 data to the cloud.

Sources

  1. Oracle LearnJDE: JD Edwards Premier Support (9.2 through at least 2037)
  2. Oracle LearnJDE: upgrade to EnterpriseOne 9.2
  3. Oracle LearnJDE: EnterpriseOne upgrade resources
  4. Oracle: Applications Upgrade Guide 9.2 for Microsoft Windows with SQL Server
  5. Oracle upgrade guide: understanding upgrade types
  6. Oracle upgrade guide: Traditional Upgrade
  7. Oracle upgrade guide: Simplified Upgrade
  8. Oracle upgrade guide: release history (supported previous releases)
  9. Oracle upgrade guide: 64-bit, upgrade from Xe or ERP 8.0
  10. Oracle upgrade guide: 64-bit, upgrade from 8.9, 8.10 or 8.11
  11. Oracle upgrade guide: 64-bit, upgrade from 8.12
  12. Oracle upgrade guide: 64-bit, upgrade from 9.0 or 9.1
  13. Oracle upgrade guide: table conversion considerations for all source releases
  14. Oracle upgrade guide: verifying Unicode settings when upgrading from Xe
  15. Oracle upgrade guide: post-installation tasks from Xe / ERP 8.0
  16. Oracle upgrade guide: upgrading from 9.1 or below
  17. Oracle upgrade guide: mandatory pre-upgrade process (Pristine environment)
  18. Oracle upgrade guide: what custom modifications an upgrade preserves and replaces
  19. Oracle: Implementing 64-bit Processing with JD Edwards EnterpriseOne learning path
  20. Oracle LearnJDE: Release 22 (Tools 9.2.6)
  21. Oracle LearnJDE: Release 23 (Tools 9.2.7)
  22. Oracle LearnJDE: Release 24 (Tools 9.2.8)
  23. Oracle LearnJDE: Release 25 (Tools 9.2.9)
  24. Oracle LearnJDE: Release 26 (Tools 9.2.26)
  25. Wikipedia: JD Edwards (release history)
  26. Spinnaker Support: Oracle extension of EnterpriseOne 9.2 support (2023)
  27. Briteskies: reasons to upgrade to EnterpriseOne 9.2

Steps marked Verify with vendor are planning inferences, not vendor statements. Effort coefficients are Netray planning assumptions and are shown in full in the Effort tab.