My Oracle Support Banner

Two Read Audit Records Created For A Drilldown On A View. (Doc ID 2086944.1)

Last updated on MARCH 02, 2017

Applies to:

Siebel CRM - Version [IP2013] and later
Information in this document applies to any platform.


On : [IP2013] version, Client Functionality

Two Read Audit records created for a drill down on a audit trial captured in source view even though the field not displayed in UI and no Lin specification and force active for the same field

The source and the destination BC here is the same. After the Drill down event, it is inserting two read audit records.

Single record need to create in audit trail BC

The issue can be reproduced at will with the following steps:

1) For the 'Service Request List Applet':
For the Drilldown object named 'Original': Set the Source Field and Destination Field as 'Id'.

2) For the 'Service Request Detail Applet':
Create a new control : 'Provider Id' and map the field 'Provider Id' of the Service Request BC to the same.
Map the new control the web layout of the Applet.

3) Navigate to Administration-->Audit Trail screen in the Application
Create a new record in the Audit Trail with the BC as 'Service Request'
And set the read field as 'Provider Id'. Click the 'Update Audit Cache' button.

Navigate to Service Request View and drill down on SR# from Service Request List Applet.
Navigate to Read Audit Items view to check the read audits created for the record on which the drilldown was performed.


To view full details, sign in with your My Oracle Support account.

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

In this Document

This document is being delivered to you via Oracle Support's Rapid Visibility (RaV) process and therefore has not been subject to an independent technical review.
My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.