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

1
An Oracle White Paper March 2010

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.......................... 12  Tip #8 – Determine Your Data Migration Strategy ......................... 12  Tip #9 – Assemble a Project Team that Combines Technical and Functional Skill Sets............................................................................... 13  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............................. 17  Tip #15 – Engage with Oracle Support ............................................. 18  Tip #16 – Develop an Issue Resolution Strategy.............................. 19  Tip #17 – Take Advantage of Oracle E-Business Suite Diagnostics20  Tip #18 – Inventory Your Customizations and Prioritize Them for Upgrade ................................................................................................... 20  Tip #19 – Consider Migrating Your Reports to Business Intelligence Publisher............................................................................. 22  Tip #20 – Reexamine User Roles and Responsibilities and Business Processes.................................................................................................. 22  Tip #21 – Consider Using Oracle’s Process Documentation and End User Training Tools ...................................................................... 23  Tip #22 – Acquire Release 12.1 Knowledge...................................... 24 

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

Page 2

Tip #23 – Fully Utilize Available Upgrade Information.................. 26  Tip #24 – Consider Using the Maintenance Wizard ........................ 27  Tip #25 – Take Steps to Minimize Downtime.................................. 28  Tip #26 – Identify Required and Recommended Pre- and PostUpgrade Patches..................................................................................... 31  Tip #27 – Review your System for Compliance with Security Best Practices ................................................................................................... 32  Tip #28 – After Your Go-Live, Stay Current with Latest Code..... 32  Tip #29 – After Your Go-Live, Stay Current with Latest Information ............................................................................................. 32  My Oracle Support Knowledge Document References ....................... 34  Change Record ............................................................................................ 35 

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

Page 3

IT. Following a brief overview of the Release 12. Release 12” paper published in June 2008 – this paper combines advice from professionals in Oracle’s Support. this paper tells you “things you wished you knew” before embarking upon your Release 12. Planning Your Oracle E-Business Suite Upgrade from Release 11i to Release 12. and Development organizations with real-life lessons learned from customers who are already live on Release 12. Similar to the “Best Practices for Adopting Oracle E-Business Suite. As we gather additional Release 12.Planning Your Oracle E-Business Suite Upgrade from Release 11i to Release 12.1 upgrade project are the primary audience. and avoid missteps that can needlessly increase your scope Assemble the right project team Develop a robust testing strategy 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. In a nutshell.1 INTRODUCTION This white paper offers best practice advice to customers currently on Release 11i who are planning a Release 12.1 Page 4 .1 upgrade. we will revise and re-publish it as My Oracle Support Knowledge Document 987516. IT professionals involved with planning.1 upgrade planning advice.1.1 upgrade project.1 upgrade value proposition. 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.1. Consulting. managing. or running a Release 12.

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

1 Value Proposition Release 12.1 rounds out Release 12 with significant enhancements to all of the other product areas.1 Page 6 . Earnest Money Deposits. and enabled our customers’ compliance with local reporting obligations. recruitment dashboards. two-stage evaluation of Request for Proposal (RFP). board quality financial statements or government mandated forms. new capabilities such as spend classification and analysis have also been added High volume warehouse operations support. and Cost Factors and Price Factors. these include Excel integration to run what-if analysis. charts.Release 12 made producing all types of reports much easier – whether reports that include images. including summarization of all talent information in a single user-friendly Talent Profile page. and integration with Oracle Transportation Management • Optimization of supply. demand-based forward pick replenishment. including advanced wave planning. enforce compliance and reduce risk. 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. Release 12. multiple fonts and colors. demand and design chains with the new Value Chain Planning solutions in Oracle Supply Chain Management • • Talent Management improvements. 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. 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. In addition.1 rounds out Release 12 with significant enhancements to all of the other product areas.1 and in related analytics and integration solutions are: • Sourcing enhancements to streamline sourcing processes. Planning Your Oracle E-Business Suite Upgrade from Release 11i to Release 12. and achieve sustained savings.

