Post on 29-Dec-2016
O2 WorksO2 Works Putting Oracle to Work
Oracle E-Business Specialists
Upgrading to R12.2 – Lessons learned and tips that you need to know to be successfulneed to know to be successfulTexas-Louisiana User Conference
O t b 27 2016October 27, 2016
Overview / Agenda
Introductions and Audience survey Upgrade vs re implement Upgrade vs. re-implement Why upgrade? Types of Upgrade Repeatable Methodology Upgrade planning Lessons learned when Upgrading from 11i to R12pg g R12.2.x – What’s so different and what are the concerns Information sources “Upgrading to the cloud” Upgrading to the cloud Contact information
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 17 years with Oracle Applications Experience with Oracle Consulting and two well
regarded Oracle Applications consulting firms Board Member of OAUG Upgrade SIGBoard Member of OAUG Upgrade SIG
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.3p
Project Manager
B i P O
p
Project Manager
B i P O
11.5.1 11.5.1 11.5.911.5.9
11 5 1011 5 10
11.5.1 11.5.1 11.5.911.5.9
11 5 1011 5 10Business 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 userEnd 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 significant reason causing you to have to re implementsignificant 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
Re-implementation considerationsYou might need to re-implement if: You have changed your basic business / organizationYou 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 unusableand 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 >>>
You can upgrade with customizationsYou can upgrade with customizations 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
Oracle Application supportRelease 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 2021** Not Available Indefinite12.2 Sep 2013 Sep 2023 Not Available 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.
Country 2013 Tax Year 2014 Tax Year
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).
** F d t il d i f ti EBS 12 0 d 12 1 b fi i d f E t d d S t i i t h i it l f t th EBS
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, 2014Australia N/A July 1, 2013 – June 30, 2014
** 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 supported for the duration of the support period for Oracle E-Business Suite 12.
E-Business Suite Applications Extensions for Oracle Endeca Products and EBS Mobile applications follow the Lifetime Support Policy of the
8
pp pp pp yE-Business Suite Release they utilize.
Support timeline
For more information check:
October, 2016
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 reqspatch pre-reqs
9
Oracle Lifetime Support PolicyOracle Applications
Go to: www.Oracle.comQuery: “lifetime-support-applications” Fill i i O l i iFill in: annoying Oracle sign in screen
10
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 / Super UserSuper UserssLeadLead
B/A Fin B/A SC & Other Trainer
AdminAdmin 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 Monday11
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 / Sys.DBA / Sys. Developer /Developer / S US UTechnical 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 optionEnd Users / Testers
Help Desk / Network Support
Application changes must be addressed; there is no option
12
Build a Repeatable Process Secure - Active Executive sponsorship and support
C i t T t ti P Communicate – Transparent reporting on Progress Gather - Proper Materials Recruit The Right Team Members Recruit - The Right Team Members Organize - Create and Update Critical documents Analyze and Plan Use Iterative Method (minimum Analyze and Plan – Use Iterative Method (minimum
= three rounds) Execute -A Serious and Dedicated Testing Processg Experience - Have a leader, bring back the vets
13
Secure Executive Sponsorship Who is the 800 lb. Gorilla?
High visibility buy-ing y y Support – active is better When you really have to have a decision… Helps control scope creep
Does the project have legs? Is it aligned to the current business objectives Strategic Return On Investment
CAUTION: When seeking Executive Sponsorship, expect the question of “What is the ROI?”q The bad news is that there is no return on an upgrade project investment Best approach is to reduce customizations in order to reduce the Total
Cost of Ownership (TCO)
14
Communication Have a comprehensive plan Understand the frequency Understand the frequency By what method / means
Know your audiencey What are they interested in Share relevant knowledge
Set the tone Be transparent Positi e Positive Recognize the value Focus on what upgrade will provide to businesspg p
15
Gather Proper Materials From My Oracle Support: Release Content Documents for releases between where
you are and where you want to be (for module leads only). Latest Implementation guides for each module in
production or moving to productionp g p Latest User guides for each module in or moving to Prod. Secure Passwords and Access for whole team New release information: New release information: E-Business Suite Upgrade Guide – [ID 461705.1] Upgrade Advisor: E-Business Suite (EBS) Upgrade from
11 5 10 2 to 12 1 3 (Doc ID 269 1)11.5.10.2 to 12.1.3 (Doc ID 269.1) Oracle E-Business Suite Release 12.2 Information Center -
Upgrade (Doc ID 1583158.1)
16
Gather Customizatons List of Customizations and Extensions Include all reports, forms, views, extracts, triggers, etcc ude a epo ts, o s, v ews, e t acts, t gge s, etc List of custom reports (in all forms) Interfaces
W kfl /A t G t D fi iti Workflow/Account Generator Definitions Oracle supported extensions Anything that touches Oracle that didn’t come shipped y g pp
from Oracle Corporation Disconnected Spreadsheet
Detailed design documents for all of above Detailed design documents for all of above Be prepared for some “unknown” customizations
17
Custom code change quagmire Oracle’s R12 Upgrade: Most code upgraded seamlessly,
butbut… Custom Code Requiring Changes during :
Forms: ~10% of forms and libraries needed touching Reports: ~1% of reports needed touching C code: ~20% of C code needed touching Java code: ~1% of overall Java code needed touchingg JSP’s: ~50% of JSP’s needed touching AutoConfig Configuration Customizations Development Tools: compilers Forms/Reports Builder 10 1 2 Development Tools: compilers, Forms/Reports Builder 10.1.2,
JDev10.1.3 Source: Ray Lin - Customer Service Support Manager: Oracle E-Business Suite Release 12 UpgradeRelease 12 Upgrade
18
More on customizations Look in aaplcust.txt for customizations
Part of Oracle application library Located in $AAPL_TOP/admin directory
Other options: CEMLI Services tool – Oracle subscription service Custom scripts Panaya – acquired by Infosys in Feb., 2015 Ringmaster
Customization strategy: Customization strategy: Identify / Assess (R12 Upgrade Considerations by Product – Doc.
889733.1) Retire as much as possiblep Upgrade what you can Re-implement what is left (only what you need)
19
Customization Strategyhttp://searchoracle.techtarget.com/tip/Working-with-custom-code-in-E-Business-Suite-upgrades
Minimize EBS custom code phase out obsolete analyze concurrent requests
Migrate only what's necessaryMigrate only what s necessary take a new copy from new release
and reintroduce the modificationsmain interface may not have been
tl difi d b tgreatly modified but test additional lookups or validations
or extra data transformations that were added
F i l t i k t dForms involve tricky custom codestart with fresh menu from Oracle &
make changes
20
Proper Materials - Hardware
Hardware, Software, and Network Space for Test Dev Training Environments Space for Test, Dev, Training Environments Cloning skills Scale-able instance strategy Adequate high speed storage / recovery capabilities Shared Project Folder or Space
Abili f O l S A if (O C Ability for Oracle Support Access if Necessary (ODC or Net meeting)
Adequate network bandwidth / throughputAdequate network bandwidth / throughput Remote access via secure VPN
21
Proper Materials – Hardware (cont.)Definition of Current State of Production All components of the tech stack All components of the tech stack
Browser Version Database App serverApp server Discoverer Self Service Framework Approvals Manager pp g Desktop OS Version of ADI Version on tools
Pay attention to certification for all tech stack elements http://blogs.oracle.com/stevenChan/certifications.html “Certifications” tab on My Oracle Support
22
Recruit Extended Team - Responsibilities
Management / Executive Sponsor
Project Manager
Business Business Technical Lead Analyst Fin.
AppsAnalyst SC &
OtherTrainer
DBA / Sys Developer / BusinessDBA / Sys. Admin
Developer / Analyst
Business Process Owners Super Users
Help Desk / Network Support
End Users / Testers
p pp
23
Recruit Team for 12.0 / 12.1 to 12.2Management / Executive Sponsor
Project Manager
DBA / Sys. Technical Lead Developer / Super UsersyAdmin Technical Lead p
Analyst Super Users
Business Business Business Analyst Fin.
AppsAnalyst SC &
OtherProcess Owners
Trainer
Help Desk / Network Support
End Users / Testers
24
Two Critical DocumentsMaster Checklist – Build a Master list for the upgrade
and list every step.and list every step. TIP: Download Maintenance Wizard to a spreadsheet. Capture
timings for pre, during, and post patching. LIST and Assign EVERYTHINGEVERYTHING.
Master Impact List – Complete full listing of allpotential changes that should require investigationpotential changes that should require investigationor retesting Drives new features use and all testingg Applies to standard Oracle features and Customer-
created impacts
25
Master Impact List Items
Some Examples: 3rd Party Check Printing System may need to be 3rd Party Check Printing System may need to be
retested or replaced with XML / BI Publisher Custom Form may need to have customization
reapplied to standard Oracle form Account Generator changes might get overwritten, and
i b l hit may be necessary to reapply changes New Report available as standard functionality, we may
want to review as a potential business solutionwant to review as a potential business solution Standard Interface may have new parameters, may need
to resubmit for recurring submission (scheduling)
27
Execute – Dedicated Testing Process Have a library of Test Cases Detailed test scriptsp Include and use cases from past 11i Implementation or
upgrades Be prepared to add some test cases for new features or Be prepared to add some test cases for new features or
functionality Modify test cases to reflect new or changed functionality
M k h ifi b d d Make sure your test cases have specifics about test data and expected results
Check them back in to the library for next timey More testers = more familiarity with application prior to go-
live > less productivity loss Track every item and assign accountability Track every item and assign accountability
28
Analyze and Plan – Iterative Method
Analyze, Plan, Estimate, Repeat
Use as a Tool to Build your Project Plan
29
Upgrade Process Flow Start the process
At l t 3 it ti b f G LiEvaluate new
release
UpgradeMake
adjustments
At least 3 iterations before Go-Live
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 date
Final Testing
Ready?YesGo
Live
Make final adjustments
No
30
The Process – Go Live & beyond Cutover / War Room Post Cutover Support (DON’T test in Production) Post Cutover Support (DON T test in Production) Update and File Library of Test Cases and
Scripts for future useScripts for future use Keep updated and available – all Training information
(how-to’s, FAQ’s, tests)A hi Archive: Master Impact List Materials for next upgradepg Redevelopment timings, etc
32
Experience – Have a leader & Bring back the vets
There is no substitute for experience Veteran users will pick up on anomalies more easily Veteran users will pick up on anomalies more easily Experienced testers know what they are looking for and
what constitutes a material issue In the 11i to R12 upgrade the leader will need to In the 11i to R12 upgrade, the leader will need to
understand the Functional concerns as well as the Technical issues.
M t b bl t i t ith th F ti l d Must be able to communicate with the Functional and Technical resources
Will need to communicate effectively with managementTh 11i R12 d i h b i l The 11i to R12 upgrade is a much more substantial project and will require a greater change management focus
33
Upgrade Process Flow Start the process Critical strategy and
planning stageEvaluate 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 date
Final Testing
Ready?YesGo
Live
Make final adjustments
No
34
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 ti t Application support Testing strategy and experience Oracle product strategy P j t l i & t it Project planning & management capacity
35
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
36
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
37
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 Significant patching requirements early in release Information expansion (TCA architecture) and data Information expansion (TCA architecture) and data
bifurcation has led to long upgrade steps and blown table extensions
38
R12 Lessons learned Web ADIWeb ADI Lost functionality/issues: Desk Top ADI > WEB ADILost functionality/issues: Desk Top ADI WEB ADI When moving from Desktop ADI to Web ADI, you lose the
ability to create financial statements in ADIWill d t l / R t M i d t Will need to learn / use Report Manager in order to replace lost functionality
DiscovererDiscovererDiscovererDiscoverer Due to changes in underlying data model, many
discoverer reports will need to be fixed. Check out EBS C i ( OSData Model Comparison Report (MOS Note
1290886.1)
39
R12 Lessons learned – More AP Most problematic module Redesign has led to data corruption in almost every Redesign has led to data corruption in almost every
upgrade Good news… MOS has scripts that can fix data issues Preventative Tool: Oracle Payables 11i Accounting
Health Check ID 416699 1Health Check ID 416699.1 Download SQL script package and run it Flags various issues that will cause a problem and generates
SR’s. Resulting scripts from MOS must be run to clean up data Accounts Payabley
40
Functionality to consider…R12
Significant functionality improvements to SC, PO, and HCM
Good info in MOS:ProcurementProcurementProcurementProcurement
Good info in MOS: 1614508.1 - Upgrade Advisor: E-
Business Suite (EBS) 11i Upgrade to 12 2 (Doc ID)
Supply Supply ChainChain
Supply Supply ChainChain
ApplicationsApplicationsTechnologyTechnology
E-Business Suite 12 1 to 12.2 (Doc ID)
806593.1 – R12.1 Info Center 740966.1 – Advisor Webcasts 804373 1 – R12 1 Value Proposition
Customer &Customer &Master DataMaster DataManagemeManageme
HumanHumanCapitalCapitalHumanHumanCapitalCapital
Customer &Customer &Master DataMaster DataManagementManagement
FinancialsFinancials12.1
& Projects& Projects
804373.1 R12.1 Value Proposition documents
ggntnt
ManagementManagement
41
A few words about R12.2 Available as of Open World, 2013 Represents the HOLY GRAIL of Patching… minimal p g
downtime (middle tier re-boot only) Makes use of Edition-Based Redefinition (EBR) feature of
the 11g and 12c Databasethe 11g and 12c Database Had been delayed for more than 2 years for extensive testing
due to potential riski d i il f O l d Beta testers consisted primarily of Oracle partners and
integrators so the initial testing did not necessarily hold up to “full use” environments
The future ability to avoid outages is critically important to 24 hour shops (i.e. world-wide operations and 3 shift manufacturers) who can’t accommodate down-timemanufacturers) who can t accommodate down-time.
42
R12.2 Overview
T l t fil t lPrepare1
Two complete file systems are always present Run Edition - Used by the running
Prepare
Application Patch Edition – Either: Currently being patched Cutover
Cutover2
1
y g por Waiting for the next patching cycle
The two files systems are rotated between RunP The two files systems are rotated between Run and Patch during every patch cycle
Prepare2
Source: Kevin Hudson - Online Patching with Oracle E-Business Suite 12.2g
43
R12.2– Resource Considerations Database SYSTEM tablespace requires double current space allocationp q p 25GB increase to 50GB
SEED tablespace requires double its current space allocation 5GB increases to 10GB
File System 2 file systems require double the space of 1 file system
Database Objects & code m st follo ne set of standards Database Objects & code must follow new set of standards Necessary in order to successfully patch objects Online
Review customizations for Online Patching standardsg Database check report (ADZDDBCC.sql) Scans the data dictionary for violating objects and code
File System check report (gscc.pl)File System check report (gscc.pl)
44
R12.2 Adoption planning Understand your risk profile Conservative or “bleeding edge”Co se vat ve o b eed g edge Higher risk on this due to technical implications
Consider the support extensions (slides 9 – 10)12 2 i t h i l l it 12.2 increases technical complexity DBA will need to re-learn how to patch New development standards If you are coming from 11i, you’re taking a double hit!
Consider the hardware requirements if making changes MOS ability to support effectively is lagging MOS ability to support effectively is lagging Not many DBA’s with R12.2 project experience
45
R12.1.3 v. R12.2 Risk Considerations
Risk area R12.1.3 R12.2
Application maturity and stability X
Functional: learning / participation required X X
Functional: testing support X X
Developer: significant code remediation X X
DBA: upgrade skills overhaul XDBA: upgrade skills overhaulExternal application support experience X
Increased hardware requirements possible X
= Risk covered / moderatedX = Risk exists
46
For More Information My Oracle Support Appsnet – Good Summary on New Features Appsnet Good Summary on New Features http://www.oracle.com/appsnet/technology/
upgrade/docs/features htmlupgrade/docs/features.html Online Help – (New Features Section) Reference Manuals Reference Manuals Blogs: Steven Chan: http://blogs.oracle.com/schan/ User Groups / Conferences User Groups / Conferences
47
More Information on R12.1.3Upgrade Advisor: E-Business Suite (EBS)
Upgrade from 11.5.10.2 to 12.1.3 (Doc ID 269.1)
48
More Information on R12.2Upgrade Advisor: E-Business Suite (EBS) 11i
Upgrade to 12.2 (Doc ID 1614508.1)
49
“Upgrading to the cloud”
For EBS customers who run or host their own platform (according to Oracle that is a “Private Cloud”) and think ( g )they have an option to “Upgrade” to the cloud… think again!
It is a full-on, heavy duty re-implementation project that , y y p p jwill require that any customizations are redeveloped as part of the Platform as a Service (PaaS) offering in addition to the Software as a Service (SaaS) component
Transitioning EBS to the cloud will reduce users flexibility to customize their applications
Be certain that that the cloud footprint features and f i li ill ll f li i dfunctionality will serve all of your application needs.
Don’t be fooled by the manic push to get everyone to think the Cloud is now. It is still years away.
50
“Upgrading to the cloud”
As Oracle shifts their focus to become the cloud leader, you will hear about how you can just “lift and shift” your EBSwill hear about how you can just lift and shift your EBS platform to the Oracle Cloud under their Infrastructure as a Service (IaaS) offering. That is correct.
Oracle’s Infrastructure as a Service Cloud (IaaS) offering is Oracle’s Infrastructure as a Service Cloud (IaaS) offering is Hosting. They have been doing it for years
It h b k “O l O D d” It has been known as “Oracle On Demand”. There are numerous EBS hosting organizations. (i.e. MTG) This is not Oracle’s Software as a Service (SaaS) cloud ( )
application that used to be know as the “Fusion” apps. It is your EBS applications running in Oracle’s data center.
51
About O2Works
O2Works is one of the leading E-Business Suite servicesproviders offering the most experienced teams of functional andtechnical consultants in the industry. Our hands-on resourcesaverage 18+ years of experience focused exclusively oni l ti di i t ti d t di O l ' Eimplementing, upgrading, integrating, and extending Oracle's E-Business Suite. Stop by and talk to us about our large portfolio ofsuccessful projects.
R12 Presentations, White Papers, and other information shared on-line at:
www.o2works.com/knowledgeworks
52