Wednesday Apr 20, 2016

Microsoft Ending Support for Vista in April 2017

Vista logoMicrosoft is ending support for Windows Vista on April 11, 2017.  The official support dates are published here:

Windows Vista is certified for desktop clients accessing the E-Business Suite today.  Our general policy is that we support certified third-party products as long as the third-party vendor supports them.  When the third-party vendor retires a product, we consider that to be an historical certification for EBS.

What can EBS customers expect after April 2017?

After Microsoft desupports Vista in April 2017:

  • Oracle Support will continue to assist, where possible, in investigating issues that involve Windows Vista.
  • Oracle's ability to assist may be limited due to limited access to PCs running Windows Vista.
  • Oracle will continue to provide access to existing EBS patches for Windows Vista.
  • Oracle will provide new EBS patches only for issues that can be reproduced on later operating system configurations that Microsoft is actively supporting (e.g. Windows 7, Windows 10)

What should EBS customers do?

Oracle strongly recommends that E-Business Suite customers upgrade their desktops from Windows Vista to the latest certified equivalents.  As of today, those are Windows 7, 8.1, and 10

Related Articles

Tuesday Jan 05, 2016

2015 in Review: 13 Things That You Must Upgrade Now

2015 was a busy year for E-Business Suite system administrators.  The following things are now considered to be out of Error Correction Support by Oracle or their respective vendors:

Database Tier

  1. Database 10g Release 2 (ended July 2015)
  2. Database 11g Release 1 (ended August 2015)
  3. Database 12.1.0.1 Patchset (ended July 2015)
  4. Database 11.2.0.3 Patchset (ended August 2015)

Application Tier

  1. Oracle Access Manager / Oracle Internet Directory 11.1.1.5 (ended June 2015)
  2. SHA-1 PKI certificates
  3. Secure Socket Layer (SSL)
Client Tier
  1. Internet Explorer (IE) 6, 7, 8, 9, 10 (ended January 2016)
  2. All JRE releases older than 1.6.0_105, 1.7.0_91, and 1.8.0_66

EBS Releases

  1. EBS 11i (Exception to Sustaining Support ended December 2015)
  2. EBS 12.0 (ended January 2015)
  3. EBS 12.1 Recommended Patch Collection 3
  4. EBS 12.2.2 Release Update Pack

What you should do

If you are running any of the things above in your EBS environments, you should click on the respective links to get guidance on your upgrade options. Oracle strongly recommends that you stay on a current product release that gets updates.

If you're confused by the continued listing of a particular combination in Oracle's Certification database after the product release's end of life, see:

Related Articles

Tuesday Dec 15, 2015

Reminder: Error Correction Support Ended for Database 11.2.0.3

E-Business Suite customers must ensure that their database remains on a level that is covered by Error Correction Support (ECS) -- i.e. while you can get new patches, Critical Patch Updates (CPU), and Patch Set Updates (PSU).  We've covered this in detail here:

The following Note lists Error Correction Support dates for all database patchsets for all database releases:

That Note shows that patching ended for the 11.2.0.3 Database patchset on August 27, 2015

All EBS customers should upgrade to a later patchset or database release.  As of today, options include upgrading to the 11.2.0.4 patchset or Database 12c 12.1.0.2.

Related Articles

Wednesday Dec 09, 2015

Reminder: EBS 11i Reverts to Sustaining Support on January 1, 2016

E-Business Suite 11.5.10.2 has been in Sustaining Support since December 1, 2013.  We have offered a one-time Exception to Sustaining Support (covering only Severity 1 issues) until December 31, 2015. 

This means that we will revert to Sustaining Support for Oracle E-Business Suite 11i 11.5.10.2 on January 1, 2016.  See:

Updated EBS Support timelines

EBS 11i users should upgrade to EBS 12.2 as soon as possible.

What happens after Extended Support ends?

The Exception to Sustaining Support coverage ends and we revert to the normal mode of Sustaining Support on January 1, 2016.  You can request diagnostic assistance for EBS 11i issues and download existing patches and documentation. Sustaining Support does not include:

  • New updates, fixes, security alerts, data fixes, and critical patch updates
  • New tax, legal, and regulatory updates
  • New upgrade scripts
  • Certification with new third-party products/versions
  • Certification with new Oracle products

For more specifics on Premier Support, Extended Support, and Sustaining Support, see:

Implications for EBS 11i users

You may need to freeze your desktop and server configurations while you upgrade to EBS 12.2. 

New versions of desktop components may not work with EBS 11i. These include new releases of:

  • Windows
  • Mac OS X
  • Internet Explorer (IE)
  • Firefox
  • Safari
  • Office
  • Desktop-based Java Runtime Environment (JRE)  

New versions of server-based components may not work with EBS 11i. 

These include new releases of:

  • Server-based operating systems (Linux, AIX, HP-UX, Solaris, etc.)
  • Oracle Database
  • Java JDK
  • Fusion Middleware components (Oracle HTTP Server, JServ, Forms, etc.)

Related Articles

Friday Dec 04, 2015

Reminder: Upgrade to IE 11 Before January 12, 2016

Microsoft IE LogoMicrosoft has published this reminder to all customers:

Beginning January 12, 2016, only the most current version of Internet Explorer available for a supported operating system will receive technical supports (sic) and security updates. Internet Explorer 11 is the last version of Internet Explorer, and will continue to receive security updates, compatibility fixes, and technical support on Windows 7, Windows 8.1, and Windows 10.

What does this mean for EBS users?

This notice applies to all Oracle E-Business Suite users.  After January 12, 2016, Oracle will no longer certify older versions of IE with any updates to Oracle E-Business Suite, including EBS releases 11i, 12.0, 12.1, and 12.2.

All EBS customers must follow Microsoft's guidance and upgrade to IE 11. See:

What are the EBS support implications of staying on an older IE version?

You will continue to have access to existing EBS patches and documentation for older IE releases via My Oracle Support.

Oracle may attempt to assist with questions about older IE releases.  Oracle's ability to assist may be limited by lack of access to desktops running those older releases.

Oracle will issue new patches only for issues that can be reproduced on IE 11.

References

Related Articles

Tuesday Sep 22, 2015

EBS Support Policy for Third-Party Client Components

End-users connect to the Oracle E-Business Suite using a variety of clients: desktops, laptops, and mobile devices.  Those clients run third-party operating systems (Microsoft Windows, Mac OS X, Apple iOS, Android) and third-party products (Microsoft Office, Internet Explorer, Mozilla Firefox, Safari, and Chrome).

What happens when you have client-related issues?  What are our support policies when issues involve third-party components as well as Oracle components?

EBS components affected by third-party client products

