Results for “xtr_mirror_dda_lim_row_tmp”

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

Overview

XTR_MIRROR_DDA_LIM_ROW_TMP is a Treasury (XTR) module table owned by the XTR schema in Oracle E-Business Suite, present in both 12.1.1 and 12.2.2 releases. The ETRM metadata records its creation date as 17-JUL-96, identifying it as one of the original objects delivered with the Treasury product foundation. The table functions as a transient staging structure used by Treasury's limit and exposure processing — specifically the mirroring of demand deposit account (DDA) limit rows used in credit limit utilisation and bank account exposure calculations.

Consistent with the "_TMP" suffix, the object is designed as a short-lived working table. Rows are populated during limit-check and exposure-mirroring programs, consumed by Treasury limit engine logic, then purged or re-inserted on subsequent processing cycles. It is not intended to hold permanent ledger data, and standard Treasury reports do not query it directly.

Applying Data Vault classification heuristics to the documented foreign key structure — a single outbound reference to CE_BANK_ACCT_USES_ALL and no inbound child references — the table is best modelled as satellite-leaning. It carries descriptive and measurable attributes (amounts, limit codes, currency detail) keyed to an upstream bank account use, rather than acting as a hub of business entities or a link resolving many-to-many relationships.

Key Information Stored

The table exposes 28 documented columns in the 12.2.2 physical schema. The most operationally significant are:

• BANK_ACCT_USE_ID — the sole documented foreign key, joining to CE_BANK_ACCT_USES_ALL; it anchors each mirrored row to a specific bank account use.
• LIMIT_CODE, LIMIT_PARTY, LIMIT_TYPE — identify the credit limit line and the counterparty against which exposure is measured.
• DEAL_NUMBER, DEAL_TYPE, DEAL_SUBTYPE, TRANSACTION_NUMBER — Treasury deal and transaction identifiers contributing to limit utilisation.
• AMOUNT, AMOUNT_DATE, AMOUNT_INDIC, UTILISED_AMOUNT, HCE_AMOUNT, HCE_UTILISED_AMOUNT — the core monetary measures, including Host Country Exposure (HCE) variants.
• CURRENCY, CONTRA_CCY, CURRENCY_COMBINATION — currency context for amount interpretation.
• COMMENCE_DATE, STATUS_CODE, PORTFOLIO_CODE, PRODUCT_TYPE, COMPANY_CODE — effective-dating and classification attributes.

The metadata does not document a surrogate primary key or unique index for this table, which is consistent with its temporary nature; in temporary working tables row identity is typically positional rather than constrained.

Common Use Cases and Queries

Because the table is a processing artefact, usage is predominantly diagnostic and reconciliation-oriented rather than analytical:

• Verifying that limit-mirroring concurrent programs completed and produced expected row counts for a given bank account use.
• Comparing mirrored amounts against the live limit source during exposure reconciliation.
• Debugging discrepancies in credit limit utilisation or HCE reporting.

Representative query patterns include:

SELECT limit_code, currency, SUM(utilised_amount) FROM xtr_mirror_dda_lim_row_tmp GROUP BY limit_code, currency;

SELECT t.* FROM xtr_mirror_dda_lim_row_tmp t, ce_bank_acct_uses_all c WHERE t.bank_acct_use_id = c.bank_acct_use_id AND c.bank_account_id = :p_account_id;

Related Objects

The principal documented relationship is to CE_BANK_ACCT_USES_ALL, joined on BANK_ACCT_USE_ID. Beyond this, the table participates in the wider Treasury limit ecosystem alongside limit definition, deal, and transaction tables referenced through LIMIT_CODE, DEAL_NUMBER, and TRANSACTION_NUMBER. As a temporary staging object it has no dependent child tables or inbound foreign keys, and no public APIs are documented against it. Any query should treat data as volatile and unsuitable for persistent reporting without an accompanying snapshot mechanism.