Search Results gr_toxic_routes_b_pk




Overview
Explore in AI Chat

Overview

The GR_TOXIC_ROUTES_B table is a core reference data entity within the Oracle E-Business Suite Process Manufacturing Regulatory Management (GR) module. It serves as the master repository for standardized codes representing the route of administration for chemical toxicity tests. These codes, which are based on the nomenclature from Sax's "Properties of Dangerous Goods," are critical for classifying and reporting the method by which a substance is introduced into a test organism (e.g., inhalation, ingestion, dermal application). The table is seeded with standard values during installation, ensuring data consistency and compliance with established regulatory frameworks. Its primary role is to provide a validated lookup source for toxicity data captured elsewhere in the system, forming an essential component of product safety and regulatory compliance management.

Key Information Stored

The table's structure is designed to store the essential code and its associated descriptive metadata. The primary column is the TOXIC_ROUTE_CODE, a three-character alphanumeric key that uniquely identifies each route of administration. While the provided metadata does not list all columns explicitly, a table of this nature in a multi-language environment typically includes standard WHO columns for tracking data creation and modification, such as CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, and LAST_UPDATED_BY. The core descriptive text for each code, stored by language, is maintained in the related translation table, GR_TOXIC_ROUTES_TL, which is linked via the TOXIC_ROUTE_CODE.

Common Use Cases and Queries

This table is primarily used in two contexts: data validation and regulatory reporting. When users enter toxicity information for a material (e.g., in GR_ITEM_TOXIC), the application validates the entered route code against this table. For reporting, it is joined to toxicity data to provide meaningful descriptions. A common query pattern involves retrieving the master list of valid codes or joining to transactional data for a report.

  • Retrieving All Valid Routes: SELECT toxic_route_code FROM gr.gr_toxic_routes_b ORDER BY 1;
  • Joining to Toxicity Data for Reporting: SELECT it.item_id, b.toxic_route_code, tl.description FROM gr_item_toxic it JOIN gr_toxic_routes_b b ON it.toxic_route_code = b.toxic_route_code JOIN gr_toxic_routes_tl tl ON b.toxic_route_code = tl.toxic_route_code AND tl.language = USERENV('LANG');

Related Objects

The GR_TOXIC_ROUTES_B table is central to a small but critical data model within Regulatory Management. It is referenced by two key objects, as documented by its foreign key relationships:

  • GR_ITEM_TOXIC: This transactional table stores specific toxicity test results for items. Its column GR_ITEM_TOXIC.TOXIC_ROUTE_CODE is a foreign key referencing GR_TOXIC_ROUTES_B, ensuring that every recorded test uses a valid, standardized administration route.
  • GR_TOXIC_ROUTES_TL: This is the translation table for GR_TOXIC_ROUTES_B. Its column GR_TOXIC_ROUTES_TL.TOXIC_ROUTE_CODE is a foreign key referencing the base table, establishing a one-to-many relationship where each code can have multiple language-specific descriptions.

The table's primary key constraint, GR_TOXIC_ROUTES_B_PK on the TOXIC_ROUTE_CODE column, enforces the uniqueness of these codes and supports these relationships.