Results for “mtl_txn_request_headers”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

MTL_TXN_REQUEST_HEADERS is the header-level table for Move Orders in Oracle Inventory (INV). A move order is an internal requisition that instructs a warehouse or subinventory to transfer material from a source subinventory to a destination subinventory, or to a different organization, without an external sales transaction. The table stores the controlling information that governs each move order: who requested it, from where, to where, when it is required, its transaction type, and its current workflow status.

Because the header record carries the primary attributes of a move order but depends on MTL_PARAMETERS, MTL_SECONDARY_INVENTORIES, GL_CODE_COMBINATIONS, and MTL_TRANSACTION_TYPES, and is itself referenced by MTL_TXN_REQUEST_LINES and several dependent objects, it behaves primarily as descriptive detail around a business process rather than as a standalone master entity. From a dimensional modeling standpoint, the heuristic Data Vault classification is satellite-leaning: it enriches the move order key with context and status attributes rather than acting as a pure hub or an association link.

Key Information Stored

The table contains 45 documented columns. The most operationally significant are:

• HEADER_ID — surrogate primary key, enforced by MTL_TXN_REQUEST_HEADERS_PK.
• REQUEST_NUMBER and ORGANIZATION_ID — the documented business-key candidate, enforced by unique index MTL_TXN_REQUEST_HEADERS_U2.
• MOVE_ORDER_TYPE — distinguishes requisition-driven versus separately generated move orders.
• TRANSACTION_TYPE_ID and FROM_SUBINVENTORY_CODE — define the transaction rules and the source subinventory.
• TO_SUBINVENTORY_CODE and TO_ACCOUNT_ID — the destination subinventory and the general ledger account used for accounting.
• DATE_REQUIRED — the date by which material movement is required.
• HEADER_STATUS and STATUS_DATE — the current state of the move order and when that state changed.
• SHIP_TO_LOCATION_ID, FREIGHT_CODE, SHIPMENT_METHOD, and AUTO_RECEIPT_FLAG — shipping and receipt attributes controlling transfer execution.
• REFERENCE_ID and REFERENCE_DETAIL_ID — linkage to the originating document or demand.
• REQUEST_ID, PROGRAM_ID, and CREATION_DATE — concurrent request and audit context, along with the standard CREATED_BY/LAST_UPDATED_BY who columns and ATTRIBUTE1–15 descriptive flexfields.

Common Use Cases and Queries

Move order headers are queried for open order status, aging analysis, and reconciliation of internal transfers. A typical query lists move orders awaiting action:

• Open move orders: SELECT request_number, header_status, date_required FROM mtl_txn_request_headers WHERE organization_id = :org AND header_status IN ('1','2');
• Transfer analysis by subinventory: join to MTL_SECONDARY_INVENTORIES on FROM_SUBINVENTORY_CODE and TO_SUBINVENTORY_CODE to report movement between storage locations.
• Line-level detail: join MTL_TXN_REQUEST_LINES on HEADER_ID to obtain items and quantities.
• Accounting reconciliation: join GL_CODE_COMBINATIONS on TO_ACCOUNT_ID to verify the charge account associated with transfers.
• Aging report: compare DATE_REQUIRED with the current date for orders still unfulfilled.

For bulk processing, the Inventory Move Order APIs and concurrent programs insert and update these headers, with errors surfaced through the concurrent request columns.

Related Objects

• MTL_TXN_REQUEST_LINES — references HEADER_ID; the detail lines for each move order.
• MTL_PARAMETERS — referenced via ORGANIZATION_ID, supplying organizational defaults.
• MTL_SECONDARY_INVENTORIES — referenced via FROM_SUBINVENTORY_CODE and TO_SUBINVENTORY_CODE.
• GL_CODE_COMBINATIONS — referenced via TO_ACCOUNT_ID for accounting purposes.
• MTL_TRANSACTION_TYPES — referenced via TRANSACTION_TYPE_ID to determine transaction behavior.
• CSP_MOVEORDER_HEADERS and CSP_MOVEORDER_LINES — reference HEADER_ID, linking service/parts move orders.
• MTL_KANBAN_CARD_ACTIVITY — references DOCUMENT_HEADER_ID, connecting kanban replenishment to move orders.

Together these relationships position MTL_TXN_REQUEST_HEADERS as the central control record for internal inventory movement in Oracle EBS 12.1.1 and 12.2.2.