How do we manage and reduce the complexity of PeopleSoft customizations?
-
Posted by Quest Customer Learning Team
- Last updated 11/13/25
- Share
This session was presented at RECONNECT Dive Deep 2025.
The management of PeopleSoft customization involves at first step – to be able to measure the extent of customizations we have in our estate. The customizations could be in objects residing within Application Designer and other objects outside it like SQRs, Cobols etc. We need to have a customization repository to track the extent of customization, why they were done, what value they added and to store metadata for them. This would help us track what customizations are strategic and what are the ones we could reduce/remove. In addition we must track the decisions taken at times of updates/upgrades/selective adoption – when encountering a customization – what was the decision taken – whether that customization was reapplied, whether it was retired, or whether it needed a rework to be kept customized. Time spent doing the actual retrofit should also be recorded to help rough order of magnitude for future upgrades/updates. In context of reducing the complexity – thankfully there are many tools available now like EMF, Dropzones, AE Pluggins, Page Field Configurator, Form Builders etc that help us move to configuring rather than customizations.
Watch the full-length video
You’ve reached the ultimate Oracle customer network—exclusively for Quest Corporate and Professional members.
Join Quest to unlock access to strategic content centers, event replays, exclusive programming, and expert insights—all designed to help Oracle users like you go further, faster.
Whether you're on JD Edwards, PeopleSoft, or Oracle Cloud, Quest connects you with a powerful peer network and Oracle experts so you can make smarter decisions, drive innovation, and get more from your investment.
Quest is where Oracle customers connect, learn, and lead with confidence. Ready to join them?
