Results for “gr_item_risk_phrases”

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

Overview

The GR_ITEM_RISK_PHRASES table is a core data object within the Oracle E-Business Suite Process Manufacturing Regulatory Management module (product code GR). It stores the Standard European Risk Phrase assignments associated with an item, enabling organizations to record and report the regulatory hazard classifications that apply to a given material, product, or substance. The table resides in the GR schema and is documented as VALID in ETRM 12.1.1 and 12.2.2. Because a single item may carry more than one applicable risk phrase — and because the same risk phrase may apply to many items — the table is designed as a many-to-many association table rather than a single-row attribute store.

From a Data Vault modeling perspective, the heuristic classification mined from the foreign-key structure is link. This is a modeling suggestion rather than a mandated implementation: the table resolves the relationship between items (via ITEM_CODE) and risk phrases (via RISK_PHRASE_CODE), which is the defining characteristic of a link entity. Practically, this means the table should be treated as a relationship record, with descriptive attributes such as temperature data and audit columns carried alongside the key combination.

Key Information Stored

The documented physical schema contains ten columns. The most significant for functional and reporting purposes are:

• ITEM_CODE — Identifies the item to which the risk phrase applies. This column participates in the composite primary key and carries a foreign key to GR_EMEA.
• RISK_PHRASE_CODE — The Standard European risk phrase code assigned to the item. This column participates in the composite primary key and carries a foreign key to GR_RISK_PHRASES_B.
• PHRASE_CODE — An additional phrase reference, carrying a foreign key to GR_PHRASES_B; it links the row to the broader phrase definition catalogue.
• TEMPERATURE — Stores the temperature value associated with the risk phrase assignment, supporting conditional or temperature-dependent hazard statements.
• TEMPERATURE_SCALE — Identifies the scale (for example, Celsius or Fahrenheit) applicable to the stored temperature value.
• CREATED_BY, CREATION_DATE — Standard EBS audit columns recording who inserted the row and when.
• LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard EBS audit columns recording the most recent modification and the login context of the change.

The surrogate primary key is GR_ITEM_RISK_PHRASES_PK, which is defined over the business-key candidate pair ITEM_CODE and RISK_PHRASE_CODE. Because the primary key is built directly on these two business columns and no separate system-generated identifier is documented, the unique index GR_ITEM_RISK_PHRASES_PK also serves as the documented uniqueness enforcement for the item-to-risk-phrase combination.

Common Use Cases and Queries

Typical uses include generating regulatory documentation such as Safety Data Sheets and labels, compliance reporting against European risk phrase requirements, and item master enrichment for hazardous materials management. The following pattern retrieves all risk phrases assigned to a specific item:

• SELECT irp.ITEM_CODE, irp.RISK_PHRASE_CODE, irp.PHRASE_CODE, irp.TEMPERATURE, irp.TEMPERATURE_SCALE FROM GR.GR_ITEM_RISK_PHRASES irp WHERE irp.ITEM_CODE = :item_code;

To resolve the descriptive text behind a risk phrase code, join to the base risk phrase table:

• SELECT irp.ITEM_CODE, rp.RISK_PHRASE_CODE FROM GR.GR_ITEM_RISK_PHRASES irp, GR.GR_RISK_PHRASES_B rp WHERE irp.RISK_PHRASE_CODE = rp.RISK_PHRASE_CODE;

Reporting queries frequently aggregate assignments to identify items carrying multiple hazard phrases, or to audit changes by filtering on LAST_UPDATE_DATE. Because the table is link-shaped, reverse lookups — finding every item associated with a given risk phrase — are equally common and use the same join columns.

Related Objects

The following objects are the most significant directly related to GR_ITEM_RISK_PHRASES, based on the documented foreign-key relationships:

• GR_EMEA — joined on GR_ITEM_RISK_PHRASES.ITEM_CODE = GR_EMEA.ITEM_CODE; provides the item-level regulatory context.
• GR_RISK_PHRASES_B — joined on GR_ITEM_RISK_PHRASES.RISK_PHRASE_CODE = GR_RISK_PHRASES_B.RISK_PHRASE_CODE; the base table holding risk phrase definitions.
• GR_PHRASES_B — joined on GR_ITEM_RISK_PHRASES.PHRASE_CODE = GR_PHRASES_B.PHRASE_CODE; the broader phrase definition base table.

These three tables form the immediate dependency set for the object. Reporting views and concurrent programs in the GR module that produce hazard documentation typically traverse from GR_ITEM_RISK_PHRASES outward to these base tables to obtain descriptive text, while the primary key GR_ITEM_RISK_PHRASES_PK enforces the uniqueness of each item-to-risk-phrase pairing.