Search Results po_hazard_classes_tl




Overview
Explore in AI Chat

Overview

The PO_HAZARD_CLASSES_TL table is a core translation table within the Oracle E-Business Suite Purchasing (PO) module. It stores the translated descriptions for hazardous material classes, enabling the system to present this critical safety information in multiple languages. This table supports the global operations of an organization by ensuring that hazard classifications on purchase orders, requisitions, and related documents are accurately communicated in the user's or supplier's preferred language. Its role is integral to maintaining compliance with international safety and environmental regulations within the procurement process.

Key Information Stored

The table's structure is designed to support multilingual data through a combination of a base key and a language code. The primary data stored includes the translated name of the hazard class. Key columns, as indicated by the documented primary and unique keys, are:

  • HAZARD_CLASS_ID: The internal identifier that links the translation row to its corresponding base record in the parent table (typically PO_HAZARD_CLASSES_B).
  • LANGUAGE: The language code (e.g., 'US', 'DE', 'FR') for the translated text.
  • HAZARD_CLASS: The translated textual description or name of the hazardous class in the specified language.

The existence of two distinct keys—a primary key on (HAZARD_CLASS_ID, LANGUAGE) and a unique key on (HAZARD_CLASS, LANGUAGE)—ensures data integrity by preventing duplicate translations for the same class in a language and maintaining uniqueness of the translated text per language.

Common Use Cases and Queries

This table is primarily accessed by the application's multilingual architecture to display hazard information. A common reporting use case involves extracting a list of all hazard classes with their descriptions in a specific language for compliance documentation or supplier communication. A typical query would join this translation table to its base table to retrieve meaningful data.

Sample SQL Pattern:
SELECT b.hazard_class_code,
      tl.hazard_class,
      tl.language
FROM po_hazard_classes_b b,
      po_hazard_classes_tl tl
WHERE b.hazard_class_id = tl.hazard_class_id
AND tl.language = USERENV('LANG')
ORDER BY tl.hazard_class;

This pattern is also fundamental for any data migration or integration project where hazard class data must be extracted or validated for a target language.

Related Objects

PO_HAZARD_CLASSES_TL has a direct relationship with its base table, PO_HAZARD_CLASSES_B, which stores the language-independent code and control attributes for each hazard class. It is also intrinsically linked to the main transactional tables in Purchasing that store item and shipment details, such as PO_LINES_ALL and PO_LINE_LOCATIONS_ALL, where a HAZARD_CLASS_ID may be referenced. The translation is typically accessed via application views that automatically handle the language resolution, providing a seamless interface for forms and reports. The table is maintained by standard Oracle translation utilities and seed data scripts.