Skip to content
Fusion Reference

PO_LINES_ALL

Product: POtransactionBU-striped (PRC_BU_ID)

Purchasing document lines — the item, category, unit price, and ordered quantity per line; the line quantity is the rollup of its schedules one level down

Notes

The item column is ITEM_ID and the table carries no inventory org — resolve the receiving org through the schedule's SHIP_TO_ORGANIZATION_ID before joining the item master. AMOUNT is populated only for service-type lines (goods use QUANTITY × UNIT_PRICE); agreement lineage rides FROM_HEADER_ID / FROM_LINE_ID.

What the badges mean
Product: EGP
Product: the Oracle product family that owns the object — the short code Oracle's Tables and Views documentation lists as the object owner. Fusion is SaaS, so this isn't a database schema; there's no SQL path to the tables at all (see the quirks guide).
master
Data class: what the table holds — master data, transaction documents, control/configuration, interface/staging, or a documented view.

Structural facts — how the table is partitioned, not a trap by itself

BU-striped (ORG_ID)
Rows are scoped to a business unit. The column is still named ORG_ID, but in Fusion it means business unit, not the EBS operating unit — treat any migrated “operating unit” filter as suspect (see the quirks guide).
Per inventory org
Rows are scoped to an inventory organization via ORGANIZATION_ID — always pair it with INVENTORY_ITEM_ID on item-level joins (see the quirks guide).
Set / ledger / named-BU striped
Some tables stripe by a named column instead of ORG_ID: reference data set (SET_ID — see the quirks guide), ledger (LEDGER_ID on the GL journal tables), or a named business-unit column (PRC_BU_ID / REQ_BU_ID in procurement). The table page’s partition line names the column, and the generated SQL anchors on it — never treat these tables as unpartitioned.
Language-striped
The table carries a LANGUAGE column (a _TL translation table or FND_LOOKUP_VALUES) — one row per language. Filter to one LANGUAGE or a join multiplies rows.

Join & extract hazards — verify before you rely on this

Date-effective
This is an _F table — one row per entity per effectivity window, with EFFECTIVE_START_DATE and EFFECTIVE_END_DATE part of the key. Join without a window filter and every fact multiplies by history (see the quirks guide).
View
This is a documented convenience view, not a physical table. Extract through the BICC data store that fronts its base objects instead of assuming the view lands as-is.
In field listings, the Key chip marks a key field — a member of the documented primary key or of a documented unique index.

Header & line

PO_LINES_ALL lines join back to their header PO_HEADERS_ALL — and the org column — so a line never fans out.

Extract access

The delivered surfaces that reach this table — the BICC extract data store (PVO) for bulk extraction and the OTBI subject areas for real-time queries. There is no SQL path to the SaaS database.

  • FscmTopModelAM.PrcExtractAM.PoBiccExtractAM.PurchasingDocumentLineExtractPVO
    OTBI: Procurement - Purchasing Real TimeOTBI: Procurement - Procure To Pay Real Time

    Purchasing Document Lines data store — keyed on PoLineId; also carries agreement lines.

    Oracle data-store documentation (opens in new tab)

Fields

18 fields · 1 key

18 fields.

Table fields: position, field name, description, data type, and flags. 18 fields.
#FieldDescriptionTypeFlags
1PO_LINE_IDSurrogate key of the lineNUMBER
Key
2PO_HEADER_IDParent purchasing document headerNUMBER
3LINE_NUMVisible line numberNUMBER
4ITEM_IDItem on the line — no inventory org here; resolve it through the schedule's ship-to orgNUMBER
5ITEM_REVISIONItem revisionVARCHAR2
6ITEM_DESCRIPTIONLine item descriptionVARCHAR2
7CATEGORY_IDPurchasing categoryNUMBER
8QUANTITYOrdered quantity — the rollup of the line's schedulesNUMBER
9UNIT_PRICEPrice per unit in document currencyNUMBER
10AMOUNTBudget amount — populated only for service-type linesNUMBER
11UOM_CODEUnit of measureVARCHAR2
12LINE_TYPE_IDGoods vs services line typeNUMBER
13LINE_STATUSLine statusVARCHAR2
14CLOSED_DATEWhen the line was closedDATE
15CANCEL_FLAGY when the line is cancelledVARCHAR2
16FROM_HEADER_IDSource agreement/quotation header the line referencesNUMBER
17FROM_LINE_IDSource agreement/quotation lineNUMBER
18PRC_BU_IDProcurement BU stripe, denormalized from the headerNUMBER