A number of E-Business Suite components or products are affected by third-party client components.  These include:

  • OA Framework (OAF: the user interface infrastructure that underlies most HTML/web-based self-service EBS products)
  • Oracle CRM Technology Foundation (JTT: the infrastructure that underlies EBS CRM products such as Sales, Marketing, Service, eCommerce, Contracts, and Interaction Center)
  • Oracle Forms (Forms-based EBS products running in Java)
  • Web Application Desktop Integrator (Web ADI: provides integrations with Microsoft Office products such as Excel)
  • Report Manager

Support options partly depend upon the third-party

Our support policy for EBS client issues depends upon whether those third-party operating systems and products are supported by the third-party vendor.

You can search Microsoft, Apple, Mozilla, and Google websites for support timelines for their products.

How to interpret this information 

We provide updates to the E-Business Suite when both of the following are true:

  1. The E-Business Suite release is eligible for Error Correction Support
  2. The third-party operating system or product is actively supported by the third-party

If a reported issue is isolated to the third-party component, Oracle will attempt to issue a fix or find a workaround.  Oracle may not be able to provide fixes for all reported issues.  For example, if a browser vendor changes their browser's behavior or chooses to remove a particular feature, customers may need to contact that vendor directly.  

It is important to keep track of support dates for third-party products.  We do not provide new EBS patches, certifications, and documentation updates for combinations that involve obsolete third-party products.

Example 1: Windows version obsoleted by Microsoft
  • It is September 1, 2015
  • You see a listing in the Certifications system for EBS 12.1.3 + IE 6 on Windows XP
  • Error Correction Support for EBS 12.1.3 continues to December 2019
  • Microsoft supports IE 6 as part of its Windows XP policy
  • Microsoft desupported Windows XP in April 2014
  • You cannot request new patches for this combination

Example 2: Office version obsoleted by Microsoft

  • It is September 1, 2015
  • You see a listing in the Certifications system for EBS 12.1.3 + Microsoft Office 2003
  • Error Correction Support for EBS 12.1.3 continues to December 2019
  • Microsoft desupported Office 2003 in April 2014
  • You cannot request new patches for this combination

Example 3: Firefox version obsoleted by Mozilla

  • It is September 1, 2015
  • You see a listing in the Certifications system for EBS 12.1.3 + Mozilla Firefox ESR 31
  • Error Correction Support for EBS 12.1.3 continues to December 2019
  • Mozilla desupported ESR 31 in August 2015
  • You cannot request new patches for this combination

Example 4: Chrome version obsoleted by Google

  • It is September 1, 2015
  • You see a listing in the Certifications system for EBS 12.1.3 + Google Chrome 35
  • Error Correction Support for EBS 12.1.3 continues to December 2019
  • The latest Chrome release available is 45
  • Google only supports the latest Chrome release
  • You cannot request new patches for this combination

Still confused?

If you're still having trouble, log a Service Request with Oracle Support.  A Support Engineer can help with these types of questions.

Related Articles

Thursday Sep 03, 2015

Are AMP Support Dates Based on EBS or EM Releases?

Guest Author: Angelo Rosado, AMP Product Management 

The Application Management Pack (AMP) for Oracle E-Business Suite is an Enterprise Manager (EM) plug-in.  What are the support dates for AMP?  Are they based upon EBS support dates, EM support dates, or the release dates of the AMP releases themselves?

AMP inherits EM support dates

Application Management Pack generally follows the support policy of the base release of Oracle Enterprise Manager upon which it is built. See:

Our recommendations

We strongly recommend that you stay current on the latest releases of Oracle Enterprise Manager and Application Management Pack.  The current release of Application Management Pack is 12.1.0.4.0.

Make sure you check the requirements for the version of Oracle Enterprise Manager that you're using. See section 6.2, "Before You Begin Installing an Enterprise Manager System" here:

Related Articles

Friday Aug 28, 2015

"Certified" vs. "Error Correction Support": What's the Difference?

We've recently gotten a string of questions about the support status of obsolete products listed in the Certifications system on My Oracle Support.  This is really important: everyone working with Oracle products should know how to determine the support status of their products.

The existence of a listing in the Certifications system doesn't necessarily mean that a product release is covered by Error Correction Support. 

To determine the support status of a particular combination:

  1. Check if the combination is listed in the Certifications system
  2. Check the support status of the product releases
  3. Check the support status of the product patch sets
  4. Interpret this information
Let's walk through these steps in more detail.

Understanding the three phases of support

We produce new patches and certifications for Oracle products while they are covered by either Premier or Extended Support.  Those two support phases are collectively known as the Error Correction Support period. 

After that period, products are covered by Sustaining Support.  You can download existing patches and documentation for products in Sustaining Support.  You cannot request new patches or certifications for these products.

See the Oracle Lifetime Support Policy site for more details about Premier, Extended, and Sustaining Support levels.

Step 1. Check if the combination is listed in the Certifications system

The Certifications system on My Oracle Support lists all of the combinations that we've tested for the E-Business Suite. Certifications are generally retained for reference purposes after the Error Correction Support phase has ended for those products. The existence of an historical listing in the Certifications system doesn't necessarily mean that that is still covered by Error Correction Support.

For example, the Certifications system includes historical listings for:

  • EBS 11.5.3 (Error Correction Support ended July 2006)
  • EBS 12.0.6 (Error Correction Support ended January 2015)
  • Oracle Single Sign-On 10.1.2.0.2 (Error Correction Support ended December 2011)
  • Oracle Database 8.1.7.4 (Error Correction Support ended December 2006)

You cannot request new patches or certifications for any products after their Error Correction Support ends.

Step 2: Check the support status of a product release

A product release is the major version.  For example, Database 11gR2 is the product release.

Database Lifetime Support dates table

You should always check the Oracle Lifetime Support documents for a product release's Premier and Support dates to determine whether the release is covered by Error Correction Support. 

See:

Step 3: Check the the support status of a product patch set

Product releases have patch sets. For example: the Database 11gR2 release has 11.2.0.3 and 11.2.0.4 patch sets.

Individual patch sets have their own Error Correction Support dates. You should always check the following documents for the support status of a given patch set:

Step 4: Interpret this information 

You can ask for new patches for a given combination only if all products within that combination are still covered by Error Correction Support. 

Example 1:

  • It is August 1, 2015.
  • You see a listing in the Certifications system for EBS 12.0.6 + Database 11.2.0.4
  • Error Correction Support for E-Business Suite 12.0.6 ended January 2015
  • Error Correction Support for Database 11.2.0.4 continues to January 2018
  • You cannot request new patches for this combination

