Oracle 11i Sustaining Support

Start Here

Get in touch with a
TriCore Solutions specialist

Blog | May 18, 2014

Oracle 11i Sustaining Support



For those companies still on Oracle eBusiness Suite 11i, time is running out to make a move to Release 12.   

 

Introduction:

For those companies still on Oracle eBusiness Suite 11i, time is running out to make a move to ReleaseOracle_R12_upgrade 12. Oracle gave companies a reprieve back at the Open World conference in October 2013 and adjusted their support model for 11.5.10.  The “Sustaining Support Exception” offering was introduced and provided a temporary service level which enabled customers to continue with their “Extended” support through December 2015.  With less than 20 months remaining, companies need to be making the move to R12 or calculating the risks associated with staying on “Sustaining” 11i support.

For companies contemplating remaining on the Sustaining Support option after December 2015, understanding what will be lost is key:

  •   New fixes for Severity 1 production issues,
  •   Critical Patch Updates (CPUs), up to and including the October 2015 CPU,
  •   United States Form 1099 2013 and 2014 year-end updates, and
  •   Payroll regulatory updates for the United States, Canada, United Kingdom, and Australia for each country’s fiscal year ending in 2014.

In summary, after December 2015 all 11.5.10 clients will be moved to the “Sustaining Support” level, offering access to the existing “Knowledge Base,” technical support, and the new releases, only – No fixes.

Here at TriCore we understand that some companies may continue to thrive for an extended time through the Sustaining support policy – These companies have typically made minimal updates to the environment, and are therefore comfortable living with any issues or problems that arise/ the risk of being on their own for production or security issues.


The concern for some companies, however, is that they have become accustomed to the stability and functionality of Oracle’s 11.5.10 Release.  The thought of paying to upgrade and the uncertainty of issues in the next release are keeping them from making the move, despite the opportunity the R12 upgrade presents to align the attention and focus of business and technology staff toward common goals.

When considering moving to a new Oracle release, several primary decisions and activities will determine the cost and effort for the transition.  The Upgrade versus Reimplementation option becomes the first directional question to be answered.   Oracle provides the “Upgrade” process as the standard approach for moving to a new release.  For 11.5.10 to R12 upgrade, Oracle has done a tremendous job with these upgrade scripts.  Our experience has been very positive with moving the data and implementing the new functionality with relative ease.

Re-implementation provides a second option for clients to move to the latest release.  Modifying your Chart of Accounts, General Ledger String structure, calendars or cost methods are the difficult configuration changes in Oracle EBS and the primary reason companies choose the more flexible Re-Implementation alternative. Replacing a heavily customized environment with new standard functionality or correcting data quality issues are two other common driving factors toward re-implementing over the upgrade process.

Regardless of the approach, companies looking to make the move can and should begin the process by evaluating a few options that will drive the effort and duration of the project.

  • Review the R12 functionality to determine which functionality you are interested in implementing.
  • Evaluate the current customizations to specify which ones are to be converted to R12, replaced with new functionality, or simply dropped as no longer needed.
  • Identify existing pain points in your current business processes that should be reviewed as part of your R12 effort.
  • Assess your hardware situation to determine if a database, OS and/or hardware update should be included with the software upgrade.
  • Determine your staff capabilities and capacity to handle the combined load of your R12 initiative along with their daily activities.
  • Outline your blackout dates for system changes to your production environment

By analyzing these areas, companies can develop the detailed plan to successfully move to Release 12. 

With a typical upgrade or re-implementation project taking six (6) to twelve (12) months, the remaining 20 months to “Sustaining” 11i support is quickly dwindling.  So as we teach our kids, a “No Decision” is actually a decision.  It’s important to make your 11i decisions informatively.


About TriCore Solutions
TriCore Solutions, the application management experts, provides a full suite of scalable and reliable managed application, cloud, infrastructure hosting, and consulting services to enterprise organizations. The company delivers its services and the TriCore Trusted Promise to more than 250 companies worldwide to reduce costs, raise service levels, improve customer experience, increase business agility, and accelerate innovation, unlocking the business value from their IT investments. TriCore Solutions is headquartered in Boston, MA, with offices in India and throughout North America.