Results for “base_rate”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

XTR_FX_ROLL_PRE_DETAILS_V is a reporting view owned by the APPS schema within the XTR (Treasury) product module of Oracle E-Business Suite. It exposes pre-roll foreign exchange deal details — that is, transactions identified as candidates for rollover before the roll is finalized. The view presents a conventional projection over its base object, surfacing deal reference data along with buy and sell currency legs, amounts, rates, value dates, and settlement routing attributes. In Oracle EBS 12.1.1 and 12.2.2, such views serve as read-only interfaces for concurrent programs, BI Publisher reports, and outbound integrations that must not query Treasury base tables directly. Because the view is documented as VALID in the ETRM metadata, it is a supported access point for the FX rollover preprocessing data set. The column BUY_AMOUNT, which prompted the user's search, represents the notional amount purchased on the rollover-pending deal and is the primary monetary measure returned by the view.

Underlying Base Objects

The documented view metadata lists a single referenced base object: the synonym XTR_FX_ROLL_PRE_DETAILS. The view text confirms this relationship directly, selecting all twenty-four listed columns from that source with no joins, unions, filters, or aggregations. Consequently, the view is a one-to-one pass-through: every row in XTR_FX_ROLL_PRE_DETAILS produces exactly one row in the view, and row counts are identical between the two. No WHERE clause, GROUP BY, or DISTINCT is applied. The synonym resolves to the underlying Treasury table in the APPS schema at runtime. Because the view contains no calculation logic, all business meaning, validation, and population rules reside in the base table and the Treasury FX rollover processing programs that insert into it.

Key Columns

• REF_NUMBER — Reference identifier for the rollover candidate record.
• COMPANY_CODE — Legal entity or company context for the deal.
• CPARTY_CODE — Counterparty identifier associated with the transaction.
• DEAL_NO — Deal number of the FX transaction pending rollover.
• CURRENCY_BUY / CURRENCY_SELL — The currency legs of the FX deal.
• BUY_AMOUNT — Amount purchased on the deal; the principal monetary measure for the buy leg.
• SELL_AMOUNT — Amount sold on the deal; the matching measure for the sell leg.
• TRANS_RATE / BASE_RATE — Transaction rate between the currencies and the base (functional currency) rate.
• VALUE_DATE / DEAL_DATE — Value date and trade date of the transaction.
• MULTIPLE_TRANS_YN — Flag indicating whether the rollover spans multiple transactions.
• SETTLED_CURRENT — Indicator of settlement status for the current leg.
• ROLL_PRE / ROLL_PRE_ON / PREV_DEAL_NO — Rollover pre-selection flags, the rollover-pending reference, and the prior deal number being rolled.
• PORTFOLIO_CODE, CLIENT_CODE, DEALER_CODE — Treasury portfolio, client, and dealer attribution.
• SETTLEMENT_PARTY, SETTLEMENT_PARTY_ACCT, COMP_SETTLEMENT_ACCT — Settlement party and the counterparty and company settlement accounts.
• LIMIT_CODE — Credit limit code applied to the exposure.

Common Use Cases and Queries

The view is typically used to preview FX deals flagged for rollover before the roll is confirmed, to reconcile buy and sell notional amounts, and to feed downstream settlement or credit-limit reporting. A common query filters by company and value date:

• SELECT deal_no, currency_buy, buy_amount, currency_sell, sell_amount, trans_rate, value_date FROM xtr_fx_roll_pre_details_v WHERE company_code = :p_company AND value_date BETWEEN :p_from AND :p_to;
• SELECT ref_number, deal_no, prev_deal_no, buy_amount, sell_amount FROM xtr_fx_roll_pre_details_v WHERE roll_pre = 'Y' AND settled_current = 'Y';
• SELECT portfolio_code, SUM(buy_amount) FROM xtr_fx_roll_pre_details_v GROUP BY portfolio_code;
• The view can also be joined to XTR deal tables by DEAL_NO or PREV_DEAL_NO for detail enrichment.

Because the object is a simple view, query performance mirrors the base table's indexing; predicates on DEAL_NO, REF_NUMBER, and COMPANY_CODE are generally the most selective.