a new succession planning module. In December 2009. and improvements in usability and user experience. we introduced two new products – Supplier Lifecycle Management and Supplier Data Hub.interview management. and so on.1 Page 7 . We also released new and enhanced Applications Integration Architecture (AIA) integrations. More specifically. and two new analytical applications – Incentive Compensation Analytics and Spend Classification. also. which contains statutory and regulatory updates as well as enhancements across the EBusiness Suite product areas. as well as continued support for Global HR and Payrolls • Ability to view fully-loaded estimated costs (including transportation.2 release update pack (RUP). and optimized and streamlined Service Request Creation & Management for faster data entry Supplier Lifecycle Management and Supplier Data Hub to support extended supplier registration. dashboards. including Web 2. Partnership with Trimble for GPS Support. • • Extending the overall 12. Telecommunications and anyone else • • We continue to add new functionality to Release 12. we provided the Release 12. learner groups and mandatory enrollment in Learning Management. Oil & Gas.1 release. In addition. objectives management and line of sight/cascading of objectives in performance management. duties. Planning Your Oracle E-Business Suite Upgrade from Release 11i to Release 12. as well as support for embedding rich content such as business intelligence reports. Utilities.1 on a regular basis. and look-ahead searching. we announced the availability of the Oracle Procurement On Demand service delivery model. 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. profiling and performance management. Mobile Field Service technician screen personalization and auto sync.1. Key highlights include enhancements in Service and Field Service and in Supplier Lifecycle Management.0 controls such as mouse-over and pop-ups. along with Master Data Management capabilities such as de-duping and merging Usability enhancements across the E-Business Suite. we delivered: • Service and Field Service Dispatch Enhancements for improved Dispatch Center Workbench Task Management. Additional Cost factor Support for more effective Scheduling of Technicians. in-line editing of attachments.

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

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

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

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

redundant. choosing the Integrated SOA Gateway responsibility.” If your intended migration scope is large. Planning Your Oracle E-Business Suite Upgrade from Release 11i to Release 12.1. “migrate all open payables and receivables invoices. you can reduce the scope of your upgrade project. You can access the Integration Repository by logging into your test installation of Release 12. determine a data migration strategy for historical data.1 Page 12 . we reviewed and standardized our setups. responsibilities. It is part of the Oracle E-Business Suite Integrated SOA Gateway.1 system. you can reduce data migration volume and prevent data inconsistencies in your Release 12. alerts. As part of your upgrade planning. work with your user community to identify any setups. and clicking the Integration Repository link. By removing or disabling this obsolete functionality while you are still running on 11i. incomplete. Typically.Tip #7 – Avoid Upgrading Obsolete Functionality By removing or disabling obsolete functionality while you are still running on 11i. embedded in the applications technology layer.1. By cleansing historical data. Figure 1: Integration Repository It’s important to determine whether your historical data needs cleansing to eliminate any data that is incorrect. data that has undergone several prior upgrades or migrations can benefit from cleansing. Tip #8 – Determine Your Data Migration Strategy For a new E-Business Suite implementation or a reimplementation. The Oracle Integration Repository is a complete catalog of the many E-Business Suite public interfaces that you can use to migrate historical data. consider engaging an experienced migration consultant from Oracle Consulting or one of Oracle’s partners. you can reduce the scope of your upgrade project. out-of-date. for example. or incorrectly formatted. prior to Oracle’s own upgrade to Release 12. For example. programs or seed data that you no longer use. Your strategy should address the scope of data to migrate. and other data to reduce our testing and upgrade effort. and we eliminated obsolete reports.

and a customization developer.1 rollout to end users • • • • • If you decide to retain outside consultants to provide expertise that is lacking from your in-house team. and to participate in end-to-end testing and end user training. you could compare the outputs obtained from Release 12.1 changes in look and process flow.For audit purposes. and Oracle’s Advanced Customer Services team offer many Release 12. an applications server (middle tier) specialist. Typically. prefer consultants with prior Release 12. an operating system administrator.1 reports with the equivalent reports from your legacy system. For example. Technical team – one or more people who can function as a technical upgrade specialist.1 adopters have commented that strong support from business users has been critical to their project success. a performance specialist. Be sure to involve business users from the start of your project so that they are prepared for Release 12.1 Page 13 . Application specialists – technical specialists with functional business knowledge who work closely with business process owners.1.and implementation-related services. Tip #9 – Assemble a Project Team that Combines Technical and Functional Skill Sets Consider including the following people on your Release 12.1 project team: • • A dedicated project manager An executive steering committee – to provide project oversight and make critical decisions. and a DBA to apply patches. In addition. consider including a tax specialist who knows the tax policies in the regions where you do business. there is a significant pool of skilled and trained consultants. a database administrator. Oracle’s partners. Tip #10 – Involve Your Business Users at Every Project Phase Several Release 12 and 12.1 experience. establish a method for reconciling migrated data with legacy data. application specialists focus on particular product areas and perform the related functional setups. With the large number of customers either implementing or live on Releases 12 and 12. Testers – both technical and functional. a change management (patching) specialist.1 operations on data migrated from your legacy system. You will also need someone to log and track service requests (SRs). you should validate through testing that you can successfully perform Release 12. A training lead – to assist in the Release 12. citing the power of a “we’re-all-in-this-together” attitude. Business process owners – to analyze business process changes. Oracle Consulting. Identify the functional Planning Your Oracle E-Business Suite Upgrade from Release 11i to Release 12. For Financials upgrades.1 upgrade.

and the Invoice workbench is significantly reworked. to help with knowledge transfer to business users (see Tip #21. make sure you budget enough time for issue resolution. focusing on new and changed functionality. Be sure to specify expected test results to compare against your actual test results. Your testing should be guided by detailed test scripts that you prepare in advance. As for any new release. The project team can serve as a backup to the smaller in-house support team that normally handles end user queries. If you do not have test scripts from your original implementation. Well before your planned go-live date. For example. Perform multiple rounds of testing. Oracle Tutor and Oracle User Productivity Kit (UPK). Plan to reinforce user learning even after your production cutover with internal documentation and job aids. areas where users will see the biggest changes and concentrate your training efforts there. The number of test rounds and your acceptance criteria should be carefully considered at the outset of your project. you can create test scripts by documenting what you currently do in the system. types of testing. updating them to reflect new Release 12.1 functionality and process changes that you intend to implement. Test upgrades help to establish that the Planning Your Oracle E-Business Suite Upgrade from Release 11i to Release 12.1 Page 14 .Be sure to involve business users from the start of your project so that they are prepared for Release 12. and then reconsidered before and after each test round. plan to keep your project team in place at least through your first Financials close. the payments process uses a new Payments dashboard. and who will be involved.1 into production. ensure that you do full functional testing with business users. Your project team can closely monitor the health of your production system.1 changes in look and process flow. 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. you should formulate a testing strategy that details the number of test rounds. You can start with the test scripts used in your original implementation. or even to advancing to the next test round. with an overall goal of performing end-to-end testing of all business flows and scenarios. In addition to conference room pilot testing to validate setups. Agree in advance which types of issues should be considered as show-stoppers to putting Release 12. begin performing test upgrades against a copy (clone) of your existing system. in Oracle Payables. logging service requests as needed and notifying end users through broadcast emails of any significant issues. and ideally through your first quarterly close. The timeframe for your testing rounds should be clearly stated.1 go-live. Consider using Oracle’s process documentation and end user training tools.) Tip #11 – Keep Your Project Team in Place through Your First Financials Close After your Release 12.1 upgrade project.

The Oracle Applications Testing Suite (OATS) is composed of: • • • Oracle Load Testing for scalability. 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. You can use the same interface to run scripts.1 Page 15 . Also using the same interface. Using the OATS graphical scripting interface. we followed our standard testing flow. Also. 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 User Acceptance Test – where business users and the technical team do several weeks of full end-to-end testing. 12. upgrade will fit into your downtime window. We also added a one-off Technical Test environment where our technical staff did simulations to identify any performance regressions. Oracle uses a standard testing flow for all systems changes. Changes are collected into release bundles that are promoted through a series of test environments. parameterize script inputs. but increased the number of test rounds.1. including regression testing of key transaction flows. and 12. mimicking normal business operations. 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. add custom test cases to validate content. • • For the 11i to Release 12 upgrade. you can create automated load test scripts that allow Oracle Load Testing to simulate thousands of concurrent virtual users. performance. which is supported for use with Oracle E-Business Suite Releases 11i. allowing us to get very accurate timings for our production go-live. we did a full dress rehearsal of the upgrade transition in the Staging Test environment.and Oracle Forms-based screens. and allow for tuning of upgrade scripts as needed. as well as iterative runs of the upgrade process to tune performance and minimize the duration. and extend scripts programmatically in Java. test execution. Just a week before go-live. and load testing Oracle Functional Testing for automated functional and regression testing Oracle Test Manager for test process management. begin performing test upgrades against a copy (clone) of your existing system. Planning Your Oracle E-Business Suite Upgrade from Release 11i to Release 12. Automated Testing Tools You can create your own functional and load test suites using Oracle Application Testing Suite. your business users can record automated test scripts by stepping through Oracle E-Business Suite business transactions. be sure to track any upgrade impacts on your custom code.Well before your planned go-live date.

test that an invoice created in Release 11i can have a credit memo issued against it in Release 12.1 Page 16 .” If you registered for the recent Oracle OpenWorld. Or. in general.1 validation. created by Oracle’s Quality Assurance team. Oracle provides a “Test Starter Kit” for Release 12. upgrade smoothly. For example.1 test system to ensure that it adequately scales to the volume of transactions you anticipate in production. then void it in Release 12.1 with matching tax calculations. and encouraging your managers to respond to pending workflow notifications. This would validate that setup differences between Release 11i and 12.oracle.1.1 do not create inconsistencies in a business document as it completes its flow. 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. While your initial conference room pilot testing may validate setups based on sample or demonstration data.com/technology/products/oem/prod_focus/etest. Oracle’s latest standard testing tool. Additionally.In an upgrade context.) The Test Starter Kit includes a Starter Guide. Best Practices Guide. it’s critical that you do full. including worst-case peak loads. validate this with testing. end-to-end testing on the complete data set that you intend to run in production.oracle. In-progress workflow items should.1 on documents that were created in Release 11i.1.1 data validation is even tighter than in prior releases. Oracle plans to migrate the kit to OATS. and Installation instructions for using Hewlett Packard’s automated testing tools with Oracle E-Business Suite. Release 12. You can use the sample test scripts as a model for building your own unique portfolio of regression test suites. However. that run against an E-Business Suite Vision Demo database. Planning Your Oracle E-Business Suite Upgrade from Release 11i to Release 12.1.com/rednetwork. so you need to find whether there are any data conditions that would fail Release 12.1 that uses Hewlett Packard’s QuickTest Professional (QTP) testing tool (see My Oracle Support Knowledge Document 239746. You can read more about the OATS solution at: http://www. you can download the presentation and listen to the live recording on the Oracle OpenWorld OnDemand site at: http://www. Note that while Oracle’s Test Starter Kit is currently available for use with the QTP tool. Test performing operations in Release 12.1. you could use the OATS tool to load test your Release 12. especially where you have customized Release 11i preseeded workflow processes or activities. It also includes sample test scripts. 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. create a payment in Release 11i.html Oracle’s Applications Performance team offered specific advice on the best uses of OATS in a recent Oracle OpenWorld presentation: “Performance-Testing Oracle E-Business Suite: Tips and Tricks from Oracle Experts.

In addition.Oracle recommends that you test your month-end and quarter-end close and reconciliation with full data volumes. looking for stress points and unexpected behaviors.1 upgrade customers who are already live on Release 11g of the database.1 database workload. Even with all of this pre. 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 http://www.oracle. This allowed our technical staff to study the behavior of reports running with different parameter settings and to detect any performance regressions. In particular. we could control the resources they consumed and ensure that they did not have a detrimental impact on our business. Oracle’s DBAs studied the system. Oracle did a six-hour “User Participation Test” on a Release 12 environment configured with full production processing capacity. simulating heavy system usage. and that you resolve any exceptions. and that you resolve any exceptions. This paper offers advice on optimizing the 11g database upgrade process. Tip #14 – Plan to Do Load and Volume Testing Because new reports and business processes may be sensitive to your data distribution. 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. Oracle does automated load and volume testing. Planning Your Oracle E-Business Suite Upgrade from Release 11i to Release 12. you test your month-end and quarter-end close and reconciliation with full data volumes. as well as avoid potential performance issues. we do even more load and stress testing.pdf. and to ensure that your system has the expected performance characteristics. 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. That’s why. Oracle recommends that during user acceptance testing. Oracle did “batch load tests. highlighting 11g features that you can use to performance-test the Release 12. By isolating these jobs in special queues. While IT and business users bombarded the system with transactions and batch processes. Additionally. in addition to doing scripted regression testing. 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.” replaying concurrent requests pulled from production against a test copy of an upgraded database. Additional Performance Advice Oracle’s Applications Performance team recommends that Release 12. For a project as major as an E-Business Suite upgrade. once you go live.go-live testing. For our Release 12 upgrade. make sure you do load and volume testing.1 Page 17 .com/apps_benchmark/doc/11g-upgrade-performance-bestpractices. Even for regularly scheduled small-to-medium changes. consider simulating a month-end close a few days before your first actual month-end close.

Oracle collects only configuration information. where we maintain a secure and updated view of each host’s configuration. In particular.oracle. such as installed patches. and network configurations. deployment dates. as well as with ongoing operations once your upgrade is complete. patch advice.1 Page 18 . Having knowledge of both your configuration and your project allows Oracle’s support engineers to proactively suggest solutions and resolve issues. configuration files. and that you understand and leverage the information. The collected data is sent via secure HTTPS to My Oracle Support. Oracle recommends that you download and install the Oracle Configuration Manager (OCM). tools. tools. and services that are available to you there. and services that are available to you there. click the “Collector” link under the “More” tab on the My Oracle Support portal. 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.com. and that you understand and leverage the information. see the “My Oracle Support Health Checks Catalog” at My Oracle Support Knowledge Document 868955. and type. You can associate your configuration with information about your upgrade project that you upload via My Oracle Support. and system health checks that are specific to your computing environment. while being sensitive to critical events in your business that could affect your upgrade. you can upload the configuration of your Oracle computing environment. 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. versions.1. Using Oracle Configuration Manager.Tip #15 – Engage with Oracle Support Ensure that you have ready access to the My Oracle Support portal. Using the collected information. deployed components and applications. a support tool that allows Oracle to more proactively assist you with your upgrade. To view the full catalog of system health checks available via the Oracle Configuration Manager. My Oracle Support provides security and product alerts. Ensure that you have ready access to the My Oracle Support portal at https://support.

For more details on the Oracle Application Management Pack for Oracle E-Business Suite.) To learn more about working with Oracle Support to resolve issues. see My Oracle Support Knowledge Document 166650. Additionally. see My Oracle Support Knowledge Document 982302. These tools can proactively monitor your Oracle E-Business Suite test and production systems. Most customers find it helpful to maintain a prioritized issues list. The Solution Support Center performed a “Customer Success Assessment”. hardware. part of Oracle’s Advanced Customer Services team. Oracle recommends that you define an incident resolution flow for handling issues internally before you log them as service requests. and based on that recommended a catalog of services. sending informational alerts to warn your system administrators of any incidents. Be sure to designate who will troubleshoot and characterize issues.1. 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. In particular. You can also set up these tools to take corrective action on common issues and reduce the impact of any incidents. including customized training and knowledge transfer. “Working Effectively with Global Planning Your Oracle E-Business Suite Upgrade from Release 11i to Release 12. If you are using the Oracle Configuration Manager. see the Oracle E-Business Suite System Administrator's Guide Documentation Set.1 upgrade project. Tip #16 – Develop an Issue Resolution Strategy Develop an issue resolution strategy that spells out how you will address issues that arise during testing. one of our enterprise customers described engaging with Oracle’s Solution Support Center at the start of their Release 12.1 Page 19 . and who will log and track Service Requests (SRs).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. For more on the Oracle Applications Manager. or Oracle Applications Manager. and software – which resulted in a change to the customer’s planned CPU and memory configuration. tracking the details of all open and resolved issues encountered during their upgrade project. In addition. “Getting Started with Oracle Application Management Pack and Application Change Management Pack for Oracle E-Business Suite”. For example. In this case. you can automatically associate a configuration with your Service Request and save the effort of manually entering configuration data. We also recommend that you install tools such as Oracle Application Management Pack for Oracle E-Business Suite. the customer found it beneficial to engage an on-site “Solution Support Center Engineer” who worked alongside of the in-house project team. the Solution Support Center joined with the customer’s hardware vendor to evaluate the customer’s topology.

10 to 12 are highlighted in product-specific “Technical Overviews” that are part of the “Release 12 Transfer of Information Online Planning Your Oracle E-Business Suite Upgrade from Release 11i to Release 12. 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. It may be possible to defer the implementation of some customizations until after the initial upgrade project. You can also use the diagnostics after you go live to help troubleshoot any issues that may arise. review country localization features. 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. Inventory your customizations and determine which functions could be replaced by standard product in Release 12. In particular.1 for advice on “Escalating Service Requests with Oracle Support Services”. eliminating the need for forward-porting. Oracle E-Business Suite Diagnostics are automatically installed with Release 12.Customer Support. The diagnostic tests do not alter your setup or transactional data in any way. that may simplify or replace your customizations (See My Oracle Support Knowledge Document 429042. See My Oracle Support Knowledge Document 342459. the backward-compatible views RA_CUSTOMERS and RA_ADDRESSES are no longer available. resolve issues on your own. validate with your business users which customizations are most critical to them so that you can prioritize your upgrade effort. note that starting with Release 12. For international deployments. Database changes from 11i.1 Page 20 . Oracle E-Business Suite Diagnostics are easy to use. A major 11i customer with several thousand customizations observed that at least half of those were already built into Release 12. or obtain diagnostic output that you can upload with a Service Request to speed Oracle’s resolution of your issue.1. designed for both functional and technical users.” Also see My Oracle Support Knowledge Document 199389.) For any customizations that remain. Assessing the Impact of Database Changes to Your Custom Code Validate with your business users which customizations are most critical to them so that you can prioritize your upgrade effort. and the latest versions of the toolset and tests are available through a standard patch. You can use these diagnostics after each test upgrade to identify and troubleshoot any issues. You should review the impact of changes to database objects on your custom code. They enable you to avoid issues. 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.1. new starting with Release 12.1.1. Once you are satisfied with the outcome of your test upgrades.1 for more information.1. so you should change any custom code that references them to reference the relevant Trading Community Architecture (TCA) tables instead.

Release 12. as well as the data models for prior releases. and Integration) framework review. “Customization Standards” in the Oracle E-Business Suite Developer’s Guide.Training” (see My Oracle Support Knowledge Document 988725.) Database changes from Release 12 to 12. Release 12.1. You can access the eTRM at https://etrm. or to defer migration until your Release 12.com. Oracle Application Framework pages.1 upgrade downtime. This should be done to assist in properly planning your upgrade program. Localization.1 are listed in product-specific Release Notes that are linked from “Oracle Applications Documentation Resources.1. or from My Oracle Support Knowledge Document 150230. For more information. See “Preparing Custom Development for the Next Oracle Applications E-Business Suite Release” (My Oracle Support Knowledge Document 374398.) The Electronic Technical Reference Manual (eTRM) documents the full data model for Release 12.1. and reports. Another resource that can help you understand database changes is the Electronic Technical Reference Manual (eTRM). which enables access to data in multiple organizations from a single responsibility.1 after you have regenerated them using the latest certified version of the Oracle Forms Migration Assistant. you should be able to run your custom forms on Release 12.1) for a discussion of migration alternatives for the deprecated technologies. see Chapter 28. In general. as well as the data models for prior releases.1” (see My Oracle Support Knowledge Document 790942.1. Note that starting with Release 12.1 Page 21 . Extension.1. Adapting Your Custom Code to Architecture and Technology Changes Release 12 introduced support for Multiple Organizations Access Control (MOAC). Planning Your Oracle E-Business Suite Upgrade from Release 11i to Release 12.1.1 to learn how to MOAC-enable your custom forms.oracle. which documents the full data model for Release 12. consider whether to migrate to newer technologies while you are still running your current E-Business Suite release. Modification. You may wish to consider engaging Oracle Consulting or an Oracle partner to execute a detailed CEMLI (Customization. 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 If you did custom development using any of these deprecated technologies. concurrent programs. See My Oracle Support Knowledge Document 420787.