Example 2:

  • It is August 1, 2015
  • You see a listing in the Certifications system for EBS 12.1.3 + Oracle Access Manager 10.1.4.3
  • Error Correction Support for EBS 12.1.3 continues to December 2019
  • Error Correction Support for Oracle Access Manager 10.1.4.3 ended December 2011
  • You cannot request new patches for this combination

Example 3:

  • It is August 1, 2015
  • You see a listing in the Certifications system for EBS 12.1.3 + Oracle Database 11.2.0.2
  • Error Correction Support for EBS 12.1.3 continues to December 2019
  • Error Correction Support for Database 11.2.0.2 ended October 2013
  • You cannot request new patches for this combination

Still confused?

If you're still having trouble, log a Service Request with Oracle Support.  A Support Engineer can help with these types of questions.

Related Articles

Monday Apr 06, 2015

Reminder: Upgrade EBS 12.2 to FMW 11.1.1.7

Oracle periodically produces Fusion Middleware patchsets -- cumulative collections of fixes -- between major product releases.  All Oracle customers have 24 months to upgrade from the prior patchset when a later patchset is released.  This is called the "grace period."  You cannot request new patches for the prior patchset after the grace period ends.

Where are Fusion Middleware grace periods documented?

The specific grace periods for upgrading from one Fusion Middleware patchset to another are published here:

Do these apply to EBS customers?

Yes.  These dates apply to all Oracle customers, including E-Business Suite customers.  

Which EBS releases are affected?

E-Business Suite 12.2 originally included Fusion Middleware 11.1.1.6 as part of its Rapid Install. Specifically, The Oracle E-Business Suite Release 12.2's Rapid Install delivers three Fusion Middleware (FMW) components:

  1. Oracle WebLogic Server 10.3.6 (this is the "$FMW_HOME") 
  2. Oracle WebTier Utilities 11.1.1.6
  3. Oracle Common Home (Part of Oracle WebTier Utilities 11.1.1.6)

According to the Note above, new patches were released for FMW 11.1.1.6 until April 30, 2014. EBS customers can still download existing patches produced for FMW 11.1.1.6, but no new patches for FMW 11.1.1.6 are being produced now.

What is the impact on EBS 12.2 customers?

EBS 12.2 customers who need new patches for their FMW components must to be on FMW 11.1.1.7. The Oracle WebTier Utilities and the Oracle Common Home should be upgraded by EBS sysadmins to get the latest updates for security, performance, and stability. 

Where can I get these updates?

You can download the latest update for these two components here: 

Here are instructions on how to apply this update to your EBS 12.2 environment:

Related Articles

Thursday Feb 26, 2015

Reminder: Upgrade Database 12.1.0.1 to 12.1.0.2 by July 2015

E-Business Suite customers must ensure that their database remains on a level that is covered by Error Correction Support (ECS) -- i.e. while you can get new patches, Critical Patch Updates (CPU), and Patch Set Updates (PSU).  We've covered this in detail here:

The following Note lists Error Correction Support dates for all database patchsets for all database releases:

That Note shows that patching ends for the 12.1.0.1 Database patchset on July 22, 2015. All EBS customers on Database 12.1.0.1 should upgrade to the Database 12c 12.1.0.2 patchset before then. 

Related Articles

Tuesday Feb 24, 2015

How To Be Notified When MOS Notes Are Updated

We update our My Oracle Support (MOS) Notes regularly.  How do you find out when a new note is published or an existing one is updated?

There is a new MOS feature -- Hot Topics -- which emails you when notes on your Favorites list are updated.

Here's what to do:

  1. Mark the document of interest as a Favorite (by clicking the yellow star to the left of the document title). 
  2. From the More dropdown, choose Settings.
  3. On the left, under Personalization, choose Hot Topics E-Mail.
  4. Select the options that meet your requirements.
  5. Click the Apply button to save your changes.

Hot Topics

In this example, I am requesting a daily email (in HTML format) listing any notes on my Favorites list that have been updated since the last email was sent. An email will only be sent if at least one note has changed.

You can also specify products if you want to be notified of updates to any notes in a specific  product area.

Notifications of New Notes

Although this mechanism does not tell you when new Oracle E-Business Suite technology stack notes are published, you can find out by adding the technology stack roadmap notes as MOS Favorites and consequently receiving notification emails when they are updated:

This example screenshot shows content from a Hot Topics notification email advising me that these two roadmap notes (as well as a couple of other important notes) have been updated:


Typically, the roadmap notes are updated to reflect the addition of a new note that supports a new or modified feature or component. A look at the latest (topmost) entry in the change log of the roadmap will quickly tell you what's new. And if the new note is relevant, you can then add it to your Favorites and be notified when it changes.

We also recommend that you review the notes currently listed in the roadmaps, and mark as Favorites any that are relevant to the technologies you are using in your Oracle E-Business Suite installation.

References

  • My Oracle Support Help - Hot Topics E-Mail instructions
  • How to use Hot Topics Email notification to subscribe to Support Product News, SRs, Bugs, etc. and events so that you Never Miss an Important Update (Doc ID 793436.2)

Related Articles

Friday Feb 13, 2015

Reminder: EBS 11i Reverts to Sustaining Support on January 1, 2016

E-Business Suite 11.5.10.2 has been in Sustaining Support since December 1, 2013.  We have offered a one-time Exception to Sustaining Support (covering only Severity 1 issues) until December 31, 2015. 

This means that we will revert to Sustaining Support for Oracle E-Business Suite 11i 11.5.10.2 on January 1, 2016.  See:


EBS 11i users should upgrade to EBS 12.1 or 12.2 as soon as possible. You might find this article useful:

What happens after Extended Support ends?

The Exception to Sustaining Support coverage ends and we revert to the normal mode of Sustaining Support on January 1, 2016.  You can request diagnostic assistance for EBS 11i issues and download existing patches and documentation. Sustaining Support does not include:

  • New updates, fixes, security alerts, data fixes, and critical patch updates
  • New tax, legal, and regulatory updates
  • New upgrade scripts
  • Certification with new third-party products/versions
  • Certification with new Oracle products

For more specifics on Premier Support, Extended Support, and Sustaining Support, see:

Implications for EBS 11i users

You may need to freeze your desktop and server configurations while you upgrade to EBS 12.1 or 12.2. 

New versions of desktop components may not work with EBS 11i. These include new releases of:

  • Windows
  • Mac OS X
  • Internet Explorer (IE)
  • Firefox
  • Safari
  • Office
  • Desktop-based Java Runtime Environment (JRE)  

New versions of server-based components may not work with EBS 11i. 

These include new releases of:

  • Server-based operating systems (Linux, AIX, HP-UX, Solaris, etc.)
  • Oracle Database
  • Java JDK
  • Fusion Middleware components (Oracle HTTP Server, JServ, Forms, etc.)

