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
- master
- Data class: what the table holds — master data, transaction documents, control/configuration, interface/staging, or a documented view.
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 →
Fields
8 fields · 1 key
| # | 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_HEADERSon 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.
-- ============================================================
-- 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 partition column 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;6 parameters not filled: <catalog>, <schema>, <HEADER_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
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