occurred. responsibilities. as well.10 for high-fidelity formatting of many external documents. 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. Custom reports based on Pasta are not supported starting with Release 12. and so on). With Oracle Applications Access Controls Governor. or Adobe Acrobat. formerly known as XML Publisher. from “roles” and “responsibilities” down to the “functions” (secured operations) in the Oracle EBusiness Suite. If you move your custom reports to BI Publisher before upgrading to Release 12. Microsoft Excel. End users can easily design report layouts using familiar desktop tools. or file data sources. such as Microsoft Word. in fact. sub-menus.1 Page 22 . many more standard reports used BI Publisher. is an enterprise reporting solution for authoring. and with Release 12. You should reexamine user roles and responsibilities due to business process changes introduced starting with Release 12.Tip #19 – Consider Migrating Your Reports to Business Intelligence Publisher Oracle Business Intelligence Publisher (Oracle BI Publisher). managing and delivering all types of highly-formatted documents. Included with Applications Access Controls Governor is the ability to ask “what if?” or to simulate changes to the authorization model (menus.1.1. With Release 12. HTTP feeds. you can evaluate all business transactions to see if any SOD violations have. Planning Your Oracle E-Business Suite Upgrade from Release 11i to Release 12.1 nearly all reports use it. but your formatting will remain valid for Release 12. For BI Publisher-based reports. and to include approval steps before assigning access rights that represent an SOD risk. web services. responsibilities. menus. and should be converted to BI Publisher. BI Publisher was used in Release 11i. For example. you can designate any combination of incompatible access points (roles. or functions. packaged applications. BI Publisher can query or accept data from practically any data source – databases. We also recommend that you convert any custom reports based on mod_plsql to BI Publisher. with Enterprise Transaction Controls Governor. Tip #20 – 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. Starting with Release 12. In addition. you may need to adjust the queries you use to produce the report output.) The application can then report occurrences of users with incompatible access points so that managers can modify the privileges and tasks assigned to them. the Oracle Applications Access Controls Governor provides the ability to analyze the entire access model. an XML data extract is provided along with a default layout (template) that you can easily modify. Consider converting your custom Oracle Reports reports to BI Publisher.

