Results for “multiple_settlements”

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

Overview

XTR_BIS_CASHFLOWS_V is an APPS-owned database view in the Oracle E-Business Suite Treasury (XTR) module. It presents the cashflows generated by Treasury deals that carry a CURRENT deal status, consolidating them into a single result set suitable for cashflow analysis and cash book reporting. The view is a union-based construct: it combines rows drawn from the existing cashflow view XTR_CASHFLOWS_V with rows derived directly from XTR_DEAL_DATE_AMOUNTS, and it further integrates intra-statement activity sourced from the bank statement tables CE_INTRA_STMT_HEADERS and CE_INTRA_STMT_LINES.

Its role is primarily analytical and reporting-oriented, exposing both net cashflow amounts and the descriptive attributes needed to summarize flows by counterparty, company, portfolio, currency, and bank account. Because it surfaces Treasury deal cashflows alongside intra-statement lines, it is relevant to reconciliation and liquidity-review processes rather than to transactional data entry.

Underlying Base Objects

The view is defined over a documented set of APPS objects. Treasury cashflow and deal data are sourced from XTR_CASHFLOWS_V, XTR_DEAL_DATE_AMOUNTS, XTR_DEAL_TYPES, XTR_DEAL_SUBTYPES, XTR_AMOUNT_TYPES, and XTR_PARTIES_V. Party and access context are provided through XTR_PARTY_INFO and the XTR_USER_ACCESS package. Banking detail is drawn from XTR_BANK_ACCOUNTS and CE_BANK_ACCOUNTS.

Intra-statement activity is contributed by CE_INTRA_STMT_HEADERS and CE_INTRA_STMT_LINES, with statement numbers and transaction types translated through the CE_LOOKUPS and FND_LOOKUPS views. Organizational and ledger context is resolved via HR_OPERATING_UNITS and GL_LEDGER_LE_V, while FND_GLOBAL supplies session-level identifiers such as the current user and responsibility. The relationship is a read-only projection: the view does not store data and joins the party, deal, and bank account objects on company code, deal type, subtype, amount type, and account number.

Key Columns

• DEAL_NUMBER / STATEMENT_NUMBER — Identifier for the Treasury deal or intra-statement source record; the first column is cast to character.
• DDA_DEAL_TYPE / DDA_DEAL_SUBTYPE — Deal classification codes used to distinguish deal families and subtypes.
• TRANSACTION_RATE — Rate applied to the cashflow amount.
• STATUS_CODE — Deal status; the view is scoped to CURRENT deals.
• CURRENCY_CODE — Currency of the cashflow amount.
• TRX_DATE / AMOUNT_DATE — Transaction or amount date governing when the cashflow falls.
• AMOUNT — Cashflow value; for certain deal subtypes the sign is inverted through a DECODE expression to reflect direction.
• BANK_CODE — Bank associated with the flow or account.
• COMPANY_CODE / COMPANY_ACCOUNT — Company and account responsible for the flow.
• SHORT_NAME — Party short name resolved from XTR_PARTIES_V.
• PRODUCT_TYPE, PORTFOLIO_CODE, CPARTY_CODE, CLIENT_CODE — Deal categorization attributes.
• DEALER, SETTLE, MULTIPLE_SETTLEMENTS — Processing and settlement indicators.

Common Use Cases and Queries

Typical usage focuses on net cashflow summaries and cash book review by company, currency, or portfolio. Analysts filter on a forward date horizon, since the union restricts cashflow rows to transactions dated on or after the current system date.

• Net cashflow by currency: SELECT CURRENCY_CODE, SUM(AMOUNT) FROM XTR_BIS_CASHFLOWS_V GROUP BY CURRENCY_CODE;
• Cash book by company: SELECT COMPANY_CODE, SHORT_NAME, SUM(AMOUNT) FROM XTR_BIS_CASHFLOWS_V GROUP BY COMPANY_CODE, SHORT_NAME;
• Intra-statement review: SELECT STATEMENT_NUMBER, AMOUNT FROM XTR_BIS_CASHFLOWS_V WHERE DDA_DEAL_TYPE = 'INTRA';

Because the view unions multiple sources, aggregations should be validated against the underlying Treasury deal and bank statement records when reconciling results.