Search Results multiple_settlements

Overview

CE_XTR_CASHFLOWS_V is an APPS-owned database view within the Oracle E-Business Suite Cash Management (CE) module. It is documented as a forecasting source – treasury, meaning it serves as a consolidated read-only projection of expected and actual treasury cash flows that feeds the Cash Management cash forecasting engine and related reporting. The view distills deal-level settlement and amount information maintained by Oracle Treasury (XTR) into a structure that Cash Management can consume without directly querying the Treasury transaction tables.

In the Oracle EBS 12.1.1 and 12.2.2 releases the object retains a VALID status and the same APPS ownership, and its definition reflects the standard multi-organization and legal-entity security model through ORG_ID and SET_OF_BOOKS_ID columns. The name of the view, incorporating "XTR" (Treasury) and "CASHFLOWS", signals that it is a bridge object: it converts Treasury deal cash flow schedules into the currency, date, and amount semantics required by Cash Management forecasting.

Underlying Base Objects

The view is defined over six documented base objects:

• XTR_DEAL_DATE_AMOUNTS (synonym) – the driving table, aliased DDA, supplying deal number, dates, amounts, currency, status, and the MULTIPLE_SETTLEMENTS flag.
• XTR_DEAL_TYPES (synonym, alias DT) – supplies user deal type and the FX/MM expiration flag.
• XTR_DEAL_SUBTYPES (synonym, alias ST) – supplies user deal subtype.
• XTR_PARTY_INFO (synonym, aliases P and P1) – resolves company and counterparty party information, legal entity, and set of books.
• XTR_AMOUNT_TYPES (synonym, alias AT) – supplies the amount type name.
• CE_BANK_ACCTS_GT_V (view, alias BA) – the global temporary bank account view providing BANK_ACCOUNT_ID and matching on owner org, currency, and account number.

Joins between XTR_DEAL_DATE_AMOUNTS, XTR_DEAL_TYPES, XTR_DEAL_SUBTYPES, and XTR_AMOUNT_TYPES are inner joins; party and bank account joins are outer joins (indicated by the (+) operator) on COMPANY_CODE, CPARTY_CODE, and the bank account attributes.

Key Columns

The view exposes 32 columns. The most operationally significant are:

• DEAL_NUMBER, TRANSACTION_NUMBER, REFERENCE_ID – identifiers for the Treasury deal and its date/amount line.
• DDA_DEAL_TYPE, DDA_DEAL_SUBTYPE, DEAL_TYPE, CATEGORY, CONTRACT_TYPE – deal classification attributes.
• TRX_DATE – derived from NVL(DDA.ACTUAL_SETTLEMENT_DATE, DDA.AMOUNT_DATE), the expected cash flow date.
• AMOUNT, CURRENCY_CODE, TRANSACTION_RATE – the cash flow value, currency, and rate.
• STATUS_CODE – excludes CANCELLED deals at the view level.
• MULTIPLE_SETTLEMENTS – the flag that determines whether a deal is eligible; only records with value 'N' (or NULL, via NVL) are surfaced.
• RECONCILED_REFERENCE – reconciliation linkage.
• ORG_ID, SET_OF_BOOKS_ID, BANK_ACCOUNT_ID, COMPANY_CODE, CPARTY_CODE – security, accounting, and account context.
• DDA_DEAL_TYPE_NAME, DDA_DEAL_SUBTYPE_NAME, TYPE_OF_AMOUNT, AMOUNT_TYPE_NAME, COUNTERPARTY – descriptive labels for reporting.

Common Use Cases and Queries

Typical consumption includes Cash Management forecasting, treasury deal reporting, and reconciliation of expected settlements. A representative query filtered by the user's search term is:

• SELECT deal_number, trx_date, amount, currency_code FROM ce_xtr_cashflows_v WHERE multiple_settlements = 'N' AND status_code <> 'CANCELLED';
• Forecast by currency and date: SELECT currency_code, trx_date, SUM(amount) FROM ce_xtr_cashflows_v GROUP BY currency_code, trx_date;
• Legal-entity scoping: SELECT * FROM ce_xtr_cashflows_v WHERE org_id = :org_id AND set_of_books_id = :sob;
• Counterparty analysis: SELECT counterparty, SUM(amount) FROM ce_xtr_cashflows_v GROUP BY counterparty;

Because the view already excludes cancelled and zero-amount lines and forces MULTIPLE_SETTLEMENTS to 'N', callers generally do not need to repeat those predicates, though applying them explicitly improves clarity and can aid the optimizer.