Results for “recv_desc”

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

Overview

PO_ORDR_DTL is a transactional table in the GML (Process Manufacturing Logistics) schema of Oracle E-Business Suite, holding purchase order line records. It stores the line-level detail associated with purchase order headers, as opposed to header-level information held in PO_ORDR_HDR. The table is schema-owned by GML and is documented as VALID in ETRM for both the 12.1.1 and 12.2.2 releases.

From a modeling perspective, PO_ORDR_DTL is the operational system-of-record for purchase order lines within the Process Manufacturing Logistics product set. It is a core dependency for downstream receiving, scheduling, returns, and purchasing documentation processes. The heuristic Data Vault classification mined from its foreign key structure is satellite-leaning, suggesting the table primarily carries descriptive attributes rather than serving as an independent hub or link. In practice, PO_ID links each line back to its purchase order header, and LINE_ID provides the unique surrogate identifier.

Key Information Stored

The primary key of PO_ORDR_DTL is LINE_ID, which uniquely identifies each purchase order line. A second unique index, PO_ORDR_DTL_U1, is defined on (PO_ID, LINE_NO), making the combination of purchase order identifier and line number the business-key candidate used to locate a specific line within an order.

Among the 83 documented columns, the most operationally significant include:

• PO_ID — foreign key to PO_ORDR_HDR, linking the line to its parent purchase order.
• LINE_NO — the line number within the purchase order; forms half of the business key.
• ITEM_ID — the inventory item being purchased, referencing IC_ITEM_MST / IC_ITEM_MST_B.
• GENERIC_ID — reference to OP_GNRC_ITM, identifying a generic item.
• ORDER_QTY1 / ORDER_QTY2 — ordered quantities in the primary and secondary units of measure.
• ORDER_UM1 / ORDER_UM2 / PRICE_UM — units of measure for ordering and pricing, each referencing SY_UOMS_MST.
• RECEIVED_QTY1 / RECEIVED_QTY2 — cumulative received quantities against the line.
• NET_PRICE / EXTENDED_PRICE — unit and extended pricing values for the purchase line.
• FROM_WHSE / TO_WHSE — source and destination warehouses, referencing IC_WHSE_MST.
• PO_STATUS — the lifecycle state of the line.
• AGREED_DLVDATE / REQUESTED_DLVDATE / REQUIRED_DLVDATE — delivery date commitments used in scheduling and expediting.
• TERMS_CODE — payment terms, referencing OP_TERM_MST.
• POHOLD_CODE / CANCELLATION_CODE — reason codes (SY_REAS_CDS_B / SY_REAS_CDS) indicating holds or cancellations.
• BPO_LINE_ID — link to a blanket purchase order line in PO_BPOS_DTL.
• SHIPVEND_ID — the ship-to vendor, referencing PO_VEND_MST.

Standard audit columns (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN) and a wide ATTRIBUTE1–ATTRIBUTE30 / ATTRIBUTE_CATEGORY set support descriptive flexibility. TRANS_CNT and EXPORTED_DATE typically support integration and export processes.

Common Use Cases and Queries

Typical usage centers on line-level purchasing analytics, receipt reconciliation, and open-line reporting. Because the table is the parent of PO_RECV_DTL, PO_RELS_SCH, and PO_RTRN_DTL, a common query joins those tables back on POLINE_ID to reconcile ordered quantities against received and returned quantities.

• Open purchase order lines: select lines where ORDER_QTY1 exceeds RECEIVED_QTY1 and PO_STATUS is open.
• Receipt reconciliation: join PO_ORDR_DTL to PO_RECV_DTL on POLINE_ID to compare ordered versus received quantities.
• Delivery date exception reporting: flag lines where REQUIRED_DLVDATE is past due.
• Hold and cancellation analysis: aggregate by POHOLD_CODE or CANCELLATION_CODE.
• Spend analysis: sum EXTENDED_PRICE by ITEM_ID, buyer, or purchase category.

A representative pattern joins the header for context: SELECT l.LINE_ID, l.PO_ID, l.LINE_NO, l.ITEM_ID, l.ORDER_QTY1, l.RECEIVED_QTY1 FROM GML.PO_ORDR_DTL l WHERE l.PO_ID = :po_id, optionally joined to PO_ORDR_HDR on PO_ID and to PO_RECV_DTL on POLINE_ID for full lifecycle visibility.

Related Objects

PO_ORDR_DTL sits between the purchase order header and a cluster of downstream transactional tables. The most significant related objects are:

• PO_ORDR_HDR — parent header; joined on PO_ID.
• PO_RECV_DTL — receipt lines; references PO_ORDR_DTL via POLINE_ID.
• PO_RELS_SCH — release schedules; references PO_ORDR_DTL via POLINE_ID.
• PO_RTRN_DTL — return lines; references PO_ORDR_DTL via POLINE_ID.
• PO_BPOS_DTL — blanket purchase order lines; joined via BPO_LINE_ID.
• IC_ITEM_MST / IC_ITEM_MST_B — item master; joined on ITEM_ID.
• PO_VEND_MST — vendor master; joined on SHIPVEND_ID for ship-to vendor.
• SY_UOMS_MST — unit of measure master; joined on ORDER_UM1, ORDER_UM2, and PRICE_UM.
• IC_WHSE_MST — warehouse master; joined on FROM_WHSE and TO_WHSE.
• PO_TEXT_HDR / SY_REAS_CDS — text and reason code references used for notes, holds, and cancellations.