Attention: To align with new corporate security policies, and to match policies adopted by other communities within Oracle, the My Oracle Support Community access requirements will change beginning September 18, 2025. MOSC will now require that member accounts in our community be associated to a *corporate* email address. This means that users with generic domains (such as gmail.com, yahoo.com, and others) will no longer be granted access to the discussion forums and ideas labs. If this policy affects you, act now to change the email address that is associated with your Oracle (and community) account. Alternatively, you can opt to create a new Oracle account that uses your corporate email domain.

PeopleTools and Lifecycle Management - PSFT (MOSC)

Record-level Auditing vs Database-Level Auditing

May 14, 2014 12:12PM edited May 22, 2014 12:00PM in PeopleTools and Lifecycle Management - PSFT (MOSC) 3 commentsAnswered

We created a record-level audit table for PS_NAMES.

It seems that when you add a new name record, the audit table contains the new name (shouldn't it contain the old name?)

It seems that when you correct an existing name record, the audit table contains the old name.

I opened a Peoplesoft Service Request and was told to use database-level auditing.

What is the difference and why would database-level auditing work in this scenario, even though record-level auditing is not working for PS_NAMES?

0

Howdy, Stranger!

To view full details, sign in to My Oracle Support Community.

Don't have a My Oracle Support Community account? Click here to get started.

Category Leaderboard

Top contributors this month