Search Results xtr_company_limits




Overview
Explore in AI Chat

Overview

XTR_COMPANY_LIMITS is a Treasury (XTR) module table in Oracle E-Business Suite 12.1.1 and 12.2.2 that stores company limit definitions and their associated limit and utilization amounts. It is the operational record of authorized exposure thresholds assigned to legal entities or counterparty companies, together with the amounts already consumed against those thresholds. In ETRM functional terms, the table supports limit monitoring, exposure tracking, and authorization workflows used by treasury and risk personnel.

The table resides in the XTR schema and is documented as VALID in the ETRM data dictionary. Its primary key, XTR_COMPANY_LIMITS_PK, is composed of COMPANY_CODE and LIMIT_CODE, meaning a given company may hold many distinct limit records while each individual limit is uniquely identified by the combination of both columns. A second unique index, XTR_COMPANY_LIMITS_U1, enforces uniqueness on (LIMIT_CODE, COMPANY_CODE). Based on the foreign key structure and the presence of descriptive, amount, and audit columns, the heuristic Data Vault classification is satellite-leaning; the business key components COMPANY_CODE and LIMIT_CODE behave as hub keys, with LIMIT_AMOUNT, UTILISED_AMOUNT, and descriptive attributes functioning as satellite payload.

Key Information Stored

The table contains 28 documented columns. The most significant are:

  • COMPANY_CODE — identifies the company or legal entity to which the limit applies; part of the composite primary key and of the unique index.
  • LIMIT_CODE — identifies the specific limit record; second component of the composite primary key and the leading column of XTR_COMPANY_LIMITS_U1.
  • LIMIT_TYPE — classifies the limit; foreign key to XTR_LIMIT_TYPES.
  • LIMIT_AMOUNT — the authorized ceiling for the limit.
  • UTILISED_AMOUNT — the amount already consumed against the limit, enabling utilization and headroom calculations.
  • AUTHORISED — authorization status indicator for the limit record.
  • NAME — descriptive label for the limit.
  • AUDIT_INDICATOR — flags the record for audit attention.
  • CREATED_BY, CREATED_ON, UPDATED_BY, UPDATED_ON — standard WHO audit columns tracking creation and last modification.
  • ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15 — the standard Oracle EBS descriptive flexfield (DFF) columns, available for customer-specific extension without schema change.

The surrogate primary key is XTR_COMPANY_LIMITS_PK (COMPANY_CODE, LIMIT_CODE), while XTR_COMPANY_LIMITS_U1 (LIMIT_CODE, COMPANY_CODE) provides the business-key uniqueness constraint on the same columns in reverse order.

Common Use Cases and Queries

Typical reporting scenarios include limit utilization, headroom analysis, and counterparty exposure monitoring. A common pattern joins the limit table to its type definition:

  • Limit utilization: SELECT company_code, limit_code, limit_amount, utilised_amount, (limit_amount - utilised_amount) headroom FROM xtr_company_limits WHERE authorised = 'Y';
  • Utilization ratio: SELECT company_code, limit_code, ROUND(utilised_amount / NULLIF(limit_amount,0) * 100, 2) pct_used FROM xtr_company_limits;
  • Limit type enrichment: SELECT c.company_code, c.limit_code, t.limit_type, c.limit_amount, c.utilised_amount FROM xtr_company_limits c, xtr_limit_types t WHERE c.limit_type = t.limit_type;
  • Audit review: SELECT * FROM xtr_company_limits WHERE audit_indicator = 'Y' ORDER BY updated_on DESC;

These queries underpin risk dashboards, period-end treasury reporting, and exception reports for limits nearing or exceeding authorized values.

Related Objects

  • XTR_LIMIT_TYPES — referenced by XTR_COMPANY_LIMITS.LIMIT_TYPE; provides the classification and definition of each limit category.
  • XTR_COMPANY_LIMITS_PK / XTR_COMPANY_LIMITS_U1 — primary and unique indexes enforcing record identity and business-key uniqueness on COMPANY_CODE and LIMIT_CODE.
  • XTR_COMPANIES / XTR_COMPANY relationships — the COMPANY_CODE column logically associates limits with company master records used across treasury transactions.
  • Treasury transaction and exposure tables in XTR — consume limit and utilization data to evaluate exposure against authorized thresholds.
  • ATTRIBUTE flexible field infrastructure — the ATTRIBUTE_CATEGORY and ATTRIBUTE1–15 columns integrate with the Oracle EBS DFF framework for client-specific extensions.