O2 WorksO2 Works Putting Oracle to Work

Oracle E-Business Specialists

R12 Upgrade Lessons learned and what you need to R12 Upgrade Lessons learned and what you need to know to succeedknow to succeedo to succeedo to succeed

NorCal OAUG2014 Training Day2014 Training Day

August 26, 2014

Overview / Agenda

Introductions and Audience survey Upgrade vs re implement Upgrade vs. re-implement Why upgrade? Upgrade types R12 Experience / Why it is different Upgrade process and planning R12.2 – what does it mean to youy Keys to Success – Process Components Resources Methodology Methodology Other Information sources

2

R12 Upgrade Introduction

Art Dowd Consulting Director O2Works Art Dowd, Consulting Director, O2Works Former VP of IT for Hospitality Company Extensive business backgroundg Implemented / Upgraded Oracle eBus Suite 12 years with Oracle Applications Experience with Oracle Consulting and two well

regarded Oracle Applications consulting firms

3

Audience survey

Role Apps Release level

Technical – DBA

Technical – Developer

Technical – DBA

Technical – Developer

10.7 10.7

11.0.311.0.3

10.7 10.7

11.0.311.0.3Technical Developer

Project Manager

Technical Developer

Project Manager

11.0.311.0.3

11.5.1 11.5.1 11.5.911.5.9

11.0.311.0.3

11.5.1 11.5.1 11.5.911.5.9

Business Process Owner

Super user

Business Process Owner

Super user

11.5.1011.5.10

12.0 12.0

11.5.1011.5.10

12.0 12.0

End user End user 12.112.1 12.112.1

4

Upgrade vs. re-implement Back in the dark ages (pre 11i) there were technical

concerns about upgrading (tech. stack and apps.) andconcerns about upgrading (tech. stack and apps.) and people opted to re-implement

Due to the significant changes to the apps in going to R12 the question is surfacing again

Recommendation = upgrade… unless there is a i ifi i h i lsignificant reason causing you to have to re-implement Upgrade process, technology, tools, and scripts are

significant improvedsignificant improved Re-implementation = much more extensive project Data conversion / testing will be an issue

5

Re-implementation considerationsYou might need to re-implement if:

Y h h d b i b i / i ti You have changed your basic business / organization structure and your application configuration does not still fit your businessy

Single instance consolidation Your original implementation was really screwed up and it g p y p

is basically unusable You have tons of really, really bad data You have tons of customizations that you would like to

retire in order to use current features and functionalities and streamline your operations >>> can also Upgradeand streamline your operations >>> can also Upgrade

6

Why Upgrade? Per Oracle, when there is compelling business reason

to do soto do so New features and functionality to assist business Change in business direction; keep IT alignedg ; p g Replace customizations and bolt-ons with standard

featuresk d f h k i Take advantage of Tech. stack improvements

Obtain better support when patched currentB “F i d ” Be “Fusion ready”

Stay “in” support

7

Key Support As it Relates to R12Release GA Date

Premier Support

Ends

Extended Support

Ends

Sustaining Support

Ends11.5.10 Nov 2004 Nov 2010 Nov 2013* Indefinite

12 Jan 2007 Jan 2012** Jan 2015 Indefinite12.1 May 2009 Dec 2016** Dec 2019 Indefinite12.2 Sep 2013 Sep 2018 Sep 2021 Indefinite

*For Sustaining Support for Oracle E-Business Suite 11.5.10, provided from December 2013–December 2015, Oracle will continue to provide: Severity 1 fixes, critical patch updates and United States Tax Form 1099 updates for the 2013 and 2014 tax years. During this period, payroll regulatory tax updates will only be provided for the countries and tax years specified below.

Customers must have the indicated baseline patches (or above) for new Severity 1 production bug fixes as per Patch Requirements for Extended S t f O l E B i S it R l 11 5 10 ( D ID 883202 1)

Country 2013 Tax Year 2014 Tax Year

United States and Canada January 1, 2013 – December 31, 2014 January 1, 2014 – December 31, 2014

United Kingdom N/A April 6, 2013 – April 5, 2014

Australia N/A July 1, 2013 – June 30, 2014

Support of Oracle E-Business Suite Release 11.5.10 (see Doc ID 883202.1).

** For more detailed information on EBS 12.0 and 12.1 bug fixing and for Extended Support minimum patch pre-requisites, please refer to the EBS Error Correction Support Policy (Doc ID 1195034.1). For additional information regarding the above points, please see the EBS Support Policies FAQ (Doc ID 1494891.1).

Customers running Oracle Fusion Middleware 10gR2 and 10gR3 in the Oracle E-Business Suite version 12 internal technology stack will remain

8

