Search Results xtr_limit_types_u1

Overview

XTR.XTR_LIMIT_TYPES is a reference (setup) table in the Oracle E-Business Suite Treasury (ETRM) module. It stores the definition of limit types that are used throughout the credit and limit management functionality. Each row in the table corresponds to exactly one limit type, and every limit type is classified into one of four investment categories: X (foreign exchange), I (investment), F (funding), and OD (overdraft). Limit types provide the mechanism by which global limits and group limits can be combined and applied across counterparties and portfolios.

The table is owned by the XTR schema, resides in the APPS_TS_TX_DATA tablespace, and is registered under FND Design Data as XTR.XTR_LIMIT_TYPES. Because there are no foreign keys originating from this table, it functions as a standalone reference or lookup entity. Applying Data Vault modeling heuristics, the table is hub-leaning: the LIMIT_TYPE column is the stable, unique business key, and the descriptive attributes (name, category, audit columns) behave as satellite-style context attached to that hub. This classification is a modeling suggestion, not a structural mandate imposed by EBS.

Key Information Stored

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

• LIMIT_TYPE — The limit type code, which is both the surrogate primary key (XTR_LIMIT_TYPES_PK) and the unique business-key candidate enforced by the unique index XTR_LIMIT_TYPES_U1. Each value ties the row to one of the four limit categories. The user search term "xtr_limit_types_u1" refers directly to this unique index.
• FX_INVEST_FUND_TYPE — The investment category indicator that classifies the limit type as F (fund), I (invest), X (foreign exchange), or OD (overdraft). This is the primary means of grouping limit types by business function.
• NAME — The descriptive limit type name (up to 20 characters) displayed in the Limit Types window.
• CREATED_BY, CREATED_ON — Standard audit columns recording the user and timestamp that created the record.
• UPDATED_BY, UPDATED_ON — Standard audit columns recording the most recent user and timestamp that modified the record.

The audit columns follow the conventional EBS WHO-column pattern and support change tracking and compliance reporting.

Common Use Cases and Queries

Because this is a low-volume setup table, it is most often queried as a lookup joined to transaction and limit tables. Typical scenarios include retrieving the full list of limit types for a given investment category, driving value sets in concurrent programs, and validating limit type assignments against company limits.

A basic listing query:

• SELECT LIMIT_TYPE, NAME, FX_INVEST_FUND_TYPE FROM XTR.XTR_LIMIT_TYPES ORDER BY FX_INVEST_FUND_TYPE, LIMIT_TYPE;

A filter by category, for example all foreign exchange limit types:

• SELECT LIMIT_TYPE, NAME FROM XTR.XTR_LIMIT_TYPES WHERE FX_INVEST_FUND_TYPE = 'X';

A reporting join resolving limit type descriptions on company limits:

• SELECT cl.LIMIT_TYPE, lt.NAME, lt.FX_INVEST_FUND_TYPE FROM XTR.XTR_COMPANY_LIMITS cl, XTR.XTR_LIMIT_TYPES lt WHERE cl.LIMIT_TYPE = lt.LIMIT_TYPE;

Common reporting uses include limit utilization analysis by category, setup validation reports, and migration extracts of limit type metadata between environments. Because LIMIT_TYPE is the unique business key, it is the natural join predicate in any lookup.

Related Objects

The metadata documents one inbound foreign key relationship and one dependent object, which define the table's integration points within ETRM:

• XTR_COMPANY_LIMITS.LIMIT_TYPE → XTR_LIMIT_TYPES.LIMIT_TYPE — The principal referencing table. Company (counterparty) limits are assigned a limit type, so this join resolves the description and category of each limit.
• XTR_LIMIT_TYPES# — The dependent object (materialized view or synonym variant) generated for the base table.

Because the table participates in the ETRM limit framework, joined reporting typically extends to company, counterparty, and group limit tables within the XTR schema, all of which use LIMIT_TYPE as the common lookup key back to XTR_LIMIT_TYPES.