We know, we know, your Oracle E-Business Suite (EBS) needs modernization but you’re figuring out which option is best for your company’s unique needs. For years, Oracle has been pushing for modernization in different ways, but ultimately, we all know the end goal is the cloud. In the meantime, not everyone is required to move the cloud and Oracle has made sure to provide its customers with plenty of Premier Support leeway so they can carefully plan their next move.
Oracle EBS customers on Release 12.2 benefit from Premier Support through at least 2033 (with yearly increments) of your on-premises software version. Unfortunately, not every EBS client is on Release 12.2 just yet, even though it’s an insecure version of the application that can lead to costs and risks that can cost your company hundreds of thousands of dollars. Why are some clients willing to take that risk?
Many are not prepared to let go of an application version they deem “works just fine.” But, why settle for “just fine” when you can achieve greatness thanks to Oracle’s most stable, productive, and innovative software? Still, many organizations have let deadlines come and go, with them being:
- Oracle EBS 11i had support end on December 31, 2015
- Oracle EBS 12.1 had support end on December 31, 2021
- Oracle Market Driven Support offers limited support through December 31, 2023 but the limitations and exclusions are plenty
- Oracle 12.2 will have support end (for now) until December 31, 2033 (with a rolling 10-year window, meaning it will continue to get extended on a yearly basis)
If you’re considering an upgrade, we’re happy you’re here. There are certain, typical, aspects of the upgrade that you should consider as part of an overview of an Oracle EBS R12 Tutorial on what the upgrade entails:
- The database upgrade
- The application server installation
- Code fixes as a result of functional changes (standard tables, APIs, objects)
- CEMLI Remediation
- Online Patching compliance
- Regression testing
This is a big undertaking, but thankfully, upgrading to Release 12.2.x is the last major upgrade you’ll ever have to make.
Fast-tracking your upgrade can be a game-changer, and there are several ways you can achieve that. Next, we provide you with a high-level overview of an Oracle EBS R12 Tutorial on expediting your Oracle EBS R12.2 upgrade.
People often confuse the functional workstream with the technical workstream, even though the functional workstream needs careful evaluation of functional changes between your current version of EBS and your target version of EBS. Most of the time, EBS clients will need help from experts in the functional workstream to talk about and manage new features and figure out what they mean for their organization so that the EBS instance keeps working well. Because of this, there needs to be at least delta training or coaching; In the functional workstream, it’s important to carefully evaluate if standard functionality can replace customizations.
To really figure out what needs more thought, functional consultants are highly recommended. EBS clients should evaluate the impact of functional changes due to 12.2 upgrade before the project even starts to make the most of the functional workstream. They have to look at any changes that could have an effect and figure out what they are. The functional workstream can be done in the R12.2 Vision instance, or the DBAs can set up a 12.2 instance that has been upgraded early on.
CEMLI Remediation or Technical Workstream
It wouldn’t be an Oracle EBS R12 tutorial if we failed to mention that the upgrade to R12.2 is more technical than it is functional, which is why this is considered the critical path. The technical workstream usually determines the overall project timeline and is often the biggest budget and time risk area.
During this workstream, developers will evaluate, assess, and decide which CEMLIs can be used as-is, if they need to be fixed, or if they need to be replaced; Developers fix CEMLIs to make sure they work properly in R12.2 and create any new CEMLIs that are needed to replace old ones.
Development or DBA Workstream
The DBA workstream is mostly in charge of the actual steps to upgrade to R12.2. As part of the Oracle EBS R12 Tutorial, this workstream includes the steps to apply all the patches needed to move the EBS application from its current version to the new, desired version. In this workstream, the database is also being updated.
Before the upgrade project starts, EBS clients following this Oracle EBS R12 Tutorial need to check the health, status, and readiness of the environment to get the most out of the DBA workstream. During this workstream, it is important to think about the following questions:
- What is the current patch level for the apps, database, and/or operating system?
- Is there enough space for the project to be upgraded?
- Is there a problem with the data?
- Would an “Archive and Purge” exercise be helpful for the project?
DBA consultants help a lot with this workstream because they give expert advice and run the first upgrade iteration. They help set up the baseline statistics to get a better idea of how long the upgrade will take and to see if it fits within the allowed window of downtime. This lets them make the first draft of the DBA upgrade runbook. During this workstream, the R12.2 environment can also be used for the project development instance so that CEMLIs that don’t compile or that broke in R12.2 can be evaluated and fixed as soon as possible.
Challenges in Expediting EBS 12.2 Upgrade
As with every major upgrade, there are several aspects involved that can truly set your process behind. Within the context of this Oracle EBS R12 Tutorial, these time wasters include unnecessary testing, testing redundant use cases, not remediating CEMLIs in advance, or waiting for environments.
Careful planning and execution of the upgrade project assisted by an experienced team of consultants is the best way to make sure you won’t be spending time on unnecessary tasks that can prolong the timeline of your upgrade project.
Some best practices to avoid these obstacles are:
- Upgrade the database and the application at the same time
- Have two environments and go back and forth between them so you don’t have to wait for an environment
- Thoroughly review your existing CEMLIs to ensure they are properly replaced by standard functionality in the new version of the software and avoid wasting time in the process
- Design tests with maximum impact so you keep them at a minimum
Employing the right approach to your Oracle EBS 12.2 upgrade can make all the difference when it comes to expediting the end result as depicted in this Oracle EBS R12 Tutorial. Customers of Oracle’s E-Business Suite (EBS) who missed the deadline must now make a difficult choice: upgrade to release 12.2 as soon as possible to regain the benefits of staying under Premier Support, or leave their EBS instance vulnerable to the risks and costs associated with remaining below R12.2.
We are here to assist you in making a swift, secure, and efficient journey. We’ll help you strike the proper balance for your organization, so you can quickly begin reaping the benefits of Oracle EBS R12.2’s new features and innovations.