Search Results premium_ccy




Overview
Explore in AI Chat

Overview

XTR_TMM_ELIGIBLE_DEALS_V is a Treasury (XTR) reporting view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It presents the population of Treasury Money Market (TMM) deals that are candidates for revaluation processing within the Oracle Treasury module. The view filters the deal population to those instruments that carry an active revaluation pricing model, are not cancelled, and have not yet been assigned to a revaluation batch. In this sense it functions as a working set — the deals a revaluation run is expected to pick up on its next execution.

Because the view consolidates deal attributes with company-level accounting parameters, it is used both by concurrent revaluation programs and by reporting queries that need to identify outstanding or unprocessed money market positions. The column naming convention (CURRENCYA, CURRENCYB, SWAP_REF, and so on) is deliberately aligned with the common deal interface structures used across Treasury, allowing the view to act as a normalized source for downstream processing. Notably, several columns are emitted as literal NULL placeholders and are documented with a value of NULL in the view text, which signifies that the field is structurally required but not populated for the TMM deal type.

Underlying Base Objects

The view is defined over two referenced base objects, both accessed through synonyms in the APPS schema:

The join is an equijoin on COMPANY_CODE with the parameter filter applied in the WHERE clause. Both base objects are referenced as synonyms, indicating that the view resolves to the underlying APPS-owned tables at runtime rather than to alternate schemas.

Key Columns

The view exposes a wide attribute set. The most operationally significant columns include:

Common Use Cases and Queries

Typical uses include validating the revaluation queue before running the revaluation concurrent program, reconciling eligible deals by company or portfolio, and investigating why a specific deal was or was not selected. A representative query is:

  • SELECT DEAL_NO, COMPANY_CODE, ELIGIBLE_DATE, FACE_VALUE FROM XTR_TMM_ELIGIBLE_DEALS_V WHERE COMPANY_CODE = :p_company;
  • SELECT PORTFOLIO_CODE, COUNT(*) FROM XTR_TMM_ELIGIBLE_DEALS_V GROUP BY PORTFOLIO_CODE;
  • SELECT DEAL_NO, PREMIUM_CCY, PREMIUM_AMOUNT FROM XTR_TMM_ELIGIBLE_DEALS_V; — noting PREMIUM_CCY will return NULL.

Because the view already applies the CANCELLED, NO_REVAL, and batch-assignment filters, ad hoc queries against it return only currently eligible deals without additional predicates.