1 Page 23 .html. you can create training on how to use Release 12. and procedures that your Release 12.1 to accomplish your business processes. Using these as a starting point. Oracle User Productivity Kit (UPK) is a powerful tool for training end users on how to use the system to accomplish your business processes. 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 applications will support.1 changes before you provide them with a live Release 12. With Tutor. you can also generate role-specific end user desk manuals and a variety of job aids. creating interactive UI simulations. 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. allowing users to learn about your enterprise’s policies and procedures by clicking the Help button on any screen. and facilitates the training of new users at any point after the initial rollout. Oracle offers over 2300 pre-recorded UPK topics for Release 12. ensuring that users always have access to the latest information. Oracle Tutor is an easy-to-use Microsoft Word-based tool for documenting the business processes. More information about Oracle Tutor and UPK is available at http://www.1 environment.1 online help system. These tools support efficient capture of knowledge during your upgrade project.Tip #21 – 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. UPK allows you to train current users on Release 12.com/applications/tutor/tutor-upk-index. The availability of these simulations may help end users become familiar with Release 12. You can also deploy Tutor and UPK in the Release 12. and just in time maintenance of knowledge after your project is over. policies.1.oracle.1 implementation.1 products. You can start with the model business processes delivered with Oracle Tutor and customize them to reflect your Release 12.

