Results for “gr_linked_risks”

30 results




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

Overview

GR_LINKED_RISKS is a table in the GR schema (Process Manufacturing Regulatory Management) in Oracle E-Business Suite 12.1.1 and 12.2.2. It stores additional Risk Phrase Codes that correspond to European environmental class hazards and which are associated with a primary ("first") Risk Phrase Code. In regulatory and hazard-communication workflows, a single substance or preparation may trigger a primary risk phrase while simultaneously requiring one or more subsidiary environmental hazard phrases. This table captures that supplementary association, allowing the regulatory engine to resolve the complete set of linked hazard phrases rather than only the initially identified one.

The ETRM relationship metadata classifies this object as satellite-leaning. In Data Vault modeling terms, this is a heuristic suggestion: the table behaves less like an independent hub and more like a descriptive satellite attached to a parent business entity, because its identity is defined entirely by the combination of columns it inherits from GR_RISK_CALCULATIONS rather than by a self-generated key. The primary key is a composite (RISK_PHRASE_CODE, CALCULATION_NAME_ID), reinforcing that the record only exists in the context of a parent calculation and risk phrase.

Key Information Stored

The table is documented with eight physical columns in the 12.2.2 schema. The most important are described below.

  • RISK_PHRASE_CODE — The primary risk phrase to which additional environmental hazard codes are attached. Part of the composite primary key and a foreign key to GR_RISK_CALCULATIONS.
  • CALCULATION_NAME_ID — Identifier of the risk calculation context under which the linkage is valid. Together with RISK_PHRASE_CODE this forms the composite primary key.
  • LINKED_RISK_PHRASE_CODE — The additional (linked) risk phrase applied because of the first risk phrase. This is the core payload column of the table.
  • CREATED_BY / CREATION_DATE — Standard EBS audit columns recording who created the row and when.
  • LAST_UPDATED_BY / LAST_UPDATE_DATE / LAST_UPDATE_LOGIN — Standard EBS audit columns capturing the last modification user, timestamp, and login session.

The surrogate key is not a single generated identifier; instead the primary key constraint GR_LINKED_RISKS_PK is defined over (RISK_PHRASE_CODE, CALCULATION_NAME_ID). Because that same index also uniquely enforces the business identity, it serves as the business-key candidate. There is no separate artificial sequence-based column documented.

Common Use Cases and Queries

Typical scenarios include resolving the full hazard-phrase set for a regulated substance, building regulatory reports for European environmental class hazards, and validating that a calculation's primary phrase is correctly expanded.

  • Listing all linked phrases for a given primary phrase and calculation:
    SELECT risk_phrase_code, calculation_name_id, linked_risk_phrase_code
    FROM   gr.gr_linked_risks
    WHERE  risk_phrase_code = :phrase
    AND    calculation_name_id = :calc;
  • Reporting every linkage defined for a calculation:
    SELECT linked_risk_phrase_code
    FROM   gr.gr_linked_risks
    WHERE  calculation_name_id = :calc;
  • Auditing recently maintained linkages using the standard audit columns:
    SELECT risk_phrase_code, linked_risk_phrase_code, last_updated_by, last_update_date
    FROM   gr.gr_linked_risks
    WHERE  last_update_date >= :since;

Related Objects

  • GR_RISK_CALCULATIONS — Referenced by GR_LINKED_RISKS via the columns RISK_PHRASE_CODE and CALCULATION_NAME_ID; this parent table supplies the calculation context.
  • GR_RISK_PHRASES — Master reference of the risk phrase codes used in RISK_PHRASE_CODE and LINKED_RISK_PHRASE_CODE.
  • GR_RISK_PHRASE_TRANSLATIONS — Supplies language-specific text for the phrase codes surfaced through this table.
  • GR_SUBSTANCE_RISK_* views — Reporting views that expand primary phrases into their linked environmental phrases.
  • GR_RISK_CALCULATIONS_PK — Parent key constraint targeted by the foreign key from this table.

Because the table is a satellite in the heuristic classification, join queries should always anchor on GR_RISK_CALCULATIONS to preserve correct parent context.