Related Articles

Thursday Feb 05, 2015

Reminder: Upgrade Database 10.2.0.5 Before July 2015

[Aug. 11, 2015 update: corrected reference to incorrect database patchset]

E-Business Suite customers must ensure that their database remains on a level that is covered by Error Correction Support (ECS) -- i.e. while you can get new patches, Critical Patch Updates (CPU), and Patch Set Updates (PSU).  We've covered this in detail here:

The following Note lists Error Correction Support dates for all database patchsets for all database releases:

That Note shows that patching ends for the 10.2.0.5 on July 31, 2015. There is additional fine print for Severity 1 fixes and other platforms -- see the Note for details.

All EBS customers should upgrade to a later patchset or database release before then.  As of today, options include upgrading to the 11.2.0.4 patchset or Database 12c 12.1.0.2.

Related Articles


Reminder: Upgrade Database 11.1.0.7 Before August 2015

E-Business Suite customers must ensure that their database remains on a level that is covered by Error Correction Support (ECS) -- i.e. while you can get new patches, Critical Patch Updates (CPU), and Patch Set Updates (PSU).  We've covered this in detail here:

The following Note lists Error Correction Support dates for all database patchsets for all database releases:

That Note shows that patching ends for the 11.1.0.7 Database patchset on August 31, 2015. There is additional fine print for Severity 1 fixes and other platforms -- see the Note for details.

All EBS customers should upgrade to a later patchset or database release before then.  As of today, options include upgrading to the 11.2.0.4 patchset or Database 12c 12.1.0.2.

Related Articles


Reminder: Upgrade Database 11.2.0.3 Before August 2015

E-Business Suite customers must ensure that their database remains on a level that is covered by Error Correction Support (ECS) -- i.e. while you can get new patches, Critical Patch Updates (CPU), and Patch Set Updates (PSU).  We've covered this in detail here:

The following Note lists Error Correction Support dates for all database patchsets for all database releases:

That Note shows that patching ends for the 11.2.0.3 Database patchset on August 27, 2015

All EBS customers should upgrade to a later patchset or database release before then.  As of today, options include upgrading to the 11.2.0.4 patchset or Database 12c 12.1.0.2.

Related Articles


Tuesday Jan 21, 2014

Support Implications for Your EBS Customizations

I've published this guidance in various articles before but it never hurts to consolidate it here for new readers.

You may choose to:

  • Modify or extend the E-Business Suite code that we ship
  • Add new database objects or modify existing database objects that we ship
  • Modify our standard EBS database partitioning schemes or add your own custom partitions
  • Introduce various forms of third-party virtualization technologies for any of the E-Business Suite's three tiers -- the database tier, the application server tier, or the desktop tier
  • Use third-party tools to modify your database directly
  • Integrate third-party software with your EBS environment, say, for reporting purposes, or to obtain additional industry-specific functionality
  • Use third-party tools to manage or configure your EBS environment
  • Run EBS on a third-party file system
Oracle generally considers all of these types of activities to be some form of customization.  This is not a complete list. Generally speaking, if you have introduced something into your environment that we haven't tested, we cannot take responsibility for it, so we consider it to be a customization.

Where these activities fall on a risk spectrum depends on their invasiveness.  The more invasive a customization is, the greater its potential risk.  Oracle generally recommends against invasive customizations.

Oracle's official policy on handling customizations is detailed here:

The support implications boil down to this:

  • Issues that are isolated to the E-Business Suite will be investigated by E-Business Suite Development.
  • Issues that are isolated to your customizations or third-party tools should be directed to the third-party vendor.
  • E-Business Suite Development will provide E-Business Suite Development patches for issues that can be reproduced in environments built using E-Business Suite documented procedures and tools.
  • If the third-party vendor cannot resolve issues isolated to their tools, you should restore from a backup and revert to using Oracle’s documented tools and procedures.

Related Articles

Wednesday Dec 11, 2013

New IBM AIX on Power OS and Tools Requirements for EBS 12

IBM logoBeginning on February 16th 2014, Oracle E-Business Suite patches for Release 12 (12.0, 12.1, 12.2) on the IBM AIX on Power Systems platform will be built with a newer version of the IBM XL C/C++ compiler (version 11). Customers who plan to patch or upgrade their E-Business Suite environments after February 16th 2014 must meet all the new requirements prior to applying new patches generated after this date.

IBM has published an end of Support date for the compiler version (XL 9) that is currently used for Release 12 builds and patching.

We are announcing this to give time for our customers to prepare and to be compliant with all requirements for E-Business Suite patches generated after this February 16th 2014 date.

Please review the documents below for all new requirements required by the changes in the runtime and utilities packages on IBM AIX on Power Systems.

Where can I find more information?

Monday Dec 02, 2013

Office 2010 64-bit Certified with EBS 12

Office 2010 logoMicrosoft Office 2010 64-bit is now certified with EBS 12.0.6, 12.1.3, and 12.2 with desktop clients using the following configurations:

The 32-bit equivalents are already certified; details are available here.

Are any patches required?

You must apply server-side patches to EBS 12.0.6 and 12.1.3 environments.  Additional server-side patches are not required for EBS 12.2.x.  All required interop patches are documented here:

What about EBS 11i?

There are no plans for this certification in E-Business Suite 11i.  This certification primarily affects Web Application Desktop Integrator (a.k.a. WebADI, BNE) and Report Manager (FRM) integration with a 64-bit desktop client configuration.  Architectural constraints in the EBS 11i versions of these components make these certifications infeasible.

What EBS products are covered by this certification?

The Oracle E-Business Suite is comprised of several product families such as Financials, Supply Chain Management, Human Resources, and so on.  These product families group together collections of individual products.  Some of these products may be optionally integrated with one or more Microsoft Office components such as Excel, Word, and Projects.

Individual E-Business Suite product teams have the option of building integrations between their products and one or more Microsoft Office components.  This is not mandatory.  Over forty E-Business Suite teams offer these kinds of Office integrations today.

Examples of available integrations include:

  • HRMS Payroll integrations with Microsoft Excel
  • Supply Chain Management Contracts Core integration with Microsoft Word
  • Financials General Ledger (GL) integration with Microsoft Excel
  • Customer Relationship Management (CRM) Proposals integration with Microsoft Word

Which Office versions are certified?

We explicitly tested Microsoft Office 2010 64-bit Professional Edition with Oracle E-Business Suite.  We expect that our certification tests also apply to the 64-bit equivalents, if available, to the following editions:

  • Home and Student Edition
  • Home and Business Edition
  • Standard Edition
  • Professional Academic Edition
  • Professional Plus Edition
