Planning Your Oracle E-Business Suite Upgrade from Release 11i to Release 12.

1
An Oracle White Paper January 2011

Planning Your Oracle E-Business Suite Upgrade from Release 11i to Release 12.1

Introduction ....................................................................................................... 4  Business Value of Upgrading to Release 12.1 ............................................... 5  Release 12 Value Proposition ................................................................. 5  Release 12.1 Value Proposition.............................................................. 6  Upgrade Planning Tips ..................................................................................... 8  Tip #1 – Target Release 12.1 for Your Upgrade................................. 8  Tip #2 – Allocate Enough Time and Resources to Your Project .... 8  Tip #3 – Determine Your Upgrade Approach.................................... 9  Tip #4 – Determine Your Project’s Technical Scope ...................... 10  Tip #5 – Determine Your Project’s Functional Scope .................... 10  Tip #6 – Plan for Required Financials Setup Steps .......................... 11  Tip #7 – Avoid Upgrading Obsolete Functionality.......................... 11  Tip #8 – Determine Your Data Migration Strategy ......................... 12  Tip #9 – Assemble a Project Team that Combines Technical and Functional Skill Sets............................................................................... 12  Tip #10 – Involve Your Business Users at Every Project Phase ... 13  Tip #11 – Keep Your Project Team in Place through Your First Financials Close ...................................................................................... 14  Tip #12 – Develop a Robust Testing Strategy .................................. 14  Tip #13 – Plan to Test with Upgraded As Well as New Data and at Full Volumes........................................................................................... 16  Tip #14 – Plan to Do Load and Volume Testing............................. 16  Tip #15 – Engage with Oracle Support ............................................. 17  Tip #16 – Develop an Issue Resolution Strategy.............................. 19  Tip #17 – Take Advantage of Oracle E-Business Suite Diagnostics .............................................................................................. 19 Tip #18 – Inventory Your Customizations and Prioritize Them for Upgrade ................................................................................................... 20  Tip #19 – Consider Migrating Your Reports to Business Intelligence Publisher............................................................................. 23  Tip #20 – Review Your Integrations and Consider Modernizing Them ........................................................................................................ 24  Tip #21 – Reexamine User Roles and Responsibilities and Business Processes.................................................................................................. 25 

Planning Your Oracle E-Business Suite Upgrade from Release 11i to Release 12.1

Page 2

Tip #22 – Consider Using Oracle’s Process Documentation and End User Training Tools ...................................................................... 26  Tip #23 – Acquire Release 12.1 Knowledge...................................... 27  Tip #24 – Fully Utilize Available Upgrade Information.................. 29  Tip #25 – Consider Using the Maintenance Wizard ........................ 30  Tip #26 – Take Steps to Minimize Downtime.................................. 31  Tip #27 – Identify Required and Recommended Pre- and PostUpgrade Patches..................................................................................... 34  Tip #28 – Review your System for Compliance with Security Best Practices ................................................................................................... 35  Tip #29 – After Your Go-Live, Stay Current with Latest Code..... 35  Tip #30 – After Your Go-Live, Stay Current with Latest Information ............................................................................................. 35  My Oracle Support Knowledge Document References ....................... 37  Change Record ............................................................................................ 38 

Planning Your Oracle E-Business Suite Upgrade from Release 11i to Release 12.1

Page 3

and Development organizations with real-life lessons learned from customers who are already live on Release 12.1 upgrade project are the primary audience. this paper launches into specific upgrade planning tips to help you: • • Understand the factors that can affect your project’s duration Decide your project scope.Planning Your Oracle E-Business Suite Upgrade from Release 11i to Release 12. As we gather additional Release 12.1. and avoid missteps that can needlessly increase your scope Assemble the right project team Develop a robust testing strategy Upgrade your custom code Minimize your upgrade downtime Leverage all of the Oracle Support resources that are available to you • • • • • • Identify the Oracle tools that can improve your upgrade and maintenance experience Become familiar with the full range of Oracle’s information resources • This white paper is intended to be a living document. IT.1 upgrade planning advice. we will revise and re-publish it as My Oracle Support Knowledge Document 987516.1 INTRODUCTION This white paper offers best practice advice to customers currently on Release 11i who are planning a Release 12.1 Page 4 . IT professionals involved with planning.1 upgrade value proposition.1. or running a Release 12.1 upgrade. In a nutshell. This paper combines advice from professionals in Oracle’s Support.1 upgrade project. Consulting. Following a brief overview of the Release 12. managing. Planning Your Oracle E-Business Suite Upgrade from Release 11i to Release 12. this paper tells you “things you wished you knew” before embarking upon your Release 12.

• Release 12 also introduced improvements in end user productivity. Release 12 introduced a new centralized architecture that improves support for shared services while standardizing and simplifying the financial infrastructure across your enterprise. • • Legal entities easily model legal corporate structures and tie all related components together with Legal Entity Configurator. providing a single point of access for internal bank accounts across Oracle applications.BUSINESS VALUE OF UPGRADING TO RELEASE 12. It supports the centralization of the following key business functions: • Accounting policies are standardized across the entire enterprise with Subledger Accounting. which offers consistent support and control of complex transactional tax requirements across the enterprise. Payments are centrally disbursed and captured with Oracle Payments. It also incorporated the latest revisions to Oracle’s middleware and database technologies. step-by-step checklists. Release 12. wizard-like pages. Supply Chain Management. Inter.1. and reduce risk.and Intra-company accounts are centrally defined with the Advanced Global Intercompany System to improve period end reconciliation.1 Page 5 . and consolidated single-page setups in these and other product areas: • • • • Collections Payments Accounting Setup Tax Planning Your Oracle E-Business Suite Upgrade from Release 11i to Release 12. Release 12 Value Proposition Release 12 introduced a new centralized architecture that improves support for shared services while standardizing and simplifying the financial infrastructure across your enterprise.1 Release 12. Human Capital Management. Customer Relationship Management and Master Data Management. including dashboards. including Procurement. Banks and bank accounts are centrally managed. rounds out Release 12 with significant enhancements to the other product areas. which became available in January 2007. Financial results are stored and easily accessible with Ledgers and Ledger Sets to support faster and simpler period end closing. It also contains usability improvements and centralized life cycle management. • • • Transaction taxes are consistently managed and processed with E-Business Tax. ensuring adherence to the same set of accounting rules. automating and streamlining integration with external financial institutions. which became available in May 2009. improve operational efficiencies. included major architectural improvements to the Financials products to support global and shared service operations.

and achieve sustained savings. these include Excel integration to run what-if analysis. charts. Planning Your Oracle E-Business Suite Upgrade from Release 11i to Release 12. multiple fonts and colors. Earnest Money Deposits. Release 12.Release 12 made producing all types of reports much easier – whether reports that include images.1 rounds out Release 12 with significant enhancements to all of the other product areas. In addition. demand-based forward pick replenishment.1 rounds out Release 12 with significant enhancements to all of the other product areas. including summarization of all talent information in a single user-friendly Talent Profile page. enforce compliance and reduce risk.1 Page 6 .1 and in related analytics and integration solutions are: Sourcing enhancements to streamline sourcing processes. and integration with Oracle Transportation Management Optimization of supply. recruitment dashboards. Some key new features in Release 12. Release 12 included enhancements across the Financials products to support global business growth at lower cost with more control and flexibility. and enabled our customers’ compliance with local reporting obligations.1 Value Proposition Release 12. and Cost Factors and Price Factors. new capabilities such as spend classification and analysis have also been added • • High volume warehouse operations support. two-stage evaluation of Request for Proposal (RFP). Below is a sample of the more than 300 new features and enhancements introduced in Release 12: • • • • • • • • • • Replacement for disabled accounts Invoice line level entry and approval Partial period revenue recognition COGS and revenue matching Line level cash applications Conversion of delinquent receivables to payment plans Funds optimization with cash pooling and zero balancing Bank account-level reconciliation options and tolerances Rollback on select assets with Automatic Depreciation Rollback Streamlined receipts management with receipts tracking and receipts missing capabilities Release 12. By delivering reports using Business Intelligence Publisher – which uses an extract and template model – we put the capability to format and deliver reports in the hands of business users. demand and design chains with the new Value Chain Planning solutions in Oracle Supply Chain Management • • Talent Management improvements. board quality financial statements or government mandated forms. including advanced wave planning.

Utilities. we delivered: • Service and Field Service Dispatch Enhancements for improved Dispatch Center Workbench Task Management. • • Extending the overall 12. including Web 2. duties.1. we provided release update packs (RUPs) in December 2009 (12. Oil & Gas. as well as continued support for Global HR and Payrolls • Ability to view fully-loaded estimated costs (including transportation. as well as support for embedding rich content such as business intelligence reports. For example. and look-ahead searching. Additional Cost factor Support for more effective Scheduling of Technicians. objectives management and line of sight/cascading of objectives in performance management. and improvements in usability and user experience. profiling and performance management.2) and again in August 2010 (12. and two new analytical applications – Incentive Compensation Analytics and Spend Classification. we introduced two new products – Supplier Lifecycle Management and Supplier Data Hub.1 release. Mobile Field Service technician screen personalization and auto sync.0 controls such as mouse-over and pop-ups.1. dashboards. learner groups and mandatory enrollment in Learning Management. Key highlights include enhancements in Service and Field Service and in Supplier Lifecycle Management. and taxes) across the complete supply chain with Oracle Landed Cost Management Ability to manage vendor rebates and special price requests and have complete visibility into the ROI for promotional funds and the effect of supplier price changes with Oracle Supplier Ship & Debit and Price Protection for Wholesale Distribution Ability to manage cash flow and payment holds and to ensure that subcontractors satisfy contract deliverables with Subcontractor Payments for Engineering & Construction. Telecommunications and anyone else • • We continue to add new functionality to Release 12. More specifically. also. These RUPs contain statutory and regulatory updates as well as enhancements across the E-Business Suite product areas. We also released new and enhanced Oracle Application Integration Architecture (AIA) integrations.1 Page 7 . Planning Your Oracle E-Business Suite Upgrade from Release 11i to Release 12.1 on a regular basis. Partnership with Trimble for GPS Support. and so on. along with Master Data Management capabilities such as de-duping and merging Usability enhancements across the E-Business Suite. in-line editing of attachments. and optimized and streamlined Service Request Creation & Management for faster data entry Supplier Lifecycle Management and Supplier Data Hub to support extended supplier registration.interview management.3). a new succession planning module.

