User ID Recorded In RPM Audit Tables Is Not The RPM Front End Application Username
Last updated on AUGUST 17, 2016
Applies to:Oracle Retail Merchandising System - Version 188.8.131.52 and later
Information in this document applies to any platform.
***Checked for relevance on 05-Dec-2013***
In RPM audit tables (anything suffixed in _AU), the user id recorded is not the RPM front end user name.
Instead this field records the schema owner for all audit trail records.
Steps to Reproduce:
RPM_PROMO_DTL table is just an example.
1.Ensure the RPM_PROMO_DTL table is switched on for auditing (RMS=>Control=>System=>Audit Trail), if it is necessary to add this table then run auditsys batch.
You have STATE/START_DATE/PROMO_DTL_ID/END_DATE/APPROVAL_DATE fields audited.
2. Enter a new promotion with two or more components, approve the promotion
3. Roll the dates to the night before the active date of the promotion
4. Run the PriceEventExecutionBatch
5. Roll the dates passed the start date
6. Maintain RPM component 1 and change the end dates of the promotion to end the promo early
7. Maintain RPM component 2 and cancel all the items in the component
8. Query RPM_PROMO_DTL_AU - the user id recorded against the record is not the application user but the DB. You cannot tell who canceled the promotion.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms