Applies to:

Product Release: V7 (Enterprise)

Version: 7.5.3 [16157]
Database: Oracle 9i
Application Server OS: Microsoft Windows 2000 Server SP 4
Database Server OS: Microsoft Windows 2000 Server SP 4
This document was previously published as Siebel SR 38-1318546151.
Symptoms
Currently, due to British Summer Time, when a date is entered into Siebel, the
database will store the time as an hour behind. For example, a date entered as '
22/05/04' will be stored as '21/05/04 23:00. However, this is the date that is t
ransferred to the datawarehouse. When we use analytics to query this data BST is
not accounted for and the data looks as if it is a day behind, (that is 21/05/0
4 is displayed instead of 22/05/04).
Is there anyway to get analytics to use BST as Siebel GUI does?
The contact for this SR is Donna Askew.
Thanks.
Solution
Message 1
For the benefit of other readers:
This customer reported that their Siebel eBusiness Reports showed different Date
and Times to the reports generated from the Siebel Analytics application.
On further investigation it was revealed that the Siebel eBusiness data was bein
g stored as UTC Date and Time and therefore the date visible to the User in the
Siebel eBusiness application was different to that stored in the database.
As the Siebel Analytics application does not currently support UTC functionality,
the data was displayed as stored in the database, and not against the Users Time
Zone.
Change Request Nos. 12-CBTUOQ & 12-LXU03O have been raised to address this funct
ionality.
Change Requests are reviewed and prioritized and maybe fixed in a later release.
Please contact Siebel Technical Support if you wish your Service Request to be a
ssociated with these Change Requests so that you can track and monitor the statu
s and progress of these Change Requests on SupportWeb.
(1 of 2)
Message 2
The current workaround to address this issue temporarily is by saving the DateTi
me value in two or more columns (depending on where your Analytic Users are based
) at the Siebel eBusiness (OLTP) end and then utilizing the best DateTime column
s for the Analytics User in the ETL Process to ensure the columns they will be q
uerying can have the correct Date and Time.
Alternatively, review whether the Dates and Times need to be saved in UTC
if a better Data Type would be appropriate for saving these records.

Time and

Further information on the UTC functionality can be found in the "Global Deploym
ent Guide", "Configuring Applications for Global Deployments", Section "Global T
ime Zone support".
Regards,
Andrew Cox
Siebel Technical Support
Keywords: BST, GMT, PST. DST, Timezone, Time Zone, Time-Zone
(2 of 2)