Results for “xtr_dealer_limits”

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

Overview

XTR_DEALER_LIMITS is a Treasury (XTR) module table in Oracle E-Business Suite 12.1.1 and 12.2.2 that stores dealer limit definitions and the monetary thresholds applied to dealers, deal types, and product types. It serves as the central control table for dealer-level exposure management, allowing treasury operations to define authorised limits, monitor utilisation, and constrain single-deal activity for each combination of dealer, deal type, and product type. The table resides in the XTR schema and holds twelve documented columns. Because the structure is dominated by foreign key relationships to three reference tables, the heuristic Data Vault classification is link. This indicates that XTR_DEALER_LIMITS functions primarily as an associative entity that resolves many-to-many relationships between dealers, deal types, and product types, while also carrying descriptive limit attributes. In EBS 12.1.1 and 12.2.2 the physical definition is consistent; the table is marked VALID in the data dictionary.

Key Information Stored

The table's business identity is defined by the unique index XTR_DEALER_LIMITS_U1 and the primary key constraint XTR_DEALER_LIMITS_UK, both spanning DEALER_CODE, DEAL_TYPE, and PRODUCT_TYPE. This composite business key ensures that only one limit record exists per dealer/deal-type/product-type combination. The most significant columns are:

• DEALER_CODE — identifies the dealer; foreign key to XTR_DEALER_CODES.
• DEAL_TYPE — classifies the type of deal; foreign key to XTR_DEAL_TYPES.
• PRODUCT_TYPE — identifies the treasury product category; foreign key to XTR_PRODUCT_TYPES.
• LIMIT_AMOUNT — the maximum authorised exposure for the dealer/deal-type/product-type combination.
• SINGLE_DEAL_LIMIT_AMOUNT — the maximum amount permitted for any individual deal.
• UTILISED_AMOUNT — the amount of the limit currently consumed.
• AUTHORISED — indicates whether the limit has been authorised for use.
• AUDIT_INDICATOR — flags the record for audit tracking.
• CREATED_BY, CREATED_ON, UPDATED_BY, UPDATED_ON — standard who-columns capturing creation and last-update audit trail information.

Note that the table has no single surrogate numeric primary key; the unique index columns themselves constitute the business key.

Common Use Cases and Queries

Typical use cases include limit monitoring, exposure reporting, and validation during deal capture. A common query retrieves limits for a specific dealer:

• SELECT dealer_code, deal_type, product_type, limit_amount, utilised_amount, authorised FROM xtr_dealer_limits WHERE dealer_code = :dealer_code;
• Comparing utilisation against authorised limits to identify breached or near-breach positions.
• Reporting on dealers with unauthorised or inactive limits before deal entry.
• Filtering single-deal limits to enforce trade-level controls.

Joins to XTR_DEALER_CODES, XTR_DEAL_TYPES, and XTR_PRODUCT_TYPES provide descriptive context for reporting. Sorting by (LIMIT_AMOUNT - UTILISED_AMOUNT) highlights remaining headroom.

Related Objects

The most significant related objects derive from the documented foreign keys:

• XTR_DEALER_CODES — joined on XTR_DEALER_LIMITS.DEALER_CODE.
• XTR_DEAL_TYPES — joined on XTR_DEALER_LIMITS.DEAL_TYPE.
• XTR_PRODUCT_TYPES — joined on DEAL_TYPE and PRODUCT_TYPE.
• XTR deals and transaction tables that validate against dealer limits during capture.
• Treasury limit-utilisation and exposure reports that read LIMIT_AMOUNT and UTILISED_AMOUNT.