Search Results gr_toxic_species_b_pk




Overview
Explore in AI Chat

Overview

The GR_TOXIC_SPECIES_B table is a core reference data entity within the Oracle E-Business Suite Process Manufacturing Regulatory Management (GR) module. Its primary role is to maintain a standardized, language-independent list of animal species codes used in toxicological testing and regulatory compliance reporting. The table is seeded with standard three-character codes derived from Sax's Properties of Dangerous Goods, a recognized industry reference. By providing a centralized, controlled vocabulary for test species, it ensures data consistency and integrity for tracking hazardous material properties across the application, which is critical for regulatory submissions and safety data sheets (SDS).

Key Information Stored

While the specific column list is not detailed in the provided metadata, the table's description and key structure define its critical data elements. The primary column is TOXIC_SPECIES_CODE, a three-character alphanumeric key that uniquely identifies each animal species (e.g., 'RAT' for rat, 'RBT' for rabbit). This code serves as the master key for all related data. The table also stores a base description for each code. As a "_B" table, it holds the language-independent transactional data, with translatable descriptions likely managed through its related Translation table (GR_TOXIC_SPECIES_TL). The table's status as seeded indicates it is pre-populated by Oracle, though it may allow for limited user extension.

Common Use Cases and Queries

The primary use case is the validation and display of toxicological test species information. When a user defines the toxic properties of a material in the GR_ITEM_TOXIC table, the application validates the entered species code against GR_TOXIC_SPECIES_B. Common reporting and query scenarios include generating regulatory reports that list all toxicological tests performed on a specific species, or validating data completeness. A typical query to retrieve all valid species codes and their descriptions would be:

  • SELECT toxic_species_code, description FROM gr_toxic_species_b WHERE [language condition];

Another common pattern is joining to the transactional data to report on item-specific toxicology:

  • SELECT i.item_number, t.toxic_species_code, s.description FROM gr_item_toxic i, gr_toxic_species_b s WHERE i.toxic_species_code = s.toxic_species_code;

Related Objects

The GR_TOXIC_SPECIES_B table is central to the toxicological data model, with defined relationships to key transactional and support tables.

  • Primary Key: GR_TOXIC_SPECIES_B_PK on the TOXIC_SPECIES_CODE column.
  • Foreign Key References:
    • GR_ITEM_TOXIC: The GR_ITEM_TOXIC.TOXIC_SPECIES_CODE column references this table. This is the primary transactional link, storing which species was used in testing for a specific inventory item.
    • GR_TOXIC_SPECIES_TL: The GR_TOXIC_SPECIES_TL.TOXIC_SPECIES_CODE column references this table. This translation table provides language-specific descriptions for the base codes stored in GR_TOXIC_SPECIES_B.