For those inclined to self-study.1.1 Documentation Library.1 Info Center You can also take advantage of the Release 12. See http://education. My Oracle Support Knowledge Document 806593.1 Info Center”.1.oracle. Transfer of Information Online Training. The Documentation Library contains Adobe Acrobat versions of all the E-Business Suite guides. available online at http://www.1 Page 24 . For international deployments. Release Content Documents. The Release 12. Planning Your Oracle E-Business Suite Upgrade from Release 11i to Release 12.oracle. Oracle provides a wealth of information resources to help you come up to speed on Release 12.Tip #22 – Acquire Release 12. a good place to start is the “Oracle E-Business Suite Release 12. and administration guides. and more. including suite-level installation.1 to access user’s guides for country localizations. Figure 4: Oracle E-Business Suite 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. see My Oracle Support Knowledge Document 429042.com for a catalog of available offerings.com/technology/documentation/index.1. Release Value Propositions. as well as product-specific implementation and user’s guides.html.1 Info Center highlights Announcements.1 Knowledge Oracle provides a wealth of information resources to help you come up to speed on Release 12. Customer Advisor Webcasts. upgrade.

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

and explains the concepts underlying the setup and use of: • • • • • • Organization Models Reporting Accounting Worldwide Operations Governance. Release 11i to Release 12.1.1. Risk Management.1”. the guide contains two main sections: Planning Your Oracle E-Business Suite Upgrade from Release 11i to Release 12.12.1 is a “must read” for anyone deploying the Release 12.1 Financials products. To present a complete picture of the upgrade process and resulting functional impacts.1. It highlights key Financials architectural and process changes since Release 11i. and Compliance Business Analytics and Corporate Performance Management Tip #23 – 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. Release 12.1 Page 26 . at My Oracle Support Knowledge Document 461705. Financials Concepts The Oracle Financials Concepts Guide. The “Oracle E-Business Suite Upgrade Center”. Figure 6: Oracle E-Business Suite Upgrade Center The primary source for upgrade information is the Oracle E-Business Suite Upgrade Guide. is a repository for documentation and advice on each phase of the upgrade life cycle. The product-level Release Notes also highlight “Known Issues” that you should be aware of as you plan your upgrade.

