Skip to content
EBS Reference

MTL_TXN_REQUEST_HEADERS

Schema: INVtransactionPer inventory org

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

Identity
Module: InventoryInventory-org partitioned (ORGANIZATION_ID)
Notes

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.

Structural facts — how the table is partitioned, not a trap by itself

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 with ORGANIZATION_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 LANGUAGE column (a _TL translation table or FND_LOOKUP_VALUES) — one row per language. Filter to one LANGUAGE or a join multiplies rows (see the quirks guide).

Join & extract hazards — verify before you rely on this

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

Header & line

MTL_TXN_REQUEST_HEADERS is the header for its lines in MTL_TXN_REQUEST_LINES.

Fields

8 fields · 1 key

8 fields.

Table fields: position, field name, description, data type, and flags. 8 fields.
#FieldDescriptionTypeFlags
1HEADER_IDSurrogate key of the move orderNUMBER
Primary-key field
2REQUEST_NUMBERThe move order number users see — unique per org, not globallyVARCHAR2
3ORGANIZATION_IDInventory organizationNUMBER
4MOVE_ORDER_TYPERequisition, replenishment, or pick-wave move orderNUMBER
5HEADER_STATUSHeader status — line status drives most processing, filter bothNUMBER
6TRANSACTION_TYPE_IDThe transaction type the move order transacts asNUMBER
7DATE_REQUIREDWhen the move is requiredDATE
8DESCRIPTIONMove order descriptionVARCHAR2

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.

Query parameters

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

  • MTL_TXN_REQUEST_HEADERSMTL_TXN_REQUEST_LINESheader line · 1:N
    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_ID
  • MTL_TXN_REQUEST_HEADERSMTL_TRANSACTION_TYPESforeign key · N:1
    ON MTL_TXN_REQUEST_HEADERS.TRANSACTION_TYPE_ID = MTL_TRANSACTION_TYPES.TRANSACTION_TYPE_ID

Browse more Inventory tables

More Inventory tables

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 E-Business Suite are registered trademarks of Oracle and/or its affiliates.