Field provenance: hand-curated. 1 key field.

Boilerplate SQL

Starting point for reading the BICC-landed copy of PO_LINES_ALL on Databricks — real DATE columns need no conversion, and the org anchor and the LAST_UPDATE_DATE watermark (the column incremental BICC extracts key on) are already in place. Set your Unity Catalog location, schema, and org values below; they’re substituted into the SQL and the copy button.

Query parameters

5 parameters not filled: <catalog>, <schema>, <PRC_BU_ID>, <PO_LINE_ID>, <watermark>

-- ============================================================
-- Table  : PO_LINES_ALL — Purchasing document lines — the item, category, unit price, and ordered quantity per line; the line quantity is the rollup of its schedules one level down
-- Purpose: Column-selected read of PO_LINES_ALL — auto-generated from field metadata
-- Grain  : One row per PO_LINE_ID
-- Notes  : Auto-generated skeleton for Oracle Fusion Cloud data landed in your lakehouse by a BICC extract — there is no SQL path to the SaaS database. Column names follow Oracle's table documentation — if your landed data still carries PVO attribute headers, map names first; see quirks #pvo-drift. 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 line",
  t.PO_HEADER_ID AS "Parent purchasing document header",
  t.LINE_NUM AS "Visible line number",
  t.ITEM_ID AS "Item on the line — no inventory org here; resolve it through the schedule's ship-to org",
  t.ITEM_REVISION AS "Item revision",
  t.ITEM_DESCRIPTION AS "Line item description",
  t.CATEGORY_ID AS "Purchasing category",
  t.QUANTITY AS "Ordered quantity — the rollup of the line's schedules",
  t.UNIT_PRICE AS "Price per unit in document currency",
  t.AMOUNT AS "Budget amount — populated only for service-type lines",
  t.UOM_CODE AS "Unit of measure",
  t.LINE_TYPE_ID AS "Goods vs services line type",
  t.LINE_STATUS AS "Line status",
  t.CLOSED_DATE AS "When the line was closed",
  t.CANCEL_FLAG AS "Y when the line is cancelled",
  t.FROM_HEADER_ID AS "Source agreement/quotation header the line references",
  t.FROM_LINE_ID AS "Source agreement/quotation line",
  t.PRC_BU_ID AS "Procurement BU stripe, denormalized from the header"
FROM <catalog>.<schema>.PO_LINES_ALL t
WHERE
  t.PRC_BU_ID = <PRC_BU_ID>  -- business unit — this table stripes by a NAMED BU column, not ORG_ID; see quirks guide #all-means-bu
  -- AND t.PO_LINE_ID = <PO_LINE_ID>
  -- AND t.LAST_UPDATE_DATE >= TIMESTAMP '<watermark>'  -- the column incremental BICC extracts key on
ORDER BY t.PO_LINE_ID;

Verified September 2026 · docs release 26C

Column names differ in BICC extracts — see PVO header drift.

Relationships

Diagram of 1-hop neighbors — join details below. FND lookup decode and translation edges are highlighted; they’re the joins newcomers most often get wrong.

Join details

  • PO_HEADERS_ALLPO_LINES_ALLheader line · 1:N
    ON PO_HEADERS_ALL.PO_HEADER_ID = PO_LINES_ALL.PO_HEADER_ID
  • PO_LINE_LOCATIONS_ALLPO_LINES_ALLforeign key · N:1
    ON PO_LINE_LOCATIONS_ALL.PO_LINE_ID = PO_LINES_ALL.PO_LINE_ID
  • PO_LINES_ALLEGP_SYSTEM_ITEMS_Bforeign key · N:M
    ON PO_LINES_ALL.ITEM_ID = EGP_SYSTEM_ITEMS_B.INVENTORY_ITEM_ID
  • PO_LINES_ALLEGP_CATEGORIES_Bforeign key · N:1
    ON PO_LINES_ALL.CATEGORY_ID = EGP_CATEGORIES_B.CATEGORY_ID

Browse more Procurement tables

More Procurement tables

Maintained by Summit Analytics, a supply chain analytics practice. The tools and references are free — the consulting is selective.

Part of the Summit Analytics reference library.

Work with the practice

Not affiliated with or endorsed by Oracle. Oracle and Oracle Fusion Cloud Applications are registered trademarks of Oracle and/or its affiliates.