POR_REQUISITION_LINES_ALL
Product: PORtransactionRequisition 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
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.
- 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 withINVENTORY_ITEM_IDon 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_IDon the GL journal tables), or a named business-unit column (PRC_BU_ID/REQ_BU_IDin 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
LANGUAGEcolumn (a _TL translation table or FND_LOOKUP_VALUES) — one row per language. Filter to oneLANGUAGEor a join multiplies rows. - Date-effective
- This is an
_Ftable — one row per entity per effectivity window, withEFFECTIVE_START_DATEandEFFECTIVE_END_DATEpart 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.
Structural facts — how the table is partitioned, not a trap by itself
Join & extract hazards — verify before you rely on this
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.RequisitionLineExtractPVOOTBI: 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.
| # | Field | Description | Type | Flags |
|---|---|---|---|---|
| 1 | REQUISITION_LINE_ID | Surrogate key of the requisition line | NUMBER | Key |
| 2 | REQUISITION_HEADER_ID | Parent requisition header | NUMBER | |
| 3 | LINE_NUMBER | Visible line number | NUMBER | |
| 4 | ITEM_ID | Requested item | NUMBER | |
| 5 | ITEM_DESCRIPTION | Item description | VARCHAR2 | |
| 6 | CATEGORY_ID | Purchasing category | NUMBER | |
| 7 | QUANTITY | Requested quantity | NUMBER | |
| 8 | UNIT_PRICE | Unit price in functional currency | NUMBER | |
| 9 | UOM_CODE | Unit of measure | VARCHAR2 | |
| 10 | NEED_BY_DATE | Internal need-by date | DATE | Filter date |
| 11 | DESTINATION_TYPE_CODE | Inventory vs expense destination | VARCHAR2 | |
| 12 | DESTINATION_ORGANIZATION_ID | Destination inventory organization — the org half of the line's item join | NUMBER | |
| 13 | REQUESTER_ID | Person the goods are for | NUMBER | |
| 14 | VENDOR_ID | Suggested or assigned supplier | NUMBER | |
| 15 | SOURCE_TYPE_CODE | Internal vs external source of supply | VARCHAR2 | |
| 16 | PO_HEADER_ID | The resulting PO header — NULL until sourced | NUMBER | |
| 17 | LINE_LOCATION_ID | The resulting PO schedule — NULL until sourced | NUMBER | |
| 18 | LINE_STATUS | Requisition line status | VARCHAR2 |
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.
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
ON POR_REQUISITION_HEADERS_ALL.REQUISITION_HEADER_ID = POR_REQUISITION_LINES_ALL.REQUISITION_HEADER_IDON POR_REQUISITION_LINES_ALL.PO_HEADER_ID = PO_HEADERS_ALL.PO_HEADER_IDON POR_REQUISITION_LINES_ALL.LINE_LOCATION_ID = PO_LINE_LOCATIONS_ALL.LINE_LOCATION_IDON POR_REQUISITION_LINES_ALL.DESTINATION_ORGANIZATION_ID = INV_ORG_PARAMETERS.ORGANIZATION_IDON 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_IDON POR_REQUISITION_LINES_ALL.VENDOR_ID = POZ_SUPPLIERS.VENDOR_ID
More Procurement tables
- POZ_SUPPLIER_SITES_ALL_MSupplier sites — the transactable endpoints purchase orders and payments point at, one row per supplier address per procurement business unit, with purchasing/pay/RFQ purpose flags and payment defaults
- POZ_SUPPLIERSThe supplier master — one row per supplier with the supplier number, type, business relationship level, and tax attributes, backed by the trading community architecture through its party id
- PO_DISTRIBUTIONS_ALLPO accounting distributions — how each schedule's quantity charges out: destination type and org, deliver-to, the GL charge account, project costing columns, and the requisition distribution it fulfills
- PO_HEADERS_ALLPurchasing document headers — one row per purchase order or agreement (standard, blanket, contract), with supplier, buyer, currency, and the document status; striped by the procurement business unit
- PO_LINE_LOCATIONS_ALLPO schedules — one row per shipment schedule (or blanket price break) with need-by/promised dates and the system-maintained received/accepted/rejected/billed quantity buckets; the workhorse grain for open-PO analytics
- PO_LINES_ALLPurchasing document lines — the item, category, unit price, and ordered quantity per line; the line quantity is the rollup of its schedules one level down