Results for “xtr_deals_v”

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

Overview

XTR_DEALS_V is a database view owned by the APPS schema in Oracle E-Business Suite Release 12.1.1 and 12.2.2. It is part of the XTR – Treasury product, the module responsible for deal capture, confirmation, settlement, and revaluation of treasury instruments such as foreign exchange contracts, money market deals, bonds, forwards, and interest rate swaps. The view presents a denormalized, read-optimized projection of treasury deal data. Rather than requiring report developers and integration builders to join the base deal table directly, XTR_DEALS_V exposes the full set of deal attributes through a single definer's-rights view, allowing callers to query deal information without holding privileges on the underlying objects. Its status is VALID, and it is documented in the ETRM repository as an APPS-owned view over the core treasury deal table plus supporting security and authority objects.

Underlying Base Objects

The documented referenced objects for XTR_DEALS_V are three: XTR_DEALS (SYNONYM), XTR_COMPANY_AUTHORITIES (SYNONYM), and XTR_USER_ACCESS (PACKAGE). The view text is a SELECT over the XTR_DEALS base table, aliased as XD, projecting columns such as DEAL_NO, DEAL_TYPE, DEAL_SUBTYPE, and DEAL_DATE. The inclusion of XTR_COMPANY_AUTHORITIES and XTR_USER_ACCESS indicates that the view is not a straight pass-through; it is a secured view that filters or augments the deal rows according to the calling user's company-level authority and the user access rules resolved by the XTR_USER_ACCESS package. This pattern restricts the rows returned so that a user or responsibility only sees deals belonging to the companies they are authorized to access, consistent with standard XTR treasury security behavior.

Key Columns

The view exposes a comprehensive column list grouped around deal identification and classification, instrument-specific attributes, monetary amounts, and audit fields. Identification columns include DEAL_NO, INTERNAL_TICKET_NO, CLIENT_REF, CPARTY_REF, CONTRACT_NOS, and the various cross-reference fields FX_PD_DEAL_NO, FX_RO_DEAL_NO, FXD_DEAL_NO, FXO_DEAL_NO, and INT_SWAP_REF. Classification columns include DEAL_TYPE, DEAL_SUBTYPE, CURRENCY, CURRENCY_BUY, CURRENCY_SELL, DEALER_CODE, CLIENT_CODE, and BROKER. Monetary and rate columns include BUY_AMOUNT, BUY_HCE_AMOUNT, FACE_VALUE_AMOUNT, FACE_VALUE_HCE_AMOUNT, INTEREST_AMOUNT, INTEREST_HCE_AMOUNT, BROKERAGE_AMOUNT, BASE_RATE, COUPON_RATE, and CONTRACT_RATE. Date and accrual columns include COMMENCE_DATE, DEAL_DATE, EXPIRY_DATE, ACCRUAL_FROM, ACCRUAL_TO, BASE_DATE, and CUM_COUPON_DATE. Audit and workflow columns include CREATED_BY, CREATED_ON, ACTION_STATUS, AUDIT_INDICATOR, DUAL_AUTHORISATION_BY, DUAL_AUTHORISATION_ON, KNOCK_EXECUTED_BY, KNOCK_EXECUTED_ON, ARCHIVE_BY, and ARCHIVE_DATE.

Common Use Cases and Queries

Typical consumers of XTR_DEALS_V include custom treasury reports, reconciliation extracts, and interfaces that feed downstream risk or general ledger systems. Because the view applies user access and company authority filtering, it is preferred over direct queries against XTR_DEALS in custom code where the session user must be respected. A common query lists active foreign exchange deals for a currency and date range:

• SELECT deal_no, deal_type, cparty_code, currency_buy, currency_sell, buy_amount, deal_date, expiry_date FROM xtr_deals_v WHERE deal_type = 'FX' AND currency_buy = 'USD' AND deal_date BETWEEN :p_from AND :p_to ORDER BY deal_date;
• SELECT deal_no, deal_type, face_value_amount, interest_amount, base_rate, accrual_from, accrual_to FROM xtr_deals_v WHERE action_status = 'AUTHORISED' AND currency = :p_ccy;
• SELECT deal_no, contract_nos, client_ref, cparty_ref, fx_pd_deal_no, int_swap_ref FROM xtr_deals_v WHERE deal_date >= TRUNC(SYSDATE) - 30;

Reports should reference the underscored column names exactly as exposed by the view, and joins to other XTR views should use DEAL_NO as the common key. All access should go through the APPS schema or a synonym granted to the reporting schema.