g g g gysupported for the duration of the support period for Oracle E-Business Suite 12.

Oracle Application Support**For Sustaining Support for Oracle E-Business Suite 11.5.10, provided from December 2013–December 2015, Oracle will continue to provide: Severity 1 fixes, critical patch updates and United States Tax Form 1099

*For Sustaining Support for Oracle E Business Suite 11 5 10 provided from December 2013 December 2015 Oracle will continue to provide:

updates for the 2013 and 2014 tax years. During this period, payroll regulatory tax updates will only be provided for the countries and tax years specified below. For Sustaining Support for Oracle E-Business Suite 11.5.10, provided from December 2013–December 2015, Oracle will continue to provide:

Severity 1 fixes, critical patch updates and United States Tax Form 1099 updates for the 2013 and 2014 tax years. During this period, payroll regulatory tax updates will only be provided for the countries and tax years specified below.

Customers must have the indicated baseline patches (or above) for new Severity 1 production bug fixes as per Patch Requirements for Extended Support of Oracle E-Business Suite Release 11.5.10 (see Doc ID 883202.1).

** For more detailed information on EBS 12.0 and 12.1 bug fixing and for Extended Support minimum patch pre-requisites, please refer to the EBS Error Correction Support Policy (Doc ID 1195034 1) For additional information regarding the above points please see the EBS SupportEBS Error Correction Support Policy (Doc ID 1195034.1). For additional information regarding the above points, please see the EBS Support Policies FAQ (Doc ID 1494891.1).

Customers must have the indicated baseline patches (or above) for new Severity 1 production bug fixes as per Patch Requirements for Extended Support of Oracle E-Business Suite Release 11 5 10 (see Doc ID 883202 1)

9

Business Suite Release 11.5.10 (see Doc ID 883202.1).

Support TimelineUpdated for changes announced at Oracle Open World Updated for changes announced at Oracle Open World –– September, 2013September, 2013

We are here!

For more information check: My Oracle Support Note 1494891.1 - E-Business Suite Releases - Support Policy FAQ MOS Note 1195034 1 - EBS 12 0 and 12 1 Extended Support minimum patch pre-reqs

10

MOS Note 1195034.1 - EBS 12.0 and 12.1 Extended Support minimum patch pre-reqs

Support InformationOracle Lifetime Support Policy

Oracle Applicationspp

Go to: www.Oracle.comQuery: “lifetime-support-applications” y pp ppFill in: annoying Oracle sign in screen

11

Upgrade Type Technical upgrade only Focus on the tech stack / less expensive option Led by DBA / Tech team with little functional support Functional impact = testing and possibly training. Common with dot release upgrades (i.e. 11.5.9 to 11.5.10)

Management / Executive Sponsor

Project Manager

Technical Technical DBA / Sys. DBA / Sys. Developer / Developer / S US Uec caec caLeadLead

B/A Fin B/A SC & Other Trainer

/ Sys/ SysAdminAdmin

e e ope /e e ope /AnalystAnalyst

Business Process Owners

Super UserSuper Userss

Help Desk / Network Support

Success = NO CHANGE on go-live MondayEnd Users / Testers

Help Desk / Network Support

Success NO CHANGE on go-live Monday12

Upgrade Type Full Business-Aligned Upgrade Aligned with Business objectives / ROI expectation Inclusive, wide-ranging project across IT and Business Requires more Executive Sponsorship Change Management Project; not just technical

Management / Executive SponsorManagement / Executive Sponsor

Project ManagerProject Manager

TechnicalTechnicalDBA / SysDBA / Sys Developer /Developer /Technical Technical LeadLead

B/A Fin B/A Fin B/A SC & B/A SC & OtherOther TrainerTrainer

DBA / Sys. DBA / Sys. AdminAdmin

Developer / Developer / AnalystAnalyst

Business Business Process Process OwnersOwners

Super UsersSuper Users

Application changes must be addressed; there is no option

End Users / TestersHelp Desk / Network SupportHelp Desk / Network Support

Application changes must be addressed; there is no option

13

Why R12 is not your standard upgrade User Interface overhaul will

change to look and feel of the li ti fapplications for everyone

Certain modules had significant modifications and enhancementsmodifications and enhancements to features and functionality General Ledger A t P bl / P bl Accounts Payable / Payables Accounts Receivable Procurement services

ll h d l i h h… generally the modules with the most users

Reporting tools have been i dimpacted

14

R12 Lessons learned Finance / GLFinance / GL Sub ledger Accounting (SLA) for Operating Unit flexibilityg g ( ) p g y E–Business tax setups for each financial module have been

removed and are now centralized. Multi-Org Access Control (MOAC) - Provides role based access to Multi-Org Access Control (MOAC) - Provides role based access to

