There are several considerations to take into account when deciding to take on an Oracle E-Business Suite R12.2 upgrade. Our experts have brought it down to 8 points for your convenience.
1) Be prepared to assign a multi-discipline team to the technical upgrade
Considering the upgrade will require some modification to the code and potentially to the design of some of your customizations, you must have developers involved in the process and maybe also business analysts who can support a customization re-design if needed.
So this means your DBA team will not be able to complete the technical upgrade by itself this time. They may have done it before when they upgraded to previous versions but this time is different.
2) Do not by-pass the warnings during the upgrade
The technical upgrade will identify and raise issues related to the development standards. Since those are related to custom programs, your DBAs will feel the temptation to move on with the standard upgrade and let the development team fix their customizations later. This won’t work as standards that are not complied with may impact the standard application.
3) Get trained on the R12.2 Development standards
The more you learn about the R12.2 Development standards, the easier it will be for you to apply the required remediation and succeed in your upgrade.
Attend a training that covers the following areas:
- R12.2 Development Standards
- The Online Patching Cycle process
- Tips and hints to work with Editioned, Non-Editioned and Effectively Editioned objects
- Tips on how to install customizations
4) Work with a productivity tool
Work with a tool that provides insight on the violations to the R12.2 Development standards, and provides information about:
- Background details about the development standard violated (so you understand its goal)
- Details about the violation (so you know exactly what’s wrong)
- Tips on how to fix the violation to the standard
- An estimation of how much time it can take you to fix the issue
- Details about what would be the impact if you don’t comply with the standard, so you can analyze if it makes sense or not to follow it.
5) Start now with what you can
If you’re currently on release 11 you can already begin working on the remediation of some of the violations to the standards, like modifying the names of some of the custom objects which name is larger than the new limits defined.
There are several items you can work in advance and before you even kick off your upgrade project. And the more issues you fix in advance, the easier the upgrade to R12.2 will be.
6) Forget about not working with Online Patching
It’s not possible to avoid working with online patching since any patches released by Oracle after 12.2 will have to be applied as online patches. So you must follow the guidelines and you can’t avoid working with the online patching cycle even if you don’t have high availability requirements in your environment.
7) Fix violations to the R12.2 Development standards in waves
Start with the pre-upgrade phase and define waves of fixes to apply. Then run the tool assessment again to see how your violations have been reduced.
Then define a new wave and progress from the easier, big impact issues, to the more detailed, complex redesigns.
Extra tip: Work with a tool that identifies the violations to the standards and classifies them by phase.
8) Get support from skilled developers
Applying fixes to your custom code so that if complies with the R12.2 development standards requires experience. After receiving training on the subject you will learn a lot of stuff but you won’t have the necessary experience yet. Get some help from an experienced consultant who can guide you through the process and help you:
- Define a customizations upgrade plan based on the results reported by the assessment tool
- Provide insight and tips on how to solve your specific environment issues
- Support you and your technical team on the application of fixes to your code, considering the lessons learned
For more information on Oracle E-Business Suite R12, don’t forget to check more of our blogs.