R12 Up Grade
Upcoming SlideShare
Loading in...5

R12 Up Grade



R12 Up Grade

R12 Up Grade

By Jody Freeman



Total Views
Views on SlideShare
Embed Views



1 Embed 11

http://www.linkedin.com 11



Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
Post Comment
Edit your comment

R12 Up Grade R12 Up Grade Presentation Transcript

  • Analyzing, Planning, and Executing an R12 EBS Upgrade by
    Absolute Applications
  • Agenda and Purpose
    This presentation is intended primarily for people who are helping to evaluate or manage an upgrade, but it also contains valuable information for anyone who might be involved in the upgrade process.
    Walk through steps in preparing for and managing an upgrade to R12, including
    • Decision making
    • Identifying objectives
    • Scope and approach
    • Organization and team preparation
    • Oracle tools and resources
    • Timeline planning
    • Testing tips
  • Overview Upgrade Steps
  • Upgrade Steps
  • Evaluate
  • Evaluate
    R12 Highlights
    Oracle development has focused on improving the ability of EBS to
    better manage complex global businesses, especially where
    organizations are centralizing their applications into a shared service
    18 new products with almost 2500 enhancements, including:
    • Ledgers and Ledger Sets - replace Sets of Books
    • Financials Accounting Engine – Sub ledger Accounting
    • Tax Engine - E-Business Tax
    • Cross Organization Responsibilities - MOAC
  • Evaluate
    Architecture and Technology Changes
    • Redesigned workflows
    • Upgraded user interface based on PeopleSoft
    • More Personalization's
    • Expanded use of BI Publisher and Fusion Middleware
    • Increased Performance
    • Lowered IT costs through hardware consolidation and virtualization
    • Improved integration with Oracle Identity Management
    • Reduced production downtime for patch applications
  • Evaluate
    Technical Considerations
    Implement significant technical advances available in R12 for business benefits
    you may need
    • High-Availability and Scalability using Oracle Database Cluster (10gRAC) and Oracle Applications Cluster with Load-balancing
    • Business Continuity and Disaster Recovery using Oracle Database Physical DataGuard across remote data-centers
    • Oracle Automated Storage Management (ASM) for a variety of storage solutions
    • Advanced Security for External Users (e.g., for iSupport Portal)
    • Use of Single Sign-on / integration with Oracle IDM
    • Use of Oracle Application Integration Architecture (AIA) based on Fusion Middleware / SOA
  • Upgrade Steps
  • Plan
    Define Appropriate Scope
    • Combine with hardware or OS upgrade
    • Instance merge into single, global instance
    • Deploy new (required) functionality
    • Deploy new (optional) functionality
    Right-Sized Phasing – Risk vs. Return
  • Plan
    Define Approach
    • Upgrade vs. Re-Implementation
    • Replace customizations
    • Retool processes
    • Take advantage of simplification opportunities in advance of upgrade
    • Phasing
  • Plan
    Customizations Revisited...
    • Whats are they?
    • Whats tools were they built with?
    • Are they still required?
    • Obsolete functionality
    • Replaced by new features
    Future Approach
    • Configuration, Not Customisation
    • Conform to Fusion architecture
    3. Result
    • Reduced maintenance Cost
    • Reduced risk of architecture obsolescence
    • Easier to upgrade
  • Plan
    Recommended required upgrade to 11g database be done in advance of R12 Upgrade
  • Upgrade Steps
  • Prepare
    Organisation preparation
    • Take into account above scope
    • Change Management
    • Data model
    • Functionality (esp. Financials)
    • Build momentum from executives through to users
    • Involve Business Owners
  • Prepare
    Assemble the team
    • Best and brightest
    • Plan to bolster weak areas
    • Assess current Oracle skills
    • Plan to backfill
    • Potential Organization Chart
  • Prepare
    Team Needed to complete Upgrade
    • X2 Functional Consultants (To split GL, AP&FA
    • X1 Functional PO consultant
    • X1 DBA
    • X1 Developer
    • X1 Project Manager
  • Prepare
    Take advantage of available R12 Content: (https://metalink.oracle.com/)
    • Online training (403349.1)
    • Upgrade Resources (461705.1)
    • Oracle Applications Upgrade Guide (E12011.02)
    • Oracle Financials and Oracle procurement Functional Upgrade Guide: Release 11i to Release 12 (B31543101)
    • Release 12 Release notes, Release content documents (404152.1)
    • Documentation resources Release 12 (394692.1)
  • Prepare
    Pre-upgrade tasks
    • Use Tums to eliminate Unnecessary upgrade tasks
    • Reduce upgrade down time
    • Upgrade guide: release 11i to Release 12
    • Reducing downtime Upgrade Guide, Appendix E)
    • Upgrade by request (upgrade Guide, Appendix G)
    • Convert to multi Org
    • Convert to OATM
    • Upgrade database to 11g
    • Record duration of each step during test upgrade
    • Make a valid back-up before both the database and applications upgrades
  • Upgrade Steps
  • Execute
    Maintenance Wizard (215527.1)
    • Step-by-step, graphical user interface for performing upgrade tasks.
    • Consolidates instructions from Multiple sources to present a comprehensive upgrade picture
    • Reduces upgrade tasks by filtering out those that do not apply to you (using TUMS)
    • Indicates Critical Patches that your system requires
    • Can automatically execute upgrade tasks for you
  • Execute
  • Execute
    Use the latest patch set to eliminate known issues (557869.1)
  • Execute
    Notes on testing
    • Leverage 11i test scripts updated to reflect new, relevant Release 12 functionality and process changes
    • Test all business flows and scenarios using new and existing data
    • Test workflows in process
    • Execute multiple testing rounds and budget enough time for issue resolution
    • Perform at least 2 successful test upgrade cycles before upgrade cutover
    • If changing OS (e.g., Unix to Linuz, or windows to Unix/Linuz), add another successful test cycle
    • Perform adequate load and volume testing
    • Time the upgrade process to gauge duration required for cutover
    • 12.1 Patchset (12.1.3 Patch Number 9239090)
  • Upgrade Steps
  • Maintenance
    Full post go-live support for a minimum 1month