Upgrade to R12 Why and How

Embed Size (px)

Citation preview

  • 8/6/2019 Upgrade to R12 Why and How

    1/51

    Putting Oracle to Work

    Oracle E-Business Specialists

    Managing a Successful R12 e Business Suite Upgrade A Repeatable Methodology to Help Ensure Success

    Michigan Oracle Users Summit September 24, 2009

  • 8/6/2019 Upgrade to R12 Why and How

    2/51

    OverviewIntroductions and Audience survey

    Upgrade typesR12 Ex erience / Wh it is differentUpgrade process and planning

    Keys to Success Process ComponentsResourcesMethodology

    2

  • 8/6/2019 Upgrade to R12 Why and How

    3/51

    Introduction - Speaker

    , ,Former VP of IT for Hospitality CompanyExtensive business back roundImplemented / Upgraded Oracle eBus Suite

    10 years with Oracle ApplicationsExperience with Oracle Consulting and two wellregarded Oracle Applications consulting firms

    3

  • 8/6/2019 Upgrade to R12 Why and How

    4/51

    Audience surveyRole Apps Release level

    Technical DBA

    10.7

    Project Manager 11.5.1 11.5.7

    Business Process Owner

    Super user

    11.5.8 or 11.5.9

    11.5.10

    End user

    4

  • 8/6/2019 Upgrade to R12 Why and How

    5/51

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

    people opted to re-implementDue to the significant changes to the apps in going to R12the question is surfacing again

    Recommendation = upgrade unless there is as gn cant reason caus ng you to ave to re- mp ement

    Upgrade process, technology, tools, and scripts aresi nificant im rovedRe-implementation = much more extensive projectData conversion / testing will be an issue

    5

  • 8/6/2019 Upgrade to R12 Why and How

    6/51

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

    ou ave c ange your as c us ness organ za onstructure and your application configuration does not stillfit our businessYou have tons of customizations that you would like to

    retire in order to use current features and functionalitiesand streamline your operationsYour original implementation was really screwed up and it

    s as ca y unusa eYou have tons of really, really bad data

    6

  • 8/6/2019 Upgrade to R12 Why and How

    7/51

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

    New features and functionality to assist businessChan e in business direction; kee IT ali nedReplace customizations and bolt-ons with standard

    featuresTake advantage of Tech. stack improvementsObtain better support when patched current

    e us on rea yStay in support

    7

  • 8/6/2019 Upgrade to R12 Why and How

    8/51

    Application supportRelease GA Date

    PremierSupport Ends

    ExtendedSupport Ends

    SustainingSupport Ends

    . .

    11.5.1 11.5.6 Jul 2006 Not Offered Indefinite

    11.5.7 May 2002 May 2007 Not Offered Indefinite

    11.5.8 Nov 2002 Nov 2007 Not Offered Indefinite

    11.5.9 Jun 2003 Jun 2008 Not Offered Indefinite

    11.5.10 Nov 2004 Nov 2010 Nov 2013 Indefinite

    R 12 Jan, 2007 Jan, 2012 Jan, 2015 Indefinite

    R12.1 May, 2009 May, 2014 May, 2017 Indefinite

    rac e - us ness u te e eases an w eac ave a rect pat to t e app cat ons u t on Oracle Fusion Middleware.

    For the first two years of Sustaining Support for release 11i9, Oracle will provide fixes for Severity 1production bugs. The only legislative update that will be provided is for U.S. Tax Form 1099 for the

    8

    tax year.

  • 8/6/2019 Upgrade to R12 Why and How

    9/51

    A lication su ortPremier Support covers five years from the general availability date Provides maintenance and support of your Oracle Database, Oracle FusionMiddleware, and Oracle Applications covering:

    Major product and technology releases Technical support , , , , Tax, legal, and regulatory updates Upgrade scripts Certification with most new third-party products/versions Certification wit most new Oracle pro ucts

    Extended Support - an extra three years of support for specific Oraclereleases for an additional fee.

    , ,including access to online support tools, knowledge bases, and technicalsupport experts. (Metalink and phone support)

    9

  • 8/6/2019 Upgrade to R12 Why and How

    10/51

    T ical U rade Process FlowStart theprocess

    Evaluate newrelease

    Make

    ? Stay put

    Install newrelease

    Perform initialup rade pass

    Test / makeadjustments

    Yes

    Perform testmove to Prod.

    Test Acceptable

    No

    No

    Yes

    Schedule cutover date

    Final TestingReady ?YesGo

    Live

    Make finaladjustments

    No

    10

  • 8/6/2019 Upgrade to R12 Why and How

    11/51

    Upgrade TypeTechnical upgrade only

    Led by DBA / Tech team with little functional supportFunctional impact = testing and potentially trainingLess expensive optionCommon with dot release upgrades

    -Aligned with Business objectivesInclusive, wide-ranging project across IT and Business

    Requires more Executive SponsorshipInvestment in the IT / Business needs

    11

  • 8/6/2019 Upgrade to R12 Why and How

    12/51

    Why R12 is not your standard upgradeUser Interface overhaul willchange to look and feel of theapp cat ons or everyoneCertain modules had significantmodifications and enhancements to features and functionality

    General Ledgerccoun s aya e aya es

    Accounts ReceivableProcurement services

    generally the modules with the most users

    Re ortin tools have beenimpacted

    12

  • 8/6/2019 Upgrade to R12 Why and How

    13/51

    R12 Lessons learnedFinance / GLFinance / GLUser Interface - Very different look and feel . Similar toPeopleSoft. Will require more training and getting used to.Sub ledger Accounting (SLA) for Operating Unit flexibility

    removed and are now centralized.

    Multi-Org Access Control (MOAC) - Provides role based access to.

    access to multiple operating units

    Check out the critical reports early - Trial balances, sub ledger

    accoun ng, e c. are eren w e ou pu . anyreports no longer exist. New setups are needed in Sub LedgerAccounting (Open balance definitions) and some new templates

    13

  • 8/6/2019 Upgrade to R12 Why and How

    14/51

    R12 Lessons learnedAccounts PayableAccounts Payable

    .

    and feel for the workbench.iPayment functionality now included and affects vendorconsolidation for AP, CE, and Advanced AR

    iSupplier portal integration had been rough when product. , .Significant patching requirements early in releaseInformation expansion (TCA arch.) led to long upgradesteps and blown table extensions

    14

  • 8/6/2019 Upgrade to R12 Why and How

    15/51

    R12 Lessons learnedOracle Business Intelligence Enterprise EditionOracle Business Intelligence Enterprise Edition

    Web Server, Portal, Oracle Internet Directory (OID),Operating System .

    not implement.

    Confirm OBIEE hardware requirements . Requires singleinsta ation on a high-performance server

    Web ADIWeb ADI

    When moving from Desktop ADI to Web ADI, you lose theability to create financial statements in ADI

    15

  • 8/6/2019 Upgrade to R12 Why and How

    16/51

    Upgrade Flow Key stepStart theprocess

    Critical strategy andplanning stage occurs

    Evaluate newrelease

    Make

    ? Stay put

    Install newrelease

    Perform initialup rade pass

    Test / makeadjustments

    Yes

    Perform testmove to Prod.

    Test Acceptable

    No

    No

    Yes

    Schedule cutover date

    Final TestingReady ?YesGo

    Live

    Make finaladjustments

    No

    16

  • 8/6/2019 Upgrade to R12 Why and How

    17/51

  • 8/6/2019 Upgrade to R12 Why and How

    18/51

    How to Ensure Success - Build aRepeatable Process

    -

    Communicate Transparent reporting on Progress-

    Recruit - The Right Team Members-

    Analyze and Plan Use Iterative Method (3 rounds)Execute -A Serious and Dedicated Testin ProcessExperience - Have a leader , bring back the vets

    Ti - rchive work rom revious iterations

    18

  • 8/6/2019 Upgrade to R12 Why and How

    19/51

    Secure Executive SponsorshipWho is the 800 lb. Gorilla?

    -

    Support active is betterWhen ou reall have to have a decisionHelps control scope creep

    Does the project have legs?Is it aligned to the current business objectivesStrategic

    e urn n nves men

    19

  • 8/6/2019 Upgrade to R12 Why and How

    20/51

    Communication

    Have a comprehensive plan

    By what method / meansKnow our audience

    What are they interested in

    Share relevant knowledgeSet the tone

    Be transparent

    os veRecognize the valueFocus on what u rade will rovide to business

    20

  • 8/6/2019 Upgrade to R12 Why and How

    21/51

    Gather Proper MaterialsFrom Metalink:

    Release Content Documents for all Releases betweenwhere you are and where you want to be (for moduleleads only).Latest Im lementation uides for each module inproduction or moving to productionLatest User guides each module in Production or moving

    Secure Passwords and Access for whole teamE-Business Suite R12 Information Center

    - us ness u te pgra e u e eta n note461705.1

    21

  • 8/6/2019 Upgrade to R12 Why and How

    22/51

    Proper Materials (cont.)

    List of Customizations and ExtensionsInclude all re orts forms views extracts tri ers etc

    List of custom reports (in all forms)Interfacesor ow ccoun enera or e n ons

    Oracle supported extensionsAnything that touches Oracle that didnt come shippedfrom Oracle CorporationDisconnected Spreadsheet (for OIE)

    Be prepared for some unknown customizations

    22

  • 8/6/2019 Upgrade to R12 Why and How

    23/51

    Custom code change quagmire

    Oracles R12 Upgrade : Most code upgraded seamlessly,

    Custom Code Requiring Changes during :Forms : ~10% of forms and libraries needed touchingReports : ~1% of reports needed touchingC code : ~20% of C code needed touchingJava code : ~1% of overall Java code needed touchinJSPs : ~50% of JSPs needed touchingAutoConfig Configuration Customizations

    , . . ,JDev10.1.3

    Source: Ray Lin - Customer Service Support Manager : Oracle E-Business Suite

    23

  • 8/6/2019 Upgrade to R12 Why and How

    24/51

    Proper Materials Tools

    Library of Test CasesDetailed test scri ts

    Include and use cases from past 11i Implementation orupgrades

    functionality

    Modify test cases to reflect new or changed functionalityMake sure your test cases have specifics about test dataand expected resultsCheck them back in to the librar for next time

    24

  • 8/6/2019 Upgrade to R12 Why and How

    25/51

    Proper Materials - Hardware

    Hardware, Software, and Network , ,

    Cloning skillsScale-able instance strategyAdequate high speed storage / recovery capabilities

    Shared Project Folder or SpaceMac and PC if necessaryAbility for Oracle Support Access if Necessary (ODC orNet meetinAdequate network bandwidth / throughputRemote access via secure VPN

    25

  • 8/6/2019 Upgrade to R12 Why and How

    26/51

    Proper Materials Hardware (cont.)

    Definition of Current State of Production

    Browser VersionDatabaseApp server

    DiscovererSelf Service Framework Approvals Manager

    Version of ADIVersion on tools

    26

  • 8/6/2019 Upgrade to R12 Why and How

    27/51

    Extended Team - Responsibilities

    Management / Executive Sponsor

    Project Manager

    Business BusinessTechnical Lead Analyst Fin.

    AppsAnalyst SC &

    OtherTrainer

    ys.Admin

    eve operAnalyst

    us nessProcess Owners Super Users

    Help Desk / Network Support

    End Users / Testers

    27

  • 8/6/2019 Upgrade to R12 Why and How

    28/51

    Team Members and Skills - Technical

    DBA(s) and duties-,

    requisitesDevelop upgrade instance strategy / validate spaceCreate test environmentPerform initial timings for patch application

    Creation of Testing EnvironmentsIncremental Backu sProduction Cutover

    28

  • 8/6/2019 Upgrade to R12 Why and How

    29/51

    Team Members and Skills Tech (cont.)

    Technical lead

    Review architecture and Instance strategySchedule development work Assess technical training needs

    Developer AnalystsReview customizations, extensions, interfacesWork with functional resources to reconstruct necessary

    Modify / update /remove CEMLIsDevelop and test code

    29

  • 8/6/2019 Upgrade to R12 Why and How

    30/51

    Team Members and Skills Tech (cont.)

    Network Specialists- ,

    Push out new versions of any necessary client softwareParticipate in load testing sessionsProvide remote Access for non-employee personnel

    e p es ersonneAssist with Testing New Features

    Update Account and Description

    30

  • 8/6/2019 Upgrade to R12 Why and How

    31/51

  • 8/6/2019 Upgrade to R12 Why and How

    32/51

    Team Members and Skills Functional

    Super Users (Functional)Review RCDs for new features and chan es

    Review draft of Master Impact ListInput to and Execution of Test Cases and Test Scriptso o erson or now e ge o ew unc ona y

    Develop and Deploy New Features Training and

    DocumentationInteract with end users for module to gain understandingof issues and needs

    32

  • 8/6/2019 Upgrade to R12 Why and How

    33/51

    Team Members and Skills Functional

    Trainers

    develop new training materials covering new featuresUpdate training material for new usersDevelop training for new features

    Additional Optional ResourcesOracle Support RepresentativeInternal or Outside Consultants

    Tip Approach this like a cross functional project

    33

  • 8/6/2019 Upgrade to R12 Why and How

    34/51

    Documents

    Identify and Pull together key information

    Get prepared for your analysis

    34

  • 8/6/2019 Upgrade to R12 Why and How

    35/51

    Two Critical Documents

    Master Checklist Build a Master list for the upgrade

    TIP: Download Maintenance Wizard to a spreadsheet. Capture timings for pre, during, and post patching. LIST and Assign .

    Master Impact List Complete full listing of all

    or retestingDrives new features use and all testin

    Applies to standard Oracle features and Customer-created impacts

    35

  • 8/6/2019 Upgrade to R12 Why and How

    36/51

    Example of Master Impact List

    36

  • 8/6/2019 Upgrade to R12 Why and How

    37/51

    Master Impact List

    Some Examples:

    retested or replaced with XML / BI PublisherCustom Form may need to have customizationreapplied to standard Oracle form

    Account Generator changes might get overwritten, andit may be necessary to reapply changesNew Report available as standard functionality, we may

    Standard Interface may have new parameters, may needto resubmit for recurring submission (scheduling)

    37

  • 8/6/2019 Upgrade to R12 Why and How

    38/51

    Analyze and Plan Iterative Method

    Analyze, Plan, Estimate, Repeat

    Use as a Tool to Build your Project Plan

    38

  • 8/6/2019 Upgrade to R12 Why and How

    39/51

  • 8/6/2019 Upgrade to R12 Why and How

    40/51

    The Method First Iteration (cont.)

    DBA team creates the test environmentSet up R12 Vision Instance for functional sandboxRefine Master Checklist Timings for Pre-Requisite Steps DBA Portion

    DBA applies patches gather good timingestimates (challenge in test environment)Gather timing on additional patching, Gather

    Stat st cs, post patc ng, etc

    40

  • 8/6/2019 Upgrade to R12 Why and How

    41/51

  • 8/6/2019 Upgrade to R12 Why and How

    42/51

  • 8/6/2019 Upgrade to R12 Why and How

    43/51

    The Method First Iteration (cont.)

    Assign Technical Impacts to developer(s) toresearch as earl as ossible

    Interfaces, Extensions, etcResearch table and other changesGet estimate of rework time if necessaryRefer back to design documents

    nsure s s use , s a requ remenOptimizer Changes - Performance

    Assi n test cases to Testin team members forExecution Have test cases for all items on MasterImpact List

    43

  • 8/6/2019 Upgrade to R12 Why and How

    44/51

  • 8/6/2019 Upgrade to R12 Why and How

    45/51

    The Method (cont.)

    Cutover / War Room

    Update and File Library of Test Cases and

    Keep updated and available all Training- , ,

    Archive:Master Im act List

    Materials for next upgradeRedevelopment timings, etc

    45

  • 8/6/2019 Upgrade to R12 Why and How

    46/51

  • 8/6/2019 Upgrade to R12 Why and How

    47/51

  • 8/6/2019 Upgrade to R12 Why and How

    48/51

    Suggestions based on Experience (cont.)

    Re-Use of Team members speeds successive

    Concept of Upgrade Tiger teamPlan can be re-used

    Scrub Oracle Docs on New features before giving

    to End users make eas and less scarCommunicate the complexities to managementand team members each iteration

    Systems for managing testing provide value but

    48

  • 8/6/2019 Upgrade to R12 Why and How

    49/51

    For More Information

    Metalink

    http://www.oracle.com/appsnet/technology/ .

    Online Help (New Features Section)

    Blogs: Stephen Chan: http://blogs.oracle.com/schan/ se ups e e es

    49

    l k

  • 8/6/2019 Upgrade to R12 Why and How

    50/51

    Important R12 Metalink notes

    Recommended b COE:

    Article Plan note #Oracle E-Business Suite Upgrade Guide 461709.1

    Oracle Payables Release 12 Known Issues 405627.1

    R12 Proactive Intelligence Center: Oracle Payables 578232.1

    Other relavent Metalink recommandations:

    Oracle Applications Upgrade Guide: Release 11i to Release 12 B31566-01

    Oracle Applications Documentation Resources, Release 12 394692.1Oracle Applications Release 12 Upgrade Sizing and Best Practices 399362.1

    50

    Slid A il bl

  • 8/6/2019 Upgrade to R12 Why and How

    51/51

    Slides Available

    O2Works Knowledge Base:www.o2works.com

    Thank youThank you

    Consulting Director214-725-2828

    .

    O2Works LLCDallas Chicago - Denver

    51