Search Results settle_amount




Overview
Explore in AI Chat

Overview

APPS.XTR_EFT_DEBITS_V is an Oracle E-Business Suite Treasury (ETRM) reporting view that consolidates outgoing electronic funds transfer (EFT) debit settlement activity. It is layered directly over XTR_DEAL_DATE_AMOUNTS_V and projects a normalized set of settlement attributes used by Treasury's EFT payment processing and netting logic. Because the view filters on TRANS_MTS = 'Y' and SETTLE = 'Y', it exposes only those deal-date cash flows that are flagged as eligible for settlement transmission. The view's distinguishing feature is the use of NVL(BENEFICIARY_PARTY, CPARTY_CODE) to derive a consolidated SETTLE_PARTY column, and NVL(BENEFICIARY_ACCOUNT_NO, CPARTY_ACCOUNT_NO) to derive a consolidated CPARTY_ACCOUNT_NO. This beneficiary-first resolution is the reason the term beneficiary_party surfaces in searches: the view prioritizes beneficiary attributes over the counterparty (CPARTY) attributes when both are present. Within the ETRM schema, the view serves as a stable integration and reporting surface for downstream settlement selection, netting reports, and reconciliation of debit instructions.

Underlying Base Objects

The documented base objects underpinning this view are XTR_DEAL_DATE_AMOUNTS_V (VIEW) and XTR_USER_ACCESS (PACKAGE).

  • XTR_DEAL_DATE_AMOUNTS_V — the primary source. It supplies all columns referenced by the view, including CASHFLOW_AMOUNT, BENEFICIARY_ACCOUNT_NO, CPARTY_ACCOUNT_NO, BENEFICIARY_PARTY, CPARTY_CODE, NETOFF_NUMBER, NETOFF_GROUP_FLAG, TRANS_MTS, and SETTLE. All filtering and aggregation in XTR_EFT_DEBITS_V is performed against this single view.
  • XTR_USER_ACCESS — the ETRM security package that enforces row-level access by company and counterparty. Its presence in the metadata indicates that records returned through the underlying view are subject to the caller's Treasury access privileges, so results depend on the operating user's assigned company/party scope.

Because XTR_EFT_DEBITS_V is defined as a UNION ALL of two branches over the same source, all underlying dependencies pass through identically; only the WHERE predicates differ.

Key Columns

  • SETTLE_AMOUNT — the settlement amount. In the netted branch it is SUM(CASHFLOW_AMOUNT) grouped by the netting keys; in the non-netted branch it is the raw CASHFLOW_AMOUNT.
  • SPARTY_ACCOUNT_NO / CPARTY_ACCOUNT_NO — resolved as NVL(BENEFICIARY_ACCOUNT_NO, CPARTY_ACCOUNT_NO), giving beneficiary account priority over counterparty account.
  • SETTLE_PARTY — resolved as NVL(BENEFICIARY_PARTY, CPARTY_CODE), the beneficiary-first party identifier central to the "beneficiary_party" search.
  • CPARTY_CODE — the counterparty code retained alongside SETTLE_PARTY for reference.
  • NETOFF_NUMBER / NETOFF_GROUP_FLAG — netting identifiers; a non-null NETOFF_NUMBER routes the row through the grouped branch.
  • ACTUAL_SETTLEMENT_DATE, CURRENCY, COMPANY_CODE — settlement dating, currency, and owning company.
  • SETTLEMENT_ACTIONED, TRANS_MTS, SETTLE — processing status flags; TRANS_MTS and SETTLE are constrained to 'Y'.

Common Use Cases and Queries

Typical uses include EFT debit selection, netting reconciliation, and beneficiary-level reporting.

  • Listing netted debit settlements by beneficiary: SELECT SETTLE_PARTY, CPARTY_ACCOUNT_NO, CURRENCY, SUM(SETTLE_AMOUNT) FROM APPS.XTR_EFT_DEBITS_V WHERE NETOFF_NUMBER IS NOT NULL GROUP BY SETTLE_PARTY, CPARTY_ACCOUNT_NO, CURRENCY;
  • Identifying non-netted debits pending action: SELECT CPARTY_CODE, ACTUAL_SETTLEMENT_DATE, SETTLE_AMOUNT FROM APPS.XTR_EFT_DEBITS_V WHERE NETOFF_NUMBER IS NULL AND SETTLEMENT_ACTIONED IS NULL;
  • Reconciling beneficiary versus counterparty resolution: SELECT BENEFICIARY_PARTY, CPARTY_CODE, SETTLE_PARTY FROM APPS.XTR_EFT_DEBITS_V WHERE BENEFICIARY_PARTY IS NOT NULL;

Because access is governed via XTR_USER_ACCESS, queries return only the company and counterparty scope permitted to the executing user.