Search Results limit_group




Overview
Explore in AI Chat

Overview

XTR_LIMIT_OVERVIEW_V is an APPS-owned reporting view within the Oracle E-Business Suite Treasury (XTR) module. It consolidates limit exposure information from several distinct limit-tracking categories into a single, uniformly shaped result set. According to ETRM metadata, the view "shows a subset of columns from counterparty, sovereign, global, currency, group and settlement limits." This makes it the primary consolidated source for limit utilisation reporting across the Treasury product. Its status is VALID in both 12.1.1 and 12.2.2, and the view text is identical across the two releases.

The view is implemented as a set of UNION ALL branches, each selecting from a different underlying limit table and projecting that table's native columns into a common column list. A literal LIMIT_TYPE discriminator column identifies which branch produced each row, allowing consumers to filter or group by limit category without knowing the physical table layout.

Underlying Base Objects

The documented base objects referenced by XTR_LIMIT_OVERVIEW_V are:

The counterparty branch joins XTR_COUNTERPARTY_LIMITS to XTR_PARTIES_V on PARTY_CODE = CPARTY_CODE, excludes rows where LIMIT_CODE = 'SETTLE', and suppresses rows where both LIMIT_AMOUNT and UTILISED_AMOUNT are zero.

Key Columns

  • LIMIT_TYPE — discriminator literal identifying the limit category ('COUNTERPARTY', 'SOVEREIGN', 'GLOBAL', and so on).
  • LIMIT_PARTY — the counterparty code for counterparty limits; 'N/A' for other branches.
  • COUNTRY — uppercased country code from XTR_PARTIES_V or the country limit table; 'N/A' where not applicable.
  • LIMIT_CODE — the limit identifier; 'N/A' for sovereign limits.
  • COMPANY — the company code owning the limit.
  • LIMIT_GROUP — populated from the limit type for global limits and from group limit definitions; 'N/A' elsewhere.
  • CURRENCY — currency code for currency limits; 'N/A' for other branches.
  • LIMIT_AMT / UTILISED / AVAILABLE — the limit amount, utilised amount, and the computed difference (LIMIT_AMOUNT minus UTILISED_AMOUNT), each wrapped in NVL(...,0).
  • EFFECTIVE_DATE — populated as TRUNC(SYSDATE), reflecting the report run date.
  • ATTRIBUTE1–ATTRIBUTE15 — descriptive flexfield columns, populated only for counterparty limits and NULL for other branches.

Common Use Cases and Queries

The view is typically used for limit utilisation dashboards, exposure monitoring, and downstream feeds into risk reporting. A common query retrieves available headroom by limit type:

  • SELECT limit_type, company, limit_party, currency, limit_amt, utilised, available FROM apps.xtr_limit_overview_v WHERE available < 0 ORDER BY available;
  • SELECT limit_group, SUM(utilised) FROM apps.xtr_limit_overview_v WHERE limit_type = 'GLOBAL' GROUP BY limit_group;
  • SELECT * FROM apps.xtr_limit_overview_v WHERE limit_type = 'COUNTERPARTY' AND country = 'US';

Because ATTRIBUTE columns are only populated on the counterparty branch, queries relying on descriptive flexfield values should constrain LIMIT_TYPE = 'COUNTERPARTY'.