Steven Chan

Subscribe to Steven Chan feed
Oracle Blogs
Updated: 11 hours 47 min ago

Oracle Technology Patch Versioning Changed

Thu, 2016-12-15 02:06

Version numbering for Oracle Database, Enterprise Manager, and Fusion Middleware products began to change after November 2015. The new version format makes it easier to see which bundle patches are from which time-frame, and in particular which patches are from the same Critical Patch Update release. 

This change is documented here:

Some bundles may continue to use a numeric 5th digit in the short term, but will transition to the new format over time.

What changed?

The new format replaces the numeric fifth digit of the bundle version with a release date in the form  "YYMMDD" where:

  • YY is the last 2 digits of the year
  • MM is the numeric month (2 digits)
  • DD is the numeric day of the month (2 digits)

The "release date" is the release date of the main bundle / PSU / SPU. In some rare cases, for example where the same bundle is released on multiple platforms, the patch for a specific platform may not be available until some days after the "release date".

Related Articles

Categories: APPS Blogs

What is the Impact of SHA-1 Desupport on EBS?

Wed, 2016-12-14 02:05

Given that Certificate Authorities have already stopped issuing SHA-1 certificates, most likely, you have already addressed the use of SHA-1 certificates for inbound connections by migrating to SHA-2 certificates. In case you have not, this is a reminder for you to do so.

What's Happening with Browsers?

Many browsers (eg, Google Chrome, MS IE) have now published their desupport plans for SHA-1. The timeline for desupport of SHA-1 is dependent on your certificate authority and your browser.

You need to ensure that your inbound connections are using SHA-2 signed PKI certificates. If you do not move to a SHA-2 certificate and the end-user browser requires one, your Oracle E-Business Suite users will receive a warning or error.

What Do You Need to Do?

Following the instructions in our documentation to meet the minimum requirements for using SHA-2 signed PKI certificates with Oracle E-Business Suite.

For TLS 1.2, refer to the following:

For TLS 1.0 and SSLv3, refer to the following:

Note: TLS 1.2 is the latest version certified with Oracle E-Business Suite Release 12.2 and 12.1. As a reminder, we recommend that you migrate to TLS 1.2 for Oracle E-Business Suite Release 12.2 and 12.1.


Related Articles

Categories: APPS Blogs

Does Flashback Data Archive work with EBS?

Tue, 2016-12-13 02:05

Flashback Data Archive is a group of Oracle Database features that that let you view past states of database objects or to return database objects to a previous state without using point-in-time media recovery. Oracle Flashback features use the Automatic Undo Management (AUM) system to obtain metadata and historical data for transactions. They rely on undo data, which are records of the effects of individual transactions.

Flashback Data Archive was formerly known as Total Recall.  Flashback Data Archive is licenced via the Oracle Advanced Compression (ACO) database option.

Oracle Flashback Data Archive diagram

Oracle Flashback is not explicitly certified with the E-Business Suite, but it is supported.  We do not currently publish any Best Practices whitepapers with guidance on how to use Flashback Data Archive with EBS.  The generic Oracle Flashback Technology documentation is applicable to E-Business Suite databases.

Related Articles

Categories: APPS Blogs

Microsoft Ending Support for Office 2007 in October 2017

Mon, 2016-12-12 02:05

Microsoft Office 2007 logoMicrosoft is ending support for Office 2007 on October 10, 2017.  The official announcement is published here:

Microsoft will stop producing security updates and non-security updates for Office 2007 after that date.

Office 2007 included Word, Outlook, Excel, PowerPoint and others.  EBS integrations with these products are 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 October 2017?

After Microsoft desupports Office 2007 in October 2017:

  • Oracle Support will continue to assist, where possible, in investigating issues that involve Office 2007.
  • Oracle's ability to assist may be limited due to limited access to PCs running Office 2007.
  • Oracle will continue to provide access to existing EBS patches for Office 2007 issues.
  • Oracle will provide new EBS patches only for issues that can be reproduced on later Office versions that Microsoft is actively supporting (e.g. Office 2010, Office 2013, Office 2016).

