Results for “xtr_temp_audit_view_v”
4 results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
Overview
XTR_TEMP_AUDIT_VIEW_V is a Treasury (XTR) module database view in Oracle E-Business Suite 12.1.1 and 12.2.2. Its name, the "_V" suffix, and its composition identify it as a lightweight, read-oriented view whose purpose is to expose audit-style tracking information about temporary Treasury operations. The ETRM metadata records the object with the description "Not implemented in this database," meaning the view exists in the Oracle EBS data model as shipped but is not necessarily created or populated in every deployment. This is characteristic of Treasury helper views used internally by concurrent programs, diagnostics, or reconciliation logic rather than by end-user forms.
The view surfaces four attributes — FROM_PERIOD, TO_PERIOD, USERNAME, and QUERIED_BY — describing which period range was queried, by which database user, and for which requesting user. This makes the view an audit trail over Treasury period-based retrieval activity. Given that the underlying source object XTR_TEMP_AUDIT_VIEW itself carries the "TEMP" designation, the data is transient by nature and is populated only while a period-sensitive Treasury process is running or immediately after it completes.
Underlying Base Objects
The documented view text is a straightforward projection:
- SELECT FROM_PERIOD, TO_PERIOD, USERNAME, QUERIED_BY FROM XTR_TEMP_AUDIT_VIEW
Per the ETRM metadata, no referenced base objects are documented beyond XTR_TEMP_AUDIT_VIEW, and the owner is not recorded. The view is not implemented in the documented database, so no row source can be confirmed at runtime. Because XTR_TEMP_AUDIT_VIEW is itself named "TEMP," XTR_TEMP_AUDIT_VIEW_V is best understood as the queryable access layer over a transient Treasury audit staging structure — a support object for the XTR period-sensitive Treasury flows rather than a persistent reporting table. There is a one-to-one column mapping between the view and its source, with no joins, filters, or expressions applied.
Key Columns
- FROM_PERIOD — The lower boundary of the period range that was queried or audited. In Treasury workflows, periods typically correspond to accounting periods or Treasury reporting cycles against which transactional data is evaluated.
- TO_PERIOD — The upper boundary of the queried range. Together with FROM_PERIOD it defines the exact window covered by the audit record.
- USERNAME — The database or application user associated with the audit entry, providing the identity context for the recorded query.
- QUERIED_BY — The party that initiated the period query. This may differ from USERNAME, allowing separation of the acting session from the originating requester.
Common Use Cases and Queries
Because the view is primarily diagnostic, it is used to trace who queried which Treasury period range and under what user context. Typical scenarios include investigating duplicate period retrievals, confirming that a concurrent process swept the correct accounting window, and supporting Treasury reconciliation troubleshooting. All sample SQL below assumes the view exists in the target instance.
- Full audit listing ordered by period:
SELECT from_period, to_period, username, queried_by FROM xtr_temp_audit_view_v ORDER BY from_period, to_period; - Activity for a specific period range:
SELECT username, queried_by, from_period, to_period FROM xtr_temp_audit_view_v WHERE from_period >= :p_from AND to_period <= :p_to; - Activity attributable to a user:
SELECT from_period, to_period FROM xtr_temp_audit_view_v WHERE queried_by = :p_user;
Because the source is a temporary audit structure and the object is documented as not implemented in the reference database, queries should be validated against the specific instance before being relied upon in production reporting. Oracle Proprietary, Confidential Information.
-
View: XTR_TEMP_AUDIT_VIEW_V 12.2.2
Not implemented in this database·Explore XTR module →
-
View: XTR_TEMP_AUDIT_VIEW_V 12.1.1
Not implemented in this database·Explore XTR module →
-
12.2.2 FND Design Data 12.2.2
-
12.1.1 FND Design Data 12.1.1