PeopleSoft kept current, one update image at a time.
PeopleSoft isn't going away. Oracle lists Premier Support for its 9.2 applications through at least December 2037. The real problem is falling behind on update images and PeopleTools until catching up feels like a reimplementation. We keep teams current, and we help those who've decided to move.
Oracle lists Premier Support for the PeopleSoft 9.2 Continuous Innovation releases through at least December 2037. Security is the part that moves. October's patch update brought 109 PeopleSoft security patches, and 41 of the flaws need no login. The next one is due 19 January 2027. We apply update images, upgrade PeopleTools and keep those patches on schedule.
you probably need this if
The last update image went in more than a year ago, and every month the catch-up gets bigger.
The compare report flags the same few hundred custom objects on every image, and they get retrofitted all over again.
PeopleTools patching waits on one administrator's availability.
terms on this pageenvironmentdefinitionThe thing that holds a set of apps, flows and agents plus their database. Admins see one per team in the list when it's Dataverse for Teams.explained in a field note →Premier SupportdefinitionThe first stage of Oracle's support policy. You get CPU patches here and in Extended Support, which you pay extra for. Once both end, the patches stop coming.explained in a field note →
10 Jun 2026June 2026 PeopleTools Security Alert, exploited CVE-2026-35273 lets an attacker run code on PeopleTools 8.61 or 8.62 without a login, and Oracle rated it 9.8. It came as a Security Alert outside the quarterly cycle. CISA lists it as exploited and used in ransomware, so check it's applied on every environment first.
07 Aug 2026Premier Support through at least Dec 2037 Covers the Continuous Innovation releases of CRM, Campus Solutions, ELM, FMS/ESA/SCM, HCM and Portal Solutions. Oracle can push the date out a year at a time, and says it has no plans to end Premier Support for them.
07 Aug 2026Latest update images Oracle's support policy lists HCM image 55 from May 2026 and FMS/ESA/SCM image 57 from July 2026. Campus Solutions has already moved past the policy's image 38, and Oracle's PeopleSoft portal now offers CS Update Image 39.
20 Oct 2026October 2026 CPU: 109 PeopleSoft patches Oracle's October Critical Patch Update has 109 new PeopleSoft security patches, and 41 of those flaws can be hit over the network without a login. The worst is a 9.8 in the Logstash that PeopleTools bundles, CVE-2026-33466. PeopleTools 8.61 to 8.63 are all affected, so test and DR copies need it too.
20 Oct 2026PeopleTools 8.61.24 patch and 8.63 Oracle put out the PeopleTools 8.61.24 product patch on 20 October 2026, for OCI and on-premises sites. If you're on 8.61, that's the patch level to test toward. October's patch update also lists 8.63 as supported, next to 8.61 and 8.62, so decide which line you'll run next year.
today · Nov 09, 2026
19 Jan 2027aheadNext Critical Patch Update: 19 Jan 2027 Oracle's next quarterly patch bundle is due 19 January 2027. Oracle also lists monthly Critical Security Patch Updates on 17 November and 15 December 2026. Book the January test window now, on the clone you used for October, so the patches don't sit for another quarter.
the story · oracle peoplesoft estate
From the first call to a setup your own team can run.
Here's what usually prompts a call about your Oracle PeopleSoft estate, what we do about it and in which order, and where you end up.
01 · where it hurts02 · what we change03 · how it runs04 · where you end up
incident board · oracle peoplesoft estate3 open
openThe last update image went in more than a year ago, and every month the catch-up gets bigger.
recurringThe compare report flags the same few hundred custom objects on every image, and they get retrofitted all over again.
blockedPeopleTools patching waits on one administrator's availability.
exposure
PUM image updatesPeopleTools upgradesCustomization reductionFluid UI and self-serviceIntegrations and identityRun support and staffing
PSERPOAM
startrehearsehandover
Currency review
Change package plan
Retrofit and rehearse
Apply and hand over
we are here
ready to hand over
Payroll is back on current tax updates.
Campus Solutions still runs, and its person data is clean.
Currency report showing which image and PeopleTools patch you're on, and how far behind…
A custom object register. Each object gets a call: keep it, move it to configuration, or…
chapter 01 · where it hurts
Why teams reach out
The last update image went in more than a year ago, and every month the catch-up gets bigger.
The compare report flags the same few hundred custom objects on every image, and they get retrofitted all over again.
PeopleTools patching waits on one administrator's availability.
chapter 02 · what we change
How we solve it
PUM image updates
PeopleTools upgrades
Customization reduction
Fluid UI and self-service
Integrations and identity
Run support and staffing
chapter 03 · how it runs
Our approach
Currency review
Change package plan
Retrofit and rehearse
Apply and hand over
chapter 04 · where you end up
What changes
Payroll is back on current tax updates.
Campus Solutions still runs, and its person data is clean.
Currency report showing which image and PeopleTools patch you're on, and how far behind the latest you've slipped
A custom object register. Each object gets a call: keep it, move it to configuration, or retire it.
what we do
Our Oracle PeopleSoft work
6 kinds of Oracle PeopleSoft work, each run by engineers who have done it on live tenants.
Selective adoption from PeopleSoft Update Manager images, with change packages built around the fixes and features you need, and customization retrofit tracked object by object.
Moves to current PeopleTools releases and patches, using DPK-based infrastructure, with Application Designer compare reports and a timed rehearsal on a production clone.
We compare custom objects against delivered functionality in recent images, replace what we can with Page and Field Configurator, Event Mapping or Drop Zones, and retire the rest.
Fluid navigation, homepages, tiles and self-service pages configured so employees and students stop asking for the classic screens.
Integration Broker and REST services, PeopleSoft feeds into SailPoint or Oracle Identity, and extracts to Snowflake or another warehouse.
PeopleSoft developers, functional analysts and PeopleSoft administrators, on contract, contract-to-hire or permanent terms.
capability 01 / 06in production
PSERPOAM
PUM image updates
Selective adoption from PeopleSoft Update Manager images, with change packages built around the fixes and features you need, and customization retrofit tracked object by object.
Moves to current PeopleTools releases and patches, using DPK-based infrastructure, with Application Designer compare reports and a timed rehearsal on a production clone.
We compare custom objects against delivered functionality in recent images, replace what we can with Page and Field Configurator, Event Mapping or Drop Zones, and retire the rest.
We pieced these together from Oracle PeopleSoft situations that come up a lot. They're patterns. You won't find a specific client in them.
case file 01
HCM image 41 with payroll tax updates now overdue
composite · not a client story
Beforethe situation
PeopleSoft HCM sits on an image from several years ago because each catch-up stalled on retrofit. Payroll tax updates are stacking up, and the compare report shows hundreds of custom objects in conflict.
What we dothe work
We build a change package for the required tax updates first and retrofit only the objects it touches. Then we move the most frequent conflicts to Event Mapping or Page and Field Configurator so later images hit fewer custom objects.
Afterwhere you end up
Payroll is back on current tax updates. Later images still run into some custom conflicts, but the list gets shorter each time.
case file 02
Campus Solutions staying put while HR moves to Workday
composite · not a client story
Beforethe situation
A university is moving HR to Workday but keeping Campus Solutions for students. Right now student employees, faculty records and the identity feeds all hang off PeopleSoft HCM.
What we dothe work
We map every data flow between HCM and Campus Solutions and design the Workday-to-Campus Solutions interfaces. Identity feeds are re-pointed so students come from Campus Solutions and employees from Workday, with tests for people who are both.
Afterwhere you end up
Campus Solutions still runs, and its person data is clean. Nobody who's both a student and an employee lost access when HR left PeopleSoft.
We don't start a step until the last one has produced something you can check.
step 01
Currency review
First we write down where you are: image level, PeopleTools release and patch, custom object counts by type, and every integration. Then we line that up against Oracle's latest images and PeopleTools patches, so you can see how far behind you actually are.
step 02
Change package plan
We plan the change packages around the regulatory updates you have to take and the features people have asked for. Each package lists the custom objects it touches, so retrofit doesn't surprise anyone.
step 03
Retrofit and rehearse
Customizations move to configuration where they can. The rest get retrofitted. Then we run the full update on a clone, write down how long each step took, and test the batch processes.
step 04
Apply and hand over
We apply the update to production with your team, then check integrations and batch runs afterward. Your administrators keep the change package history and the retrofit notes, so the next image doesn't start from scratch.
ai on oracle peoplesoft
Where AI fits on Oracle PeopleSoft, and where it needs guardrails.
PeopleSoft has little vendor AI to configure. Oracle frames PeopleTools 8.63 around enabling AI securely, alongside search and security, but Oracle doesn't currently offer a PeopleSoft agent framework or MCP server. The useful AI work is around the platform: documenting PeopleCode, speeding up PUM retrofits and letting agents call Integration Broker services.
AI agentasks for data or an action
Scoped identityonly the access it needs
MCP serverthe one door into the platform
Logged, approveda person signs off on writes
PSOracle PeopleSoftdoes the work
Oracle doesn't have a PeopleSoft MCP server, as far as we found, so you'd own one. It can wrap Integration Broker REST service operations and sign in as a dedicated PeopleSoft user ID per agent, with permission lists that allow only those operations. Log every call. Writes go for approval.
Documenting customizations
Years of PeopleCode, Application Engine programs and SQR reports often have no documentation. AI can describe what each custom object does and flag any that recent update images now deliver. We run that before anyone decides to retrofit or retire them.
PUM retrofit and test generation
Every PeopleSoft Update Manager image means another round of comparing customizations against delivered code. We use AI to summarize the compare reports and draft test scripts for the pages and processes affected, and a functional analyst confirms them.
Batch and integration log triage
After failed runs, Process Scheduler and Integration Broker logs pile up. We export them and let a model group the errors and suggest likely causes for the on-call engineer. It never reads the production database.
Agents through Integration Broker
Integration Broker can publish REST services, and agents call PeopleSoft through those. Each agent gets its own user ID with a narrow permission list, and we expose only the service operations it needs. Hires, terminations and payments still go to a person for approval.
architecture
Where PeopleSoft sits in a campus or HR estate
People records start in PeopleSoft HCM or Campus Solutions. From there they feed identity governance, so access follows hires and leavers. Finance data goes to the ledger, and table extracts land in the data warehouse for reporting.
use cases
Typical Oracle PeopleSoft projects
The work teams usually bring us, and the platforms Oracle PeopleSoft has to talk to while we do it.
PEO-01You're several update images behind and every catch-up feels like an upgrade
common request
PEO-02PeopleTools is near the end of its patch support window
common request
PEO-03Customizations turn every new image into another retrofit project, and the same objects come up each time
common request
PEO-04Staff and students still do self-service on classic pages, and nobody has moved them to Fluid
common request
PEO-05Nobody has confirmed the June PeopleTools alert fix and October's patches are on every environment
common request
PEO-06You're weighing staying on PeopleSoft against a move to Workday or Oracle Cloud, and need numbers for both
common request
These are working documents, written against your configuration, so your team can run them without us.
tests01
Currency report showing which image and PeopleTools patch you're on, and how far behind the latest you've slipped
yours to keep
inventory02
A custom object register. Each object gets a call: keep it, move it to configuration, or retire it.
yours to keep
plan03
Change package plan that starts from the regulatory updates you can't skip and adds the features people asked for
yours to keep
runbook04
Runbook for the PeopleTools upgrade, with the timings we recorded rehearsing it on a clone
yours to keep
design05
Design for the identity feed, so hires and leavers in PeopleSoft reach your governance platform
yours to keep
document06
Scoring of each process and customization for stay or move, so leadership has numbers to argue over
yours to keep
talent and delivery · oracle peoplesoft
Certified engineers, wherever you need them.
Some clients want a project team, some want a couple of engineers on theirs. Either works. Onsite, nearshore or offshore, with handovers across time zones that keep things moving.
Put these to anyone bidding on your Oracle PeopleSoft work. The ones who've done it answer differently from the ones who've read about it.
Q1
Which images carry this year's tax and regulatory updates, the ones we can't skip?
Selective adoption lets you skip a lot, but never regulatory updates. They set the minimum cadence, and the plan should be built from them outward.
Q2
In the latest image's compare report, how many of our custom objects clash with delivered ones?
Compare report conflicts are what drive retrofit effort. If you know the count and the repeat offenders, you can see where moving changes into configuration pays off.
Q3
Of all our customizations, which ones could move to Event Mapping, Drop Zones or Page and Field Configurator?
A change that sits outside delivered code survives the next image with far less retrofit. Do that enough times and staying current gets cheaper.
Q4
Over five years, what does staying on PeopleSoft cost us, and what does moving cost?
Oracle lists Premier Support through at least 2037, so staying is a supported choice. Make the call on cost and fit. Worry about end of support shouldn't be what decides it.
Q5
If HR moves off PeopleSoft but student records stay, what happens to our identity feeds?
People who are employees and students at once are where this usually breaks. Their access needs its own rules, and its own tests.
Q6
Is the CVE-2026-35273 fix on every PeopleTools 8.61 and 8.62 environment, test and DR included?
CISA lists that no-login flaw as exploited and used in ransomware. A test copy someone forgot about is still a way in.
01Is PeopleSoft still supported, and until when?
Yes. Oracle's Lifetime Support Policy gives the PeopleSoft 9.2 Continuous Innovation releases Premier Support through at least December 2037. You don't upgrade to get new features anymore, because they arrive in update images. Staying supported mostly means applying those images and keeping PeopleTools patched.
02What's in Oracle's October patch update for PeopleSoft, and what do we patch first?
It has 109 new PeopleSoft security patches, and 41 of the flaws can be exploited over the network without a login. The worst is a 9.8 in the Logstash component that PeopleTools bundles, so start there. PeopleTools 8.61 to 8.63 are affected. The next quarterly update is due 19 January 2027, so book that test window now.
03Do we need to apply every update image?
No. Images are cumulative, and with selective adoption you take the fixes and features you need. The ones you can't skip are regulatory updates such as tax and payroll changes. We build change packages around those and add the features the business has asked for.
04How do we cut the retrofit effort on each image?
Stop customizing delivered objects where you can. With Page and Field Configurator, Event Mapping and Drop Zones, many changes can live outside delivered code, and images apply with fewer compare conflicts. We go after the objects that appear in every compare report first.
05Should we stay on PeopleSoft or move to Workday or Oracle Cloud?
That depends on how much your processes lean on PeopleSoft customizations and whether you can live with vendor-driven updates. Cost matters too. Plenty of institutions stay because Campus Solutions or a complicated payroll suits them well. We score the customizations and processes before recommending anything.
06How long does a PeopleTools upgrade take?
It depends on the number of environments, custom PeopleCode and integrations, and how far you're jumping. The upgrade itself runs on a clone first so we can time it, and testing integrations and batch processes usually takes the longest.
07Can you provide PeopleSoft developers on short notice?
We place PeopleSoft developers, functional analysts and admins on contract, contract-to-hire or permanent terms. Some sit onsite with your team in the US. Others work nearshore or offshore, across time zones.
services
Related services
Projects on Oracle PeopleSoft usually end up touching one of these, so they're worth a look.
