Delivering Oracle Success

R12 Upgrade versus Re-implementation and Impact Analysis

John Malone RMOUG QEW August 19, 2011

About DBAK
Oracle solution provider Co-founded in 2005 Based in Englewood, CO 2008 Emerging Business of the Year South Metro Denver Chamber of Commerce More than 140 implementations, upgrades, conversions, and support projects for 90+ clients Average 15 years of Oracle expertise Oracle Gold Partner OEM Specialized

DBAK2011

Agenda
Upgrade vs. Re-implementation Impact Analysis Case Studies Questions

DBAK2011

Upgrade vs. Reimplementation

Data quality Changes to Key Flexfields Multiple Oracle EBS environments Significant changes to business structures (acquisitions, mergers, re-organizations) since initial implementation Number and complexity of customizations Changes to business process requirements Oracle EBS version

DBAK2011

Upgrade vs. Reimplementation

Upgrade
1
Does your Application configuration still meet your business requirements? (considering growth,expansion, acquisition)

Re - Implement
2 3 4 5 6 7 8 9 10

They meet our requirements

A change is needed

Do you wish to make changes to configurations that cannot be easily modified (flexfield structures, Customizations, Calendar) Has your business structure changed significantly since your implementation ( more/less business units/orgs, currencies, shared services) How significantly have you integrated with 3rd party applications that could be replaced with new Oracle Applications modules, features or functionality?

Our existing configuration is OK

We require changes

Our structure is correct for our needs

Our structure needs to change

Not Much

Significantly

DBAK2011

R12 Methodology

Phase I
R12 Assessment and Impact Analysis
Test Iteration 1 Test Iteration 2

Phase II

Test Iteration 3

- New Features Prioritization - Technical Architecture Analysis - Application Architecture Analysis - Assessment Review - Project Scope - Project Schedule

UAT

Training

Post-Production Support

Planning and Execution Milestones

R12 Go Live

DBAK2011

Impact Analysis
New Features Prioritization Technical Architecture Analysis Application Architecture Analysis Assessment Review Project Scope Project Schedule

DBAK2011

Impact Analysis
New Features Prioritization
New/Changed R12 Features and Functionality Review existing (standard and custom) functionality within 11i and look for opportunities to leverage new features within R12
Primary goals are to: Remove customizations where possible Identify opportunities to leverage new R12 functionality

Analyze impacts to current business processes and determine the approach going forward with R12 Determine which new features will be included in the R12 upgrade and which features could be included in post upgrade projects Reference Materials
Release Content Documents (RCD) Release Value Proposition (RVP) documents Product specific upgrade guides (e.g. Financials, Procurement) Oracle E-Business Suite Release 12.x Information Center

DBAK2011

Impact Analysis
Technical Architecture Analysis
Technical Architecture Analyze impacts to the infrastructure between 11i and R12
Servers Operating System version Database version Application Server version Disk Space (Storage) requirements Reporting Workstations (e.g. browsers, memory, CPU) Third party software impacts

Reference Materials
Upgrade Guide for 11i to R12 R12 Infrastructure - Differences between 11i and 12 Oracle Applications Release 12 Upgrade Sizing and Best Practices

DBAK2011

Impact Analysis
Application Architecture Analysis
Application Architecture and Extensions/Customizations Interfaces with 3rd party applications Workflow Reporting tools (e.g. BI Publisher, e-Text) New application modules Impact to existing extensions/customizations Reference Materials
Upgrade Guide for 11i to R12 11.5.10 to 12.x EBS Object Changes

DBAK2011

10

Impact Analysis
Assessment Review
Review Impact Analysis results

Project Scope
Develop Project Scope Determine Upgrade or Reimplementation Approach Consider:
Technical Architecture Impact Applications Architecture and Extensions/Customizations Impact New/Changed Features Prioritization Functional and Business Process Impact Assessment

DBAK2011

11

