Upgrading to Release 12

Upgrading from E-Business Suite Release 11i to Release 12 Overview

The process of upgrading the E-Business Suite from Release 11i to Release 12 is a simpler process relative to past E-Business Suite upgrades. The R12 upgrade process includes replacing the Release 11i applications technology stack with an updated technology stack that is founded on the principles of the Fusion Middleware. Rapid Install provides the most up-to-date, certified version of Oracle Applications products, along with the certified technology stack components. An upgrade creates the new file system for the application (middle) tier components and the new file system for the database. After the upgrade, you run Rapid Install again to configure servers and start services. In Release 12, a common data model improves the quality of your data, simplifies its management, and makes it easier for shared service centers to work across worldwide operations and provide information about your business to decision makers. An Applications upgrade alters both the technical and functional aspects of your Oracle Applications system. In addition to changes to the technology stack and file system, an upgrade also initiates specific changes that affect the way your existing products work after the upgrade and the way they look and feel. These functional (business-related) changes have an impact on the way you use the products as you conduct daily business.

Functional
Coupled with the common data model are enhanced integrations between Oracle Financials and Oracle Procurement products, Trading Community Architecture and other applications. Functional topics that should be carefully investigated:
y y y y y

Reasons for the change and areas that benefit from new functionality Functionality that is temporarily disabled or has been made obsolete Changes to user interfaces, terminology or concepts, and menu options Steps you can take to verify that all transactional data is upgraded as expected Suggestions for reducing downtime
y y

Consider running depreciation with or without closing the current period as permitted by business prior to the upgrade Prepare and post these pending Mass Addition lines before the upgrade: o GL Journals Entries Pre-Upgrade consists of the Program - Prepare Posted Journals Before Upgrade concurrent program o The Catalog Data Pre-upgrade Process: ICX_CATALOG_MIG process is strongly recommended if you are upgrading iProcurement from Release 11.5.9 or 11.5.10 to Release 12. It pre-processes bulk-loaded content to

reduce the actual time required for the upgrade and to ensure the upgrade process runs smoothly. o Migrate Rules and Time values for Oracle Service Contracts - This applies to all releases prior to Release 11.5.10: If OKS is registered in your system and you are upgrading from a release prior to 11.5.10, the rules and time values are migrated to the new architecture during the upgrade. If you want to significantly reduce downtime, perform the main part of the migration now, before the upgrade. Multiple Organization architecture (MOAC) is required for Release 12. It supports performance improvements across the E-Business Suite, as well as Multiple Organization Access Control, which enables an Applications responsibility to access multiple operating units if desired. The upgrade process includes this conversion. Converting to Multiple Organizations does not require the use of multiple operating units or sets of books, but it does enable you to use these features if you desire. Converting to Multiple Organizations by itself does not produce any noticeable Oracle changes. Oracle Subledger Accounting provides a common accounting engine that replaces the existing accounting processes in the different subledgers. Consequently, the Subledger Accounting upgrade consists of migrating the existing accounting data to ensure a continuous business operation between the two releases. Multiple reporting currency functionality has migrated to Reporting Currency functionality in the Oracle Subledger Accounting model. Oracle Subledger Accounting provides a single repository where you can view amounts in reporting currencies. The Oracle Legal Entity Configurator is a new module in Release 12. It is populated with data that is migrated from a number of Release 11i sources. Its purpose is to provide a consistent definition of the legal structure of your enterprise and relate it to other structures within Oracle E-Business Suite. With the Oracle Legal Entity Configurator, you can manage your legal corporate structure and track data from the legal perspective. This enables detailed reporting at the legal entity, establishment, and registration level. The concept of Legal Entity has an impact on all customers who use the Human Resources model to define legal entities. Legal entities exist as Trading Community Architecture parties with legal information stored in the Legal Entity (XLE) data model. Subsidiaries of the legal entities are defined as establishments, which are also defined as parties with legal information stored in the Legal Entity data model. HRMS organizations with an operating unit or inventory organization classification are migrated to establishments in the Release 12 Legal Entity model. No other classification of organization other than operating unit or inventory organization classification is migrated as establishment.

Setting up operating units is more streamlined with the integration with Accounting Setup Manager, a new feature in General Ledger that centralizes the setup and maintenance of common financial components, such as legal entities, operating units, and ledgers within an accounting setup. All Release 11i HR Organizations classified as Operating Units are preserved in Release 12. If operating units are assigned to a set of books, they are associated to a primary ledger in an accounting setup. You can now view all operating units assigned to an upgraded primary ledger using Accounting Setup Manager.

