MTL_TXN_REQUEST_HEADERS
Schema: INVtransactionPer inventory orgMove order headers — the user-visible move order number, type, status, and required date for requests to move material within an organization
REQUEST_NUMBER is unique per organization, not globally. Processing state mostly lives on the lines — filter line status, not just header status.
What the badges mean
- Schema: INV
- Schema: the Oracle product schema that owns the table (INV, ONT, WSH, PO, BOM, WIP, MRP, MSC, AR, AP, GL, HR, APPLSYS) — tells you which product family the object belongs to, not who can query it.
- master
- Data class: what the table holds — master data, transaction documents, control/configuration, interface/staging, or an APPS-schema view.
- OU-striped (ORG_ID)
- Rows are scoped to an operating unit. A landed extract carries every operating unit’s rows — filter or join on
ORG_ID, and don’t confuse it withORGANIZATION_ID(see the quirks guide). - Per inventory org
- Rows are scoped to an inventory organization (plant or warehouse) via
ORGANIZATION_ID— a different partition from OU-striped tables (see the quirks guide). - 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 (see the quirks guide). - View
- This is an APPS-schema convenience view, not a physical table. Extract the base tables it joins instead — views can be slow at scale and aren't guaranteed stable across patches.
Structural facts — how the table is partitioned, not a trap by itself
Join & extract hazards — verify before you rely on this
Header & line
MTL_TXN_REQUEST_HEADERS is the header for its lines in MTL_TXN_REQUEST_LINES.
Fields
8 fields · 1 key
8 fields.
| # | Field | Description | Type | Flags |
|---|---|---|---|---|
| 1 | HEADER_ID | Surrogate key of the move order | NUMBER | Primary-key field |
| 2 | REQUEST_NUMBER | The move order number users see — unique per org, not globally | VARCHAR2 | |
| 3 | ORGANIZATION_ID | Inventory organization | NUMBER | |
| 4 | MOVE_ORDER_TYPE | Requisition, replenishment, or pick-wave move order | NUMBER | |
| 5 | HEADER_STATUS | Header status — line status drives most processing, filter both | NUMBER | |
| 6 | TRANSACTION_TYPE_ID | The transaction type the move order transacts as | NUMBER | |
| 7 | DATE_REQUIRED | When the move is required | DATE | |
| 8 | DESCRIPTION | Move order description | VARCHAR2 |
Field provenance: hand-curated. 1 key field.
Boilerplate SQL
Starting point for reading MTL_TXN_REQUEST_HEADERS on Databricks — real DATE columns need no conversion, and the org anchor is already in place. The optional LAST_UPDATE_DATE watermark is included. Set your Unity Catalog location, schema, and org values below; they’re substituted into the SQL and the copy button.
5 parameters not filled: <catalog>, <schema>, <inventory_org_id>, <HEADER_ID>, <watermark>
-- ============================================================
-- Table : MTL_TXN_REQUEST_HEADERS — Move order headers — the user-visible move order number, type, status, and required date for requests to move material within an organization
-- Purpose: Column-selected read of MTL_TXN_REQUEST_HEADERS — auto-generated from field metadata
-- Grain : One row per inventory org (ORGANIZATION_ID) + HEADER_ID
-- Notes : Auto-generated skeleton for Oracle EBS R12 data landed in your lakehouse. 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 "Surrogate key of the move order",
t.REQUEST_NUMBER AS "The move order number users see — unique per org, not globally",
t.ORGANIZATION_ID AS "Inventory organization",
t.MOVE_ORDER_TYPE AS "Requisition, replenishment, or pick-wave move order",
t.HEADER_STATUS AS "Header status — line status drives most processing, filter both",
t.TRANSACTION_TYPE_ID AS "The transaction type the move order transacts as",
t.DATE_REQUIRED AS "When the move is required",
t.DESCRIPTION AS "Move order description"
FROM <catalog>.<schema>.MTL_TXN_REQUEST_HEADERS t
WHERE
t.ORGANIZATION_ID = <inventory_org_id> -- inventory org, NOT the operating unit — see quirks guide #two-orgs
-- AND t.HEADER_ID = <HEADER_ID>
-- AND t.LAST_UPDATE_DATE >= TIMESTAMP '<watermark>' -- WHO watermark, bulk-stamped by batch jobs; see quirks guide #who-columns
ORDER BY t.HEADER_ID;Verified September 2026
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 MTL_TXN_REQUEST_HEADERS.HEADER_ID = MTL_TXN_REQUEST_LINES.HEADER_ID AND MTL_TXN_REQUEST_HEADERS.ORGANIZATION_ID = MTL_TXN_REQUEST_LINES.ORGANIZATION_IDON MTL_TXN_REQUEST_HEADERS.TRANSACTION_TYPE_ID = MTL_TRANSACTION_TYPES.TRANSACTION_TYPE_ID
More Inventory tables
- MTL_TXN_REQUEST_LINESMove order lines — each row requests moving a quantity of an item from a source to a destination subinventory, individually statused, allocated (quantity detailed), and transacted (quantity delivered)
- MTL_DEMANDThe legacy demand picture used by ATP and planning — summary demand, open demand, and pre-R12 reservation rows for an item in an org, keyed to the order document that generated them
- MTL_ITEM_LOCATIONSThe stock locator master — the physical bin/row/rack positions inside a subinventory, with the locator name held as SEGMENTn flexfield columns
- MTL_LOT_NUMBERSThe lot master — definition, genealogy (parent lot), status, grade, and the origination/expiration/retest dates for every lot, keyed by item + organization + lot number
- MTL_MATERIAL_TRANSACTIONSThe 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
- MTL_ONHAND_QUANTITIES_DETAILThe on-hand balance detail — receipt-level slices of stock per item, org, subinventory, locator, lot, and revision, consumed in FIFO order as material issues