Tip #2 – Allocate Enough Time and Resources to Your Project Plan for your 11i to Release 12. we encourage you to consider an upgrade to Release 12.1 Page 8 . Release 12.1? Are you combining your Release 12. and potentially upgrading that code to apply it to Release 12. evaluating Release 12.1 just two months prior to their planned go-live and still made their original go-live date. requiring you to devote significant time to inventorying your custom code.1 impacts on that code. Several customers already underway with an 11i to Release 12 upgrade were able to cut over to Release 12. or are you fully implementing new Release 12. While the Release 12 to 12.1 adoption with other systems projects. Many customers have asked: “How long does a Release 12. and how much of their time will be dedicated to Release 12.5.1. operating system. we recommend that you consider changing your target to Release 12.10. posing a minimal disruption to your Release 12 deployment.5. Any customer beginning an 11i upgrade project or planning a new installation of Oracle E-Business Suite should target Release 12.1.1. If you are already live on Release 12. While customers can expect the same support service level for Release 12 as for Release 12. or database? Are you performing a minimal technical upgrade.1 without a material impact on their budget or schedule. such as upgrades to hardware.1 Financials upgrade has very minor impacts.1 has a longer support horizon and will be the basis for all future enhancements. as a wide range of variables can affect your project’s duration.1 will face the same Financials upgrade considerations as applied to the 11i to Release 12 upgrade.UPGRADE PLANNING TIPS Tip #1 – Target Release 12.1 functionality? How big is your project team.5. If you are already in progress with an upgrade to Release 12 – unless you are in the late stages of stabilizing on the release.1 upgrade to require more time and resources than were required for E-Business Suite maintenance pack upgrades.1 upgrade to require more time and resources than were required for E-Business Suite maintenance pack upgrades. such as the upgrade from 11.1 includes centralized functionality to handle accounting. Plan for your 11i to Release 12. taxation.1.10. Release 12. While the bulk of these changes were introduced in Release 12 of Financials.1. with more flexible implementation options than were available in Release 11i to meet a wider variety of business needs.9 to 11.1 upgrade project take?” There is no fixed answer to the question. For example: • Is your current E-Business Suite system heavily customized. An 11i to Release 12. especially in the Financials product area. such as the upgrade from 11. One enterprise changed direction from 12 to 12. and access to data across organizations.1 adoption? • • • Planning Your Oracle E-Business Suite Upgrade from Release 11i to Release 12.1 for Your Upgrade Any customer beginning an 11i upgrade project or planning a new installation of Oracle E-Business Suite should target Release 12.5.9 to 11. customers upgrading from 11i to Release 12. the functional advances in other product areas are compelling and mostly incremental.1 upgrade involves significant changes in data model and functionality.

A standard upgrade allows you to take advantage of supported tools. You could freshly implement Release 12. you install the Release 12. It is a project that you would generally undertake with the support of a professional services provider. or calendar.1.1 software and implement it to reflect your enterprise structure and operating practices. Generally.1 by upgrading.1 by implementing.1 system using public interface tables and application programming interfaces (APIs) that Oracle provides. The standard upgrade process converts your existing setup to Release 12. you should consider whether to perform a standard upgrade versus a reimplementation. even if some of those businesses were running E-Business Suite. If you adopt Release 12. on the other hand. Your enterprise has undergone significant change in the number and structure of its business units and organizations since your original Oracle implementation. you have grown through acquisition and you want to establish a new standard applications setup for all of your business units. then your fresh implementation may be described as a “reimplementation”. You are merging several E-Business Suite instances with different charts of accounts.1. which are currently running disparate application systems. If the legacy system from which you migrate your historical data is an earlier release of the E-Business Suite.1.1 data model.1 software and use Oracle-supplied tools and scripts to transform your historical data in place to the new Release 12. such as your chart of accounts definition.Many systems integrators have experience completing Release 12. You then load any historical data from your legacy systems into your freshly-implemented Release 12.1 Page 9 . or calendars into a single global instance and you would like to “start fresh”. Let’s start by distinguishing what we mean by the terms “implementing” and “upgrading. • • Planning Your Oracle E-Business Suite Upgrade from Release 11i to Release 12. You would consider doing a reimplementation under circumstances such as: • You wish to change configurations that are not easily changed. Tip #3 – Determine Your Upgrade Approach Many systems integrators have experience completing Release 12. allows you greater flexibility in your setup and in how you migrate your historical data using supported public interfaces. you use custom scripts to transform your historical data into a format that is compatible with those public interfaces.1 upgrade projects with a wide range of project scopes and complexity. and then migrate historical data from your existing businesses. If you are moving from an existing release of Oracle E-Business Suite to Release 12.” If you adopt Release 12. taking full advantage of new Financials features such as secondary ledgers. costing methods. A reimplementation. such as Oracle Consulting. costing method. scripts and documentation to move your existing Release 11i setups and historical data to Release 12.1 – reimplementation is not required. you install the Release 12. We recommend that you consult with Oracle Consulting Services or your systems integrator to estimate the time and effort that your particular project will require. For example.1 upgrade projects with a wide range of project scopes and complexity.

while others prefer to phase changes across multiple projects and downtimes. decide whether to perform the upgrade before versus during your Release 12.1.1 for information about Release 12.1 upgrade from other systems architecture projects.1.1 with the same setups and functionality. (See Chapter 1. how long any single downtime can be. If either of these technology components needs upgrading. well ahead of the Release 12 upgrade. or merging multiple instances into a single global instance. or to divide your adoption into multiple projects. versus Planning Your Oracle E-Business Suite Upgrade from Release 11i to Release 12. in the Oracle E-Business Suite Upgrade Guide. such as upgrading your hardware or your operating system. In general.1 Page 10 . “Planning for an Upgrade”. how much testing they typically apply to systems changes. or in a subsequent project. Release 11i to 12. default functionality around tax. but at the cost of more total downtime and more testing of interim states. For example.) Tip #5 – Determine Your Project’s Functional Scope The standard upgrade moves you from 11i to Release 12.1 downtime window. Some customers prefer to combine multiple systems architecture changes into a single project with a single downtime. As part of your technical scoping exercise. as part of the same project. Oracle took a phased approach – completing a database upgrade and an upgrade to middle tier hardware and software as separate projects.1 adoption as a single project that fully encompasses all the functional and business process changes you are targeting. Reimplementation (Financials)”.1. Oracle combined the smaller 12 to 12. you could simplify your Release 12. The benefit of a phased approach is that you simplify your troubleshooting and minimize the business risk associated with any single project. but you accept more complex troubleshooting and increased business risk. Conversely. when you concentrate multiple systems architecture changes into a single project.For more upgrade versus reimplementation considerations. Tip #4 – Determine Your Project’s Technical Scope Evaluate the costs and benefits of separating your Release 12. ledgers and payments.1 project by performing a minimal upgrade.1 system requirements. Evaluate the costs and the benefits of separating your Release 12. My Oracle Support Knowledge Document 780989.1 upgrade and an associated database upgrade into a single project with a single downtime – allowing us to minimize our testing effort. plus some additional. There is no right or wrong approach – different enterprises will make different technical scoping decisions based on how frequently their business allows a downtime. and other considerations. see “R12: Upgrade vs. You then have the option to implement additional new functionality either immediately. investigate whether you need to upgrade your database or your operating system to the minimum level required by Release 12. By contrast. For our Release 12 upgrade and associated architecture projects. consider whether to scope your Release 12. subledger accounting.1 upgrade from other systems architecture projects. you minimize downtime and testing.

work with your user community to identify any setups. it provides the foundation for over 300 new features across all of the product areas. “Preparing for the Upgrade”. Furthermore. you can reduce the scope of your upgrade project. of what is appropriate for most business situations.1 functionality.1. Assets. the upgrade scripts that move Release 11i Financials setups to Release 12. you should resolve them before you upgrade. While you can upgrade successfully without running this report and without modifying your setup.1 features in the other product areas. Tip #6 – Plan for Required Financials Setup Steps Even a minimal upgrade requires some setup of the new Financials features that come by default. Planning Your Oracle E-Business Suite Upgrade from Release 11i to Release 12. as well as many new Release 12.1. Some accounting entities (such as taxes. Payments and E-Business Tax. you can reduce the scope of your upgrade project. You can analyze the new features and implement them at your own pace at any time after your upgrade. If you have setup inconsistencies among Release 11i products for setups that are centralized in Release 12. Regardless of how you adopt Release 12. programs or seed data that you no longer use. such as Trading Community Architecture (TCA) for supplier data. These include the Oracle Financials accounting and tax engines and the multi-organization capability that were introduced in Release 12.1 upgrade. and Receivables. plan on modifying your Release 12. If those assumptions would lead to an outcome that is inappropriate for your business situation. banks and suppliers) that were modeled by several Financials products in Release 11i were moved to a common implementation starting with Release 12. As part of your upgrade planning. You can run the Accounting Setup Manager Pre-Update Diagnosis Report to view your Release 11i setup for Multiple Reporting Currencies. This report identifies setups that are potentially problematic. you should review your 11i supplier data and remove any duplicates prior to your 11i to Release 12. However. since supplier data moved from individual product tables in Release 11i to common TCA tables starting with Release 12. you may find it more difficult to take advantage of new Release 12. Release 11i to 12. Global Accounting Engine. (See Chapter 2. in the Oracle E-Business Suite Upgrade Guide.1. By removing or disabling this obsolete functionality while you are still running on 11i. For example.upgrading and fully implementing new features to the target state.1 are based on assumptions.1 for more information about the Accounting Setup Manager Pre-Update Diagnosis report.1 Financials setups. Regardless of how you adopt Release 12.) Tip #7 – Avoid Upgrading Obsolete Functionality By removing or disabling obsolete functionality while you are still running on 11i.1 Page 11 . General Ledger. you may want to scope your adoption to include all of the features that support your return on investment as a single project. detailed in the Oracle Financials and Oracle Procurement Functional Upgrade Guide. depending on your circumstances. Payables. it provides the foundation for over 300 new features.1.

