Bookshelf Home | Contents | Index | PDF | ![]() ![]() |
Siebel Applications Administration Guide > Siebel Audit Trail > About Siebel Audit TrailSiebel Audit Trail creates a history of the changes that have been made to data in Siebel Business Applications. An audit trail is a record showing who has accessed an item, which operation was performed, when it was performed, and how the value was changed. Therefore, it is useful for maintaining security, examining the history of a particular record, documenting modifications for future analysis, and record keeping. Siebel Audit Trail logs information without requiring any interaction with, or input from, your users. Siebel Audit Trail can be used for a variety of purposes. In a simple example, a call center uses an audit trail to track the status change of a service request, who changed it and when. Siebel Audit Trail capabilities can also be used to track the time needed to change the state of an item, such as a service request from open to closed. A calculation of the time difference can help the call center manager measure and improve service quality. Siebel Audit Trail can also be used to reproduce a record at a given point in time to maintain regulatory compliance. You look at the audit trail for the record and compare the audit trail details with the current state of the record. Siebel Audit Trail can also be used to track the viewing and export of data. For example, financial services organizations can use Siebel Audit Trail to monitor who has read or exported an account holder's information. Siebel Audit Trail can be implemented for the Siebel Audit Trail functionality itself to help you track any changes made to the Siebel Audit Trail settings. NOTE: For any Siebel Audit Trail deployment, the combination of the number of fields audited and the number of audit records created by a given business process has performance implications. If you audit a large number of fields on a business component, or audit fields in a large number of business components, unacceptable performance might result. Because read operations are common, if you audit a large number of these operations, unacceptable performance might result. Siebel Audit Trail FeaturesMore Siebel Audit Trail features are described in the following topics: |
![]() |
![]() ![]() |
Siebel Applications Administration Guide | Copyright © 2013, Oracle and/or its affiliates. All rights reserved. Legal Notices. | |