PeopleTools and Lifecycle Management - PSFT (MOSC)

MOSC Banner

Adding Query Security to Audit Records

edited Sep 15, 2016 5:01AM in PeopleTools and Lifecycle Management - PSFT (MOSC) 4 commentsAnswered ✓

We have a requirement to added Query Security to our Audit Records.  Has anybody done this before?  Concerned about this statement from PeopleBooks indicating that there should be no keys except for AUDIT_OPRID, AUDIT_STAMP and AUDIT_ACTION: "Remove all edit and key attributes from the newly saved record"

If we add additional keys (so PS Query Security can use) and the same Query Record used for normal tab will be introduce issues?

HCM 9.1 Example (Tools 8.53):

PS_JOB uses EMPLMT_SRCH_QRY as Query Security Record.  Would like to use same Query Security Record on PS_AUDIT_JOB but Keys will be different.  If we make KEYS on Audit table AUDIT_OPRID, AUDIT_STAMP, AUDIT_ACTION  plus EMPLID, EMPL_RCD, EFFDT, EFFSEQ will Audit writes still work and will Query Security work with same EMPLMT_SRCH_QRY?

Howdy, Stranger!

Log In

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

Register

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

Category Leaderboard

Top contributors this month

New to My Oracle Support Community? Visit our Welcome Center

MOSC Help Center