Results for “xtr_audit_summary_v”
16 results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
Overview
XTR_AUDIT_SUMMARY_V is a reporting view owned by the APPS schema in Oracle E-Business Suite, defined under the XTR (Treasury) product. It exposes the audit trail captured for Treasury-related transactions, presenting who requested an audit, the scope of records audited, the specific column changed, and the before-and-after values. In Oracle EBS 12.1.1 and 12.2.2 the view is a straightforward projection over its base synonym, carrying no inline filter or transformation logic. Its principal role is to support audit reporting, compliance review, and reconciliation of changes made to Treasury deal, instrument, and limit data. Because the object is a view rather than a table, it is read-only and inherits the security and grants defined on the underlying synonym and base table. The view is especially relevant for users searching on the "updated_by_user" attribute, since that column records the application user who performed the audited change and is central to accountability and change-tracking queries.
Underlying Base Objects
The view is defined over the documented base object XTR_AUDIT_SUMMARY, which is referenced through a synonym. The view text selects all fifteen columns of that base object without alteration:
- SELECT AUDIT_REQUESTED_BY, AUDIT_REQUESTED_ON, AUDIT_RECORDS_FROM, AUDIT_RECORDS_TO, NAME_OF_COLUMN_CHANGED, TABLE_NAME, REFERENCE_CODE, UPDATED_ON_DATE, UPDATED_BY_USER, OLD_VALUE, NEW_VALUE, TRANSACTION_REF, NON_TRANSACTION_REF, ACTION_CODE, AUDIT_REQUEST_ID FROM XTR_AUDIT_SUMMARY
Because the projection is a one-to-one mapping of the base columns, the view adds no derived fields and imposes no row-level restriction. Any business logic, audit population, or purging behavior resides in the base table and the Treasury audit engine that writes to it. Consequently, the view's performance and data freshness mirror XTR_AUDIT_SUMMARY exactly.
Key Columns
- AUDIT_REQUEST_ID — Identifier of the audit request that generated the summary row; useful for grouping all changes made under one submission.
- AUDIT_REQUESTED_BY / AUDIT_REQUESTED_ON — The user and timestamp of when the audit was requested, distinct from when the change occurred.
- AUDIT_RECORDS_FROM / AUDIT_RECORDS_TO — Range boundaries defining the record set included in the audit.
- TABLE_NAME — The Treasury base table affected by the change.
- NAME_OF_COLUMN_CHANGED / OLD_VALUE / NEW_VALUE — The attribute modified and its previous and current values, forming the core of any audit diff report.
- UPDATED_BY_USER / UPDATED_ON_DATE — The application user who performed the change and the effective change timestamp; this pair answers the "updated_by_user" search intent.
- REFERENCE_CODE / TRANSACTION_REF / NON_TRANSACTION_REF — Contextual identifiers linking the change to a Treasury transaction or non-transaction reference.
- ACTION_CODE — Classification of the action taken (for example, insert, update, or delete).
Common Use Cases and Queries
Typical scenarios include investigating who modified a specific Treasury record, reconstructing the history of a deal, and producing audit evidence for internal or regulatory review. The following queries illustrate standard access patterns.
- Identify all changes made by a given user: SELECT * FROM XTR_AUDIT_SUMMARY_V WHERE UPDATED_BY_USER = 'USERNAME';
- Review changes to a specific table over a period: SELECT REFERENCE_CODE, NAME_OF_COLUMN_CHANGED, OLD_VALUE, NEW_VALUE, UPDATED_ON_DATE FROM XTR_AUDIT_SUMMARY_V WHERE TABLE_NAME = 'XTR_DEALS' AND UPDATED_ON_DATE >= SYSDATE - 30;
- Trace a single audit request: SELECT * FROM XTR_AUDIT_SUMMARY_V WHERE AUDIT_REQUEST_ID = :request_id ORDER BY UPDATED_ON_DATE;
Reports should join to user and responsibility tables for descriptive names, and apply date and reference-code predicates to limit volume. Because the view performs no filtering, efficient querying depends on the indexes present on XTR_AUDIT_SUMMARY and on supplying selective predicates such as UPDATED_BY_USER, TABLE_NAME, or DATE ranges.
-
View: XTR_AUDIT_SUMMARY_V 12.2.2
APPS.XTR_AUDIT_SUMMARY_V·↳ XTR_AUDIT_SUMMARY·Explore XTR module →
-
View: XTR_AUDIT_SUMMARY_V 12.1.1
APPS.XTR_AUDIT_SUMMARY_V·↳ XTR_AUDIT_SUMMARY·Explore XTR module →
-
12.2.2 DBA Data 12.2.2
-
12.1.1 DBA Data 12.1.1
-
12.1.1 FND Design Data 12.1.1
-
12.2.2 FND Design Data 12.2.2
-
eTRM - XTR Tables and Views 12.2.2
Created on 29-OCT-96
-
eTRM - XTR Tables and Views 12.1.1
Created on 29-OCT-96
-
12.2.2 DBA Data 12.2.2
-
12.1.1 DBA Data 12.1.1
-
eTRM - XTR Tables and Views 12.2.2
Created on 29-OCT-96
-
eTRM - XTR Tables and Views 12.1.1
Created on 29-OCT-96