Results for “closure_code”

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

Overview

PO_BPOS_HDR is the header table for blanket purchase orders (BPOs) within the Process Manufacturing Logistics module (GML) of Oracle E-Business Suite. It stores the master-level attributes of a blanket purchase agreement — the negotiated contract instrument that establishes agreed pricing, terms, and delivery conditions with a supplier over a defined validity period — against which subsequent releases and standard purchase orders are authorized. In EBS 12.1.1 and 12.2.2 the table resides in the GML schema and is documented as VALID with 74 physical columns. Each row represents a single blanket purchase order header, uniquely identified within an operating unit by the combination of organization code and BPO number.

From a dimensional modeling perspective, the mined foreign-key structure suggests a satellite-leaning classification. The table carries a distinct surrogate primary key, its business key is documented through a dedicated unique index, and it is referenced by multiple dependent tables spanning transactional, interface, and archival contexts, which is characteristic of an entity that records descriptive state around a stable business key rather than acting as a pure hub or link.

Key Information Stored

The surrogate primary key is BPO_ID, defined by constraint PO_BPOS_HDR_PK. The business-key candidate is documented as PO_BPOS_HDR_U1, a composite unique index on ORGN_CODE and BPO_NO, guaranteeing that blanket purchase order numbers are unique within an operating unit.

• BPO_ID — surrogate primary key and the join column used by all dependent tables.
• ORGN_CODE — operating unit owning the blanket order; part of the unique business key.
• BPO_NO — the user-visible blanket purchase order number; part of the unique business key.
• BPO_STATUS — lifecycle state of the agreement (for example active, on hold, closed, or cancelled).
• PAYVEND_ID and SHIPVEND_ID — pay-to and ship-from supplier identifiers referencing PO_VEND_MST.
• CONTRACT_NO, CONTRACT_VALUE, CONTRACT_CURRENCY, and CONTRACT_EXCHANGE_RATE — the negotiated agreement reference, ceiling value, currency, and conversion rate.
• AMOUNT_PURCHASED — cumulative value released against the agreement, the primary measure for tracking consumption against CONTRACT_VALUE.
• CONTRACT_START_DATE and CONTRACT_END_DATE — validity window of the agreement.
• BPOHOLD_CODE, CANCELLATION_CODE, and CLOSURE_CODE — reason codes referencing SY_REAS_CDS governing hold, cancellation, and closure.
• REL_COUNT and PRINT_COUNT — release count and document print count for the header.
• REVISION_COUNT, CREATION_DATE, LAST_UPDATE_DATE, CREATED_BY, and LAST_UPDATED_BY — standard concurrency and audit columns.

Common Use Cases and Queries

Typical usage centers on agreement consumption reporting, expiry monitoring, and release auditing. The following pattern lists active agreements with their remaining balance.

• Consumption analysis: SELECT bpo_no, orgn_code, contract_value, amount_purchased, contract_value - amount_purchased remaining FROM po_bpos_hdr WHERE bpo_status = 'ACTIVE';
• Expiry monitoring: filter on CONTRACT_END_DATE within the next 30 days for procurement renewal alerts.
• Release activity: aggregate PO_BPOS_DTL or PO_ORDR_HDR rows joined on BPO_ID and compare against REL_COUNT.
• Supplier spend by agreement: join PAYVEND_ID to PO_VEND_MST to roll up committed value by vendor.
• Hold and closure audit: join BPOHOLD_CODE, CANCELLATION_CODE, and CLOSURE_CODE to SY_REAS_CDS for reason descriptions.
• Interface reconciliation: compare staged rows in CPG_PURCHASING_INTERFACE against PO_BPOS_HDR on BPO_ID to detect unprocessed agreements.

Related Objects

• PO_BPOS_DTL — detail line items of the blanket order; joins on BPO_ID.
• PO_ORDR_HDR — standard purchase orders released against the agreement; joins on BPO_ID.
• PO_VEND_MST — supplier master referenced by PAYVEND_ID and SHIPVEND_ID.
• SY_ORGN_MST / SY_ORGN_MST_B — operating unit definitions referenced by ORGN_CODE.
• GL_CURR_MST — currency definitions referenced by CONTRACT_CURRENCY.
• SY_REAS_CDS / SY_REAS_CDS_B — reason code lookups for hold, cancellation, and closure.
• OP_TERM_MST, OP_SHIP_MTH, OP_FOBC_MST, OP_SHIP_MST, and OP_FRGT_MTH — terms, shipment, FOB, shipper, and freight method masters referenced by the corresponding header columns.
• CPG_PURCHASING_INTERFACE and CPG_ORAGEMS_MAPPING — interface and mapping tables that depend on BPO_ID.
• PO_BPOS_HDR_EFC and the CPG archival tables — dependent tables sharing the BPO_ID key.