Search Results po_bpos_dtl




Overview
Explore in AI Chat

Overview

The PO_BPOS_DTL table is a core data object within the Oracle E-Business Suite Process Manufacturing Logistics (GML) module, specifically for releases 12.1.1 and 12.2.2. It serves as the detailed repository for line-level information associated with blanket purchase orders (BPOs). A blanket purchase order is a long-term agreement with a supplier for the provision of goods or services, against which specific releases are issued. This table stores all transactional and master data attributes for each line item on a BPO, enabling the management of pricing, quantities, sourcing, shipping, and quality specifications. Its role is integral to the procure-to-pay cycle within process manufacturing environments, linking master data for items, vendors, and warehouses to the contractual terms of a blanket agreement.

Key Information Stored

The table's structure captures comprehensive line details. Its primary keys, LINE_ID and the composite key (TO_WHSE, BPO_ID, LINE_NO), ensure uniqueness. Critical columns include BPO_ID, which links to the parent header record in PO_BPOS_HDR, and LINE_NO for sequencing. Key foreign key columns define the business context: ITEM_ID links to the item master (IC_ITEM_MST_B), FROM_WHSE and TO_WHSE define the sourcing and destination warehouses (IC_WHSE_MST), and SHIPVEND_ID identifies the shipping vendor (PO_VEND_MST). The table also holds commercial terms via FOB_CODE, TERMS_CODE, and SHIP_MTHD, and quality requirements via QC_GRADE_WANTED. Status management is facilitated through columns like BPOHOLD_CODE, CANCELLATION_CODE, and CLOSURE_CODE, which reference reason codes (SY_REAS_CDS).

Common Use Cases and Queries

This table is central to operational reporting and process execution. Common use cases include generating open blanket agreement reports for procurement analysis, validating line details before creating a release (PO_RELS_SCH), and auditing price and term compliance. A typical query might join to the header and item master to list all active BPO lines for a specific item:

  • SELECT hdr.BPO_NO, dtl.LINE_NO, mst.ITEM_NO, dtl.UNIT_PRICE, dtl.QTY_ORDERED FROM GML.PO_BPOS_DTL dtl JOIN GML.PO_BPOS_HDR hdr ON dtl.BPO_ID = hdr.BPO_ID JOIN GML.IC_ITEM_MST mst ON dtl.ITEM_ID = mst.ITEM_ID WHERE mst.ITEM_NO = '&ITEM' AND dtl.CLOSURE_CODE IS NULL;

Another critical pattern involves tracing releases (PO_ORDR_DTL) back to their source blanket line using the BPO_LINE_ID foreign key to analyze commitment versus actual consumption.

Related Objects

PO_BPOS_DTL maintains extensive relationships with master and transactional tables, as documented by its foreign keys. The primary relationship is with its header table, PO_BPOS_HDR, via BPO_ID. It is the source for downstream procurement transactions, referenced by PO_RELS_SCH (schedule releases) via BPOLINE_ID and by PO_ORDR_DTL (order detail lines) via BPO_LINE_ID. Key master data references include:

  • IC_ITEM_MST_B / IC_ITEM_MST (Item): ITEM_ID
  • IC_WHSE_MST (Warehouse): FROM_WHSE, TO_WHSE
  • PO_VEND_MST (Vendor): SHIPVEND_ID
  • SY_REAS_CDS / SY_REAS_CDS_B (Reason Codes): BPOHOLD_CODE, CANCELLATION_CODE, CLOSURE_CODE
  • OP_TERM_MST (Terms): TERMS_CODE
  • OP_SHIP_MTH (Ship Method): SHIP_MTHD
  • GMD_GRADES_B / QC_GRAD_MST (Quality Grade): QC_GRADE_WANTED

These relationships enforce data integrity and define the table's central position in the blanket purchasing data model.