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

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
master
Data class: what the table holds — master data, transaction documents, control/configuration, interface/staging, or a documented view.
In field listings, K marks a primary-key field.

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

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_LINESon 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
-- ============================================================
-- 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;

7 parameters not filled: <catalog>, <schema>, <inventory_org_id>, <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

  • 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 Inventorytables →

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.