Search Results mtl_txn_request_headers




Overview
Explore in AI Chat

Overview

The MTL_TXN_REQUEST_HEADERS table is a core transactional data object within the Oracle E-Business Suite Inventory (INV) module. It serves as the header table for Move Orders, a critical component of the material movement and internal requisitioning process. A Move Order is a formal request to move material from one location to another within an organization, such as from a storage subinventory to a production staging area. This table stores the overarching control information for each move order transaction, establishing the context and parameters for the detailed line items stored in its related child table. Its existence is fundamental to managing and tracking the approval, sourcing, and fulfillment of internal material transfer requests.

Key Information Stored

The table's primary key is the HEADER_ID, a unique system-generated identifier for each move order. Key descriptive and control columns include REQUEST_NUMBER, which is the user-facing identifier for the order, and DESCRIPTION. The ORGANIZATION_ID links the header to the specific inventory organization. Critical transactional parameters are stored, such as TRANSACTION_TYPE_ID (linking to MTL_TRANSACTION_TYPES to define the move purpose), STATUS (e.g., Draft, Approved, Cancelled), and REQUESTED_COMPLETION_DATE. It also holds sourcing and destination information, including FROM_SUBINVENTORY_CODE, TO_SUBINVENTORY_CODE, and TO_ACCOUNT_ID (linking to GL_CODE_COMBINATIONS for the destination charge account). Columns like CREATED_BY and CREATION_DATE provide standard EBS audit trail information.

Common Use Cases and Queries

This table is central to reporting on move order volume, status, and lifecycle. Common queries involve joining to MTL_TXN_REQUEST_LINES to get a complete view of an order. For example, to find all approved move orders pending fulfillment for a specific organization, one might query:

  • SELECT mtrh.request_number, mtrh.status, COUNT(mtrl.line_id) as line_count FROM inv.mtl_txn_request_headers mtrh JOIN inv.mtl_txn_request_lines mtrl ON mtrh.header_id = mtrl.header_id WHERE mtrh.organization_id = :p_org_id AND mtrh.status = 'APPROVED' GROUP BY mtrh.request_number, mtrh.status;

Another common use case is tracing the source of a material transaction back to its originating move order header via the MTL_MATERIAL_TRANSACTIONS table. Integration points include custom workflows for move order approval and interfaces with warehouse management systems for pick release and shipment confirmation.

Related Objects

As documented in the ETRM, MTL_TXN_REQUEST_HEADERS has extensive foreign key relationships, primarily as a parent table. Its most critical child is MTL_TXN_REQUEST_LINES (via HEADER_ID), which holds the detailed items for the move order. It references master data tables for validation: MTL_PARAMETERS (ORGANIZATION_ID), MTL_SECONDARY_INVENTORIES (FROM_SUBINVENTORY_CODE and TO_SUBINVENTORY_CODE, both with ORGANIZATION_ID), GL_CODE_COMBINATIONS (TO_ACCOUNT_ID), and MTL_TRANSACTION_TYPES (TRANSACTION_TYPE_ID). It is also referenced by other transactional entities, including CSP_MOVEORDER_HEADERS, CSP_MOVEORDER_LINES, and MTL_KANBAN_CARD_ACTIVITY (DOCUMENT_HEADER_ID), highlighting its role in Kanban and Consigned Inventory processes.