INV_TRANSFER_ORDER_LINES
Product: INVtransactionTransfer order lines — the actionable grain carrying item, source and destination organizations, the requested/shipped/received/delivered quantity lifecycle, dates, and the transfer price
Fulfillment is a quantity ladder — REQUESTED_QTY → SHIPPED_QTY → RECEIVED_QTY → DELIVERED_QTY — with no stored open-quantity column; open is arithmetic
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.
- 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
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.TransferOrderLineExtractPVOOTBI: 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.
| # | Field | Description | Type | Flags |
|---|---|---|---|---|
| 1 | LINE_ID | Transfer-order-line surrogate key | NUMBER | Key |
| 2 | HEADER_ID | Parent transfer order | NUMBER | |
| 3 | LINE_NUMBER | Line sequence | NUMBER | |
| 4 | INVENTORY_ITEM_ID | Item transferred | NUMBER | |
| 5 | SOURCE_ORGANIZATION_ID | Shipping (supply) inventory organization | NUMBER | |
| 6 | DESTINATION_ORGANIZATION_ID | Receiving (demand) inventory organization | NUMBER | |
| 7 | DESTINATION_TYPE_LOOKUP | Whether material lands in inventory or expense | VARCHAR2 | |
| 8 | SOURCE_TYPE_LOOKUP | Originating process for the line | VARCHAR2 | |
| 9 | STATUS_LOOKUP | Line status — OPEN, CLOSED, or CANCELLED as a VARCHAR2 code | VARCHAR2 | |
| 10 | INTERFACE_STATUS_LOOKUP | Handoff state to orchestration/shipping (awaiting, interfaced, error) | VARCHAR2 | |
| 11 | QTY_UOM_CODE | UOM for the quantity ladder | VARCHAR2 | |
| 12 | REQUESTED_QTY | Quantity ordered — note the _QTY spelling | NUMBER | |
| 13 | SHIPPED_QTY | Quantity shipped so far | NUMBER | |
| 14 | RECEIVED_QTY | Quantity received at the destination | NUMBER | |
| 15 | DELIVERED_QTY | Quantity put away into destination inventory | NUMBER | |
| 16 | NEED_BY_DATE | Requested arrival date | DATE | Filter date |
| 17 | SCHEDULED_SHIP_DATE | Planned ship date | DATE | |
| 18 | UNIT_PRICE | Transfer price per unit, in the requesting org's currency | NUMBER |
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.
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
ON INV_TRANSFER_ORDER_HEADERS.HEADER_ID = INV_TRANSFER_ORDER_LINES.HEADER_IDON 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_IDON INV_TRANSFER_ORDER_LINES.SOURCE_ORGANIZATION_ID = INV_ORG_PARAMETERS.ORGANIZATION_IDON INV_TRANSFER_ORDER_LINES.DESTINATION_ORGANIZATION_ID = INV_ORG_PARAMETERS.ORGANIZATION_ID
More Inventory tables
- 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
- INV_TXN_REQUEST_LINESMovement 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
- INV_ITEM_LOCATIONSThe stock locator master — the physical bin/row/rack positions inside a subinventory, with the human-readable locator name, capacity limits, and pick sequencing
- INV_LOT_NUMBERSThe lot master — definition, genealogy (parent lot), grade, and the origination/expiration/retest dates for every lot, keyed by item + organization + lot number
- INV_MATERIAL_TXNSThe material transaction ledger — one row per inventory movement or cost update, classified by transaction type, action, and source type, with quantity, date, and the document reference that caused it; the reconciliation backbone for every stock question
- INV_ONHAND_QUANTITIES_DETAILThe on-hand balance detail — receipt-level slices of stock per item, org, subinventory, locator, and lot, consumed in FIFO order as material issues