Results for “xtr_mirror_dda_limit_row_v”

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

Overview

The XTR_MIRROR_DDA_LIMIT_ROW_V view is a security-filtered reporting construct within the Oracle E-Business Suite Treasury (XTR) module. Its primary role is to expose limit utilisation and deal-level credit limit data to end users while restricting visibility based on the dealer-to-company authorisation model configured in the application. Rather than presenting all rows from the underlying mirror table, the view applies a runtime predicate that limits returned records to those company codes the currently logged-in dealer is authorised to view and input against.

This view is especially relevant in 12.1.1 and 12.2.2 environments where Treasury limit monitoring, exposure reporting, and downstream integration extracts require dealer-scoped data. Because the filter is driven by FND_GLOBAL.USER_ID, the same view automatically returns different result sets depending on which user session queries it, making it suitable for Oracle Reports, OAF pages, and custom SQL used in limit dashboards or scheduled extracts.

Underlying Base Objects

The view is defined in the APPS schema and selects from XTR_MIRROR_DDA_LIMIT_ROW, which is the primary mirror table holding deal-level limit rows. The join predicate references three supporting objects:

• XTR_COMPANY_AUTHORITIES — supplies the mapping between company codes (PARTY_CODE) and dealers, along with the COMPANY_AUTHORISED_FOR_INPUT flag.
• XTR_DEALER_CODES — resolves the dealer code to a specific application user via USER_ID.
• FND_GLOBAL — the standard EBS package providing the session USER_ID used to bind the authorised dealer.

The WHERE clause correlates COMPANY_CODE to PARTY_CODE, matches DEALER_CODE across both authority and dealer tables, requires COMPANY_AUTHORISED_FOR_INPUT = 'Y', and restricts DEALER_CODE to the row whose USER_ID equals FND_GLOBAL.USER_ID. The result is a security-scoped projection of the mirror table with no data transformation beyond filtering.

Key Columns

The view exposes the full column list of the mirror table, including:

• DEAL_NUMBER, DEAL_TYPE, DEAL_SUBTYPE, TRANSACTION_NUMBER — deal identification and classification.
• LIMIT_CODE, LIMIT_TYPE, LIMIT_PARTY — the credit limit being monitored and the counterparty.
• AMOUNT, HCE_AMOUNT, UTILISED_AMOUNT, HCE_UTILISED_AMOUNT — limit amounts and utilisation, with HCE (home currency equivalent) variants.
• CURRENCY, CONTRA_CCY, CURRENCY_COMBINATION, TRANSACTION_RATE — currency and conversion attributes.
• COMPANY_CODE, DEALER_CODE, PORTFOLIO_CODE, COUNTRY_CODE — organisational and booking attributes.
• STATUS_CODE, AMOUNT_DATE, COMMENCE_DATE, DATE_LAST_SET — lifecycle and dating fields.
• CROSS_REF_TO_OTHER_PARTY, ACCOUNT_NO, AMOUNT_INDIC — supplementary reference and indicator fields.

Common Use Cases and Queries

Typical uses include dealer-scoped limit exposure reports, reconciliation extracts, and custom dashboards that must respect input authority. A representative query retrieving utilisation for the current user's authorised companies:

• SELECT deal_number, limit_code, currency, utilised_amount, hce_utilised_amount FROM xtr_mirror_dda_limit_row_v WHERE status_code = 'ACTIVE';
• SELECT company_code, SUM(hce_utilised_amount) FROM xtr_mirror_dda_limit_row_v GROUP BY company_code;
• SELECT deal_number, limit_party, amount, amount_date FROM xtr_mirror_dda_limit_row_v WHERE limit_code = :p_limit_code ORDER BY amount_date DESC;

Because authorisation is enforced within the view, queries inherit the dealer filter automatically, eliminating the need for additional row-level security in custom code.