Operating Units. It can be confusing and dangerous to set up due to access to multiple operating units

Check out the critical reports early - Trial balances sub ledger Check out the critical reports early - Trial balances, sub ledger accounting, etc. are different with the XML /PDF output. Many reports no longer exist. New setups are needed in Sub Ledger Accounting (Open balance definitions) and some new templatesAccounting (Open balance definitions) and some new templates

15

R12 Lessons learned Accounts PayableAccounts Payable Invoice workbench and Invoice Processing New look Invoice workbench and Invoice Processing. New look

and feel for the workbench. iPayment functionality now included and affects vendor

consolidation for AP, CE, and Advanced AR iSupplier portal integration had been rough when product

was first released Has been cleaned up but test thoroughlywas first released. Has been cleaned up, but test thoroughly. Significant patching requirements early in release Information expansion (TCA arch.) led to long upgrade p ( ) g pg

steps and blown table extensions

16

R12 Lessons learned Oracle Business Intelligence Enterprise EditionOracle Business Intelligence Enterprise Edition Confirm OBIEE environment technical requirements forConfirm OBIEE environment technical requirements for

Web Server, Portal, Oracle Internet Directory (OID), OS

Web ADIWeb ADI Lost functionality/issues: Desk Top ADI > WEB ADI When moving from Desktop ADI to Web ADI, you lose the

ability to create financial statements in ADIy Will need to learn / use Report Manager

DiscovererDiscoverer Due to changes in underlying data model, many discoverer

reports will need to be fixed. Check out EBS Data Model Comparison Report (MOS Note 1290886.1)

17

Functionality to consider…R12.1.3

Released May, 2009 Significant functionality

improvements to SC, PO, and HCM

ProcurementProcurementProcurementProcurement

HCM Good info in MOS:

806593.1 – R12.1 Info CenterR12.1 Info Center269 1 d Ad i

Supply Supply ChainChain

Supply Supply ChainChain

ApplicationsApplicationsTechnologyTechnology

E-Business Suite 12 1 269.1 - Upgrade Advisor: E-

Business Suite (EBS) Upgrade from 11.5.10.2 to 12.1.3

740966 1 Advisor Webcasts

Customer &Customer &Master DataMaster DataManagemeManageme

HumanHumanCapitalCapitalHumanHumanCapitalCapital

Customer &Customer &Master DataMaster DataManagementManagement

FinancialsFinancials12.1

& Projects& Projects

740966.1 – Advisor Webcasts 804373.1 – R12.1 Value Proposition

documents

ggntnt

ManagementManagement

18

Upgrade Type Technical upgrade only Focus on the tech stack / less expensive option Led by DBA / Tech team with little functional support Functional impact = testing and possibly training Common with dot release upgrades (i.e. 11.5.9 to 11.5.10)

Management / Executive Sponsor

Project Manager

Technical Technical DBA / Sys. DBA / Sys. Developer / Developer / S US Uec caec caLeadLead

B/A Fin B/A SC & Other Trainer

/ Sys/ SysAdminAdmin

e e ope /e e ope /AnalystAnalyst

Business Process Owners

Super UserSuper Userss

Help Desk / Network Support

Success = NO CHANGE on go-live MondayEnd Users / Testers

Help Desk / Network Support

Success NO CHANGE on go-live Monday19

Upgrade Process Flow Start the process Critical strategy and

planning stage occursEvaluate new

release

UpgradeMake

adjustments

planning stage occurs here

Upgrade? Stay put

Install new release

Perform initial upgrade pass

Test / make adjustments

Yes

Perform test move to Prod. Test Acceptable

adjustmentsNo

No

pg p j

Yes

Schedule cut over dateFinal TestingReady?Yes

Go Live

Make final adjustments

No

20

Upgrade PlanningPlanning process needs to be comprehensive and inclusive of Business alignment and technicalBusiness alignment and technical aspects

Areas to evaluate include: Upgrade extent Business alignment Hardware / platform / network capacity Human resource availability – who and

when Training capacity and tools

A li i Application support Testing strategy and experience Oracle product strategy

P j l i & i Project planning & management capacity

21

A few words about R12.2 Available as of Open World, 2013

R t th HOLY GRAIL f P t hi i i l Represents the HOLY GRAIL of Patching… minimal downtime (middle tier re-boot only)

Makes use of Edition-Based Redefinition (EBR) Makes use of Edition-Based Redefinition (EBR) feature of the 11g Database

Had been delayed for more than 2 years for extensive y ytesting due to potential risk

Beta testers consist primarily of Oracle partners and integrators

22

System requirements

T l t fil t lPrepare1

Two complete file systems are always present Run Edition - Used by the running Application