How to Use the Audit Trail

The audit trail is used to track what records have been changed.

See About Audits for the different types of audits in OTM.

Configuration

Complete these steps to enable the audit trail.

Create a Contact

Before you can audit any records, you must add at least one contact (per domain) using the Contact Manager. The contact must be assigned the Audit (AUD) communication method. Then you can assign the contact to the specific Oracle Transportation Management events you want to audit.

By default, any user in that domain that is assigned to the DEFAULT user role can perform an audit. An Oracle Transportation Management Administrator can grant or restrict audit access using the standard Access Control functionality.

All audit records are stored in the domain where the contact that has auditing privileges resides. If your Oracle Transportation Management implementation has multiple domains or sub-domains, you can configure the audit contact to store audit records in a specific domain so that you can audit other domains.

Navigate to Business Process Automation > Communication Manager > Contacts.
Create a new contact in the Communication Manager or modify an existing contact.
Enter the appropriate domain in the Recipient Domain Name field that determines where you want to store audit records. This allows users in that domain to perform an audit on the records from your current domain.
In the Com Method ID field select AUD.
Enter a Rank of 1.
Click Save.
Click Finished.

Assigning Contact to Contact Notifications

Navigate to Business Process Automation > Communication Manager > Contact Notification.

You can use the Search page to find a specific contact notification or leave the page blank and click Search to display a list of all contact notifications.
Edit the contact notification and assign the contact.
Select AUD as the communication method and click Save.
Click Finished.
Repeat this procedure for each contact notification that you want to audit.

Set Before/After Value Auditing

The default level of auditing is Data Change Auditing. This method saves information including the ID of what was changed, the change made, the user who made the change and the date and time of the change.

However, if you want more data, you have to enable the Before/After Value Auditing, which collects the before and after values as well as which tables changed and the table keys. If you want to use the detailed auditing, then you must first set the glog.audit.beforeafter property to "on" to be able to see changes to each database column. Once that property is "on", a detailed audit for every event that is currently configured for audit is saved and can be seen when you use View Audit Trail. You can restrict the detailed auditing to only those objects defined in Audit Control. Note that setting this may impact system performance and storage.

Set Audit Control

To constrain the amount of audit data collected, create an active Audit Control which causes audit data to be collected for only those business objects that you want.

Audit Records

Audit by Business Object

Use the Audit Trail action to track how records have been changed for different business objects.

Audit by User, Event, or Notification

You can use Business Process Automation > Audit Trail Management to conduct a more global audit across different business object types. You have the option of viewing By User, By Event, and By Notification. For example, you can audit orders, rates, shipments, invoices and bills from one page based on the contact notification events that are activated for auditing. You can also audit against specific business object types and events as well by selecting audit criteria.