You are on page 1of 6

Bookmarks Admin Profile Feedback Sign Out Help Headli nes Knowle dge Service Request Advanced Searc

h Configuration Support Manager Bug Searc # & o Foru ms Certi f

!no"ledge Bro" ser %ui ck Find

Secure $nterprise Sea rc#


Secure Enterprise Search Advanced Saved Searches

'id t#is article #elp solve our problem(

)ould ou recommend t#is document to ot#ers(

*+P, Click #elp for a detailed e-planation of t#is page.

Bookmark &o to $nd

Sub/ect, A Guide to Set Up Of Audit Trail In Oracle HRMS 'oc +', Note: !"#$ * pe, %U&&'TIN 0ast Revision Status, ()*A+R*,((! +U%&ISH''ate,
A GUIDE TO SET UP OF AUDIT TRAIL IN ORACLE HRMS ===============================================

PURPOSE ======== This paper guides the User in the Set Up and Configuration of Audit Trail in the Oracle Human Resources Management (HRMS) application.

SCOPE & APPLICATION ====================

This document will guide support analysts and users through the use of the System Profiles in the set up and administration of the Oracle HRMS application. It will list the System Profiles which must be populated to use the system and provide brief descriptions of the profiles which may be set. It will not cover the many set up steps not related to HRMS or System Profiles. Some profiles will only be available following set up steps in the Core Application. This paper will assume that pre-requisite steps have been taken to enable use of each Profile.

RELATED DOCUMENTS ================== The Oracle HRMS UK Users Guide, Oracle Payroll UK Users Guide and On-Line help all cover the basic set up and maintenance of HRMS. Oracle Human Resources UK Users Guide Release 11 Note 66299.1 Audit Set Up in R10.7 Note 69660.1 Understanding Auditing Note 105630.1 Setup & Usage (Audit Trail) NOTE BODY ========== General Introduction Pre-requisite Patches Enable Auditing Disable Auditing Re-enable Auditing Data checks [A58345-01]

GENERAL INTRODUCTION ===================== Audit Trail allows the system User to keep a history of changes to data. It is possible to record what has changed, who changed it and when. The User is able to specify which table(s), and in fact which columns within those tables, they wish to audit. The set up of Audit Trail in Release 11.0 and 11.5 is, to a greater extent the same as R10.7. However, there are several differences which it is critical to be aware of.

PRE-REQUISITE PATCHES ====================== NOTE: These patches are R11.0 pre-reqs - These finctions are seeded in R11.5 677563 - Shadow Table updated when non-audited Columns changed 781694 - Audit Trail Report fails 852010 - Audit Trail Report parameters lists database users Should be application users 736388 - Audit Groups form errors

ENABLE AUDITING ================ - System Administrator responsibility Profiles > System Application = Oracle Human Resources Profile = AuditTrails%

Click Find Set to Yes for either SITE (Not recommended as ALL applications [when the audit related setup has been done on those tables in the other applications], will be actively recording audited changes) OR Application level (Recommended for controlling how much data is collected at any given time) Note : This option can only be set at the Site and Application levels.

- System Administrator responsibility Navigate Security --> AuditTrail --> Groups Application Name : Oracle Human Resources Audit Group : <User Defined Name> Group State : Enabled User Table Name : Pick required tables from List of Values

The 'User Table Name' selected is associated with its corresponding base table 'Table Name' - it is this base table which will be audited. It is also the 'User Table Name' which is selected as a parameter when you run the predefined Audit Report. Normally the 'User Table Name' and 'Table Name' will be identical but this is not always the case - For example: User Table Name --------------PER_PEOPLE_F PER_ASSIGNMENTS_F Table Name ---------PER_ALL_PEOPLE_F PER_ALL_ASSIGNMENTS_F

- System Administrator responsibility Navigate Security --> AuditTrail --> Tables User Table Name : Query the tables from above Column Name : Pick required columns from List of Values Note : Columns of data type Long, Raw or Long Raw cannot be audited. - System Administrator responsibility Navigate Security --> AuditTrail --> Install Oracle Username : Pick required usernames from List of Values Note : These usernames are those used by the application to connect to the database. APPS and HR must both be picked and the Audit Enabled checkbox must be ticked. - System Administrator responsibility Navigate Requests --> Run

