Search Results mtl_icg_categories_pk

Overview

The MTL_ICG_CATEGORIES table is a core data object within the Oracle E-Business Suite (EBS) Inventory (INV) module, specifically for versions 12.1.1 and 12.2.2. It functions as a mapping or recommendation table that links Item Catalog Groups to specific item categories within defined category sets. Its primary role is to facilitate and standardize the item creation and classification process. When a user creates a new item and assigns it to a particular Item Catalog Group, the system can leverage the associations stored in this table to suggest appropriate, pre-defined categories for that item. This enforces data consistency, accelerates data entry, and ensures items are categorized according to established organizational taxonomies.

Key Information Stored

The table's structure is defined by a three-column composite primary key, which uniquely identifies each recommendation record. The key columns are ITEM_CATALOG_GROUP_ID, CATEGORY_ID, and CATEGORY_SET_ID. The ITEM_CATALOG_GROUP_ID is a foreign key to MTL_ITEM_CATALOG_GROUPS_B, identifying the specific catalog group. The CATEGORY_ID, a foreign key to MTL_CATEGORIES_B, holds the identifier for the recommended inventory category. The CATEGORY_SET_ID, a foreign key to MTL_CATEGORY_SETS_B, specifies the category set to which the recommended category belongs. This three-part key ensures that for any given item catalog group, the system can recommend one or more valid category assignments within the context of specific functional category sets (e.g., Inventory, Purchasing, Costing).

Common Use Cases and Queries

A primary use case is during the item master creation workflow in forms like the Item Master or Item Catalog. The application queries this table to populate lists of values for the category fields based on the selected item catalog group. For reporting and data validation, common queries include listing all category recommendations for a specific catalog group or identifying catalog groups that recommend a particular category. A sample SQL pattern to retrieve these recommendations is:

• SELECT cig.ITEM_CATALOG_GROUP_NAME, cat.CATEGORY_NAME, cs.CATEGORY_SET_NAME
• FROM INV.MTL_ICG_CATEGORIES icg,
• INV.MTL_ITEM_CATALOG_GROUPS_B cig,
• INV.MTL_CATEGORIES_B cat,
• INV.MTL_CATEGORY_SETS_B cs
• WHERE icg.ITEM_CATALOG_GROUP_ID = cig.ITEM_CATALOG_GROUP_ID
• AND icg.CATEGORY_ID = cat.CATEGORY_ID
• AND icg.CATEGORY_SET_ID = cs.CATEGORY_SET_ID
• ORDER BY 1, 3, 2;

Administrators may also query this table to audit or maintain the classification rules governing item setup.

Related Objects

MTL_ICG_CATEGORIES is centrally linked to three other fundamental Inventory tables via foreign key constraints. Its dependency on MTL_ITEM_CATALOG_GROUPS_B provides the link to the catalog group entity. The relationships to MTL_CATEGORIES_B and MTL_CATEGORY_SETS_B are critical, as they validate that the recommended categories exist within valid functional sets. While not explicitly listed in the provided metadata, this table is intrinsically related to the Item Master (MTL_SYSTEM_ITEMS_B) entity, as the recommendations stored here are applied during its creation. The table's integrity is enforced by the primary key constraint MTL_ICG_CATEGORIES_PK.