How to Track or Audit Any Changes Made Within P6 EPPM
(Doc ID 907655.1)
Last updated on SEPTEMBER 08, 2021
Primavera P6 Enterprise Project Portfolio Management Cloud Service - Version 22.214.171.124 and later Primavera P6 Enterprise Project Portfolio Management - Version 6.0 and later Primavera Gateway - Version 126.96.36.199 and later All Platforms
Starting in version 6.0, Native database auditing was added to the P6 database. Auditing is a method to log the edits, additions and deletions made by users of the Primavera application. Every change made by a user results in Data Manipulation Language or DML (INSERT, UPDATE or DELETE statements) execution against tables in the database schema. Every application table in the schema has its own auditing trigger that can log the changes to the table whenever and by whomever makes the change. Because the trigger is owned by the database schema owner there is no way to bypass its execution.
In general, auditing does not take affect until the user creates a new session after auditing is enabled. Additionally, auditing does not stop auditing active sessions (sessions established prior to disabling) until the session is terminated. For example, a user is logged in to application and auditing is enabled. The user will not be audited until the customer closes out of the application and logs in again.
In P6 EPPM r15.1 and later releases, native database auditing can be configured from within P6 Web without the need to run any stored procedures against the database directly.
The goal of this document is to provide instruction for utilizing the database auditing functionality to track or audit any changes made within the P6 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!