Search Results po_hazard_classes_vl




Overview

The PO_HAZARD_CLASSES_VL view is a public, language-enabled (VL) reporting and integration object owned by the APPS schema within the Oracle E-Business Suite Purchasing (PO) module. It exposes the hazard class definitions maintained by an enterprise for use on purchased items, receiving transactions, and inventory records where regulatory or safety classification is required. Because it is a VL view, it joins the base transaction table to its translation table and filters rows to the session language using USERENV('LANG'), returning a single localized row per hazard class. This design shields consuming forms, reports, concurrent programs, and external interfaces from having to resolve language independently, while still exposing the full set of descriptive flexfield and audit columns defined on the underlying base entity.

Underlying Base Objects

Per the documented ETRM 12.2.2 metadata, the view is defined over two synonyms: PO_HAZARD_CLASSES_B (the base table holding language-independent attributes such as the primary key, inactive date, audit fields, descriptive flexfield segments, and concurrent program context) and PO_HAZARD_CLASSES_TL (the translation table holding the language-dependent hazard class name and description). The view text selects all columns from the base table (aliased B) and the HAZARD_CLASS and DESCRIPTION columns from the translation table (aliased T), joined on HAZARD_CLASS_ID, with the language predicate restricting results to the current session language. This structure is the standard Oracle EBS multi-language pattern and is consistent across 12.1.1 and 12.2.2.

Key Columns

  • ROW_ID – The ROWID of the underlying base table row, used by Oracle Forms for row-level locking.
  • HAZARD_CLASS_ID – Primary key and foreign key linking the base and translation tables; also referenced by item, shipping, and inventory entities that consume hazard classifications.
  • HAZARD_CLASS – The language-specific hazard class code or name (from the TL table).
  • DESCRIPTION – The translated description of the hazard class.
  • INACTIVE_DATE – Indicates when the hazard class was end-dated and should no longer be selected for new transactions.
  • Audit and concurrency columnsCREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE.
  • ATTRIBUTE_CATEGORY and ATTRIBUTE1–15 – Descriptive flexfield segments available for customer extension.

Common Use Cases and Queries

Typical usage includes hazard class validation during item or purchase order entry, populating LOVs, and generating regulatory reports. The example below returns only active hazard classes for the current session language:

  • SELECT HAZARD_CLASS_ID, HAZARD_CLASS, DESCRIPTION FROM PO_HAZARD_CLASSES_VL WHERE INACTIVE_DATE IS NULL ORDER BY HAZARD_CLASS;
  • Joining to item or purchase order tables to include hazard class on integration extracts.
  • Reporting on end-dated classifications for audit or compliance reviews.