Search Results xtr_mirror_dda_limit_row_u1

Overview

The table XTR.XTR_MIRROR_DDA_LIMIT_ROW is a mirror staging table within the Oracle E-Business Suite (EBS) Treasury (ETRM/ XTR) module. It captures the cashflow information for all deal transactions that currently reside in CURRENT status. Each physical row corresponds to a single deal transaction and stores the associated cashflow details, along with weighted limit utilization amounts and their reporting-currency equivalents. The object is owned by the XTR schema and resides in the APPS_TS_TX_DATA tablespace with a PCT FREE of 10. Its FND Design Data identifier is XTR.XTR_MIRROR_DDA_LIMIT_ROW, and its status is VALID across EBS 12.1.1 and 12.2.2.

From a Data Vault modeling perspective, the heuristic classification of this table is satellite-leaning. This suggests that the table most closely resembles a satellite entity attached to a business hub, carrying descriptive and measurable attributes (amounts, dates, currency, utilization) rather than serving as an independent hub or a link between hubs. The presence of a surrogate primary key alongside unique business-key columns supports this interpretation.

The table is actively maintained by database triggers. The after insert, update or delete trigger on the XTR_DEAL_DATE_AMOUNTS table inserts a not-null LIMIT_CODE into this table, calculates the weighted limit utilization amount and its reporting-currency equivalent for the deal transaction, and populates those values. The same triggers also propagate limit utilization amounts into the applicable limits tables.

Key Information Stored

The most significant columns in this table are outlined below. The documented surrogate primary key is XTR_MIRROR_DDA_LIMIT_ROW_PK, composed of DEAL_NUMBER and HCE_AMOUNT. The business-key candidate is defined by the unique index XTR_MIRROR_DDA_LIMIT_ROW_U1, covering DEAL_NUMBER, TRANSACTION_NUMBER, and DEAL_TYPE.

• DEAL_NUMBER — identifier of the deal transaction; part of both the PK and the unique business key.
• TRANSACTION_NUMBER — sequence within the deal; part of the unique business key.
• DEAL_TYPE — classification of the deal; part of the unique business key.
• DEAL_SUBTYPE — finer classification of the deal.
• HCE_AMOUNT — host currency equivalent amount; part of the primary key.
• UTILISED_AMOUNT — the limit utilization amount for the transaction.
• HCE_UTILISED_AMOUNT — reporting-currency equivalent of the utilized amount.
• LIMIT_CODE — not-null limit code populated by the trigger.
• LIMIT_PARTY — party against whom the limit is tracked; indexed by XTR_MIRROR_DDA_LIMIT_ROW_N1.
• LIMIT_TYPE — category of limit being utilized.
• AMOUNT — transaction amount; AMOUNT_DATE is indexed by XTR_MIRROR_DDA_LIMIT_ROW_N2.
• CURRENCY and CURRENCY_COMBINATION — currency code and combined base/contra quotation.
• STATUS_CODE — status indicator for the mirrored row (CURRENT for included deals).
• BANK_ACCT_USE_ID — foreign key to CE_BANK_ACCT_USES_ALL.

Common Use Cases and Queries

This table is typically used for limit utilization reporting, exposure analysis, and reconciliation of treasury deal cashflows. A common pattern retrieves utilization by limit party within a date window:

• SELECT deal_number, transaction_number, deal_type, limit_party, utilised_amount, hce_utilised_amount FROM xtr_mirror_dda_limit_row WHERE limit_party = :party AND amount_date BETWEEN :from_date AND :to_date;
• Joining to CE_BANK_ACCT_USES_ALL on bank_acct_use_id to attribute utilization to a specific bank account use.
• Aggregating HCE_UTILISED_AMOUNT by LIMIT_CODE or LIMIT_TYPE for limit consumption dashboards.
• Filtering by STATUS_CODE = 'CURRENT' to replicate the trigger-maintained population.

Data extraction for downstream warehouses frequently keys on the unique index columns (deal_number, transaction_number, deal_type) to perform idempotent merges.

Related Objects

• XTR_DEAL_DATE_AMOUNTS — source table whose DML trigger populates and maintains this mirror table.
• CE_BANK_ACCT_USES_ALL — referenced through the foreign key column BANK_ACCT_USE_ID.
• XTR_LIMITS (and related limit tables) — updated by the same triggers with utilization amounts.
• XTR_DEALS — parent deal entity providing deal_number and deal_type context.
• XTR_DEAL_TRANSACTIONS — supplies transaction_number and transaction-level detail.