What should EBS customers do?

Oracle strongly recommends that E-Business Suite customers upgrade their desktops from Office 2007 to the latest certified equivalents.  As of today, those are Office 2010, Office 2013, and Office 2016.

Related Articles

Categories: APPS Blogs

AMP Required as Minimum Baseline for EM 12c

Fri, 2016-12-09 02:05

The first Application Management Pack (AMP) plug-in for Oracle Enterprise Manager 12c was released in 2012.  We have released several updates since then, including AMP,, and  Most recently, we released AMP Bundle Patch 3 in February 2016.

The minimum baseline for new Application Management Pack patches for EM 12c has been raised to AMP  All new patches and updates for Application Management Pack 12.1 running on EM 12c will require AMP

For details about upgrading your AMP plug-in to the new AMP minimum patching baseline, see:

Upgrade to AMP 13

If you are still running any version of AMP 12.x, we strongly encourage you to upgrade to Application Management Pack 13 running on Enterprise Manager Cloud Control 13c Release 2 (13r2).  For details, see:

Related Articles

Categories: APPS Blogs

Updated: Why Does EBS Integration with Oracle Access Manager Require Oracle Internet Directory?

Thu, 2016-12-08 02:05

[The article applies to EBS 12.1 and 12.2; it is an updated version of this older article that covered EBS 12.0 and 11i]

The E-Business Suite has its own security and user-management capabilities.  You can use the E-Business Suite's native features to authenticate users, authorize users (i.e. assign responsibilities to them), and manage your EBS user repository.  The majority of E-Business Suite system administrators simply use these built-in capabilities for enabling access to the E-Business Suite.

When EBS built-in capabilities aren't enough

Some organisations have third-party user authentication systems in place.  These include CA Netegrity SiteMinder, Windows Kerberos, and others.  These organisations frequently use third-party LDAP directory solutions such as Microsoft Active Directory, OpenLDAP, and others. 

We don't certify the E-Business Suite with those third-party products directly, and we don't have any plans to do so.  This article is intended to explain why Oracle Internet Directory (OID) is required when integrating with Oracle Access Manager (OAM). 

OAM and OID are mandatory for third-party integration

Oracle Internet Directory and Oracle Access Manager are mandatory requirements when integrating third-party authentication products directly with the E-Business Suite.

It is not possible to integrate E-Business Suite directly with Microsoft Active Directory, Windows Kerberos, or CA Netegrity Siteminder directly.

It's possible to integrate the E-Business Suite with those third-party solutions via Oracle Access Manager and Oracle Internet Directory.  See these articles:

Before going on, I'd recommend reading that third-party integration articles.  If you don't have those concepts under your belt, the rest of this article isn't going to make much sense.

Architecture diagram showing Oracle Access Manager Oracle Internet Directory E-Business Suite AccessGate WebGate

Why does EBS require OID with OAM?

Oracle Access Manager itself doesn't require Oracle Internet Directory.  However, Oracle Internet Directory is a mandatory requirement when Oracle Access Manager is integrated with the E-Business Suite.

Why?  The short answer is that the E-Business Suite has hardcoded dependencies on Oracle Internet Directory for this configuration. These dependencies mean that you cannot replace Oracle Internet Directory with any third-party LDAP directory for this particular configuration. 

There are two cases of hardcoded dependencies on Oracle Internet Directory:

1. Reliance on Oracle GUIDs

From the articles linked above, you know that user authentication is handled by Oracle Access Manager, and user authorization is handled by the E-Business Suite itself.  This means that there are two different user namespaces. 

These namespaces must be linked and coordinated somehow, to ensure that a particular user logging in via Oracle Access Manager is the same user represented within the E-Business Suite's own internal FNDUSER repository.

We associate externally-managed Oracle Access Manager users with internally-managed E-Business Suite users via a Global Unique Identifier (GUID).  These Global Unique Identifiers are generated exclusively by Oracle Internet Directory. 

