INV_TRANSFER_ORDER_HEADERS
Product: INVtransactionTransfer order headers — the orchestration document for internal material moves within or between organizations, carrying the order number, originating process, and requisitioning business unit
Deliberately thin: no header status, no org pair — source/destination organizations, statuses, and quantities all live on the lines, so header-level rollups must be derived. REQ_BU_ID is the requisitioning business unit (a named BU id column, not an ORG_ID stripe). FULFILL_ORCHESTRATION_REQUIRED marks orders routed through Order Management for fulfillment.
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_HEADERS is the header for its lines in INV_TRANSFER_ORDER_LINES.
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.TransferOrderHeaderExtractPVOOTBI: Inventory - Inventory Transfer Order Real Time
Keyed on HeaderId. The subject-area name is singular Order in Oracle's book — not Transfer Orders.
Oracle data-store documentation (opens in new tab)
Fields
8 fields · 1 key
8 fields.
| # | Field | Description | Type | Flags |
|---|---|---|---|---|
| 1 | HEADER_ID | Transfer-order surrogate key | NUMBER | Key |
| 2 | HEADER_NUMBER | The transfer order number users see | VARCHAR2 | |
| 3 | DESCRIPTION | Order description | VARCHAR2 | |
| 4 | REQ_BU_ID | Requisitioning business unit — a named BU id column, not an ORG_ID stripe | NUMBER | |
| 5 | SOURCE_TYPE_LOOKUP | Where the order originated (self-service, planning, return, min-max…) | VARCHAR2 | |
| 6 | ORDERED_DATE | Order creation date | DATE | Filter date |
| 7 | FULFILL_ORCHESTRATION_REQUIRED | Whether the order was routed through Order Management for fulfillment | VARCHAR2 | |
| 8 | BUDGET_CONTROL_ENABLED_FLAG | Under budgetary control or not | VARCHAR2 |
Field provenance: hand-curated. 1 key field.
Boilerplate SQL
Starting point for reading the BICC-landed copy of INV_TRANSFER_ORDER_HEADERS 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>, <HEADER_ID>, <DATE_FROM>, <DATE_TO>, <watermark>
-- ============================================================
-- Table : INV_TRANSFER_ORDER_HEADERS — Transfer order headers — the orchestration document for internal material moves within or between organizations, carrying the order number, originating process, and requisitioning business unit
-- Purpose: Column-selected read of INV_TRANSFER_ORDER_HEADERS — auto-generated from field metadata
-- Grain : One row per HEADER_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.HEADER_ID AS "Transfer-order surrogate key",
t.HEADER_NUMBER AS "The transfer order number users see",
t.DESCRIPTION AS "Order description",
t.REQ_BU_ID AS "Requisitioning business unit — a named BU id column, not an ORG_ID stripe",
t.SOURCE_TYPE_LOOKUP AS "Where the order originated (self-service, planning, return, min-max…)",
t.ORDERED_DATE AS "Order creation date",
t.FULFILL_ORCHESTRATION_REQUIRED AS "Whether the order was routed through Order Management for fulfillment",
t.BUDGET_CONTROL_ENABLED_FLAG AS "Under budgetary control or not"
FROM <catalog>.<schema>.INV_TRANSFER_ORDER_HEADERS t
WHERE
1 = 1 -- no automatic partition anchor on this table; the filters below are optional
-- AND t.HEADER_ID = <HEADER_ID>
-- AND t.ORDERED_DATE >= DATE '<DATE_FROM>'
-- AND t.ORDERED_DATE <= DATE '<DATE_TO>'
-- AND t.LAST_UPDATE_DATE >= TIMESTAMP '<watermark>' -- the column incremental BICC extracts key on
ORDER BY t.HEADER_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_HEADERS.REQ_BU_ID = FUN_ALL_BUSINESS_UNITS_V.BU_ID
More Inventory tables
- 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
- 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