Results for “po_hazard_classes_b”

50+ results




AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

PO_HAZARD_CLASSES_B is a Purchasing (PO) module reference table that stores hazardous material classification definitions used across Oracle E-Business Suite 12.1.1 and 12.2.2. Each row represents a distinct hazard class that can be assigned to inventory items, purchase order lines, requisition lines, and shipping or delivery records, allowing organizations to identify, track, and report on regulated or dangerous goods throughout the procure-to-pay and order fulfillment lifecycle.

The table resides in the PO schema and is classified as VALID in ETRM. Under the heuristic Data Vault classification supplied in the metadata, PO_HAZARD_CLASSES_B is described as hub-leaning. In Data Vault modeling terms, this suggests treating the table as a hub: HAZARD_CLASS_ID serves as the durable business key around which descriptive attributes and downstream associations (links) are organized. This classification is a modeling suggestion rather than an implemented constraint, but it accurately reflects the table's role as a stable reference point referenced by many transactional and interface tables.

Key Information Stored

PO_HAZARD_CLASSES_B contains 27 documented columns. The most significant are summarized below.

  • HAZARD_CLASS_ID — The surrogate primary key, enforced by PO_HAZARD_CLASSES_B_PK. It is also the single column of the unique index PO_HAZARD_CLASSES_U1, making it the principal business-key candidate for joining to dependent tables.
  • INACTIVE_DATE — The date on which a hazard class becomes inactive and should no longer be assigned to new items or lines; used to filter active reference data.
  • CREATION_DATE, CREATED_BY — Standard audit columns recording when and by whom the hazard class record was created.
  • LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — Standard audit columns capturing the most recent modification and the login context of the change.
  • ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15 — The flexible descriptive flexfield (DFF) columns, enabling customers to store organization-specific hazard attributes without schema changes.
  • REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE — Concurrent program context columns identifying the request and program that last inserted or updated the row, supporting traceability of batch loads.

The surrogate key HAZARD_CLASS_ID is the only documented unique identifier; no separate human-readable code column appears in the documented metadata, so integrations typically resolve hazard classes by ID.

Common Use Cases and Queries

Typical scenarios include validating hazard class assignments on purchase orders, auditing which items are flagged as hazardous, and populating shipping documentation for regulated goods.

To retrieve active hazard classes with their flexible attributes:

  • SELECT hazard_class_id, inactive_date, attribute_category, attribute1 FROM po.po_hazard_classes_b WHERE inactive_date IS NULL OR inactive_date > SYSDATE;

To count purchase order lines per hazard class:

  • SELECT h.hazard_class_id, COUNT(l.po_line_id) FROM po.po_hazard_classes_b h JOIN po.po_lines_all l ON l.hazard_class_id = h.hazard_class_id GROUP BY h.hazard_class_id;

Because most consumer tables carry HAZARD_CLASS_ID, the join predicate is consistently on that column. Reporting use cases include hazardous materials registers for compliance, item master audits joining MTL_SYSTEM_ITEMS_B, and reconciliation of interface loads in PO_LINES_INTERFACE.

Related Objects

PO_HAZARD_CLASSES_B is referenced through HAZARD_CLASS_ID by numerous dependent tables. The most significant include:

Master data quality in PO_HAZARD_CLASSES_B directly affects item setup, procurement, and shipping compliance across these dependent objects.