Understanding Audit Job Implementation

You must perform the following implementation tasks prior to running the audit jobs:

Import the audit .dsx file to your IBM WebSphere DataStage project.
- For the FMS Warehouse:
  
  Customers using FSCM 8.8 should import the WFN_OWS_AUDIT_E.dsx file.
  
  Customers using FSCM 8.9 should import the WFN_OWS_AUDIT_E_FSCM89_EPM9_IU.dsx file.
  
  Customers using FSCM 9.0 should import the WFN_OWS_AUDIT_E_FSCM9_EPM9_IU.dsx file.
  
  Customers using FSCM 9.1 should import the WFN_OWS_AUDIT.dsx file.
- For the Campus Solutions Warehouse:
  
  Customers using Campus Solutions 8.9 should import the WCS_OWS_AUDIT_E.dsx file.
  
  Customers using Campus Solutions 9.0 should import the WCS_OWS_AUDIT_E_CS9_EPM9_IU.dsx file.
In the PeopleSoft source transaction database, use PeopleSoft Application Designer to import the audit project.
- For the FMS Warehouse:
  
  Customers using FSCM 8.8 should import the AUDIT_FMS project.
  
  Customers using FSCM 8.9 should import the AUDIT_FMS_89 project.
  
  Customers using FSCM 9.0 should import the AUDIT_FMS_9 project.
  
  The audit project contains all the related audit records for the source tables.
- For the Campus Solutions Warehouse:
  
  Customers using Campus Solutions 8.9 should import the AUDIT_CS_89 project.
  
  Customers using Campus Solutions 9.0 should import the AUDIT_CS_9 project.
In the source transaction system database, use Application Designer to build the audit tables for which you want to use with the audit jobs.
Define audit triggers for each audit record you build using the Audit Trigger page.

You must create an audit trigger for each audit record. A trigger is a database level object that the system initiates based on a specified event occurring on a table. The audit trigger ensures that auditing is triggered whenever there is a change to the source record.

You must choose the record to hold the auditing data, the audit record, using the Audit Triggers page.
Create and run trigger scripts.

Note: Before you enable and run audit jobs, you must first load your source data into EPM using the delivered OWS jobs that use CRC logic. This ensures that all subsequent changes in the source records are captured in the audit record.