We have no plans to certify the following editions with Oracle E-Business Suite:
  • Office Web Apps
  • Starter Edition
  • Mac Edition
  • Office Mobile
I would not expect the results of our certification with Office 2010 Professional Edition to apply to the four editions above.

How are these integrations supported?

You can log Service Requests against the E-Business Suite product that you're trying to integrate with Microsoft Office. 

For example, you might be trying to take advantage of CRM Marketing (AMS) 12.1.2's integration with Excel 2010.  To get support, you can log an SR against CRM Marketing directly. 

The Support team for that product will help you diagnose and resolve the problem.  If the issue is isolated to a Microsoft product, then it may be necessary to log a corresponding support ticket with Microsoft, as well.

Related Articles


Thursday Nov 21, 2013

Can You Use Third-Party Tools to Modify Your EBS Database?

In short: no. But it's possible to give a more-nuanced answer for one scenario where they might be useful.

Our official policy on direct modifications to EBS databases

Every Oracle E-Business Suite manual in our documentation library contains this warning (emphasis added):

Do Not Use Database Tools to Modify Oracle E-Business Suite Data

Oracle STRONGLY RECOMMENDS that you never use SQL*Plus, Oracle Data Browser, database triggers, or any other tool to modify Oracle E-Business Suite data unless otherwise instructed.

Oracle provides powerful tools you can use to create, store, change, retrieve, and maintain information in an Oracle database. But if you use Oracle tools such as SQL*Plus to modify Oracle E-Business Suite data, you risk destroying the integrity of your data and you lose the ability to audit changes to your data.

Because Oracle E-Business Suite tables are interrelated, any change you make using an Oracle E-Business Suite form can update many tables at once. But when you modify Oracle E-Business Suite data using anything other than Oracle E-Business Suite, you may change a row in one table without making corresponding changes in related tables. If your tables get out of synchronization with each other, you risk retrieving erroneous information and you risk unpredictable results throughout Oracle E-Business Suite.

When you use Oracle E-Business Suite to modify your data, Oracle E-Business Suite automatically checks that your changes are valid. Oracle E-Business Suite also keeps track of who changes information. If you enter information into database tables using database tools, you may store invalid information. You also lose the ability to track who has changed your information because SQL*Plus and other database tools do not keep a record of changes.

Can data corruption really occur?

Yes. Even if you're using SQL*Plus, which is obviously not a third-party tool, you run the risk of corrupting your EBS database.  This is true for all tools that modify an EBS database directly.

What about third-party data archiving and purging tools?

Some third-party tools reduce the size of EBS databases by deleting data.  Some use database links, aliases, and other approaches to separate older data into other databases.

These tools can be useful for reducing the size of a production database for development purposes.  It generally doesn't matter if these smaller sandbox or testbed databases have referential integrity violations.

You should never use these tools to reduce the size of your production EBS database.

Why are these tools dangerous?  They claim that they're safe.

The E-Business Suite data model is partially documented here:

Unfortunately, that manual is not comprehensive. Third-party tools that rely on it to determine data relationships in the EBS data model will miss important dependencies.

EBS data dependencies are implemented through seed data, business logic, and other undocumented areas.  These hidden and undocumented dependencies mean that only current EBS Development staff are qualified to determine whether data can be safely removed. 

It is certain that third-party tools will violate EBS database referential integrity in some manner.  This is true even for third-party tools that are produced by people who used to work for Oracle EBS development.  EBS products continue to evolve and new dependencies are introduced on a regular basis.  These new dependencies may be undocumented.

What are the support implications of using third-party tools?

Oracle regards the use of third-party database tools to be customizations. Oracle's official policy is detailed here:

You should also review the support implications for using third-party tools.  They boil down to this:

  • Issues that are isolated to the E-Business Suite will be investigated by E-Business Suite Development.
  • Issues that are isolated to third-party tools should be directed to the third-party vendor.
  • E-Business Suite Development will provide E-Business Suite Development patches for issues that can be reproduced in environments built using E-Business Suite documented procedures and tools.
  • If the third-party vendor cannot resolve issues isolated to their tools, you should restore from a backup and revert to using Oracle’s documented tools and procedures.

Related Articles


Saturday Sep 28, 2013

E-Business Suite Support Timelines Updated at OpenWorld 2013

[Oct. 30, 2013 Update: Corrected typo -- US Form 1099 updates are provided to 2014]

Our release of E-Business Suite 12.2 is accompanied by changes to support timelines for previous releases.  These changes were announced at OpenWorld 2013.  They override changes announced at OpenWorld 2012.

Latest changes to EBS Support timelines 2013

EBS 11.5.10.2 covered by an Exception to Sustaining Support to December 31, 2015

This provides updates during the Sustaining Support period for:

  • New fixes for Severity 1 production issues
  • Critical Patch Updates (CPU) for security-related issues
  • Legislative updates
    • US Form 1099 2013 and 2014 year-end updates
    • Payroll regulatory updates for US, Canada, UK, and Australia for each country's fiscal years ending in 2014

Longer EBS 12.1 Premier and Extended Support timelines

  • Premier Support runs to December 31, 2016
    (Originally was to end May 2014; 31 extra months added)
  • Extended Support runs to December 31, 2019
    (Originally was to end December 2018; one extra year added)

These changes are officially documented here:

Table showing latest 2013 EBS Premier Extended Sustaining Support timelines windows

What about E-Business Suite technology stack components?

These support date extensions only cover internal EBS application tier technology stack components such as Oracle Forms and Reports, Oracle HTTP Server, Oracle JServ, Oracle Containers for Java (OC4J), and Java (JDK and JRE).

They do not extend support dates for the Oracle Database or optional externally-integrated application tier components such as Discoverer, Oracle Single Sign-On, Oracle Access Manager, Oracle Internet Directory, or other Fusion Middleware products.

To learn more about the interlocking EBS+techstack component support windows, see these two articles:

Related Articles


Friday Jan 11, 2013

When will my Oracle bug fix or enhancement request be released?

As EBS customers using mission-critical software, you are naturally curious about when you will get fixes for bugs that you've reported.  It's also understandable that you'd like to know when certain enhancements will be delivered.

Oracle tracks all bugs and enhancement requests in a single massive database, which we use for released and unreleased products. This centralized database is an amazing accomplishment: it's a treasure trove of detailed technical analyses, debates, development decisions, and future plans.

Locked down by default

Oracle's Revenue Recognition policies place strict boundaries on the type of information that can be shared about unreleased products.  The centralized nature of the bug database makes for some conundrums around external disclosure, since it can sometimes be very tricky to determine whether something is a bug fix or an enhancement, and whether the codeline is already released or not.

