Monday Oct 14, 2013

Fusion Middleware 11gR1 Support Dates Updated

Support dates for Premier and Extended Support for Oracle Fusion Middleware 11gR1 products were recently extended.  The new dates allow more time for current FMW 11gR1 users to upgrade to FMW 12c.  These new dates are published here:
These changes are explained in more detail here:
Impact on E-Business Suite Users

These changes do not affect support dates for EBS 11.5.10.2, 12.0, 12.1, or 12.2.  Fusion Middleware components used in the internal application-tier technology stack for these EBS releases include Oracle HTTP Server, Forms & Reports, Oracle Containers for Java (OC4J), and others.  Support dates for the E-Business Suite for these internal components override the published FMW support dates.

These changes affect EBS users who are currently running:
  • Java SE 6 (JDK and JRE)
  • Oracle WebCenter Portal 11.1.1.x
  • Oracle Business Intelligence Suite Enterprise Edition 11.1.1.x
EBS users who have integrated their environments with the following products are not affected:

Getting help for your questions about Fusion Middleware support dates

We're EBS specialists on this blog.  We can only provide basic assistance with questions about FMW support dates.  You should log Service Requests against the specific Fusion Middleware products for which you have support date-related questions.

Related Articles


Thursday Jun 13, 2013

Important Changes to E-Business Suite Error Correction Support Policy

Oracle provides bug fixes and legislative updates for Oracle E-Business Suite as part of its Premier and Extended Support offerings.  The requirements and methods for delivering those updates are explained here:

We've made some important changes to our policies.  All EBS customers should read Version 4 carefully.

Why did we make these changes?

Version 3 was published in 2011.  That version stated that new EBS 12.1 one-off patches would require all customers to have applied the suite-wide EBS 12.1.3 Release Update Pack by January 2013.

A significant number of customers have told us that they have not been able to apply EBS 12.1.3 in time.  These customers have expressed concerns that 12.1.1 or 12.1.2 "were being desupported" and that they would not be able to request new updates.

What is our standard guidance?

Oracle recommends that all customers apply the latest suite-wide Release Update Pack. There are significant benefits to keeping your E-Business Suite environment updated with the latest suite-wide Release Update Packs:

  • They are cumulative, reducing the overhead of identifying many individual patchsets
  • They deliver the latest new features and enhancement requests
  • They include the latest updates for performance, stability, and security
  • They reduce the number of prerequisites required for other patches or new technology integrations

What has changed?

The 2011 version stated that all new one-off patches would require the suite-wide EBS 12.1.3 Release Update Pack as a minimum prerequisite.

The 2013 version relaxes the prerequisites for new one-off patches.  New one-off patches will be produced with the individual 12.1.3 Family Packs as minimum prerequisites. This is so that vast majority of customers, who are at the 12.1.3 level, can get simpler and smaller patches. 

How will this work?

For example, you request a new one-off patch for an Oracle Financials issue that you've encountered with EBS 12.1.2:

  • Under the 2011 policy, the new Financial patch's prerequisite would be the EBS 12.1.3 suite wide Release Update Pack.
  • Under the 2013 policy, the new Financial patch's prerequisite is the Financials 12.1.3 Family Pack.
Are EBS 12.1.1 or 12.1.2 desupported?

You are not desupported if you are on 12.1.1 or 12.1.2.  The question incorrectly assumes that 12.1.1 or 12.1.2 are "releases" covered by our Premier or Extended Support offerings.

An EBS environment consists of a base release and subsequent updates.

Base releases are used to create new E-Business Suite environments or upgrade environments running older EBS releases.  Base releases are documented in Oracle Lifetime Support Policy: Oracle Applications and are eligible for Premier, Extended, and Sustaining Support.

EBS 12 Base release support dates

Examples of base releases:

  • E-Business Suite Release 12.0
  • E-Business Suite Release 12.1

You get updates to base releases through:

  • Release Update Packs (RUPs)
  • One-off patches
  • Critical patch updates (CPUs)
Here's the same question, restated:
  • Q: "How do I get updates for the EBS 12.1 base release?" 
  • A: By applying the latest Release Update Pack.  If the fix that you need is not already included in the latest Release Update Pack, you may request a new one-off patch.  New one-off patches will require their respective 12.1.3 Family Packs as a minimum prerequisite.

What if you haven't applied the relaxed minimum prerequisites?

