DSTv27 is now available and certified with Oracle E-Business Suite Release 12.2. The DSTv27 update includes the timezone information from the IANA tzdata 2016f. 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:
The latest DSTv27 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:
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.
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.