Search Results xtr_settlements_v




Overview
Explore in AI Chat

Overview

XTR_SETTLEMENTS_V is a Treasury (XTR) module view owned by the APPS schema that exposes the settlement transactions associated with Treasury deals. In Oracle E-Business Suite 12.1.1 and 12.2.2, it functions as the primary reporting and integration surface for settlement activity, presenting one row per cashflow-driven settlement instruction. The view is a filtered projection of the underlying date-and-amounts entity, restricted to records that represent payable or receivable settlement rather than purely informational or cancellation entries. Because it is a view rather than a table, it imposes no additional storage and always reflects the current state of the base data at query time. Its significance for reporting stems from the fact that it flattens dealer, counterparty, portfolio, accounting flexfield, and authorization attributes into a single denormalized result set, which allows settlement operations, treasury back-office staff, and downstream interfaces to retrieve deal-level settlement detail without navigating the normalized XTR deal schema. The view is documented as VALID in the APPS schema and is referenced by dashboards, reconciliation extracts, and payment-format integrations.

Underlying Base Objects

The view text selects exclusively from XTR_DEAL_DATE_AMOUNTS_V, aliased as A, which supplies the deal, transaction, cashflow, counterparty, and authorization columns. A second referenced object, the XTR_USER_ACCESS package, governs row-level access to Treasury data and is applied by the calling application rather than embedded in the view predicate itself. The view applies four documented filter conditions. First, CASHFLOW_AMOUNT must be non-zero, eliminating zero-value cashflows. Second, AMOUNT_TYPE must not be FXOBUY or FXOSELL, excluding FX outright buy and sell legs that settle through a different process. Third, EXP_SETTLE_REQD defaulted to 'Y' must equal 'Y', and MULTIPLE_SETTLEMENTS defaulted to 'N' must equal 'N', so only single expected settlements are surfaced. Fourth, STATUS_CODE must not be CANCELLED and DEAL_SUBTYPE must not be INDIC. The parent entity XTR_DEAL_DATE_AMOUNTS_V in turn derives from the Treasury deal header and cashflow tables, so XTR_SETTLEMENTS_V is effectively a second-level projection over the deal and transaction base tables.

Key Columns

The view exposes thirty-seven columns. Identification and timing columns include DEAL_NUMBER, TRANSACTION_NUMBER, SETTLEMENT_NUMBER, AMOUNT_DATE, ACTUAL_SETTLEMENT_DATE-derived AMOUNT_DATE, and DAY_VARIANCE, which computes the slippage between actual and expected settlement. Financial columns include CURRENCY, TYPE_OF_AMOUNT, AMOUNT, CASHFLOW_AMOUNT, HCE_AMOUNT, RATE, and CODE_COMBINATION_ID, the latter supporting General Ledger account derivation. Party and organizational columns include COMPANY, CPARTY, CLIENT, DEALER, BENEFICIARY_PARTY, LIMIT_PARTY, PORTFOLIO, PRODUCT, CONTRACT_TYPE, and SUBTYPE. Settlement instruction attributes include COMPANY_ACCOUNT, CPARTY_ACCOUNT, BENEFICIARY_ACCOUNT, DIRECT_DEBIT, CHQ_REQD, SETTLE, and CURRENCY_COMBINATION. CONTRACT_STATUS, the column most relevant to the user's search, is exposed directly from the base STATUS_CODE and indicates the lifecycle state of the parent deal — for example active, matured, or cancelled — with the CANCELLED value already excluded by the view predicate. Governance columns include AUTHORISED_BY and AUTHORISED_ON from the dual authorization fields, ACTION_CODE, ATTACHMENT_EXISTS, COMMENTS, and DIARY_NOTE_DETAILS.

Common Use Cases and Queries

  • Daily settlement worklists filtered by contract status and value date.
  • Counterparty and currency exposure extracts feeding bank payment files.
  • Reconciliation of Treasury settlements against GL cash postings using CODE_COMBINATION_ID.
  • Good-value claim and settlement slippage analysis via DAY_VARIANCE.
  • Interfaces to external treasury management or SWIFT payment systems.

Typical status-oriented query:

SELECT deal_number, transaction_number, contract_status, currency,
      cashflow_amount, amount_date, cparty, company
FROM  apps.xtr_settlements_v
WHERE  contract_status = 'ACTIVE'
AND    amount_date BETWEEN :start_date AND :end_date
ORDER BY amount_date, deal_number;

To surface open settlements awaiting authorization:

SELECT deal_number, settlement_number, contract_status, authorised_by,
      authorised_on, direct_debit, chq_reqd
FROM  apps.xtr_settlements_v
WHERE  authorised_on IS NULL
AND    contract_status <> 'CANCELLED';

Access should be granted through the XTR_USER_ACCESS package to honor Treasury row-level security, and queries should be bounded by date ranges because the view is not indexed independently of its base entity.