Search Results po_headers_pk

Overview

PO_HEADERS_ALL is the master header table of the Oracle Purchasing (PO) module, residing in the PO schema. It stores the top-level document records for every purchasing document type managed by the application, including standard purchase orders, blanket and contract purchase agreements, quotations, and requests for quotation (RFQs). Each row represents a single document header, carrying the supplier, terms, currency, approval, and status information that governs the associated lines and shipments. The table is one of the foundational objects of the EBS procurement and supply chain data model, and it is referenced throughout Oracle Purchasing, Payables, Receiving, Projects, and Inventory.

From a dimensional modeling perspective, the ETRM metadata classifies PO_HEADERS_ALL heuristically as a hub in a Data Vault construction. This reflects its role as a central business entity that other structures reference: the document header acts as the anchor point, with descriptive attributes behaving satellite-like and transactional links (lines, distributions, receipts, invoices) attaching to the hub through the PO_HEADER_ID business key. This classification should be treated as a modeling suggestion rather than a physically enforced construct.

Key Information Stored

The table contains 202 documented columns. Among the most significant are:

• PO_HEADER_ID — the surrogate primary key defined by index PO_HEADERS_PK, and the sole column of unique index PO_HEADERS_U1. It is the numeric identifier used by nearly every dependent table.
• SEGMENT1 — the visible document number. Together with TYPE_LOOKUP_CODE and ORG_ID it forms the business-key candidate PO_HEADERS_U2, distinguishing a document number within a document type and operating unit. Additional SEGMENT2 through SEGMENT5 support document numbering schemes.
• TYPE_LOOKUP_CODE — identifies the document class (standard PO, blanket, contract, quotation, RFQ).
• ORG_ID — the operating unit that owns the document, enabling multi-org security.
• VENDOR_ID, VENDOR_SITE_ID, VENDOR_CONTACT_ID — foreign keys to the supplier, supplier site, and contact.
• AGENT_ID — the buyer responsible for the document, referencing PO_AGENTS.
• CURRENCY_CODE and RATE_TYPE — currency and the GL daily conversion rate type applied.
• AUTHORIZATION_STATUS, APPROVED_FLAG, and APPROVED_DATE — approval and document lifecycle state.
• STATUS_LOOKUP_CODE and CLOSED_CODE — current processing and closure status.
• TERMS_ID, SHIP_VIA_LOOKUP_CODE, FOB_LOOKUP_CODE, FREIGHT_TERMS_LOOKUP_CODE — commercial terms.
• SHIP_TO_LOCATION_ID and BILL_TO_LOCATION_ID — ship-to and bill-to locations from HR_LOCATIONS_ALL.
• FROM_HEADER_ID — self-referencing key linking releases, quotations, and other derived documents to their source document.
• BLANKET_TOTAL_AMOUNT, AMOUNT_LIMIT, and MIN_RELEASE_AMOUNT — agreement financial controls.

Common Use Cases and Queries

PO_HEADERS_ALL is queried for procurement reporting, document lookups, and supplier spend analysis. A common pattern retrieves active standard purchase orders for a supplier:

• SELECT pha.segment1, pha.type_lookup_code, pha.authorization_status, pha.currency_code FROM po_headers_all pha WHERE pha.vendor_id = :vendor_id AND pha.org_id = :org_id AND pha.type_lookup_code = 'STANDARD'
• Reconciling agreements to releases by joining a release back to its source through the FROM_HEADER_ID self-reference.
• Building spend and commitment reports by aggregating PO_LINES_ALL and PO_LINE_LOCATIONS_ALL under each header.
• Tracing matched invoices in Payables via AP_INVOICES_ALL.PO_HEADER_ID through to receiving shortage by joining RCV_SHIPMENT_LINES and RCV_TRANSACTIONS.
• Document approval and workflow reporting using AUTHORIZATION_STATUS, APPROVED_FLAG, and WF_ITEM_TYPE/WF_ITEM_KEY.

Reports frequently join PO_HEADERS_ALL to PO_VENDORS, PO_VENDOR_SITES_ALL, and HR_LOCATIONS_ALL to produce human-readable supplier and location descriptions. Multi-org queries should always filter by ORG_ID.

Related Objects

The following are the most significant dependent and referenced objects:

• PO_LINES_ALL — joins on PO_HEADER_ID (and FROM_HEADER_ID), holding document lines.
• PO_LINE_LOCATIONS_ALL — shipment and distribution scheduling, joined by PO_HEADER_ID.
• PO_DISTRIBUTIONS_ALL — accounting distributions referencing PO_HEADER_ID.
• PO_RELEASES_ALL — releases against blanket agreements, joined by PO_HEADER_ID.
• AP_INVOICES_ALL — matched invoices referencing PO_HEADER_ID.
• RCV_SHIPMENT_LINES and RCV_TRANSACTIONS — receiving activity linked through PO_HEADER_ID.
• PO_VENDORS, PO_VENDOR_SITES_ALL, PO_VENDOR_CONTACTS, and PO_AGENTS — the supplier and buyer master data referenced through foreign keys VENDOR_ID, VENDOR_SITE_ID, VENDOR_CONTACT_ID, and AGENT_ID.
• HR_LOCATIONS_ALL — supplies SHIP_TO_LOCATION_ID and BILL_TO_LOCATION_ID.
• FND_CURRENCIES and GL_DAILY_CONVERSION_TYPES — referenced via CURRENCY_CODE and RATE_TYPE.
• MTL_SUPPLY and OE_DROP_SHIP_SOURCES — supply and drop-ship planning references through PO_HEADER_ID.

The PO_HEADERS_ALL.ORG_ID and document key columns also drive the _ALL synonym conventions that resolve to organization-secured views in a multi-org environment.