Results for “max_rels_qty”

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

Overview

PO_BPOS_DTL is the blanket purchase order line table owned by the GML schema (Process Manufacturing Logistics) in Oracle EBS 12.1.1 and 12.2.2. It stores the individual line-level detail for blanket purchase orders (BPOs) created and managed within the Process Manufacturing Logistics module, which is designed for process manufacturing industries such as chemicals, pharmaceuticals, and food and beverage. Each row in this table represents a distinct blanket purchase order line, capturing the negotiated terms, quantities, pricing, receiving information, and quality specifications agreed with a supplier over a defined contract period. The table serves as the operational backbone for repetitive procurement activity: rather than creating a new standard purchase order for every replenishment, buyers define blanket agreements here, and downstream release schedules and standard purchase order lines draw against these negotiated terms.

From a Data Vault modeling perspective, the heuristic classification for PO_BPOS_DTL is satellite-leaning. This suggests the table primarily holds descriptive, descriptive-attribute content that changes over time around a business key, with its own surrogate key rather than acting purely as a hub of unique business entities or a link resolving many-to-many relationships. The presence of extensive descriptive columns plus audit columns (CREATION_DATE, LAST_UPDATE_DATE, and the standard WHO columns) reinforces this satellite characterization.

Key Information Stored

PO_BPOS_DTL contains 75 documented columns. The most significant, grouped by purpose, are:

• Identity and structure: LINE_ID is the surrogate primary key (PO_BPOS_DTL_PK). BPO_ID identifies the parent blanket purchase order and joins to PO_BPOS_HDR. LINE_NO is the line number within the BPO. Together with TO_WHSE and BPO_ID, LINE_NO forms the unique business-key index PO_BPOS_DTL_U1, distinguishing each line within a destination warehouse and order context.
• Item and classification: ITEM_ID references the inventory item master, while GENERIC_ID links to a generic item definition. ICPURCH_CLASS carries the purchasing classification, and PURCH_CATEGORY_ID provides the purchasing category.
• Quantities and pricing: CONTRACT_VALUE, CONTRACT_QTY, AMOUNT_PURCHASED, QTY_PURCHASED, STD_QTY, NET_PRICE, and MAX_RELS_QTY capture the negotiated contract value, maximum release quantity, unit price, and cumulative purchased quantities against the agreement.
• Logistics and receiving: FROM_WHSE and TO_WHSE identify source and destination warehouses; RECV_LOCT, RECVADDR_ID, and RECV_DESC describe the receiving location; SHIP_MTHD, SHIPPER_CODE, and SHIPVEND_ID specify shipping terms and the shipping vendor.
• Terms and controls: TERMS_CODE, FOB_CODE, and FRTBILL_MTHD define payment terms, FOB point, and freight billing method. BPOHOLD_CODE, CANCELLATION_CODE, and CLOSURE_CODE reference reason codes used for holds, cancellations, and closures. BPO_STATUS reflects the current lifecycle state of the line.

Common Use Cases and Queries

Typical reporting and integration scenarios include reviewing active blanket agreements, monitoring purchased-versus-contract quantities, tracking lines on hold, and feeding downstream release and receiving processes. A representative query to list active blanket lines with their vendor and item context might join PO_BPOS_DTL to PO_BPOS_HDR on BPO_ID, IC_ITEM_MST on ITEM_ID, and PO_VEND_MST on SHIPVEND_ID:

• SELECT d.LINE_ID, d.LINE_NO, d.ITEM_ID, d.CONTRACT_QTY, d.QTY_PURCHASED, d.NET_PRICE, d.BPO_STATUS FROM PO_BPOS_DTL d WHERE d.BPO_ID = :p_bpo_id ORDER BY d.LINE_NO; — retrieve all lines for a given blanket order.
• SELECT d.BPO_ID, SUM(d.AMOUNT_PURCHASED) FROM PO_BPOS_DTL d WHERE d.BPO_STATUS = 'ACTIVE' GROUP BY d.BPO_ID; — aggregate spend against active blankets.
• SELECT COUNT(*) FROM PO_BPOS_DTL WHERE BPOHOLD_CODE IS NOT NULL; — identify lines currently placed on hold.

Because PO_ORDR_DTL carries BPO_LINE_ID and PO_RELS_SCH carries BPOLINE_ID, both referencing this table, release schedules and standard purchase order lines can be traced directly back to the originating blanket line, enabling contract-compliance and consumption reporting.

Related Objects

The most significant related objects, based on documented foreign-key relationships, are:

• PO_BPOS_HDR — the parent blanket purchase order header, joined via PO_BPOS_DTL.BPO_ID.
• PO_ORDR_DTL — standard purchase order lines referencing this table through BPO_LINE_ID, linking actual orders to the blanket agreement.
• PO_RELS_SCH — release schedules referencing this table through BPOLINE_ID.
• IC_ITEM_MST / IC_ITEM_MST_B — the inventory item master, joined via ITEM_ID.
• PO_VEND_MST — the vendor master, joined via SHIPVEND_ID.
• SY_REAS_CDS / SY_REAS_CDS_B — reason code tables referenced by BPOHOLD_CODE, CANCELLATION_CODE, and CLOSURE_CODE.
• IC_WHSE_MST — the warehouse master, referenced by both FROM_WHSE and TO_WHSE.
• GMD_GRADES_B and QC_GRAD_MST — quality grade definitions referenced via QC_GRADE_WANTED.

Additional optional references include OP_TERM_MST, OP_FOBC_MST, OP_SHIP_MTH, OP_SHIP_MST, OP_FRGT_MTH, SY_UOMS_MST, OP_GNRC_ITM, SY_ADDR_MST, and PO_TEXT_HDR, covering terms, shipping, freight, units of measure, generic items, addresses, and text attachments.