Search Results xtr_rollover_transactions_u1

Overview

XTR.XTR_ROLLOVER_TRANSACTIONS is a core transaction-level table in the Oracle E-Business Suite Treasury (ETRM) module, owned by the XTR schema and registered under FND Design Data as XTR.XTR_ROLLOVER_TRANSACTIONS. It stores general information about individual transactions that make up deals across the following instrument families: bonds, interest rate swaps, negotiable instruments, short term money, retail term money, and wholesale term money. Because each deal may be composed of one or more transactions, this table captures the granular, row-per-transaction detail beneath the deal header level.

Physically, the table resides in the APPS_TS_TX_DATA tablespace with PCT Free 10, and is indexed in APPS_TS_TX_IDX. The primary key XTR_ROLLOVER_TRANSACTIONS_PK is defined on (DEAL_NUMBER, TRANSACTION_NUMBER), enforced by the unique index XTR_ROLLOVER_TRANSACTIONS_U1. From a heuristic Data Vault modeling perspective, this object is classified as satellite-leaning, meaning it behaves primarily as a descriptive, keyed satellite attached to deal and counterparty hubs rather than as an independent hub or a pure link.

Key Information Stored

The table exposes 146 documented columns. The most operationally significant include:

• DEAL_NUMBER and TRANSACTION_NUMBER — the composite business/primary key identifying each transaction and its parent deal; only DEAL_NUMBER, TRANSACTION_NUMBER, and DEAL_TYPE are mandatory.
• DEAL_TYPE, DEAL_SUBTYPE, and PRODUCT_TYPE — classify the instrument (bond, swap, negotiable instrument, term money, etc.).
• COMPANY_CODE and CPARTY_CODE — identify the owning company and counterparty.
• DEAL_DATE, START_DATE, and MATURITY_DATE — drive cash flow and accrual timing.
• CURRENCY and CURRENCY_EXCHANGE_RATE — support multi-currency valuation and HCE reporting columns.
• INTEREST_RATE, INTEREST, INTEREST_FREQ, YEAR_BASIS, and YEAR_CALC_TYPE — define interest accrual mechanics.
• BROKERAGE_CODE, BROKERAGE_AMOUNT, BROKERAGE_RATE — capture brokerage/fee data.
• STATUS_CODE, ACTION_STATUS, and TRANS_CLOSEOUT_NO — track lifecycle state.
• PRINCIPAL_ACCT_USE_ID, ACCUM_INT_ACCT_USE_ID, and BAL_OS_ACCT_USE_ID — link to bank account uses.
• FIRST_REVAL_BATCH_ID and LAST_REVAL_BATCH_ID — tie transactions to revaluation batches.

Non-unique indexes support common access paths: _N2 (DEAL_LINKING_CODE), _N4 (START_DATE, COMPANY_CODE, CPARTY_CODE), _N5 (STATUS_CODE), _N7 (TRANS_CLOSEOUT_NO), _N8 (DEAL_TYPE, MATURITY_DATE), and _N9 (DEAL_NUMBER, STATUS_CODE, CPARTY_CODE, MATURITY_DATE).

Common Use Cases and Queries

Typical reporting scenarios include maturity ladders, exposure by counterparty, and interest accrual schedules.

• Open transactions by maturity: SELECT deal_number, transaction_number, cparty_code, maturity_date FROM xtr_rollover_transactions WHERE status_code = 'ACTIVE' ORDER BY maturity_date;
• Deal roll-up: join to XTR_DEALS on DEAL_NUMBER to aggregate principal across transactions.
• Revaluation reporting: filter by LAST_REVAL_BATCH_ID to trace which transactions fell into a given XTR_BATCHES run.

Related Objects

Foreign keys and reverse dependencies identify the most significant related objects:

• XTR_DEALS — joined on DEAL_NUMBER (parent deal header).
• CE_BANK_ACCT_USES_ALL — referenced via PRINCIPAL_ACCT_USE_ID, ACCUM_INT_ACCT_USE_ID, and BAL_OS_ACCT_USE_ID.
• XTR_MASTER_CURRENCIES — joined on CURRENCY.
• XTR_BATCHES — referenced via FIRST_REVAL_BATCH_ID and LAST_REVAL_BATCH_ID.
• XTR_PARCEL_SPLITS — linked on DEAL_NUMBER.
• Child tables referencing this table: XTR_ACCRLS_AMORT, XTR_CONFIRMATION_DETAILS, XTR_DEAL_DATE_AMOUNTS, XTR_LIMIT_EXCESS_LOG, and XTR_REVALUATION_DETAILS (all via their DEAL_NO/DEAL_NUMBER columns).