Technical
In Release 12, the upgrade process has been enhanced and streamlined. New features have been added to Rapid Install and AutoPatch to increase their capabilities. In addition, an upgrade no longer relies on AutoUpgrade processes. All upgrade functionality has been consolidated into a single unified upgrade driver that performs the upgrade without reliance on the information formerly captured on the AutoUpgrade screens. The primary utilities used in the R12 upgrade process are Rapid Install and AutoPatch. Rapid Install installs the new R12 technology stack and AutoPatch upgrades the E-Business Suite database to Release 12. The upgrade no longer requires a two-step approach of upgrading the EBusiness Suite database by running AutoUpgrade and AutoPatch. The upgrade is a one step approach of updating the data model by using an enhanced version of AutoPatch. The requirement for upgrading to R12 is that the E-Business Suite version be at 11.5.7 or later. E-Business Suite systems on Releases 11.5.1 to 11.5.6 must be upgraded to at least 11.5.7. However, Oracle strongly recommends upgrading to 11.5.10.2. For all E-Business Suite systems, the database must be upgraded to 10.2.0.2 either before or during the R12 upgrade process and prior to running AutoPatch to upgrade the data model to R12. This document assumes the Release 11i E-Business Suite system is running a version of the 9iR2, 10gR1, or 10gR2 database. Customers running 8.1.7 will need to upgrade their database accordingly. All referenced chapters refer to: Oracle Applications Upgrade Guide: Release 11i to Release 12.

Customizations
To preserve customizations and minimize the impact during the upgrade:
y y y

Follow the Oracle Applications Developers Guide instructions for customizing your system and upgrading your customizations Maintain complete documentation for customizations Back up customizations before the upgrade

Oracle E-Business Suite Configurations

Oracle E-Business Suite systems running releases 11.5.7 or greater can be categorized into two groups. The first group includes systems that are currently running Release 11.5.7, 11.5.8, 11.5.9 (base or CU1), or 11.5.10 (base or CU1). The second group is systems running Release 11.5.9 CU2 or 11.5.10.2. Release 11.5.10.2 includes systems installed with Rapid Install 11.5.10.2 and those upgraded by using the 11.5.10 CU2 maintenance pack. For the first group of systems, there is no interoperability of running the Release 11i E-Business Suite system with a 10.2.0.2 database, therefore, the database must be upgraded to 10.2.0.2 during the R12 upgrade downtime. This means there will be a prolonged upgrade downtime because the E-Business Suite upgrade to R12 must include the necessary downtime to upgrade the database to 10.2.0.2. For the second group of systems, that is, those on 11.5.9 CU2 or 11.5.10.2, there is interoperability between those versions of the E-Business Suite and 10.2.0.2 of the database. Therefore, the upgrade of the database can take place prior to the R12 upgrade downtime or during the R12 upgrade downtime. By upgrading the database prior to the R12 upgrade downtime, the requisite downtime can be separated into two downtimes. In this scenario, the database upgrade is performed independently of the R12 upgrade and the 11i E-Business Suite system can be made available to users between the two downtimes.

Upgrade Paths
There are three possible database upgrade preparation paths. The first category of systems described in the prior section has one available upgrade path in regard to upgrading the database to 10.2.0.2 and the E-Business Suite system to R12. The second group of systems has three available database preparation paths. This section details each of the available paths. The following table lists the paths available for each of the E-Business Suite 11i releases supported for an upgrade to R12. For convenience, these paths are labeled Path A, Path B, and Path C.

Path A: Standard Upgrade

Path Path A is applicable to any E-Business Suite system of Release 11.5.7 or later. However, Path A is the only path available to systems running releases 11.5.7, 11.5.8, 11.5.9 (base or CU1), 11.5.10 (base or CU1). This path requires an extended R12 upgrade downtime because the

upgrade of the database to 10.2.0.2 must take place during the critical downtime for the R12 upgrade. In Chapter 2 of the Oracle Applications Upgrade Guide, you run Rapid Install to install the applications technology stack as well as the 10.2.0.2 Oracle home.

Path B or Path C
Systems using Path B or Path C have or will have databases already upgraded to 10.2.0.4 by using the process documented in the Interoperability Notes: Oracle Applications Release 11i with Oracle Database 10g Release 2 (10.2.0). Path C breaks out the R12 upgrade downtime window into two separate downtimes as opposed to one extended downtime in Path B.

Path B: Upgrade Path for Systems with 11.5.9 CU2 or 11.5.10.2 with a 10.2.0.4 Database
During the Migrate database to Oracle10g Release 2 step in Chapter 3, apply the 10.2.0.4 database patch to the RapidWiz-installed 10.2.0.3 Oracle home, before continuing with the standard R12 upgrade process, or use 10.2.0.3 DB Home supplied by RapidWiz and upgrade to 10.2.0.4 later.

Path C: Upgrade Path for Systems with 11.5.9 CU2 or 11.5.10.2 with a 9iR2 or 10gR1 Database
Either prior to beginning the R12 upgrade preparation process or during the Migrate or upgrade your database to Oracle 10g Release 2 step in Chapter 2. At this time, you can bring the E-Business Suite 11i system back on line and make it available to users while continuing to plan for the other phases of the R12 upgrade process.

For all Upgrade Paths Plan Upgrade to R12

Perform all requirements documented in Chapter 1 and all applicable steps in Chapter 2.

Install the R12 Technology Stack and 10.2.0.2 Oracle home

Use Rapid Install to install the R12 applications technology stack and the 10.2.0.2 Oracle home

Complete the R12 upgrade

Perform the remaining steps in Chapter 3 and all applicable steps in Chapter 4 to complete the upgrade to R12.