Search Results cap_or_floor




Overview
Explore in AI Chat

Overview

XTR_IG_ELIGIBLE_DEALS_V is a Treasury (XTR) module view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It presents intergroup transfer records that are eligible for FX revaluation processing. The view normalizes data from the XTR_INTERGROUP_TRANSFERS table into a deal-oriented column layout, so downstream revaluation, accounting, and reporting logic can consume intergroup transfers as if they were standard treasury deals.

The view filters its source rows using three documented predicates: the intergroup transfer must not have been processed by a batch (LAST_BATCH_ID IS NULL), the deal's company code must resolve to a valid party in XTR_PARTY_INFO tied to a set of books, the functional currency of that set of books must differ from the transfer currency, and the pricing model must not be 'NO_REVAL'. In effect, the view returns only cross-currency intergroup positions that still require revaluation. Many columns are deliberately projected as NULL or zero because they belong to the broader deal interface but have no meaning for intergroup transfers.

Underlying Base Objects

The view is defined over three documented objects. XTR_INTERGROUP_TRANSFERS (referenced through a synonym) is the primary driver, supplying the deal number, company code, currency, deal type, product type, portfolio, transfer date, balance, and transaction number. XTR_PARTY_INFO (synonym) provides the party-to-set-of-books mapping used to join the transfer to a ledger. GL_SETS_OF_BOOKS (view) supplies the functional currency of that ledger, which is compared against the transfer currency to determine eligibility. The join chain is: IG.COMPANY_CODE = PI.PARTY_CODE, then PI.SET_OF_BOOKS_ID = GL.SET_OF_BOOKS_ID, with the final currency and pricing model filters applied to restrict the result set. Because the base objects are synonyms and a view, the definition remains stable across the 12.1.1 and 12.2.2 releases documented under ETRM 12.2.2 metadata.

Key Columns

Common Use Cases and Queries

Typical scenarios include identifying intergroup transfers awaiting FX revaluation, reconciling balances per company code and currency, and feeding downstream deal interfaces. A representative query filters by eligible date:

  • SELECT deal_no, company_code, currencya, eligible_date, face_value, deal_subtype FROM xtr_ig_eligible_deals_v WHERE eligible_date BETWEEN :from_date AND :to_date;
  • SELECT company_code, currencya, SUM(face_value) FROM xtr_ig_eligible_deals_v GROUP BY company_code, currencya;
  • SELECT deal_no, product_type, pricing_model FROM xtr_ig_eligible_deals_v WHERE currencya = 'EUR' ORDER BY eligible_date;

Because eligibility depends on the currency mismatch and the LAST_BATCH_ID filter, results change as batches are run; queries should therefore be treated as point-in-time extracts.