The E-Business Suite has hardcoded functions to handle the mapping of these Global Unique Identifiers between Oracle Access Manager and the E-Business Suite.  These mapping functions are specific to Oracle Internet Directory; it isn't possible to replace Oracle Internet Directory with a generic third-party LDAP directory and still preserve this functionality.

2. Synchronous user account creation

The E-Business Suite is predominantly used internally within an organisation.  Certain E-Business Suite application modules can be made visible to users outside of an organisation.  These include iStore, iRecruitment, iSupplier, and other application modules where the users aren't necessarily restricted to an organisation's own employees.

Users of some of those application modules expect to be able to register for a new account and use it immediately.  This makes sense.  If you're posting job openings via iRecruitment, potential applicants shouldn't need to hold off on submitting their resumes while your E-Business Suite sysadmin creates an account manually, assigns EBS responsibilities, and emails them the account login details. They'll be long gone before that happens.

This means that EBS application modules that support self-registration must create user accounts synchronously.  A new account must be created within the E-Business Suite and the externalized directory at the same time, on demand.

The E-Business Suite has hardcoded dependencies upon Oracle Internet Directory function calls that handle these synchronous account creation tasks.  These function calls are specific to Oracle Internet Directory; it isn't possible to replace Oracle Internet Directory with a generic third-party LDAP directory and still preserve this functionality.