Oracle will first recommend that you apply the appropriate 12.1.3 Family Packs. In cases of urgent business need, Oracle will evaluate the feasibility of creating one-off patches without the established minimum prerequisites. Whether this is practical will vary depending upon the complexity of the dependencies.  If the patch is in an area of code that has undergone little revision with few dependencies, it may be straightforward to produce one-off patches without the established minimum prerequisites. 

In most cases involving complex code objects, such as the major transaction screens, it is likely that a full dependency analysis will show that a major portion of the established minimum prerequisites levels are, in fact, required to apply the patch.  In these cases, Oracle will recommend that customers minimize their risk by installing the established minimum prerequisites rather than a one-off dependency tree that is nearly as extensive but has not undergone the same level of testing.

You are closer to 12.1.3 than you realize

Our patching minimum prerequisite have been relaxed.  We still recommend that all customers apply the EBS 12.1.3 suite-wide Release Update Pack.  If you can't apply the EBS 12.1.3 suite-wide Release Update Pack, you should still apply the 12.1.3 Family Packs for the EBS products that you're using.

You are probably a lot closer to 12.1.3 in most areas than you may realize.  Any patches that were created since you went live almost certainly delivered code above the 12.1.3 version level.  So, in areas where you had any patching or tuning as you stabilized on 12.1, it's pretty likely that any further patching would not require the 12.1.3 Family Pack.  To understand this in more detail, you can run "Patch Wizard" to do an analysis of what files on your system would really change if you applied each 12.1.3 Family Pack.  

What are the impacts of these changes for 12.0 customers?

The patching prerequisites for EBS 12.0 are not affected by these policy changes.  EBS 12.0 customers must have the minimum prerequisites

Your feedback is welcome

We've relaxed these policies to simplify your EBS maintenance requirements.  Please feel free to let us know if you have any comments or questions about these updated policies. 

Monday Apr 29, 2013

How to Obtain Media Packs for Older Versions of Oracle Products

Installation media for all Oracle products can be downloaded from the Oracle Software Delivery Cloud (SDC, formerly called Oracle eDelivery). You can use this site to obtain Media Packs for the latest versions of all licensable Oracle products.  Media Packs are available in zip and ISO formats, which you can unzip or burn to DVDs, respectively.  All of the download links on the Oracle Technology Network (OTN) point to the Software Delivery Cloud, making the latter the authoritative source for all Oracle downloads.

Screenshot of Oracle Software Delivery Cloud

For more information about SDC, see:

Need to download older versions?

The Oracle Software Delivery Cloud hosts the latest released versions.  There may be times when you need a media pack for an older release.  

For example:

As of today, the latest version of Oracle Access Manager available for download is Oracle Access Manager 11.1.2.1.0.

We're certifying Oracle Access Manager 11.1.2.1.0 with the E-Business Suite right now.  In the interim, E-Business Suite customers should use only the 11.1.2.0.0 version.

If you need a Media Pack for an older release, you can log a Service Request requesting the specific release.  Oracle Support has a team that's dedicated to handling these types of shipping requests and other non-technical issues.  Also see:

Friday Apr 05, 2013

Covering our EBS Technology Stack Roadmap at OAUG Collaborate

OAUG Collaborate 2013 Denver logo

