[Editor Update May 21, 2008: Nilesh has moved on to another team within Oracle and, sadly, is no longer an active contributor to this blog. Feel free to direct any questions about his posted articles directly to Steven Chan, instead.]
[Editor Feb 2, 2007 Update: A recording of the first webcast discussing these changes is available here. A second webcast will be held on Feb 14, 2007]
[Editor Feb 2, 2007 Update: A recording of the first webcast discussing these changes is available here. A second webcast will be held on Feb 14, 2007]
The Energy Policy Act of 2005 was passed by the US Congress and then signed into law by President George W. Bush on August 8, 2005. Under
the new law, Daylight Saving Time begins three weeks earlier in 2007 and is also extended one month for most of the United States:
- Daylight Saving Time begins: 2:00 a.m on the second
Sunday of March
- Daylight Saving Time ends: 2:00 a.m. on the first
Sunday of November
These changes will affect an Apps system that has specific setups that include one of the affected time zones. The effects are limited to date values that contain a time component. Time values, recorded or displayed, may be offset by one hour from the actual time. In most circumstances this will not impact E-Business Suite systems or will cause minor inconvenience.
With this in mind, Oracle foresees that only a small number of EBS customers will need to address this issue. As always, we would appreciate your help in validating this assumption. If you believe that your organization may experience other significant side-effects, please let us know — either by posting a comment to this article, or by emailing us directly.
A Quick Primer on Dates in Apps
Conceptually, there are two types of date fields:
- Dates with a time component which indicates a specific point in time.
- Dates without a time component which shows a day but not a specific time.
- EBS Databased running in an affected time zone
- EBS users with the Client Timezone profile option set to affected time zones. This profile option is accessible from user preferences in self-service web pages.
- Product communications to and from another system running in an affected time zone.
- Product features that have specific time zone functionality
The new Daylight Saving Time changes start in March 2007:
Year DST Begins DST
Ends
-
2007
March
11
November 4 -
2008
March
9
November 2 -
2009
March
8
November 1 -
2010
March
14
November 7 -
2011
March
13
November 6 -
2012
March
11
November 4 -
2013
March
10
November 3 -
2014
March
9
November 2 -
2015
March
8
November 1
These changes affect Canada as well. Mexico is still using the old Daylight Saving Time rules.
For more information on how this impacts Oracle Database and Fusion Middleware, see:
- USA 2007 Daylight Saving Time(DST) Compliance for Database and Fusion Middleware (Metalink Note 397281.1)
For more information on how this impacts E-Business Suite environments, see:
- Impact of US 2007 Timezone Changes on E-Business Suite Environments (Metalink Note 403311.1)
Related
- Daylight Saving Time 2007 Forum on Metalink Now Open
- Invitation to US 2007 Daylight Saving Time Webcast #2
- User Preferred Time Zone Support in the E-Business Suite 11.5.10 CU2 (Metalink Note 330075.1)
- Australian Western Daylight Time (AWDT) Change E-Business Suite Recommendations (Metalink Note 401006.1)