Life after upgrading to r12
Download as POT, PDF0 likes1,232 views
Origin upgraded its Oracle E-Business Suite from version 11i to R12 in 2009, which led to various performance, validation, and module issues over the first few months; a remediation project was implemented to address the backlog of issues through additional resources, optimization, and patches over 4 months; after further hardware upgrades and implementation of additional patches over 4-6 months, the system was stabilized and help desk calls were reduced.
Ad
More Related Content
What's hot (20)
Viewers also liked (6)
Ad
Similar to Life after upgrading to r12 (20)
Ad
More from InSync Conference (20)
Recently uploaded (20)
Life after upgrading to r12
- 1. Life after upgrading to R12 at Origin Mark Bollmeyer Origin 16 th August 2010 The most comprehensive Oracle applications & technology content under one roof
- 3. Origin in 2008 Oracle eBusiness version 11.5.10 Relatively low number of production issues Stable Production environment. Well known and understood processes No Performance issues
- 4. Why did Origin go to R12 ? Origin had multiple requirements for an Asset Management system Oracle Asset Management Solution (eAMS) selected as the enterprise solution The functionality Origin required in the eAMS solution had R12 as pre-requisite Project set up to Upgrade to R12 Rollout eAMS Migrate our upstream business from JD Edwards to Oracle eBusiness Introduce a new operating unit for APLNG โ Joint Venture In hindsight, any one of these components would have been a project with sufficient challenges to tackle on their own
- 5. Originโs R12 project Originโs R12 project was run during 2008 Originally scheduled for go โ live in November 2008 Rescheduled to January 2009 Key lessons learnt from the project Post Implementation Review The R12 Upgrade should be a project in itโs own right if possible Allocate time and resources to understanding the mandatory new modules and functionality Upgrading customisations will take more effort than you expect Test early, test thoroughly Defect management and resolution will take more effort than you expect Training is important, but communications are critical
- 6. R12 go live Go live went from 8 th Jan โ 11 th Jan 2009 Implementations for the remainder of the project (upstream rollout, eAMS rollout ) occurred over the next 1-2 weeks Went live with version 12.0.5 Upgraded 2 existing operating units from R11 to R12 Implemented 2 new operating units in R12
- 7. What happened in the 1st month after R12 go live โฆ
- 8. Some of the key R12 issues we experienced were โฆ Performance What we saw Delays logging on Java forms slow Disconnections Workflow mailer backlog What we did Ensure technical software versions and configurations are correct Web Cache software improved performance at remote sites Reverted to forms Socket Mode (from Servlet Mode) JVM sizing wrong for 11i and required resizing in R12 Tuned concurrent manager sizing
- 9. Some of the key R12 issues we experienced were โฆ Points to note This was not unexpected due to limited R12 implementations in Australia Ensure time scheduled for load testing Ensure Oracle and hardware vendor reviews and signs off on versions and configurations
- 10. Some of the key R12 issues we experienced were โฆ Invoice Validation Performance What we saw Invoice validation was not completing overnight Operating units conflicting with each other If a run was terminated -> records locked Particularly an issue at month end -> couldnโt close payables until finished What we did Baby-sit invoice validation overnight Hot-fix supplied by Oracle to ensure correct indexes used Patch supplied to limit the number of records processed Points to note Ensure hot-fix and patch applied Ensure invoice validation is in your regression test suite
- 11. Some of the key R12 issues we experienced were โฆ Payables table structures changed What we saw Could not process R11 invoices in R12 What we did Data fixes to process some records Cancel R11 invoices and create R12 invoices Points to note Ensure all invoices processed before upgrade Develop in-flight process for those that canโt Ensure processes for how to handle R11 well communicated
- 12. Some of the key R12 issues we experienced were โฆ Reports What we saw Originโs plan to move back to standard reports as much as possible was not successful What we did Many custom reports upgrade / developed after go live Points to note Commit to using Standard reports or plan (schedule & budget) to do a lot of report upgrade / development
- 13. Some of the key R12 issues we experienced were โฆ New / Reworked modules (Payments, eBusiness tax, SLA) What we saw These modules gave us the most issues What we did Steep learning curve Obtain outside assistance Points to note Plan (schedule & budget) to understand these modules before go-live
- 14. Some of the key R12 issues we experienced were โฆ Withholding Tax What we saw Withholding Tax did not work in R12 What we did Implement workarounds Long engagement with Oracle to resolve this SR Points to note Ensure the version you go live with contains the required patches
- 15. Which modules were impacted by R12 โฆ
- 16. What happened then โฆ Transition to Support
- 17. The picture after 4 months โฆ
- 18. Remediation Project Situation did not materially change as a result of transition to support Not sustainable for our business Remediation Project set up to address the backlog Objectives Return outstanding calls to Business as Usual level (target 275) Return outstanding SRs with Oracle to Business as Usual level (target 30) Reduce the number of new calls per day by 20% New calls to be actioned within our Service Level Agreement Recommendation made on a patch release Technical review undertaken
- 19. โฆ And then โฆ
- 20. Remediation Project Details 4-6 additional functional resources required for 4 months Availability, Cost, Travel and Accom Lot of work required with Oracle to progress critical SRs Focus required to ensure support process for new calls was appropriate Outside of difficult SRs, no real problems encountered Technical review done by Oracle โ tactical hardware upgrade recommended Review of potential next patch release No official patch release would address our critical SRs Testing confirmed that a combination of several mega-patches (400-600 fixes in each patch), July CPC and a range of smaller patches would address our critical SRs Project Targets achieved
- 21. Help desk calls by module โ after remediation
- 22. Tactical Hardware Upgrade Goals Address month end performance issues Create headroom to re-introduce end-user reporting capacity Ensure capacity available for coming 12 months Tasks Transform from 1-tier to 2-tier architecture New server plus additional memory required Proof of concept, Regression Test, Performance Test
- 23. Tactical Hardware Upgrade (cont) Timeframes Very tight timeframes to meet project deadlines and half year-end reporting Approval thru to implement in 2 months Results Very successful Performance issues gone Project deadlines not impacted Half Year end not impacted
- 24. Patch Release Goals Implement solutions to critical SRs Retain performance of Invoice validation Tasks Scope and build test cases Use of structured test cases and defect management Integration Testing, User Acceptance Testing 5-6 FTEs
- 25. Patch Release (cont) Timeframes Originally 3 months, Grew to 4 months Significant effort to resolve Tax config issues for upgraded operating units Results Very Successful Improved stability of P2P particularly Invoice Workbench Identified some tax config issues resulting from the R12 upgrade 1 minor issue post go-live Now have full set of P2P test cases which are used in regression testing
- 26. โฆ Finallyโฆ
- 27. Help desk calls by module โ after patch release
- 28. In Summary In the 12 months since go live, Origin has had 4 months of Project Heightened Support 4 months of Remediation project Implemented several new projects Hardware upgrade Major patch release This has been achieved by Significant hard work by my support team and our project team Significant hard work, patience and support from our business stakeholders Important assistance from Oracle at the crunch times First12 months after R12 was probably the 12 months we had to have as we were early adopters (thanks Paul Keating)
- 29. Final Thoughts Consider carefully before including any other scope in your R12 project Make sure your technical environment and hardware is set up to perform to R12 requirements early on in your project Consider carefully whether you want to upgrade to R12 or re-implement R12. Plan for expert assistance from Oracle to assist with New Payments engine E-Business Tax Sub Ledger Accounting Donโt plan on a short Heightened Support period โ minimum of 3 month ends Plan for a period of Remediation and/or stabilization for some months after that Plan for a hardware health check post stabilization Regression Testing is all-important in an R12 environment
- 30. Tell us what you thinkโฆ http://feedback.insync10.com.au