embedded in the applications technology layer. choosing the Integrated SOA Gateway responsibility.1 reports with the equivalent reports from your legacy system. consider engaging an experienced migration consultant from Oracle Consulting or one of Oracle’s partners. alerts. In addition.1 project team: Planning Your Oracle E-Business Suite Upgrade from Release 11i to Release 12. For example.For example. responsibilities. and clicking the Integration Repository link.” If your intended migration scope is large. and we eliminated obsolete reports. The Oracle Integration Repository is a complete catalog of the many E-Business Suite public interfaces that you can use to migrate historical data. prior to Oracle’s own upgrade to Release 12. establish a method for reconciling migrated data with legacy data. Your strategy should address the scope of data to migrate. and other data to reduce our testing and upgrade effort. Figure 1: Integration Repository It’s important to determine whether your historical data needs cleansing to eliminate any data that is incorrect. Tip #8 – Determine Your Data Migration Strategy For a new E-Business Suite implementation or a reimplementation. redundant. out-of-date. For audit purposes.1. determine a data migration strategy for historical data. Typically. You can access the Integration Repository by logging into your test installation of Release 12. The Oracle Integration Repository is a complete catalog of the many E-Business Suite public interfaces that you can use to migrate historical data. incomplete. Tip #9 – Assemble a Project Team that Combines Technical and Functional Skill Sets Consider including the following people on your Release 12. you should validate through testing that you can successfully perform Release 12. you can reduce data migration volume and prevent data inconsistencies in your Release 12.1 system. data that has undergone several prior upgrades or migrations can benefit from cleansing.1 operations on data migrated from your legacy system. By cleansing historical data.1 Page 12 .1. we reviewed and standardized our setups. It is part of the Oracle E-Business Suite Integrated SOA Gateway. for example. you could compare the outputs obtained from Release 12. “migrate all open payables and receivables invoices. or incorrectly formatted.

1 experience.1 Page 13 . and Oracle’s Advanced Customer Services team offer many Release 12.1 adopters have commented that strong support from business users has been critical to their project success. and a DBA to apply patches. in Oracle Payables. Typically.) Planning Your Oracle E-Business Suite Upgrade from Release 11i to Release 12.1 upgrade. an operating system administrator. Oracle’s partners.1 changes in look and process flow. Be sure to involve business users from the start of your project so that they are prepared for Release 12.1 changes in look and process flow. application specialists focus on particular product areas and perform the related functional setups. For Financials upgrades. and to participate in end-to-end testing and end user training. Application specialists – technical specialists with functional business knowledge who work closely with business process owners.1 rollout to end users • • • • • If you decide to retain outside consultants to provide expertise that is lacking from your in-house team. an applications server (middle tier) specialist.1. a database administrator. the payments process uses a new Payments dashboard. Consider using Oracle’s process documentation and end user training tools. consider including a tax specialist who knows the tax policies in the regions where you do business. a change management (patching) specialist. Testers – both technical and functional. prefer consultants with prior Release 12. For example. Identify the functional areas where users will see the biggest changes and concentrate your training efforts there. and the Invoice workbench is significantly reworked. Oracle Tutor and Oracle User Productivity Kit (UPK). a performance specialist.• • A dedicated project manager An executive steering committee – to provide project oversight and make critical decisions. Oracle Consulting. citing the power of a “we’re-all-in-this-together” attitude. You will also need someone to log and track service requests (SRs).and implementation-related services. and a customization developer. Be sure to involve business users from the start of your project so that they are prepared for Release 12. there is a significant pool of skilled and trained consultants. Plan to reinforce user learning even after your production cutover with internal documentation and job aids. Tip #10 – Involve Your Business Users at Every Project Phase Several Release 12 and 12. to help with knowledge transfer to business users (see Tip #22. Technical team – one or more people who can function as a technical upgrade specialist. With the large number of customers either implementing or live on Releases 12 and 12. Business process owners – to analyze business process changes. A training lead – to assist in the Release 12.

and allow for tuning of upgrade scripts as needed. updating them to reflect new Release 12. and ideally through your first quarterly close. The timeframe for your testing rounds should be clearly stated. Oracle’s Testing Practices Oracle uses a standard testing flow for all systems changes.1 go-live. be sure to track any upgrade impacts on your custom code. plan to keep your project team in place at least through your first Financials close. Also. and then reconsidered before and after each test round. you can create test scripts by documenting what you currently do in the system. Your project team can closely monitor the health of your production system. with an overall goal of performing end-to-end testing of all business flows and scenarios. If you do not have test scripts from your original implementation.1 into production. Your testing should be guided by detailed test scripts that you prepare in advance. The number of test rounds and your acceptance criteria should be carefully considered at the outset of your project. logging service requests as needed and notifying end users through broadcast emails of any significant issues. begin performing test upgrades against a copy (clone) of your existing system. each of which runs a full-sized copy of our production database: • Build Test – where the technical team tests changes for several weeks before handing off to business users for testing Planning Your Oracle E-Business Suite Upgrade from Release 11i to Release 12. As for any new release. and who will be involved. Changes are collected into release bundles that are promoted through a series of test environments. Perform multiple rounds of testing. Test upgrades help to establish that the upgrade will fit into your downtime window. Be sure to specify expected test results to compare against your actual test results. Issues and slow turnaround on resolutions may affect your testing period. Tip #12 – Develop a Robust Testing Strategy We cannot over-emphasize the importance of testing to the success of your Release 12. begin performing test upgrades against a copy (clone) of your existing system. or even to advancing to the next test round.Tip #11 – Keep Your Project Team in Place through Your First Financials Close After your Release 12. you should formulate a testing strategy that details the number of test rounds. Well before your planned go-live date. You can start with the test scripts used in your original implementation. Agree in advance which types of issues should be considered as show-stoppers to putting Release 12.1 functionality and process changes that you intend to implement.1 Page 14 . ensure that you do full functional testing with business users. The project team can serve as a backup to the smaller in-house support team that normally handles end user queries. types of testing. make sure you budget enough time for issue resolution.1 upgrade project. Well before your planned go-live date. focusing on new and changed functionality. In addition to conference room pilot testing to validate setups.

you could use the OATS tool to load test your Release 12. Staging Test – where the technical team does final regression testing of key transaction flows and a full dry run of the transition outage about one week prior to production cutover. In an upgrade context. as well as iterative runs of the upgrade process to tune performance and minimize the duration. We also added a one-off Technical Test environment where our technical staff did simulations to identify any performance regressions. which is supported for use with Oracle E-Business Suite Releases 11i. The Test Starter Kit includes sample test scripts and an instruction guide for using the OATS automated testing tool with Oracle E-Business Suite.and Oracle Forms-based screens. add custom test cases to validate content. parameterize script inputs.oracle. including worst-case peak loads. Using the OATS graphical scripting interface.1 Page 15 . Oracle provides a “Test Starter Kit” for Release 12. and load testing Oracle Functional Testing for automated functional and regression testing Oracle Test Manager for test process management.• User Acceptance Test – where business users and the technical team do several weeks of full end-to-end testing. performance. but increased the number of test rounds. You can create your own functional and load test suites using Oracle Application Testing Suite. Also using the same interface. you can create automated load test scripts that allow Oracle Load Testing to simulate thousands of concurrent virtual users. which is supported for use with Oracle E-Business Suite Releases 11i.1. Just a week before go-live. mimicking normal business operations. • For the 11i to Release 12 upgrade. Automated Testing Tools You can create your own functional and load test suites using Oracle Application Testing Suite.1 test system to ensure that it adequately scales to the volume of transactions you anticipate in production. The Planning Your Oracle E-Business Suite Upgrade from Release 11i to Release 12.html Additionally. and defect tracking OATS uses Oracle E-Business Suite Accelerators to enable support for automated functional testing and load testing of both E-Business Suite Web. 12. and 12. allowing us to get very accurate timings for our production go-live.com/technology/products/oem/prod_focus/etest. The Oracle Application Testing Suite (OATS) is composed of: • • • Oracle Load Testing for scalability. test execution. and 12. your business users can record automated test scripts by stepping through Oracle E-Business Suite business transactions. You can read more about the OATS solution at: http://www. 12.1. we followed our standard testing flow.1. including regression testing of key transaction flows. we did a full dress rehearsal of the upgrade transition in the Staging Test environment. You can use the same interface to run scripts. and extend scripts programmatically in Java.1 that uses OATS.

