Search Results xtr_deals

Overview

The XTR_DEALS table is a core master data object within the Oracle E-Business Suite Treasury (XTR) module, specifically for versions 12.1.1 and 12.2.2. It serves as the central repository for recording and storing the fundamental attributes of all financial instrument deals entered into by an organization, excluding exposure transactions. Every executed transaction, such as a foreign exchange deal, money market deposit, or bond trade, is captured as a record in this table. Its primary role is to provide the single source of truth for deal inception data, which is subsequently referenced by numerous sub-modules for processing, settlement, revaluation, and reporting. The table's extensive network of foreign keys underscores its integral position in the Treasury data model, linking deals to counterparties, currencies, product definitions, accounting details, and statuses.

Key Information Stored

The table's structure is defined by its primary and foreign key relationships, which highlight its critical data elements. The primary key is DEAL_NO, a unique identifier for each transaction. Essential descriptive columns include DEAL_TYPE, PRODUCT_TYPE, and DEAL_SUBTYPE, which classify the financial instrument. Counterparty information is stored in CPARTY_CODE and RISKPARTY_CODE. Financial terms are captured in columns such as CURRENCY, CURRENCY_BUY, CURRENCY_SELL, REF_CCY, and CTY_CCY. The table also maintains vital lifecycle and control data, including STATUS_CODE (linked to XTR_DEAL_STATUSES), DEALER_CODE, PORTFOLIO_CODE, and references to revaluation batches via FIRST_REVAL_BATCH_ID and LAST_REVAL_BATCH_ID. Crucially, it holds foreign keys to the Cash Management module's CE_BANK_ACCT_USES_ALL table for accounting purposes, such as BUY_ACCT_USE_ID, SELL_ACCT_USE_ID, and MATURITY_ACCT_USE_ID.

Common Use Cases and Queries

This table is central to treasury operations and reporting. Common use cases include generating deal tickets and confirmations, populating position and risk management dashboards, feeding settlement and accounting entries, and supporting audit trails. Typical analytical queries involve joining to related master tables to produce comprehensive deal listings. For example, a report to list all active Foreign Exchange deals would join XTR_DEALS to XTR_DEAL_TYPES, XTR_COUNTERPARTIES, and XTR_MASTER_CURRENCIES. Another critical pattern is tracing accounting impacts by joining DEAL_NO to various XTR transaction tables (like XTR_DEAL_DATE_AMOUNTS) and then to the GL interface. Queries also frequently filter on STATUS_CODE to identify deals pending settlement or authorization, and on DEALER_CODE for performance analysis.

Related Objects

As indicated by its foreign keys, XTR_DEALS has dependencies and relationships with a wide array of objects within and beyond the XTR schema. Key related tables include:

• Master Definitions: XTR_DEAL_TYPES, XTR_PRODUCT_TYPES, XTR_DEAL_SUBTYPES, XTR_MASTER_CURRENCIES, XTR_BUY_SELL_COMBINATIONS.
• Counterparty & Limits: XTR_COUNTERPARTY_LIMITS (for both CPARTY and RISKPARTY).
• Lifecycle & Control: XTR_DEAL_STATUSES, XTR_DEALER_CODES, XTR_PORTFOLIOS, XTR_BATCHES.
• Instrument Specific: XTR_BOND_ISSUES, XTR_PAYMENT_SCHEDULE.
• Cross-Module Integration: CE_BANK_ACCT_USES_ALL (Cash Management) for bank account assignments.

This table is a parent to numerous transaction and settlement child tables (e.g., XTR_DEAL_DATE_AMOUNTS) not listed in the provided foreign key metadata but inherent to the module's design.