Search Results xtr_eft_debits_v




Overview
Explore in AI Chat

Overview

XTR_EFT_DEBITS_V is an Oracle E-Business Suite database view owned by the APPS schema and delivered as part of the XTR (Treasury) product module. It exposes debit-side cash flow data that has been marked for settlement, presenting a consolidated, EFT-ready picture of outgoing payment obligations. The view is a reporting and integration artifact rather than a transactional entity; no DML is performed against it, and its content is derived entirely at query time from underlying settlement and netting data.

Its principal role is to feed electronic funds transfer (EFT) processing, bank file generation, and treasury settlement reconciliation. By restricting output to records where the settlement indicator and the multi-currency transfer flag are both affirmative, and by filtering out non-positive amounts, the view isolates obligations that will actually be disbursed. In Oracle EBS 12.1.1 and 12.2.2, the view is commonly accessed by custom reports, concurrent programs, and outbound interfaces that require a normalized, one-row-per-settlement-line projection of debit activity.

Underlying Base Objects

The documented referenced base objects are XTR_DEAL_DATE_AMOUNTS_V (the driving view) and XTR_USER_ACCESS (package).

XTR_DEAL_DATE_AMOUNTS_V supplies all transactional columns—cash flow amount, counterparty details, account information, settlement date, netting identifiers, currency, and company code. XTR_EFT_DEBITS_V applies further logic on top of that source, including a predicate requiring NETOFF_NUMBER to be populated and TRANS_MT = 'Y' together with SETTLE = 'Y'. The reference to XTR_USER_ACCESS reflects the treasury security model that governs visibility of settlement data by user and organization.

Structurally, the view is a UNION ALL of two branches. The first branch aggregates cash flows by beneficiary account, account number, actual settlement date, netting number, netting group flag, currency, company code, settlement status, transfer flag, and settlement party, retaining only groups whose summed cash flow is positive. The second branch handles cash flows where no netting number exists, returning individual positive cash flow rows. The result is a single result set in which netted and non-netted debit obligations coexist.

Key Columns

  • SETTLE_AMOUNT — In the aggregated branch, the sum of CASHFLOW_AMOUNT for the netting group; in the non-netted branch, the individual cash flow amount. Represents the debit value to be settled.
  • CPARTY_ACCOUNT_NO — The counterparty bank account, resolved as NVL(BENEFICIARY_ACCOUNT_NO, CPARTY_ACCOUNT_NO).
  • ACCOUNT_NO — The internal company or bank account associated with the cash flow.
  • ACTUAL_SETTLEMENT_DATE — The date on which settlement is to occur; the primary date key for EFT file sequencing.
  • NETOFF_NUMBER — Identifier of the netting agreement or netting run; NULL for non-netted entries.
  • NETOFF_GROUP_FLAG — Indicates whether the row belongs to a netting group.
  • CURRENCY — Currency of the settlement amount.
  • COMPANY_CODE — The legal entity or treasury company owning the obligation.
  • SETTLEMENT_ACTIONED — Status flag indicating whether settlement processing has been triggered.
  • TRANS_MTS — Transfer flag; the view requires 'Y'.
  • SETTLE_PARTY — The settlement party, resolved as NVL(BENEFICIARY_PARTY, CPARTY_CODE).
  • CPARTY_CODE — Counterparty identifier retained alongside the resolved settlement party.

Common Use Cases and Queries

Typical scenarios include producing settlement reports by value date, generating bank EFT debit files, reconciling netted versus non-netted obligations, and aggregating debits by counterparty or company code.

  • List all pending debits for a settlement date:
    SELECT SETTLE_PARTY, CPARTY_ACCOUNT_NO, CURRENCY, SETTLE_AMOUNT, NETOFF_NUMBER FROM APPS.XTR_EFT_DEBITS_V WHERE ACTUAL_SETTLEMENT_DATE = :p_date;
  • Total debits by currency and company:
    SELECT COMPANY_CODE, CURRENCY, SUM(SETTLE_AMOUNT) FROM APPS.XTR_EFT_DEBITS_V GROUP BY COMPANY_CODE, CURRENCY;
  • Separate netted from non-netted obligations:
    SELECT NETOFF_GROUP_FLAG, COUNT(*), SUM(SETTLE_AMOUNT) FROM APPS.XTR_EFT_DEBITS_V GROUP BY NETOFF_GROUP_FLAG;
  • Filter to a specific counterparty for a bank instruction:
    SELECT * FROM APPS.XTR_EFT_DEBITS_V WHERE CPARTY_CODE = :p_cparty;

Because the view performs aggregation, always apply date and party predicates to limit result sets in production queries.