Can The FND_USER Table Be Used For Auditing Purposes In Tracking The Password Changes
(Doc ID 1642530.1)
Last updated on FEBRUARY 12, 2019
Applies to:Oracle Application Object Library - Version 220.127.116.11 to 12.2 [Release 11.5 to 12.2]
Information in this document applies to any platform.
A custom report developed based on audit-table FND_USER_A is created, but the report output is not providing the correct information.
The discrepancy is => USER_A can not have the right to change the password of USER_B, but USER_A information is seen in the output who changed the password of USER_B. Audit Functionality inserts the table FND_USER_A based on DML operations performed on table FND_USER, with the help of AUDIT database triggers.
Data changes are recorded in FND_USER_A table using Oracle-Application or direct insert/update/delete statement.
What are the other sources from which data can be modified affecting the FND_USER table?
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