Oracle E-Business Suite (EBS) is the backbone of your critical operations that help keep your business up and running. Back in 2018, when Oracle announced that Oracle E-Business Suite (EBS) clients fixed to releases below 12.2 would be losing Premier Support, we saw many organizations take action to begin their modernization journey. With little time left, the urgency to take action is at the top of everyone’s mind, but it’s also important to consider and evaluate what types of costs and risks you may end up with if you don’t adopt the EBS upgrades. We have also discussed a detailed Oracle EBS testing strategy that can assist your Oracle EBS 12.2 upgrade step by step with zero defects at go-live.
Staying with EBS 12.1.3 or upgrading to EBS 12.2 Status Quo
Many Oracle E-Business Suite (EBS) users already know that Oracle Premier Support for EBS 12.1.3 ends on December 31, 2021. Anyone who is still running on EBS 12.1.3 has already entered Oracle’s Sustaining support. Sustaining support is an inferior form of support that does not grant you access to new patches, security fixes, or regulatory updates for your instance.
Can you stick with EBS 12.1.3? You absolutely can. But does it provide seamless and risk-free business continuity? It is important to remember that EBS 12.1.3 is over a decade old. So, while your staff may be comfortable using it, it does not offer the functionality provided by newer versions of EBS upgrades.
The change in support timelines from Oracle has compelled organizations that depend on EBS 12.1.3 to make important decisions. They can upgrade to a more recent version of EBS or use the opportunity to migrate to Oracle Cloud Applications.
Define your EBS upgrade test strategy to eliminate go-live risk
To ensure a smoother transition to EBS 12.2, having an Oracle EBS testing plan is critical and will make your upgrade that much easier. You’ll need to define your scope of testing, resources required, timeline, and efforts. Businesses need to evaluate carefully and set up a robust Oracle EBS testing strategy that is essential to planning and executing a successful, stress-free upgrade.
Define what to test: Determining what exactly to test is still a million-dollar question. The majority of EBS upgrades involve CEMLI (Customization, Extension, Modification, Localization, Integration) update, functional testing, and an infrastructure migration to Cloud (OCI/AWS/Azure). Finding a method to test more functionality within a strict timeline is one of the biggest challenges associated with Oracle EBS upgrades, so finding a cost-effective resolution is extremely valuable.
Define what to fix: Defining exactly what to fix in your Oracle EBS upgrade project is crucial. This includes identifying non-relevant objects and unused solutions, preventing defect duplication, and preventing your integration and interfaces.
Protect your integration touchpoints: Rigorous Oracle EBS testing is required to ensure that there is no broken functionality in the upgraded environment when you have multiple end-to-end integrations. For EBS upgrades, the IT team should test all business test cases to ensure minimal disruption during project cycles.
A dedicated Oracle EBS testing tool can help you cut down on your EBS upgrade project time, cost, and risk.
Top comments (0)