1 do not create inconsistencies in a business document as it completes its flow.com/technology/software/products/apptesting/index. Tip #14 – Plan to Do Load and Volume Testing Because new reports and business processes may be sensitive to your data distribution. and to ensure that your system has the expected performance characteristics. While your initial conference room pilot testing may validate setups based on sample or demonstration data. validate this with testing.1 validation. test that an invoice created in Release 11i can have a credit memo issued against it in Release 12. Or. You can use the sample test scripts as a model for building your own unique portfolio of regression test suites. it’s critical that you do full.sample test scripts were created by Oracle’s Quality Assurance team and they run against an E-Business Suite Vision Demo database. Oracle does automated load and volume testing. Release 12. in general. consider simulating a month-end close a few days before your first actual month-end close. make sure you do load and volume testing.1 Page 16 .1 on documents that were created in Release 11i. For a project as major as an E-Business Suite upgrade.1 data validation is even tighter than in prior releases.1. you test your month-end and quarter-end close and reconciliation with full data volumes. simulating heavy system usage.1. Planning Your Oracle E-Business Suite Upgrade from Release 11i to Release 12. Tip #13 – Plan to Test with Upgraded As Well as New Data and at Full Volumes Test all of your business scenarios with documents upgraded from Release 11i as well as those created in Release 12. end-to-end testing on the complete data set that you intend to run in production. Additionally. upgrade smoothly. once you go live. and encouraging your managers to respond to pending workflow notifications. create a payment in Release 11i. You could consider reducing the number of in-progress workflow items by turning off applications such as iExpenses and iProcurement for some interval prior to your upgrade. You can download the Test Start Kit from the Oracle Application Testing Suite site linked from http://www. especially where you have customized Release 11i preseeded workflow processes or activities. Test performing operations in Release 12. we do even more load and stress testing. and that you resolve any exceptions. Oracle’s Load and Volume Testing Oracle’s Applications IT team has learned from experience that doing adequate performance testing of any system change is critical.1 with matching tax calculations. In particular. and that you resolve any exceptions. However. Even for regularly scheduled small-to-medium changes. Oracle recommends that you test your month-end and quarter-end close and reconciliation with full data volumes. For example. This would validate that setup differences between Release 11i and 12. then void it in Release 12.html.oracle. so you need to find whether there are any data conditions that would fail Release 12. In-progress workflow items should. Oracle recommends that during user acceptance testing.

” replaying concurrent requests pulled from production against a test copy of an upgraded database. you can upload the configuration of your Oracle computing environment. or those who are combining their applications upgrade with an 11g database upgrade follow the advice in the “Upgrade to 11g Performance Best Practices” white paper at My Oracle Support Knowledge Document 1100303. You can associate your configuration with information about your upgrade project that you upload via My Oracle Support. Additional Performance Advice Oracle’s Applications Performance team recommends that Release 12. as well as avoid potential performance issues. While IT and business users bombarded the system with transactions and batch processes. and that you understand and leverage the information.com.oracle. The collected data is sent via secure HTTPS to My Oracle Support. Having knowledge of both your configuration and your project allows Oracle’s support engineers to proactively suggest solutions and resolve issues. as well as with ongoing operations once your upgrade is complete. Using Oracle Configuration Manager. Oracle did a six-hour “User Participation Test” on a Release 12 environment configured with full production processing capacity.go-live testing. Oracle did “batch load tests. In addition.For our Release 12 upgrade. highlighting 11g features that you can use to performance-test the Release 12.1. By isolating these jobs in special queues. and services that are available to you there. Oracle recommends that you download and install the Oracle Configuration Manager (OCM). while being sensitive to critical events in your business that could affect your upgrade. and services that are available to you there. Oracle has found that there is no substitute for letting end users loose on a test environment to introduce a diverse and unexpected mix of transactions and batch load. a support tool that allows Oracle to more proactively assist you with your upgrade. and that you understand and leverage the information. Tip #15 – Engage with Oracle Support Ensure that you have ready access to the My Oracle Support portal.1 database workload. In particular. That’s why. tools.1 Page 17 . where we maintain a Planning Your Oracle E-Business Suite Upgrade from Release 11i to Release 12.1 upgrade customers who are already live on Release 11g of the database. Even with all of this pre. we could control the resources they consumed and ensure that they did not have a detrimental impact on our business. This paper offers advice on optimizing the 11g database upgrade process. looking for stress points and unexpected behaviors. Oracle took the precautionary step of defining special concurrent manager queues into which we could move any jobs that demonstrated performance issues after go-live. This allowed our technical staff to study the behavior of reports running with different parameter settings and to detect any performance regressions. in addition to doing scripted regression testing. Ensure that you have ready access to the My Oracle Support portal at https://support. tools. Oracle’s DBAs studied the system. The Oracle Configuration Manager includes a data collector that is designed to track key Oracle and system parameters for each host on which it runs.

see the “My Oracle Support Health Checks Catalog” at My Oracle Support Knowledge Document 868955.1 upgrade project.1. the Solution Support Center joined with the customer’s hardware vendor to evaluate the customer’s topology. configuration files. the customer found it beneficial to engage an on-site “Solution Support Center Engineer” who worked alongside of the in-house project team.secure and updated view of each host’s configuration. such as installed patches. In addition. and network configurations. To view the full catalog of system health checks available via the Oracle Configuration Manager. To learn more about the Oracle Configuration Manager and the automated services it provides. Planning Your Oracle E-Business Suite Upgrade from Release 11i to Release 12. deployment dates. versions. one of our enterprise customers described engaging with Oracle’s Solution Support Center at the start of their Release 12. patch advice. and based on that recommended a catalog of services. deployed components and applications.1 Page 18 . part of Oracle’s Advanced Customer Services team. For example. The Solution Support Center performed a “Customer Success Assessment”. My Oracle Support provides security and product alerts. Figure 2: Oracle Configuration Manager: Collector You may also wish to take advantage of the highly personalized services available from Oracle’s Solution Support Center. hardware. Using the collected information. and software – which resulted in a change to the customer’s planned CPU and memory configuration. Oracle collects only configuration information. including customized training and knowledge transfer. and system health checks that are specific to your computing environment. In this case. and type. click the “Collector” link under the “More” tab on the My Oracle Support portal.

designed for both functional and technical users. or Oracle Applications Manager. Additionally. “Getting Started with Oracle Application Management Pack and Application Change Management Pack for Oracle E-Business Suite”. Tip #17 – Take Advantage of Oracle E-Business Suite Diagnostics Oracle E-Business Suite Diagnostics consist of a toolset and tests to help you collect and analyze information about E-Business Suite setup and processing issues. Once you are satisfied with the outcome of your test upgrades.1. you can automatically associate a configuration with your Service Request and save the effort of manually entering configuration data. You can also use the diagnostics after you go live to help troubleshoot any issues that may arise.1 Page 19 . see the Oracle E-Business Suite System Administrator's Guide Documentation Set.1. Oracle recommends that you define an incident resolution flow for handling issues internally before you log them as service requests. or Planning Your Oracle E-Business Suite Upgrade from Release 11i to Release 12. You can also set up these tools to take corrective action on common issues and reduce the impact of any incidents. sending informational alerts to warn your system administrators of any incidents. Be sure to designate who will troubleshoot and characterize issues. see My Oracle Support Knowledge Document 166650. We also recommend that you install tools such as Oracle Application Management Pack for Oracle E-Business Suite. “Working Effectively with Global Customer Support. In particular. and who will log and track Service Requests (SRs). If you are using the Oracle Configuration Manager.) To learn more about working with Oracle Support to resolve issues. You can use these diagnostics after each test upgrade to identify and troubleshoot any issues.” Also see My Oracle Support Knowledge Document 199389. The diagnostic tests do not alter your setup or transactional data in any way. Oracle E-Business Suite Diagnostics are easy to use. tracking the details of all open and resolved issues encountered during their upgrade project. These tools can proactively monitor your Oracle E-Business Suite test and production systems. see My Oracle Support Knowledge Document 982302. For more on the Oracle Applications Manager. set up the Oracle E-Business Suite Diagnostics framework and understand how to use it so that you can transmit diagnostic reports to Oracle Support (see Tip #17 for more information.1 for advice on “Escalating Service Requests with Oracle Support Services”. They enable you to avoid issues. For more details on the Oracle Application Management Pack for Oracle E-Business Suite. it’s a good idea to save your diagnostic output so that you can compare it with the diagnostic output that you get just after your production upgrade. Most customers find it helpful to maintain a prioritized issues list.Tip #16 – Develop an Issue Resolution Strategy Develop an issue resolution strategy that spells out how you will address issues that arise during testing. resolve issues on your own.

