8/22/2019 R12 Upgrade Versus Reimplementation RMOUG QEW Aug 19 2011
1/16
Delivering Oracle Success
R12 Upgrade versus
Re-implementation andImpact Analysis
John Malone
RMOUG QEWAugust 19, 2011
8/22/2019 R12 Upgrade Versus Reimplementation RMOUG QEW Aug 19 2011
2/16
DBAK2011 2
About DBAK
Oracle solution provider
Co-founded in 2005Based in Englewood, CO
2008 Emerging Business of the Year SouthMetro 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
8/22/2019 R12 Upgrade Versus Reimplementation RMOUG QEW Aug 19 2011
3/16
DBAK2011 3
Agenda
Upgrade vs. Re-implementation
Impact AnalysisCase Studies
Questions
8/22/2019 R12 Upgrade Versus Reimplementation RMOUG QEW Aug 19 2011
4/16
DBAK2011 4
Upgrade vs. Reimplementation
Data quality
Changes to Key FlexfieldsMultiple Oracle EBS environments
Significant changes to business structures(acquisitions, mergers, re-organizations) sinceinitial implementation
Number and complexity of customizations
Changes to business process requirements
Oracle EBS version
8/22/2019 R12 Upgrade Versus Reimplementation RMOUG QEW Aug 19 2011
5/16
Upgrade vs. Reimplementation
DBAK2011 5
Has your business structure changed
significantly since your implementation
( more/less business units/orgs,
currencies, shared services)
Do you wish to make changes to
configurations that cannot be easilymodified (flexfield structures, Customizations,
Calendar)
Does your Application configuration still meet
your business requirements? (considering
growth,expansion, acquisition)
How significantly have you integrated
with 3rd party applications that could be
replaced with new Oracle Applications
modules, features or functionality?
They meet our
requirementsA change is needed
1 2 3 4 5 6 7 8 9 10
Not Much
Our structure is correct
for our needs
Our existing
configuration is OK
We require
changes
Our structure
needs to change
Significantly
Upgrade Re - Implement
8/22/2019 R12 Upgrade Versus Reimplementation RMOUG QEW Aug 19 2011
6/16
DBAK2011 6
R12 Methodology
Training
Test
Iteration 1
Post-Production Support
Test
Iteration 2
Test
Iteration 3
Phase IIPhase I
- New Features Prioritization- Technical Architecture Analysis- Application Architecture Analysis- Assessment Review- Project Scope- Project Schedule
R12 Assessment and Impact Analysis
UAT
Planning and Execution Milestones R12 Go Live
8/22/2019 R12 Upgrade Versus Reimplementation RMOUG QEW Aug 19 2011
7/16
DBAK2011 7
Impact Analysis
New Features Prioritization
Technical Architecture AnalysisApplication Architecture Analysis
Assessment Review
Project ScopeProject Schedule
8/22/2019 R12 Upgrade Versus Reimplementation RMOUG QEW Aug 19 2011
8/16
DBAK2011 8
Impact Analysis
New Features PrioritizationNew/Changed R12 Features and Functionality
Review existing (standard and custom) functionality within 11i andlook 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 theapproach 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
8/22/2019 R12 Upgrade Versus Reimplementation RMOUG QEW Aug 19 2011
9/16
DBAK2011 9
Impact Analysis
Technical Architecture AnalysisTechnical 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
8/22/2019 R12 Upgrade Versus Reimplementation RMOUG QEW Aug 19 2011
10/16
DBAK2011 10
Impact Analysis
Application Architecture AnalysisApplication 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
8/22/2019 R12 Upgrade Versus Reimplementation RMOUG QEW Aug 19 2011
11/16
DBAK2011 11
Impact Analysis
Assessment ReviewReview Impact Analysis results
Project ScopeDevelop 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
8/22/2019 R12 Upgrade Versus Reimplementation RMOUG QEW Aug 19 2011
12/16
DBAK2011 12
Impact Analysis
Project ScheduleDevelop 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 to12.1.3
Planning Your Oracle E-Business Suite Upgrade from Release 11i toRelease 12.1
Next StepsOrganize 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
8/22/2019 R12 Upgrade Versus Reimplementation RMOUG QEW Aug 19 2011
13/16
Case Study R12 Upgrade for an Energy Company
Company Description
Leading provider in the mid-stream services for thenatural gas industry. Headquartered in Denver, thecompany is engaged in the gathering, processing andtransportation of natural gas; the transportation,fractionation, storage and marketing of NGLs; and thegathering and transportation of crude oil.
Management Challenge
The company implemented Oracle Financials, Projects,iExpense, and Logical Apps in the 2007-2008. They haveapproximately 200 core application users and all
employees are iExpense users. They have a moderatenumber of extensions/ customizations and severalmission critical interfaces between Oracle EBS and theirrevenue/operations applications.
The project objective was to migrate the Oracleapplications from 11.5.10 to R12 and also upgrade thedatabase from 10g to 11g. The upgrade would beinstalled on a new server and include an upgrade of theoperating system.
High level planning had been completed but the approachfor executing the project had not been determined.
Scope
Develop the methodology and tools for completing the R12upgrade project.
Conduct the upgrade assessments to define the projectscope, resource requirements, and project schedule.
Manage the upgrade project tasks, resources, issues, andrisks
Results
Completed the impact analysis for new/changed features,customizations, application architecture and infrastructure
Created a detail project schedule and assigned resourcesto the various work streams.
Utilized extract out of Maintenance Wizard to create theinitial list of upgrade tasks
Completed three upgrade test cycles (iterations) and UserAcceptance testing
Created end user training materials and conducted trainingcourses
Executed the production cutover plan to complete theupgrade over a weekend to minimize impact on dailybusiness operations.
Project was completed on-time (6 months) and underbudget. There were very few post-production issues.
13 DBAK2011 13
8/22/2019 R12 Upgrade Versus Reimplementation RMOUG QEW Aug 19 2011
14/16
Case Study R12 Implementation for Services Company
Company Description
Leading provider of software and services that help theworlds best companies manage their extended workforceand procured services.
Global provider of contingent labor.
Management Challenge
The companies Oracle E-Business suite had not beenupgraded in many years (version 11.5.4), howeverbusiness changes required changes in how the companyused Oracle.
Due to increasing volume and a need for additional
flexibility, a custom front office application wasdeveloped to replace Oracle Projects. The legacyProjects data still exists and there is a large quantityof data that is no longer used.
Implement new module: Fixed Assets.
Consolidation of many operating units
The company wanted to expand use Oracle functionalityto 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 forupgrade
The company is switching to a new hardwareplatform
Scope - Re-implement Oracle E-Business Suite (R12.1.3)
Impact Assessment
Review existing 11i functionality New R12 functionality
Prioritize new features
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 enablebusiness 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
14 DBAK2011 14
8/22/2019 R12 Upgrade Versus Reimplementation RMOUG QEW Aug 19 2011
15/16
DBAK2011 15
Questions
8/22/2019 R12 Upgrade Versus Reimplementation RMOUG QEW Aug 19 2011
16/16
DBAK2011 16
Contact
J ohn Malone
720.475-8600
Presentation available at:www.dbaknow.com/downloads
www.dbaknow.com