Search Results xtr_confirmation_details




Overview
Explore in AI Chat

Overview

The XTR_CONFIRMATION_DETAILS table is a core data object within the Oracle E-Business Suite (EBS) Treasury (XTR) module, specifically for versions 12.1.1 and 12.2.2. It serves as the central repository for storing detailed information related to confirmation letters generated for treasury transactions. Confirmation letters are critical legal documents exchanged between a company and its counterparty to formally confirm the terms of a financial deal, such as a foreign exchange contract or money market transaction. The table's primary role is to maintain a definitive audit trail of confirmation actions, linking specific confirmation events to their underlying deals and transactions, thereby ensuring operational integrity and compliance within the treasury function.

Key Information Stored

The table's structure is defined by its primary key and foreign key relationships, which dictate the essential data elements it stores. The primary key is a composite of several columns: ACTION_TYPE, CLIENT_CODE, CPARTY_CODE, DEAL_NO, and TRANSACTION_NO. This design ensures a unique record for each confirmation action on a specific transaction. Key columns include DEAL_NO, which stores the unique identifier of the master treasury deal, and TRANSACTION_NO, which identifies the individual transaction (e.g., a settlement leg or rollover) within that deal. The ACTION_TYPE column categorizes the confirmation activity, while CLIENT_CODE and CPARTY_CODE identify the internal entity and the external counterparty involved, respectively. The table likely contains additional columns to store details such as confirmation generation date, status, and user identifiers.

Common Use Cases and Queries

A primary use case is tracking the confirmation lifecycle for audit and operational reporting. Treasury analysts may query the table to identify deals with pending confirmations or to generate a history of all confirmations sent for a specific counterparty. Common SQL patterns involve joining to master tables like XTR_DEALS to enrich the data with deal terms. For example, a query to list recent confirmations for a client might be:

  • SELECT d.deal_no, d.deal_type, cd.action_type, cd.cparty_code, cd.transaction_no FROM xtr_confirmation_details cd, xtr_deals d WHERE cd.deal_no = d.deal_no AND cd.client_code = '&client' ORDER BY cd.deal_no;

Another critical use case is supporting the confirmation generation and matching process within the XTR module, where this table acts as the system of record for all confirmation-related events.

Related Objects

The XTR_CONFIRMATION_DETAILS table has defined foreign key relationships with several other core Treasury tables, as documented in the ETRM metadata. These relationships are fundamental to maintaining referential integrity and enabling data navigation:

  • XTR_DEALS: Joined via DEAL_NO. This is the primary relationship, linking confirmation details to the master deal record containing all commercial terms.
  • XTR_ROLLOVER_TRANSACTIONS: Joined via the composite key of DEAL_NO and TRANSACTION_NO. This links confirmations specifically to rollover transactions within deals.
  • XTR_DEAL_CONFO_TYPES: Joined via ACTION_TYPE. This table likely provides a validation list or description for the types of confirmation actions (e.g., 'SENT', 'MATCHED', 'AMENDED') recorded in XTR_CONFIRMATION_DETAILS.