Results for “contra_ccy”

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

Overview

XTR_MIRROR_DDA_LIM_ROW_TMP_V is a Treasury (XTR) view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It functions as a reporting and integration surface for temporary mirror rows that represent deal and limit utilisation data within the Treasury module. The view is defined over XTR_MIRROR_DDA_LIM_ROW_TMP, a temporary staging object used to hold limit-related deal rows before they are processed, reconciled, or posted to their permanent destinations. The "_V" suffix confirms that this is a view rather than a table, and its primary purpose is to expose the staging contents in a stable, queryable form without forcing consumers to reference the underlying synonym directly.

In the context of the search term "date_last_set", this view is significant because it explicitly exposes the DATE_LAST_SET column, which records the timestamp at which a given staging row was last populated or refreshed. That makes the view a natural target for auditing, freshness checks, and incremental extraction, which is why it surfaces in searches for that column name.

Underlying Base Objects

The documented metadata lists a single referenced base object: XTR_MIRROR_DDA_LIM_ROW_TMP, accessed through a synonym. Because the base object name carries the "_TMP" suffix, it is treated as a transient holding structure rather than a transactional master. Rows are typically inserted by Treasury processing programs, such as deal mirroring or limit utilisation routines, and are subsequently consumed or purged.

The view performs a simple projection: it selects a defined set of columns from the base object without joins, aggregation, or filtering in the documented view text. As a result, row counts and cardinality in the view match those of the underlying synonym at query time. This one-to-one relationship means the view adds naming stability and access control but no transformation logic, so any volatility in the base object is reflected immediately in the view.

Key Columns

The view exposes a broad set of deal, limit, and currency attributes. The most commonly referenced columns include:

• DATE_LAST_SET — the timestamp of the last update to the staging row; central to freshness and incremental-load logic.
• DEAL_NUMBER, DEAL_TYPE, DEAL_SUBTYPE, TRANSACTION_NUMBER — deal identification and classification attributes.
• LIMIT_CODE, LIMIT_PARTY, LIMIT_TYPE — limit definition and counterparty context.
• AMOUNT, HCE_AMOUNT, UTILISED_AMOUNT, HCE_UTILISED_AMOUNT — nominal and highly capital exposed (HCE) amounts, both gross and utilised.
• AMOUNT_DATE, COMMENCE_DATE — effective and commencement dates for the underlying exposure.
• CURRENCY, CONTRA_CCY, CURRENCY_COMBINATION, TRANSACTION_RATE — currency and rate information.
• COMPANY_CODE, COUNTRY_CODE, PORTFOLIO_CODE, DEALER_CODE, ACCOUNT_NO — organisational and account dimensions.
• STATUS_CODE, AMOUNT_INDIC, CROSS_REF_TO_OTHER_PARTY, PRODUCT_TYPE — status, indicator, cross-reference, and product attributes.

Together these columns support limit checking, exposure aggregation, and deal-level reconciliation.

Common Use Cases and Queries

Typical uses include verifying which staging rows have been refreshed most recently, extracting rows for downstream limit reporting, and reconciling mirrored Treasury deals against permanent limit tables. A simple freshness query uses DATE_LAST_SET directly:

• SELECT DEAL_NUMBER, LIMIT_CODE, AMOUNT, DATE_LAST_SET FROM APPS.XTR_MIRROR_DDA_LIM_ROW_TMP_V WHERE DATE_LAST_SET >= SYSDATE - 1;
• SELECT LIMIT_PARTY, SUM(UTILISED_AMOUNT) FROM APPS.XTR_MIRROR_DDA_LIM_ROW_TMP_V GROUP BY LIMIT_PARTY;

Because the view is a thin projection, queries should account for the transient nature of the base staging data and avoid relying on historical persistence.