Results for “mtl_category_set_valid_cats_u1”

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

Overview

MTL_CATEGORY_SET_VALID_CATS is an Inventory (INV) module table in Oracle E-Business Suite 12.1.1 and 12.2.2 that defines the set of categories valid within a given category set. A category set is a grouping construct that determines which categories can be assigned to items, and this table acts as the intersection that binds each category set to the specific categories permitted inside it. In effect, it is the authorization list that governs categorization: a category cannot be used in a category set unless a corresponding row exists here. The table resides in the INV schema and is classified as VALID in the ETRM repository.

From a Data Vault modeling perspective, the mined classification of this object is satellite-leaning. Read as a modeling suggestion rather than a physical fact, this reflects the table's nature as a dependent, attribute-bearing structure whose identity is derived from the relationship between two parent entities rather than from an independent business key of its own.

Key Information Stored

The table's documented physical schema comprises 13 columns. The most significant are:

• CATEGORY_SET_ID — Foreign key to MTL_CATEGORY_SETS_B; identifies the category set within which the category is valid.
• CATEGORY_ID — Foreign key to MTL_CATEGORIES_B; identifies the category that is authorized for use in that set.
• PARENT_CATEGORY_ID — Captures the parent category in the set's hierarchical structure, where one exists.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — Standard EBS WHO-column audit trail.
• REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE — Concurrent program context that created or last modified the row.
• ZD_EDITION_NAME — Editioning column supporting online patching in the 12.2.x architecture.

The surrogate primary key is defined by the constraint MTL_CATEGORY_SET_VAL_CATS_PK over the composite of CATEGORY_SET_ID and CATEGORY_ID. A separate unique index, MTL_CATEGORY_SET_VALID_CATS_U1, extends that combination with ZD_EDITION_NAME, confirming this triple as the business-key candidate across editions.

Common Use Cases and Queries

Typical uses include validating that a category is permitted in a category set before item categorization, reporting the enabled category lists per set, and reconciling item assignments against the valid list. A representative query returns all valid categories for a given set:

• SELECT vc.category_id, c.category_name FROM mtl_category_set_valid_cats vc JOIN mtl_categories_b c ON c.category_id = vc.category_id WHERE vc.category_set_id = :p_category_set_id

Detection of orphaned or invalid item assignments—rows in MTL_ITEM_CATEGORIES whose set/category pair is absent here—is a frequent data-cleansing pattern. Form and concurrent program logic driven by the item category assignment UI also reads this table to populate list-of-values selections.

Related Objects

The following objects are most significant to this table based on documented relationships:

• MTL_CATEGORY_SETS_B — parent of the CATEGORY_SET_ID foreign key; defines the category set.
• MTL_CATEGORIES_B — parent of the CATEGORY_ID foreign key; defines the category.
• MTL_ITEM_CATEGORIES — references this table through the CATEGORY_SET_ID and CATEGORY_ID pair, binding item assignments to the valid category list.
• MTL_CATEGORY_SETS_TL and MTL_CATEGORIES_TL — translation views supplying user-facing names for the parent entities.
• Item category assignment APIs and the Inventory item setup concurrent programs that maintain valid category membership.