Search Results gr_toxic_effects_b




Overview
Explore in AI Chat

Overview

The GR_TOXIC_EFFECTS_B table is a core reference data entity within the Oracle E-Business Suite Process Manufacturing Regulatory Management (GR) module, specifically in versions 12.1.1 and 12.2.2. It functions as the master repository for standardized codes representing observed toxic effects of substances, such as those found in chemical products or hazardous materials. Its primary role is to ensure data integrity and consistency in regulatory compliance reporting by providing a controlled, language-independent list of toxic effect classifications. The table is pre-seeded with standard three-character codes derived from authoritative sources like Sax's Properties of Dangerous Goods, establishing a foundational taxonomy used throughout the regulatory management system.

Key Information Stored

The table's central purpose is to store the unique identifier for each toxic effect. Based on the provided metadata, the primary structure revolves around the TOXIC_EFFECT_CODE column, which serves as the table's primary key. This column holds the critical three-character alphanumeric code that classifies a specific toxicological outcome (e.g., 'IRR' for irritation, 'NVS' for nervous system effects). While the specific column list is not fully detailed in the excerpt, the description indicates the base table (_B suffix) stores language-independent data. The associated translation table, GR_TOXIC_EFFECTS_TL, holds the descriptive name (e.g., "Irritant", "Carcinogen") for each code in multiple languages, linked via the TOXIC_EFFECT_CODE foreign key.

Common Use Cases and Queries

This table is primarily used in two key regulatory contexts: product safety management and compliance documentation. A common operational use case is the assignment of toxic effect codes to specific items or ingredients within the GR_ITEM_TOXIC table, which links substances to their potential hazards. For reporting, the table enables the generation of Safety Data Sheets (SDS), hazardous material labels, and regulatory submissions that require standardized hazard classifications. A typical query would join the base table to its translation table to retrieve a user-friendly list of codes and descriptions for a setup or reporting interface:

  • SELECT b.TOXIC_EFFECT_CODE, tl.MEANING FROM GR.GR_TOXIC_EFFECTS_B b, GR.GR_TOXIC_EFFECTS_TL tl WHERE b.TOXIC_EFFECT_CODE = tl.TOXIC_EFFECT_CODE AND tl.LANGUAGE = USERENV('LANG');

Another frequent pattern is validating or reporting on items associated with a specific toxic effect, requiring a join to the GR_ITEM_TOXIC table.

Related Objects

The GR_TOXIC_EFFECTS_B table is central to a small but critical data model within Regulatory Management. Its relationships, as documented, are as follows:

  • Primary Key: The table is uniquely identified by the constraint GR_TOXIC_EFFECTS_B_PK on the column TOXIC_EFFECT_CODE.
  • Foreign Key Dependencies (Child Tables): Two tables reference GR_TOXIC_EFFECTS_B via foreign key relationships:
    • GR_ITEM_TOXIC: Links inventory items to their specific toxic effects. The join is on GR_ITEM_TOXIC.TOXIC_EFFECT_CODE = GR_TOXIC_EFFECTS_B.TOXIC_EFFECT_CODE.
    • GR_TOXIC_EFFECTS_TL: The translation table that provides the language-specific description for each code. The join is on GR_TOXIC_EFFECTS_TL.TOXIC_EFFECT_CODE = GR_TOXIC_EFFECTS_B.TOXIC_EFFECT_CODE.

These relationships enforce referential integrity, ensuring that any toxic effect assigned to an item or described in a translation must first be defined in the GR_TOXIC_EFFECTS_B master table.