Siebel Field Service Guide > Service Requests and Solutions >

About Siebel Audit Trail


Siebel Audit Trail creates a history of the changes to service requests. An audit trail record shows the performed operation, the date and time of the operation, and the change to the value. Therefore, Siebel Audit Trail is useful for examining the history of a service request. Siebel Audit Trail logs information without requiring any interaction with, or input from, users.

By using Siebel Audit Trail, your users can determine the employee who modified a certain field and the data that changed. An audit trail record is created for each status change. This record includes a time stamp and the ID of the user who made the change.

For Siebel Remote users who change records, Siebel Audit Trail works for every Siebel Web deployment and configuration option, including synchronization. Audit trail records show not only successfully committed transactions, but also transactions that are not synchronized to the server because of conflicts.

Audit trail data is written directly into the Siebel database, supporting both remote users and replicated databases. Changes to a Siebel Audit Trail field are cached in the Siebel application. Exiting from a Siebel application and restarting it writes all cached changes to the Siebel database. Alternatively, when the cache size is reached, all cached entries are automatically written to the Siebel database even when a user does not exit from the Siebel application.

NOTE:  Siebel Audit Trail supports the Service Requests and Asset Mgmt - Asset business components.

The Audit Trail view shows the history of changes to specific service request records. This view is read-only. For more information about Siebel Audit Trail, see Siebel Applications Administration Guide.

Siebel Field Service Guide Copyright © 2013, Oracle and/or its affiliates. All rights reserved. Legal Notices.