Skip to content
Fusion Reference

POR_REQUISITION_LINES_ALL

Product: PORtransaction

Requisition lines — item, quantity, price, need-by date, destination org, and suggested supplier per line; carries the keys of the resulting PO header, line, and schedule once sourced

Notes

The req→PO bridge points forward from here (PO_HEADER_ID / PO_LINE_ID / LINE_LOCATION_ID, NULL until sourced); the PO side's return path is the distribution's REQ_DISTRIBUTION_ID. PARENT_REQ_LINE_ID marks split/multisourced lines; the buyer hint is SUGGESTED_BUYER_ID (no AGENT_ID here).

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

POR_REQUISITION_LINES_ALL lines join back to their header POR_REQUISITION_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.PorBiccExtractAM.RequisitionLineExtractPVO
    OTBI: Procurement - Requisitions Real TimeOTBI: Procurement - Procure To Pay Real Time

    Requisition Lines data store — keyed on RequisitionLineId, with documented PO linkage attributes.

    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
1REQUISITION_LINE_IDSurrogate key of the requisition lineNUMBER
Key
2REQUISITION_HEADER_IDParent requisition headerNUMBER
3LINE_NUMBERVisible line numberNUMBER
4ITEM_IDRequested itemNUMBER
5ITEM_DESCRIPTIONItem descriptionVARCHAR2
6CATEGORY_IDPurchasing categoryNUMBER
7QUANTITYRequested quantityNUMBER
8UNIT_PRICEUnit price in functional currencyNUMBER
9UOM_CODEUnit of measureVARCHAR2
10NEED_BY_DATEInternal need-by dateDATE
Filter date
11DESTINATION_TYPE_CODEInventory vs expense destinationVARCHAR2
12DESTINATION_ORGANIZATION_IDDestination inventory organization — the org half of the line's item joinNUMBER
13REQUESTER_IDPerson the goods are forNUMBER
14VENDOR_IDSuggested or assigned supplierNUMBER
15SOURCE_TYPE_CODEInternal vs external source of supplyVARCHAR2
16PO_HEADER_IDThe resulting PO header — NULL until sourcedNUMBER
17LINE_LOCATION_IDThe resulting PO schedule — NULL until sourcedNUMBER
18LINE_STATUSRequisition line statusVARCHAR2

Field provenance: hand-curated. 1 key field.

Boilerplate SQL

Starting point for reading the BICC-landed copy of POR_REQUISITION_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

6 parameters not filled: <catalog>, <schema>, <REQUISITION_LINE_ID>, <DATE_FROM>, <DATE_TO>, <watermark>

-- ============================================================
-- Table  : POR_REQUISITION_LINES_ALL — Requisition lines — item, quantity, price, need-by date, destination org, and suggested supplier per line; carries the keys of the resulting PO header, line, and schedule once sourced
-- Purpose: Column-selected read of POR_REQUISITION_LINES_ALL — auto-generated from field metadata
-- Grain  : One row per REQUISITION_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.REQUISITION_LINE_ID AS "Surrogate key of the requisition line",
  t.REQUISITION_HEADER_ID AS "Parent requisition header",
  t.LINE_NUMBER AS "Visible line number",
  t.ITEM_ID AS "Requested item",
  t.ITEM_DESCRIPTION AS "Item description",
  t.CATEGORY_ID AS "Purchasing category",
  t.QUANTITY AS "Requested quantity",
  t.UNIT_PRICE AS "Unit price in functional currency",
  t.UOM_CODE AS "Unit of measure",
  t.NEED_BY_DATE AS "Internal need-by date",
  t.DESTINATION_TYPE_CODE AS "Inventory vs expense destination",
  t.DESTINATION_ORGANIZATION_ID AS "Destination inventory organization — the org half of the line's item join",
  t.REQUESTER_ID AS "Person the goods are for",
  t.VENDOR_ID AS "Suggested or assigned supplier",
  t.SOURCE_TYPE_CODE AS "Internal vs external source of supply",
  t.PO_HEADER_ID AS "The resulting PO header — NULL until sourced",
  t.LINE_LOCATION_ID AS "The resulting PO schedule — NULL until sourced",
  t.LINE_STATUS AS "Requisition line status"
FROM <catalog>.<schema>.POR_REQUISITION_LINES_ALL t
WHERE
  1 = 1  -- no automatic partition anchor on this table; the filters below are optional
  -- AND t.REQUISITION_LINE_ID = <REQUISITION_LINE_ID>
  -- AND t.NEED_BY_DATE >= DATE '<DATE_FROM>'
  -- AND t.NEED_BY_DATE <= DATE '<DATE_TO>'
  -- AND t.LAST_UPDATE_DATE >= TIMESTAMP '<watermark>'  -- the column incremental BICC extracts key on
ORDER BY t.REQUISITION_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

  • POR_REQUISITION_HEADERS_ALLPOR_REQUISITION_LINES_ALLheader line · 1:N
    ON POR_REQUISITION_HEADERS_ALL.REQUISITION_HEADER_ID = POR_REQUISITION_LINES_ALL.REQUISITION_HEADER_ID
  • POR_REQUISITION_LINES_ALLPO_HEADERS_ALLforeign key · N:1
    ON POR_REQUISITION_LINES_ALL.PO_HEADER_ID = PO_HEADERS_ALL.PO_HEADER_ID
  • POR_REQUISITION_LINES_ALLPO_LINE_LOCATIONS_ALLforeign key · N:1
    ON POR_REQUISITION_LINES_ALL.LINE_LOCATION_ID = PO_LINE_LOCATIONS_ALL.LINE_LOCATION_ID
  • POR_REQUISITION_LINES_ALLINV_ORG_PARAMETERSforeign key · N:1
    ON POR_REQUISITION_LINES_ALL.DESTINATION_ORGANIZATION_ID = INV_ORG_PARAMETERS.ORGANIZATION_ID
  • POR_REQUISITION_LINES_ALLEGP_SYSTEM_ITEMS_Bforeign key · N:1
    ON POR_REQUISITION_LINES_ALL.ITEM_ID = EGP_SYSTEM_ITEMS_B.INVENTORY_ITEM_ID AND POR_REQUISITION_LINES_ALL.DESTINATION_ORGANIZATION_ID = EGP_SYSTEM_ITEMS_B.ORGANIZATION_ID
  • POR_REQUISITION_LINES_ALLPOZ_SUPPLIERSforeign key · N:1
    ON POR_REQUISITION_LINES_ALL.VENDOR_ID = POZ_SUPPLIERS.VENDOR_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.