Search Results gr_source_risks




Overview
Explore in AI Chat

Overview

The GR_SOURCE_RISKS table is a core data object within Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2, specifically for the Process Manufacturing Regulatory Management (GR) module. It functions as a critical junction table that establishes and maintains the regulatory relationships between hazard classifications and specific risk phrases. Its primary role is to store the predefined mappings that determine which Risk Phrases (R-phrases) are automatically applied to a product or formulation based on the presence and concentration of specific hazardous ingredients. This enables automated, compliant labeling and safety documentation in regulated manufacturing environments, particularly those adhering to European Union (EU) chemical regulations.

Key Information Stored

The table's structure is defined by its composite primary key, which consists of two foreign key columns. It does not typically store extensive descriptive data, but rather the essential links between other master regulatory tables.

  • HAZARD_CLASSIFICATION_CODE: A foreign key referencing the GR_EUROHAZARDS_B table. This code identifies a specific hazard classification or category (e.g., "Flammable," "Toxic," "Corrosive") as defined within the regulatory framework.
  • RISK_PHRASE_CODE: A foreign key referencing the GR_RISK_PHRASES_B table. This code identifies a standardized risk phrase (e.g., "R10 Flammable," "R23 Toxic by inhalation") that must be communicated on safety data sheets (SDS) and labels.

The combination of these two columns forms a unique record, representing a rule that states: "If an ingredient is assigned this HAZARD_CLASSIFICATION_CODE, then the associated RISK_PHRASE_CODE must be applied."

Common Use Cases and Queries

The primary use case is the automated generation of regulatory content during product development and compliance checks. When a formulator adds an ingredient with a known hazard profile to a recipe, the system queries GR_SOURCE_RISKS to determine all mandatory risk phrases to propagate. A common reporting need is to audit or review all risk phrases linked to a particular hazard class.

Sample Query: List all Risk Phrases for a Specific Hazard

SELECT eh.HAZARD_CLASSIFICATION_CODE, eh.DESCRIPTION as HAZARD_DESCRIPTION,
rp.RISK_PHRASE_CODE, rp.DESCRIPTION as RISK_PHRASE_DESCRIPTION
FROM GR.GR_SOURCE_RISKS sr,
GR.GR_EUROHAZARDS_B eh,
GR.GR_RISK_PHRASES_B rp
WHERE sr.HAZARD_CLASSIFICATION_CODE = eh.HAZARD_CLASSIFICATION_CODE
AND sr.RISK_PHRASE_CODE = rp.RISK_PHRASE_CODE
AND eh.HAZARD_CLASSIFICATION_CODE = 'FLAMMABLE_LIQ' -- Example code
ORDER BY rp.RISK_PHRASE_CODE;

This table is also central to any data migration or initialization scripts for loading country-specific regulatory rules into the GR module.

Related Objects

GR_SOURCE_RISKS is a junction table with defined foreign key relationships to two key reference tables in the GR module. It has no independent meaning without these relationships.

  • GR_EUROHAZARDS_B: The table referenced via the HAZARD_CLASSIFICATION_CODE column. This table stores the master list of hazard classifications used for regulatory assessment.
  • GR_RISK_PHRASES_B: The table referenced via the RISK_PHRASE_CODE column. This table is the master repository for all standardized risk phrase codes and their textual descriptions.

The table's primary key constraint, GR_SOURCE_RISKS_PK, enforces the uniqueness of the hazard-risk phrase combination, preventing duplicate regulatory rules.