For maximum safety, all Oracle staff are required to take the most-conservative stance by default:

  • We are not permitted to discuss release dates or release vehicles.

This is true regardless of whether you're speaking with someone in Oracle Support, Development, Sales, Consulting, or any other Oracle functions. This covers nearly all variants of the question, "When will ___ be { fixed | certified | released }?"

You shouldn't be surprised or disappointed if you get an answer that boils down to, "I'm sorry, but I'm afraid that I can't provide any information specific dates or release vehicles." 

Please be gentle with our messengers; they're just doing their job.

Escalated Severity 1 situations

There may be special circumstances for Severity 1 bugs that have severe negative impact on production environments. If you have an escalated Severity 1 Service Request that meets these criteria, an Oracle Escalation Manager can assist further.

Related Articles


Monday Feb 20, 2012

Extended Support Fees Waived for E-Business Suite 11i and 12.0

[Mar. 13, 2012 update: The Oracle Software Technical Support Policies document is now updated to reflect these fee waivers]

Extended Support fees for Oracle E-Business Suite Release 11i and 12.0 have been waived.  These fee waivers cover the entire three-year Extended Support periods for both of these releases:

  • EBS 11i Extended Support from November 1, 2010 to November 30, 2013
  • EBS 12.0 Extended Support from February 1, 2012 - January 31, 2015

Customers with an active Oracle Premier Support for Software contract will automatically be entitled to Extended Support coverage for EBS 11i and 12.0.  Also remember that Extended Support fees are waived for the first year of EBS 12.1 Extended Support.

Diagram showing EBS 11i 12.0 and 12.1 Premier and Extended Support dates

Where is this documented officially?

These Extended Support fee waivers are published here:

Support dates for Premier and Extended Support for the E-Business Suite are published here on the Oracle Lifetime Support -- Software Brochures site:

Minimum patching baselines required

These fee waivers do not change the minimum patching baselines for each of these EBS Releases.  For more details about those minimum baselines, see:

Related Articles



Friday Dec 30, 2011

Limited Extended Support Available for Oracle Single Sign-On through 2012

Premier Support for Oracle Single Sign-On 10gR3 ends on December 31, 2011.  This was originally slated to be the end of error correction support for Oracle Single Sign-On 10gR3. 

Our Oracle Identity Management team has just revised that policy.  If you have an existing support contract, you will now be able to receive limited Extended Support for Oracle Single Sign-On from January 2012 through December 2012.  Only Severity 1 fixes for Oracle Single Sign-On will be released during the limited Extended Support period.  Critical Patch Updates (CPUs) for Oracle Single Sign-On will not be released during the limited Extended Support period. 

These changes are published in:

This is good news for those of you that have not been able to migrate to a single sign-on solution utilizing Oracle Access Manager and Oracle E-Business Suite Access Gate.  Keep in mind though, the clock is ticking and limited extended support will end in a mere 12 months.  It is strongly recommended that you use this additional time to integrate your single sign-on deployment with Oracle Access Manager and Oracle E-Business Suite Access Gate.  


Our recommendations

EBS 12 customers should move to a single sign-on solution using Oracle Access Manager 11g

EBS 11i customers first upgrade to EBS Release 12.1.3, then integrate with Oracle Access Manager 11g.  If an R12 upgrade is not possible, then R11i customers are encouraged to migrate their single sign-on solution to Oracle Access Manager 10gR3

EBS customers looking to deploy a single sign-on solution for the first time are strongly encouraged to deploy a solution using Oracle Access Manager 11g.

References

Related Articles

Thursday Nov 03, 2011

ATG 12.1.3 Release Update Pack Required by Feb 2012 for Premier Support

If you're already running any of the E-Business Suite 12.1 releases -- 12.1.1, 12.1.2, or 12.1.3 -- you don't need to be concerned about yesterday's article about 12.0 minimum baselines. Even better, you should be reassured that EBS 12.1 Extended Support fees have been waived for the first year.

However, there is one important thing from yesterday's article that you may have missed.  We will certify all new EBS 12.1 patches on the following technology stack baseline after February 1, 2012:

Screenshot of download page for ATG 12.1.3 Release Update Pack

Staying current if you're on EBS 12.1.1 or 12.1.2

The simplest solution for all EBS 12.1.1 and 12.1.2 customers is to apply the suite-wide EBS 12.1.3 Release Update Pack. We recommend that all EBS 12.1.1 and 12.1.2 upgrade to 12.1.3.

If you need to stay on 12.1.1 or 12.1.2 for a while, you still must apply the ATG 12.1.3 Release Update Pack by February 1, 2012 to be eligible for Premier Support.  The ATG 12.1.3 RUP is cumulative and includes all important technology stack updates released individually for EBS 12.1.1 and 12.1.2.

Keeping on top of EBS support policies

All E-Business Suite sysadmins should regularly review the two interlocking support policy documents that affect your environments' support status:

  1. Oracle's Lifetime Support Policy
    Specifies support dates for major EBS release codelines (e.g. EBS 11.5.10.2, 12.0, 12.1) -- and by implication, the latest EBS patchset for a given codeline. The Lifetime Support Policy presents support definitions and dates for three different levels of support:  Premier, Extended, and Sustaining. 

  2. E-Business Suite Error Correction Support Policy (Note 1195034.1)
    Specifies support principles for EBS release update packs for a given EBS releases codeline covered by Premier Support.  Examples of EBS release update packs (RUPs) include EBS 12.0.2, 12.0.3, 12.0.4, 12.0.5, 12.0.6, 12.1.2, 12.1.3. 
What about E-Business Suite technology stack components?

It's important to remember that Fusion Middleware and database components in EBS instances are separate from the the ATG Release Update Packs and are governed by their own support policies and dates.  This applies to the technology stack components installed by the E-Business Suite Rapid Install (e.g. Oracle Forms, OC4J, database).  This also applies to external standalone components (e.g. Oracle Single Sign-On, Discoverer, SOA Suite) that you may have integrated with your E-Business Suite environment.

You must also plan to update those technology stack components on an ongoing basis.  If you're interested in learning more about the implications of Fusion Middleware and database support windows for E-Business Suite users, see these two articles:

Related Articles


Wednesday Nov 02, 2011

EBS 12.0 Minimum Baseline Required by Feb 2012 for Extended Support

This is a reminder that Oracle E-Business Suite Release 12.0 will transition from Premier Support to Extended Support on February 1, 2012.  After that date, new EBS 12.0 patches will be created and tested against the minimum patching baseline documented here:

Chart showing EBS support timelines

