Search Results cparty_name




Overview
Explore in AI Chat

Overview

APPS.XTR_DISC_LIMIT_OVERVIEW_V is a reporting and inquiry view within the Oracle E-Business Suite Treasury (ETRM) module. It exposes a consolidated, security-filtered picture of limit utilization across counterparties, companies, and countries. The view is built on top of the base limit overview view XTR_LIMIT_OVERVIEW_V, enriching it with party names, country territory names, and counterparty full names. Its principal purpose is to present limit amounts, utilized amounts, and available balances in a form suitable for reporting, dashboards, and integration extracts. A defining characteristic is that the view applies user-level access control through XTR_COMPANY_AUTHORITIES, XTR_DEALER_CODES, and FND_GLOBAL.USER_ID, meaning the result set an end user sees is restricted to the companies that user is authorized to input for. This makes it appropriate for self-service inquiries and for any downstream report that must respect treasury authorization rules.

Underlying Base Objects

The documented base objects are FND_GLOBAL (package), FND_TERRITORIES_VL (view), XTR_COMPANY_AUTHORITIES (synonym), XTR_DEALER_CODES (synonym), XTR_LIMIT_OVERVIEW_V (view), XTR_PARTY_INFO (synonym), and XTR_USER_ACCESS (package). The view is a UNION ALL of two branches. The first branch joins XTR_LIMIT_OVERVIEW_V (alias LI) to XTR_PARTY_INFO (PA) on LI.COMPANY = PA.PARTY_CODE, to XTR_PARTY_INFO (PA1) via an outer join for the counterparty name, and to FND_TERRITORIES_VL (FT) via an outer join on country code. It further joins XTR_COMPANY_AUTHORITIES (XCA) and XTR_DEALER_CODES (XDC) to enforce that the company is authorized for input (COMPANY_AUTHORISED_FOR_INPUT = 'Y') and that the dealer code belongs to the currently logged-in user (XDC.USER_ID = FND_GLOBAL.USER_ID). The second branch handles records where LI.COMPANY = 'N/A', returning NULL for company and counterparty names while still resolving the territory name through FND_TERRITORIES_VL.

Key Columns

  • LIMIT_TYPE — Classification of the limit being reported.
  • LIMIT_PARTY — The counterparty to which the limit applies.
  • COUNTRY / TERRITORY_SHORT_NAME — Country code and its resolved territory short name.
  • LIMIT_CODE — Identifier of the limit definition.
  • COMPANY — The company (party code) owning or subject to the limit; NULL-derived logic for the 'N/A' branch.
  • FULL_NAME — Company party full name sourced from XTR_PARTY_INFO.
  • LIMIT_GROUP — Grouping attribute for limit aggregation.
  • CURRENCY — Currency in which the limit is denominated.
  • LIMIT_AMT, UTILISED, AVAILABLE — The authorized limit, amount consumed, and remaining availability.
  • EFFECTIVE_DATE — Date the limit becomes effective.
  • CPARTY_NAME — Counterparty full name from the outer-joined XTR_PARTY_INFO (PA1); this is the alias resolved by the user's search term cparty_name.

Common Use Cases and Queries

Typical usage centers on limit monitoring and authorization-aware extracts. A basic query returns all limits visible to the connected user:

  • SELECT limit_type, company, cparty_name, currency, limit_amt, utilised, available FROM apps.xtr_disc_limit_overview_v;
  • SELECT company, cparty_name, SUM(utilised) FROM apps.xtr_disc_limit_overview_v GROUP BY company, cparty_name;
  • SELECT * FROM apps.xtr_disc_limit_overview_v WHERE cparty_name = :counterparty AND available > 0;

Because the view filters on FND_GLOBAL.USER_ID, results vary by session. Reports and integrations should be aware that rows for companies not authorized for the calling user will be absent, and the 'N/A' branch will show NULL company and counterparty names by design.