INV_TXN_REQUEST_HEADERS
Product: INVtransactionPer inventory orgMovement request (move order) headers — the user-visible request number, type, status, and required date for requests to move material within an organization
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.
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
| # | Field | Description | Type | Flags |
|---|---|---|---|---|
| 1 | HEADER_ID | Movement-request surrogate key | NUMBER | Key |
| 2 | REQUEST_NUMBER | The user-visible move order number — unique per organization, not globally | VARCHAR2 | Key |
| 3 | ORGANIZATION_ID | Inventory organization of the request | NUMBER | |
| 4 | MOVE_ORDER_TYPE | Category of movement request (requisition, pick wave…) — a numeric code | NUMBER | |
| 5 | TRANSACTION_TYPE_ID | Default transaction type for the request | NUMBER | |
| 6 | HEADER_STATUS | Overall request status — a numeric code; line status is the working truth | NUMBER | |
| 7 | STATUS_DATE | When the status last changed | DATE | |
| 8 | DATE_REQUIRED | When the material is needed | DATE | Filter date |
| 9 | DESCRIPTION | Free-text description of the request | VARCHAR2 | |
| 10 | FROM_SUBINVENTORY_CODE | Default source subinventory — lines can override | VARCHAR2 | |
| 11 | FROM_LOCATOR_ID | Default source locator | NUMBER | |
| 12 | TO_SUBINVENTORY_CODE | Default destination subinventory | VARCHAR2 | |
| 13 | TO_LOCATOR_ID | Default destination locator | NUMBER | |
| 14 | TO_ACCOUNT_ID | Destination account for account-issue moves | NUMBER | |
| 15 | SHIP_TO_LOCATION_ID | Ship-to location reference | NUMBER |
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.
-- ============================================================
-- 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
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