Auditing Tables Not Showing Old And New Values And Not Published To Reporting (Extended) Schema
(Doc ID 2452478.1)
Last updated on JUNE 04, 2019
Applies to:Primavera P6 Enterprise Project Portfolio Management Cloud Service - Version 22.214.171.124 and later
Information in this document applies to any platform.
Audit Old and Audit New values are not being populated in the PAUDIT table when auditing is turned on. This limits the information available from native auditing since we can only see that insert, update, or delete operations were performed against a table, but not what the old or new values were. Additionally, when these fields are left null the records are not pushed to the extended schema during publication.
STEPS TO REPRODUCE:
- Enable auditing for a tables.
- Make a change to values in P6 related to the table audited.
- Save Changes
- Query the PAUDIT table and note the missing values for Old and New values
- Run Audit Publication
- Note that the value are not published to the Reporting Schema (also known as the Extended Schema)
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