INV_RESERVATIONS
Product: INVtransactionPer inventory orgFirm 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
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.
- 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
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.ScmExtractAM.InvBiccExtractAM.InventoryReservationsExtractPVO
Keyed on ReservationId. No dedicated reservations subject area exists in the 26B OTBI book — BICC is the delivered bulk path.
Oracle data-store documentation (opens in new tab)
Fields
18 fields · 1 key
18 fields.
| # | Field | Description | Type | Flags |
|---|---|---|---|---|
| 1 | RESERVATION_ID | Surrogate key of the reservation | NUMBER | Key |
| 2 | INVENTORY_ITEM_ID | Reserved item | NUMBER | |
| 3 | ORGANIZATION_ID | Org where the reservation lives | NUMBER | |
| 4 | SUBINVENTORY_CODE | Subinventory of reserved stock — NULL for org-level reservations | VARCHAR2 | |
| 5 | LOCATOR_ID | Locator of reserved stock, when detailed | NUMBER | |
| 6 | LOT_NUMBER | Lot of reserved stock, when detailed | VARCHAR2 | |
| 7 | REVISION | Item revision of the reserved stock | VARCHAR2 | |
| 8 | DEMAND_SOURCE_TYPE_ID | What kind of demand consumes the reservation | NUMBER | |
| 9 | DEMAND_SOURCE_HEADER_ID | Demand document header | NUMBER | |
| 10 | DEMAND_SOURCE_LINE_ID | Demand document line | NUMBER | |
| 11 | SUPPLY_SOURCE_TYPE_ID | What kind of supply backs the reservation (on-hand, WIP…) | NUMBER | |
| 12 | SUPPLY_SOURCE_HEADER_ID | Supply document header | NUMBER | |
| 13 | SUPPLY_SOURCE_LINE_ID | Supply document line | NUMBER | |
| 14 | RESERVATION_QUANTITY | Reserved quantity in the reservation UOM | NUMBER | |
| 15 | PRIMARY_RESERVATION_QUANTITY | Reserved quantity in the item's primary UOM | NUMBER | |
| 16 | RESERVATION_UOM_CODE | UOM of the reservation | VARCHAR2 | |
| 17 | REQUIREMENT_DATE | When the demand needs the material | DATE | Filter date |
| 18 | DETAILED_QUANTITY | Portion of the reservation already pinned to subinventory/locator/lot | NUMBER |
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.
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
ON INV_RESERVATIONS.INVENTORY_ITEM_ID = EGP_SYSTEM_ITEMS_B.INVENTORY_ITEM_ID AND INV_RESERVATIONS.ORGANIZATION_ID = EGP_SYSTEM_ITEMS_B.ORGANIZATION_IDON INV_RESERVATIONS.ORGANIZATION_ID = INV_ORG_PARAMETERS.ORGANIZATION_ID
More Inventory tables
- INV_SECONDARY_INVENTORIESThe subinventory master — each row a named section of stock within an organization (stores, staging, receiving, rejects) with its asset/expense nature, tracking and reservability controls, and replenishment source
- INV_SERIAL_NUMBERSThe serial number master — definition and current position (status, org, subinventory, locator, lot) of every serialized unit, with manufacturing and shipping lifecycle dates
- INV_TRANSACTION_TYPES_BThe transaction type list — seeded and user-defined types, each mapping to the transaction action and source type that together classify material transactions
- INV_TRANSFER_ORDER_HEADERSTransfer order headers — the orchestration document for internal material moves within or between organizations, carrying the order number, originating process, and requisitioning business unit
- INV_TRANSFER_ORDER_LINESTransfer order lines — the actionable grain carrying item, source and destination organizations, the requested/shipped/received/delivered quantity lifecycle, dates, and the transfer price
- INV_TXN_REQUEST_HEADERSMovement request (move order) headers — the user-visible request number, type, status, and required date for requests to move material within an organization