JDE 9.1 to 9.2 Upgrade Retrofit Effort Calculator
This calculator estimates retrofit and testing effort for a JD Edwards EnterpriseOne upgrade to 9.2 from the number of modified Oracle objects and custom objects you carry. It also shows how much effort you avoid by replacing modifications with UDOs such as personalised forms and orchestrations before or during the upgrade.
Your numbers
Mostly carried forward, but each needs a check and a test.
1.5 adds 50% of retrofit hours for unit and regression testing.
Your results
Hours per object are planning rules of thumb for a first estimate, not Oracle figures. Replace them with your own averages from a pilot retrofit of 10 to 20 objects.
Total hours vs modified applications
Sweeps Modified interactive applications from 0 to 400, holding your other inputs fixed.
Get your retrofit estimate reviewed
Send us your object counts and merge report summary and we will review the hours per object and test scope for your upgrade plan.
Optional. The tool and every export work without this. No spam.
How to use it
Count the Oracle objects you have modified, by type, and your custom objects in system codes 55 to 59. The usual source is an object list from Object Management Workbench and the upgrade's specification merge reports, which show which modified objects were merged and which conflicted. Enter hours per object from your own history if you have it; the defaults are mid-range planning numbers. Pick the share of modifications you expect to retire by replacing them with UDOs, set the testing multiplier, rate and team, and read total hours, cost and elapsed weeks.
- Count only objects that are still used; Object Usage Tracking helps find dead mods
- Treat modified tables separately, they drive table conversions and data work
- Run a pilot on 10 to 20 objects and replace the defaults with real averages
The formula behind it
Modified object hours are the count of each type times its hours per object: applications times hours per application, plus UBEs, business functions and tables likewise. That figure is reduced by the share you replace with UDOs, because a mod retired is a mod you do not retrofit. Custom objects add a small carry-forward check each, since they are not overwritten by the upgrade but still need rebuilding, review and testing. Total hours are retrofit hours times the testing multiplier. Cost is total hours times the rate, and elapsed weeks are total hours divided by team size times productive hours per week.
Worked example
With the defaults: 120 applications at 4 hours, 150 UBEs at 3, 80 business functions at 5 and 30 tables at 6 give 1,510 hours of modified object work. A 10% UDO share removes 151 hours, leaving 1,359; 300 custom objects at 0.5 hours add 150, for 1,509 retrofit hours. Testing at 1.5 gives about 2,264 hours, roughly 215,000 dollars at 95 per hour, and about 24 weeks for three developers at 32 productive hours. Raising the UDO share to 40% saves about 906 hours.
Version differences and gotchas
A move from 9.1 to 9.2 is an application upgrade with specification merges and table conversions; once on 9.2, Oracle's continuous delivery model means later updates arrive as ESUs and Tools releases rather than another full upgrade, which is what people mean by a simplified upgrade path. Modified tables cost the most because table conversions must preserve your added columns and data. Visual Compare in the development client helps retrofit applications and reports by showing differences between your version and Oracle's. Do not forget interfaces, versions with changed processing options and BI Publisher templates in the test scope.
Frequently Asked Questions
How long does a JDE 9.1 to 9.2 upgrade take?
It depends mostly on the number of modified objects, the amount of testing and how much data the table conversions touch. Lightly modified sites can finish in a few months; heavily modified ones take much longer. Use this calculator with your object counts and a pilot retrofit to get a defensible estimate.
What is a table conversion in JDE?
A table conversion is a batch process that changes the structure or content of a table during an upgrade or data migration, for example adding columns Oracle introduced or moving data between tables. In an upgrade they run as part of the plan; modified tables need extra care so your added columns survive.
What is the JDE simplified upgrade?
After reaching 9.2, Oracle delivers new functionality through continuous delivery: ESUs and Tools releases applied to 9.2 instead of a new major release. Staying close to standard objects and using UDOs keeps those updates cheap, which is why reducing modifications pays off beyond the current upgrade.
How can I reduce JDE upgrade retrofit effort?
Retire unused mods found through Object Usage Tracking, replace form changes with personalisation and form extensions, move logic into orchestrations, and keep custom code in 55 to 59 objects instead of changing Oracle objects. Every modification removed lowers retrofit hours and the testing that comes with them.
If you want your team to ask what a JD Edwards modification does and where it is used in plain English on your own servers before you retrofit it, we can index your objects for that.
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.
Developer ToolsJD Edwards C Business Function Skeleton Generator
Generate the .h and .c skeleton of a JD Edwards EnterpriseOne C business function that reads one table record by key, returns a value and sets an error correctly.
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 World Custom Object Conversion Effort Calculator
Turn your count of custom RPG programs, DREAM Writer reports, screens and interfaces into build and test hours, cost and elapsed time.
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.0 / 9.1 to 9.2 Application Upgrade ChecklistA step-by-step checklist for an EnterpriseOne application upgrade from 9.0 or 9.1 to 9.2, from planning and table conversions to retrofit, packages and go/no-go.
- 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 EnterpriseOne AI Assistant Sizing and Value CalculatorEstimate peak load, GPUs, index size, hours saved and payback for an on-prem AI assistant on JD Edwards EnterpriseOne.
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.
- 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.
- 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.
Runs with your ERP
- 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.
- Oracle CPQ and JD Edwards EnterpriseOne: quote to sales orderHow Oracle CPQ integrates with JD Edwards EnterpriseOne: customer data into quotes, sales orders created from quotes, and status back, with setup and pitfalls.
- Cleo Integration Cloud with JD Edwards: EDI Connector and Migration PathCleo Integration Cloud has a prebuilt JD Edwards EnterpriseOne connector for EDI. See data flows, setup steps, pitfalls and Oracle Fusion migration notes.
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.