Search Results xtr_disc_limit_overview_v




Overview
Explore in AI Chat

Overview

XTR_DISC_LIMIT_OVERVIEW_V is a Treasury (XTR) reporting view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It exposes credit and settlement limit amounts alongside their utilization and remaining availability across all defined limit areas, while simultaneously enforcing user-level company (counterparty/legal entity) access restrictions. The view is a security-filtered superset of XTR_LIMIT_OVERVIEW_V, meaning it presents the same limit-versus-utilization picture as the base overview but restricts the returned rows to companies that the currently logged-in user is authorized to view or input against.

Its principal role is in Treasury limit monitoring, exposure dashboards, and integration extracts where row-level access control is mandatory. Because authorization is driven by FND_GLOBAL.USER_ID, results are inherently session- and user-dependent, making the view unsuitable for unrestricted background extracts unless the user context is explicitly set.

Underlying Base Objects

The view is defined as a UNION ALL of two branches over the following documented base objects:

  • XTR_LIMIT_OVERVIEW_V (VIEW) — the core source of limit type, limit party, country, limit code, company, limit group, currency, limit amount, utilized, available, and effective date.
  • XTR_PARTY_INFO (SYNONYM) — joined on LI.COMPANY = PA.PARTY_CODE to supply the company full name (COMPANY_NAME), and again as PA1 (outer join on LI.LIMIT_PARTY) to supply the counterparty name (CPARTY_NAME).
  • FND_TERRITORIES_VL (VIEW) — outer-joined on LI.COUNTRY = FT.TERRITORY_CODE to resolve COUNTRY_NAME.
  • XTR_COMPANY_AUTHORITIES (SYNONYM) — joined on LI.COMPANY = XCA.PARTY_CODE and filtered by COMPANY_AUTHORISED_FOR_INPUT = 'Y' to enforce access.
  • XTR_DEALER_CODES (SYNONYM) — joined on XCA.DEALER_CODE = XDC.DEALER_CODE and XDC.USER_ID = FND_GLOBAL.USER_ID to tie authorization to the current user.
  • FND_GLOBAL (PACKAGE) — supplies the runtime USER_ID used in the access-control predicate.
  • XTR_USER_ACCESS (PACKAGE) — documented as referenced, supporting the Treasury access model.

The first UNION ALL branch returns authorized companies only (COMPANY <> 'N/A'), with company and counterparty names populated. The second branch returns rows where COMPANY = 'N/A', with COMPANY_NAME and CPARTY_NAME set to NULL, so that unassigned or global limit records remain visible without an authorization join.

Key Columns

  • LIMIT_TYPE / LIMIT_CODE / LIMIT_GROUP — classify the limit area and its grouping.
  • LIMIT_PARTY / CPARTY_NAME — counterparty identifier and resolved name.
  • COMPANY / COMPANY_NAME — the legal entity/company owning the limit; COMPANY_NAME is NULL for the 'N/A' branch.
  • COUNTRY / COUNTRY_NAME — territory code and its descriptive short name.
  • CURR — currency of the limit amounts.
  • LIMIT_AMOUNT — the authorized limit amount.
  • UTILIZED — amount consumed against the limit.
  • AVAILABLE — remaining headroom (limit less utilization).
  • EFFECTIVE_DATE — the date the limit becomes or became effective.

Common Use Cases and Queries

Typical scenarios include Treasury limit utilization dashboards, counterparty exposure reports, and access-controlled extracts embedded in concurrent programs. A representative query is:

  • SELECT limit_code, limit_party, cparty_name, company_name, curr, limit_amount, utilized, available FROM xtr_disc_limit_overview_v WHERE company = :p_company ORDER BY limit_code;
  • SELECT company_name, SUM(limit_amount), SUM(utilized), SUM(available) FROM xtr_disc_limit_overview_v GROUP BY company_name;
  • SELECT * FROM xtr_disc_limit_overview_v WHERE available < 0; — to isolate over-utilized limits.

Because visibility depends on FND_GLOBAL.USER_ID and XTR_COMPANY_AUTHORITIES, queries must be executed in an authenticated session with appropriate Treasury dealer-code setup to return the expected rows.