Skip to content
EBS Reference

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

Notes

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.
In field listings, K marks a primary-key field.

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

Table fields: position, field name, description, data type, and flags. 17 fields.
#FieldDescriptionTypeFlags
1REQUISITION_LINE_IDSurrogate key of the requisition lineNUMBER
Key
2REQUISITION_HEADER_IDThe parent requisitionNUMBER
3ORG_IDOperating unitNUMBER
4LINE_NUMLine number within the requisitionNUMBER
5ITEM_IDThe item requested — pairs with the destination org for item-master joinsNUMBER
6ITEM_DESCRIPTIONItem description on the lineVARCHAR2
7CATEGORY_IDPurchasing categoryNUMBER
8UNIT_MEAS_LOOKUP_CODEUnit of measure, name formVARCHAR2
9UNIT_PRICEUnit price on the requisition lineNUMBER
10QUANTITYRequested quantityNUMBER
11QUANTITY_DELIVEREDQuantity delivered against the lineNUMBER
12QUANTITY_CANCELLEDQuantity cancelledNUMBER
13SOURCE_TYPE_CODESupplier-sourced vs inventory-sourced (internal) lineVARCHAR2
14DESTINATION_TYPE_CODEWhere the goods charge to — inventory, expense, shop floorVARCHAR2
15DESTINATION_ORGANIZATION_IDThe receiving inventory org — the org half of this table's item joinNUMBER
16NEED_BY_DATEWhen the requester needs the goods — the primary analysis dateDATE
Filter date
17LINE_LOCATION_IDThe PO shipment autocreate built from this line — NULL until then; the req-to-PO threadNUMBER

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.

Query parameters
-- ============================================================
-- 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

  • OE_DROP_SHIP_SOURCESPO_REQUISITION_LINES_ALLforeign key · N:1
    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_ID
  • PO_REQUISITION_HEADERS_ALLPO_REQUISITION_LINES_ALLheader line · 1:N
    ON 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_ID
  • PO_REQUISITION_LINES_ALLPO_LINE_LOCATIONS_ALLforeign key · N:1
    ON 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_ID
  • PO_REQUISITION_LINES_ALLMTL_SYSTEM_ITEMS_Bforeign key · N:1
    ON 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

Browse more Purchasingtables →

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 E-Business Suite are registered trademarks of Oracle and/or its affiliates.