Search Results dda_deal_subtype




Overview
Explore in AI Chat

Overview

XTR_CASHFLOWS_V is a reporting view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the XTR – Treasury (External Treasury Management / ETRM) product family. The view is classified as VALID and is available in both Oracle EBS 12.1.1 and 12.2.2. Its documented purpose is to present internal Treasury and external cashflows in a single, denormalised result set suitable for reporting, reconciliation, and downstream integration.

The view draws its data from the deal date/amount table, joining descriptive reference tables so that raw deal identifiers (deal type, subtype, amount type, bank account) are resolved to their user-facing equivalents. This makes XTR_CASHFLOWS_V particularly useful where business users require readable cashflow listings rather than coded values. A search for the column or attribute "dda_deal_type" typically lands on this view because DDA_DEAL_TYPE is one of the exposed columns, representing the DEAL_TYPE attribute of the underlying XTR_DEAL_DATE_AMOUNTS record.

The view excludes cancelled deals, zero-value cashflows, cancellation deals (DEAL_TYPE = 'CA'), and multiple-settlement deals, so its result set reflects only single, active, non-zero cashflows.

Underlying Base Objects

XTR_CASHFLOWS_V is defined over five base objects, all referenced through public synonyms in the APPS schema:

The joins on DEAL_TYPES, DEAL_SUBTYPES, and AMOUNT_TYPES are inner joins, meaning a cashflow row only appears if matching reference definitions exist. The bank account join is an outer join, so cashflows without a matching bank account still appear, with a null BANK_CODE.

Key Columns

The documented column list includes DEAL_NUMBER, DDA_DEAL_TYPE, DDA_DEAL_SUBTYPE, TRANSACTION_RATE, STATUS_CODE, CURRENCY_CODE (sourced as DDA.CURRENCY), TRX_DATE (NVL of ACTUAL_SETTLEMENT_DATE and AMOUNT_DATE), AMOUNT, COMPANY_CODE, COMPANY_ACCOUNT, BANK_CODE, PRODUCT_TYPE, PORTFOLIO_CODE, CPARTY_CODE, CLIENT_CODE, DEAL_TYPE, CATEGORY, DEAL_SUBTYPE, TYPE_OF_AMOUNT, AMOUNT_TYPE, TRANSACTION_NUMBER, DEALER, SETTLE, CONTRACT_TYPE, and MULTIPLE_SETTLEMENTS.

  • DEAL_TYPE / DDA_DEAL_TYPE — the coded deal classification (the user-searched term maps here); USER_DEAL_TYPE provides the descriptive equivalent from XTR_DEAL_TYPES.
  • DEAL_SUBTYPE / DDA_DEAL_SUBTYPE — subordinate classification, resolved to USER_DEAL_SUBTYPE.
  • AMOUNT_TYPE / TYPE_OF_AMOUNT — identifies the nature of the amount, with USER_AMOUNT_TYPE as the display value.
  • TRX_DATE — the effective cashflow date, deriving from actual settlement date where populated, else amount date.
  • STATUS_CODE — deal status; cancelled rows are already filtered out at view level.
  • COMPANY_CODE / COMPANY_ACCOUNT / BANK_CODE — identify the owning entity and settling bank account.
  • SETTLE / MULTIPLE_SETTLEMENTS — control flags for settlement behaviour, with multiple-settlement deals excluded.

Common Use Cases and Queries

Typical uses include treasury cash position reporting, counterparty and portfolio exposure listings, and feeding cashflow extracts to external systems. Because the view already applies the cancelled, zero-amount, cancellation, and multiple-settlement filters, reports built on it are consistent with the ETRM reporting baseline.

  • Cashflows by deal type and currency for a period.
  • Counterparty (CPARTY_CODE) exposure aggregation.
  • Bank account settlement listings using BANK_CODE.
  • Feed queries for downstream cash forecasting.

Sample SQL:

  • SELECT DEAL_NUMBER, USER_DEAL_TYPE, CURRENCY_CODE, TRX_DATE, AMOUNT FROM XTR_CASHFLOWS_V WHERE TRX_DATE BETWEEN :p_from AND :p_to ORDER BY TRX_DATE;
  • SELECT CPARTY_CODE, CURRENCY_CODE, SUM(AMOUNT) FROM XTR_CASHFLOWS_V GROUP BY CPARTY_CODE, CURRENCY_CODE;
  • SELECT DEAL_TYPE, DEAL_SUBTYPE, COUNT(*) FROM XTR_CASHFLOWS_V GROUP BY DEAL_TYPE, DEAL_SUBTYPE;

Oracle proprietary and confidential. Refer to Oracle legal notices for usage terms.