Search Results po_hazard_classes




Overview
Explore in AI Chat

Overview

APPS.POBV_HAZARD_CLASSES is a read-only database view in Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2 that exposes hazard class information maintained within the Purchasing module. The view is defined with the WITH READ ONLY clause, meaning it cannot be used as a DML target for INSERT, UPDATE, or DELETE statements; it is intended strictly for query and reporting purposes.

Hazard classes are used in Oracle Purchasing to categorize items and materials according to the hazardous characteristics they carry. They are typically referenced on purchasing documents and item definitions so that shipping, handling, and regulatory information travels with the material. The POBV_HAZARD_CLASSES view presents the master list of these hazard class definitions together with their identifiers, descriptions, and audit columns. Because it is owned by the APPS schema and named with the POBV prefix (Purchasing Oracle Base View), it is designed as a stable, read-only interface that reporting tools, integrations, and custom code can rely on without touching the underlying base table directly.

Underlying Base Objects

The view is defined over a single base object: the PO_HAZARD_CLASSES table, referenced through the synonym PO_HAZARD_CLASSES in the APPS schema. The view definition is a straightforward projection of selected columns from that table, aliased as HC:

No joins, filters, or aggregation are applied in the documented view text. Consequently, POBV_HAZARD_CLASSES behaves as a one-to-one projection of PO_HAZARD_CLASSES, exposing all rows present in the base table. The only functional constraint imposed by the view is the read-only directive, which prevents modification through the view layer and thereby protects the integrity of the underlying purchasing setup data. Because the view carries no WHERE clause, callers requiring active hazard class information must apply their own filtering, typically on INACTIVE_DATE.

Key Columns

The columns exposed by the view map directly to the hazard class definition:

  • HAZARD_CLASS_ID — The system-generated primary key uniquely identifying each hazard class record. This is the value referenced by foreign keys in dependent purchasing and inventory tables.
  • HAZARD_CLASS — The short name or code of the hazard class as displayed to users and printed on documents.
  • DESCRIPTION — The descriptive text explaining the nature of the hazard class, used on forms and reports to give users additional context.
  • INACTIVE_DATE — The date on which the hazard class was disabled. A NULL value indicates an active, selectable hazard class; a populated value indicates the record is retired from active use but retained for historical reference.
  • CREATION_DATE, CREATED_BY — Standard EBS audit columns recording when and by which user the record was created (CREATED_BY stores a user ID reference).
  • LAST_UPDATE_DATE, LAST_UPDATED_BY — Standard EBS audit columns recording the most recent modification and the user responsible for it. These columns are essential for incremental or delta-based data extraction.

Common Use Cases and Queries

Typical uses include reporting on the available hazard classes for purchasing documents, validating hazard class references during data conversion or integration, and extracting hazard class values into external systems. A basic listing of active hazard classes is shown below:

SELECT hazard_class_id, hazard_class, description FROM apps.pobv_hazard_classes WHERE inactive_date IS NULL ORDER BY hazard_class;

To retrieve the full set, including retired classes for historical reporting, the filter can be omitted or replaced with a date range. For incremental extraction, the audit columns support change detection:

SELECT hazard_class_id, hazard_class, description, last_update_date, last_updated_by FROM apps.pobv_hazard_classes WHERE last_update_date >= :p_since_date;

Because the view is read-only, it is safe to grant SELECT privileges to reporting schemas and integration accounts without risk of accidental data modification. All maintenance of hazard class records must be performed through the standard Purchasing setup forms or, where permitted, directly against the PO_HAZARD_CLASSES base table by authorized processes.