[Update Apr. 25, 2013:  The presentation is available for download here:

I have historically covered our technology certification roadmap for the E-Business Suite in two sessions at OAUG Collaborate every year:  once during the EBS technology stack Special Interest Group meeting on Sunday, and again later in the week as a formally-scheduled conference session.

We're trying to expand our coverage of other topics with other speakers.  This year you'll only have one chance -- not two -- to hear this material:

  • EBS Applications Technology Special Interest Group
    SIG chair: Srini Chavali, Cummins
    Sunday, April 07, 12:00 PM - 01:00 PM
    Location: Room 603

Please join us for this session if you'd like to hear about our latest E-Business Suite technology stack certification roadmap and updates to our support terms and policies. 

There will be a special panel in the same room at 1:15 PM where you will have the chance to ask questions of our Applications Technology Group staff members attending the conference.  These include Elke Phelps, Max Arderius, Kevin Hudson, Gustavo Jimenez, Isam Alyousfi, and me.  Other Oracle Development staff will be in the audience, too, since the dais can only seat a small number of us.

Related Articles


Wednesday Mar 27, 2013

Migrating from EBS 11i + Oracle Single Sign-On to EBS 12 + Oracle Access Manager

Our Identity Management team has just published an important change in the Oracle Software Technical Support Policies document (March, 2013):

"For customers with a current support contract for Oracle Single Sign-On 10gR3, Extended Support will be made available until December 2013 at then-current Extended Support fees. During this period, Extended Support will be limited to Severity 1 fixes only; critical patch updates will not be made available."

This is important if you've been wondering how to deal with this challenge: 

  • You know that Oracle Access Manager has supplanted Oracle Single Sign-On.  
  • You integrated Oracle Single Sign-On 10g with your E-Business Suite 11i environment several years ago.  
  • You plan to switch from Oracle Single Sign-On to Oracle Access Manager as part of your EBS 12 upgrade.
  • You want to get to EBS 12, but want to perform your EBS upgrade and OAM migrations different downtimes.
  • You've been staring at the latest EBS support timelines and deliberating your options:

Timeline showing updated EBS Support dates

All of the crucial pieces for this are now in place:

  1. Oracle Access Manager 11.1.2 is certified with EBS 11.5.10.2.
  2. Support for Oracle Single Sign-On 10g has been extended to Dec. 31, 2013.
  3. EBS 11.5.10's Exception to Sustaining Support has been extended to Dec. 31, 2014.
  4. EBS 12.1's Extended Support has been extended to Dec. 31, 2018.

This means that you have sufficient support coverage for all major components while you do this in a multi-phase implementation.  You can migrate your EBS 11i environment from Oracle SSO 10g to Oracle Access Manager 11.1.2 this year, in one initial downtime.  You can then upgrade that environment from EBS 11i to EBS 12.1.3 in a later downtime. 

Your implementation phases will look like this:

  1. Today: EBS 11i + Oracle Single Sign-On 10.1.4.3
  2. Interim phase:  EBS 11i + Oracle Access Manager 11.1.2
  3. Final phase: EBS 12.1.3 + Oracle Access Manager 11.1.2

Each of these undertakings can be fairly major initiatives on their own, so breaking the overall project into smaller parts helps you manage your risk.  I would be very interested in hearing about your experiences with this kind of combined migration + upgrade implementation approach.  Please feel free to post a comment here or drop me a line privately.

Related Articles


Monday Feb 25, 2013

Avoid Mixing Custom Applications with E-Business Suite Environments

The E-Business Suite technology stack is extensive. Many components are distributed across the EBS database and application tiers.  These include the Oracle Database, Oracle HTTP Server, Oracle Forms and Reports 10g, Oracle Containers for Java, and many others.

EBS 12.1 technology stack architecture

Internal EBS components are tightly-coupled

Most of these components are not "user-serviceable" in the conventional manner.  They're tightly integrated with the E-Business Suite, with deep dependencies, custom configuration files, and dedicated configuration management utilities that are designed specifically for the E-Business Suite.  

The internal E-Business Suite technology stack is relatively tightly-coupled: you generally cannot change one thing without understanding how those changes will affect other components. 

Examples of what this means:

  • You can't drop a new UIX library into an EBS environment without also delivering the corresponding changes in the OA Framework layer.
  • You can't simply replace the E-Business Suite's Oracle Forms and Reports 10g with, say, Oracle Forms and Reports 11g. 

External integrations are loosely-coupled

It is also possible to integrate the E-Business Suite with other Oracle products.  These integrations are optional, in the sense that you don't need them to use the core E-Business Suite functionality.  These are sometimes called external integrations since they're outside of the core EBS technology stack.

Examples of external integrations:

  • You can optionally integrate Oracle Business Intelligence Enterprise Edition with your EBS environment to offer advanced analytic capabilities.
  • You can optionally use Oracle Access Manager and Oracle Internet Directory if you'd like to integrate the E-Business Suite with a third-party authentication system.
External integrations (e.g. OBIEE, Oracle Access Manager, Discoverer) are loosely-coupled.  For example, applying the Discoverer 11.1.1.6 patchset won't trigger changes to EBS products that deliver Discoverer workbooks. Some small interoperability patches required, but you can generally upgrade externally-integrated Oracle products without significant changes to E-Business Suite technology stack components or product level code. 

Before you upgrade internal and external components

You should always check that newer versions of internal and external components are certified before upgrading them.  We release around 80 new certified component updates a year, comprising over 150 configurations.  Monitoring or subscribing to this blog is the best way of keeping up.

The official Certification database on My Oracle Support is the definitive source of all EBS certifications.  I've also published a one-page summary of all of the latest E-Business Suite techstack certifications on this blog.

What does this mean for custom applications?

You might be tempted to deploy a custom application in the E-Business Suite technology stack.  After all, you think to yourself, that's easier than installing a separate server for, say, OC4J. 

Don't do it.

The E-Business Suite internal technology stack should be reserved strictly for the E-Business Suite. Mingling your own custom applications into the E-Business Suite technology stack:

  • Makes it difficult to debug or isolate EBS performance or stability issues.
  • Increases your security risk.  If your custom application is compromised, then your EBS environment may also be jeopardized, or vice versa.
  • Makes it difficult to upgrade EBS components if your custom application is dependent on older versions.
  • Makes it difficult to upgrade your custom application if the E-Business Suite is dependent on older component versions than your custom code.
  • Potentially doubles your maintenance outages for your users. Your EBS environment will be taken down every time you need to apply an update to your custom application, and vice versa.

What you should do

Option 1: Deploy on a separate server

Ideally, you should install your custom application and its required technology stack prerequisites on a different physical server.  This will ensure that the E-Business Suite remains completely isolated from your custom application, its technical requirements, and its load requirements.  This is the recommended approach.

Option 2: Deploy in a separate ORACLE_HOME on an EBS server

Less ideally, you can install your custom application in a different ORACLE_HOME on an existing E-Business Suite server.

This is not recommended. There are a number of downsides to this approach:

  • If your custom application's security is compromised, this might put your E-Business Suite environment at risk.
  • Deploying your custom application and its components on your EBS server will make performance tuning difficult.  If your server's resources are maxed out, how do you determine whether the problem lies with EBS or your custom application?  

  • A single point of failure: server maintenance or outages take down all applications that share that server.  Physical consolidation saves money but increases risk.

Implications for support

Here's the biggest reason not to mix EBS environments with custom applications:  it makes support very difficult, if not impossible. 

Oracle can best assist with issues that we can reproduce.  We can issue EBS patches only for issues that can be reproduced on standard EBS environments. 

If a problem occurs in an E-Business Suite environment that includes other uncertified components or code, then our default recommendation will be to disable those before investigating further.

Related Articles

Wednesday Feb 06, 2013

Using Oracle Label Security with Oracle E-Business Suite

Most security administrators know how to use E-Business Suite responsibilities to manage access to data and functionality.  The majority of EBS customers will never need anything beyond those standard capabilities. Some organisations may need specialised security to complement the EBS responsibility model. Oracle Label Security may appropriate for certain specialised requirements.

Oracle Label Security example diagram

Oracle Label Security allows administrators to classify every row in a table, ensuring that access to sensitive data is restricted to users with the appropriate clearance level. OLS can be used to enforce regulatory compliance with a policy-based administration model to support custom data classification schemes for implementing “need to know” access. Labels can be used as factors within Oracle Database Vault command rules for multi-factor authorization polices.

Supported but not certified

It is possible to use Oracle Label Security with the E-Business Suite.  Custom OLS policies will -- by design -- change the end-user behavior of EBS.  It is possible for an OLS policy to break EBS, so we can't offer the standard technology certification in this case.   What is certified is "the approach" of using OLS to implement custom security policies over EBS relational data.  We do not certify specific versions of OLS, nor do we certify specific OLS policies.

From a support perspective, we treat OLS policies like any other EBS customization, namely:

  • We can only issue EBS patches for issues that can be reproduced in environments without custom OLS policies.
  • If you report an issue that can't be reproduced in vanilla, uncustomized environments, our default guidance will be to disable the custom OLS policies.
  • We cannot review your OLS policies or make recommendations on how to create custom OLS policies.

How do I define OLS policies in EBS environments?

This rather-elderly Note explains techniques for adding OLS policy initialization logic to EBS session initialization.  Although this Note is written specifically for Oracle9i Label Security and EBS 11i, the techniques documented here remain valid today to later database and EBS releases:

Related Articles


Friday Feb 01, 2013

Grace Period Increased for Applying (some) Database Patchsets

It's crucial to maintain the database in your E-Business Suite environments by applying the latest database patchsets.  Database patchsets contain important security, performance, and stability updates. As of today, the latest database patchset certified with EBS is 11.2.0.3. We strongly recommend that all EBS customers should be running this patchset now.

Oracle Database release roadmap

Until now, whenever a new database patchset was released, you had up to 12 months to apply it.  This is called the grace period.  No new patches for the previous patchset would be released after that 12 month grace period.

Oracle's Server Technologies group has just increased the grace period for the second and later patchsets to two years.

This is easier to understand with an example:

  • 11.2.0.1 was the major release for the 11gR2 codeline.
  • 11.2.0.2 was the first patchset.  You had 12 months to apply that patchset once it was released.
  • 11.2.0.3 was the second patchset.  You now have 24 months to apply that patchset after its release.

For more information about these database support policies, see:

Related Articles

Thursday Oct 18, 2012

Frequently Asked Questions about Latest EBS Support Changes

Two important changes to the Oracle Lifetime Support policies for Oracle E-Business Suite were announced at OpenWorld.  These changes affect EBS Releases 11i and 12.1.

Timeline showing updated EBS Support dates

The changes are detailed in this My Oracle Support document:

A new document answering the top Frequently Asked Questions about these support changes is now available:

Questions answered in this new FAQ include:

  1. Why is Oracle providing an exception for Severity 1 Production Support for the first year of Sustaining Support for EBS 11.5.10?
  2. Will customers need to purchase an additional contract for the 11.5.10 Exception to Sustaining Support?
  3. What defines Severity 1 Production Support in the 11.5.10 Exception to Sustaining Support?
  4. What are the differences in the Lifetime Support Policy feature benefits from Extended Support to the Severity 1 Production Support in the 11.5.10 Exception to Sustaining Support?
  5. More questions about US 1099, Payroll legislative updates, security patches, and more

1. Changes for EBS 11i Sustaining Support

The first change is that  we will be providing an exception for the first 13 months of Sustaining Support on Oracle E-Business Suite Release 11.5.10 (11i10), valid from December 1, 2013 – December 31, 2014. This exception support will be comprised of three components:

  1. New fixes for Severity 1 production issues
  2. United States Form 1099 2013 year-end updates
  3. Payroll regulatory updates for the United States, Canada, United Kingdom, and Australia for fiscal years ending in 2014

Customers environments must have the minimum baseline patches (or above) for new Severity 1 production bug fixes as documented here:

2. Changes for EBS 12.1 Extended Support

More time:  Extended Support period for E-Business Suite Release 12.1 has been extended by nineteen months through December, 2018. Customers with an active Oracle Premier Support for Software contract will automatically be entitled to Extended Support for E-Business Suite 12.1.

Fees waived:  Uplift fees are waived for all years of Extended Support (June, 2014 – December. 2018) for customers with an active Oracle Premier Support for Software contract. During this period, customers will receive all of the components of Extended Support at no additional cost other than their fees for Software Update License & Support.

Where can I learn more?

There are two interlocking policies that affect the E-Business Suite:  Oracle's Lifetime Support policies for each EBS release (timelines which were updated by this announcement), and the Error Correction Support policies (which state the minimum baselines for new patches).

For more information about how these policies interact, see:

What about E-Business Suite technology stack components?

Things get more complicated when one considers individual techstack components such as Oracle Forms or the Oracle Database.  To learn more about the interlocking EBS+techstack component support windows, see these two articles:

Related Articles

Tuesday Oct 09, 2012

EBS 11i and 12.1 Support Timeline Changes

Two important changes to the Oracle Lifetime Support policies for Oracle E-Business Suite were announced at OpenWorld last week.  These changes affect EBS Releases 11i and 12.1.

The changes are detailed in this My Oracle Support document:

1. Changes for EBS 11i Sustaining Support

The first change is that  we will be providing an exception for the first 13 months of Sustaining Support on Oracle E-Business Suite Release 11.5.10 (11i10), valid from December 1, 2013 – December 31, 2014. This exception support will be comprised of three components:

  1. New fixes for Severity 1 production issues
  2. United States Form 1099 2013 year-end updates
  3. Payroll regulatory updates for the United States, Canada, United Kingdom, and Australia for fiscal years ending in 2014

Customers environments must have the minimum baseline patches (or above) for new Severity 1 production bug fixes as documented here:

2. Changes for EBS 12.1 Extended Support

More time:  Extended Support period for E-Business Suite Release 12.1 has been extended by nineteen months through December, 2018. Customers with an active Oracle Premier Support for Software contract will automatically be entitled to Extended Support for E-Business Suite 12.1.

Fees waived:  Uplift fees are waived for all years of Extended Support (June, 2014 – December. 2018) for customers with an active Oracle Premier Support for Software contract. During this period, customers will receive all of the components of Extended Support at no additional cost other than their fees for Software Update License & Support.

Where can I learn more?

There are two interlocking policies that affect the E-Business Suite:  Oracle's Lifetime Support policies for each EBS release (timelines which were updated by this announcement), and the Error Correction Support policies (which state the minimum baselines for new patches).

For more information about how these policies interact, see:

What about E-Business Suite technology stack components?

Things get more complicated when one considers individual techstack components such as Oracle Forms or the Oracle Database.  To learn more about the interlocking EBS+techstack component support windows, see these two articles:

Related Articles

Thursday Feb 26, 2009

On Apps Tier Patching and Support: A Primer for E-Business Suite Users

The Oracle Server Technologies division issued some important updates to their support policies in the following document:

I discussed the implications of the database-related policy updates for E-Business Suite users in this recently-published article.  It's time to discuss the implications of these policy updates for E-Business Suite application tier servers and externally-integrated Oracle Application Server instances.  This article also discusses the E-Business Suite application tier certification process and the safety of applying interim Fusion Middleware patches to your Apps environments. 

If you've read the previous article about database patching implications, parts of this new article will sound very familiar.  But stick with us; the implications for E-Business Suite application tier servers are subtly different and it's important that EBS sysadmins get the whole picture for both tiers.

[Read More]

Friday Feb 20, 2009

On Database Patching and Support: A Primer for E-Business Suite Users

The Oracle Server Technologies division has issued some important updates to their support policies in the following document:

These changes affect support policies for the database, Oracle Enterprise Manager, Fusion Middleware, and Collaboration Suite.  These changes are important enough to warrant an in-depth discussion about the implications of the database-related updates for E-Business Suite customers.  This article also discusses the E-Business Suite database certification process and the safety of applying interim patches to your Apps environments.  I'll cover the Apps-specific implications for the other technology products in a future article.

[Read More]

Tuesday Dec 30, 2008

Reminder: Migrate Your JInitiator Clients to Sun JRE Now!

[June 29, 2009 Update: The July 2009 desupport date for JInitiator 1.3 applies to E-Business Suite customers only. Generic Oracle Forms customers should see Note 761159.1 for generic JInitiator desupport dates.]

The significance of many problems lessens over time, so procrastination has its place as a stress management technique.  Unfortunately, putting off your EBS end-user migration from Oracle JInitiator to the native Sun Java plug-in doesn't fall into that category.  We are down to the last grains of sand in this particular hourglass.

Oracle E-Business Suite Release 11i end-users access Forms-based content either with the native Sun Java Runtime Engine (JRE) client or Oracle JInitiator.  Oracle JInitiator comes in two flavors: 1.8 and 1.3.  The sun is setting for both JInitiator versions.

Error Correction Support (ECS) for JInitiator 1.1.8 will end on December 31, 2008.  In other words, the Oracle Forms group will no longer issue bug fixes for the JInitiator 1.1.8 codeline as of tomorrow.

Error Correction Support for JInitiator 1.3 for E-Business Suite Release 11i customers will end on July 31, 2009.

Diagram showing Forms JRE JInitiator desktop client architecture layers

[Read More]

Thursday Sep 11, 2008

The Case of The Missing Database Links

[Sep 12, 2008 Update: Thanks to questions posted by readers in the comments and via private emails, I've confirmed that there are some EBS products -- including Advanced Planning (APS), Enterprise Data Warehouse (EDW), and Workflow -- that do use database links today. These products' usage of database links have been reviewed and approved by our architects because they do not invoke ATG (or AOL) code in any way, and because their functionality fundamentally requires a distributed architecture. More updates will follow on questions raised about G/L's use of database links via the Financial Statement Generator functionality.

Here's a scenario that might sound familiar to some of you: a customer built an extension for the E-Business Suite Release 11i using database links. When they upgraded their 9iR2 database to 10gR2, they were dismayed to find that those database links stopped working. They logged a Service Request and were surprised to be informed that, "Database links aren't supported with the E-Business Suite."

I ended up being involved in the resulting discussion. The support statement above isn't entirely correct, and the actual truth is more nuanced than you might think.  This case illustrates something much more fundamental about "certification" and "support" of generic database features and options that all EBS developers should understand.

[Read More]
About

Search

Categories
Archives
« April 2014
SunMonTueWedThuFriSat
  
1
4
5
6
7
8
9
10
11
12
13
14
19
20
21
22
23
24
25
26
27
28
29
30
   
       
Today