Search Results netoff_group_flag




Overview
Explore in AI Chat

Overview

APPS.XTR_SETTLEMENT_LETTERS_V is a reporting view within the Oracle E-Business Suite Treasury (ETRM) module, available in releases 12.1.1 and 12.2.2. It presents a consolidated, ready-to-print image of settlement instructions and netting results that feed settlement letter generation. The view consolidates treasury deal cashflows into settlement amounts and attaches the banking, counterparty, and control attributes required to produce settlement letters and related payment documentation.

Its principal role is to expose a single row per settlement event, keyed by netting number, counterparty account, settlement date, and currency. This makes the view suitable as a data source for concurrent programs, BI Publisher templates, and custom reporting that must display what is due to or from a counterparty on a given settlement date. The SETTLEMENT_ACTIONED column, which is often the subject of user searches, indicates the processing state of the settlement, allowing reports to distinguish settled from outstanding items.

Underlying Base Objects

Per the documented ETRM 12.2.2 metadata, the view is owned by APPS and is defined over two referenced objects:

  • XTR_DEAL_DATE_AMOUNTS_V (VIEW) — the primary source of cashflow amounts, dates, counterparty details, and settlement flags. All columns projected by XTR_SETTLEMENT_LETTERS_V originate from this view.
  • XTR_USER_ACCESS (PACKAGE) — referenced for access control, ensuring that only the records a user is authorized to see are returned.

The definition is a UNION ALL of two branches over XTR_DEAL_DATE_AMOUNTS_V. The first branch selects records where NETOFF_NUMBER IS NOT NULL and SETTLE = 'Y', aggregating cashflow amounts by counterparty account, account number, settlement date, netting number, netting group flag, currency, company code, settlement actioned, transaction MTS, settlement party, counterparty code, direct debit, and cheque-required flag, with a HAVING clause that excludes zero-value settlements. The second branch selects non-netted records where NETOFF_NUMBER IS NULL, CASHFLOW_AMOUNT <> 0, and SETTLE = 'Y', returning each cashflow as an individual settlement line.

Key Columns

  • SETTLE_AMOUNT — the settlement value, either the SUM of grouped cashflows (netted branch) or the individual cashflow amount (non-netted branch).
  • CPARTY_ACCOUNT_NO / ACCOUNT_NO — the beneficiary or counterparty bank account and the internal account used for the settlement.
  • ACTUAL_SETTLEMENT_DATE — derived as NVL(ACTUAL_SETTLEMENT_DATE, AMOUNT_DATE), supplying the effective value date.
  • NETOFF_NUMBER / NETOFF_GROUP_FLAG — identify whether and how the item was netted, distinguishing aggregated netting groups from standalone payments.
  • CURRENCY, COMPANY_CODE, TRANS_MTS — currency and legal-entity context, plus the transaction identifier.
  • SETTLEMENT_ACTIONED — the processing indicator showing whether the settlement has been actioned.
  • SETTLE_PARTY / CPARTY_CODE — the party receiving or making the settlement.
  • DIRECT_DEBIT / CHQ_REQD — payment-method flags controlling whether the item is collected by direct debit or requires a cheque.

Common Use Cases and Queries

Typical uses include generating settlement letters, reconciling netting output, and monitoring outstanding vs. actioned settlements. A representative query filtering by processing state:

SELECT settle_party, cparty_account_no, currency,
       settle_amount, actual_settlement_date, settlement_actioned
FROM   apps.xtr_settlement_letters_v
WHERE  settlement_actioned = 'N'
AND    actual_settlement_date >= SYSDATE
ORDER BY actual_settlement_date, settle_party;

Netting groups can be inspected by constraining on NETOFF_NUMBER, while cheque and direct-debit requirements are isolated using CHQ_REQD and DIRECT_DEBIT. Because the view applies user-access restrictions through XTR_USER_ACCESS, reports inherit standard ETRM security without additional predicates.