Be sure to consider the many user interface (UI) improvements in Release 12. This should be done to assist in properly planning your upgrade program.1’s increased personalization capabilities. Oracle E-Business Suite Diagnostics are automatically installed with Release 12. In particular.) Database changes from Release Planning Your Oracle E-Business Suite Upgrade from Release 11i to Release 12. see the Release Content Document for Application Technology (linked from My Oracle Support Knowledge Document 561580. Inventory your customizations and determine which functions could be replaced by standard product in Release 12. Modification. Localization. the redesigned and streamlined workflows. and the improved overall look and feel. note that starting with Release 12.1. For any customizations that remain. It may be possible to defer the implementation of some customizations until after the initial upgrade project. Extension.1.1 for more information. notice the reduction in pop-ups and duplicate screens.1. the reduced number of steps to complete key tasks. eliminating the need for forward-porting.1.1. review country localization features. and the latest versions of the toolset and tests are available through a standard patch. Database changes from 11i.) Validate with your business users which customizations are most critical to them so that you can prioritize your upgrade effort. and Integration) framework review. that may simplify or replace your customizations (See My Oracle Support Knowledge Document 429042. Oracle documents database changes for each major release.1.1 UI and personalization enhancements. In particular. See My Oracle Support Knowledge Document 342459. validate with your business users which customizations are most critical to them so that you can prioritize your upgrade effort.1 Page 20 . A major 11i customer with several thousand customizations observed that at least half of those were already built into Release 12.) For international deployments. Also consider how you can leverage Release 12. so you should change any custom code that references them to reference the relevant Trading Community Architecture (TCA) tables instead. You may wish to consider engaging Oracle Consulting or an Oracle partner to execute a detailed CEMLI (Customization.1.10 to 12 are highlighted in product-specific “Technical Overviews” that are part of the “Release 12 Transfer of Information Online Training” (see My Oracle Support Knowledge Document 988725. new starting with Release 12. the backward-compatible views RA_CUSTOMERS and RA_ADDRESSES are no longer available. To learn more about these 12. Assessing the Impact of Database Changes to Your Custom Code You should review the impact of changes to database objects on your custom code.1 as you evaluate customizations for retirement.obtain diagnostic output that you can upload with a Service Request to speed Oracle’s resolution of your issue. Tip #18 – Inventory Your Customizations and Prioritize Them for Upgrade Inventory your customizations and determine which functions could be replaced by standard product in Release 12.

and reports.1 technology stack.1” (see My Oracle Support Knowledge Document 790942.1 to learn how to MOAC-enable your custom forms.1. identify those that you can move with minimal investment versus those that you need to re-implement. In addition. and Oracle Workflow) and built according to Oracle’s customization standards is.1 after regenerating them using the latest certified version of the Oracle Forms Migration Assistant. For more information on the Forms Migration Assistant and Oracle’s customization standards.1 Page 21 . See My Oracle Support Knowledge Document 420787. as well as the data models for prior releases.) The Electronic Technical Reference Manual (eTRM) documents the full data model for Release 12. Release 12 introduced support for Multiple Organizations Access Control (MOAC). concurrent programs.1. in general. see the Oracle EBusiness Suite Developer’s Guide. For example. Note that starting with Release 12. You can access the eTRM at https://etrm.oracle. which documents the full data model for Release 12.com. consider whether to migrate to newer technologies while you are still running your current E-Business Suite release. which enables access to data in multiple organizations from a single responsibility. or from My Oracle Support Knowledge Document 150230. or to defer migration until your Release 12. See “Preparing Custom Development for the Next Oracle Applications E-Business Suite Release” (My Oracle Support Knowledge Document 374398. Planning Your Oracle E-Business Suite Upgrade from Release 11i to Release 12.1. as well as the data models for prior releases.1 are listed in product-specific Release Notes that are linked from “Oracle Applications Documentation Resources. Release 12. Oracle E-Business Suite migrated to new technologies from these now-deprecated technologies: • • • • mod_plsql Oracle Reports Server Reports Oracle Graphics integrations with Oracle Forms AK mode of Oracle Application Framework If you did custom development using any of these deprecated technologies. you should be able to run your custom forms on Release 12. Release 12. Planning for Re-implemented Customizations Of your remaining customizations. you must reimplement customizations that were developed using now-deprecated technologies.12 to 12.1 upgrade downtime.1.1. compatible with the Release 12. In particular. Adapting Your Custom Code to Architecture and Technology Changes Custom code developed using standard Release 11i development technologies (such as Oracle Forms. Oracle Application Framework pages. Another resource that can help you understand database changes is the Electronic Technical Reference Manual (eTRM). Oracle Application Framework.1) for a discussion of migration alternatives for the deprecated technologies.

There are also some features.You may also need to re-factor or refine customizations that are partially replaced by Release 12. such as flexfields. Wherever possible. Oracle Forms. consider using the standard EBusiness Suite development technologies.1 Page 22 . you can declaratively modify the user interface of OA Framework pages to produce immediate. Customizing with OA Personalization Framework Using the OA Personalization Framework. However. Using the OA Personalization Framework. For example. consider using the standard EBusiness Suite development technologies. These include Oracle Application Framework (using the OA Extension to JDeveloper 10g). consider using the latest Fusion Middleware technologies. For self-contained extensions. where users expect the standard E-Business Suite user experience. Extending with Oracle’s E-Business Suite and Fusion Middleware Development Tools For extensions that are incremental to existing business flows. using OA Personalization Framework. and no need for a separate development tool. there is no impact to the base page definition. visual feedback of changes. For extensions that are incremental to existing business flows. carefully consider your approach. If you must extend the E-Business Suite applications. you cannot build new pages or modify existing business logic such as data validations. visual feedback of changes. titles and text re-order items or regions make items required With OA Personalization Framework. consider using the latest Fusion Middleware technologies. and the OA Personalization Framework – to tailor the applications to your needs. where users expect the standard E-Business Suite user experience. and Oracle Workflow. Oracle SOA Suite. targeted to users who do not require the standard EBusiness Suite user experience. Planning Your Oracle E-Business Suite Upgrade from Release 11i to Release 12. you can extend the value of your current For self-contained extensions. These include the Application Development Framework (ADF). With these tools. that are only available on the standard EBusiness Suite technology stack. Oracle BI Publisher. you can declaratively modify the user interface of OA Framework pages to produce immediate. and Oracle Business Intelligence Enterprise Edition (OBIEE). targeted to users who do not require the standard EBusiness Suite user experience. Oracle WebCenter. you can leverage the same coding standards and user interface components that we use internally at Oracle to create extensions that are tightly integrated with the E-Business Suite. folders. With these tools. any changes that you make are upgrade-safe – patching the base page does not affect existing user interface personalizations. you can: • • • • • hide or show page items or regions add new items change prompts. and you have limited ability to change existing page flows. Additionally. use either the standard E-Business Suite development tools or the latest Fusion Middleware development tools. use E-Business Suite personalization functionality – which includes flexfields. For any customizations that you decide to re-implement.1 functionality or that are affected by significant data model changes.

1. such as Microsoft Word. packaged applications. http://www. (For additional examples of ADF self-service extensions. linked from My Oracle Support Knowledge Document 561580. web services. formerly known as XML Publisher. managing and delivering all types of highly-formatted documents.applications while gaining valuable IT and operational skills that you will need to prepare for Oracle’s next-generation.pdf) • • Releases 12. For more on Oracle Fusion Middleware and the many benefits it provides to the EBusiness Suite.oracle. which allows users to submit requisitions but not access the entire E-Business Suite. For example. Microsoft Excel. End users can easily design report layouts (“templates”) using familiar desktop tools. Fusion Middleware-based applications. Develop a self-service extension to E-Business Suite for “casual” or “infrequent” users of the system who are unconcerned about UI consistency.com/technology/products/applications/ebs/whyfmwisb estmiddlewareforebs. including: Planning Your Oracle E-Business Suite Upgrade from Release 11i to Release 12. For example.pdf • Tip #19 – Consider Migrating Your Reports to Business Intelligence Publisher Oracle Business Intelligence Publisher (Oracle BI Publisher).1 Page 23 . HTTP feeds. or file data sources.) Create an advanced user interface leveraging the AJAX UI capabilities of ADF. you can embed rich content – such as OBIEE analytics or an ADF task flow – into an OAF page to produce an advanced UI. using ADF you could create a simplified.oracle.1.oracle. BI Publisher merges template files with XML data to produce a wide variety of formatted outputs.pdf “Application Upgrades and SOA”.com/applications/evolutionary-path-to-fusion.3 provide additional functionality that allows you to flexibly combine E-Business Suite and Fusion Middleware development technologies. For more on this topic. see the Release Content Document for Application Technology. see “The Evolutionary Path: Things You Can Do Today to Prepare for Oracle Fusion Applications” at http://www. see the following white papers: • “Oracle E-Business Suite and Oracle Fusion Middleware”. BI Publisher can query or accept data from practically any data source – databases. efficient user interface. is an enterprise reporting solution for authoring. launched from the EBS home page.1. you can: • Create a composite application spanning E-Business Suite and one or more other applications (packaged or custom. http://www. For example.2 and 12. At runtime.com/technologies/soa/docs/soa-applicationupgrades. or Adobe Acrobat.

but your formatting will remain valid for Release 12. "Filled-out" third-party provided PDF documents. For example. contracts. We recommend that you convert any custom reports based on mod_plsql to BI Publisher. you may need to adjust the queries you use to produce the report output. which embeds both data extraction logic and report layout. as well. Tip #20 – Review Your Integrations and Consider Modernizing Them Consider whether certain integrations would be easier to maintain and upgrade if they were modernized using tools from the Fusion Middleware Suite. marketing materials. and converts it to the separate data extract and layout objects necessary for a BI Publisher report. Release 12. and purchase orders using colors. For BI Publisher-based reports. Oracle provides a migration utility to facilitate the conversion of Oracle Reports to BI Publisher reports. As you inventory your custom code. your data and template merge to produce a "filled-out" form. look for “brittle” integrations or needless data replications. Consider converting your custom Oracle Reports reports to BI Publisher. also inventory your integrations and make a plan to re-test and re-tune them. “Oracle Report to XML Publisher Report Migration” in the Oracle XML Publisher Administration and Developer’s Guide. DBLink). Consider converting your custom Oracle Reports reports to BI Publisher as well. Integrations implemented “point to point”. HTML output for optimum online viewing. you can use a government form in PDF as a template. footers. The conversion process takes an Oracle Reports RDF file. If you move your custom reports to BI Publisher before upgrading to Release 12. such as financial statements.• Customer-ready PDF documents. images. Flat text files to exchange with business partners for EDI and EFT transmission. invoices. see Appendix D. At runtime. where data is transformed as it moves between different data schemas used by different applications that may be evolving independently from one another. many more standard reports used BI Publisher. and with Release 12. headers. and other formatting and design options. Excel output to create a spreadsheet of your report data. application-independent data model that can act as a • Planning Your Oracle E-Business Suite Upgrade from Release 11i to Release 12. For example. font styles.1. which depend upon a particular database schema and circumvent the application’s own validation logic. Today’s best practice is to leverage a canonical. To learn more about the migration process. With Release 12.1. an XML data extract is provided along with a default layout (template) that you can easily modify. • • • • BI Publisher was used in Release 11i.10 for high-fidelity formatting of many external documents.1 nearly all reports use it. including: • Integrations implemented using database synchronization (for example. We recommend that you convert any custom reports based on mod_plsql to BI Publisher.1 Page 24 . Consider whether certain integrations would be easier to maintain and upgrade if they were modernized using tools from the Fusion Middleware Suite.

responsibilities. occurred. and so on). which are less resilient to exception and error handling. menus. We also suggest that you use Oracle B2B instead of Oracle EDI Gateway or Oracle XML Gateway to develop any new B2B integrations. or functions. for example using a visual BPEL process flow. For example.hub for all integrations.1 upgrade or a companion project to re-implement any problem integrations. from “roles” and “responsibilities” down to the “functions” (secured operations) in the Oracle EBusiness Suite. you can evaluate all business transactions to see if any SOD violations have. • Complex integrations implemented using programmatic. sub-menus. with Enterprise Transaction Controls Governor.1 Page 25 . In addition. Oracle Fusion Middleware components. You should reexamine user roles and responsibilities due to business process changes introduced starting with Release 12. Planning Your Oracle E-Business Suite Upgrade from Release 11i to Release 12. who should be responsible for any issues related to the new tax and subledger engines? Who will read and interpret the related exception reports? You should also consider whether users have access to data and functions that are incompatible with each other from a segregation of duties (SOD) perspective. • Decide if you should take the opportunity of the Release 12. In addition. hard-to-debug procedures. responsibilities. Oracle Data Integrator can be leveraged for batch-style data integrations. Included with Applications Access Controls Governor is the ability to ask “what if?” or to simulate changes to the authorization model (menus. in fact. Oracle Application Integration Architecture (AIA) is Oracle's product offering that implements a best practice canonical service model. Tip #21 – Reexamine User Roles and Responsibilities and Business Processes You should reexamine user roles and responsibilities due to business process changes introduced starting with Release 12. With Oracle Applications Access Controls Governor. such as those based on PLSQL. the Oracle Applications Access Controls Governor provides the ability to analyze the entire access model. Integrations completed as batches. such as Oracle SOA Suite. and to include approval steps before assigning access rights that represent an SOD risk. Starting with Release 12. can help you leverage the realtime integration capabilities made possible through the service-enablement of the E-Business Suite achieved through the Integrated SOA Gateway.) The application can then report occurrences of users with incompatible access points so that managers can modify the privileges and tasks assigned to them. versus integrations implemented declaratively. you can designate any combination of incompatible access points (roles.

You can also deploy Tutor and UPK in the Release 12. ensuring that users always have access to the latest information.1 implementation. UPK allows you to train current users on Release 12. Oracle offers tools to document business processes and train end users that can help you transfer knowledge on the use of your system to business process owners and business users. you can also generate role-specific end user desk manuals and a variety of job aids. Oracle offers over 2300 pre-recorded UPK topics for Release 12.1 to accomplish your business processes. you can create training on how to use Release 12.com/applications/tutor/tutor-upk-index. With Tutor. policies. These tools support efficient capture of knowledge during your upgrade project. You can start with the model business processes delivered with Oracle Tutor and customize them to reflect your Release 12. More information about Oracle Tutor and UPK is available at http://www. and procedures that your Release 12. Using these as a starting point.1.1 applications will support.1 products.1 changes before you provide them with a live Release 12. and facilitates the training of new users at any point after the initial rollout. and just in time maintenance of knowledge after your project is over. Oracle Tutor is an easy-to-use Microsoft Word-based tool for documenting the business processes.1 online help system. Oracle User Productivity Kit (UPK) is a powerful tool for training end users on how to use the system to accomplish your business processes. The availability of these simulations may help end users become familiar with Release 12.html.oracle. UPK allows you to record the flow through application screens and data entry fields. Figure 3: Oracle User Productivity Kit (UPK) Planning Your Oracle E-Business Suite Upgrade from Release 11i to Release 12.1 Page 26 . allowing users to learn about your enterprise’s policies and procedures by clicking the Help button on any screen. creating interactive UI simulations.Tip #22 – Consider Using Oracle’s Process Documentation and End User Training Tools Oracle offers tools to document business processes and train end users that can help you transfer knowledge on the use of your system to business process owners and business users.1 environment.

1 Info Center highlights Announcements. See http://education.Tip #23 – Acquire Release 12. Project team members new to Oracle E-Business Suite or those needing a refresher should consider enrolling in training offered by Oracle University. a good place to start is the “Oracle E-Business Suite Release 12.1. Planning Your Oracle E-Business Suite Upgrade from Release 11i to Release 12. Figure 4: Oracle E-Business Suite Release 12. My Oracle Support Knowledge Document 806593. For those inclined to self-study.1.com for a catalog of available offerings.oracle.oracle.1 Knowledge Oracle provides a wealth of information resources to help you come up to speed on Release 12.1 Info Center You can also take advantage of the Release 12. including suite-level installation. Customer Advisor Webcasts. see My Oracle Support Knowledge Document 429042.1 Page 27 . For international deployments. and administration guides. upgrade. and more. as well as product-specific implementation and user’s guides.1 Documentation Library.1 Info Center”. Transfer of Information Online Training. Release Value Propositions. The Documentation Library contains Adobe Acrobat versions of all the Oracle EBusiness Suite guides. Release Content Documents.html. The Release 12.com/technology/documentation/index.1 to access user’s guides with full details of country-specific localizations. available online at http://www.

Figure 5: Release 12. respectively. and Document 807319. see the Release Content Documents for Release 12.1. Release Value Propositions can help you plan your IT projects and investments. see the preceding 11i Release Content Documents. available from My Oracle Support Knowledge Document 804373.1 Your application specialists should review Release 12. Transfer of Information (TOI) online training is another source of “what’s new?” information.1 links to Release 12 TOIs.1 links to Release 12.10.1 Documentation Library “What’s New?” in Release 12.1 (the “why”). Release Content Documents detail the new and changed features (the “what” and the “how”. “Oracle Applications Documentation Resources. Technical TOIs are replaced by product-level Release Notes.1. Organized by product or major feature. plus those for Release 12.10. Technical changes to database objects. including changes to setup and usage flows. profile options.5. They can help you plan your IT projects and investments.1.1 (See My Oracle Support Knowledge Document 404152.1).) To learn about new and changed features since Release 11.1 upgrade to your senior management.1 and Document 561580.) Starting with Release 12. Whereas the Release Value Propositions present the business benefits of Release 12. understanding new features and process changes that come by default. My Oracle Support Knowledge Document 988725.1.1 Page 28 . and position the value of a Release 12. linked from My Oracle Support Knowledge Document 790942.1 TOIs. describe the functionality new with Releases 12 and 12. TOIs enable self-service learning about functional changes and enhancements.5.) If you are coming from a release earlier than 11. Transfer of Information (TOI) online training is another source of “what’s new?” information. Release Planning Your Oracle E-Business Suite Upgrade from Release 11i to Release 12.1. as well (My Oracle Support Knowledge Document 163400. The Release Value Propositions.1 in terms of value to your business.1 enhancements module by module. and position the value of a Release 12. and so on are detailed in Release 12 Technical Overview TOIs (My Oracle Support Knowledge Document 988725. code objects. along with optional new features that you may want to implement.1 upgrade to your senior management.

the guide contains two main sections: • The initial chapters. Financials Concepts The Oracle Financials Concepts Guide. Figure 6: Oracle E-Business Suite Upgrade Center The primary source for upgrade information is the Oracle E-Business Suite Upgrade Guide.1”. describe technical tasks to perform before.1.1 Page 29 .1 Financials products. The “Oracle E-Business Suite Upgrade Center”.1. Release 11i to Release 12. and Compliance Business Analytics and Corporate Performance Management Tip #24 – Fully Utilize Available Upgrade Information The “Oracle E-Business Suite Upgrade Center” on My Oracle Support is a repository of documentation and advice on each phase of the upgrade life cycle. is a repository for documentation and advice on each phase of the upgrade life cycle. during.12. at My Oracle Support Knowledge Document 461705.1. targeted to database administrators (DBAs). Planning Your Oracle E-Business Suite Upgrade from Release 11i to Release 12. The product-level Release Notes also highlight “Known Issues” that you should be aware of as you plan your upgrade. It highlights key Financials architectural and process changes since Release 11i.1 is a “must read” for anyone deploying the Release 12. Release 12. Risk Management. To present a complete picture of the upgrade process and resulting functional impacts. and after the upgrade. and explains the concepts underlying the setup and use of: • • • • • • Organization Models Reporting Accounting Worldwide Operations Governance.

1. It also indicates critical patches that your system requires. The Maintenance Wizard can help you reduce upgrade tasks by filtering out those that do not apply to you. It explains how 11i Financials setup and transaction data are upgraded.) Tip #25 – Consider Using the Maintenance Wizard The Maintenance Wizard is a free tool that provides a step-by-step. which details process changes. It can automatically execute upgrade tasks for you.1) that provides a step-by-step.1 Page 30 . Financials Upgrade There is a separate guide that focuses on Financials upgrade impacts: Oracle Financials and Oracle Procurement Functional Upgrade Guide: Release 11i to Release 12. and post-upgrade tasks for verifying that transactional data upgraded correctly. describe functional impacts on user interfaces and processes. You can use Oracle’s Maintenance Wizard to record the outcome of your various test upgrades. operational. Setup and Operational Tips” (My Oracle Support Knowledge Document 11041631. and other upgrade considerations that your Financials applications specialists should understand (see My Oracle Support Knowledge Document 889733. graphical user interface for performing upgrade tasks.) A collection of detailed upgrade preparation.• The appendices. targeted to application specialists.1 Financials Pre-Upgrade. configuration changes.1. annotating individual upgrade steps with hints. setup. or Planning Your Oracle E-Business Suite Upgrade from Release 11i to Release 12. and troubleshooting tips is maintained in “Oracle E-Business Suite R12. It consolidates instructions from the upgrade guide with other relevant documents to present a complete picture of the upgrade process. The Maintenance Wizard is a free tool (available via My Oracle Support Knowledge Document 215527. and maintains a log with status information for all executed tasks. lessons learned. addressing questions such as: • • • • • • What happens to my Tax Codes? How are the new Payables Invoice Lines derived? How are Legal Entities derived? How does the Accounting Setup Manager get set up? How will my Bank Accounts be migrated? How are Suppliers and Supplier Sites moved into Trading Community Architecture (TCA)? How have Global Descriptive Flexfields changed? How have Profile Options changed? • • Additional Financials upgrade planning advice is provided in the “R12 Upgrade Considerations by Product: Financials”. graphical user interface for performing upgrade tasks. functional pre-upgrade tasks for reducing downtime.

taking system backups. You can even create custom steps at the appropriate spots in the tool so that custom actions won't be forgotten on subsequent upgrade attempts. TUMS examines your current configuration and generates a report that indicates which tasks do not apply to your system and can be omitted from the upgrade process (for example. and so on. a task required for a product that you do not use or for applying a patch that you have previously applied. Release 11i to Release 12. leaving only un-posted and newly posted journals to upgrade during downtime. carefully choreographing your downtime activities to minimize their duration. Appendix E of Oracle E-Business Suite Upgrade Guide.advice that will help you during your production upgrade. See “Scheduling Time for an Upgrade” in Chapter 1 of the Oracle E-Business Suite Upgrade Guide. The Maintenance Wizard also keeps logs for each execution of each step. when it happened and who did it. Pay special attention to the instructions about running “The Upgrade Manual Script” (TUMS).) In addition. The best way to minimize production downtime is to perform a number of complete test upgrades.1 describes functional pre-upgrade tasks that you can perform ahead of your upgrade outage to reduce downtime. Planning Your Oracle E-Business Suite Upgrade from Release 11i to Release 12. Release 11i to Release 12.1. such as running clean-up scripts.1 Page 31 . it describes how you can upgrade posted General Ledger Journal Entries before your planned downtime.1 to learn about issues that affect downtime duration and the actions Oracle recommends to reduce downtime. carefully choreographing your downtime activities to minimize their duration. Be sure to focus on the duration of operational tasks that you perform before and after you run the core upgrade driver. For example.1. so you have documentation of what happened. Figure 7: Maintenance Wizard Tip #26 – Take Steps to Minimize Downtime The best way to minimize production downtime is to perform a number of complete test upgrades.

Below we describe. If you do not update all of your accounting data during the upgrade downtime.1 upgrade process.1. while giving you the flexibility to upgrade the omitted data at any time after the initial upgrade. During the upgrade. for illustrative purposes.1.1 and “Use of Multiple Organizations (Multi-Org) in Release 11i”. to ensure that at least six periods are included in the upgrade. as well as the necessary periods of the previous fiscal year. However. you should consider using “Upgrade by Request” for your historical accounting data. Oracle performed a Planning Your Oracle E-Business Suite Upgrade from Release 11i to Release 12. if you need to cancel invoices from two years ago. you have the flexibility to limit the amount of subledger data you update during the upgrade to reduce downtime and save on disk space. that you can consider making during regular 11i maintenance windows to reduce your Release 12. either during daily business operations.1) “Upgrade by Request” Appendix G of Oracle E-Business Suite Upgrade Guide. In particular. This is an important decision because some SLA functionality relies on the existence of previous accounting data. For example. In particular. Several months before our Release 12 upgrade. For example. you can specify that a larger range of periods be upgraded. existing accounting data from the subledgers is upgraded into the new Subledger Accounting (SLA) data model. different enterprises will make different project scoping decisions that will affect the duration of their upgrade downtime. My Oracle Support Knowledge Document 210193. “Determine Your Project’s Technical Scope”.1 upgrade downtime. you can perform additional updating at a later point. introduced by the Release 12.1 describes “Upgrade by Request” options that allow you to omit certain historical data from your initial upgrade process (downtime window). you could convert to the new Oracle Applications Tablespace Model (OATM) and also to the new Multiple Organizations (Multi-Org) architecture while you are still on 11i. My Oracle Support Knowledge Document 248857. You can change the amount of historical accounting data to be upgraded to SLA as a pre-upgrade step. By default. Release 11i to Release 12. How Oracle Minimized Upgrade Downtime As discussed under Tip #3. then you need to upgrade at least two years of accounting data to SLA. how Oracle minimized downtime during our Release 12 upgrade: • Separated the database upgrade – The E-Business Suite upgrade requires that a minimum database version be in place before the upgrade driver can run.1 describes systems architecture changes. or during a subsequent downtime. Chapter 1 of the Oracle E-Business Suite Upgrade Guide. Release 11i to Release 12. (See “Oracle Applications Tablespace Model Release 11i – Tablespace Migration Utility”. the upgrade updates the data for the current fiscal year.Additionally.1 Page 32 .

