Putting Oracle to Work Oracle E-Business Specialists. NorCal OAUG

Transcription

1 O2 Works Putting Oracle to Work Oracle E-Business Specialists R12 Upgrade Lessons learned and what you need to know to succeed NorCal OAUG 2014 Training Day August 26, 2014

2 Overview / Agenda Introductions and Audience survey 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 you Keys to Success Process Components Resources Methodology Other Information sources 2

3 R12 Upgrade Introduction Art Dowd, Consulting Director, O2Works Former VP of IT for Hospitality Company Extensive business background Implemented / Upgraded Oracle ebus Suite 12 years with Oracle Applications Experience with Oracle Consulting and two well regarded Oracle Applications consulting firms 3

4 Audience survey Role Technical DBA Technical Developer Project Manager Business Process Owner Super user Apps Release level End user

5 Upgrade vs. re-implement Back in the dark ages (pre 11i) there were technical concerns 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 significant ifi reason causing you to have to re-implement Upgrade process, technology, tools, and scripts are significant improved Re-implementation = much more extensive project Data conversion / testing will be an issue 5

6 Re-implementation considerations You might need to re-implement if: You have changed your basic business / organization structure and your application configuration does not still fit your business Single instance consolidation Your original implementation was really screwed up and it 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 Upgrade 6

7 Why Upgrade? Per Oracle, when there is compelling business reason to do so New features and functionality to assist business Change in business direction; keep IT aligned Replace customizations and bolt-ons with standard features Take advantage of Tech. stack improvements Obtain better support when patched current Be Fusion ready Stay in support 7

8 Key Support As it Relates to R12 Release GA Date Premier Support Ends Extended Support Ends Sustaining Support Ends Nov 2004 Nov 2010 Nov 2013* Indefinite 12 Jan 2007 Jan 2012** Jan 2015 Indefinite 12.1 May 2009 Dec 2016** Dec 2019 Indefinite 12.2 Sep 2013 Sep 2018 Sep 2021 Indefinite *For Sustaining Support for Oracle E-Business Suite , 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. 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 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 (see Doc ID ). ** 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 ). For additional information regarding the above points, please see the EBS Support Policies FAQ (Doc ID ). Customers running Oracle Fusion Middleware 10gR2 and 10gR3 in the Oracle E-Business Suite version 12 internal technology stack will remain supported for the duration of the support period for Oracle E-Business Suite 12. 8

9 Oracle Application Support **For Sustaining Support for Oracle E-Business Suite , 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. *For Sustaining Support for Oracle E-Business Suite , 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 (see Doc ID ). ** 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 ). 1) For additional information regarding the above points, please see the EBS Support Policies FAQ (Doc ID ). 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 (see Doc ID ). 9

10 Support Timeline Updated for changes announced at Oracle Open World September, 2013 We are here! For more information check: My Oracle Support Note E-Business Suite Releases - Support Policy FAQ MOS Note EBS 12.0 and Extended Support minimum patch pre-reqs 10

11 Support Information Oracle Lifetime Support Policy Oracle Applications Go to: Query: lifetime-support-applications Fill in: annoying Oracle sign in screen 11

12 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 to ) Management / Executive Sponsor Project Manager DBA /Sys Sys. Technical ca Developer e / Admin Lead Analyst Super Users B/A Fin B/A SC & Other Business Process Owners Help Desk / Network Support End Users / Testers Trainer Success = NO CHANGE on go-live Monday 12

13 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 Sponsor Project Manager DBA / Sys. Technical Developer / Admin Lead Analyst Super Users B/A Fin B/A SC & Other Business Process Owners Help Desk / Network Support End Users / Testers Trainer Application changes must be addressed; there is no option 13

14 Why R12 is not your standard upgrade User Interface overhaul will change to look and feel of the applications for everyone Certain modules had significant modifications and enhancements to features and functionality General Ledger Accounts Payable /P Payables Accounts Receivable Procurement services generally the modules with the most users Reporting tools have been impacted 14

15 Finance / GL R12 Lessons learned Sub ledger Accounting g( (SLA) for Operating Unit flexibility 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 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 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 templates 15

16 R12 Lessons learned Accounts Payable 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 thoroughly. Significant patching requirements early in release Information expansion (TCA arch.) led to long upgrade steps and blown table extensions 16

17 R12 Lessons learned Oracle Business Intelligence Enterprise Edition Confirm OBIEE environment technical requirements for Web Server, Portal, Oracle Internet Directory (OID), OS Web 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 ADI Will need to learn / use Report Manager Discoverer Due to changes in underlying data model, many discoverer reports will need to be fixed. Check out EBS Data Model Comparison Report (MOS Note ) 17

18 Functionality to consider R Procurement Applications Technology E-Business Financials & Projects Suite Customer Customer & Master Data Master Data Management Manageme nt Supply Chain Human Capital Released May, 2009 Significant functionality improvements to SC, PO, and HCM Good info in MOS: R12.1 Info Center Upgrade Advisor: E- Business Suite (EBS) Upgrade from to Advisor Webcasts R12.1 Value Proposition documents 18

19 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 to ) Management / Executive Sponsor Project Manager DBA /Sys Sys. Technical ca Developer e / Admin Lead Analyst Super Users B/A Fin B/A SC & Other Business Process Owners Help Desk / Network Support End Users / Testers Trainer Success = NO CHANGE on go-live Monday 19

20 Upgrade Process Flow Start the process Evaluate new release Critical strategy and planning stage occurs here Upgrade? No Stay put Make adjustments Yes No Install new release Perform initial Test / make upgrade pass adjustments Perform test move to Prod. Test Acceptable Yes Go Live Yes Ready? Final Testing Schedule cut over date No Make final adjustments 20

21 Upgrade Planning Planning process needs to be comprehensive and inclusive of Business 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 Application i support Testing strategy and experience Oracle product strategy Project planning & management capacity 21

22 A few words about R12.2 Available as of Open World, 2013 Represents the HOLY GRAIL of Patching minimal i downtime (middle tier re-boot only) Makes use of Edition-Based Redefinition (EBR) feature of the 11g Database Had been delayed for more than 2 years for extensive testing due to potential risk Beta testers consist primarily of Oracle partners and integrators 22

23 System requirements 1 Prepare Two complete file systems are always present Run Edition - Used by the running Application