1. or advice that will help you during your production upgrade. describe functional impacts on user interfaces and processes. It explains how 11i Financials setup and transaction data are upgraded. graphical user interface for performing upgrade tasks.1 Page 27 . configuration changes. targeted to application specialists. describe technical tasks to perform before. functional pre-upgrade tasks for reducing downtime.) Tip #24 – Consider Using the Maintenance Wizard The Maintenance Wizard is a free tool (available via My Oracle Support Knowledge Document 215527. You can use Oracle’s Maintenance Wizard to record the outcome of your various test upgrades. lessons learned. It also indicates critical patches that your system requires. 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 advice on the Financials upgrade is provided in the “R12 Upgrade Considerations by Product: Financials”.• The initial chapters.1) that provides a step-by-step. annotating individual upgrade steps with hints. It consolidates instructions from the upgrade guide with other relevant documents to present a complete picture of the upgrade process. and maintains a log with status information for all executed tasks. and post-upgrade tasks for verifying that transactional data upgraded correctly. and other upgrade considerations that your Financials applications specialists should understand (see My Oracle Support Knowledge Document 889733. You can even create Planning Your Oracle E-Business Suite Upgrade from Release 11i to Release 12. during. • 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. The appendices. It can automatically execute upgrade tasks for you. which details process changes. targeted to database administrators (DBAs). The Maintenance Wizard can help you reduce upgrade tasks by filtering out those that do not apply to you. and after the upgrade.

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

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

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