Related Articles

      Categories: APPS Blogs

      New OA Framework 12.2.5 Update 8 Now Available

      Wed, 2016-12-07 02:05

      Web-based content in Oracle E-Business Suite 12 runs on the Oracle Application Framework (OAF or "OA Framework") user interface libraries and infrastructure.  Since the release of Oracle E-Business Suite 12.2 in 2013, we have released several cumulative updates to Oracle Application Framework to fix performance, security, and stability issues. 

      These updates are provided in cumulative Release Update Packs, and cumulative Bundle Patches that can be applied on top of the Release Update Pack. "Cumulative" means that the latest RUP or Bundle Patch contains everything released earlier.

      The latest OAF update for EBS 12.2.5 is now available:

      OA Framework 12.2.5 Update 8

      Where is the documentation for this update?

      Instructions for installing this OAF Release Update Pack are here:

      Who should apply this patch?

      All EBS 12.2.5 users should apply this patch.  Future OAF patches for EBS 12.2.5 will require this patch as a prerequisite. 

      What's new in this update?

      This bundle patch is cumulative: it includes all fixes released in previous EBS 12.2.5 bundle patches.

      This latest bundle patch includes new fixes for the following critical issues:

      • Formatting issues with Email notifications after 12.2.5 upgrade.
      • Popup is not rendering correctly with Right-to-Left language sessions in Internet Explorer when default browser language is set as Arabic.
      Related Articles
      Categories: APPS Blogs

      Troubleshooting RAC Cloning Issues in EBS 12.1

      Tue, 2016-12-06 02:09

      We have a white paper that outlines a framework for troubleshooting Rapid Clone issues:

      Cloning EBS 12.1.3

      Things can get more-involved if your E-Business Suite environment uses Real Application Clusters (RAC). There's another white paper that has more details about what to do if you encounter problems when cloning RAC-based EBS environments:

      This whitepaper has additional RAC-specific information, such as:

      • Pairsfile.txt
      • RMAN restore phases
      • Secondary node context file creation
      • Known issues (e.g. RAC to RAC cloning causing inventory registration issues)

      Related Articles

      Categories: APPS Blogs

      Ten Years and Counting

      Mon, 2016-12-05 02:05

      This blog turned 10 this year.  When I started it in 2006 with this article, I had no idea that it would become what it is today.  Things certainly turned out differently than I expected. 

      Photo credit: Fulvio Spada, Wikimedia Commons

      This little blog now gets millions of visits a year.  It has helped us shape EBS to meet your needs better.  I've been schooled in the many ways that we can do things better for you.  I've been chastised for offhand editorial remarks and have learned to deal with hate mail.  I've learned how hard it is to be a journalist, to state just the facts and pare prose down to its simplest form, accessible to all (with this verbose article being an exception to that rule).

      Over the years, I've had several people who have helped me paint this fence. Some of those people have since joined the ranks of Oracle's esteemed alumni.  Some still pitch in occasionally.  Either way, I'm grateful for their contributions over the years.  As with the Stone Soup parable, this little corner of the world is richer for their sharing their expertise with us.

      I am sometimes mistaken as an expert, but the real experts are my colleagues and friends in the E-Business Suite division and our sister organizations across Oracle.  They deserve the real credit for all of their dedication, professionalism, and expertise. They are a brilliant team and I am always humbled by their desire to do the best for you.  I am privileged to work alongside them and talk about their achievements on their behalf.  Please join me in thanking all of them for their hard work in polishing EBS to a shine for you. 

      And, of course, thank you for joining me on this journey.  I am fortunate to have many of the world's leading EBS experts as readers and friends, and they contribute to this blog in ways large and small.  This blog would not be the same without the lively interactions with all of you.  I look forward to seeing what lies down the road around the corner!

      Categories: APPS Blogs

      Database Vault Certified with EBS 12.1 and 12.2

      Fri, 2016-12-02 02:05

      Oracle Database Vault allows security administrators to protect a database from privileged account access to application data.  Database objects can be placed in protected realms, which can be accessed only if a specific set of conditions are met.

      We are pleased to announce that Oracle Database Vault 12c is now certified with Oracle E-Business Suite Release 12.2 and 12.1. To integrate Oracle Database Vault 12c with Oracle E-Business Suite Release 12.2 or 12.1, follow the instructions in the corresponding My Oracle Support Knowledge Document:

      Note:  We deliver a default realm via two different patches for Oracle E-Business Suite 12.2 and 12.1 .  You may use the default realm as-is or choose a subset.

      Pending Certifications with External Integrations

      The following two configurations are still underway and pending:

      • Single Sign-On Integration with Oracle Access Manager
      • Oracle Discoverer

      Oracle's Revenue Recognition rules prohibit us from discussing certification and release dates, but you're welcome to monitor or subscribe to this blog. I'll post updates here as soon as soon as they're available.   


      Related Articles

      Categories: APPS Blogs

      Which Oracle Internet Directory Patchsets Can Be Used With EBS?

      Thu, 2016-12-01 02:05
      You can apply any Oracle Internet Directory (OID) bundle patchsets that have been certified at the fourth-level digit to a certified Oracle E-Business Suite release.  The fifth-level digit in OID versions is not relevant to E-Business Suite certifications. 

      For example, we have certified EBS 12.2 with OID All of the following Oracle Internet Directory patchsets will work with EBS 12.2:

      • Oracle Internet Directory (documented certification)
      • Oracle Internet Directory
      • Oracle Internet Directory

      This is sometimes shown in our documentation in either of the following ways:

      • Oracle Internet Directory
      • Oracle Internet Directory

      The absence of a fifth-digit or the presence of an 'X' in the fifth digit's place means any fifth-digit level updates may be applied to an Oracle Internet Directory environment integrated with EBS 12.2 without requiring a new certification.  This applies to all environments, including test and production environments.


      Related Articles

      Categories: APPS Blogs

      Load-Balancing EBS 12.2 Environments

      Wed, 2016-11-30 02:06
      You can use load-balancing routers (LBR) to protect your E-Business Suite 12.2 environment from system failures.  Load-balancers increase your environment's fault-tolerance and scalability by distributing load across a pool of servers. See: HTTP Layer Load-Balancing

      HTTP Layer load-balancing is the most common method used in E-Business Suite environments. In this configuration, end-users navigate to a specific Web Entry Point that represents your E-Business Suite's domain name.  An HTTP Layer load-balancer routes all subsequent traffic for a specific user to a specific Web Node.

      EBS LBR Architecture

      HTTP Layer load-balancers may use heartbeat checks for node death detection and restart, and sophisticated algorithms for load-balancing.

      DNS-Based Load-Balancing

      When an end-user's browser attempts to access your E-Business Suite environment, your local Domain Name Server (DNS) can direct that user to a specific application server in a pool based on available capacity:

      Traffic for that user's session will be handled by the application server, while other users' traffic may be directed to other application servers in the pool.  Like HTTP layer load-balancers, many DNS-based load-balancers use heartbeat checks against nodes and sophisticated algorithms for load-balancing.

      Minimum Requirement:  Session Persistence

      Oracle doesn't certify specific load-balancers or networking hardware with the E-Business Suite.  We've designed the E-Business Suite to be able to use load-balancers in general. Our instructions for configuring load-balancers should work for all standards-compliant networking solutions, whether they are hardware or software-based.

      The minimum requirement is that a load-balancer support session persistence.  Persistence describes a mode where a client's initial HTTP connection is directed to a particular application server, and then subsequent HTTP requests from that client are directed to the same server.  As long as a load-balancer is able to handle session persistence (also referred to as "stickiness"), it's likely to work with the E-Business Suite.

      Other load-balancing variations

      EBS 12.2 can be deployed in a number of variations to handle specialized or advanced load-balancing requirements.  For details about implementing the following variations, see:

      WLS Clusters: EBS 12.2 uses WebLogic Server.  It is possible to deploy multiple WebLogic Server instances in a cluster to increase scalability and fault-tolerance. A cluster appears to clients to be a single WebLogic Server instance. The server instances that constitute a cluster can run on the same machine, or be located on different machines. You can increase a cluster’s capacity by adding additional server instances to the cluster on an existing machine, or you can add machines to the cluster to host the incremental server instances. Each server instance in a cluster must run the same version of WebLogic Server.

      Multiple Web Entry Points:  It is possible to configure the same EBS environment to have multiple web entry points (URLs).  For example, users might be able to access your EBS environment via the following different URLs:


      Functional redirection:  It is possible to direct users to specific servers based upon the functional responsibilities that they chose.  For example, manufacturing end-users may be directed to a different pool of servers than, say, HRMS end-users.

      Related Articles

      Categories: APPS Blogs

      EBS Presentations at December 2016 UK Oracle User Group Meeting

      Tue, 2016-11-29 02:05
      Staff from Oracle E-Business Suite Development will be contributing to the APPS16 track of the UKOUG Conference & Exhibition 2016. The conference takes place at the International Convention Centre, Birmingham, England, and runs from Sunday 4th December to Wednesday 7th December.

      Please bring your questions or issues about any aspect of running EBS: feel free to ask about overall strategy, specific deployment aspects, or anything else you want to know.

      You'll also have the chance to attend numerous formal presentations from prominent Oracle speakers on many aspects of EBS. Here are some highlights.

      On the Monday (5th), there is a great opportunity to hear the latest news from the general manager of EBS:

      Another presentation that will be of particular interest to readers of this blog is:

      General EBS presentations include:

      And last but not least, don't miss the chance to hear about EBS Release 12.2 online patching feature from one of its architects:

      You'll also be well placed to attend the TECH16 track, where you can learn about the latest developments in Oracle Database and other technologies.

      We look forward to seeing you at APPS16!


      Related Articles
      Categories: APPS Blogs

      Will EBS Work with Microsoft Unified Update Platform?

      Mon, 2016-11-28 02:00

      Windows 10 logoMicrosoft is changing their packaging of major Windows 10 updates from full operating system downloads to smaller, incremental downloads.  This new delivery method is called the Unified Update Platform (UUP).

      The new UUP delivery method will provide only the Windows 10 patches that have been released since the last time a desktop was updated.  Microsoft currently expects to switch to this new delivery method after the Windows 10 Creators Update is released in early 2017.

      Will this work with EBS?

      Yes.  Windows 10 is certified with all current EBS releases, including EBS 12.1 and 12.2.  This new delivery method is not expected to change that.

      Microsoft emphasizes that nothing changes with Windows 10 itself -- this only modifies the way that Win10 patches are delivered:

      It’s important to note that with UUP, nothing will look or behave differently on the surface, UUP is all underlying platform and service optimization that happens behind the scenes.

      Related Articles

      The 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.

      Categories: APPS Blogs

      Reminder: Upgrade to EM

      Fri, 2016-11-18 02:05

      Oracle periodically produces Fusion Middleware patchsets -- cumulative collections of fixes -- between major product releases.  All Oracle customers have a limited amount of time 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. 

      What is the impact on EBS customers using Application Management Pack?

      Enterprise Manager was released in June 2015.  Oracle continued to create new patches for EM until June 2016.  New patches for EM are no longer available. New patches are being created only for EM

      EBS 12.1 and 12.2 customers who need new patches for their Enterprise Manager components must be on EM and AMP BP3, at minimum.  No new patches for earlier versions of AMP will be available.

      EBS customers should consider upgrading to Enterprise Manager 13c and AMP 13.1 or higher:

      Related Articles

      Categories: APPS Blogs

      Oracle Enterprise Manager 12.1 Support Dates Changed

      Thu, 2016-11-17 02:08

      Two important changes have been made to Oracle Enterprise Manager 12.1 Lifetime Support dates:

      1. Extended Support fees have been waived for the first year up to October 31, 2017
      2. Extended Support now ends on October 31, 2020 (one extra year of Extended Support)

      These changes are published here:

      Impact on EBS customers

      These support changes apply to E-Business Suite customers using Application Management Pack released as part of Oracle Application Management Suite for Oracle E-Business Suite. 

      EBS customers should consider upgrading to Enterprise Manager 13c and AMP 13.1 or higher:

      Categories: APPS Blogs

      E-Business Suite Technology Codelevel Checker Updated for EBS 12.2

      Wed, 2016-11-16 02:05

      The E-Business Suite Technology Codelevel Checker (ETCC) tool helps you identify missing application tier or database bugfixes that need to be applied to your E-Business Suite Release 12.2 system. ETCC maps missing bugfixes to the default corresponding patches and displays them in a patch recommendation summary.

      What's New

      ETCC was recently updated to include bug fixes and patching combinations for the following:

      • October 2016 WebLogic Server (WLS) Patch Set Update (PSU)
      • October 2016 Database Patch Set Update and Bundle Patch
      • July 2016 Database Patch Set Update and Bundle Patch
      • July 2016 Database Cloud Service (DBCS) / Exadata Cloud Service (ExaCS) service

      Obtaining ETCC

      We recommend always using the latest version of ETCC, as new bugfixes will not be checked by older versions of the utility. The latest version of the ETCC tool can be downloaded via Patch 17537119 from My Oracle Support.

      Related Articles


      Categories: APPS Blogs

      DSTv28 Timezone Patches Available for E-Business Suite 12.1 and 12.2

      Tue, 2016-11-15 02:04
      Hourglass iconIf your E-Business Suite Release environment is configured to support Daylight Saving Time (DST) or international time zones, it's important to keep your timezone definition files up-to-date. They were last changed in October 2016 and released as DSTv27.

      DSTv28 is now available and certified with Oracle E-Business Suite Release 12.1 and 12.2. This update includes the timezone information from the IANA tzdata 2016g.  It is cumulative: it includes all previous Oracle DST updates. 

      Is Your Apps Environment Affected?

      When a country or region changes DST rules or their time zone definitions, your Oracle E-Business Suite environment will require patching if:

      • Your Oracle E-Business Suite environment is located in the affected country or region OR
      • Your Oracle E-Business Suite environment is located outside the affected country or region but you conduct business or have customers or suppliers in the affected country or region

      The latest DSTv28 timezone definition file is cumulative and includes all DST changes released in earlier time zone definition files. DSTv27 includes changes to the following timezones since the DSTv24 release:

      • Asia/Rangoon
      • Asia/Istanbul
      • Europe/Istanbul
      • Turkey

      What Patches Are Required?

      In case you haven't been following our previous time zone or Daylight Saving Time (DST)-related articles, international timezone definitions for E-Business Suite environments are captured in a series of patches for the database and application tier servers in your environment. The actual scope and number of patches that need to be applied depend on whether you've applied previous DST or timezone-related patches. Some sysadmins have remarked to me that it generally takes more time to read the various timezone documents than it takes to apply these patches, but your mileage may vary.

      Proactive backports of DST upgrade patches to all Oracle E-Business Suite tiers and platforms are not created and supplied by default. If you need this DST release and an appropriate patch is not currently available, raise a service request through support providing a business case with your version requirements.

      The following Note identifies the various components in your E-Business Suite environment that may need DST patches:

      What is the business impact of not applying these patches?

      Timezone patches update the database and other libraries that manage time. They ensure that those libraries contain the correct dates and times for the changeover between Daylight Savings Time and non-Daylight Savings Time.

      Time is used to record events, particularly financial transactions.  Time is also used to synchronize transactions between different systems.  Some organizations’ business transactions are more-sensitive to timezone changes than others. 

      If you do not apply a timezone patch, and do business with a region that has changed their timezone definitions, and record a transaction that occurs at the boundary between the “old” and the “new” time, then the transaction may be recorded incorrectly. That transaction's timestamp may be off by an hour. 

      For example:

      • An order is placed for a customer in a country which changed their DST dates in DST v27
      • The old Daylight Savings Time expiration date was Nov. 2
      • The new Daylight Savings Time expiration date is now October 31
      • An order is set to ship at 12am on November 1st
      • Under the old Daylight Savings Time rules, the revenue would be recorded for November
      • Under the new Daylight Savings Time rules, the revenue would be recorded for October

      Related Article

      Oracle's Revenue Recognition rules prohibit us from discussing certification and release dates, but you're welcome to monitor or subscribe to this blog. I'll post updates here as soon as soon as they're available.   

      Categories: APPS Blogs

      Application Management Pack Certified with Enterprise Manager 13.2

      Mon, 2016-11-14 02:05

      In July 2016, we announced the general availability of Oracle Application Management Suite for Oracle E-Business Suite as a plug-in for Enterprise Manager Cloud Control 13c. Application Management Suite is now certified as a plug-in with Oracle Enterprise Manager Cloud Control 13c Release 2.

      EM 13cR2 compatibility

      We encourage all customers to upgrade to the latest release of Oracle Enterprise Manager 13.2 and Oracle Application Management Pack If you are planning to manage Oracle E-Business Suite cloud environments, you must be on Oracle Enterprise Manager 13c and Oracle Application Management Pack Release with latest patches listed in the Note below.


      For release details and product documentation links, see:

      Downloading this update

      Oracle Application Management Suite for Oracle E-Business Suite can be downloaded and installed by:

      Related Article

      Categories: APPS Blogs

      Troubleshooting Cloning Issues in EBS 12.1

      Tue, 2016-11-08 02:06

      The Rapid Clone tool is used to create a working identical copy of an existing Oracle E-Business Suite 12.1 environment.  There are several ways of using Rapid Clone, including cloning a single node environment to another single node environment, adding additional nodes to an existing environment, and reducing nodes when cloning a multinode environment to a single node clone. 

      Cloning EBS 12.1.3

      The guide to using Rapid Clone in EBS 12.1 environments is:

      When things go wrong

      Given the variety of ways that this tool can be used, it is inevitable that some things might not go as expected.  When that happens, it's helpful to have a troubleshooting framework to narrow down the possible root causes and identify a solution. 

      If you've encountered a problem with Rapid Clone, your first stop should be:

      This excellent Note covers the most-common questions and issues associated with Rapid Clone, such as:

      • Location of cloning log files
      • Missing prerequisite patches
      • Preparing the source system's database and application tiers
      • The expected layout of the cloning stage area for both the applications and database tiers
      • Execution of the cloning process
      • Inventory registration issues
      • Common issues when cloning the database tier
      • Known issues

      Related Articles

      Categories: APPS Blogs