Audit Trail Customization (Doc ID 508330.1)

Last updated on MARCH 02, 2017

Applies to:

Siebel Tools - Version 7.5.2.211 [16061] and later
z*OBSOLETE: Microsoft Windows 2000
Product Release: V7 (Enterprise)
Version: 7.5.2.211 [16061]
Database: Oracle 8.1.7.4
Application Server OS: Microsoft Windows 2000 Server SP 3
Database Server OS: Sun Solaris 2.8
Checked for Relevance on 22-Jul-2016

This document was previously published as Siebel SR 38-1049596981.


Goal

We are upgrading to Siebel 7 from 2000. In our Siebel 2000 system we had a custom audit trail using the s_srv_req_xm table with code in the PreSetFieldValue of the Service Request BC. We are now switching to the out of the box audit trail in 7. The out of the box audit trail is working, but I need to change the functionality.

We need to have two dates for every transaction, Start Date and End Date, so we can calculate the duration that an SR was in a particular state. So if the severity changes from High to Low, we want the audit trial to fill in the end time of the record where the value changed to High. That way we can tell how long the SR was at High state.

I have added a column to the s_audit_item table and then added the field to the Audit Trail Item 2 BC. I have tried to add code to the Audit Trail BC in the PresetField value, but any code causes the audit trail to stop working.

How does this BC work? When a value is changed on the SR how is information passed into this BC and can it be manipulated?

Solution

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms