Upgrade Planning

•Clear definition of Project Scope•Upgrade Objectives•New Features and functionalities to be implemented•Potential Changes to business processes•Impact on current customizations or interfaces --opportunity to remove customizations and replace with R12 offered functionality --evaluation of CEMLI’s that may require updates due to upgrade-All interfaces, form customizations, dff and customized reports will require extensive testing to ensure they have not been affected by changes in tables or API’s in the upgraded software. --Custom responsibilites and menus must be reviewed and updated•System downtime•Governance Structure•Communication with key stake holders•Training Plan

New Release Setups

•Accounting entities such as taxes, banks and suppliers have been moved to common implementation starting R12•With R12 need to understand new features such as Trading community architecture for supplier data, payments and E-Btax.

•What happens to my tax codes•How are new payables invoice lines derived?•How are legal entities derieved•How does Accounting setup manager get setup•How will my bank accounts be migrated?•How are supplier and supplier sites moved in to TCA model?•How have profile options changed?

Upgrade from Release 11.5.x to Release R12

• Upgrade to 11.10.2•Upgrade database to 10t•Apply pre-requisites for release R12•Apply R12 upgrade driver•Apply R12 patches•Upgrade database to 11g

•Upgrade best practices:1) Determine Upgrade path --determine if you can upgrade directly to R12 or first upgrade to a previous release before

upgrading to R12 --determine complexity of upgrade effort based on modules implemented, # of customizations, #

interfaces and total # of scripts2) Treat upgrade activity as a formal Company project Planning and project management rigor. Structured approach for managing the tasks, resolving issues and measuring progress is very critical. Equally important is clearly defined and documented scope

Experience has demonstrated that:--CEMLI, third party products, Hardware, Softeare releases, patches, os, db, oebs application

Upgrade from Release 11.5.x to Release R12

Clear issue definition Strong project management and executive ownership are critical factors to a well performing project effort.3) Plan for upgrade tuning: Performance tuning of new system is critical. Tuning your production upgrade script can significantly reduce

downtime during final stages of your upgrade. Tune conversion codes4) Escalate and resolve problems as appropriate Governance structure work closely with Oracle to resolve SR5) Prepare and engage the entire affected organization for work ahead and changes they will experience in their job.6) Secure agreement on all business blackout periods for system changes7) Ensure quality of data: Ensure data is accurate and complete standard practices for handling duplicate records, verify data integrity, and ensuring overall health of your data. Time before an upgrade is an important time to review what practices are in place or need to be created to ensure what data is relevant

and reliable8) Complete a detailed review of your reporting strategy prior to upgrade ex web v/s paper, reduction and consolidation, minimize report

maintenance9) Inventory your system: All configuration elelments of your system should be inventories and they current configurations items shuld be copied and stored.

Inventory should include --CEMLI, third party products, Hardware, Softeare releases, patches, os, db, ebs application8) Prepare a go live checklist robust checklist to assess go/no go decision9) Understand and mitigate project lists --resource contention --other projects going live at the same time and have dependency –need well defined plans around them --look for key points of failure (10) Get code current in the new environment before you invest in testing, configuration and validation associated with go live