PO_REQUISITION_LINES_ALL
Schema: POtransactionOU-striped (ORG_ID)Requisition lines — item, quantity, price, need-by date, destination inventory org, and sourcing suggestion per line; carries the link to the PO shipment autocreate built from it
The item column is ITEM_ID; DESTINATION_ORGANIZATION_ID (an inventory org) is the org half of its item join. LINE_LOCATION_ID points at the PO shipment created from the line — NULL until autocreate.
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_REQUISITION_LINES_ALL lines join back to their header PO_REQUISITION_HEADERS_ALL — and the org column — so a line never fans out.
Fields
17 fields · 1 key
| # | Field | Description | Type | Flags |
|---|---|---|---|---|
| 1 | REQUISITION_LINE_ID | Surrogate key of the requisition line | NUMBER | Key |
| 2 | REQUISITION_HEADER_ID | The parent requisition | NUMBER | |
| 3 | ORG_ID | Operating unit | NUMBER | |
| 4 | LINE_NUM | Line number within the requisition | NUMBER | |
| 5 | ITEM_ID | The item requested — pairs with the destination org for item-master joins | NUMBER | |
| 6 | ITEM_DESCRIPTION | Item description on the line | VARCHAR2 | |
| 7 | CATEGORY_ID | Purchasing category | NUMBER | |
| 8 | UNIT_MEAS_LOOKUP_CODE | Unit of measure, name form | VARCHAR2 | |
| 9 | UNIT_PRICE | Unit price on the requisition line | NUMBER | |
| 10 | QUANTITY | Requested quantity | NUMBER | |
| 11 | QUANTITY_DELIVERED | Quantity delivered against the line | NUMBER | |
| 12 | QUANTITY_CANCELLED | Quantity cancelled | NUMBER | |
| 13 | SOURCE_TYPE_CODE | Supplier-sourced vs inventory-sourced (internal) line | VARCHAR2 | |
| 14 | DESTINATION_TYPE_CODE | Where the goods charge to — inventory, expense, shop floor | VARCHAR2 | |
| 15 | DESTINATION_ORGANIZATION_ID | The receiving inventory org — the org half of this table's item join | NUMBER | |
| 16 | NEED_BY_DATE | When the requester needs the goods — the primary analysis date | DATE | Filter date |
| 17 | LINE_LOCATION_ID | The PO shipment autocreate built from this line — NULL until then; the req-to-PO thread | NUMBER |
Field provenance: hand-curated. 1 key field.
Boilerplate SQL
Starting point for reading PO_REQUISITION_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_REQUISITION_LINES_ALL — Requisition lines — item, quantity, price, need-by date, destination inventory org, and sourcing suggestion per line; carries the link to the PO shipment autocreate built from it
-- Purpose: Column-selected read of PO_REQUISITION_LINES_ALL — auto-generated from field metadata
-- Grain : One row per operating unit (ORG_ID) + REQUISITION_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.REQUISITION_LINE_ID AS "Surrogate key of the requisition line",
t.REQUISITION_HEADER_ID AS "The parent requisition",
t.ORG_ID AS "Operating unit",
t.LINE_NUM AS "Line number within the requisition",
t.ITEM_ID AS "The item requested — pairs with the destination org for item-master joins",
t.ITEM_DESCRIPTION AS "Item description on the line",
t.CATEGORY_ID AS "Purchasing category",
t.UNIT_MEAS_LOOKUP_CODE AS "Unit of measure, name form",
t.UNIT_PRICE AS "Unit price on the requisition line",
t.QUANTITY AS "Requested quantity",
t.QUANTITY_DELIVERED AS "Quantity delivered against the line",
t.QUANTITY_CANCELLED AS "Quantity cancelled",
t.SOURCE_TYPE_CODE AS "Supplier-sourced vs inventory-sourced (internal) line",
t.DESTINATION_TYPE_CODE AS "Where the goods charge to — inventory, expense, shop floor",
t.DESTINATION_ORGANIZATION_ID AS "The receiving inventory org — the org half of this table's item join",
t.NEED_BY_DATE AS "When the requester needs the goods — the primary analysis date",
t.LINE_LOCATION_ID AS "The PO shipment autocreate built from this line — NULL until then; the req-to-PO thread"
FROM <catalog>.<schema>.PO_REQUISITION_LINES_ALL t
WHERE
t.ORG_ID = <operating_unit_id> -- operating unit (MOAC does not filter extracts)
-- 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>' -- WHO watermark, bulk-stamped by batch jobs; see quirks guide #who-columns
ORDER BY t.REQUISITION_LINE_ID;7 parameters not filled: <catalog>, <schema>, <operating_unit_id>, <REQUISITION_LINE_ID>, <DATE_FROM>, <DATE_TO>, <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 OE_DROP_SHIP_SOURCES.REQUISITION_LINE_ID = PO_REQUISITION_LINES_ALL.REQUISITION_LINE_ID AND OE_DROP_SHIP_SOURCES.ORG_ID = PO_REQUISITION_LINES_ALL.ORG_IDON PO_REQUISITION_HEADERS_ALL.REQUISITION_HEADER_ID = PO_REQUISITION_LINES_ALL.REQUISITION_HEADER_ID AND PO_REQUISITION_HEADERS_ALL.ORG_ID = PO_REQUISITION_LINES_ALL.ORG_IDON PO_REQUISITION_LINES_ALL.LINE_LOCATION_ID = PO_LINE_LOCATIONS_ALL.LINE_LOCATION_ID AND PO_REQUISITION_LINES_ALL.ORG_ID = PO_LINE_LOCATIONS_ALL.ORG_IDON PO_REQUISITION_LINES_ALL.ITEM_ID = MTL_SYSTEM_ITEMS_B.INVENTORY_ITEM_ID AND PO_REQUISITION_LINES_ALL.DESTINATION_ORGANIZATION_ID = MTL_SYSTEM_ITEMS_B.ORGANIZATION_ID