The DSTv36timezone upgrade is now available and certified with Oracle E-Business Suite Releases 12.2.
Note: DST patches are cumulative and therefore include all previous Oracle DST updates.
How Does Oracle E-Business Suite Work Across Time Zones?
Periodically, a country or region changes their DST rules or timezone definitions. In addition, and more frequently, they may switch to or from Daylight Saving Time or Summer Time.
If your Oracle E-Business Suite environment is configured to support doing business across multiple time zones, you need to keep your timezone definition files up-to-date by applying patches as described in this article. This will ensure that the times transactions take place are recorded correctly, and thereby meet applicable business and legal requirements.
Is My Oracle E-Business Suite Environment Affected?
When a country or region changes its timezone definitions or DST rules, your Oracle E-Business Suite environment will require patching if either of the following is true:
Your EBS environment is located in the affected country or region
or
Your EBS environment is located outside the affected country or region, but you conduct business or have customers or suppliers there
The following are major additions or changes in the DSTv36 time zones definitions compared to the previous release:
Volgograd switches to Moscow time on 2020-12-27 at 02:00
Volgograd changes time zone from +04 to +03 on 2020-12-27 at 02:00
What Patches Do I Require?
The following MOS note identifies the various components in your Oracle E-Business Suite environment that may need DST patches:
Note: Proactive back ports 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 and your version requirements.
What if I Do Not Apply the Relevant Patches?
If you do business with a country or region that has changed its 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. Specifically, that transaction’s timestamp may be out by an hour.
Elke is a Product Manager in the Oracle E-Business Suite Applications Technology Group. She joined Oracle in 2011 after having been an Oracle customer and Oracle Technologist (Oracle Database Administrator, Oracle Applications DBA, Technical Architect and Technical Manager of an Oracle Applications DBA Team) since 1993. As part of the Oracle E-Business Suite Applications Technology Product Management Team, her scope of responsibility includes security, database certifications and advanced architectures for on-premises and Oracle Cloud deployments. She is a frequent contributor and editor of the Oracle E-Business Suite Technology Blog.
Elke is the lead author of the Oracle Applications DBA Field Guide (Apress 2006) and Oracle R12 Applications DBA Field Guide (Coqui Tech and Press 2010). Elke is also the founder of the Oracle Applications User Group (OAUG) E-Business Suite Applications Technology Special Interest Group (SIG) and served as President of the SIG from February 2005 - August 2011. Elke has been a speaker at the Oracle OpenWorld and Collaborate conferences since 2004. Prior to joining Oracle, Elke was designated an Oracle ACE (2007) and Oracle ACE Director (2009). She received the OAUG Oracle Ambassador of the Year award in 2015.
Elke has a Computer Science Degree and a Masters of Business Administration from the University of Oklahoma. In her spare time, Elke enjoys traveling especially to Europe, Puerto Rico and the amazing US National Parks. Elke also enjoys hiking, antiquing, gardening and cooking.