Request Name : Audit Trail Update Tables (process executable FNDATUPD) Parameters : None Note : This process will create Shadow Tables with the same data type columns as the audited tables picked above. Shadow Tables have the name <tablename>_A which mirror the audited tables. It will also create views on the Shadow Tables with the name <tablename>_AC1 and <tablename>_AV1 which allow access to the data in the Shadow Tables. It creates database triggers on the audited tables picked above with the name <tablename>_AI, <tablename>_AU and <tablename>_AD which fire respective when the audited columns are Inserted, Updated or Deleted. Lastly it creates procedures that are called by the triggers with the name <tablename>_AIP, <tablename>_AUP and <tablename>_AID. These save the old data from the audited tables into the Shadow Tables. - UK HRMS Manager responsibility Navigate Processes and Reports - -> Submit Processes & Reports Request Name : Audit Trail Update Datetracked Tables (process executable PYATUPD) Parameters : None Note : This process creates indexes on the Shadow Tables and creates the function <tablename>_TT and the procedure <tablename>_VP. These extract the data from the Shadow Tables when the Audit Report is run. Important : When the Audit Trail Update Datetracked Tables process is run, the concurrent process may complete in Error. However, this may be ignored if examination in SQL/PLUS shows that the above functions and parameters have been created. - UK HRMS Manager responsibility Navigate Processes and Reports --> Submit Processes & Reports Request Name : Audit Report (process executable PAYAUDIT) Table Name : Pick table to be audited Initialization : Yes - Removes obsolete data for selected table Re-populates tables with new data and reports No - Reports on the existing data in tables Refresh - Removes data for ALL tables Reports on new data. User Name : Pick Applications username to be audited Start Date : Date from which to report audit transactions End Date : Date at which to cease reporting audit transactions

DISABLE AUDITING

================= - System Administrator responsibility Navigate Security --> AuditTrail --> Groups Audit Group : Query the Audit Group created above Group State : Disable - Interrupt Audit - System Administrator responsibility Navigate Requests --> Run Request Name : Audit Trail Update Tables (process executable FNDATUPD) Parameters : None OR - System Administrator responsibility Set the Profile option to NO at the level previously set to YES RE-ENABLE AUDITING =================== - System Administrator responsibility Navigate Security --> AuditTrail --> Groups Audit Group : Query the Audit Group created above Group State : Enabled - System Administrator responsibility Navigate Requests --> Run Request Name : Audit Trail Update Tables (process executable FNDATUPD) Parameters : None OR - System Administrator responsibility Set the Profile option to Yes at the level previously set to No DATA CHECKS ============ - Audit Trail Update Tables -- check that shadow tables exist select substr(owner,1,10) "OWNER" , substr(object_name,1,30) "OBJECT" , substr(object_type,1,10) "TYPE" , status "STATUS" from all_objects where object_name like upper('%/_a') escape'/'; -- check that shadow views exist select substr(owner,1,10) "OWNER" , substr(object_name,1,30) "OBJECT" , substr(object_type,1,10) "TYPE" , status "STATUS" from all_objects where object_name like upper('%/_a__') escape'/'; -- check that database triggers exist select substr(owner,1,10) "OWNER" , substr(object_name,1,30) "OBJECT"

, substr(object_type,1,10) "TYPE" , status "STATUS" from all_objects where object_name like upper('%/_a_') escape'/'; -- check that procedures exist select substr(owner,1,10) "OWNER" , substr(object_name,1,30) "OBJECT" , substr(object_type,1,10) "TYPE" , status "STATUS" from all_objects where object_name like upper('%/_a__') escape'/';

- Audit Trail Update Datetracked Tables -- check that functions exist select substr(owner,1,10) "OWNER" , substr(object_name,1,30) "OBJECT" , substr(object_type,1,10) "TYPE" , status "STATUS" from all_objects where object_name like upper('%/_tt') escape'/'; -- check that procedures exist select substr(owner,1,10) "OWNER" , substr(object_name,1,30) "OBJECT" , substr(object_type,1,10) "TYPE" , status "STATUS" from all_objects where object_name like upper('%/_vp') esca

. Bookmarks Admin Profile Feedback Sign Out Help


Copyright 2006, Oracle. All rights reserved. Legal Notices and Terms of Use | Privacy Statement