Search Results exchange_code




Overview
Explore in AI Chat

Overview

XTR_A_DEALS_V is an APPS-owned database view within the Oracle EBS Treasury (XTR) module. It belongs to the family of "A" (archive/active deal) objects in the Treasury data model and is documented in ETRM 12.2.2 with the status VALID and a description of "- Retrofitted." The view presents a wide, denormalized projection of treasury deal information, exposing interest-rate, foreign-exchange, bond, swap, option, and brokerage attributes in a single relational surface. Its principal role is to serve as a reporting and integration layer over the underlying deals entity, allowing concurrent programs, Discoverer workbooks, custom reports, and outbound interfaces to query deal data without joining the numerous normalized columns of the base table directly.

The view is particularly relevant to the search term exchange_code, which it exposes as an explicit column. This column carries the exchange identifier associated with a deal, a value commonly used when reconciling exchange-traded instruments and when segregating reporting by trading venue.

Underlying Base Objects

The documented view metadata for ETRM 12.2.2 identifies a single referenced base object: XTR_A_DEALS, accessed through a synonym in the APPS schema. XTR_A_DEALS is the Treasury deal archive table that stores both active and archived transaction records. Because the view is defined as a column-selective projection rather than a join, its relationship to the base object is one-to-one: each qualifying row in XTR_A_DEALS maps to a corresponding row in XTR_A_DEALS_V. The view text indicates that rows are drawn from the base table without aggregation, so row counts and unique transaction identifiers (TRANSACTION_NO, NI_DEAL_NO) remain consistent between the view and its base object.

Key Columns

The view exposes a large number of columns spanning several functional areas. The following are of particular importance:

Common Use Cases and Queries

Typical uses include venue-level deal reporting, reconciliation of exchange-traded positions, feeds into downstream risk or settlement systems, and ad hoc analysis via BI Publisher or Oracle Discoverer. A frequent query filters on the exchange code and deal status:

  • SELECT transaction_no, deal_type, exchange_code, currency, buy_amount, status_code FROM apps.xtr_a_deals_v WHERE exchange_code = :p_exchange_code;
  • SELECT deal_type, COUNT(*), SUM(buy_amount) FROM apps.xtr_a_deals_v WHERE archive_date IS NULL GROUP BY deal_type;
  • SELECT transaction_no, cparty_code, coupon_rate, fixed_or_floating_rate FROM apps.xtr_a_deals_v WHERE currency = 'USD' AND status_code = 'ACTIVE';

Because the view simply reshapes XTR_A_DEALS, performance follows the base table's indexes; filtering on TRANSACTION_NO or exchange_code and restricting by archive status generally yields the most efficient plans.