Search Results cparty_account




Overview
Explore in AI Chat

Overview

APPS.XTR_SETTLEMENTS_V is a reporting and integration view within the Oracle E-Business Suite Treasury (ETRM) module, exposing settlement-related data drawn from treasury deals and their associated cashflows. Its defining characteristic is the filter set applied in its WHERE clause, which restricts output to records that represent genuine, single-occurrence settlement obligations. Specifically, the view excludes cancelled contracts (STATUS_CODE <> 'CANCELLED'), indicative deals (DEAL_SUBTYPE <> 'INDIC'), FX buy and sell amount types ('FXOBUY', 'FXOSELL'), and any row where CASHFLOW_AMOUNT is zero. It further requires that expected settlement be flagged (EXP_SETTLE_REQD = 'Y' by default) and that the transaction not be part of a multiple-settlement arrangement (MULTIPLE_SETTLEMENTS = 'N'). The result is a clean, settlement-ready record set suitable for outward payment processing, bank file generation, and reconciliation reporting. Because it is defined over XTR_DEAL_DATE_AMOUNTS_V, it also inherits any user-access security enforced through XTR_USER_ACCESS, making it consistent with the responsibility-level data restrictions applied elsewhere in ETRM.

Underlying Base Objects

The view is defined over two documented objects:

  • XTR_DEAL_DATE_AMOUNTS_V (VIEW): the primary source, supplying deal, cashflow, counterparty, account, and date attributes. The settlement view selects a designated projection of columns from this object and applies its own filtering logic on top.
  • XTR_USER_ACCESS (PACKAGE): the access-control mechanism consulted to enforce user data privileges against the underlying date/amounts view.

No base tables are referenced directly by XTR_SETTLEMENTS_V; all derivation occurs through the intermediary view, which aligns settlement reporting with the transactional grain of deal date amounts.

Key Columns

The projection includes the following salient columns:

Common Use Cases and Queries

Typical applications include monitoring settlement delays, preparing payment instructions, and reconciling expected versus actual value dates. A representative query isolating material variances is:

  • SELECT SETTLEMENT_NUMBER, DEAL_NUMBER, CPARTY, CURRENCY, AMOUNT, AMOUNT_DATE, DAY_VARIANCE FROM APPS.XTR_SETTLEMENTS_V WHERE DAY_VARIANCE > 0 ORDER BY DAY_VARIANCE DESC;
  • SELECT COMPANY, CURRENCY, SUM(CASHFLOW_AMOUNT) FROM APPS.XTR_SETTLEMENTS_V WHERE AMOUNT_DATE = TRUNC(SYSDATE) GROUP BY COMPANY, CURRENCY;
  • SELECT DEAL_NUMBER, CPARTY, AMOUNT, GOOD_VALUE_CLAIM FROM APPS.XTR_SETTLEMENTS_V WHERE GOOD_VALUE_CLAIM IS NOT NULL;

Because DAY_VARIANCE is a computed difference between two date columns, it must be quoted directly in the outer query rather than filtered within the underlying view, which does not expose that expression for predicate pushdown.