Search Results mtl_item_catalog_groups_kfv




Overview
Explore in AI Chat

Overview

MTL_ITEM_CATALOG_GROUPS_KFV is a key flexfield (KFF) view in the Oracle E-Business Suite Inventory (INV) module. Its name follows the standard KFF naming convention: the "_KFV" suffix identifies it as a key flexfield view that exposes a concatenated, display-ready representation of a flexfield structure. In this case, the flexfield belongs to the Item Catalog Groups entity, which in Oracle Inventory is implemented through the Item Catalog Group key flexfield. This flexfield allows an organization to define its own catalog group structure (for example, a segmented hierarchy of catalog categories used to organize items for ordering, browsing, or reporting).

The view is documented in ETRM 12.2.2 under the Inventory product with the description "Item Catalog Key Flexfield View." Its principal role is to present the catalog group identifier along with its concatenated segment values in a form suitable for reporting, list-of-values queries, and integrations. Rather than reconstructing the flexfield combination from individual segment columns, consumers can read a single concatenated string from the view. In 12.1.1 and 12.2.2 the KFV pattern is consistent, though availability and registration may vary by deployment.

Underlying Base Objects

According to the documented view text, the view is defined over a single base table:

  • MTL_ITEM_CATALOG_GROUPS — the base table holding Item Catalog Group definitions, including segment columns, descriptive flexfield (DFF) attributes, and WHO/audit columns.

The view is a straightforward projection: it selects all significant columns from the base table, adds a synthetic ROW_ID derived from ROWID, and appends two literal values ('X', 'X') that map to the flexfield view's standard CONCATENATED_SEGMENTS and PADDED_CONCATENATED_SEGMENTS columns. In a fully compiled flexfield view, these two columns would normally be generated by the key flexfield compiler to hold the concatenated segment string and its space-padded equivalent. Here, however, they are exposed as static literals, and the ETRM metadata explicitly records "Not implemented in this database," meaning the flexfield view has not been compiled/registered in that environment. The documented referenced base objects list is empty, but the view text clearly establishes MTL_ITEM_CATALOG_GROUPS as the sole source object.

Key Columns

  • ROW_ID — pseudocolumn derived from ROWID, used to uniquely identify a row within the view.
  • ITEM_CATALOG_GROUP_ID — the primary identifier of the catalog group; the flexfield's unique combination identifier.
  • SEGMENT1 — the segment column holding the flexfield segment value for this catalog group structure.
  • DESCRIPTION — descriptive text associated with the catalog group.
  • ATTRIBUTE1–ATTRIBUTE15, ATTRIBUTE_CATEGORY — descriptive flexfield (DFF) context and attribute columns, allowing extensible, customer-defined attributes on the catalog group.
  • START_DATE_ACTIVE, END_DATE_ACTIVE, INACTIVE_DATE — date-range fields controlling when the catalog group is active or inactive.
  • ENABLED_FLAG, SUMMARY_FLAG — status indicators for whether the group is enabled and whether it is a summary (roll-up) node.
  • CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — standard WHO audit columns.
  • REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE — concurrent program / request tracking columns.
  • CONCATENATED_SEGMENTS, PADDED_CONCATENATED_SEGMENTS — in this implementation literal 'X' values rather than compiled segment concatenations, reflecting that the flexfield view is not fully implemented.

Common Use Cases and Queries

The view is typically used to retrieve catalog group definitions for reporting, validation, or integration. A basic query returns the identifier, segment, and descriptive attributes:

  • SELECT item_catalog_group_id, segment1, description FROM mtl_item_catalog_groups_kfv WHERE enabled_flag = 'Y';
  • SELECT k.item_catalog_group_id, k.description FROM mtl_item_catalog_groups_kfv k ORDER BY k.item_catalog_group_id;
  • SELECT k.item_catalog_group_id, k.segment1, k.enabled_flag, k.start_date_active, k.end_date_active FROM mtl_item_catalog_groups_kfv k WHERE TRUNC(SYSDATE) BETWEEN NVL(k.start_date_active, SYSDATE) AND NVL(k.end_date_active, SYSDATE);

Because the view is documented as "Not implemented in this database," consumers in 12.1.1 and 12.2.2 should verify that the flexfield view has been compiled before relying on CONCATENATED_SEGMENTS. Where the view is not compiled, queries should instead join to the base table MTL_ITEM_CATALOG_GROUPS or use the flexfield APIs (FND_FLEX_APIS) to derive the concatenated combination. Developers should not treat CONCATENATED_SEGMENTS as a valid concatenation unless the implementation confirms the view has been generated by the key flexfield compiler.