Search Results gr_toxic_species_tl




Overview
Explore in AI Chat

Overview

The GR_TOXIC_SPECIES_TL table is a core data object within the Process Manufacturing Regulatory Management (GR) module of Oracle E-Business Suite (EBS) releases 12.1.1 and 12.2.2. It functions as a translation table (indicated by the "_TL" suffix), designed to store language-specific descriptions for standardized codes representing animal species used in toxicological testing. Its primary role is to support the global regulatory compliance features of the application by enabling the multilingual representation of controlled scientific vocabulary. This ensures that safety data sheets, regulatory reports, and hazard communications can be accurately generated in the user's preferred language while maintaining referential integrity to a base set of standard codes.

Key Information Stored

The table stores translated textual descriptions keyed by a species code and a language identifier. The critical columns include TOXIC_SPECIES_CODE, a three-character standard code based on references like Sax's Properties of Dangerous Goods. The LANGUAGE column holds the code (e.g., 'US', 'F') for the translation's language, linked to the FND_LANGUAGES table. A corresponding DESCRIPTION column (implied by standard TL table conventions) would store the translated name of the species (e.g., "Rat," "Mouse") in the specified language. The SOURCE_LANG column identifies the original language in which the record was created, also referencing FND_LANGUAGES. The combination of TOXIC_SPECIES_CODE and LANGUAGE forms the table's primary key, enforcing uniqueness of translations per language.

Common Use Cases and Queries

This table is primarily accessed to retrieve localized species descriptions for regulatory reporting and UI display. A common use case is populating a list of values (LOV) for a "Test Species" field in a toxicology data entry form, filtered by the current session language. For reporting, it is used to join translated descriptions onto core toxicological data. Sample SQL to fetch all translations for a specific species code, or to get the description for the current session language, would be typical patterns.

  • Retrieving Translations for a Session Language: SELECT t.description FROM gr_toxic_species_tl t, fnd_languages l WHERE t.language = l.language_code AND t.toxic_species_code = :p_code AND l.nls_language = USERENV('LANG');
  • Reporting Join with Base Table: SELECT b.toxic_species_code, t.description FROM gr_toxic_species_b b, gr_toxic_species_tl t WHERE b.toxic_species_code = t.toxic_species_code AND t.language = :p_report_lang;

Related Objects

The GR_TOXIC_SPECIES_TL table maintains defined foreign key relationships with several key EBS entities, ensuring data integrity and enabling joins for application logic.

  • GR_TOXIC_SPECIES_B: This is the base or "seed" table. The relationship is defined on the TOXIC_SPECIES_CODE column. The "_B" table stores the language-independent code, which the "_TL" table provides translations for.
  • FND_LANGUAGES (for LANGUAGE column): This relationship validates that the LANGUAGE code used for a translation is an active, installed language within the EBS instance.
  • FND_LANGUAGES (for SOURCE_LANG column): This separate relationship validates the source language code, which tracks the original language of the seeded translation data.