It is that time of year when customers are producing year end forms, running integrity reports, balancing their books, and officially closing out the calendar year.  We find ourselves asking the questions;  How did that get changed?  Or who updated that record? 


Set up Database Audit Manager over your major files, you’ll have the answers to those questions.  Database Audit Manager is a tool which enables selective historical database transaction logging.  It also contains support for electronic signature verification, enforcement, and capture all within Database Audit Manager.

The Database Audit Manager provides the ability to select a file and the fields in the file to be tracked. In addition, it allows the following:

  • Add a new audit process
  • Build an audit
  • Activate and deactivate audit triggers
  • Maintain reason code
  • Set the default library names used throughout the system

For example, let’s say that the FDA requires tracking address changes. You can set up an audit to record changes to the address data field of the Address Book Master file (F0101). Once you have identified the file to audit, define an audit program (P0101AUD) and a target file (F0101AUD).  Now, select the address data field to trigger the audit program. Finally, attach reason codes to the actions. Easy!

For more information on setting up Data Base Audit Manager, please review:  JD Edwards World Database Audit Manager

Oracle Support also created a quick reference quide to help setup DBAM, Database Audit Manager with Electronic Signature Quick Reference Guide (Doc ID 647975.1)