Skip to content
Fusion Reference

INV_TRANSFER_ORDER_LINES

Product: INVtransaction

Transfer order lines — the actionable grain carrying item, source and destination organizations, the requested/shipped/received/delivered quantity lifecycle, dates, and the transfer price

Grain note

Fulfillment is a quantity ladder — REQUESTED_QTY → SHIPPED_QTY → RECEIVED_QTY → DELIVERED_QTY — with no stored open-quantity column; open is arithmetic

Notes

Column quirks: quantities are *_QTY (not *_QUANTITY), statuses are VARCHAR2 *_LOOKUP codes (STATUS_LOOKUP: OPEN/CLOSED/CANCELLED), and the orgs are SOURCE_ORGANIZATION_ID / DESTINATION_ORGANIZATION_ID with no plain ORGANIZATION_ID — so the table gets no automatic org anchor; filter the org column you mean. DESTINATION_TYPE_LOOKUP says whether material lands in inventory or expense.

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_TRANSFER_ORDER_LINES lines join back to their header INV_TRANSFER_ORDER_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.

  • FscmTopModelAM.ScmExtractAM.InvBiccExtractAM.TransferOrderLineExtractPVO
    OTBI: Inventory - Inventory Transfer Order Real Time

    Keyed on LineId. Distribution detail rides the companion TransferOrderDistributionExtractPVO store.

    Oracle data-store documentation (opens in new tab)

Fields

18 fields · 1 key

18 fields.

Table fields: position, field name, description, data type, and flags. 18 fields.
#FieldDescriptionTypeFlags
1LINE_IDTransfer-order-line surrogate keyNUMBER
Key
2HEADER_IDParent transfer orderNUMBER
3LINE_NUMBERLine sequenceNUMBER
4INVENTORY_ITEM_IDItem transferredNUMBER
5SOURCE_ORGANIZATION_IDShipping (supply) inventory organizationNUMBER
6DESTINATION_ORGANIZATION_IDReceiving (demand) inventory organizationNUMBER
7DESTINATION_TYPE_LOOKUPWhether material lands in inventory or expenseVARCHAR2
8SOURCE_TYPE_LOOKUPOriginating process for the lineVARCHAR2
9STATUS_LOOKUPLine status — OPEN, CLOSED, or CANCELLED as a VARCHAR2 codeVARCHAR2
10INTERFACE_STATUS_LOOKUPHandoff state to orchestration/shipping (awaiting, interfaced, error)VARCHAR2
11QTY_UOM_CODEUOM for the quantity ladderVARCHAR2
12REQUESTED_QTYQuantity ordered — note the _QTY spellingNUMBER
13SHIPPED_QTYQuantity shipped so farNUMBER
14RECEIVED_QTYQuantity received at the destinationNUMBER
15DELIVERED_QTYQuantity put away into destination inventoryNUMBER
16NEED_BY_DATERequested arrival dateDATE
Filter date
17SCHEDULED_SHIP_DATEPlanned ship dateDATE
18UNIT_PRICETransfer price per unit, in the requesting org's currencyNUMBER

Field provenance: hand-curated. 1 key field.

Boilerplate SQL

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

6 parameters not filled: <catalog>, <schema>, <LINE_ID>, <DATE_FROM>, <DATE_TO>, <watermark>

-- ============================================================
-- Table  : INV_TRANSFER_ORDER_LINES — Transfer order lines — the actionable grain carrying item, source and destination organizations, the requested/shipped/received/delivered quantity lifecycle, dates, and the transfer price
-- Purpose: Column-selected read of INV_TRANSFER_ORDER_LINES — auto-generated from field metadata
-- Grain  : One row per LINE_ID
-- Caution: Fulfillment is a quantity ladder — REQUESTED_QTY → SHIPPED_QTY → RECEIVED_QTY → DELIVERED_QTY — with no stored open-quantity column; open is arithmetic
-- 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 "Transfer-order-line surrogate key",
  t.HEADER_ID AS "Parent transfer order",
  t.LINE_NUMBER AS "Line sequence",
  t.INVENTORY_ITEM_ID AS "Item transferred",
  t.SOURCE_ORGANIZATION_ID AS "Shipping (supply) inventory organization",
  t.DESTINATION_ORGANIZATION_ID AS "Receiving (demand) inventory organization",
  t.DESTINATION_TYPE_LOOKUP AS "Whether material lands in inventory or expense",
  t.SOURCE_TYPE_LOOKUP AS "Originating process for the line",
  t.STATUS_LOOKUP AS "Line status — OPEN, CLOSED, or CANCELLED as a VARCHAR2 code",
  t.INTERFACE_STATUS_LOOKUP AS "Handoff state to orchestration/shipping (awaiting, interfaced, error)",
  t.QTY_UOM_CODE AS "UOM for the quantity ladder",
  t.REQUESTED_QTY AS "Quantity ordered — note the _QTY spelling",
  t.SHIPPED_QTY AS "Quantity shipped so far",
  t.RECEIVED_QTY AS "Quantity received at the destination",
  t.DELIVERED_QTY AS "Quantity put away into destination inventory",
  t.NEED_BY_DATE AS "Requested arrival date",
  t.SCHEDULED_SHIP_DATE AS "Planned ship date",
  t.UNIT_PRICE AS "Transfer price per unit, in the requesting org's currency"
FROM <catalog>.<schema>.INV_TRANSFER_ORDER_LINES t
WHERE
  1 = 1  -- no automatic partition anchor on this table; the filters below are optional
  -- AND t.LINE_ID = <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>'  -- 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_TRANSFER_ORDER_HEADERSINV_TRANSFER_ORDER_LINESheader line · 1:N
    ON INV_TRANSFER_ORDER_HEADERS.HEADER_ID = INV_TRANSFER_ORDER_LINES.HEADER_ID
  • INV_TRANSFER_ORDER_LINESEGP_SYSTEM_ITEMS_Bforeign key · N:1
    ON INV_TRANSFER_ORDER_LINES.INVENTORY_ITEM_ID = EGP_SYSTEM_ITEMS_B.INVENTORY_ITEM_ID AND INV_TRANSFER_ORDER_LINES.DESTINATION_ORGANIZATION_ID = EGP_SYSTEM_ITEMS_B.ORGANIZATION_ID
  • INV_TRANSFER_ORDER_LINESINV_ORG_PARAMETERSforeign key · N:1
    ON INV_TRANSFER_ORDER_LINES.SOURCE_ORGANIZATION_ID = INV_ORG_PARAMETERS.ORGANIZATION_ID
  • INV_TRANSFER_ORDER_LINESINV_ORG_PARAMETERSforeign key · N:1
    ON INV_TRANSFER_ORDER_LINES.DESTINATION_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.