All EBS 12.0 customers must apply the minimum patches listed in that document to be eligible for Extended Support. Those patches include the  EBS 12.0.6 Release Update Pack, technology stack infrastructure updates, and updates for EBS products if they're shared or fully-installed.

Instead of applying the minimum baseline

If you haven't applied any of those updates yet, the simplest solution would be to apply the suite-wide EBS 12.1.3 Release Update Pack.  That way, you bypass the 12.0 minimum patching requirements and immediately comply with the EBS 12.1 minimum requirements simultaneously.

As an added benefit of applying the 12.1.3 Release Update Pack, you will be eligible for the waiver of the first year of Release 12.1 Extended Support.  For more details, about that fee waiver, see:

Don't Forget EBS Release 12.1 Support Milestones

If you're already on EBS 12.1, you don't need to worry about the 12.0 minimum baselines described above.  However, the same note describes the 12.1 minimum prerequisites:

  • By July 1, 2011:  You must apply the Applications Technology Release Update Pack (RUP) 12.1.2 (R12.ATG_PF.B.Delta.2, Note 845809.1) 
  • By Feb. 1, 2012:  You must apply the Applications Technology Release Update Pack (RUP) 12.1.3 (R12.ATG_PF.B.Delta.3, Note 1066312.1)
  • By Feb. 1, 2013:  You must apply the suite-wide E-Business Suite 12.1.3 Release Update Pack
If you're still on EBS 12.1.1 and haven't applied any of these updates, the simplest thing would be to apply the suite-wide E-Business Suite 12.1.3 Release Update Pack.

Related Articles

Tuesday Oct 25, 2011

EBS 12.1 Extended Support Fees Waived for First Year

In response to concerns raised by the Oracle Applications User Group Support Council, Oracle has waived the first year of EBS 12.1 Extended Support fees. 

This waiver will be valid from June 2014 to May 2015.  During this period, customers receive access to Extended Support features at no additional cost other than their fees for Software Update License & Support.

For more details about this waiver, see:

Diagram showing ebs 11i 12-0 12-1 support timelines

Use this time wisely -- upgrade to 12.1.3 now

The clock is on: E-Business Suite 11i and 12.0 customers should upgrade to E-Business Suite 12.1 as soon as possible.  Extended Support for EBS 11.5.0 ends in November 2013.  Premier Support for EBS 12.0 ends in January 2012.

Related Articles


Tuesday Jul 05, 2011

Reminder: Important Upcoming E-Business Suite Release 12 Support Milestones

This is a reminder that Oracle E-Business Suite Release 12.0 will transition from Premier Support to Extended Support on February 1, 2012.  After that date, new EBS 12.0 patches will be created and tested against the minimum patching baseline documented here:

Diagram showing EBS 11i 12.0 and 12.1 premier and extended support timelines

All EBS 12.0 customers must apply the minimum patches listed in that document to be eligible for Extended Support. Those patches include the  EBS 12.0.6 Release Update Pack, technology stack infrastructure updates, and updates for EBS products if they're shared or fully-installed.

If you haven't applied any of those updates yet, the simplest solution would be to apply the suite-wide EBS 12.1.3 Release Update Pack.  That way, you bypass the 12.0 minimum patching requirements and immediately comply with the EBS 12.1 minimum requirements simultaneously.

Don't Forget EBS Release 12.1 Support Milestones

If you're already on EBS 12.1, you don't need to worry about the 12.0 minimum baselines described above.  However, the same note describes the 12.1 minimum prerequisites:

  • By July 1, 2011:  You must apply the Applications Technology Release Update Pack (RUP) 12.1.2 (R12.ATG_PF.B.Delta.2, Note 845809.1) 
  • By Feb. 1, 2012:  You must apply the Applications Technology Release Update Pack (RUP) 12.1.3 (R12.ATG_PF.B.Delta.3, Note 1066312.1)
  • By Feb. 1, 2013:  You must apply the suite-wide E-Business Suite 12.1.3 Release Update Pack
If you're still on EBS 12.1.1 and haven't applied any of these updates, the simplest thing would be to apply the suite-wide E-Business Suite 12.1.3 Release Update Pack.

Related Articles


Friday Jun 03, 2011

E-Business Suite Technology Stack Roadmap (June 2011) Now Available

We certify over 150 new combinations and versions of Oracle products with the E-Business Suite a year -- and that's before you factor in our forty or so platform-based combinations.  We also update our certification plans and roadmap as new third-party products like Microsoft Office 2010 and Firefox are announced or released.  Complicating matters further, various Oracle products leave Premier Support or are superceded by more-recent versions.

This constant state of change means that any static representation of our roadmap is really a snapshot in time, and a snapshot that might begin to yellow and fade fairly quickly.  With that caveat in mind, here's this month's snapshot (which has some updates following my OAUG/Collaborate presentation in April 2011):

EBS release roadmap


What's in the latest roadmap?
  • Comparisons of support categories (Premier, Extended, Sustaining)
  • Summaries of the latest database, Fusion Middleware, and E-Business Suite Lifetime Support Policies
  • Desktop Client certifications (browsers, JREs, operating systems)
  • Database Tier certifications
  • Application Server Tier certifications
  • External Integrations certifications
  • Security-Related certifications
  • "Other Cool Stuff" -- virtualization, clouds
How should I use this roadmap?
  1. Check the support status of your currently deployed techstack component versions
  2. Plan your upgrades to the next certified level
  3. Build a business case for switching from older technology to the latest technology (e.g. switching from Discoverer to Oracle Business Intelligence Enterprise Edition+)
  4. Seek clarification on open questions
Related Articles

Tuesday Feb 15, 2011

EBS 12.0 Minimum Requirements for Extended Support Finalized

Oracle E-Business Suite Release 12.0 will transition from Premier Support to Extended Support on February 1, 2012.  New EBS 12.0 patches will be created and tested during Extended Support against the minimum patching baseline documented in our E-Business Suite Error Correction Support Policy (Note 1195034.1).

Timeline diagram showing E-Business Suite 11i 12 Premier and Extended Support windows ebs_11i_12_support_windows.pngThese new technical requirements have now been finalized.  To be eligible for Extended Support, all EBS 12.0 customers must apply the EBS 12.0.6 Release Update Pack, technology stack infrastructure updates, and updates for EBS products if they're shared or fully-installed.  The complete set of minimum EBS 12.0 baseline requirements are listed here:
What are the impacts of this new baseline?

As always, Oracle Support will assist with diagnosis, triage, and debugging of any issues that you report for your E-Business Suite environment.  You will continue to have access to any existing online support tools, knowledge base documentation, and pre-existing fixes.

