Search Results script_name




Overview
Explore in AI Chat

Overview

XTR_MTS_RECORDS_V is a reporting view owned by the APPS schema within the XTR (Treasury) product module of Oracle E-Business Suite. It is a thin projection layer defined over the XTR_MTS_RECORDS base object, exposing a fixed subset of five columns: SCRIPT_NAME, TRANSFER_DETAILS, CREATED_ON_DATE, FILE_NAME, and SETTLEMENT_DATE. The view is documented as VALID in both Oracle EBS 12.1.1 and 12.2.2, and the ETRM metadata for 12.2.2 confirms the underlying reference resolves through the XTR_MTS_RECORDS synonym in APPS.

The view's primary purpose in the Treasury module context is to present settlement-oriented records produced by the MTS (Money Transfer System) record-keeping process. Because it limits the column list to a small, stable set, it functions as a controlled read interface for downstream reporting, extracts, and integration feeds that must not be coupled to every column on the base table. Analysts searching for settlement_date will find this view particularly relevant, since SETTLEMENT_DATE is one of the five projected columns and is directly queryable without navigating the full base table.

Underlying Base Objects

The documented base object for this view is XTR_MTS_RECORDS, referenced through its APPS synonym. The view definition is a straightforward SELECT over that object with no joins, aggregations, or filter predicates recorded in the metadata:

  • SELECT SCRIPT_NAME, TRANSFER_DETAILS, CREATED_ON_DATE, FILE_NAME, SETTLEMENT_DATE FROM XTR_MTS_RECORDS

Because the view performs no transformation of the underlying rows, it inherits the row cardinality and data types of the base columns. It carries no DISTINCT clause and no WHERE predicate, so it returns every qualifying row present in XTR_MTS_RECORDS. Any security applied at the base table or synonym level (for example, row-level security through a VPD policy on the synonym) would continue to govern access through the view, since the view is not defined with the AUTHID or security attributes that bypass the base policy.

Key Columns

  • SCRIPT_NAME — Identifier of the script or process that created or loaded the MTS record into the base table. Useful for tracing the origin of a settlement record and for filtering by process run.
  • TRANSFER_DETAILS — Descriptive payload carrying the specifics of the transfer represented by the record. This is typically the most verbose column and contains the settlement-relevant transaction detail.
  • CREATED_ON_DATE — The date the record row was created. This is the standard audit timestamp used for date-range reporting, aging analysis, and reconciliation window queries.
  • FILE_NAME — Name of the associated file, commonly the inbound or outbound MTS file that carried the record. Essential for file-level reconciliation and locating source artifacts.
  • SETTLEMENT_DATE — The date on which the transaction is valued or settled. This is the key column for settlement reporting, period cutoff, and matching settlement activity against bank or system statements.

Common Use Cases and Queries

The view supports settlement reporting, file reconciliation, and audit extracts. A typical retrieval of records by settlement date is shown below:

  • SELECT SCRIPT_NAME, FILE_NAME, SETTLEMENT_DATE, CREATED_ON_DATE FROM APPS.XTR_MTS_RECORDS_V WHERE SETTLEMENT_DATE BETWEEN :p_from AND :p_to ORDER BY SETTLEMENT_DATE;
  • SELECT FILE_NAME, COUNT(*) FROM APPS.XTR_MTS_RECORDS_V GROUP BY FILE_NAME HAVING COUNT(*) > 1; — duplicate detection per source file.
  • SELECT SCRIPT_NAME, MAX(CREATED_ON_DATE) FROM APPS.XTR_MTS_RECORDS_V GROUP BY SCRIPT_NAME; — confirmation that each loader has run and produced records.

Because the view exposes only five columns, it should be treated as a constrained interface; queries requiring the complete XTR_MTS_RECORDS column set must read the base table directly. However, for settlement-date-centric reporting — the query pattern most often associated with this object — the view provides a clean, documented access path in both 12.1.1 and 12.2.2.