Search Results xtr_rollover_transactions




Overview
Explore in AI Chat

Overview

XTR_ROLLOVER_TRANSACTIONS is a Treasury (XTR) module table in Oracle E-Business Suite 12.1.1 and 12.2.2 that stores transaction-level information for rollover deals across a range of Treasury instruments. The documented scope covers bond deals, interest rate swaps, negotiable instruments, short term money, retail term money, and wholesale term money. Because a single Treasury deal can span multiple rollover transactions, this table functions as the transactional child of the deal header, capturing the amounts, rates, accruals, taxes, and settlement attributes that apply to each individual rollover event.

Within the XTR schema, the table is a high-volume transactional object rather than a reference or setup entity. Each row carries the business context of one rollover transaction associated with a parent deal, including principal and interest movements, brokerage and tax calculations, revaluation batch references, and bank account usage identifiers. Deals with many rollovers will produce multiple rows sharing the same DEAL_NUMBER but distinguished by TRANSACTION_NUMBER. This makes the table a central repository for rollover lifecycle tracking, interest accrual, and revaluation processing.

From a dimensional modeling perspective, the FK topology suggests a satellite-leaning classification. The composite primary key (DEAL_NUMBER, TRANSACTION_NUMBER) identifies a transaction uniquely and hangs off the XTR_DEALS parent, consistent with a satellite attached to a deal hub. The presence of multiple revaluation batch IDs and account-use references reinforces this transactional, history-oriented character, though the classification is heuristic and should be validated against the business key definition during any data vault exercise.

Key Information Stored

The primary key, XTR_ROLLOVER_TRANSACTIONS_PK, is composed of DEAL_NUMBER and TRANSACTION_NUMBER. A unique index, XTR_ROLLOVER_TRANSACTIONS_U1, covers the same two columns, confirming that the composite pair is the effective business key as well as the surrogate identifier for the row.

Common Use Cases and Queries

Typical reporting scenarios include retrieving all rollover transactions for a given deal, tracing revaluation coverage, and reconciling interest accruals to the general ledger. A representative query joins the transaction to its parent deal:

SELECT t.DEAL_NUMBER, t.TRANSACTION_NUMBER, t.DEAL_TYPE,
       t.CURRENCY, t.START_DATE, t.MATURITY_DATE,
       t.INTEREST_RATE, t.BALANCE_OUT, t.STATUS_CODE
  FROM XTR.XTR_ROLLOVER_TRANSACTIONS t
 WHERE t.DEAL_NUMBER = :deal_number
 ORDER BY t.TRANSACTION_NUMBER;

To identify transactions that have undergone revaluation but may still require it, the revaluation batch columns are useful:

SELECT t.DEAL_NUMBER, t.TRANSACTION_NUMBER,
       t.FIRST_REVAL_BATCH_ID, t.LAST_REVAL_BATCH_ID
  FROM XTR.XTR_ROLLOVER_TRANSACTIONS t
 WHERE t.LAST_REVAL_BATCH_ID IS NULL
   AND t.STATUS_CODE = 'ACTIVE';

Limit exposure reporting aggregates transactions by COMPANY_CODE, CPARTY_CODE, and LIMIT_CODE to reconcile against XTR_COUNTERPARTY_LIMITS, while interest dashboards sum INTEREST and ACCUM_INTEREST by portfolio or currency. Joining the account-use columns to CE_BANK_ACCT_USES_ALL supports cash positioning and treasury bank account analysis.

Related Objects

  • XTR_DEALS — Parent header joined on DEAL_NUMBER; supplies the deal-level attributes for each transaction.
  • XTR_PARCEL_SPLITS — Joined on DEAL_NUMBER and PARCEL_SPLIT_NO for transactions created through parcel splitting.
  • XTR_COUNTERPARTY_LIMITS — Validates exposure using COMPANY_CODE, CPARTY_CODE, and LIMIT_CODE.
  • CE_BANK_ACCT_USES_ALL — Referenced by ACCUM_INT_ACCT_USE_ID, BAL_OS_ACCT_USE_ID, and PRINCIPAL_ACCT_USE_ID for bank account usage detail.
  • XTR_BATCHES — Referenced by FIRST_REVAL_BATCH_ID and LAST_REVAL_BATCH_ID for revaluation batch tracking.
  • XTR_MASTER_CURRENCIES — Joined on CURRENCY for currency attributes.
  • XTR_ACCRLS_AMORT — Child table keyed by DEAL_NO and TRANS_NO for accruals and amortization.
  • XTR_DEAL_DATE_AMOUNTS — Child by DEAL_NUMBER and TRANSACTION_NUMBER holding dated amount schedules.
  • XTR_REVALUATION_DETAILS and XTR_LIMIT_EXCESS_LOG — Dependent detail tables keyed by deal and transaction for revaluation and limit excess history.
  • XTR_CONFIRMATION_DETAILS — Confirmation record keyed by DEAL_NO and TRANSACTION_NO.