Search Results xtr_confirmation_details




Overview
Explore in AI Chat

Overview

XTR_CONFIRMATION_DETAILS is a Treasury (XTR) module table in Oracle E-Business Suite 12.1.1 and 12.2.2 that stores the confirmation letter details generated for treasury deals and their associated transactions. Confirmation letters are the formal documents exchanged between counterparties to verify the commercial terms of a deal — amounts, currencies, settlement dates, and deal types — before settlement. This table captures the lifecycle state of each confirmation, including whether it was initially printed, reprinted, checked by a party, or validated internally.

From a Data Vault modeling perspective, the mined foreign-key structure suggests this object behaves as a link table: its primary key is a composite of five foreign-key-derived columns, indicating it resolves and qualifies relationships between deals, rollover transactions, deal confirmation types, clients, and counterparties, rather than acting as a standalone hub. Practically, it is a transactional detail table keyed by deal and transaction context.

Key Information Stored

The table owner is XTR and the documented physical schema contains 27 columns in ETRM 12.2.2. The surrogate/composite primary key, enforced by the unique index XTR_CONFIRMATION_DETAILS_UK, is composed of ACTION_TYPE, CLIENT_CODE, CPARTY_CODE, DEAL_NO, and TRANSACTION_NO. These same columns are therefore also business-key candidates, since together they uniquely identify a confirmation record.

The most significant columns include:

Common Use Cases and Queries

Typical usage centers on confirmation tracking and audit. A common query retrieves all confirmations for a deal:

  • SELECT DEAL_NO, TRANSACTION_NO, CpARTY_CODE, AMOUNT, CURRENCY, STATUS_CODE FROM XTR_CONFIRMATION_DETAILS WHERE DEAL_NO = :deal_no;
  • Confirmations awaiting counterparty check: filter on PARTY_CONFO_CHECKED = 'N'.
  • Internal validation backlog: filter on CONFIRMATION_VALIDATED_ON IS NULL.
  • Reprint reporting: select records where REPRINTED_ON IS NOT NULL, grouped by REPRINT_REQUESTED_BY.
  • Deal-amended confirmations: filter on DEAL_UPDATED_YN = 'Y' to flag confirmations requiring regeneration.

Reporting use cases include confirmation-aging reports, counterparty validation dashboards, and settlement-readiness checks joining SETTLE_DATE to cash flow schedules.

Related Objects

The documented foreign keys and PK lineage tie this table to the following principal objects:

  • XTR_DEALS — joined via DEAL_NO; the parent treasury deal header.
  • XTR_ROLLOVER_TRANSACTIONS — joined via DEAL_NO and TRANSACTION_NO; ties confirmations to rollover activity.
  • XTR_DEAL_CONFO_TYPES — joined via ACTION_TYPE; supplies the confirmation/action type definitions.
  • Counterparty and client master tables referenced through CPARTY_CODE and CLIENT_CODE (Treasury counterparty setup).
  • Concurrent program output and printing processes that populate FILE_NAME / PARTY_CONFO_FILE_NAME.

These relationships make XTR_CONFIRMATION_DETAILS a central link between deal origination, counterparty confirmation, and settlement processing in Oracle Treasury.