Results for “limit_amount”

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

Overview

XTR.XTR_COUNTRY_COMPANY_LIMITS is a Treasury (XTR) module table that stores sovereign limit information for legal entities operating within Oracle E-Business Suite 12.1.1 and 12.2.2. Each row defines an exposure limit assigned to a specific company (legal entity) against a specific country, together with the amount authorized and the amount utilized to date. This construct supports country-risk and sovereign-exposure management, allowing treasury users to monitor counterparty exposure by jurisdiction and to enforce concentration ceilings at the entity level.

The table resides in the XTR schema and is documented in ETRM with a status of VALID. Its structure is defined by a composite primary key, XTR_COUNTRY_COMPANY_LIMITS_PK, built on (COMPANY_CODE, COUNTRY_CODE). A corresponding unique index, XTR_COUNTRY_COMP_LIMITS_U1, enforces the same business-key combination, guaranteeing that only one limit record exists per company-country pair. Ten columns are documented in the 12.2.2 physical schema. Based on the foreign-key profile—this table references FND_TERRITORIES and is not itself referenced as a hub of dependent children—the heuristic Data Vault classification is satellite-leaning; that is, the object behaves more like a descriptive attribute set attached to an entity key than an independent hub or a pure link table.

Key Information Stored

The most significant columns fall into three groups: keys, limit measures, and audit attributes.

• COMPANY_CODE — Identifies the legal entity or company to which the sovereign limit applies. It is part of both the primary key and the business-key unique index.
• COUNTRY_CODE — The territory against which exposure is limited; this column is the foreign key to FND_TERRITORIES and the second component of the composite key.
• LIMIT_AMOUNT — The authorized sovereign exposure ceiling for the company-country combination.
• UTILISED_AMOUNT — The amount of the limit already consumed, enabling utilization-versus-limit analysis.
• AUTHORISED — A status flag indicating whether the limit record has been approved or is active.
• AUDIT_INDICATOR — A control flag used for audit tracking of changes to the limit
• CREATED_BY, CREATED_ON, UPDATED_BY, UPDATED_ON — Standard WHO-column audit trail capturing who created or last modified the record and when.

The composite primary key (COMPANY_CODE, COUNTRY_CODE) is the surrogate identifier in the sense that it uniquely addresses each row; the unique index XTR_COUNTRY_COMP_LIMITS_U1 independently confirms these two columns as the business-key candidate.

Common Use Cases and Queries

Typical usage centers on sovereign exposure reporting, limit-breach monitoring, and reconciliations that map internal company codes to recognized territories.

• Available headroom: SELECT company_code, country_code, limit_amount, utilised_amount, (limit_amount - utilised_amount) available FROM xtr.xtr_country_company_limits WHERE authorised = 'Y';
• Territory enrichment: join to FND_TERRITORIES on COUNTRY_CODE to obtain territory names for reporting.
• Utilization percentage: compute utilised_amount / limit_amount to identify near-breach positions for escalation.
• Audit delta analysis: compare UPDATED_ON and UPDATED_BY to track limit revisions over time.

Related Objects

Because the FK metadata identifies only one outbound reference, the related-object set is led by the territory table, supplemented by the standard treasury/foundation objects commonly joined at implementation.

• FND_TERRITORIES — joined via XTR_COUNTRY_COMPANY_LIMITS.COUNTRY_CODE = FND_TERRITORIES.TERRITORY_CODE; the only documented foreign-key target.
• XTR_COUNTRY_COMPANY_LIMITS_PK / XTR_COUNTRY_COMP_LIMITS_U1 — the primary key constraint and unique business-key index enforcing uniqueness.
• Company/legal-entity definition (for example, HR or FND-based organization tables linked through COMPANY_CODE) — resolves the entity behind the company code.
• Treasury deal and exposure tables in the XTR schema — used to reconcile utilized amounts against actual booked exposure.
• Standard audit/WHO views built over the XTR schema for audit and reconciliation reporting.

Together these objects allow the sovereign limits table to serve as the reference point for country-risk control within Oracle Treasury.