Search Results mtl_categories_b_kfv




Overview
Explore in AI Chat

Overview

MTL_CATEGORIES_B_KFV is a key flexfield (KFV) view owned by the APPS schema in Oracle E-Business Suite, belonging to the Inventory (INV) product family. It presents category definition data from the Item Categories key flexfield, exposing each category's unique identifier, structure assignment, descriptive attributes, and the individual flexfield segments that make up the category. In the Oracle EBS architecture, "_KFV" views are generated and maintained by the Key Flexfield infrastructure so that concatenated segment values can be reported and queried as a single logical value, while the individual segments remain independently accessible.

Because categories in Oracle Inventory are defined through a key flexfield, the raw definition data resides in a structure that separates the segments from the category identity. This view reconciles the two by surfacing both CONCATENATED_SEGMENTS and the discrete SEGMENT1 through SEGMENT20 columns, along with the standard WHO audit and concurrent program columns. It is used extensively in reporting, integration, and inquiry layers where a category must be presented either in its concatenated form or segmented for validation and analysis.

Underlying Base Objects

According to the ETRM metadata for 12.2.2, the view is defined over a single referenced base object: MTL_CATEGORIES_B, referenced through a synonym. MTL_CATEGORIES_B is the category definitions base table in Oracle Inventory, storing each category's identity, structure assignment, descriptive and supplier-related flags, enablement dates, and the flexfield segment columns. The "_B" suffix indicates the base (non-translated) table, and the corresponding translated table, MTL_CATEGORIES_TL, supplies language-specific descriptions in other reporting objects.

Consistent with the documented view text, MTL_CATEGORIES_B_KFV performs a direct projection from MTL_CATEGORIES_B, selecting the identifier, structure, attributes, segments, and standard audit columns. Notably, the view text hard-codes the concatenated segment and padded concatenated segment expressions as blank padded strings, reflecting the documented definition in this environment. ROW_ID is derived from ROWID to supply a stable row identifier for the result set.

Key Columns

Common Use Cases and Queries

The view is typically queried to resolve category identifiers into readable category definitions, to validate segment combinations, and to drive inventory and pricing reports. A common pattern joins the view to item-category assignment tables on CATEGORY_ID and filters by STRUCTURE_ID to isolate a particular category set.

  • Listing active categories within a given structure for reporting or reconciliation.
  • Resolving CATEGORY_ID values from assignment tables into concatenated segment values.
  • Validating that expected segments are populated for a category structure.
  • Filtering categories by effective dates, enablement, or supplier enablement flags.

Sample query:

SELECT category_id, structure_id, concatenated_segments, segment1, segment2, segment3, description, enabled_flag
FROM apps.mtl_categories_b_kfv
WHERE structure_id = :structure_id
AND enabled_flag = 'Y';