Skip to content
Fusion Reference

INV_TXN_REQUEST_LINES

Product: INVtransactionPer inventory org

Movement request lines — each row requests moving a quantity of an item from a source to a destination subinventory (or account), individually statused, allocated (quantity detailed), and delivered

Identity
Module: InventoryInventory-org partitioned (ORGANIZATION_ID)Header: INV_TXN_REQUEST_HEADERS
Notes

QUANTITY_DETAILED is the allocated quantity, QUANTITY_DELIVERED the transacted quantity — the difference against QUANTITY is the open balance; there is no stored open-quantity column. TO_ORGANIZATION_ID appears on cross-org moves alongside the row's own ORGANIZATION_ID.

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.

Header & line

INV_TXN_REQUEST_LINES lines join back to their header INV_TXN_REQUEST_HEADERS — 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.

Fields

18 fields · 1 key

18 fields.

Table fields: position, field name, description, data type, and flags. 18 fields.
#FieldDescriptionTypeFlags
1LINE_IDMovement-request-line surrogate keyNUMBER
Key
2HEADER_IDParent movement requestNUMBER
3LINE_NUMBERLine sequence within the requestNUMBER
4ORGANIZATION_IDInventory organization of the lineNUMBER
5INVENTORY_ITEM_IDItem being movedNUMBER
6FROM_SUBINVENTORY_CODESource subinventoryVARCHAR2
7FROM_LOCATOR_IDSource locatorNUMBER
8TO_SUBINVENTORY_CODEDestination subinventoryVARCHAR2
9TO_LOCATOR_IDDestination locatorNUMBER
10TO_ORGANIZATION_IDDestination organization on cross-org movesNUMBER
11TO_ACCOUNT_IDDestination account on account-issue linesNUMBER
12UOM_CODEUOM for the quantity columnsVARCHAR2
13QUANTITYRequested quantityNUMBER
14QUANTITY_DETAILEDQuantity already allocated (pick-detailed)NUMBER
15QUANTITY_DELIVEREDQuantity actually delivered — open balance is QUANTITY minus thisNUMBER
16DATE_REQUIREDLine need dateDATE
Filter date
17LINE_STATUSLine status — a numeric codeNUMBER
18TRANSACTION_TYPE_IDTransaction type governing the moveNUMBER

Field provenance: hand-curated. 1 key field.

Boilerplate SQL

Starting point for reading the BICC-landed copy of INV_TXN_REQUEST_LINES 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>, <LINE_ID>, <DATE_FROM>, <DATE_TO>, <watermark>

-- ============================================================
-- Table  : INV_TXN_REQUEST_LINES — Movement request lines — each row requests moving a quantity of an item from a source to a destination subinventory (or account), individually statused, allocated (quantity detailed), and delivered
-- Purpose: Column-selected read of INV_TXN_REQUEST_LINES — auto-generated from field metadata
-- Grain  : One row per inventory org (ORGANIZATION_ID) + 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.LINE_ID AS "Movement-request-line surrogate key",
  t.HEADER_ID AS "Parent movement request",
  t.LINE_NUMBER AS "Line sequence within the request",
  t.ORGANIZATION_ID AS "Inventory organization of the line",
  t.INVENTORY_ITEM_ID AS "Item being moved",
  t.FROM_SUBINVENTORY_CODE AS "Source subinventory",
  t.FROM_LOCATOR_ID AS "Source locator",
  t.TO_SUBINVENTORY_CODE AS "Destination subinventory",
  t.TO_LOCATOR_ID AS "Destination locator",
  t.TO_ORGANIZATION_ID AS "Destination organization on cross-org moves",
  t.TO_ACCOUNT_ID AS "Destination account on account-issue lines",
  t.UOM_CODE AS "UOM for the quantity columns",
  t.QUANTITY AS "Requested quantity",
  t.QUANTITY_DETAILED AS "Quantity already allocated (pick-detailed)",
  t.QUANTITY_DELIVERED AS "Quantity actually delivered — open balance is QUANTITY minus this",
  t.DATE_REQUIRED AS "Line need date",
  t.LINE_STATUS AS "Line status — a numeric code",
  t.TRANSACTION_TYPE_ID AS "Transaction type governing the move"
FROM <catalog>.<schema>.INV_TXN_REQUEST_LINES t
WHERE
  t.ORGANIZATION_ID = <inventory_org_id>  -- inventory org, NOT the business unit — see quirks guide #item-org-striping
  -- AND t.LINE_ID = <LINE_ID>
  -- AND t.DATE_REQUIRED >= DATE '<DATE_FROM>'
  -- AND t.DATE_REQUIRED <= DATE '<DATE_TO>'
  -- AND t.LAST_UPDATE_DATE >= TIMESTAMP '<watermark>'  -- the column incremental BICC extracts key on
ORDER BY t.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

  • INV_TXN_REQUEST_HEADERSINV_TXN_REQUEST_LINESheader line · 1:N
    ON INV_TXN_REQUEST_HEADERS.HEADER_ID = INV_TXN_REQUEST_LINES.HEADER_ID AND INV_TXN_REQUEST_HEADERS.ORGANIZATION_ID = INV_TXN_REQUEST_LINES.ORGANIZATION_ID
  • INV_TXN_REQUEST_LINESEGP_SYSTEM_ITEMS_Bforeign key · N:1
    ON INV_TXN_REQUEST_LINES.INVENTORY_ITEM_ID = EGP_SYSTEM_ITEMS_B.INVENTORY_ITEM_ID AND INV_TXN_REQUEST_LINES.ORGANIZATION_ID = EGP_SYSTEM_ITEMS_B.ORGANIZATION_ID
  • INV_TXN_REQUEST_LINESINV_TRANSACTION_TYPES_Bforeign key · N:1
    ON INV_TXN_REQUEST_LINES.TRANSACTION_TYPE_ID = INV_TRANSACTION_TYPES_B.TRANSACTION_TYPE_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.