Search Results dda_deal_type_name

Overview

The APPS.CE_XTR_CASHFLOWS_V view is a public database view in the Oracle E-Business Suite Treasury (ETRM) module. It exposes treasury deal transactions used for cash forecasting, consolidating deal, transaction, party, and settlement information into a single queryable structure. The Cash Forecasting program consumes this view to generate projected cash inflows and outflows derived from trading activities and exposures. Based on the forecast template definition and the forecast submission criteria, the Cash Forecasting program selects only the applicable deals from this view to determine forecast amounts. Because the view is designated public, it is also a supported source for custom reporting and other data requirements, particularly for users who need to report on treasury deal activity without navigating the underlying normalized Treasury tables directly.

Underlying Base Objects

The documented base objects referenced by the view are:

• CE_BANK_ACCTS_GT_V (VIEW) — supplies bank account and company account context.
• XTR_AMOUNT_TYPES (SYNONYM) — supplies amount type codes and their descriptive names.
• XTR_DEAL_DATE_AMOUNTS (SYNONYM) — supplies dated deal amount records that drive transaction dates and amounts.
• XTR_DEAL_SUBTYPES (SYNONYM) — supplies deal subtype codes and their names.
• XTR_DEAL_TYPES (SYNONYM) — supplies deal type codes and their names.
• XTR_PARTY_INFO (SYNONYM) — supplies counterparty, client, and related party details.

The view joins the transactional deal data held in XTR_DEAL_DATE_AMOUNTS with the setup and reference data held in XTR_DEAL_TYPES, XTR_DEAL_SUBTYPES, and XTR_AMOUNT_TYPES, resolving codes to descriptive names. Party information is joined from XTR_PARTY_INFO, and account context is provided through CE_BANK_ACCTS_GT_V. The CE prefix indicates Cash Management integration, reflecting the view's role as the bridge between Treasury deal records and cash forecasting.

Key Columns

The view exposes deal identifiers, classification, financial values, dates, and organizational context. Notable columns include DEAL_NUMBER and TRANSACTION_NUMBER, which uniquely identify the deal and its transaction line. DDA_DEAL_TYPE and DDA_DEAL_SUBTYPE carry the deal type and subtype codes, while DDA_DEAL_TYPE_NAME and DDA_DEAL_SUBTYPE_NAME (the latter being the column users most commonly search for) provide the corresponding descriptive names. AMOUNT, TYPE_OF_AMOUNT, AMOUNT_TYPE_NAME, and TRANSACTION_RATE describe the financial magnitude and rate of each transaction. TRX_DATE supplies the transaction date used for forecast timing. CURRENCY_CODE, COMPANY_CODE, COMPANY_ACCOUNT, PRODUCT_TYPE, PORTFOLIO_CODE, and SET_OF_BOOKS_ID provide currency, company, product, portfolio, and ledger context. Party columns include CPARTY_CODE, CLIENT_CODE, and COUNTERPARTY. Settlement and reconciliation are represented by SETTLE, MULTIPLE_SETTLEMENTS, and RECONCILED_REFERENCE. STATUS_CODE, CATEGORY, DEAL_TYPE, DEAL_SUBTYPE, DEALER, CONTRACT_TYPE, and ORG_ID complete the operational and multi-organization context.

Common Use Cases and Queries

Typical scenarios include forecasting projected cash flows, reconciling Treasury deals to bank statement lines through RECONCILED_REFERENCE, and reporting deal activity by portfolio or counterparty. The following query retrieves active cash flow transactions with resolved deal classification:

SELECT deal_number,
       dda_deal_type_name,
       dda_deal_subtype_name,
       counterparty,
       currency_code,
       trx_date,
       amount,
       type_of_amount
FROM   apps.ce_xtr_cashflows_v
WHERE  org_id = :p_org_id
AND    trx_date BETWEEN :p_start_date AND :p_end_date
ORDER BY trx_date, deal_number;

To summarize forecast amounts by subtype for a given period:

SELECT dda_deal_subtype_name,
       SUM(amount) total_amount
FROM   apps.ce_xtr_cashflows_v
WHERE  org_id = :p_org_id
AND    trx_date BETWEEN :p_start_date AND :p_end_date
GROUP BY dda_deal_subtype_name
ORDER BY total_amount DESC;

Because the view resolves codes to names, it is well suited for custom Treasury reporting and integration extracts requiring human-readable deal type and subtype descriptions.