Results for “bpo_release_no”

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

Overview

PO_ORDR_HDR is the purchase order header table within the GML (Process Manufacturing Logistics) schema of Oracle E-Business Suite. It stores the master-level attributes of a purchase order — vendor, organization, dates, status, currency, shipment and receiving defaults — while line-level detail is held in PO_ORDR_DTL. This table is specific to the Oracle Process Manufacturing (OPM) purchasing flow and is distinct from the discrete-manufacturing PO_HEADERS_ALL table; it belongs to the process-industry purchasing model that integrates with inventory, receiving, and returns.

Under a heuristic Data Vault classification derived from its foreign-key structure, PO_ORDR_HDR is satellite-leaning: it holds a stable business key plus a wide set of descriptive and status attributes that change over the document lifecycle, and it is referenced by many dependent tables. Practically, it functions as the parent record for a single purchase order document.

Key Information Stored

The table is documented with 80 columns. The surrogate primary key is PO_ID, enforced by index PO_ORDR_HDR_PK. A second unique index, PO_ORDR_HDR_U1, defines the business-key candidate (ORGN_CODE, PO_NO), meaning a purchase order number is unique only within a given organization. The most operationally significant columns include:

• PO_ID — surrogate primary key and the join key used throughout the OPM purchasing schema.
• ORGN_CODE — the organization that owns the order; part of the business-key candidate.
• PO_NO — the user-visible purchase order number; part of the business-key candidate.
• PO_TYPE — classifies the order (for example, standard versus blanket release).
• PO_STATUS — current document status, driving most operational reporting.
• PAYVEND_ID / SHIPVEND_ID — the paying and shipping vendors (both reference PO_VEND_MST).
• BPO_ID / BPO_RELEASE_NO — links a release back to its blanket purchase order in PO_BPOS_HDR.
• PO_DATE, REQUIRED_DLVDATE, AGREED_DLVDATE, REQUESTED_DLVDATE — the core scheduling and commitment dates.
• BILLING_CURRENCY, PURCHASE_EXCHANGE_RATE, MUL_DIV_SIGN — currency and conversion information.
• TERMS_CODE, FOB_CODE, SHIP_MTHD, SHIPPER_CODE, FRTBILL_MTHD — commercial and logistics terms.
• FROM_WHSE / TO_WHSE — source and destination warehouses for inter-organization transfers.
• POHOLD_CODE / CANCELLATION_CODE — hold and cancellation reason codes from SY_REAS_CDS.
• RECVADDR_ID, RECV_DESC, RECV_LOCT — delivery address and receiving location details.
• TEXT_CODE — reference to header-level boilerplate text in PO_TEXT_HDR.

Common Use Cases and Queries

PO_ORDR_HDR is the entry point for purchase order reporting in OPM environments: open-order aging, spend by vendor or organization, blanket release tracking, and delivery-date compliance. A typical query joining the header to its detail lines is:

SELECT h.po_no, h.orgn_code, h.po_status, h.po_date,
       h.required_dlvdate, d.line_no, d.item_no
FROM   po_ordr_hdr h, po_ordr_dtl d
WHERE  h.po_id = d.po_id
AND    h.orgn_code = :orgn
AND    h.po_status IN ('O','C');

Vendor-centric reporting joins PO_VEND_MST on PAYVEND_ID to resolve vendor names, while blanket-release analysis joins PO_BPOS_HDR on BPO_ID. Receiving and returns reconciliation joins PO_RECV_DTL and PO_RTRN_DTL on PO_ID. Because ORGN_CODE and PO_NO form the unique business key, lookups by document number should always be qualified by organization.

Related Objects

• PO_ORDR_DTL — purchase order lines, joined on PO_ID.
• PO_RECV_DTL and PO_RTRN_DTL — receiving and return transactions referencing PO_ID.
• PO_VEND_MST — vendor master, joined on PAYVEND_ID and SHIPVEND_ID.
• PO_BPOS_HDR — blanket purchase orders, joined on BPO_ID.
• PO_TEXT_HDR — header text, joined on TEXT_CODE.
• SY_ORGN_MST — organization master, joined on ORGN_CODE.
• SY_REAS_CDS — reason codes for holds and cancellations.
• CPG_PURCHASING_INTERFACE — external purchasing integration, referencing PO_ID.
• GML_PO_MIG_ERRORS — migration error tracking against PO_ID.