Search Results gr_toxic_routes_tl




Overview
Explore in AI Chat

Overview

The GR_TOXIC_ROUTES_TL table is a core data entity within the Oracle E-Business Suite (EBS) Process Manufacturing Regulatory Management (GR) module. It functions as a translation table, storing language-specific descriptions for standard observed toxic routes. These codes are critical for classifying and documenting the pathways through which a substance can cause toxic effects, such as inhalation, ingestion, or skin contact, in compliance with global regulatory standards. The table's design follows the standard EBS multilingual architecture, enabling the system to present toxic route information in a user's installed application language. It is a seeded reference table, meaning it is pre-populated by Oracle with standard three-character codes based on the authoritative source, Sax's Properties of Dangerous Goods.

Key Information Stored

The table's structure is defined by its composite primary key and its language columns. The primary key consists of the TOXIC_ROUTE_CODE and LANGUAGE columns, ensuring a unique translated description exists for each code in each supported language. The TOXIC_ROUTE_CODE is the short, three-character identifier (e.g., 'INH' for inhalation) that links to the base table. The LANGUAGE column identifies the language of the specific row (e.g., 'US' for American English). A critical supporting column is SOURCE_LANG, which records the original language in which the data was entered, facilitating the translation process. The most user-facing column is typically DESCRIPTION (implied by the TL table convention), which holds the translated textual name of the toxic route. Other standard TL columns like CREATED_BY and LAST_UPDATE_DATE are also present for auditing.

Common Use Cases and Queries

This table is primarily queried to support regulatory reporting, safety data sheet (SDS) generation, and user interface displays within the GR module. A common use case is retrieving the user-friendly description of a toxic route for a given code in the session language. For example, when displaying a list of hazards associated with a product, the system would join to this table to present the toxic route description correctly. A typical query pattern involves joining to the base table (GR_TOXIC_ROUTES_B) and filtering by the current session language.

SELECT b.TOXIC_ROUTE_CODE,
       tl.DESCRIPTION
FROM   GR_TOXIC_ROUTES_B b,
       GR_TOXIC_ROUTES_TL tl
WHERE  b.TOXIC_ROUTE_CODE = tl.TOXIC_ROUTE_CODE
AND    tl.LANGUAGE = USERENV('LANG')
ORDER BY tl.DESCRIPTION;

Another key use case is during the setup and maintenance of regulatory content, where administrators may need to view or update translations for all installed languages.

Related Objects

The GR_TOXIC_ROUTES_TL table has defined dependencies on several key EBS objects, as documented by its foreign key constraints:

  • GR_TOXIC_ROUTES_B: This is the base (translation-independent) table for toxic routes. The TL table references it via the TOXIC_ROUTE_CODE column. All codes in the TL table must exist in the base table.
  • FND_LANGUAGES (two relationships): The TL table references this Oracle Application Object Library table twice. The LANGUAGE column foreign key ensures the value is a valid installed language. The SOURCE_LANG column foreign key similarly ensures the source language is valid.

This relationship structure confirms that GR_TOXIC_ROUTES_TL is a child of GR_TOXIC_ROUTES_B and is integral to the EBS foundation's multilingual support framework.