PeopleSoft & JD Edwards licensing — acquired products, inherited metrics, underused leverage.

How are PeopleSoft and JD Edwards licensed?

Both are licensed principally by Application User and Employee, with custom metrics such as $M in revenue for selected modules. The Application User metric counts authorised users, exactly as in E-Business Suite. The Employee metric is different and more dangerous: it counts the entire population a module serves — every employee processed by an HR or payroll module — not the handful of staff who operate the screens. Both suites also bundle the same restricted-use Oracle Database Enterprise Edition and Fusion Middleware, with the same boundary rules. And both sit under Oracle's Applications Unlimited support umbrella, which is the single most underused piece of leverage in the estate.

Why is the Employee metric so easy to under-declare?

Because growth moves the count without anyone touching the system. An Employee-metric module is licensed for the size of the workforce it serves at contract time; when headcount rises through hiring or an acquisition, the licensed quantity must rise with it. There is no log-in event to flag the change, so the band is crossed silently and only surfaces when Oracle reconciles your licensed Employee count against current payroll headcount. The table shows how the three metric families behave under organisational change.

Are PeopleSoft and JD Edwards being end-of-lifed?

No — and the sales narrative that they are is the lever Oracle uses and buyers fail to counter. Under Applications Unlimited, Oracle commits to Premier Support for PeopleSoft and JD Edwards EnterpriseOne with roadmaps extending into the 2030s, and JD Edwards runs a continuous-delivery model rather than big-bang upgrades. That means a migration to Oracle Fusion Cloud is optional. The credible alternatives — stay on Premier Support, or move to third-party support such as Rimini Street at roughly half the maintenance cost — are real, and naming them changes the renewal conversation entirely.

Does the restricted-use rule apply to PeopleSoft and JDE too?

Yes, identically. The Oracle Database Enterprise Edition and WebLogic that ship with PeopleSoft and JD Edwards are restricted-use: they may run only the licensed application. PeopleSoft estates are especially prone to the breach because reporting and analytics are often bolted directly onto the application database, and integration hubs write to custom schemas in the same instance. Each of those converts a bundled entitlement into a full-use database liability — read the same way in DBA_FEATURE_USAGE_STATISTICS as any other Oracle database. The mechanics are in our Oracle Database options guide, and the middleware side in WebLogic & Fusion Middleware licensing.

What does a clean PeopleSoft / JDE position look like?

Four parts. First, a metric inventory that pins each module to its actual metric and current count — Application User from the security tables, Employee from payroll headcount, revenue bands from finance. Second, a true-up forecast that anticipates band crossings from growth or M&A before Oracle finds them. Third, the same restricted-use boundary discipline you apply to every Oracle database, with reporting and integration moved off the bundled instance. Fourth, a renewal strategy built on the Applications Unlimited support runway, with third-party support modelled as a live alternative — holding that support runway as leverage is the heart of our Oracle negotiation work. Get those right and the "modernise or lose support" pitch loses its force. The cross-cutting playbook is in our Oracle audit defence guide.