Tips on the Oracle EBS R12 Upgrade Dilemma

on Thursday, 03 April 2014. Posted in Enterprise Software , Business Analysis, Blog

Tips on the Oracle EBS R12 Upgrade Dilemma

If taking away choices is a bad thing, then giving more choices must be good, right? Not necessarily for all Oracle clients. Too many choices can overwhelm a company. I think Oracle`s strategy is a fair one provide customers with a wide selection of products of a certain type to increase customer satisfaction and meet their unique requirements. After all, we all do it at the supermarket, when they provide us 20 different brands of toast, we are more likely to find a brand that suits our taste and meets our families’ requirements.

Any EBS upgrade is a nerve-racking situation for any entity. Let`s go directly into the subject. Before you begin your upgrade follow these 5 steps:

1. Ask what you are looking to really achieve with the upgrade if you keep your options as open as possible.

By doing this, you can see that the time and stress invested to keep a wide range of choice isn’t likely to outweigh the benefit of possibly just saving a few dollars upgrade or re-implement R12. Do a full analysis conventional upgrade or re-Implementation of R12.

2. Once you’ve made your decision, stick with it.

Don’t allow yourself a “safety net” of being able to take it back or swap just because you’ve changed your mind. Know that this is the right choice for your organization, right now. Stick with your decision all 3 Oracle versions are valid – The decision has No wrong answer. Stop talking and execute Oracle will support you with any of the 3 versions you select.

3. Forget about the other “EBS versions”.

They’re will always be someone that will question or doubt that decision, don’t dwell on how wonderful the things may have been if you selected the other version. Move ahead, many companies i see spend lots of time and money on this point Don’t.

4. Ask: do you really need it anyway?

