Search Results mtl_default_sets_view




Overview

MTL_DEFAULT_SETS_VIEW is an APPS-owned database view in the Oracle E-Business Suite Inventory (INV) module. It is documented as VALID in both Oracle EBS 12.1.1 and 12.2.2. The view exists specifically to work around the 240-character limit imposed by Oracle Reports-based concurrent programs (referred to in the metadata as "SRS's 240 char limit") when defaulting category sets. Because the standard defaulting logic must resolve localized category set names and descriptions — potentially lengthy multilingual strings — packaging that resolution into a view allows concurrent programs and report parameters to reference a single, compact object rather than embedding an oversized SQL statement directly in the report definition.

Functionally, the view presents the set of category sets that have been designated as defaults for a given functional area. It joins the base category set definition, its translation table (restricted to the session's language), and the default-category-set assignment table. This makes it a convenient lookup source for reporting, validation, and integration logic that needs to know which category sets are flagged as system defaults within Inventory.

Underlying Base Objects

The view is defined over three base objects, all referenced through APPS synonyms:

The joins are driven from MTL_CATEGORY_SETS_B (alias S), which is equijoined to the translation row (alias ST) on CATEGORY_SET_ID and to the default assignment row (alias D) on CATEGORY_SET_ID. Because the join to MTL_DEFAULT_CATEGORY_SETS is an inner join, the view returns only those category sets that have an entry in the defaults table; category sets not designated as defaults are excluded entirely.

Key Columns

  • CATEGORY_SET_ID — primary identifier of the category set; the join key across all three base objects.
  • CATEGORY_SET_NAME — the translated, user-facing name of the category set, resolved from MTL_CATEGORY_SETS_TL in the session language.
  • DESCRIPTION — the translated description of the category set.
  • STRUCTURE_ID — identifies the category set structure (the logical grouping of categories/inventory items) to which the set belongs.
  • VALIDATE_FLAG — indicates whether validation is enforced for the category set, controlling whether only valid category assignments are permitted.
  • FUNCTIONAL_AREA_ID — the functional area for which this category set is the default, from MTL_DEFAULT_CATEGORY_SETS.

Common Use Cases and Queries

Typical uses include resolving the default category set for a functional area within a report or interface, populating a report parameter LOV, and validating that an incoming category set is a designated default. Because the view already restricts to the session language, callers avoid redundant translation joins.

List all default category sets with their functional areas:

  • SELECT category_set_id, category_set_name, structure_id, functional_area_id FROM apps.mtl_default_sets_view;

Retrieve the default category set for a specific functional area:

  • SELECT category_set_name, description FROM apps.mtl_default_sets_view WHERE functional_area_id = :p_area_id;

Join to a functional area reference to produce a readable report:

  • SELECT v.category_set_name, v.validate_flag FROM apps.mtl_default_sets_view v WHERE v.category_set_id = :p_set_id;

Oracle proprietary and confidential information; refer to the ETRM for authoritative definitions.