[Nov. 22, 2010 Update: Office 2010 (32-Bit) is now certified with the E-Business Suite; see this article for details]
Microsoft Office 2003 and 2007 are certified with Oracle E-Business Suite Release 11i and 12. While this isn't a new announcement, per se
, a recent surge of Office-related questions suggests that it's worth covering this topic here.
How does the E-Business Suite work with Microsoft Office?
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 these integrations include:
What Does "Certified" Mean?
- 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
It's easy enough to state
that Oracle E-Business Suite is certified with Microsoft Office. But
the E-Business Suite is a collection of multiple products, just like
Microsoft Office. So what does the generalized statement of
"certified" really mean?
an E-Business Suite team integrates their product with Microsoft
Office, they are responsible for ensuring that these integrations
continue to work with all of their new releases and patches. They are
also responsible for testing their products with new versions of
Microsoft Office, including major Office patches and Service Packs.
When a specific
product team completes their testing of their product with a given
version of, say, Microsoft Excel 2007, they are permitted to state that
their product is certified with that Office version and component.
teams with Office dependencies complete their tests of, say, E-Business
Suite 12 with Office 2007, then we consider that E-Business Suite
release to be certified with that version of Microsoft Office.
Where are these integrations documented?
product teams are responsible for ensuring that their product
documentation describes their integration points and procedures for
using Microsoft Office. This documentation is decentralized and
distributed today, and I would expect things to continue along those
We understand that it would be helpful to have a
central document that acts like a Table of Contents or integration
roadmap with pointers to the product-specific Office documentation.
We've scheduled this documentation project; watch this blog for more
details when that supplemental documentation is released.
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.
example, you might be trying to take advantage of CRM Marketing (AMS)
12.1.2's integration with Excel 2007. 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.
What about Microsoft Office 2010?
Microsoft has recently released a beta of Office 2010
Our EBS product teams are evaluating this release now. I'll post more
details about our plans for certifying Office 2010 with the E-Business
Suite as soon as they're available.
What about StarOffice and OpenOffice variants?
Our existing E-Business Suite integrations with Microsoft are built on
a variety of published Microsoft technologies, including Microsoft's
Visual Basic (VBA) macro functions and Microsoft document filetypes.
StarOffice, OpenOffice and its many open source variants
offer a lot of functionality that is very similar or equivalent to
Microsoft Office. However, these open source applications are not
drop-in replacements for their Microsoft Office equivalents, given that
they do not offer VBA macro compatibility.
organisation currently uses Microsoft Office with the E-Business Suite
and is considering a large-scale cutover from Microsoft Office to
OpenOffice or another open source equivalent, please drop me an email
with the following details:
preceding is intended to outline our general product direction. It is
intended for information purposes only, and may not be incorporated
into any contract. It is not a commitment to deliver any material,
code, or functionality, and should not be relied upon in making
purchasing decision. The development, release, and timing of any
features or functionality described for Oracle's products remains at
the sole discretion of Oracle.
- Name of your organisation
- EBS Release (e.g. 126.96.36.199, 12.1.2)
- EBS+Office integrations that you're using today
- Microsoft Office version that you're using today
- Number of end-user desktops affected
- Windows versions used by those EBS+Office end-users
- OpenOffice distribution and versions to be deployed
- Will there be a mix of Microsoft Office and OpenOffice deployments?
- Migration schedule to OpenOffice or open source equivalent