Search Results toxic_exposure_code




Overview
Explore in AI Chat

Overview

The GR_ITEM_TOXIC table is a core data entity within the Oracle E-Business Suite Process Manufacturing Regulatory Management (GR) module. It serves as the central repository for storing detailed toxicity and hazard information associated with manufactured or inventoried items. This table is critical for regulatory compliance, enabling organizations to systematically record and manage the toxicological profile of substances as required by various health, safety, and environmental regulations. Its design supports the association of multiple toxicity records—each representing a distinct toxicological endpoint or study—to a single item, providing a comprehensive view of potential hazards.

Key Information Stored

The table's structure is defined by a composite primary key and several foreign key relationships that enforce data integrity. The primary key, GR_ITEM_TOXIC_PK, uniquely identifies a record through a combination of five columns: TOXIC_EXPOSURE_CODE, LABEL_CODE, ITEM_CODE, TOXIC_ROUTE_CODE, and TOXIC_SPECIES_CODE. These columns, along with TOXIC_EFFECT_CODE, form the core relational links to reference data. The table primarily stores coded keys that point to master data in other tables, such as the specific item (ITEM_CODE), the applicable regulatory label (LABEL_CODE), the route of exposure (e.g., inhalation, dermal), the species tested, the observed toxic effect, and the exposure conditions. It acts as a junction entity that links these discrete pieces of reference information to define a complete toxicological data point for an item.

Common Use Cases and Queries

The primary use case for GR_ITEM_TOXIC is regulatory reporting and label generation. Compliance teams query this table to compile safety data sheets (SDS), prepare regulatory submissions, or generate hazard labels for products. A typical query involves joining the table to its referenced code tables to translate codes into meaningful descriptions. For example, to retrieve all toxicity data for a specific item, one might use a SQL pattern such as:

  • SELECT git.item_code, glb.label_name, gtrb.route_name, gtsb.species_name, gteb.effect_name FROM gr_item_toxic git, gr_labels_b glb, gr_toxic_routes_b gtrb, gr_toxic_species_b gtsb, gr_toxic_effects_b gteb WHERE git.label_code = glb.label_code AND git.toxic_route_code = gtrb.toxic_route_code AND git.toxic_species_code = gtsb.toxic_species_code AND git.toxic_effect_code = gteb.toxic_effect_code AND git.item_code = '<ITEM_CODE>';

This data is also essential for internal risk assessments and operational safety procedures within manufacturing and supply chain contexts.

Related Objects

The GR_ITEM_TOXIC table has defined foreign key relationships with several key reference tables in the GR schema, as documented in the ETRM metadata. These relationships are fundamental to maintaining a valid and consistent toxicity database:

  • GR_ITEM_GENERAL: Links via ITEM_CODE to the master item record within the Regulatory Management module.
  • GR_LABELS_B: Links via LABEL_CODE to the definitions of regulatory labels or hazard classifications.
  • GR_TOXIC_ROUTES_B: Links via TOXIC_ROUTE_CODE to valid routes of exposure (e.g., oral, inhalation).
  • GR_TOXIC_SPECIES_B: Links via TOXIC_SPECIES_CODE to the species (e.g., rat, human) associated with the toxicity data.
  • GR_TOXIC_EFFECTS_B: Links via TOXIC_EFFECT_CODE to the specific toxicological effects or endpoints observed.

These relationships ensure that all toxicity records are associated with valid items, labels, routes, species, and effects, forming a robust and auditable data model for regulatory information.