Search Results no_reval




Overview
Explore in AI Chat

Overview

APPS.XTR_STOCK_ELIGIBLE_DEALS_V is a reporting view in the Oracle E-Business Suite Treasury (ETRM) module, exposed under the APPS schema. It presents stock-type deals that qualify for revaluation processing within a given accounting period. The view is intentionally shaped to conform to a generic "eligible deals" column layout used by ETRM's revaluation engine, which consumes a uniform set of columns (deal identifiers, currency, amounts, dates, and pricing attributes) regardless of the underlying instrument type.

The view is read-only and does not persist data. Its role is to supply candidate rows to the fair-value or market-value revaluation programs, which then determine which positions require an accounting revaluation entry. Because the view filters out cancelled deals, already-processed deals, and deals excluded from revaluation by policy, downstream consumers receive a pre-qualified population without needing to re-implement ETRM's eligibility logic.

The user's search term "no_reval" maps directly to a hard-coded predicate in the view definition: D.PRICING_MODEL <> 'NO_REVAL'. Any deal whose pricing model is set to NO_REVAL is deliberately excluded, since such instruments are not subject to revaluation under ETRM's valuation rules. This single filter is frequently the reason a stock deal appears absent from revaluation output, making the view's logic an important diagnostic reference.

Underlying Base Objects

The view is defined over two documented base objects, both referenced through APPS synonyms:

The join is an equality join on COMPANY_CODE (plus the fixed parameter code), meaning only stock deals belonging to companies that maintain an ACCNT_TSDTM parameter record will be returned.

Key Columns

  • DEAL_NO, DEAL_TYPE, DEAL_SUBTYPE, STATUS_CODE — deal identity and lifecycle attributes; DEAL_TYPE is fixed to 'STOCK' and DEAL_SUBTYPE to 'BUY' by the view's filters.
  • COMPANY_CODE, PORTFOLIO_CODE, MARKET_DATA_SET, PRICING_MODEL — organizational and valuation context. PRICING_MODEL is the column that carries the NO_REVAL exclusion.
  • ELIGIBLE_DATE — derived via DECODE(CP.PARAMETER_VALUE_CODE, 'TRADE', D.DEAL_DATE, D.START_DATE). When the ACCNT_TSDTM parameter resolves to 'TRADE', the deal date is used; otherwise the start date is returned. This governs which date drives revaluation eligibility.
  • FACE_VALUE, FX_REVAL_PRINCIPAL_BAL, FXO_SELL_REF_AMOUNT — mapped from START_AMOUNT, QUANTITY, and REMAINING_QUANTITY respectively.
  • TRANSACTION_RATE, TRANSACTION_NO — mapped from CAPITAL_PRICE and NVL(D.TRANSACTION_NO, 1).
  • Placeholder columns — ACCOUNT_NO, CAP_OR_FLOOR, CURRENCYB, DISCOUNT_YIELD, EXPIRY_DATE, MATURITY_DATE, PREMIUM_*, SETTLE_*, SWAP_REF, YEAR_BASIS, and YEAR_CALC_TYPE are cast as NULL or TO_DATE/TO_NUMBER(NULL) to satisfy the generic eligible-deals contract. They carry no stock-specific meaning.

Common Use Cases and Queries

The principal use case is auditing which stock deals will be picked up by revaluation, and diagnosing why a specific deal is excluded. The most common diagnostic query checks whether a deal has been filtered by the NO_REVAL pricing model:

  • SELECT deal_no, pricing_model FROM xtr_deals WHERE deal_type = 'STOCK' AND deal_subtype = 'BUY' AND pricing_model = 'NO_REVAL';
  • SELECT company_code, deal_no, eligible_date, face_value FROM apps.xtr_stock_eligible_deals_v WHERE deal_no = :deal_no;
  • SELECT deal_no, currencya, portfolio_code FROM apps.xtr_stock_eligible_deals_v WHERE company_code = :company_code ORDER BY eligible_date;

Other scenarios include reconciliation of revaluation batches (joining DEAL_NO back to revaluation result tables), period-end reporting of revaluable stock exposures, and integration extracts where the view's fixed column layout is consumed by downstream valuation systems. Because the view excludes rows where LAST_REVAL_BATCH_ID is populated, it also serves as a ready-to-process worklist for the next revaluation run.