The remaining 12 years of SLA data remain in the database should we choose to upgrade it in the future. Oracle upgraded just 8 out of 20 years of Subledger Accounting (SLA) data. Oracle’s applications specialists completed all of the functional tasks listed in the “Reducing Downtime” section (Appendix E) of the upgrade guide. while the upgrade driver was running on the database. My Oracle Support Knowledge Document 761570.1 Page 33 .1. Parallelized pre. with a transition outage months in advance of the Release 12 upgrade.) Prior to our Release 12 upgrade.3). Created a “Master” R12 APPL_TOP – Prior to the upgrade downtime. Used “Upgrade by Request” – Using the “Upgrade by Request” option.0. This project was managed separately. and we re-registered single sign-on.1 Upgrade”.required database upgrade to 10g Release 2 (10. Oracle upgraded the middle tier hardware and operating system to a new standard. see the “Best Practices” section of “Oracle Applications Release 12 Upgrade Sizing and Best Practices”. reducing downtime and data volume.1. Completed functional tasks ahead – A week prior to the Release 12 upgrade outage. For more information. reducing the number of middle tier servers by 40%. and a shared APPL_TOP (applications file system. My Oracle Support Knowledge Document 399362.1. Oracle performed technical upgrade tasks in parallel.2. For example. generation of files such as forms. with all file system patches pre-applied. We set up a separate concurrent manager queue for these requests. This was managed as a separate project with its own complete cycle of testing.and post-upgrade technical activities – Where feasible. Prioritized concurrent programs (requests) that must complete prior to system release – The upgrade process itself submitted over 2000 concurrent requests. we performed Release 12 setups on the middle tiers. • Separated hardware and operating system upgrades – Oracle has a common middle tier hardware and software footprint. If you registered for the most recent Oracle Planning Your Oracle E-Business Suite Upgrade from Release 11i to Release 12. • • • • • Leaders of Oracle’s Applications IT organization periodically give presentations at user conferences where they provide more details on the practices Oracle has followed to reduce upgrade downtime. For more information. see “Database Preparation Guidelines for an Oracle E-Business Suite Release 12. so that post-upgrade testing of standard run-time requests could proceed without interference from upgrade-related processes. In addition. we created a “Master” staged APPL_TOP using the most recent test upgrade. reports and message files was performed before the upgrade downtime.

1. Plan to apply these patches during your test upgrades so that you can assess their impact and identify any additional fixes you might need. My Oracle Support Knowledge Document 798258.and Post-Upgrade Patches As you prepare for your upgrade. Go to the Recommended Release 12 Patches list on the My Oracle Support Patches and Updates tab to learn about critical patches for the products you plan to deploy. My Oracle Support Knowledge Document 1127593. including information about high-priority patches.com/rednetwork. Make sure you identify the latest Consolidated Upgrade Patch (see the “Oracle Applications Release Notes. a list of critical pre-upgrade patches that are supplemental to the Consolidated Upgrade Patch (CUP) is maintained in “R12. For Financials customers.1. The Consolidated Upgrade Patch is targeted specifically to customers who have not yet upgraded their environment from 11i to Release 12. Release 12. “What is a Generic Datafix Patch (GDF) and what GDFs are available for Payables?” In particular. My Oracle Support Knowledge Document 798258. see the “Oracle Applications Release Notes.1 Page 34 .1. it is also highly recommended to review the list of Generic Data Fix patches described in My Oracle Support Knowledge Document 874903. My Oracle Support Knowledge Document 954704. for latest release information.1”. Release 12. you can download these presentations and listen to live recordings of them at: http://www. Release 11i to 12. In addition.1.1.1.1: Oracle Financials Pre-Upgrade Patch – Supplemental List for EBS CUP”.and post-upgrade patch list: • Review the required pre-upgrade patches identified in Appendix I of the Oracle E-Business Suite Upgrade Guide. These GDF patches. make sure you maintain an up-to-date list of required and recommended pre. pay attention to any Generic Data Fix (GDF) patches designated as “Pre-Upgrade”.1.1 Upgrade Driver.1) and apply it to your Applications Code Tree (APPL_TOP) prior to running the Release 12.1 – you need not apply these fixes to environments that have already been upgraded to Release 12. Plan to merge the appropriate patches and apply them when your Release 12. • • • • Planning Your Oracle E-Business Suite Upgrade from Release 11i to Release 12.1 Financials Recommended Patches”. so pay close attention to the patch instructions.oracle. a list of post-upgrade Financials recommended patches is maintained in “R12. For Financials customers. As needed. Below are some key resources to help you identify patches you should include in your pre.1. Also.1 upgrade is complete. Tip #27 – Identify Required and Recommended Pre.OpenWorld conference.and post-upgrade patches applicable to your environment and licensed products. Some patches may need to be applied PRIOR to the upgrade to have the desired impact.1.1”. Oracle releases a Consolidated Upgrade Patch (CUP) that contains critical error corrections and performance improvements to the EBusiness Suite upgrade process.

In addition. Tip #29 – After Your Go-Live.1. After your upgrade is complete. see My Oracle Support Knowledge Document 403537. application server.1. continue to consult My Oracle Support for the latest information on the Oracle E-Business Suite.1 Page 35 . clean up data issues. For more information about CPUs and advice on keeping your system secure. stay current with the latest available code. Tip #28 – Review your System for Compliance with Security Best Practices A major upgrade is a good time to review your system for compliance with secure deployment best practices.1. and you are live on Release 12. that commonly cause issues in Release 12+ Financials. customers should consider whether it is more efficient to proactively apply RUPs and critical patches at their earliest maintenance opportunity. monitor the Recommended Release 12 Patches list on the My Oracle Support Patches and Updates tab to learn about recommended patches for the products you have deployed. take advantage of the 12. The Release 12. continue to consult My Oracle Support for the latest information on the Oracle E-Business Suite. For example. Stay Current with Latest Information After your go-live. Oracle consolidates security patches for database. and testing fixes for what ultimately are found to be known issues. After your go-live. stay current with the latest available code. “Best Practices for Securing Oracle EBusiness Suite Release 12”. and you are live on Release 12.1. Tip #30 – After Your Go-Live. To ensure that you have up-to-date fixes and performance improvements for the patching infrastructure and for the application technology and management products.1. which consolidate the latest maintenance fixes for the release.which should be run on 11i prior to upgrading to Release 12 or 12. It is particularly important for Financials customers to stay current with latest code. introduced by known bugs. Since the alternative may be to cycle through the timeconsuming process of identifying. Oracle maintains a document highlighting Release 12. Oracle appreciates that customers are sometimes reluctant to apply the latest RUP or critical patch because they are concerned about the time needed to apply and test these recommended fixes. fixing.1 Info Center on My Oracle Support is kept up-to-date with the latest information on certifications. we also recommend that you stay current on the latest AD and ATG Family RUPs. Oracle strongly recommends that you apply the latest available CPU patches before you upgrade and on an ongoing basis. qualifying. Contact your Oracle Support representative for any additional patches you may need beyond those you have already identified. reporting.1.1 Financials recommended patches at My Oracle Support Knowledge Document 954704. Stay Current with Latest Code After your upgrade is complete.x Release Update Packs (RUPs). Planning Your Oracle E-Business Suite Upgrade from Release 11i to Release 12. and Oracle E-Business Suite code in Critical Patch Updates (CPUs) that are released quarterly.

You can also use the Oracle Technology Network (OTN). release notes. (See http://forums.oracle.com/technology. tagging.1 Page 36 . It allows you to personalize the My Oracle Support interface to show the information most relevant to you.1) Take advantage of the Web 2. there is an associated discussion thread that you can participate in and mine for additional insights and advice. document exchange. or an update has been made to an SR. at http://www. and RSS feeds—that allow you to stay informed about the E-Business Suite topics that matter most to you.Release Update Packs.oracle. (See My Oracle Support Knowledge Document 806593.oracle.com and http://blogs. My Oracle Support also provides multiple community channels—such as discussion forums.com) Planning Your Oracle E-Business Suite Upgrade from Release 11i to Release 12. you can receive notifications when Knowledge Base information on selected products has been published or updated. diagnostics. For many blog entries. documentation resources.0 technology built into My Oracle Support. and so on. It also lets you designate Knowledge Documents and service requests as “Favorites” so that you can quickly find them again. Using the “Hot Topics E-Mail” feature. people finder. to access forums and blogs on a wide range of Oracle E-Business Suite and other related topics.

1: Oracle Financials Pre-Upgrade Patch -.1 988725.1 420787.0.1 163400.1 166650.1 1127593. Reimplementation (Financials)” “Test Start Kit Information Center” “My Oracle Support Health Checks Catalog” “Getting Started with Oracle Application Management Pack and Application Change Management Pack for Oracle E-Business Suite” “Working Effectively with Global Customer Support” “Escalating Service Requests with Oracle Support Services” “Oracle E-Business Suite Diagnostic Tools Overview” “Introduction to Add-On Localizations for Release 12” “Oracle E-Business Suite: Release 12 Transfer of Information (TOI) Online Training” “Oracle Applications Documentation Resources.1 804373.1 Upgrade” “What is a Generic Datafix Patch (GDF) and what GDFs are available for Payables?” “Oracle Applications Release 12 Upgrade Sizing and Best Practices” “Best Practices for Securing Oracle E-Business Suite Release 12” “EBS: R12.1 889733.1 399362.1 403537.1 868955.1 342459. Setup and Operational Tips” “Maintenance Wizard Overview” “Oracle Applications Tablespace Model Release 11i – Tablespace Migration Utility” “Use of Multiple Organizations (Multi-Org) in Release 11i” “Database Preparation Guidelines for an Oracle E-Business Suite Release 12.1 561580.1 Transfer of Information (TOI) Online Training” “Oracle E-Business Suite Upgrade Center” “Upgrade Considerations by Product: Financials” “Oracle E-Business Suite R12.1 Info Center” “Oracle E-Business Suite Release 12.1 Release Value Propositions” “Release Content Documents for E-Business Suite Release 12 and 12.1 Page 37 .1 374398.1 11041631.1 806593.x Release Update Packs” “Oracle E-Business Suite Release 12.1 Release Content Documents” “Release Content Documents and Feature Summary Matrices” “Oracle E-Business Suite Release 12.1 404152.My Oracle Support Knowledge Document References ID 780989. Release 12.1 150230.1 215527.1 807319.Supplemental List for EBS CUP” Planning Your Oracle E-Business Suite Upgrade from Release 11i to Release 12.1 982302.1 461705.1 Oracle Financials Recommended Patches” “R12.1 248857.1 954704.1 210193.1 874903.1 Document “R12: Upgrade vs.1 429042.1.1 761570.1 199389.1 239746.1 790942.1” “eTRM Direct Access Document” “Oracle Applications Multiple Organizations Access Control for Custom Code” “Preparing Custom Development for the Next Oracle Applications E-Business Suite Release” “Oracle E-Business Suite Release 12.1 Financials Pre-Upgrade.

3 Release Update Pack (RUP). to include advice on personalization and extension of Oracle E-Business Suite. on upgrading customizations.1 Financials Pre-Upgrade. Also expanded Tip #18. and Operational Tips” in Tip #24.1 Value Proposition to include a reference to the 12.1 Page 38 . Setup.Change Record Date 4-March2010 30-March2010 12-August2010 Version 1. Added a reference to “Oracle E-Business Suite R12. Revised Tip #19 to include more information on how BI Publisher works and on how to convert Oracle Reports to BI Publisher reports.1 1.1 Revised Release 12.0 Change Reference First published version 1. Added references to Financials recommended patching documents in Tip #27. and on when to consider using standard E-Business Suite development tools and Fusion Middleware development tools. to include a reference to the Test Starter Kit for the Oracle Application Test Suite. Updated Tip #12.1. Planning Your Oracle E-Business Suite Upgrade from Release 11i to Release 12.3 Removed reference to obsolete My Oracle Support Document 580299.2 25-January2011 1. on test strategy. Inserted a new Tip #20 on reviewing your existing integrations to determine if they should be modernized using tools from the Fusion Middleware Suite.

Victoria Pickard.7200 oracle. Udayan Parvate. Cliff Godwin. . Anand Subbaraman. without our prior written permission.com Copyright © 2010. Steven Chan. Nigel Cooper.7000 Fax: +1.650. Adam Lief. Veshaal Singh. Sarah Bowen. Nirajita Mitra. Amrita Mehrok. This document is provided for information purposes only and the contents hereof are subject to change without notice. All rights reserved. Biju Mohan. Robert Farrington. Kevin Dahms. CA 94065 U. This document may not be reproduced or transmitted in any form or by any means. Mark Stebelton. George Buzsaki. nor subject to any other warranties or conditions. Murali Subramanian. electronic or mechanical.1 January 2011 Author: Anne Carlson Contributors: Isam Alyousfi. Worldwide Inquiries: Phone: +1. Krishna Prasad Ramkumar. Chris Cianciolo. Elise Mattei.S. Srikanth Krishnan.506. Kevin Hudson.Planning Your Oracle E-Business Suite Upgrade from Release 11i to Release 12. Markus Zirn Oracle Corporation World Headquarters 500 Oracle Parkway Redwood Shores. Other names may be trademarks of their respective owners.506. This document is not warranted to be error-free. Jacques Bouchet. Rondy Ng. Dennis Horton. Nick Reichenbach. Kirsten Klagenberg.A. Nadia Bendjedou. Anand Naik. Nayyar Siddiqui. Terrance Wampler. Nick Zaveri. Bill Bounds. Mark Peachey. Scott Bangert. Oracle is a registered trademark of Oracle Corporation and/or its affiliates. Siddharth Sinha. Donna Buhlig. Oracle and/or its affiliates. Vasu Rao. Jen Sherman. Krithika Bhat. Cheryl Ludwig. Ognjen Pavlovic. for any purpose. Pamela Fisher. Deep Ram.650. Scott Lockridge. including implied warranties and conditions of merchantability or fitness for a particular purpose. Lisa Parekh. Lester Gutierrez. whether expressed orally or implied in law. Mazen Khanfar. Stuart Dunsmore. Matthew Halliday. Ivo Dujmovic. We specifically disclaim any liability with respect to this document and no contractual obligations are formed either directly or indirectly by this document. Simer Sahani. Vickie Parrott. Mildred Wang.

Sign up to vote on this title
UsefulNot useful