Search Results xtr_counterparty_limits




Overview
Explore in AI Chat

Overview

The XTR_COUNTERPARTY_LIMITS table is a core data object within the Oracle E-Business Suite Treasury (XTR) module for versions 12.1.1 and 12.2.2. It serves as the central repository for defining and tracking credit and risk exposure limits assigned to counterparties. The table's primary role is to enforce risk management policies by storing the authorized limit amounts and the current utilization against those limits for specific counterparties, as defined by a company within the treasury system. This data is critical for ensuring that new financial transactions do not exceed pre-established risk thresholds, thereby supporting compliance and financial control.

Key Information Stored

The table's structure is defined by its composite primary key, which uniquely identifies a limit record through the combination of COMPANY_CODE, CPARTY_CODE, and LIMIT_CODE. This design allows a single counterparty to have multiple types of limits (e.g., different products or currencies). While the specific column list is not detailed in the provided metadata, the description confirms the table holds both limit and utilization amounts. Typical columns in such a structure would include fields for the limit currency, the total approved limit value, the current utilized amount, the available balance, effective dates, and status indicators. The foreign key relationships indicate it also stores data to differentiate between direct counterparty limits and risk party limits.

Common Use Cases and Queries

The primary use case is real-time limit checking during deal entry in the XTR module. Before booking a transaction, the system queries this table to validate sufficient available limit. Common reporting and monitoring queries include identifying counterparties with high utilization percentages or breached limits. A typical SQL pattern retrieves the current limit status for analysis:

  • SELECT company_code, cparty_code, limit_code, limit_amount, utilized_amount, (limit_amount - utilized_amount) AS available_amount FROM xtr_counterparty_limits WHERE company_code = '&COMPANY';

Another critical query involves joining with the XTR_DEALS table to analyze utilization by specific deal types or to reconcile limit consumption.

Related Objects

As per the documented foreign keys, the XTR_COUNTERPARTY_LIMITS table has a direct and integral relationship with core transaction tables. The XTR_DEALS table references it twice: once for the deal's primary counterparty limit (CPARTY_CODE, LIMIT_CODE) and once for the risk party limit (RISKPARTY_CODE, RISKPARTY_LIMIT_CODE). This allows a single deal to consume limits from two different parties if applicable. The XTR_ROLLOVER_TRANSACTIONS table also references it, ensuring rollovers of existing deals continue to respect the original counterparty limits. These relationships ensure that all treasury transactions are governed by the centralized limit definitions stored in this table.