Audit Feature Not Working Properly For WF_LOCAL_USER_ROLES Table
(Doc ID 846435.1)
Last updated on MARCH 02, 2023
Applies to:
Oracle Application Object Library - Version 11.5.10.0 to 11.5.10.2 [Release 11.5]Information in this document applies to any platform.
Symptoms
On 11.5.10 CU2 in Production:
Shadow table FND_USER_A and the audit view FND_USER_AV1 shows incorrect or unexpected records of Audit Transaction Type Update. AUDIT_USERNAME of these records shows ANONYMOUS USER.
EXPECTED BEHAVIOR
Records with ANONYMOUS USER as the AUDIT_USERNAME are not expected in the shadow table and audit view.
STEPS
The issue can be reproduced at will with the following steps:
1. Login to Oracle Applications.
2. Select System Administrator responsibility.
3. Enable AuditTrail on the table FND_USER from the below navigation
Security -> AuditTrail
4. Provide the instance to users to perform different transactions.
5. Shadow table FND_USER_A and the audit view fnd_user_av1 shows incorrect or unexpected
records.
BUSINESS IMPACT
The issue has the following business impact:
Users and Responsibilities data should be audited for SOX compliance. Due to this issue there is
no SOX compliance.
WHAT IS WORKING
When making changes to a user via the define User screen, than AUDIT_USERNAME column of the shadow
table (FND_USER_A) populates correctly i.e. with the name of the user who makes the changes.
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 |