Wrong END_DATE In Signon Audit Users(FNDSCSRU) In Case Of Forceful Log Out
(Doc ID 1613130.1)
Last updated on FEBRUARY 20, 2019
Applies to:
Oracle Application Object Library - Version 12 to 12.1.3 [Release 12 to 12.1]Oracle Concurrent Processing - Version 12.1.3 to 12.1.3 [Release 12.1]
Information in this document applies to any platform.
Symptoms
In EBS 12.1.3, Signon Audit Users report (FNDSCSRU) returns incorrect 'End Active Time'
after a timeout and when a user exits the application session in an unsupported/improper way e.g. by only closing the browser.
Steps
-----
1-Apply both patch 11904176 and patch 9612674 and verify the file versions:
AFSCSGNS.pls 120.4.12010000.3 + AFSCSGNB.pls 120.8.12010000.5 (query User_Source)
FNDSCSRU.rdf 120.9.12010000.7 (using adident)
2-Log into EBS as user TESTUSR and navigate to forms-based apps,
3-Let the session time out and choose "No" when prompted by the system whether you would like to login or not,
4-Close the browser by only clicking on the 'X' without a proper logout.
5-Run the report and the 'End Active Time' can have a value or be NULL,
Ex:
Session Number=1083552, End Active Time=22-JUL-13 14:35
Session Number=1083967, End Active Time=NULL
6-Repeat the above steps and the report this time returns another value for 'End Active Time' for the same Session Number.
Ex:
Session Number=1083552, End Active Time=22-JUL-13 14:35
Session Number=1083967, End Active Time=22-JUL-13 14:35
Notes:
You can see 3 problems here:
a) The end-time for session number 1083552 (19-JUL-13 20:17) is wrong.
It is neither the time stamp for timeout nor the on for pressing 'No'.
This is verified, considering the next start time (19-JUL-13 16:15).
b) The end-time for session number 1083552 is changed from 19-JUL-13 20:17 to 22-JUL-13 14:35, in the second report.
c) The end-date for multiple session numbers is identical.
It seems that the system sometimes sets the end-date as SYSDATE.
In either case this means that the value of the end-date is changing all the time and hence not reliable.
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
Symptoms |
Cause |
Solution |
References |