1 Page 31 . Oracle releases a Cumulative Upgrade Patch (CUP) that contains critical error corrections and performance improvements to the EBusiness Suite upgrade process. see the “Oracle Applications Release Notes. 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.1) and apply it to your Applications Code Tree (APPL_TOP) prior to running the Release 12.oracle.1.1”. Tip #26 – Identify Required and Recommended Pre.1 upgrade is complete. Plan to merge the appropriate patches and apply them when your Release 12. Plan to apply these patches during your test upgrades so that you can assess their impact and identify any additional fixes you might need.com/rednetwork.and Post-Upgrade Patches As you prepare for your upgrade. pay attention to any Generic Data Fix (GDF) patches designated as “Pre-Upgrade”. Release 12. Make sure you identify the latest Cumulative Upgrade Patch (see the “Oracle Applications Release Notes. My Oracle Support Knowledge Document 798258. introduced by known bugs. Release 11i to 12.1 – you need not apply these fixes to environments that have already been upgraded to Release 12. it is highly recommended to review the list of Generic Data Fix patches described in My Oracle Support Knowledge Document 874903. The Cumulative Upgrade Patch is targeted specifically to customers who have not yet upgraded their environment from 11i to Release 12.1.1. As needed. including information about high-priority patches. Release 12.OpenWorld conference.1. These GDF patches. Planning Your Oracle E-Business Suite Upgrade from Release 11i to Release 12. Below are some key resources to help you identify patches you should include in your pre. Some patches may need to be applied PRIOR to the upgrade to have the desired impact.1. clean up data issues. make sure you maintain an up-to-date list of required and recommended pre.1”.1 Upgrade Driver. that commonly cause issues in Release 12+ Financials. “What is a Generic Datafix Patch (GDF) and what GDFs are available for Payables?” In particular.1. for latest release information.and post-upgrade patches applicable to your environment and licensed products. Also.1. so pay close attention to the patch instructions. which should be run on 11i prior to upgrading to Release 12 or 12. you can download these presentations and listen to live recordings of them at: http://www.and post-upgrade patch list: • Review the required pre-upgrade patches identified in Appendix I of the Oracle E-Business Suite Upgrade Guide. For Financials customers. • • • Contact your Oracle Support representative for any additional patches you may need beyond those you have already identified. My Oracle Support Knowledge Document 798258.1.

After your upgrade is complete. Tip #28 – After Your Go-Live. diagnostics.1. “Best Practices for Securing Oracle EBusiness Suite Release 12”.1. we also recommend that you stay current on the latest AD and ATG Family RUPs. and testing fixes for what ultimately are found to be known issues. To ensure that you have up-to-date fixes and performance improvements for the patching infrastructure and for the application technology and management products. Stay Current with Latest Information After your go-live. For example. For more information about CPUs and advice on keeping your system secure. reporting. Release Update Packs. qualifying. It is particularly important for Financials customers to stay current with latest code. application server. continue to consult My Oracle Support for the latest information on the Oracle E-Business Suite. (See My Oracle Support Knowledge Document 806593. and so on.x Release Update Packs (RUPs).1. and you are live on Release 12. Oracle consolidates security patches for database. Tip #29 – After Your Go-Live. 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. Oracle maintains a document highlighting Release 12. Stay Current with Latest Code After your upgrade is complete.1 Financials critical patches at My Oracle Support Knowledge Document 954704.1 Info Center on My Oracle Support is kept up-to-date with the latest information on certifications. In addition. The Release 12.1) Planning Your Oracle E-Business Suite Upgrade from Release 11i to Release 12.1.1. release notes. and Oracle E-Business Suite code in Critical Patch Updates (CPUs) that are released quarterly. 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. Oracle strongly recommends that you apply the latest available CPU patches before you upgrade and on an ongoing basis. customers should consider whether it is more efficient to proactively apply RUPs and critical patches at their earliest maintenance opportunity.1 Page 32 .Tip #27 – 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. stay current with the latest available code. see My Oracle Support Knowledge Document 403537. Since the alternative may be to cycle through the timeconsuming process of identifying. stay current with the latest available code. which consolidate the latest maintenance fixes for the release. documentation resources. and you are live on Release 12.

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

x Release Update Packs” “Oracle E-Business Suite Release 12.1 166650.1 150230.1 342459.1 404152.1 461705.1 868955.1 954704.1 Release Content Documents” “Release Content Documents and Feature Summary Matrices” “Oracle E-Business Suite Release 12.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 Info Center” “Oracle E-Business Suite Release 12.1 420787. 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 982302.1 239746.1 889733.1 988725.1 248857.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. Release 12” “R12: Upgrade vs.1 Release Value Propositions” “Release Content Documents for E-Business Suite Release 12 and 12.1 780989.1 210193.1 163400.1.1 561580. Release 12.1 874903.1 Oracle Financials Critical Patches” Planning Your Oracle E-Business Suite Upgrade from Release 11i to Release 12.1 403537.1 807319.1 199389.1 804373.1 399362.My Oracle Support Knowledge Document References ID 580299.1 790942.1 215527.1 374398.0.1 Document “Best Practices for Adopting Oracle E-Business Suite.1 761570.1 Transfer of Information (TOI) Online Training” “Oracle E-Business Suite Upgrade Center” “Upgrade Considerations by Product: Financials” “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 429042.1 806593.1 Page 34 .

0 Change Reference First published version Planning Your Oracle E-Business Suite Upgrade from Release 11i to Release 12.1 Page 35 .Change Record Date 4-March2010 Version 1.

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

Sign up to vote on this title
UsefulNot useful

Master Your Semester with Scribd & The New York Times

Special offer: Get 4 months of Scribd and The New York Times for just $1.87 per week!

Master Your Semester with a Special Offer from Scribd & The New York Times