Search Results gmi_category_sets




Overview
Explore in AI Chat

Overview

GMI_CATEGORY_SETS is an Oracle Process Manufacturing (OPM) Inventory table owned by the GMI schema. Its documented purpose is to store the association between OPM Classifications and Oracle Inventory category sets. Any defined category set can be assigned to an OPM Classification, and the category drawn from that category set is subsequently used within OPM for displaying and validating values. The table therefore acts as the configuration bridge that allows OPM item classification screens and validation routines to consume standard Oracle category structures.

From a heuristic Data Vault modeling perspective, the metadata classifies GMI_CATEGORY_SETS as a standalone object. In Data Vault terms this suggests treating it as a hub-like reference table: the durable business keys (OPM_CLASS and USER_OPM_CLASS) identify a classification-to-category-set assignment, while descriptive and audit attributes behave like satellite columns. The heuristic is a modeling suggestion only; the object has no documented foreign-key dependencies to other tables.

Key Information Stored

The table is documented with 10 physical columns in the ETRM 12.2.2 schema. The most significant are:

  • OPM_CLASS — the OPM Classification identifier. This column is the surrogate primary key component underlying constraint GMI_CATEGORY_SETS_PK.
  • USER_OPM_CLASS — the user-facing classification value. This is the business-key candidate, enforced by unique index GMI_CATEGORY_SETS_U1.
  • CATEGORY_SET_ID — the identifier of the Oracle Inventory category set assigned to the classification; this is the central business payload of the row.
  • RESTRICTED — a flag indicating whether the assignment is restricted, controlling the scope in which the category set may be applied.
  • MIGRATED_IND — indicates whether the record originated from a data migration rather than native setup.
  • CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — the standard EBS WHO audit columns recording row creation and change history.

The distinction between OPM_CLASS and USER_OPM_CLASS is important: one functions as the internal primary key while the other serves as the human-readable business key enforced by a unique index.

Common Use Cases and Queries

Typical usage centers on determining which category set is attached to a given classification, or listing all classifications that share a category set.

SELECT gcs.opm_class, gcs.user_opm_class, gcs.category_set_id, gcs.restricted
FROM   gmi.gmi_category_sets gcs
WHERE  gcs.user_opm_class = :classification;

A reverse lookup by category set supports impact analysis before a category set is modified or retired:

SELECT gcs.user_opm_class, gcs.category_set_id
FROM   gmi.gmi_category_sets gcs
WHERE  gcs.category_set_id = :category_set_id;

Reporting scenarios include auditing classifications that lack a valid category set assignment, identifying migrated records via MIGRATED_IND, and validating configuration consistency across environments prior to a 12.1.1 to 12.2.2 upgrade. Because the table is standalone, joins to Oracle Inventory category set definitions are driven by CATEGORY_SET_ID rather than by a documented foreign key.

Related Objects

The ETRM metadata documents no foreign-key relationships for this table, so the following are logical dependencies inferred from its role in the OPM Inventory schema:

  • GMI_CLASSIFICATIONS (or the equivalent OPM classification definition table) — joined on OPM_CLASS / USER_OPM_CLASS to resolve classification descriptions.
  • FND_FLEX_VALUES / FND_FLEX_VALUE_SETS — supply the underlying category values referenced through CATEGORY_SET_ID.
  • EGP_CATEGORY_SETS / category set definition tables — joined on CATEGORY_SET_ID to resolve the category set name and structure.
  • GMI_ITEMS — OPM items are classified against these assignments during item setup and validation.
  • FND_USER — joins to CREATED_BY and LAST_UPDATED_BY for audit reporting.

Because the table is classified as standalone, integrators should treat CATEGORY_SET_ID and the OPM_CLASS columns as the principal join paths when building dependent queries or extracts.