Skip to content
Fusion Reference

INV_RESERVATIONS

Product: INVtransactionPer inventory org

Firm reservations tying a demand source (a sales order line, most commonly) to a supply source (on-hand or expected supply) for an item in an org, optionally pinned down to subinventory, locator, and lot

Identity
Module: InventoryInventory-org partitioned (ORGANIZATION_ID)
EBS equivalents (1)
Notes

Subinventory/locator/lot columns are nullable — org-level reservations leave them empty; DETAILED_QUANTITY says how much of the reservation is pinned to a location. The demand/supply source model carries over from EBS nearly column-for-column.

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.

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.

Fields

18 fields · 1 key

18 fields.

Table fields: position, field name, description, data type, and flags. 18 fields.
#FieldDescriptionTypeFlags
1RESERVATION_IDSurrogate key of the reservationNUMBER
Key
2INVENTORY_ITEM_IDReserved itemNUMBER
3ORGANIZATION_IDOrg where the reservation livesNUMBER
4SUBINVENTORY_CODESubinventory of reserved stock — NULL for org-level reservationsVARCHAR2
5LOCATOR_IDLocator of reserved stock, when detailedNUMBER
6LOT_NUMBERLot of reserved stock, when detailedVARCHAR2
7REVISIONItem revision of the reserved stockVARCHAR2
8DEMAND_SOURCE_TYPE_IDWhat kind of demand consumes the reservationNUMBER
9DEMAND_SOURCE_HEADER_IDDemand document headerNUMBER
10DEMAND_SOURCE_LINE_IDDemand document lineNUMBER
11SUPPLY_SOURCE_TYPE_IDWhat kind of supply backs the reservation (on-hand, WIP…)NUMBER
12SUPPLY_SOURCE_HEADER_IDSupply document headerNUMBER
13SUPPLY_SOURCE_LINE_IDSupply document lineNUMBER
14RESERVATION_QUANTITYReserved quantity in the reservation UOMNUMBER
15PRIMARY_RESERVATION_QUANTITYReserved quantity in the item's primary UOMNUMBER
16RESERVATION_UOM_CODEUOM of the reservationVARCHAR2
17REQUIREMENT_DATEWhen the demand needs the materialDATE
Filter date
18DETAILED_QUANTITYPortion of the reservation already pinned to subinventory/locator/lotNUMBER

Field provenance: hand-curated. 1 key field.

Boilerplate SQL

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

7 parameters not filled: <catalog>, <schema>, <inventory_org_id>, <RESERVATION_ID>, <DATE_FROM>, <DATE_TO>, <watermark>

-- ============================================================
-- Table  : INV_RESERVATIONS — Firm reservations tying a demand source (a sales order line, most commonly) to a supply source (on-hand or expected supply) for an item in an org, optionally pinned down to subinventory, locator, and lot
-- Purpose: Column-selected read of INV_RESERVATIONS — auto-generated from field metadata
-- Grain  : One row per inventory org (ORGANIZATION_ID) + RESERVATION_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.RESERVATION_ID AS "Surrogate key of the reservation",
  t.INVENTORY_ITEM_ID AS "Reserved item",
  t.ORGANIZATION_ID AS "Org where the reservation lives",
  t.SUBINVENTORY_CODE AS "Subinventory of reserved stock — NULL for org-level reservations",
  t.LOCATOR_ID AS "Locator of reserved stock, when detailed",
  t.LOT_NUMBER AS "Lot of reserved stock, when detailed",
  t.REVISION AS "Item revision of the reserved stock",
  t.DEMAND_SOURCE_TYPE_ID AS "What kind of demand consumes the reservation",
  t.DEMAND_SOURCE_HEADER_ID AS "Demand document header",
  t.DEMAND_SOURCE_LINE_ID AS "Demand document line",
  t.SUPPLY_SOURCE_TYPE_ID AS "What kind of supply backs the reservation (on-hand, WIP…)",
  t.SUPPLY_SOURCE_HEADER_ID AS "Supply document header",
  t.SUPPLY_SOURCE_LINE_ID AS "Supply document line",
  t.RESERVATION_QUANTITY AS "Reserved quantity in the reservation UOM",
  t.PRIMARY_RESERVATION_QUANTITY AS "Reserved quantity in the item's primary UOM",
  t.RESERVATION_UOM_CODE AS "UOM of the reservation",
  t.REQUIREMENT_DATE AS "When the demand needs the material",
  t.DETAILED_QUANTITY AS "Portion of the reservation already pinned to subinventory/locator/lot"
FROM <catalog>.<schema>.INV_RESERVATIONS t
WHERE
  t.ORGANIZATION_ID = <inventory_org_id>  -- inventory org, NOT the business unit — see quirks guide #item-org-striping
  -- AND t.RESERVATION_ID = <RESERVATION_ID>
  -- AND t.REQUIREMENT_DATE >= DATE '<DATE_FROM>'
  -- AND t.REQUIREMENT_DATE <= DATE '<DATE_TO>'
  -- AND t.LAST_UPDATE_DATE >= TIMESTAMP '<watermark>'  -- the column incremental BICC extracts key on
ORDER BY t.RESERVATION_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

  • INV_RESERVATIONSEGP_SYSTEM_ITEMS_Bforeign key · N:1
    ON INV_RESERVATIONS.INVENTORY_ITEM_ID = EGP_SYSTEM_ITEMS_B.INVENTORY_ITEM_ID AND INV_RESERVATIONS.ORGANIZATION_ID = EGP_SYSTEM_ITEMS_B.ORGANIZATION_ID
  • INV_RESERVATIONSINV_ORG_PARAMETERSforeign key · N:1
    ON INV_RESERVATIONS.ORGANIZATION_ID = INV_ORG_PARAMETERS.ORGANIZATION_ID

Browse more Inventory tables

More Inventory 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.