Results for “xtr_group_limits”

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

Overview

XTR_GROUP_LIMITS is a Treasury (XTR) module table that stores counterparty group limit definitions and their associated utilization amounts. In Oracle EBS 12.1.1 and 12.2.2, it holds the credit or exposure limits applied to a group of counterparties within a company, together with the amounts already consumed against those limits. This enables treasury users to monitor available headroom, enforce exposure ceilings, and support limit-breach reporting across the counterparty hierarchy.

The documented primary key is XTR_GROUP_LIMITS_PK, composed of COMPANY_CODE, CPARTY_CODE, and LIMIT_TYPE. This three-column composite key defines the uniqueness of a group-limit record. Under a heuristic Data Vault classification, the table resolves as a standalone object rather than a clean hub, link, or satellite: the composite business key (company, counterparty, limit type) carries descriptive attributes such as LIMIT_AMOUNT, UTILISED_AMOUNT, AUTHORISED, and EXPIRY_DATE. A dimensional modeler could treat COMPANY_CODE, CPARTY_CODE, and LIMIT_TYPE as a composite hub key, with the amount, authorization, and audit columns modeled as a satellite on that key.

Key Information Stored

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

• COMPANY_CODE — the legal entity or company context for the limit; part of the composite primary key.
• CPARTY_CODE — the counterparty or counterparty group to which the limit applies; part of the primary key.
• LIMIT_TYPE — the classification of limit being defined; completes the primary key.
• LIMIT_AMOUNT — the authorized limit amount granted for that company, counterparty, and limit type.
• UTILISED_AMOUNT — the portion of the limit already consumed, enabling available-limit computation.
• AUTHORISED — flag indicating whether the limit has been formally approved and is active.
• EXPIRY_DATE — the date on which the limit lapses and should no longer be enforced.
• AUDIT_INDICATOR — flag supporting audit or tracking behavior on the record.
• CREATED_BY, CREATED_ON — standard WHO columns recording record creation.
• UPDATED_BY, UPDATED_ON — standard WHO columns recording the last update.

The surrogate-style uniqueness is delivered by XTR_GROUP_LIMITS_PK over the three business columns; the remaining columns are attributes. No separate single-column sequence key is documented, so the composite key also functions as the business key.

Common Use Cases and Queries

Typical scenarios include limit utilization reporting, available-limit calculation, expiry monitoring, and authorization review. The central reporting pattern computes headroom as LIMIT_AMOUNT minus UTILISED_AMOUNT:

• Available limit by counterparty: select COMPANY_CODE, CPARTY_CODE, LIMIT_TYPE, LIMIT_AMOUNT, UTILISED_AMOUNT, (LIMIT_AMOUNT - UTILISED_AMOUNT) available from XTR_GROUP_LIMITS where COMPANY_CODE = :company order by CPARTY_CODE.
• Expiring limits: filter EXPIRY_DATE between SYSDATE and SYSDATE + 30 to flag upcoming lapses.
• Unauthorized exposure: select records where AUTHORISED is not set, for review before enforcement.
• Threshold alerts: query where UTILISED_AMOUNT / LIMIT_AMOUNT exceeds a tolerance to surface near-breach counterparties.

Because the table is standalone, queries join directly to counterparty, company, and limit-type reference data via the coded columns rather than through documented foreign keys.

Related Objects

As a standalone table, XTR_GROUP_LIMITS has no documented FK relationships, so association with other objects is by shared coded columns:

• Counterparty master — joined on CPARTY_CODE to resolve counterparty names and group hierarchies.
• Company/legal entity reference — joined on COMPANY_CODE to identify the owning entity.
• Limit-type lookup — joined on LIMIT_TYPE to translate limit classifications.
• Treasury limit and utilization tables — related by COMPANY_CODE, CPARTY_CODE, and LIMIT_TYPE for exposure aggregation.
• XTR audit/WHO conventions — CREATED_BY and UPDATED_BY reference the standard EBS user identifiers.

Administrators should treat the composite key columns and the AUTHORISED, LIMIT_AMOUNT, UTILISED_AMOUNT, and EXPIRY_DATE attributes as the core enforcement set when integrating this table with treasury reporting or limit-monitoring extensions.