Search Results PO_HEADERS_ALL

Overview

The PO_HEADERS_ALL table is the central repository for header-level information of all purchasing documents within Oracle E-Business Suite Purchasing (PO) module. It serves as the master record for purchase orders, purchase agreements, quotations, and requests for quotation (RFQs). As a multi-organization table, denoted by the "_ALL" suffix, it stores data for all operating units, with access typically controlled by the MOAC (Multi-Org Access Control) security profile. Its primary role is to define the overarching contractual and business terms for a procurement transaction, which are then detailed in associated line and shipment tables.

Key Information Stored

The table's structure captures the essential attributes of a purchasing document header. The primary key is PO_HEADER_ID, a unique system-generated identifier. A significant business key is SEGMENT1, which stores the human-readable document number. Critical foreign key relationships define the business context: VENDOR_ID and VENDOR_SITE_ID link to the supplier and their site; AGENT_ID identifies the buyer; SHIP_TO_LOCATION_ID and BILL_TO_LOCATION_ID define delivery and invoicing addresses. Other vital columns include TYPE_LOOKUP_CODE to distinguish between document types (e.g., STANDARD PO, BLANKET AGREEMENT), CURRENCY_CODE, RATE_TYPE for currency conversion, AUTHORIZATION_STATUS to track approval workflow, and CREATION_DATE. The FROM_HEADER_ID column supports document copying and blanket agreement releases by referencing the source agreement.

Common Use Cases and Queries

This table is fundamental for procurement reporting, data validation, and integration. Common scenarios include tracking the status of documents across operating units, analyzing buyer and supplier activity, and validating document integrity. A typical query to retrieve standard purchase orders for a specific vendor would join to related supplier and lookup tables.

• Sample Query: SELECT pha.segment1 AS po_number, pha.type_lookup_code, pha.authorization_status, pv.vendor_name, pvsa.vendor_site_code FROM po_headers_all pha JOIN po_vendors pv ON pha.vendor_id = pv.vendor_id JOIN po_vendor_sites_all pvsa ON pha.vendor_site_id = pvsa.vendor_site_id WHERE pha.type_lookup_code = 'STANDARD' AND pv.vendor_name LIKE 'ACME%';
• Reporting Use Case: Generating a report of all purchase agreements (BLANKET or CONTRACT) that are currently active, including their effective date ranges and total agreement amounts, often requires filtering on TYPE_LOOKUP_CODE and START_DATE/END_DATE columns.
• Data Validation: Identifying documents where header-level data (like currency) conflicts with line-level data by joining to PO_LINES_ALL.

Related Objects

PO_HEADERS_ALL has extensive relationships within and beyond the Purchasing module, as evidenced by its foreign key constraints. Core related Purchasing tables include PO_LINES_ALL (for document lines), PO_DISTRIBUTIONS_ALL (for accounting distributions), and PO_VENDORS. Crucially, it is referenced by AP_INVOICES_ALL for invoice matching and payment processing. Other significant dependencies include AHL_OSP_ORDERS_B (for service procurement), IGC_CC_HEADERS (for budgetary control), and various JAI (Java APIs for India) tables for localized tax and excise functionality. The table is also the base for key views like PO_HEADERS (a single-organization view filtered by ORG_ID).