Search Results xtr_settlement_summary_pk

Overview

XTR.XTR_SETTLEMENT_SUMMARY is a Treasury (XTR) module table within Oracle E-Business Suite 12.1.1 and 12.2.2. It stores all information associated with authorized settlements in the Treasury system. As a settlement summary, it functions as a consolidated record of a settlement instruction that has moved through Treasury authorization, capturing the parties involved, the bank accounts debited or credited, the settlement amount and currency, the settlement date, and the processing status. Treasury users rely on this table for cash positioning, bank account reconciliation, and downstream payment processing through Oracle Payments and Cash Management.

From a data-modeling perspective, the heuristic Data Vault classification mined from the foreign-key structure is link. This is a modeling suggestion only: the table bridges two bank account usages — company-side and counterparty-side — and records a measurable transaction event (the settlement) between them. It therefore behaves like a link table with attached descriptive attributes, rather than a pure hub (a list of unique business entities) or a satellite (descriptive history keyed to a hub). The surrogate primary key SETTLEMENT_SUMMARY_ID, enforced by XTR_SETTLEMENT_SUMMARY_PK, anchors each row.

Key Information Stored

The table exposes 19 documented columns in the 12.2.2 physical schema. The most operationally significant are:

• SETTLEMENT_SUMMARY_ID — surrogate primary key from XTR_SETTLEMENT_SUMMARY_PK; the technical row identifier, not a business key.
• SETTLEMENT_NUMBER — the business-facing settlement reference; a strong candidate business key for user-facing lookups and reconciliation.
• COMPANY — the internal Treasury company (legal entity) originating the settlement.
• CURRENCY — the settlement currency, driving amount interpretation and FX reporting.
• SETTLEMENT_AMOUNT — the monetary value of the authorized settlement.
• SETTLEMENT_DATE — the effective date used for value-dating, cash positioning, and period reporting.
• COMPANY_ACCT_NO / CPARTY_ACCT_NO — the internal and counterparty bank account numbers, presented as natural identifiers alongside the underlying account use IDs.
• COMPANY_ACCT_USE_ID and CPARTY_ACCT_USE_ID — foreign keys to CE_BANK_ACCT_USES_ALL, resolving the company-side and counterparty-side bank account usages respectively.
• CPARTY_CODE — the counterparty identifier associated with the settlement.
• NET_ID — the netting reference linking this settlement to a Treasury netting batch or settlement net.
• STATUS — the lifecycle state of the settlement record (for example, authorized, settled, or cancelled).
• EXTERNAL_SOURCE — indicates the originating system when the settlement was interfaced rather than created natively in Treasury.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard EBS audit (WHO) columns.

Common Use Cases and Queries

Typical reporting includes settlement registers by company and date, counterparty exposure summaries, and reconciliation of Treasury settlements against bank statements in Cash Management. A representative query joining both bank account usages is:

SELECT s.SETTLEMENT_NUMBER, s.COMPANY, s.CURRENCY, s.SETTLEMENT_AMOUNT, s.SETTLEMENT_DATE, s.STATUS, cba.BANK_ACCOUNT_NAME
FROM XTR.XTR_SETTLEMENT_SUMMARY s, CE.CE_BANK_ACCT_USES_ALL cba
WHERE s.COMPANY_ACCT_USE_ID = cba.ACCT_USE_ID
AND s.SETTLEMENT_DATE BETWEEN :p_from AND :p_to;

Counterparty analysis substitutes CPARTY_ACCT_USE_ID for the join and adds CPARTY_CODE to the select list. Netting reports filter on NET_ID, while interface monitoring filters on EXTERNAL_SOURCE and STATUS. Because SETTLEMENT_AMOUNT and CURRENCY are stored per row, currency conversion is normally applied at query time rather than persisted here.

Related Objects

• CE.CE_BANK_ACCT_USES_ALL — referenced twice, via XTR_SETTLEMENT_SUMMARY.COMPANY_ACCT_USE_ID and XTR_SETTLEMENT_SUMMARY.CPARTY_ACCT_USE_ID; supplies bank account, legal entity, and currency context.
• XTR_SETTLEMENT_SUMMARY_PK — the primary key constraint on SETTLEMENT_SUMMARY_ID.
• Treasury settlement and netting objects (for example, settlement batch and netting tables keyed by NET_ID) — depend on this summary for authorized settlement totals.
• Oracle Payments and Cash Management reconciliation objects — consume settlement amounts and dates for bank statement matching.

Because the documented metadata exposes only the two Cash Management foreign keys, additional relationships should be confirmed against the ETRM data model for the specific patch level in use.