If you report a new issue that requires a new bug fix, you should be aware that new patches will be released only for the new baseline patches listed in the EBS Error Correction Support Policy.  You should plan to apply the baseline updates (at minimum) listed in Note 1195034.1 by February 2011 in order to receive any new bug fixes.

What EBS 12.0 products are affected by this new baseline?

The Note lists minimum baseline update requirements for the following EBS 12.0 products (see the Note for specific patch numbers):
  • Financials (Payables, Receivables, Advanced Collections, Public Sector Financials, Financials for Asia/Pacific)
  • Human Resources (Payroll, US Federal HR)
  • Process Manufacturing (OPM Financials, OPM Process Execution, OPM Process Execution Mobile, Inventory Converge)
  • Service (Complex Maintenance, Repair & Overhaul)
  • Supply Chain Planning (Engine + UI, UI Source Side, Data Collections, Global Order Processing, Collaborative Planning, Demand Planning, Demantra)
What about E-Business Suite technology stack components?

Here are the highlights of the technology stack-related minimum baseline requirements from that Note:
  • E-Business Suite 12.0.6 Release Update Pack
  • Oracle Forms & Reports 10.1.2.3
  • Oracle Containers for Java (OC4J) 10.1.3.5
  • Oracle Database 10.2.0.5, 11.1.0.7, or 11.2.0.2
  • Java 6 for server-side Java
  • Sun JRE 1.6.0_03 for Windows desktops
Support dates for Oracle Forms & Reports, Oracle Containers for Java (OC4J), Oracle Database, and Java are set by their respective Lifetime Support Policies.  The minimum versions listed in Note 1195034.1 may be superseded by their respective support policies by February 1, 2012.

EBS 12.0 users must ensure that installed versions of the components above comply with the components' respective Lifetime Support Policies listed here:
This also applies to external standalone components (e.g. Oracle Single Sign-On, Discoverer, SOA Suite) that you may have integrated with your E-Business Suite environment.

You must also plan to update those technology stack components on an ongoing basis.  If you're interested in learning more about the implications of Fusion Middleware and database support windows for E-Business Suite users, see these two articles:
Ranking your upgrade options

If I were running EBS 12.0 today, I'd rank my options like this:
1. Upgrade to EBS 12.1.3

Upgrading to EBS 12.1.3 unquestionably provides the greatest return on your patching investment.  This allows you to completely avoid having to ask, "What EBS 12.0 patches do I need to apply to reach the minimum patching baseline?" 

This option may be relatively more work than simply patching EBS 12.0, but it's the most-efficient strategy in the long-run.  Moving to 12.1.3 means that you don't need to worry about new minimum patching baselines until June 1, 2014.

2. Apply the 12.0.6 minimum baseline

Applying the 12.0.6 Release Update Pack, the latest technology stack updates, and the product-specific patches is a straightforward process.  This option may require nominally less effort than upgrading to 12.1.3. 

All of these updates will require retesting of all affected products.  Testing is usually more time-consuming and resource-intensive than applying the patches themselves.  If I was in your shoes and had to go to the trouble of testing everything again, I'd choose Option 1 rather that 2.

3. Do nothing

This is always an option.  I wouldn't recommend it.  Leaving your EBS environment at the, say, 12.0.4 level with one or two other later product family Release Update Packs may create support problems downstream.  For example, you may report a problem that can be reproduced on 12.0.6 and the minimum baseline.  Oracle will provide a patch for that issue, but you will first need to apply the minimum baseline to your 12.0 environment before applying the patch.
Getting ahead of the curve

It might seem like February 1, 2012 is a long way off, but don't be fooled.  That's the temporal equivalent of an optical illusion.  It's only 12 months away.  I urge you to get started on your EBS 12.0 upgrade planning immediately.

Related Articles

Tuesday Dec 14, 2010

Heads-Up: Preparing for E-Business Suite 12.0 Extended Support

Oracle E-Business Suite Release 12.0 will transition from Premier Support to Extended Support on February 1, 2012.  New EBS 12.0 patches will be created and tested during Extended Support against the minimum patching baseline documented in our E-Business Suite Error Correction Support Policy (Note 1195034.1).

Timeline diagram showing E-Business Suite 11i 12 Premier and Extended Support windows ebs_11i_12_support_windows.png
That document currently reads:
To be eligible for Extended Support, [EBS 12.0] customers will need to have applied at minimum the 12.0.6 Release Update Pack (Note ID 743368.1) and the Financials CPC July 2009 (Note ID 557869.1).   Additional minimum requirements for Oracle E-Business Suite Release 12.0 have not been finalized yet.

Oracle E-Business Suite Release 12.0 users are strongly encouraged to apply the latest suite-wide Release Update Packs, product family Release Update Packs, Critical Patch Updates, and applicable technology stack certifications to minimize future upgrade requirements.
Ranking your upgrade options

If I were running EBS 12.0 today, I'd rank my options like this:
1. Upgrade to EBS 12.1.3

Upgrading to EBS 12.1.3 unquestionably provides the greatest return on your patching investment.  This allows you to completely avoid having to ask, "What EBS 12.0 patches do I need to apply to reach the minimum patching baseline?" 

This option may be relatively more work than simply patching EBS 12.0, but it's the most-efficient strategy in the long-run.  Moving to 12.1.3 means that you don't need to worry about new minimum patching baselines until June 1, 2014.

2. Apply the suite-wide 12.0.6 Release Update Pack

Applying the 12.0.6 Release Update Pack is straightforward.  This option may require less effort than upgrading to 12.1.3.  However, there's a non-trivial chance that 12.0.6 may not be the only patch needed.  The Error Correction Support Policy document explicitly states, "Additional minimum requirements for Oracle E-Business Suite Release 12.0 have not been finalized yet." 

This means that it's possible that other patches on top of 12.0.6 may be added to the minimum patching baseline.  In other words, it's possible that other product family Release Update Packs, Critical Patch Updates, and technology stack certifications may be added to that list.

3. Do nothing

This is always an option.  I wouldn't recommend it.  Leaving your EBS environment at the, say, 12.0.4 level with one or two other later product family Release Update Packs may create support problems downstream.  For example, you may report a problem that can be reproduced on 12.0.6.  The subsequent patch will have 12.0.6 as a hard prerequisite.
Getting ahead of the curve

It might seem like February 1, 2012 is a long way off, but don't be fooled.  That's the temporal equivalent of an optical illusion.  It's only 13 months away.  I urge you to get started on your EBS 12.0 upgrade planning immediately.

Related Articles

About

Search

Categories
Archives
« July 2016
SunMonTueWedThuFriSat
     
2
3
5
6
7
8
9
10
12
13
15
16
17
18
22
23
24
28
29
30
31
      
Today