Results for “gr_hazard_groups”

48 results




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

Overview

GR_HAZARD_GROUPS is a reference (lookup) table owned by the GR schema within Oracle E-Business Suite Process Manufacturing Regulatory Management. Its defined purpose is narrow and precise: it stores the Hazard Group Code together with the corresponding Hazard Group Description. In practice the table acts as the controlled vocabulary that classifies hazardous materials for regulatory reporting, labeling, and MSDS (Material Safety Data Sheet) generation. Rather than describing individual substances, GR_HAZARD_GROUPS defines the grouping categories that downstream hazard definitions inherit.

Applying the heuristic Data Vault classification mined from its foreign key structure, this object is hub-leaning. That is, it behaves as a business-key hub: a durable list of unique hazard group identifiers (HAZARD_GROUP_CODE) that other tables reference. Under this modeling suggestion, GR_HAZARD_GROUPS would serve as the hub of business keys, while descriptive attributes such as HAZARD_GROUP_DESCRIPTION would be modeled as satellite data. The table status is VALID in both Oracle EBS 12.1.1 and 12.2.2 environments.

Key Information Stored

The documented physical schema in ETRM 12.2.2 shows seven columns. The most significant are:

  • HAZARD_GROUP_CODE — The primary key column and the sole business-key candidate, enforced by the unique index GR_HAZARD_GROUPS_PK. This code is the value propagated to dependent hazard tables. It is the single most important column in the object.
  • HAZARD_GROUP_DESCRIPTION — The human-readable, translatable text label describing the hazard group. It is the principal descriptive attribute and the field most often surfaced in reports and LOVs.
  • CREATED_BY, CREATION_DATE — Standard Oracle EBS WHO columns recording the user and timestamp of row creation.
  • LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard auditing columns recording the last modifying user, timestamp, and login session.

Note that HAZARD_GROUP_CODE functions as the business key published to foreign tables; the schema does not document a separate surrogate numeric primary key, so the code itself is the identifier.

Common Use Cases and Queries

Typical usage centers on validating, translating, and joining hazard group codes against the tables that consume them. A common reporting pattern retrieves the code and description for display:

  • SELECT HAZARD_GROUP_CODE, HAZARD_GROUP_DESCRIPTION FROM GR.GR_HAZARD_GROUPS ORDER BY HAZARD_GROUP_CODE;
  • Joining to dependent hazard records: SELECT e.*, g.HAZARD_GROUP_DESCRIPTION FROM GR.GR_EUROHAZARDS_B e, GR.GR_HAZARD_GROUPS g WHERE e.HAZARD_GROUP_CODE = g.HAZARD_GROUP_CODE;
  • A validation query to detect orphaned or invalid codes: left-join dependent rows to GR_HAZARD_GROUPS and filter where the group is null.
  • An LOV/concatenated value query for form or concurrent program parameters, concatenating code and description.

Because the table is small and static, it is frequently cached and used primarily for data enrichment rather than transactional activity.

Related Objects

The documented relationships identify the following:

  • GR_EUROHAZARDS_B — The principal dependent table. Its HAZARD_GROUP_CODE column has a foreign key to GR_HAZARD_GROUPS, meaning each European hazard definition belongs to a hazard group. This is the only foreign key source documented.
  • GR_HAZARD_GROUPS_PK — The unique index / primary key constraint on HAZARD_GROUP_CODE that enforces uniqueness and provides the integration point for foreign keys.
  • GR_EUROHAZARDS_TL — The translated (TL) companion of GR_EUROHAZARDS_B, joined via its base table on hazard records that in turn resolve through the group code.
  • Additional GR-schema hazard and MSDS-related objects that store HAZARD_GROUP_CODE as a descriptive attribute.

The dominant integration path is GR_EUROHAZARDS_B.HAZARD_GROUP_CODE → GR_HAZARD_GROUPS.HAZARD_GROUP_CODE, making this table a reference source rather than a transaction target.