PO_LINES_ALL
Schema: POtransactionOU-striped (ORG_ID)Purchasing document lines — the item, category, unit price, and ordered quantity per line across the same seven document types; shipment schedules and accounting live one and two levels down
The item column is ITEM_ID (not INVENTORY_ITEM_ID) and the table carries no inventory org — resolve the receiving org through the shipment's SHIP_TO_ORGANIZATION_ID before joining the item master, or join at the master org.
What the badges mean
- master
- Data class: what the table holds — master data, transaction documents, control/configuration, interface/staging, or an APPS-schema view.
Header & line
PO_LINES_ALL lines join back to their header PO_HEADERS_ALL — and the org column — so a line never fans out.
Fields
14 fields · 1 key
| # | Field | Description | Type | Flags |
|---|---|---|---|---|
| 1 | PO_LINE_ID | Surrogate key of the document line | NUMBER | Key |
| 2 | PO_HEADER_ID | The parent document header — unique with LINE_NUM | NUMBER | |
| 3 | ORG_ID | Operating unit | NUMBER | |
| 4 | LINE_NUM | Line number within the document | NUMBER | |
| 5 | LINE_TYPE_ID | Line type — goods vs amount-based services | NUMBER | |
| 6 | ITEM_ID | The item — this table's name for the item-master id; the org for the join comes from the shipment schedule | NUMBER | |
| 7 | ITEM_REVISION | Item revision ordered | VARCHAR2 | |
| 8 | ITEM_DESCRIPTION | Item description as it appears on the document | VARCHAR2 | |
| 9 | CATEGORY_ID | Purchasing category — the category-spend rollup key | NUMBER | |
| 10 | UNIT_MEAS_LOOKUP_CODE | Unit of measure, in its 25-character name form | VARCHAR2 | |
| 11 | QUANTITY | Total ordered quantity across the line's shipments | NUMBER | |
| 12 | UNIT_PRICE | Unit price on the line | NUMBER | |
| 13 | CLOSED_CODE | Line closure state | VARCHAR2 | |
| 14 | CANCEL_FLAG | Y when the line is cancelled | VARCHAR2 |
Field provenance: hand-curated. 1 key field.
Boilerplate SQL
Starting point for reading PO_LINES_ALLon Databricks — real DATE columns need no conversion, and the org anchor and the LAST_UPDATE_DATE watermark are already in place. Set your Unity Catalog location, schema, and org values below; they’re substituted into the SQL and the copy button.
-- ============================================================
-- Table : PO_LINES_ALL — Purchasing document lines — the item, category, unit price, and ordered quantity per line across the same seven document types; shipment schedules and accounting live one and two levels down
-- Purpose: Column-selected read of PO_LINES_ALL — auto-generated from field metadata
-- Grain : One row per operating unit (ORG_ID) + PO_LINE_ID
-- Notes : Auto-generated skeleton for Oracle EBS R12 data landed in your lakehouse. Dates are real DATE/TIMESTAMP columns — no conversion needed. WHO audit columns omitted (see the quirks guide); the optional LAST_UPDATE_DATE watermark filter supports incremental extracts.
-- ============================================================
SELECT
t.PO_LINE_ID AS "Surrogate key of the document line",
t.PO_HEADER_ID AS "The parent document header — unique with LINE_NUM",
t.ORG_ID AS "Operating unit",
t.LINE_NUM AS "Line number within the document",
t.LINE_TYPE_ID AS "Line type — goods vs amount-based services",
t.ITEM_ID AS "The item — this table's name for the item-master id; the org for the join comes from the shipment schedule",
t.ITEM_REVISION AS "Item revision ordered",
t.ITEM_DESCRIPTION AS "Item description as it appears on the document",
t.CATEGORY_ID AS "Purchasing category — the category-spend rollup key",
t.UNIT_MEAS_LOOKUP_CODE AS "Unit of measure, in its 25-character name form",
t.QUANTITY AS "Total ordered quantity across the line's shipments",
t.UNIT_PRICE AS "Unit price on the line",
t.CLOSED_CODE AS "Line closure state",
t.CANCEL_FLAG AS "Y when the line is cancelled"
FROM <catalog>.<schema>.PO_LINES_ALL t
WHERE
t.ORG_ID = <operating_unit_id> -- operating unit (MOAC does not filter extracts)
-- AND t.PO_LINE_ID = <PO_LINE_ID>
-- AND t.LAST_UPDATE_DATE >= TIMESTAMP '<watermark>' -- WHO watermark, bulk-stamped by batch jobs; see quirks guide #who-columns
ORDER BY t.PO_LINE_ID;5 parameters not filled: <catalog>, <schema>, <operating_unit_id>, <PO_LINE_ID>, <watermark>
Relationships
1-hop neighbors — click a table to navigate there. FND lookup decode and translation edges are highlighted; they’re the joins newcomers most often get wrong.
Join details
ON PO_HEADERS_ALL.PO_HEADER_ID = PO_LINES_ALL.PO_HEADER_ID AND PO_HEADERS_ALL.ORG_ID = PO_LINES_ALL.ORG_IDON PO_LINES_ALL.ITEM_ID = MTL_SYSTEM_ITEMS_B.INVENTORY_ITEM_IDON PO_LINES_ALL.CATEGORY_ID = MTL_CATEGORIES_B.CATEGORY_IDON PO_LINE_LOCATIONS_ALL.PO_LINE_ID = PO_LINES_ALL.PO_LINE_ID AND PO_LINE_LOCATIONS_ALL.ORG_ID = PO_LINES_ALL.ORG_IDON MTL_SUPPLY.PO_LINE_ID = PO_LINES_ALL.PO_LINE_IDON RCV_SHIPMENT_LINES.PO_LINE_ID = PO_LINES_ALL.PO_LINE_ID