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
- master
- Data class: what the table holds — master data, transaction documents, control/configuration, interface/staging, or an APPS-schema view.
Header & line
MTL_TXN_REQUEST_HEADERS is the header for its lines in MTL_TXN_REQUEST_LINES.
Fields
8 fields · 1 key
| # | Field | Description | Type | Flags |
|---|---|---|---|---|
| 1 | HEADER_ID | Surrogate key of the move order | NUMBER | Key |
| 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_HEADERSon Databricks — real DATE columns need no conversion, and the org anchor and the LAST_UPDATE_DATE watermark 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 : 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;5 parameters not filled: <catalog>, <schema>, <inventory_org_id>, <HEADER_ID>, <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 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