How to Implement Unified Auditing for Oracle RMS Purchase Order (PO) Tables
(Doc ID 2427456.1)
Last updated on DECEMBER 04, 2019
Applies to:Oracle Retail Merchandising System - Version 16.0.1 and later
Information in this document applies to any platform.
Unified Auditing is tracking the Audit data as per the policy is defined, but it is not tracking the Application user who is modifying the data in the tables.
How do we get the Application User Information updated?
Needing Audit Purchase Order (PO) Related tables in RMS.
Auditing data is updated to the table UNIFIED_AUDIT_TRAIL, but it does not track the Application user who modified the PO Data.
Steps To Recreate:
1. Login to RMS as a user who has a role to update the PO data and Modify any PO.
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