Search Results mtl_txn_request_status




Overview
Explore in AI Chat

Overview

APPS.MTL_TXN_BACKORDERS_V is a reporting view in Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2 that exposes move order lines which could not be fully satisfied during the pick/detailed-quantity allocation process. It is defined over the move order header and line tables, and its defining filter restricts output to lines where the requested quantity exceeds the quantity that could be detailed (allocated), so the view effectively isolates backordered demand.

Because the view joins both the header and line status columns to the MTL_TXN_REQUEST_STATUS lookup type, it is directly relevant to users searching for "mtl_txn_request_status." Rather than requiring consumers to hard-code lookup meanings, the view automatically translates the stored status codes into their descriptive MEANING values, presenting readable move order and line statuses alongside backordered quantities. This makes the view suitable for operational reporting, backorder analysis, and integration extracts that must surface unfulfilled move order demand.

Underlying Base Objects

Per the documented ETRM metadata, MTL_TXN_BACKORDERS_V is owned by APPS and references the following objects:

  • MTL_TXN_REQUEST_HEADERS (synonym) — the move order header, supplying header_id, request_number, move_order_type, organization_id, date_required, header_status, and status_date.
  • MTL_TXN_REQUEST_LINES (synonym) — the move order lines, supplying line_id, item, revision, subinventory/locator details, lot/serial ranges, UOM, quantity, quantity_detailed, reason, references, project/task, transaction attributes, and strategy/cost group identifiers.
  • MFG_LOOKUPS (view) — joined three times to resolve header status, line status, and move order type codes into descriptive meanings via the MTL_TXN_REQUEST_STATUS and MOVE_ORDER_TYPE lookup types.
  • CST_COST_GROUPS (synonym) — an outer-joined source for the from-cost-group and to-cost-group descriptions.

The view is not a stored object; it is a SQL definition that associates the header to its lines on HEADER_ID, applies lookup joins to decode statuses and move order type, and restricts rows to lines where quantity_detailed is not null and quantity exceeds quantity_detailed.

Key Columns

The view exposes header-level identifying and scheduling attributes (HEADER_ID, REQUEST_NUMBER, MOVE_ORDER_TYPE and its meaning, ORGANIZATION_ID, DATE_REQUIRED, header status meaning, and STATUS_DATE) and line-level detail (LINE_ID, LINE_NUMBER, INVENTORY_ITEM_ID, REVISION, FROM/TO_SUBINVENTORY_CODE, FROM/TO_LOCATOR_ID, UOM_CODE, and line status meaning).

Central to the view's purpose is the computed column BACKORDERED_QUANTITY, defined as (QUANTITY − QUANTITY_DETAILED), which quantifies the unfulfilled portion of each line. Lot and serial controls are exposed through LOT_NUMBER, SERIAL_NUMBER_START, and SERIAL_NUMBER_END. Cost group columns (FROM_COST_GROUP_ID, TO_COST_GROUP_ID and the CST.COST_GROUP / CST2.COST_GROUP descriptions) provide costing context, while project/task and transaction reference columns link the backorder to downstream activity.

Common Use Cases and Queries

The view is typically used to report outstanding backorders and to analyze why move order demand remains unfulfilled by organization, item, or status.

  • List open backorders for an organization, ordered by required date:
SELECT request_number, move_order_type, date_required,
       inventory_item_id, backordered_quantity, line_id
FROM   apps.mtl_txn_backorders_v
WHERE  organization_id = :org_id
ORDER BY date_required;
  • Summarize backordered quantity by item:
SELECT inventory_item_id, SUM(backordered_quantity) backordered_qty
FROM   apps.mtl_txn_backorders_v
GROUP BY inventory_item_id;

Because the view already decodes MTL_TXN_REQUEST_STATUS for both header and line, operational reports can display readable statuses directly, and integration extracts can key on the same statuses the user searched for. Note that only fully or partially detailed lines with a shortfall are returned; move requests with no detail activity are excluded by the quantity_detailed IS NOT NULL predicate.