Search Results move_order_type_name




Overview
Explore in AI Chat

Overview

The APPS.MTL_TXN_REQUEST_HEADERS_V view presents the header-level information of move orders (transaction requests) within Oracle E-Business Suite inventory management. It is a denormalized reporting view that joins the base move order header table to lookup and transaction type tables, exposing human-readable meanings alongside stored code values. This view is the principal read interface for retrieving move order headers together with their translated attributes, and it is widely referenced by forms, concurrent programs, and custom reporting queries across Oracle Inventory and Oracle Warehouse Management.

The view addresses a specific reporting gap: the base table MTL_TXN_REQUEST_HEADERS stores MOVE_ORDER_TYPE and HEADER_STATUS as coded values that are not self-describing. The view resolves those codes through MFG_LOOKUPS so consumers receive the display meaning directly.

Underlying Base Objects

Per the ETRM 12.2.2 metadata, the view is owned by APPS and is defined over the following referenced objects:

The joins are lookup-based, meaning each header row is enriched with decoded meanings rather than aggregating detail lines. Note that the view exposes header-level fields only; move order line and detail information resides in MTL_TXN_REQUEST_LINES and related objects.

Key Columns

Common Use Cases and Queries

The view is typically used to build move order status reports, integration extracts, and self-service queries. A representative query filters by move order type name and status name:

  • Listing move orders by type: SELECT request_number, move_order_type_name, header_status_name, organization_id FROM mtl_txn_request_headers_v WHERE move_order_type_name = 'Pick Wave';
  • Pending move orders by organization: SELECT request_number, date_required, from_subinventory_code, to_subinventory_code FROM mtl_txn_request_headers_v WHERE organization_id = :org_id AND header_status_name IN ('Pending','In-Process');
  • Integration extract: Selecting HEADER_ID, TRANSACTION_TYPE_NAME, MOVE_ORDER_TYPE_NAME, and the flexfield attributes for downstream system synchronization.

Because lookups are resolved inline, the view is preferable to reading the base table directly whenever human-readable output is required. Performance is generally acceptable for header-scoped queries; joining to MTL_TXN_REQUEST_LINES should be done on HEADER_ID.