For many JD Edwards customers, customizations are both a necessity and a burden. They solve unique business challenges, but they also create ongoing maintenance headaches whenever Oracle releases updates. At BLUEPRINT 4D 2026, Lisa Tran of Monterey Mushrooms shared a practical, real-world approach to reducing that burden through strategic retrofitting and the gradual elimination of base program modifications.

Rather than treating retrofitting as a routine upgrade exercise, Tran views it as an opportunity to modernize customizations, replace code with JD Edwards extensibility tools, and reduce future maintenance requirements.

Why Retrofitting Matters

Monterey Mushrooms operates a highly specialized business. Beyond growing and distributing fresh mushrooms, the company also produces mushroom spawn, manufactures health and nutrition products, and manages its own transportation network. Those operational requirements have historically led to a significant number of JD Edwards customizations.

Like many organizations, Monterey accumulated a mixture of custom reports, custom applications, processing option enhancements, and modifications to standard JD Edwards programs. While some customizations support unique business requirements, others were created years ago to fill gaps that can now be addressed through modern JD Edwards capabilities.

Tran’s goal is straightforward: reduce the number of base program modifications while preserving business functionality.

That effort serves two purposes. First, it makes future upgrades and updates easier. Second, it allows the organization to take advantage of new Oracle enhancements without repeatedly retrofitting the same custom code.

Starting with What Oracle Already Provides

One of the most important lessons from Tran’s presentation was that retrofitting should begin with evaluation, not coding.

Instead of automatically merging existing modifications into updated Oracle objects, she recommends reviewing each customization to determine whether it is still necessary. In several cases, Monterey discovered that custom functionality had become redundant because Oracle now provided equivalent capabilities out of the box.

For example, one MRP-related customization simply replicated standard version-calling functionality already available within JD Edwards. By reverting to standard behavior, the customization could be removed entirely. Another modification that displayed associated descriptions was replaced through a form extension feature that now provides the same functionality without custom code.

These may seem like small wins, but eliminating even a handful of recurring retrofit candidates can significantly reduce long-term maintenance effort.

Using JD Edwards Extensibility Tools to Replace Custom Code

Much of Tran’s retrofit strategy centers on leveraging modern JD Edwards tools, particularly form extensions, logic extensions, orchestrations, and other User Defined Object (UDO) capabilities.

One example involved a Lot Master customization that automatically filtered out zero-quantity lots. Historically, this required a program modification. By using a logic extension during form initialization, Monterey was able to automatically enable the desired option and eliminate the need for future retrofits of that functionality.

Throughout the session, Tran repeatedly demonstrated how seemingly minor customizations could be recreated using extensibility tools rather than source code changes. Adding columns, making fields required, relocating fields on forms, defaulting values, hiding controls, and enforcing business rules were all candidates for replacement through extensions rather than modifications.

The cumulative impact is significant. Every customization moved into UDOs represents one less object that must be retrofitted when Oracle delivers updates.

A Deep Dive into a Complex Retrofit

The most detailed portion of the session focused on a heavily customized Work Order Completion program.

Tran selected this application because it contained a wide variety of modifications and represented an ideal test case for determining how much functionality could realistically be migrated out of base code.

The retrofit included:

• Additional columns and field renaming
• Required field validation
• Processing option-driven defaults
• Conditional field visibility
• Lot number generation logic
• Label printing controls
• Completion date calculations
• Location validation
• Memo lot enforcement
• Custom business rules tied to mushroom production processes

Many of these requirements were successfully recreated using logic extensions and orchestrations. For example, processing option values were retrieved and mapped into form controls, allowing fields to be automatically populated, enabled, disabled, shown, or hidden depending on business requirements.

Tran also demonstrated how logic extensions could perform calculations, query related data, evaluate conditions, and dynamically update form behavior. Complex scenarios involving pouch production, lot management, and date validation were recreated without directly modifying large portions of the application source code.

By the end of the project, she estimated that approximately 95% of the original customization had been successfully migrated away from traditional modifications.

The Challenges That Still Exist

While the session highlighted impressive progress, Tran was equally candid about the limitations she encountered.

Certain capabilities still cannot be fully replicated through existing extensibility tools. Examples included enabling QBE functionality on edit forms, modifying form interconnect behavior, and working around situations where Oracle formatting routines execute after custom logic extensions.

Date formatting and location formatting proved particularly frustrating. In several cases, Tran resorted to custom logic and workarounds because standard functions were either unavailable or difficult to access through the extension framework.

She also discovered a product bug related to disabling fields through logic extensions. Working with Oracle ultimately led to a fix, but it reinforced the reality that organizations adopting newer extensibility features may occasionally encounter edge cases that require creative solutions.

Lessons Learned from Three Years of Retrofitting

After three consecutive upgrade cycles, Monterey has developed a much clearer picture of where retrofit effort should be focused.

One key observation is that not every modified object changes during every update. By tracking retrofit candidates over multiple years, Tran identified a small group of objects that consistently required attention. Those became priority targets for modernization efforts.

She also emphasized the importance of understanding the business process behind every customization. Early in her tenure at Monterey, retrofitting required additional effort because she first had to learn both the code and the operational reasons behind it. Once that knowledge was established, identifying replacement opportunities became much easier.

Perhaps most importantly, Tran encouraged organizations to view retrofitting as a continuous improvement exercise rather than a compliance task. Every retrofit presents an opportunity to evaluate whether custom code still belongs in the system at all.

Moving from Maintenance to Modernization

The biggest takeaway from Tran’s presentation is that retrofitting no longer has to mean merging code line by line and hoping nothing breaks.

JD Edwards continues to expand its extensibility framework, giving customers more options for moving business logic out of modified applications and into configurable, upgrade-friendly tools. While not every customization can be eliminated today, many can.

Monterey Mushrooms’ experience demonstrates that a deliberate strategy of evaluating customizations, leveraging UDOs, and gradually reducing base program modifications can dramatically simplify future upgrades. The result is not just less retrofit work—it is a cleaner, more maintainable JD Edwards environment that is better positioned to take advantage of Oracle’s ongoing innovation.

Want more?

Explore more content and resources to help you get the most from your Oracle investment:

• Visit the Quest Learn Library for blogs, how-to demos, and on-demand sessions.
• Connect with peers in one of our Quest JD Edwards Community User Groups to swap stories, ask questions, and share tips with other users facing the same challenges.
• Bookmark LearnJDE for updates from JD Edwards development.

Not a Quest member yet? Join today and tap into the ultimate Oracle customer network.