Upgrading to Oracle R12? Keep Fusion in mind

R12 is a milestone in Journey to Fusion

Oracle’s E-Business Suite Release 12 is Oracle’s latest version of their business applications with an upgrade path to Oracle Fusion Application. The technology stack is upgraded to Fusion Middleware, the backbone of Fusion Applications.

It is about 60% Java based, compared to its predecessor, Release 11i, which is only 40% Java based. Release 12 already has incorporated some of the Fusion Middleware products that are available today. Unlike Release 11i, Release 12 makes extensive use of XML.

There are various packs/flavors of the applications surrounding the existing core ERP functionality that will be released. At Infosys, we are already seeing the early version of AIA-Foundation packs that have been released that are incorporating the pre-packaged canonicals. Oracle’s strategy is to slowly incorporate the new generation technology into their applications and hence there would not be a big bang major release of Fusion Applications

Also, the functionality of ERP would be released in phases and in terms of pillars like CRM pillar, SCM pillar, etc. so with this kind of functionality being rolled out, we should assume that the stabilized version of complete fusion applications is 4-5 years from now.

Recommendations for R12 upgrade and preparing for Fusion

R12 upgrades can be approached in many ways, each with its own set of opportunities and benefits. A typical technology upgrade of ERP Application requires:

• Upgrade of the Infrastructure. The R12 upgrade process involves replacing 11i Tech stack (9iAS & 806) to Fusion Middleware (10g Application Server)

• Upgrade the integration strategy from point-to-point to Service-Oriented Architecture

• Upgrade the Reporting Strategy by bringing together stovepipe applications by ERP revitalization and creating a virtual composite application.

• Make better business decisions with Oracle Business Intelligence Applications and create executive dashboard for real-time business activity monitoring.

Upgrade to R12 as the point from where you want to jump to Fusion Applications.

Evaluate and document the customizations. Convert customizations to Fusion technology-based solutions where decommission is not possible. As an example, since we know that Workflow will be replaced by BPEL for the Fusion Applications, now is the time to learn BPEL. Any existing workflow customizations – or new ones should be written using BPEL

Upgrade Overview:

Before pursuing an upgrade, it is imperative that you fully understand the upgrade process, potential upgrade paths, and most importantly, your criteria for considering an upgrade of your Oracle E-Business Suite solution.

Key points to note in Oracle Apps R12 upgrade from 11i

• R12 upgrade process involve replacing 11i Tech stack (9iAS & 806) to Fusion Middleware (10g Application Server)

• Basic upgrade process involves Rapid Install & Auto patch

• Rapid Install involves installing new R12 tech stack as mentioned in first point

• Auto patch process involves upgrading E-Business Suite database compatible to R12 (Data Model)

• Final upgrade process is of updating data model using enhanced version of Auto Patch

• Minimum version from which you can upgrade to R12 is 11.5.7 and higher

Upgrade is broadly divided in to three steps

• Preupgrade Step (lay down file system for R12 using rapid wiz/Rapid Install)

• Upgrade Step (Upgrade database to 10gR2 (if not already upgraded), apply R12.AD.A on R12 APPL_TOP and apply 12.0.4 patch database portion only)

• Post Upgrade step (Run rapid wiz/Rapid Install one more time to configure and start services on R12)

The Upgrade Process

An upgrade project is similar to an implementation project; however, upgrade projects can be significantly more efficient than implementations because they leverage your previous implementation efforts and outputs. In addition, upgrades can be executed within the current change management system used by your organization. Within the upgrade project, there are several key areas of work that begin with project evaluation and definition, continuing through the adoption of the new system by personnel.

A standard upgrade project can be divided into the following six major phases:

• evaluating the upgrade (including development of a comprehensive business case)

• planning the upgrade project

• performing the technical upgrade (including conference room pilots/test rounds)

• performing the functional testing (including conference room pilots/test rounds)

• Facilitating end-user learning and adoption

• Cutover to production