If you already own several pairs of boots, how will another pair affect your happiness? Focus on what value the upgraded EBS version provides to your company, rather than just upgrading because of Oracle`s roadmap.

5. Trust yourself.

You know what you really need, and what is right for you. Be happy with your choice when you’ve made it, and know that your company will not cease to exist if, by the slightest chance, this was the wrong choice.

When looking to upgrade your EBS release below is the timeframe with the support policies for 11.5 and 12.1

 timeline

For people that are not familiar with Oracle support policies, Each new version of EBS when launched the first 5 years is called premier and support costs are defined when software is purchased, the next 3 years are named Extended and an extra support cost is usually added.

For example EBS 12.2 that was released GA (General availability) in 2013, premier support ends in 2018.

Decision process for the R12 EBS Upgrade

Lets go to the heart of the question upgrade to which version, Here are my thoughts on the topic:

Upgrading to Release 12.1.3 : This EBS version is currently used by thousands of customers and will provide you the least surprises. The upgrade path is well known and provides the least risk, also if your only requirement is to upgrade for the cheapest short term cost and no new functionality is required for your organization 12.1.3 is your best bet. Currently the majority of EBS customers are on this version and you should be good for the next 4 years.

Upgrading to Release 12.2.2 : Requires to upgrade to 12.2 and then install the 12.2.2 release pack , this version includes lots of new features Online patching which allows the E-Business Suite to be updated while the system is still running and users entering transactions, but lots of new feature here is the link to all new business and technical features : E-Business Suite 12.2 Release Content Document (Note 1302189.1)

Upgrading to Release 12.2.3 : Requires to upgrade to EBS 12.2 and then to install the 12.2.3 release pack, one of the many features of 12.2.3 is to be able to change the new-look and feel of the user interface by changing the below profile :

Screenshot of the profile option that you need to change

 look and feel profile

One of the multiple look and feels available within R12.2.3

screenshot of new UI

For a full complete list of 12.2.3 features, it can be found at the following hyperlink Oracle E-Business Suite Product Specific Release Notes, Release 12.2.3 (Doc ID 1605928.1)

To conclude, my opinion upgrading to the latest version minus 1 is always the safest upgrade. If you think about it most bugs get resolved in the next version following the one the bug was identified.

Like usual share your thoughts & the approach that is or was followed at your company.

 

Comments (17)

  • Lisa Gordon

    Lisa Gordon

    03 April 2014 at 12:47 |
    Nice analysis, we performed an upgrade to 12.1.3 we are a conservative UK manufacturing company
  • Marc Lawson

    Marc Lawson

    03 April 2014 at 14:27 |
    Alex, we went live in March with EBS 12.2.2, our important requirement was to reduce downtime, things went well we had some hiccups in production with some of our European units. Overall Oracle was great and fixing these bugs. Solid blog!
  • Mustaquim Chowduhry

    Mustaquim Chowduhry

    03 April 2014 at 14:57 |
    We are in the middle of the R12 upgrade, we are planning to go-live in May, we selected 12.1.3. we felt like you mentioned 12.2 is pretty new but with nice features , I work for an organization that is risk averse.
  • Nathan Wong

    Nathan Wong

    03 April 2014 at 15:20 |
    Alex, we upgraded to 12.1.3 went live in December 2013, on a side note will you be going to OpenWorld this year in SF, our company this year will be sending 5 people to the conference, we can schedule a meeting to discuss our enterprise initiatives.
    • Alex Antonatos

      Alex Antonatos

      03 April 2014 at 15:42 |
      Hi Nathan,
      Thank you for sharing, 12.1.3 has the lion share of number of EBS R12 instances, I go to OpenWorld in SF every year, and yes will gladly meetup with you and your colleagues. Send me an email or call me and we can arrange a Video Skype early next week to discuss.
      Kind regards,
  • Monica Hernandez

    Monica Hernandez

    03 April 2014 at 16:17 |
    Alex, this post is great. I really like the way you blog by asking questions, the posts engage others and the site is from a person, with a photo, with a name, and a Reply button. We are mainly in Mexico and South America, we are upgrading in June to 12.2.2, it is going well, we are completing our second mock, we had Oracle Development involved to resolve some legislation issues we encountered on the first Mock with the Project costing and billing modules, overall the project and user experience is positive.
  • Justin Bowers

    Justin Bowers

    03 April 2014 at 18:49 |
    We went with 12.1.3, experience was positive, no major issues reported.
    I would emphasize take your decision quickly, we spend lots of time on analyzing each version.
  • Victor Nguyen

    Victor Nguyen

    03 April 2014 at 19:03 |
    We went with the latest version 12.2.3, it was a roller coaster experience, currently we have stabilized our environment, during testing we got different snags mostly on HCM functionalities/Legislations with EB tax, and overall EBS performance issues. We persevered and know quite happy with the move, 12.2.3 is not for the faint of heart. We had many evening discussions with Oracle development and support.
  • Maureen Wilson

    Maureen Wilson

    03 April 2014 at 20:30 |
    we just started the analysis of the 11.5.10 upgrade in March and we are looking to upgrade to 12.1.3 , main reason we have a good support network in Australia and path is well documented.
  • Subroto Singh

    Subroto Singh

    03 April 2014 at 22:44 |
    We just completed our upgrade to 12.1.3 went well, no major issues to report, most of our issues were resolved quickly. Oracle support was great!
  • Marc Powers

    Marc Powers

    04 April 2014 at 09:21 |
    12.1.3 in December, our company was not ready to take the risk to be on the latest version. Oracle support was quick to resolve issues.
  • Vijay Patel

    Vijay Patel

    04 April 2014 at 18:51 |
    We went live with 12.2.2 , as a single instance, we had no choice as we have one global instance in production implemented in different timezones the online patching was a must. During testing we encountered some errors, we had a hard time troubleshooting since the documentation was not that complete but Oracle support was always able to help us. The first week after go-live we had performance issues for the first week Oracle development was able to find the issues. Overall it was a roller coaster ride but we are happy with the outcome. By the way great blog!
  • John Hiroto

    John Hiroto

    04 April 2014 at 19:23 |
    Thanks Alex ! Great pointers and definitely something to think about, we went with 12.1.3, our main criterias were reliability and to minimize risk.
  • Antonio Garcia

    Antonio Garcia

    04 April 2014 at 20:43 |
    We went with 12.2.2 version, but we are small company with only 50 financial's users, we think the big jump is better, in past we move from 11.5.2 to 11.5.10.2.
  • Marlene

    Marlene

    05 April 2014 at 04:32 |
    Our upgrade to 12.1.3 was pretty smooth. our strategy was to quickly create the upgrade recipe and test,test,test. We are 6 months in production and the instance is quite stable.
  • Vinh Lam Sam

    Vinh Lam Sam

    05 April 2014 at 14:11 |
    We selected 12.1.3 to mitigate risk.
  • Michael Li

    Michael Li

    05 April 2014 at 20:27 |
    We are in the middle of an upgrade to 12.2.2. Going well we had issues with legislation and data bugs but they are being corrected, the only thing not too many clients on this version and issues are taking longer to resolve as compared to 11.5.10.2.

Copyright 2014 Appsconsultant.com. All rights reserved.