After Enabling Auditing, PAUDIT AUDIT_OLD and AUDIT_NEW columns Do Not Display Changes And Execution Of 'Publish Audit Data' Does Not Move Records To PAUDITX (Doc ID 2460067.1)

Last updated on MAY 09, 2023

Applies to:

Symptoms

ACTUAL BEHAVIOR
--------------------
P6 EPPM Database Auditing has been enabled but the AUDIT_OLD and AUDIT_NEW column is not being populated in the PAUDIT table after updates are made. Null values observed in these columns.

This will create an issue with the global scheduled service 'Publish Audit Data' because it will not insert any records into PAUDITX during the global publication job since the old and new fields are used to filter the records being published.


EXPECTED BEHAVIOR
--------------------
After enabling auditing, changes should be tracked in AUDIT_OLD and AUDIT_NEW column.

This will also ensure the global scheduled service 'Publish Audit Data' properly writes to PAUDITX for reporting against published data.  


STEPS TO REPRODUCE
--------------------
The following steps can be used to reproduce the issue (using PROJWBS as example):

• Ensure auditing is enabled and table(s) have been selected:
  
  1. Login to P6
  2. Select the 'Administration' tab
  3. Select 'Application Settings'
  4. Select 'Audit'
  5. Select 'Enable auditing for selected tables'
  6. Add a table, i.e. 'PROJWBS'
• Use case:
  
  1. Login to P6
  2. Navigate to EPS
  3. Select Activities tab
  4. Create/Edit/Delete a WBS
     
     • Result:
       
       • Validate from Database that correct data is getting updated in 'AUDIT_OLD' and 'AUDIT_NEW' PAUDIT columns. 
       • Additionally, after making the change, execution of global scheduled service 'Publish Audit Data' will not update PAUDITX table for reporting purposes.

Changes

Cause

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.