Skip to content
Fusion Reference

INV_TXN_REQUEST_HEADERS

Product: INVtransactionPer inventory org

Movement request (move order) headers — the user-visible request number, type, status, and required date for requests to move material within an organization

Module: InventoryInventory-org partitioned (ORGANIZATION_ID)
Notes

REQUEST_NUMBER is unique per organization, not globally. The source/destination columns here are only line defaults, and processing state mostly lives on the lines — filter line status, not just header status. Status and type columns are numeric codes.

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_TXN_REQUEST_HEADERS is the header for its lines in INV_TXN_REQUEST_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.MovementRequestHeaderExtractPVO

    Keyed on HeaderId. No movement-request subject area exists in the 26B OTBI book — BICC is the delivered bulk path.

    Oracle data-store documentation →

Fields

15 fields · 2 key

Table fields: position, field name, description, data type, and flags. 15 fields.
#FieldDescriptionTypeFlags
1HEADER_IDMovement-request surrogate keyNUMBER
Key
2REQUEST_NUMBERThe user-visible move order number — unique per organization, not globallyVARCHAR2
Key
3ORGANIZATION_IDInventory organization of the requestNUMBER
4MOVE_ORDER_TYPECategory of movement request (requisition, pick wave…) — a numeric codeNUMBER
5TRANSACTION_TYPE_IDDefault transaction type for the requestNUMBER
6HEADER_STATUSOverall request status — a numeric code; line status is the working truthNUMBER
7STATUS_DATEWhen the status last changedDATE
8DATE_REQUIREDWhen the material is neededDATE
Filter date
9DESCRIPTIONFree-text description of the requestVARCHAR2
10FROM_SUBINVENTORY_CODEDefault source subinventory — lines can overrideVARCHAR2
11FROM_LOCATOR_IDDefault source locatorNUMBER
12TO_SUBINVENTORY_CODEDefault destination subinventoryVARCHAR2
13TO_LOCATOR_IDDefault destination locatorNUMBER
14TO_ACCOUNT_IDDestination account for account-issue movesNUMBER
15SHIP_TO_LOCATION_IDShip-to location referenceNUMBER

Field provenance: hand-curated. 2 key fields.

Boilerplate SQL

Starting point for reading the BICC-landed copy of INV_TXN_REQUEST_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_TXN_REQUEST_HEADERS — Movement request (move order) headers — the user-visible request number, type, status, and required date for requests to move material within an organization
-- Purpose: Column-selected read of INV_TXN_REQUEST_HEADERS — auto-generated from field metadata
-- Grain  : One row per inventory org (ORGANIZATION_ID) + HEADER_ID + REQUEST_NUMBER
-- 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 "Movement-request surrogate key",
  t.REQUEST_NUMBER AS "The user-visible move order number — unique per organization, not globally",
  t.ORGANIZATION_ID AS "Inventory organization of the request",
  t.MOVE_ORDER_TYPE AS "Category of movement request (requisition, pick wave…) — a numeric code",
  t.TRANSACTION_TYPE_ID AS "Default transaction type for the request",
  t.HEADER_STATUS AS "Overall request status — a numeric code; line status is the working truth",
  t.STATUS_DATE AS "When the status last changed",
  t.DATE_REQUIRED AS "When the material is needed",
  t.DESCRIPTION AS "Free-text description of the request",
  t.FROM_SUBINVENTORY_CODE AS "Default source subinventory — lines can override",
  t.FROM_LOCATOR_ID AS "Default source locator",
  t.TO_SUBINVENTORY_CODE AS "Default destination subinventory",
  t.TO_LOCATOR_ID AS "Default destination locator",
  t.TO_ACCOUNT_ID AS "Destination account for account-issue moves",
  t.SHIP_TO_LOCATION_ID AS "Ship-to location reference"
FROM <catalog>.<schema>.INV_TXN_REQUEST_HEADERS t
WHERE
  t.ORGANIZATION_ID = <inventory_org_id>  -- inventory org, NOT the business unit — see quirks guide #item-org-striping
  -- AND t.HEADER_ID = <HEADER_ID>
  -- AND t.REQUEST_NUMBER = '<REQUEST_NUMBER>'
  -- AND t.DATE_REQUIRED >= DATE '<DATE_FROM>'
  -- AND t.DATE_REQUIRED <= DATE '<DATE_TO>'
  -- AND t.LAST_UPDATE_DATE >= TIMESTAMP '<watermark>'  -- the column incremental BICC extracts key on
ORDER BY t.HEADER_ID;

8 parameters not filled: <catalog>, <schema>, <inventory_org_id>, <HEADER_ID>, <REQUEST_NUMBER>, <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_TXN_REQUEST_HEADERSINV_TXN_REQUEST_LINESheader line · 1:N
    ON INV_TXN_REQUEST_HEADERS.HEADER_ID = INV_TXN_REQUEST_LINES.HEADER_ID AND INV_TXN_REQUEST_HEADERS.ORGANIZATION_ID = INV_TXN_REQUEST_LINES.ORGANIZATION_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.