A Closer Look at When to Upgrade vs Re-Implement to EBS 12.2
You’ve made the decision to upgrade to EBS 12.2, and you’re ready to take advantage of the Continuous Innovation delivery model. Now, you have another choice to make: How will you move to EBS 12.2?
Choosing between an upgrade or re-implementation can have a huge impact on your new EBS 12.2 system and what your business gets out of it. That’s why it's vital you understand the difference between the two methods—because each comes with its own unique benefits, features, and challenges.
To help you navigate which method is right for your business, here’s a breakdown of what you can expect from an upgrade or a re-implementation—and how to assess your best move.
What is involved in an upgrade?
When choosing to upgrade to EBS 12.2, you’ll encounter two distinct ways to go about it: Technical and functional.
Option One: A Technical Upgrade
The path of least resistance, technical upgrades are the fastes t, least costly, and least disruptive upgrades. Put simply, a technical upgrade keeps the software on the same platform and only implements changes to business processes required by the software.
A typical tech upgrade consists of upgrading to a new version/relsease of the software to enhance or expand current functionalities. For example, functional enhancements achieved in a technical upgrade would improve the capabilities of the existing applications and improve the overall capabilities of the platform.
This type of upgrade will also allow you to move to EBS 12.2 and keep your existing data. So things like existing custom reports, programs, and third-party software interfaces can continue to function with minimal changes.
Because of this, a technical upgrade also yields a shorter pay to a 12.2 environment.
However, if you choose a technical upgrade, you’ll use Oracle-provided scripts that convert your data from the current release to the latest release. That means all configurations and all modules that existed in the original instance remain the same, and at the end of the day, your new EBS 12.2 will still reflect the transactional processing of an older environment (like 11.5, for example).
Option Two: A Functional Upgrade
Functional upgrades offers some of the advantages of a technical upgrade (like speed and minimal disruption), but added benefits. This includes selected strategic configurations, new functionality process designs, and new technical features.
Compared to a technical upgrade, the new applications found in a functional upgrade can supply your company with an added competitive advantage. EBS 12.2, for example, has new and enhanced features and applications that are not available in older versions. These applications can help eliminate manual or custom-coded processes, for example, and drive your business forward.
What is involved in a re-implementation?
A re-implementation is a mix of functional and technical upgrades, along with extensive business process modeling, complex technical redesigns, and new module implementations. A re-implementation is sometimes called a transformational upgrade or complete migration to a new environment, and it reflects a major change in how your organization uses the system as a whole.
For EBS customers, data is extracted from the current environment, transformed, and loaded into a new environment. That new environment is a new instance of Oracle software that has been installed from scratch, and all modules have been reconfigured. During a re-implementation, a company generally chooses to load only one year’s worth of data.
It’s important to note that even though a re-implementation is still an EBS-to-EBS upgrade, there are big enough changes in the technical architecture and functionality to warrant the classification of a migration.