Answers for the Million Dollar Question on Oracle EBS R12.2 Customization

Last week we had our webcast

“Answering the Million Dollar Question for Oracle E-Business Suite R12.2 Customization”

and boy, did we have some interesting questions to answer – besides the million dollar one, that is. We are bringing you the transcript below.Is it mandatory to be on database Oracle 11gR2 for Oracle R12.2?

Yes, that is the minimum database version that you need to be on, it’s mandatory. We see that many organizations prefer to upgrade their database to Oracle 12c because of security concerns and other benefits, but the minimum is Oracle 11gR2.

Online patching: what will happen if you have custom codes? How will that be treated?
What will happen if you try to run the upgrade directly is that you will realize at the enablement step that the custom code is violating Online Patching, and you will not be able to move forward to the next step.

Instead of getting to the point where you reach a dead end, you can use the readiness report and development standards before starting the upgrade in order to have the process run smoothly, remediating all the custom code beforehand.

Do you have any customers that are using Dell Stat to move customizations?

Whatever your tool is, bear in mind that it needs to be certified with Oracle EBS 12.2 in order to meet the new standards.
By checking in the product’s page ( Oracle E-Business Suite 12.2.x is certified.

Is R12.2.4 Vision database available to download? If not, what’s the latest vision demo database available?

Oracle just released a Vision environment for 12.2.4. It’s a Virtual Machine template you can download, so if you have a contract with Oracle you should download it and play around with the new standards, check your code and train your users.

What’s the impact on Form and Web Page customization in Patch application online?

You have to consider that all the customizations for Form and OAF pages are going to be in two file systems which one of them is the “run” and another is the “patched”. This involves having the users running forms/HTML pages in the run edition which is the “old” version and you’re applying the changes to the patch edition which will be converted into the “run” after the cutover phase. So, in other words, the impact during patch application is transparent for all the objects in the application and the users can run the system as usual.

Where can the Oracle E-Business Suite customizations coding standards be found?

The documentation in My Oracle Support (MOS) is very rich and I’d recommend starting in the Oracle E-Business Suite Release 12.2 Information Center – Documentation (Doc ID 1583110.1).
From there you can find all the documents related to the functional and technical aspects of Release 12.2. The main document to understand the new concepts is the Oracle® E-Business Suite Concepts Release 12.2 Part No. E22949-09 and specifically to the development standards Oracle® E-Business Suite Developer’s Guide Release 12.2 Part No. E22961-11.

Online Patching will not help you migrate from 11.5.10 to 12.2, right? It works only after you are on 12.2?

That’s correct. Online patching is part of the Release 12.2. It will be a one-way ticket to online patching after you “enable” it as shown in the picture below on step 5.

What is the average time during cut over?

Based on IT Convergence’s implementation and some of our customers you would expect between 15 minutes and 30 minutes of total cutover – meaning real downtime for the users.

Is web logic included in 12.1.3?

No, Weblogic Server (WLS) was introduced in Release 12.2.2 and as far as we know Oracle is not planning to back port WLS to 12.1.

With online patching, can we apply patches on Monday and switch over on Sunday?  What happens to the data that is changed or added after the patches are done on Monday?

Yes, that’s actually some of the real life experience that we see. A DBA starting the online patching process during business hours, proceeding with the first 3 phases of the online patching cycle and executing the cutover over the weekend when the load of the system decreases. Now, keep in mind that we’re actually talking about less than half hour of downtime so, that means that you could have a downtime window at midnight.

The patches are being applied to the “patching file system” and “patch version” in the database. For consistency and business continuity the “run edition” remains intact and that’s why the users can continue to operate without interruption. Once you execute the cutover then the “patched edition” becomes your “run edition” and that’s where your users will see the changes applied.

Stay Connected for More on Oracle R12.2.4!

Are you interested in Oracle’s latest mobile solutions and user experience development? Join our upcoming webcast “Go Mobile with EBS – How to improve your productivity through User Experience” on Tuesday December 16th at 9:00 am Pacific/12:00 am Eastern. You can click here to reserve your spot now.