Search Results settle_date




Overview
Explore in AI Chat

Overview

XTR_FX_ELIGIBLE_DEALS_V is a reporting and integration view in the Oracle E-Business Suite Treasury (XTR) module, owned by the APPS schema. It exposes foreign exchange (FX) deals that are eligible for revaluation processing. The view functions as a filtered projection of the transaction-level deal data, restricting output to deals where DEAL_TYPE is 'FX', the deal has not been cancelled, the pricing model is not 'NO_REVAL', and the LAST_REVAL_BATCH_ID is null — meaning the deal has not yet been picked up by a revaluation batch.

Because it is a view rather than a base table, it provides a read-only, denormalized surface for reporting tools, concurrent programs, and interfaces that need to identify open FX deals awaiting mark-to-market or revaluation. The MARKET_DATA_SET column, which the user searched for, identifies the market data set associated with each deal and is central to how revaluation engine pricing inputs are resolved.

Underlying Base Objects

The view is defined solely over XTR_DEALS (referenced in the APPS schema via a synonym). The view text selects approximately 37 columns, aliasing or transforming several of them. Notable transformations include NVL(START_DATE, VALUE_DATE) producing EFFECTIVE_DATE, a DECODE that substitutes START_DATE for spot deals to produce ELIGIBLE_DATE, and NVL(TRANSACTION_NO, 1) defaulting the transaction number. Preference columns such as ACCOUNT_NO, CAP_OR_FLOOR, CONTRACT_CODE, PREMIUM_CCY, and SWAP_REF are projected as literal NULLs, allowing the view to present a uniform FX shape alongside other deal-eligible views used by the same downstream revaluation process.

Key Columns

  • DEAL_NO / DEAL_SUBTYPE / DEAL_TYPE — Identity and classification of the FX deal (e.g., SPOT, FORWARD).
  • ELIGIBLE_DATE / EFFECTIVE_DATE — Date used to determine participation in a revaluation run; spot deals use START_DATE or VALUE_DATE.
  • MARKET_DATA_SET — The market data set key driving rate sourcing for revaluation of the deal.
  • PRICING_MODEL — Valuation methodology; deals with 'NO_REVAL' are excluded.
  • CURRENCYA / CURRENCYB — The buy and sell currencies of the FX transaction.
  • FACE_VALUE / FXO_SELL_REF_AMOUNT — Buy amount and sell amount, respectively.
  • STATUS_CODE — Deal lifecycle state; cancelled deals are excluded from the view.
  • TRANSACTION_RATE / YEAR_BASIS / YEAR_CALC_TYPE — Contract rate and day-count conventions.
  • LAST_REVAL_BATCH_ID (filter) — Non-null values mark deals already processed, so they are excluded from this view.

Common Use Cases and Queries

Typical usage includes feeding revaluation concurrent programs, reconciling unprocessed FX exposures, and reporting on market data set coverage across open FX deals.

List eligible deals for a market data set:

  • SELECT deal_no, deal_subtype, currencya, currencyb, eligible_date, market_data_set FROM xtr_fx_eligible_deals_v WHERE market_data_set = :p_market_data_set;

Count unprocessed FX deals by subtype:

  • SELECT deal_subtype, COUNT(*) FROM xtr_fx_eligible_deals_v GROUP BY deal_subtype;

Identify forward deals maturing within a window:

  • SELECT deal_no, maturity_date FROM xtr_fx_eligible_deals_v WHERE deal_subtype = 'FORWARD' AND maturity_date BETWEEN :from_date AND :to_date;

Because the view excludes cancelled deals and any deal already assigned a revaluation batch, results reflect only the actionable population for the next revaluation cycle.