Running Oracle? Find out exactly what you're overpaying. Free cost analysis, no commitment.
500+ enterprise clients · Est. 2016 · 15-min response · No commitment
JD Edwards EnterpriseOne 9.2 has been in Sustaining Engineering since December 2021. Oracle still collects 22% of your net licence value every year. The maths stopped making sense four years ago.
Unlike EBS or PeopleSoft, JDE's installed base — overwhelmingly in manufacturing, distribution, construction and asset-intensive sectors — is not rushing to Oracle Cloud ERP. Implementations are heavily customised. Integrations run deep. The business case for migration rarely survives contact with the actual project scoping exercise. The result: hundreds of organisations paying premium Oracle support for a product in sustaining status and no viable upgrade path that doesn't cost more than the next decade of support fees.
This guide covers what sustaining engineering means in practice, what third-party support covers for E1 9.2, version-by-version timelines, and the cost models that explain why TPS has become the default strategic position for JDE customers with no near-term migration appetite.
What Sustaining Engineering Actually Means for JDE
Oracle declared JD Edwards EnterpriseOne 9.2 in Sustaining Engineering in December 2021. The marketing language makes this sound like an extension of support. It is not. Sustaining Engineering removes almost everything that made the 22% annual fee defensible.
Under Sustaining Engineering, Oracle will not release new patches, fixes or updates unless they are already in development. They will not provide fixes for newly discovered security vulnerabilities. They will not certify JDE against new versions of operating systems, databases or third-party products. They will not provide regulatory updates for tax, legal or payroll changes — a significant exposure for multinational manufacturers running JDE's Payroll, Financials or Localisation modules.
What remains: you can still log support requests, and Oracle will attempt to answer them using existing documentation. You can still access previously released patches via Oracle Support. And you continue to pay 22% of licence value annually for this diminished service.
Third-party support providers step into exactly this gap. They provide the fixes, security patches, regulatory updates and expert guidance that Oracle has withdrawn — at 50–70% lower cost.
JDE EnterpriseOne Version Matrix
| Release | Premier Support Ended | Extended Support Ended | Current Status | TPS Available |
|---|---|---|---|---|
| E1 8.12 | Nov 2013 | Nov 2016 | Sustaining Engineering | ✔ Full TPS |
| E1 9.0 | Nov 2013 | Nov 2016 | Sustaining Engineering | ✔ Full TPS |
| E1 9.1 | Dec 2018 | Dec 2021 | Sustaining Engineering | ✔ Full TPS |
| E1 9.2 | Dec 2021 | N/A | Sustaining Engineering (active) | ✔ Full TPS |
All active JDE releases are in Sustaining Engineering. There is no version of JDE EnterpriseOne under Premier or Extended support. Every organisation paying Oracle support for JDE is already receiving the diminished sustaining-only service.
What's JDE Support Costing You?
We model your exact JDE licence value against TPS pricing in 15 minutes. No obligation, no sales pitch — just the numbers.
Get Your JDE Cost ModelWhat Third-Party Support Covers for JDE E1
For organisations running JDE EnterpriseOne on a standard stack — whether AIX/IBM i, Linux or Windows, with Oracle Database or SQL Server — third-party support provides comprehensive coverage across all application tiers.
Application Layer Coverage
TPS providers cover all EnterpriseOne modules — Financials (GL, AP, AR, Fixed Assets), Supply Chain Management (Procurement, Inventory, Sales Order, MRP/MPS), Manufacturing (Shop Floor, Work Orders, Product Costing, Quality), Human Capital Management (Payroll, HR, Benefits, Time and Labour), and Project Management (Contract, Billing, Equipment). Custom objects, customer-specific modifications and third-party integrations are included in scope — unlike Oracle's standard support which excludes customisations.
Technical and Infrastructure Coverage
- HTML Server and AIS (Application Interface Services) issues
- Orchestrator Framework (including custom orchestrations for integrations)
- JDE Tools release compatibility and patching guidance
- Oracle Database compatibility for versions in use (including 12c, 19c)
- Business Data network (BDN) replication issue resolution
- UBE (Universal Batch Engines) and report server support
- CNC (Configuration Navigation Customisation) configuration and troubleshooting
Regulatory and Tax Update Coverage
This is where the Oracle sustaining engineering gap creates the most immediate risk. Tax table updates for PAYE, VAT/GST, statutory payroll changes, electronic invoicing mandates (e.g. HMRC Making Tax Digital, Germany ZUGFeRD, SAF-T) — all are outside Oracle's sustaining engineering scope. TPS providers maintain dedicated tax and legislative update teams covering the major JDE deployment geographies including UK/Ireland, Germany, France, Netherlands, Australia, New Zealand and North America.
Oracle Support Cost Reduction Playbook
54-page guide: how Oracle support contracts are structured, what you're actually paying for, and the legal framework for switching to third-party support.
Download FreeJDE TPS Cost Model: Four Organisation Profiles
The following cost model is based on typical JDE EnterpriseOne deployments by net licence value (NLV). Oracle support is billed at 22% of NLV annually. TPS is typically priced at 8–12% of NLV — a 50–66% reduction on support costs alone.
| Organisation Profile | Est. JDE NLV | Oracle Annual (22%) | TPS Annual (10%) | Annual Saving | 5-Year Saving |
|---|---|---|---|---|---|
| Mid-size manufacturer (250 users) | £800K | £176,000 | £80,000 | £96,000 | £480,000 |
| Distribution group (500 users) | £1.8M | £396,000 | £180,000 | £216,000 | £1.08M |
| Engineering/EPC firm (800 users) | £3.2M | £704,000 | £320,000 | £384,000 | £1.92M |
| Large manufacturer (>1,500 users) | £6.5M | £1.43M | £650,000 | £780,000 | £3.9M |
These savings compound. If Oracle applies a 5% uplift in year two (a common renewal tactic), the Oracle support bill for a £1.8M NLV deployment rises to £415K. The TPS rate remains contractually fixed. The gap widens every year you stay on Oracle support.
Oracle's JDE Migration Pressure Playbook
Oracle's account management playbook for JDE customers follows a predictable pattern. Expect the following pressure tactics during your next renewal conversation.
Oracle Cloud ERP Migration
Oracle positions JDE as legacy and Cloud ERP as the only future. The reality: Cloud ERP requires complete re-implementation, not a migration. 80% of JDE customisations don't map to Cloud ERP modules without rebuild.
Tools Release Lock-In
Oracle pushes Tools Release upgrades at each renewal. Tools 9.2.x upgrades are substantial IT projects — not routine patches. Pressure to upgrade tools is pressure to consume IT budget that could fund three years of TPS.
Customisation Vulnerability Claims
Oracle support will claim your customisations make TPS impractical. This is incorrect. TPS providers specifically include customisation support in their contracts — unlike Oracle, which explicitly excludes it.
Security Threat Amplification
Oracle's sustaining engineering stance means they aren't releasing CVE fixes for JDE. Yet Oracle support teams will warn about security risks from non-Oracle support. The irony: TPS providers release security patches Oracle won't.
Ready for an Honest JDE Assessment?
We've helped manufacturers running JDE 9.2 cut support costs by £200K–£800K annually. The conversation takes 15 minutes.
Speak to a JDE SpecialistYour Four Strategic Options
Switch to Third-Party Support
Best for: Organisations with stable E1 9.2 deployments, no near-term cloud migration, and meaningful NLV. Immediate 50–70% saving. Full coverage maintained.
Negotiate Oracle Contract
Best for: Small NLV deployments where TPS economics are less compelling. TPS competition gives you real leverage — Oracle has discounted 15–25% on renewal when a TPS switch is credible.
Selective Modernisation
Best for: Organisations with specific modules (e.g. HCM) where Oracle Cloud offers genuine value, while keeping E1 core on TPS. Run TPS on E1 core while selectively adopting cloud for HR/Payroll only.
Planned Migration with TPS Bridge
Best for: Organisations with a genuine 3–5 year migration roadmap. Switch to TPS now, use savings to fund the migration project, retire E1 on your timeline — not Oracle's.
Sector-Specific Considerations
Manufacturing and Assembly
JDE's manufacturing modules — Shop Floor, Work Orders, Quality Management, Product Costing — are mature, stable and deeply integrated with MES, SCADA and PLM systems in many production environments. Disrupting that integration via a cloud migration creates operational risk that no IT director or plant manager will accept lightly. TPS preserves the production-critical integration layer while cutting support cost.
Distribution and Logistics
JDE's Transport Management and Warehouse Management modules are widely deployed across third-party logistics and distribution groups. Many integrations run to carrier systems, EDI hubs and customer portals via custom business functions. TPS providers' explicit coverage of custom code means the integration layer is protected — not left to the customer to maintain independently as Oracle's sustaining engineering position implies.
Engineering, Procurement and Construction
EPC firms use JDE's Project Management, Contract Billing and Service Management modules across capital project cycles. Project-linked revenue recognition, multi-currency project accounting and contract compliance workflows are frequently customised. TPS preserves these configurations without the risk of a forced Tools Release upgrade disrupting a live project billing environment.
The Transition Process: What to Expect
- Technical Assessment (Week 1): GoVendorFree reviews your E1 tools release, modules in scope, database version, OS platform, customisation inventory and current CNC configuration. No access to production systems required at this stage.
- Contract Negotiation (Weeks 1–2): TPS contract drafted with explicit scope covering all in-use modules, custom objects, regulatory updates and response SLAs. Fixed annual fee — no Oracle-style uplift clauses.
- Knowledge Transfer (Weeks 2–3): GoVendorFree engineers receive documentation, existing Oracle SR history (where available) and CNC topology diagram. Deep dive on any active critical issues.
- Oracle Contract Termination (Week 4): Oracle support terminated with appropriate notice period. Oracle must accept termination — they cannot force continued support of a product in sustaining engineering.
- Go Live (Week 4–5): GoVendorFree support goes live. Typical transition takes 4–5 weeks from contract signature to active support.
Calculate Your JDE Saving
Tell us your Oracle support invoice total. We'll show you the three-year saving and what full TPS coverage looks like for your specific E1 deployment.
Start the Assessment