Impact Analysis
Project Schedule
Develop Project Schedule based on Impact Assessment results Including timeline, resources, and cost Leverage experienced R12 resources to supplement internal team members Project schedule/plan Reference Materials
E-Business Suite Technical Guided Upgrade Path from 11.5.10.2 to 12.1.3 Planning Your Oracle E-Business Suite Upgrade from Release 11i to Release 12.1

Next Steps
Organize and launch Phase II (Upgrade) Determine if you want to use Maintenance Wizard or other tools (MS-Project, Excel) to track and manage upgrade tasks Start Iteration 1 test and customizations migration
DBAK2011 12

Case Study R12 Upgrade for an Energy Company

Company Description
Leading provider in the mid-stream services for the natural gas industry. Headquartered in Denver, the company is engaged in the gathering, processing and transportation of natural gas; the transportation, fractionation, storage and marketing of NGLs; and the gathering and transportation of crude oil.

Scope
Develop the methodology and tools for completing the R12 upgrade project. Conduct the upgrade assessments to define the project scope, resource requirements, and project schedule. Manage the upgrade project tasks, resources, issues, and risks

Management Challenge
The company implemented Oracle Financials, Projects, iExpense, and Logical Apps in the 2007-2008. They have approximately 200 core application users and all employees are iExpense users. They have a moderate number of extensions/ customizations and several mission critical interfaces between Oracle EBS and their revenue/operations applications. The project objective was to migrate the Oracle applications from 11.5.10 to R12 and also upgrade the database from 10g to 11g. The upgrade would be installed on a new server and include an upgrade of the operating system. High level planning had been completed but the approach for executing the project had not been determined.

Results
Completed the impact analysis for new/changed features, customizations, application architecture and infrastructure Created a detail project schedule and assigned resources to the various work streams. Utilized extract out of Maintenance Wizard to create the initial list of upgrade tasks Completed three upgrade test cycles (iterations) and User Acceptance testing Created end user training materials and conducted training courses Executed the production cutover plan to complete the upgrade over a weekend to minimize impact on daily business operations. Project was completed on-time (6 months) and under budget. There were very few post-production issues.

DBAK2011

13

13

Case Study R12 Implementation for Services Company

Company Description
Leading provider of software and services that help the worlds best companies manage their extended workforce and procured services. Global provider of contingent labor.

Scope - Re-implement Oracle E-Business Suite (R12.1.3)

Impact Assessment Review existing 11i functionality New R12 functionality
Prioritize new features

Management Challenge
The companies Oracle E-Business suite had not been upgraded in many years (version 11.5.4), however business changes required changes in how the company used Oracle. Due to increasing volume and a need for additional flexibility, a custom front office application was developed to replace Oracle Projects. The legacy Projects data still exists and there is a large quantity of data that is no longer used. Implement new module: Fixed Assets. Consolidation of many operating units The company wanted to expand use Oracle functionality to enable business processes The company wanted to take advantage of new features within Oracle R12 Enable existing functionality not being used to automate business processes Key implementation versus upgrade decision factors Limited Down-time available for cutover 11.5.4 version expanded the tasks required for upgrade The company is switching to a new hardware platform

Leverage setups from existing 11i system Re-implement Oracle R12 for existing modules Migrate required customizations and interfaces to R12 Limited Data Conversion: GL Balances and current year transactions AR/AP Customers/Suppliers AR/AP Open invoices Fixed Assets load existing into R12 System Setup / System Validation / Integration Testing Migration to Production

Expected Results
Expand usage of current Oracle functionality to enable business processes Ability to use new R12 functionality Reduction of customizations Clean-up of old/non-used data Ability to quickly cut-over to the new system Deployment on new hardware platform Consolidated operating units

DBAK2011

14

14

Questions

DBAK2011

15

Contact
John Malone 720.475-8600 jmalone@dbaknow.com Presentation available at: www.dbaknow.com/downloads

www.dbaknow.com

DBAK2011

16