Search Results header_status_name

Overview

MTL_TXN_REQUEST_HEADERS_V is an APPS-owned Oracle E-Business Suite view in the Inventory (INV) product module. It presents the header-level information for move order transactions — internal material transfer requisitions managed within Oracle Inventory — in a denormalized, report-ready form. The view joins the base move order header table to transaction type and lookup definitions so that consumers receive descriptive names alongside the raw coded identifiers. It is a standard, VALID object in both the 12.1.1 and 12.2.2 releases, and it is commonly used as a read-only data source in reports, conversions, integrations, and programmatic queries against move order data.

The view is particularly relevant to users searching on to_subinventory_code, because that column is exposed directly by the view. It carries the destination subinventory for the move order header, making the view a convenient single source for evaluating where material is being directed without joining to the underlying header table manually.

Underlying Base Objects

Per the documented metadata, the view is defined over the following referenced base objects:

• MTL_TXN_REQUEST_HEADERS (SYNONYM) — the primary source of header data, aliased as MTRH. It supplies the core columns: HEADER_ID, REQUEST_NUMBER, ORGANIZATION_ID, FROM_SUBINVENTORY_CODE, TO_SUBINVENTORY_CODE, HEADER_STATUS, DATE_REQUIRED, the ATTRIBUTE1–15 flex columns, and audit columns.
• MTL_TRANSACTION_TYPES (SYNONYM) — aliased as MTT, providing TRANSACTION_TYPE_NAME and the TRANSACTION_ACTION_ID that classify the move order.
• MFG_LOOKUPS (VIEW) — joined twice (MFG1 and MFG2) to decode lookup meanings. MFG1 resolves MOVE_ORDER_TYPE_NAME, and MFG2 resolves HEADER_STATUS_NAME, both driven by the appropriate lookup_type values.

The join to MFG_LOOKUPS is what converts internal codes (move order type and header status) into user-facing meanings, sparing the report author from performing the lookup translation independently.

Key Columns

• HEADER_ID — primary identifier of the move order header; useful for joining to detail lines in MTL_TXN_REQUEST_LINES.
• REQUEST_NUMBER — the user-visible move order number.
• TRANSACTION_TYPE_ID / TRANSACTION_TYPE_NAME — the transaction type classification and its descriptive name.
• MOVE_ORDER_TYPE / MOVE_ORDER_TYPE_NAME — the move order type code and decoded lookup meaning.
• ORGANIZATION_ID — the inventory organization that owns the move order.
• FROM_SUBINVENTORY_CODE / TO_SUBINVENTORY_CODE — source and destination subinventories. The to_subinventory_code column answers where material is being received.
• TO_ACCOUNT_ID / SHIP_TO_LOCATION_ID — destination account and ship-to location for the transfer.
• HEADER_STATUS / HEADER_STATUS_NAME — the workflow status code and its decoded meaning.
• DATE_REQUIRED, STATUS_DATE — required completion date and status change date.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–15 — descriptive flexfield values.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE — standard audit columns.

Common Use Cases and Queries

The view supports move order status reporting, transfer destination analysis, and integration extracts. A typical query filtering on the requested column:

• Report all move orders directed to a specific subinventory.
• Reconcile header status against required dates for open move orders.
• Extract header data with decoded type and status for downstream systems.

Sample SQL:

SELECT h.request_number,
       h.organization_id,
       h.from_subinventory_code,
       h.to_subinventory_code,
       h.transaction_type_name,
       h.header_status_name,
       h.date_required
  FROM apps.mtl_txn_request_headers_v h
 WHERE h.to_subinventory_code = :p_to_subinventory
   AND h.header_status_name = 'Approved';

Because the view already decodes status and type, it is well suited to ad-hoc reporting and to integration interfaces that must present human-readable move order information.