Results for “xtr_exposure_transactions”

50+ results




AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

XTR_EXPOSURE_TRANSACTIONS is a Treasury module (XTR) transaction table that stores exposure transactions used for gap analysis of all Treasury cash flows. In Oracle E-Business Suite 12.1.1 and 12.2.2 it functions as the staging and analytical record of every cash-flow-relevant event — deal payments, estimates, and settlement actions — so that Treasury analysts can bucket cash inflows and outflows by currency, counterparty, value date, and exposure type. Each row represents one exposure transaction, identified by a surrogate primary key and keyed by a unique transaction number used across the Treasury deal lifecycle.

The table is owned by the XTR schema and is flagged VALID in the ETRM data dictionary. Its physical definition is broad: 76 documented columns, spanning deal, counterparty, bank account, amount, currency, and settlement attributes, plus the standard Oracle EBS 15-attribute descriptive flexfield columns. The exposed heuristic Data Vault classification places XTR_EXPOSURE_TRANSACTIONS as satellite-leaning: it carries descriptive, context-rich attributes around deal and exposure business keys rather than acting as a pure reference hub.

Key Information Stored

The primary key is the unique constraint XTR_EXPOSURE_TRANSACTIONS_PK on TRANSACTION_NUMBER, which also backs the unique index XTR_EXPOSURE_TRANSACTIONS_U1. The documented business-key candidate is therefore TRANSACTION_NUMBER, the transaction's externally meaningful identifier.

Common Use Cases and Queries

Typical Treasury reporting uses XTR_EXPOSURE_TRANSACTIONS to produce cash-flow gap analysis by currency and maturity bucket, counterparty exposure concentration reports, and settlement exception reports based on ACTION_CODE and PAYMENT_STATUS.

A simple gap-analysis aggregation looks like:

  • SELECT CURRENCY, VALUE_DATE, EXPOSURE_TYPE, SUM(AMOUNT)
  • FROM XTR.XTR_EXPOSURE_TRANSACTIONS
  • WHERE VALUE_DATE BETWEEN :p_start AND :p_end
  • GROUP BY CURRENCY, VALUE_DATE, EXPOSURE_TYPE;

Counterparty exposure is commonly reported with:

  • SELECT CPARTY_CODE, CURRENCY, SUM(AMOUNT) NET_EXPOSURE
  • FROM XTR.XTR_EXPOSURE_TRANSACTIONS
  • GROUP BY CPARTY_CODE, CURRENCY;

Because each row links to a deal via XTR_DEAL_DATE_AMOUNTS.DEAL_NUMBER, joins to that table support drill-down from aggregate exposure to individual deal flow records. Filtering on DEAL_STATUS and PAYMENT_STATUS supports open-item and settlement-exception reporting.

Related Objects

  • XTR_EXPOSURE_TYPES — parent reference for company/counterparty exposure and tax-brokerage classification; joined on COMPANY_CODE, CPARTY_CODE, EXPOSURE_TYPE, and TAX_BROKERAGE_TYPE.
  • CE_BANK_ACCT_USES_ALL — bank account uses for the company and counterparty; joined on COMPANY_ACCT_USE_ID and CPARTY_ACCT_USE_ID.
  • XTR_DEAL_DATE_AMOUNTS — child table keyed by DEAL_NUMBER, holding dated deal amount detail that references the exposure transaction.
  • XTR_EXPOSURE_TRANSACTIONS_PK / XTR_EXPOSURE_TRANSACTIONS_U1 — primary key and unique index on TRANSACTION_NUMBER.

These relationships confirm that XTR_EXPOSURE_TRANSACTIONS sits between reference master data (exposure types, bank account uses) and detailed deal flow data, serving as the central analytical transaction record for Treasury gap analysis in Oracle EBS Release 12.1.1 and 12.2.2.