Results for “xtr_limit_types_v”

41 results




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

Overview

XTR_LIMIT_TYPES_V is an APPS-owned database view in the Oracle E-Business Suite Treasury (XTR) module. It exposes a focused projection of the limit type configuration maintained in Treasury, presenting the identifying key, the descriptive name, standard audit columns, and the FX investment fund type attribute. The view is registered as VALID in the EBS data dictionary on both 12.1.1 and 12.2.2 environments, and it follows the conventional EBS pattern of publishing a stable, read-oriented interface over a base table so that reports, concurrent programs, and integration extracts do not need to bind directly to the underlying storage object.

Because the view is defined with a simple column list and no filtering predicate, it returns every row present in the base table. Its primary role is therefore reporting and integration: it gives Treasury limit type reference data a named, schema-qualified access point that can be granted to read-only reporting users and referenced from BI Publisher data templates, Oracle Reports, and outbound interface queries. The presence of the FX_INVEST_FUND_TYPE column is significant — it links limit type definitions to foreign exchange investment fund categorisation, which makes the view relevant to users searching for that attribute when building FX-related limit or exposure reports.

Underlying Base Objects

The view is defined entirely over a single base object: the table XTR_LIMIT_TYPES, which the ETRM metadata records as referenced through a SYNONYM. The view text is a straight SELECT of seven columns from that table — LIMIT_TYPE, NAME, CREATED_BY, CREATED_ON, UPDATED_BY, UPDATED_ON, and FX_INVEST_FUND_TYPE — with no joins, unions, DISTINCT clauses, or WHERE conditions. Consequently, there is a one-to-one row correspondence between XTR_LIMIT_TYPES_V and XTR_LIMIT_TYPES; each row in the base table produces exactly one row in the view.

This structure means the view carries no independent storage or logic of its own. Any DML performed against the base table is immediately visible through the view, and any changes to the base table's structure would require recompilation of the view. From an administrative standpoint, XTR_LIMIT_TYPES is a Treasury reference/setup table, and the view sits above it as a curated access layer. Because the view is a simple projection, Oracle can generally resolve queries efficiently, though query plans will depend on indexes and constraints present on the base table.

Key Columns

  • LIMIT_TYPE — The primary business key of the limit type record. This is the value used throughout Treasury limit and exposure processing to identify which category of limit a record belongs to.
  • NAME — The descriptive, user-facing name of the limit type. This is the label presented in setup forms and on reports, and it is the column most often used in ordering and grouping clauses.
  • CREATED_BY, CREATED_ON — Standard EBS audit columns capturing the user and timestamp associated with the initial insert of the record.
  • UPDATED_BY, UPDATED_ON — Standard EBS audit columns capturing the most recent user and timestamp associated with modification of the record. Together with CREATED_BY and CREATED_ON, these support audit and change-tracking reporting.
  • FX_INVEST_FUND_TYPE — The attribute that classifies the limit type in terms of FX investment fund type. This is the column most directly associated with the search term "fx_invest_fund_type" and is central to reporting that distinguishes limit types by their FX investment fund classification.

Common Use Cases and Queries

The view is typically queried to populate LOVs, validate reference data, or join limit type descriptions onto transaction and limit records. The following example lists all limit types ordered by name:

SELECT limit_type, name, fx_invest_fund_type FROM apps.xtr_limit_types_v ORDER BY name;

To isolate records tied to FX investment fund types, filter on the relevant column:

SELECT limit_type, name FROM apps.xtr_limit_types_v WHERE fx_invest_fund_type IS NOT NULL ORDER BY limit_type;

A common integration pattern joins the view to Treasury limit balance or exposure tables to resolve the limit type name and FX fund classification onto transactional output. Audit-oriented queries select CREATED_BY, CREATED_ON, UPDATED_BY, and UPDATED_ON to trace when limit type setup changed. Because the view contains no filtering, any selective query should apply predicates explicitly, and consumers should be aware that all rows from XTR_LIMIT_TYPES are exposed. Reading the view rather than the base table keeps custom reporting aligned with the supported Treasury data model.