Search Results gr_linked_risks




Overview
Explore in AI Chat

Overview

The GR_LINKED_RISKS table is a core data object within the Oracle E-Business Suite (EBS) Process Manufacturing Regulatory Management (GR) module. It plays a specialized role in managing regulatory compliance for products, specifically within the context of European environmental hazard classifications. The table's primary function is to store associations between a primary Risk Phrase Code and additional, linked Risk Phrase Codes. This linkage is essential for accurately representing complex regulatory hazards where a single substance or product classification may require the combination of multiple, specific risk phrases to fully describe its environmental impact, as mandated by regulations such as the EU CLP (Classification, Labelling and Packaging) regulation.

Key Information Stored

The table structure is defined by a composite primary key, ensuring a unique relationship between its two core columns. The key columns are:

  • RISK_PHRASE_CODE: This column stores the code for the primary or base risk phrase. It acts as a foreign key linking back to the master list of risk calculations.
  • CALCULATION_NAME_ID: This column holds an identifier that, in conjunction with the RISK_PHRASE_CODE, defines a specific regulatory calculation context. It is also part of the foreign key relationship.
Together, these columns form the primary key (GR_LINKED_RISKS_PK). For each unique pair, the table stores a record of an additional risk phrase code that is linked to the primary one, thereby building a complete set of required phrases for a given hazard scenario.

Common Use Cases and Queries

This table is critical for generating accurate safety data sheets (SDS), product labels, and regulatory reports within the EBS environment. A common operational use case involves querying all linked risk phrases for a specific product's hazard profile to ensure compliance documentation is complete. For example, a regulatory analyst might execute a query to retrieve all supplementary environmental risk phrases associated with a primary hazard code for a specific calculation set. Sample SQL would involve joining GR_LINKED_RISKS with GR_RISK_CALCULATIONS on the RISK_PHRASE_CODE and CALCULATION_NAME_ID columns to fetch descriptive details. Reporting use cases focus on auditing and validating that all mandated risk phrase combinations are correctly maintained in the system for substances falling under European environmental hazard classes.

Related Objects

The GR_LINKED_RISKS table has a direct and singular foreign key dependency within the GR module schema, as documented in the provided metadata.

  • GR_RISK_CALCULATIONS: This is the primary related table. The GR_LINKED_RISKS table references it via a foreign key constraint using both columns of its composite primary key: GR_LINKED_RISKS.RISK_PHRASE_CODE and GR_LINKED_RISKS.CALCULATION_NAME_ID map to corresponding columns in GR_RISK_CALCULATIONS. This relationship ensures referential integrity, meaning a linked risk phrase must be associated with a valid, existing risk calculation record.
This relationship is fundamental, as GR_RISK_CALCULATIONS serves as the master source for risk phrase definitions and calculation logic, while GR_LINKED_RISKS stores the specific multi-phrase combinations derived from that master data.