know.2nth.ai Tech MuleSoft
tech · Oracle legacy apps · Skill Leaf

The old estate isn't going anywhere until at least 2036.

A large part of what runs South African enterprises is genuinely old Oracle software — E-Business Suite, Oracle Forms & Reports, PeopleSoft, JD Edwards, Siebel, Hyperion. The reflex is to panic about end-of-life. The facts say otherwise: these lines carry Premier Support through at least 2036. That changes the question from "when must we rip it out?" to "how do we put modern interfaces and agent access on top of it without a decade-long rewrite?" — which is exactly what the rest of this cluster is for.

EBS 12.2 PeopleSoft · JDE Support ≥ 2036 Modernise on top Forms & Reports

Applications Unlimited — the estate that predates the cloud.

Under the banner Oracle calls Applications Unlimited sit the on-premises application suites many organisations still run their core operations on: E-Business Suite (financials, supply chain, HR), PeopleSoft, JD Edwards EnterpriseOne, Siebel CRM, and Hyperion — plus the older Oracle Forms & Reports UI technology beneath a lot of custom EBS screens. These are systems of record with decades of embedded process and customisation, sitting on an Oracle database.

The 2036 runway, and what it changes.

Oracle has extended Premier Support for E-Business Suite 12.2 through at least 2036, aligning it with the other Applications Unlimited lines — JD Edwards EnterpriseOne, PeopleSoft, Siebel, Hyperion — which carry the same commitment. Since June 2018 EBS 12.2 has been on a Continuous Innovation model: ongoing updates without a forced major upgrade. The practical consequence is that the "you must re-platform now or lose support" pressure is largely manufactured — for these systems you have roughly a decade of runway, which is enough time to modernise deliberately rather than in a panic.

What the runway is for

A decade of support is a window to add value on top, not a reason to freeze. It buys time to put modern web UIs, REST integration, and agent access onto the estate incrementally — and to make any eventual move a considered one rather than a forced march. The runway is the opportunity; the mistake is treating it as permission to do nothing.

The same seams the rest of this cluster describes.

The pragmatic path is to keep the transactional core and add modern surfaces over it, exactly as the other Oracle leaves lay out. APEX builds new web UIs on the same database — the standard answer for replacing a Forms screen without touching the data model. ORDS exposes the estate as REST and, from 26.2, as an MCP surface agents can call. Oracle's own Visual Builder (VBCS) and Oracle Integration Cloud sit in the same space for lower-code UIs and integrations. None of these require re-implementing the system of record; they wrap and extend it.

Supported is not the same as strategic.

Two things are true at once, and a good decision holds both. The estate is supported and modernisable on top — and Oracle's own long-term recommendation is to move to Fusion Cloud ERP, which is a re-implementation, not an upgrade: multi-year, expensive, and disruptive to embedded process. "Supported through 2036" is a runway, not an argument for never moving; a system frozen for a decade accrues its own risk in skills, security posture, and integration debt.

One component deserves singling out: Oracle Forms & Reports is genuinely dated UI technology, and even if you keep the EBS database for years, the Forms front-end is the part worth modernising first — that is the clearest, highest-value APEX-on-top project in most estates. The honest position: use the runway to modernise the experience and open the estate to agents now, and make the bigger re-platform-vs-stay call as a deliberate strategy, not a deadline panic. And keep the ownership lens in view — a supported estate is still rent on someone else's technology, in dollars.

Big estates, a real budget question, and residency.

SA banks, insurers, and government departments run large EBS and PeopleSoft estates, and the live budget question in Johannesburg is precisely the three-way one: modernise on top, re-implement on Fusion, or stay put. The 2036 runway means the honest default for most is "modernise on top now, decide the big move later" — it preserves optionality and defers the largest spend. Residency stays answerable throughout: these systems can run on-premises or in the OCI Johannesburg region, so opening them to agents via ORDS need not send anything offshore. The estate that felt like a liability is, read correctly, a decade-long asset you can make modern in place.

Where the legacy estate links in the tree.

Primary sources only.