Search Results exp_settle_reqd




Overview
Explore in AI Chat

Overview

XTR_R_DEAL_DATE_AMOUNTS_V is a reporting view owned by the APPS schema in the Oracle E-Business Suite Treasury (XTR) module. It presents date-based deal amount and settlement information drawn from the underlying Treasury deal date amount table. The view is documented as VALID in ETRM 12.1.1 and 12.2.2 and is primarily consumed by Treasury reporting, settlement processing, and integration logic that needs to interrogate deal amounts by transaction date, amount type, and settlement status.

The view text exposes a broad column list covering deal identification (DEAL_NUMBER, TRANSACTION_NUMBER, DEAL_TYPE, DEAL_SUBTYPE), monetary values (AMOUNT, HCE_AMOUNT, CASHFLOW_AMOUNT, TRANSACTION_RATE), settlement attributes (SETTLE, SETTLEMENT_NUMBER, SETTLEMENT_PARTY, ACTUAL_SETTLEMENT_DATE), and control flags. Among these, EXP_SETTLE_REQD is the column most relevant to the user's search term "exp_settle_reqd". It indicates whether expected settlement is required for the transaction record, and is one of several settlement-related indicators alongside CHQ_REQD, DIRECT_DEBIT, and MULTIPLE_SETTLEMENTS.

Underlying Base Objects

The view is defined over a single referenced object, XTR_R_DEAL_DATE_AMOUNTS, accessed through a synonym. The view text is a direct projection: it selects a defined column list FROM XTR_R_DEAL_DATE_AMOUNTS. No joins, unions, or aggregations are present in the documented view text, meaning the view functions as a stable, read-only column interface over the base deal date amount entity.

Because the definition is a straight projection, the row cardinality of XTR_R_DEAL_DATE_AMOUNTS_V matches that of XTR_R_DEAL_DATE_AMOUNTS exactly. Filtering, ordering, and aggregation must be applied by the calling report or interface. This design is common in ETRM, where underscore _V report views provide a controlled column surface while protecting direct table access.

Key Columns

Common Use Cases and Queries

Typical uses include settlement exception reporting, expected-settlement identification, cashflow and exposure reporting by date type, and Treasury-to-General-Ledger reconciliation. A query isolating records requiring expected settlement is:

  • SELECT DEAL_NUMBER, TRANSACTION_NUMBER, DEAL_TYPE, CURRENCY, AMOUNT, ACTUAL_SETTLEMENT_DATE FROM XTR_R_DEAL_DATE_AMOUNTS_V WHERE EXP_SETTLE_REQD = 'Y' AND SETTLE = 'N';
  • SELECT DATE_TYPE, CURRENCY, SUM(AMOUNT), SUM(HCE_AMOUNT) FROM XTR_R_DEAL_DATE_AMOUNTS_V WHERE TRANSACTION_DATE BETWEEN :p_from AND :p_to GROUP BY DATE_TYPE, CURRENCY;
  • SELECT DEAL_NUMBER, SETTLEMENT_NUMBER, SETTLEMENT_PARTY, SETTLEMENT_ACTIONED FROM XTR_R_DEAL_DATE_AMOUNTS_V WHERE SETTLEMENT_ACTIONED IS NULL ORDER BY TRANSACTION_DATE;

Because the view exposes no filters, always constrain queries by DEAL_TYPE, TRANSACTION_DATE, or company and portfolio columns to avoid full scans on high-volume Treasury data.