Hosted by Chandra Wobschall and Paul Houtkooper
Hello, JDE Connection community! We’re back and we’re thrilled to continue our chat with Pete Cotton from IREX Services, LLC. Pete’s straight forward approach to simplifying your customization backlog for EnterpriseOne sparked some serious thoughts on our end, and we hope they’ll do the same for you!
Extending UDOs: A New Era for Customization
One of the standout parts of this episode was Pete’s discussion on the power of User Defined Objects (UDOs) to replace customizations in a smart, efficient way. Paul kicked off the discussion by highlighting the flexibility of UDOs in JD Edwards for customizing forms and processes without diving into core code. It’s clear that UDOs like form personalizations, logic extensions, and orchestration are only becoming more valuable with each release.
We’re especially excited about how form extensions can add rows and exits without altering the codebase. Pete noted that even basic JD Edwards features, like data dictionary jargon codes for renaming fields, can prevent unnecessary customizations. Sometimes, the tools to simplify are already at our fingertips—we just need to use them!
Tackling the Tougher Customizations: What About Batch Jobs?
While UDOs offer solutions for interactive applications, Pete pointed out that batch processes (or UBEs) often remain highly customized and tough to tackle. Paul hinted at some possible research the development team may be doing into addressing UBE customizations through the UDO framework—a potential game-changer if it comes to fruition.
Until then, Pete recommended creative workarounds, like linking orchestrations or notifications to UBEs. These strategies, while not complete de-customizations, can significantly reduce the manual workload during updates. It’s a start, and sometimes, incremental wins are the best way forward.
Don’t Forget the De-customization Tool!
If you’re new to de-customization, JD Edwards offers a built-in customization analyzer tool that provides an excellent starting point. As Paul explained, this tool scans your environment, identifies common customizations, and suggests UDOs as possible replacements. It’s not a magic fix for everything, but it’s one more weapon in the fight to lighten the customization load.
Catalog, Replace, and Repeat
Pete emphasized that de-customization isn’t a one-time project—it’s a lifestyle choice. At IREX, they review their customizations annually, cataloging them, evaluating their necessity, and exploring UDO replacements where possible. It’s about chipping away at the problem over time, rather than trying to clear it all at once.
Change Control and Documentation: The Secret Weapons
Another critical piece of Pete’s approach is creating a culture of change control. As Paul explained, documenting the “why” behind each customization is as important as tracking “what” it does. By understanding the business purpose, future team members have a clearer sense of whether a customization is still relevant.
Change control also means bringing other departments into the discussion, helping everyone understand the benefits of a streamlined JD Edwards system. Pete shared his experience of fostering this within IREX, stressing how crucial it is to involve all stakeholders, from developers to business analysts, in the process.
It’s a Marathon, Not a Sprint
As we wrapped up, Pete reminded us that de-customization is a long-term commitment. By approaching it in stages and making it a part of your company culture, you’re investing in a JD Edwards environment that’s flexible, efficient, and, ultimately, easier to upgrade. After our chat with Pete, Chandra was more motivated than ever to bring these practices into her own organization.
Final Thoughts
De-customization can feel overwhelming, but, as Pete said, the most important step is simply to start. Whether it’s cataloging what’s there, experimenting with UDOs, or rethinking how you document customizations, every small step moves you toward a cleaner, more agile JD Edwards environment.
We close out our discussion with Pete with another Midwestern phrase that pays tribute to our guest, which we honestly hope you enjoy.
Thank you for tuning in to this episode of The JDE Connection! We hope this two-part series with Pete has been as inspiring for you as it was for us. If you have questions, ideas, or feedback, reach out to us at TheJDEConnection@questoraclecommunity.org.
Until next time, keep learning, sharing, and, as always, laughing with us.
Toodles,
Missed an episode? Check out the full episode list!
Learn More
Quest Oracle Community is where you learn. Ask questions, find answers, swap stories and connect to other JD Edwards customers and product experts in the JD Edwards Community, where you can also check out what’s happening in the Business Analyst SIG.