1st January 1900 Is Wrongly Saved In The Database
Last updated on SEPTEMBER 13, 2016
Applies to:Siebel Call Center - Version 22.214.171.124.17 [IP2013] and later
Information in this document applies to any platform.
The customer needs to set a UTC DateTime field to "01/01/1900" as they use that date as the "earliest possible time".
The problem they found is that if you write 1/1/1900 (even though you set the time 00:00:00 manually) in any UTC Date Time field in the GUI Siebel writes "12/31/1899 11:00:00" in the database instead.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms