Search Results po_ordr_hdr




Overview
Explore in AI Chat

Overview

The PO_ORDR_HDR table is the central repository for purchase order header information within the Process Manufacturing Logistics (GML) module of Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2. It serves as the master record for a purchase order, capturing high-level transactional metadata that governs the entire procurement lifecycle. As a core table in the GML schema, it is integral to managing procurement for process manufacturing environments, which often have specialized requirements for material tracking, lot control, and compliance. The table's structure, defined by its primary and foreign keys, establishes critical relationships with vendors, organizations, warehouses, payment terms, and other foundational master data, ensuring data integrity and supporting complex business processes.

Key Information Stored

The table's primary identifier is the PO_ID column, which is the primary key for the PO_ORDR_HDR_PK constraint. A unique key constraint (PO_ORDR_HDR_U1) also enforces uniqueness on the combination of ORGN_CODE (operating unit) and PO_NO (purchase order number). Beyond these identifiers, the table stores comprehensive header-level attributes that define the purchase order's business context. Key foreign key columns link to essential reference data: ORGN_CODE to the organization (SY_ORGN_MST), SHIPVEND_ID and PAYVEND_ID to the vendor (PO_VEND_MST), and FROM_WHSE/TO_WHSE to warehouses (IC_WHSE_MST). Other critical columns manage financial and logistical details, such as BILLING_CURRENCY (linked to GL_CURR_MST), TERMS_CODE (OP_TERM_MST), FOB_CODE (OP_FOBC_MST), SHIP_MTHD (OP_SHIP_MTH), and FRTBILL_MTHD (OP_FRGT_MTH). Status management is facilitated through columns like POHOLD_CODE and CANCELLATION_CODE, which reference reason codes (SY_REAS_CDS).

Common Use Cases and Queries

This table is fundamental for procurement reporting, order tracking, and integration workflows. Common operational queries involve joining PO_ORDR_HDR with its detail lines (PO_ORDR_DTL) and related master tables to generate comprehensive purchase order reports. For instance, a report to list all open purchase orders for a specific vendor and organization would typically join PO_ORDR_HDR to PO_VEND_MST and PO_ORDR_DTL. Another critical use case is validating order status during goods receipt (PO_RECV_DTL) or return (PO_RTRN_DTL) processing, where the system must confirm the PO_ID is valid and active. Technical consultants often query this table to troubleshoot data issues, analyze procurement cycles, or extract data for custom interfaces. A sample query pattern is:

SELECT h.po_no, h.orgn_code, v.vendor_name, h.creation_date
FROM gml.po_ordr_hdr h,
     gml.po_vend_mst v
WHERE h.shipvend_id = v.vendor_id
AND h.orgn_code = 'M1'
AND h.pohold_code IS NULL;

Related Objects

PO_ORDR_HDR is a pivotal table with extensive relationships. Its primary child tables are PO_ORDR_DTL (purchase order lines), PO_RECV_DTL (receipt details), and PO_RTRN_DTL (return details), all linked via the PO_ID column. As indicated by its foreign keys, it depends on numerous master data tables for validation, including SY_ORGN_MST (organization), PO_VEND_MST (vendor), IC_WHSE_MST (warehouse), GL_CURR_MST (currency), and various setup tables for terms, shipping, and FOB. It also references PO_BPOS_HDR (blanket purchase agreements) via BPO_ID and PO_TEXT_HDR via TEXT_CODE for standard notes. These relationships underscore its role as a hub connecting procurement execution to foundational enterprise data.