JD Edwards EnterpriseOne 9.1 to 9.2 Upgrade Checklist
This checklist covers an EnterpriseOne application upgrade from 9.0 or 9.1 to 9.2: planning, deployment server and platform pack, table conversions, spec merge and retrofit, packages, testing and cutover. Use it alongside the Oracle 9.2 Upgrade Guide for your database platform.
0 of 38 items complete
11 critical items still open - these are the highest-risk gaps.
Planning
Deployment server and platform pack
Table conversions and control tables
Spec merges and retrofit
Packages
Testing and cutover
Workbench names and order follow the Oracle EnterpriseOne 9.2 upgrade documentation, which differs by database platform and source release. Use the Oracle Upgrade Guide for your platform as the authority for exact steps.
Get your upgrade plan reviewed
Send us your source release, database platform and custom object count and we will review the checklist and cutover window with you.
Optional. The tool and every export work without this. No spam.
How to use it
Run the checklist twice: once for the test upgrade on a prod-size copy, and again for the production cutover. The first pass produces the numbers that matter, especially table conversion runtimes and the list of objects that would not merge. Critical items are gates. Export to Excel and add owner and date columns, then review it in the weekly upgrade meeting. Keep the evidence (conversion logs, merge logs, build logs, reconciliation spreadsheets) linked to each item so audit and the business can follow the decisions.
- Do not skip the timed test upgrade
- Assign one owner per group
- Store logs with the checklist export
Where the upgrade work happens in EnterpriseOne
Most of the technical work runs from the deployment server. The Installation Planner defines the upgrade plan, then the Installation Workbench drives the workbenches in sequence: environment and data source setup, control table merges, Table Conversion Workbench for business data, and Specification Merge Workbench for central objects. Modified objects are then retrofitted in OMW, using Visual Compare to see what changed between your version and the new standard object. Packages are built in Package Build and deployed with Package Deployment, and the business services package is a separate build.
Worked example: sizing the conversion window
A 9.1 site on SQL Server with 400 million F0911 rows ran a test upgrade on a prod-size copy. The table conversions took 19 hours, longer than the 36-hour cutover weekend allowed once spec merge, package deployment and validation were added. The team archived closed years of F0911 and F0902 history before the upgrade, re-timed the conversions at 11 hours, and wrote the go/no-go point at hour 30. Reconciliation compared F0902 balances by company and fiscal year between source and target before the business signed off.
Version differences and gotchas
A 9.0 source upgrade has more table conversions than a 9.1 source, so do not reuse a 9.1 plan for 9.0. Retrofit is usually the largest effort: modified standard objects need comparison object by object, and custom objects in 55-59 can break where 9.2 changed table layouts. Retire unused customisations instead of retrofitting them. UDOs need their own test pass because they are not part of the OMW spec merge in the same way. Finally, a tools release upgrade is a separate exercise from an applications upgrade, though both are often done together.
- Check conversion lists for your exact source release
- Plan retrofit effort per object, not per project
- Retest UDOs and security as a separate stream
Frequently Asked Questions
What is involved in a JDE 9.1 to 9.2 upgrade?
An applications upgrade installs the 9.2 release on the deployment server and platform pack on servers, then runs control table merges, table conversions on business data and spec merges on central objects. Modified and custom objects are retrofitted, full packages are built and deployed, and the business tests and reconciles data before cutover.
How do table conversions work in JD Edwards?
Table conversions change business data tables to the 9.2 structure. The Table Conversion Workbench runs the conversion programs for your source release and writes logs for each. Time them on a prod-size copy, review every log for failures and reconcile row counts and totals on key tables before go-live.
What does the JDE simplified upgrade mean?
Oracle positions 9.2 as a release that stays current through continuous delivery of ESUs and tools releases instead of new major releases, and publishes guidance to streamline the move to it. The jump from 9.0 or 9.1 to 9.2 is still a full applications upgrade with conversions and retrofit; check the Oracle upgrade documents for your source release.
How long does a JD Edwards 9.2 upgrade take?
It depends on data volume, number of modified objects, and test scope. Typical projects run several months, with retrofit and testing taking most of the time. The cutover itself is sized from the timed test upgrade, so measure conversion and package times rather than estimating them.
If you want an on-prem AI assistant that helps your team compare objects, track retrofit decisions and answer questions about your 9.2 data, we can set that up on your servers.
Related Tools
JD Edwards Tools Release Upgrade Checklist
A phased checklist for moving JD Edwards EnterpriseOne to a newer tools release, from certification checks to post-cutover monitoring.
OracleJD Edwards Package Build and Deployment Checklist
Step-by-step checklist for building and deploying JDE packages: pre-build checks, build, deployment, verification and rollback.
OracleJD Edwards Go-Live Cutover Plan Worksheet
Plan each cutover task with an owner, start hour and duration, and see end times and total window length before the weekend arrives.
OracleJD Edwards Orchestrator Error Handling and Production Readiness Checklist
Check an EnterpriseOne orchestration before it goes live: what happens when a step fails, who it runs as, how it is monitored and scheduled, and how it is promoted.
More Oracle tools
See all- JD Edwards EnterpriseOne Private AI Layer Blueprint Generator
- JD Edwards EnterpriseOne AI Assistant Sizing and Value Calculator
- JD Edwards F4211 vs F42119 Sales Order Detail and History Columns Reference
- JD Edwards Inventory Tables Reference (F41021, F4111, F4105, F4108, F4100)
- JD Edwards EnterpriseOne System and Object Librarian Tables Reference
- JD Edwards EnterpriseOne 9.2 Tools Release History Reference
- JD Edwards AAI and DMAAI Reference (F0012, F4095)
- JD Edwards AP and AR Ledger Tables Reference (F0411, F0413, F0414, F03B11, F03B13, F03B14)
- JD Edwards Security Tables and Security Types Reference (F00950, F95921, F9312)
Keep exploring
Free tools
- JD Edwards EnterpriseOne 9.2 Upgrade Retrofit Effort CalculatorEstimate retrofit and test hours, cost and duration for a JD Edwards EnterpriseOne upgrade to 9.2 from your counts of modified objects, and see how much replacing mods with UDOs saves.
- JD Edwards EnterpriseOne 9.2 Tools Release History ReferenceTools releases of EnterpriseOne 9.2 with their Release 22 to 26 names, update months, headline tools features and certifications, plus how to check which tools release you run.
- JD Edwards Tools Release Upgrade ChecklistA phased checklist for moving JD Edwards EnterpriseOne to a newer tools release, from certification checks to post-cutover monitoring.
ERP fixes and how-tos
- How to Add a Private AI Layer to JD Edwards EnterpriseOne On-PremAdd a private AI layer to JD Edwards EnterpriseOne: AIS data service, Orchestrator, Security Workbench mapping, a local model and human approval.
- How to set up JD Edwards Orchestrator (step by step)Set up a working JD Edwards Orchestrator end to end: enable the AIS server, build a form or service request, wire it into an orchestration, and call it over REST.
- JD Edwards table conversion: how it works and how to run oneWhat a JD Edwards table conversion does to a JDE table's structure and data, when it runs in a package build, and how to run or design one manually.
Runs with your ERP
- Esker Accounts Payable with JD Edwards: Invoice Capture and PO MatchingEsker Accounts Payable captures invoices, matches POs and posts to JD Edwards 9.0 and later. Data flows, setup, pitfalls and where a private AI helps.
- Vertex Tax Connectors with JD Edwards EnterpriseOneHow Vertex calculates sales, use and VAT tax for JD Edwards EnterpriseOne and World, plus Oracle EBS and Cloud ERP: integration model, flows, setup, pitfalls.
- Prometheus Planning & Scheduling with JD Edwards EnterpriseOne maintenanceHow Prometheus Group's planning and scheduling tool works with JD Edwards EnterpriseOne maintenance: Gantt scheduling, time confirmation, setup and pitfalls.
AI on your ERP
- AI for JD Edwards EnterpriseOne Manufacturing, Without Leaving the F-Tables ExposedGrounded AI over JD Edwards EnterpriseOne Manufacturing: work orders, routings, and Orchestrator data, answered on-prem without sending F-table data to a public model.
- AI for JD Edwards EnterpriseOne, Built on Orchestrator and AISAdd AI to JD Edwards E1 9.2 using Orchestrator, AIS, and BSSV rather than screen-scraping. Ground a private LLM on F4211, F4111, and F0411 data.
Integrations
- How to add AI agents to JD Edwards EnterpriseOneHow to add AI agents to JD Edwards EnterpriseOne: Orchestrator and AIS as the tool layer, read-only first, human approval on writes, on-prem models.
- How to add an AI chatbot to JD Edwards EnterpriseOneAdd an AI chatbot to JD Edwards EnterpriseOne: grounded in ERP data via AIS, for planners, buyers and customers, and able to run fully on-prem.