Last updated on JUNE 20, 2017
Applies to:Siebel Financial Services Call Center - Version 15.12 [IP2015] and later
Information in this document applies to any platform.
According to various other postings, the LAST_LOGIN_TS column on table S_USER is used to track when users last LOGGED OFF (as oppose to logged in per the name). However, it was noticed that the timestamp is off a few hours. UTC is enabled.
For instance, let's say the user is in EST timezone and logs out of the application at 1:00PM ET. We see LAST_UPD stored as 4:00PM GMT, which is correct as it is converted to 1:00PM ET. However, we see LAST_LOGIN_TS having a timestamp of 8:00PM, which does not seem to correlate to anything.
What causes the LAST_LOGIN_TS field to offset a few hours?
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms