Skip to content
Fusion Reference

INV_TRANSFER_ORDER_HEADERS

Product: INVtransaction

Transfer order headers — the orchestration document for internal material moves within or between organizations, carrying the order number, originating process, and requisitioning business unit

Module: InventoryNot org-partitioned
Notes

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.
In field listings, K marks a primary-key field.

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.TransferOrderHeaderExtractPVO
    OTBI: 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

Table fields: position, field name, description, data type, and flags. 8 fields.
#FieldDescriptionTypeFlags
1HEADER_IDTransfer-order surrogate keyNUMBER
Key
2HEADER_NUMBERThe transfer order number users seeVARCHAR2
3DESCRIPTIONOrder descriptionVARCHAR2
4REQ_BU_IDRequisitioning business unit — a named BU id column, not an ORG_ID stripeNUMBER
5SOURCE_TYPE_LOOKUPWhere the order originated (self-service, planning, return, min-max…)VARCHAR2
6ORDERED_DATEOrder creation dateDATE
Filter date
7FULFILL_ORCHESTRATION_REQUIREDWhether the order was routed through Order Management for fulfillmentVARCHAR2
8BUDGET_CONTROL_ENABLED_FLAGUnder budgetary control or notVARCHAR2

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.

Query parameters
-- ============================================================
-- 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

  • 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_HEADERSFUN_ALL_BUSINESS_UNITS_Vforeign key · N:1
    ON INV_TRANSFER_ORDER_HEADERS.REQ_BU_ID = FUN_ALL_BUSINESS_UNITS_V.BU_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.