Results for “gr_product_classes”

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

Overview

GR_PRODUCT_CLASSES is a reference table in the Oracle E-Business Suite Process Manufacturing Regulatory Management (GR) module. It stores the classifications used to group products that share similar regulatory requirements or physical properties, such as solids, liquids, or acid-based formulations. In Oracle EBS 12.1.1 and 12.2.2, the table resides in the GR schema and carries a VALID status, confirming it is an active, supported object within the regulatory data model.

Because product classes drive downstream compliance logic—particularly the automatic assignment of safety phrases—this table functions as a central reference point for both item-level regulatory data and label configuration. From a Data Vault modeling perspective, the mined foreign-key structure suggests a hub-leaning classification, since GR_PRODUCT_CLASSES is referenced by multiple dependent tables rather than acting as a transactional link or a purely descriptive satellite. This positions it as a natural business-key hub candidate, though the ultimate modeling decision depends on the broader enterprise data architecture.

Key Information Stored

The table contains eight documented columns. The primary key, GR_PRODUCT_CLASSES_PK, is defined on the PRODUCT_CLASS column, which serves as the unique business identifier and the natural join key for related tables. The most significant columns include:

• PRODUCT_CLASS — The unique classification code identifying a product class; also the primary key and business-key candidate.
• PRODUCT_CLASS_DESC — The descriptive name of the class, used in reporting and user-facing selections.
• AUTO_ASSIGN_REC_SAFETY_PHRASES — A flag controlling whether recommended safety phrases are automatically applied to products assigned to the class.
• CREATED_BY, CREATION_DATE — Standard audit columns capturing the creating user and timestamp.
• LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard audit columns recording the most recent modification user, timestamp, and login context.

The audit columns follow the conventional EBS WHO-column pattern and support change tracking and concurrency handling. The single unique index documented is the primary key on PRODUCT_CLASS, making it the definitive business-key candidate for the table.

Common Use Cases and Queries

Typical usage centers on regulatory reporting, label configuration, and item setup. A common query lists all classes with their auto-assignment behavior:

• SELECT PRODUCT_CLASS, PRODUCT_CLASS_DESC, AUTO_ASSIGN_REC_SAFETY_PHRASES FROM GR.GR_PRODUCT_CLASSES;
• Joining to items to enumerate products in a class: SELECT gpc.PRODUCT_CLASS, gig.INVENTORY_ITEM_ID FROM GR.GR_PRODUCT_CLASSES gpc, GR.GR_ITEM_GENERAL gig WHERE gpc.PRODUCT_CLASS = gig.PRODUCT_CLASS;
• Joining to label configuration: SELECT gpc.PRODUCT_CLASS, glpc.* FROM GR.GR_PRODUCT_CLASSES gpc, GR.GR_LABEL_PROD_CLASSES glpc WHERE gpc.PRODUCT_CLASS = glpc.PRODUCT_CLASS;

These patterns support compliance audits, safety-phrase determination, and label generation workflows. Reporting on classes that auto-assign safety phrases is especially useful during regulatory reviews.

Related Objects

The foreign-key relationships documented in the ETRM metadata identify the principal dependent objects:

• GR_ITEM_GENERAL — References GR_PRODUCT_CLASSES through GR_ITEM_GENERAL.PRODUCT_CLASS, linking items to their regulatory class.
• GR_LABEL_PROD_CLASSES — References GR_PRODUCT_CLASSES through GR_LABEL_PROD_CLASSES.PRODUCT_CLASS, associating product classes with label definitions.

These relationships make GR_PRODUCT_CLASSES a parent reference for item-level regulatory data and label configuration. Together with the primary key index GR_PRODUCT_CLASSES_PK, they define the integrity constraints that govern how product classifications propagate through the GR module.