Results for “move_order_type_name”

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

Overview

APPS.MTL_TXN_BACKORDERS_V is a reporting and integration view in the Oracle E-Business Suite Inventory (INV) module. It exposes move order lines that could not be fully staged or transacted, surfacing the shortfall between the quantity originally requested on a move order line and the quantity that could actually be detailed or picked. This shortfall is published as the derived column BACKORDERED_QUANTITY, defined in the view text as (MOL.QUANTITY - MOL.QUANTITY_DETAILED).

The view is defined with a filter restricting output to genuinely short move order demand: MOL.QUANTITY_DETAILED IS NOT NULL AND MOL.QUANTITY > MOL.QUANTITY_DETAILED. Lines with no detailing performed, or those fully satisfied, are excluded. Because the view joins header, line, lookup and cost group objects in a single accessible structure, it serves as a convenient source for operational reports, alerts, and inbound integrations that monitor unfilled material movement demand rather than requiring custom joins across the move order tables. Its status is VALID and it is owned by APPS. The object is present in both EBS 12.1.1 and 12.2.2, and the documented ETRM metadata is consistent across those releases.

Underlying Base Objects

The view is defined over four referenced base objects, all resolved through APPS-owned synonyms or views:

• MTL_TXN_REQUEST_HEADERS (SYNONYM) — the move order header, aliased MOH. Supplies header-level attributes such as request number, move order type, organization, date required and header status.
• MTL_TXN_REQUEST_LINES (SYNONYM) — the move order line, aliased MOL. Supplies item, revision, subinventory and locator detail, lot and serial ranges, UOM and the quantity columns used to derive the backordered quantity.
• MFG_LOOKUPS (VIEW) — referenced three times (MFG1, MFG2, MFG3) to translate lookup codes into meanings for move order type, header status and line status.
• CST_COST_GROUPS (SYNONYM) — referenced twice (CST, CST2) via outer joins to resolve the from and to cost group names.

The header and line objects are joined on MOH.HEADER_ID = MOL.HEADER_ID. Lookup joins are equijoins constrained by lookup type (MOVE_ORDER_TYPE, MTL_TXN_REQUEST_STATUS), and the cost group joins are outer joins using the (+) operator on COST_GROUP_ID, so lines without a cost group still return.

Key Columns

• HEADER_ID, REQUEST_NUMBER — move order header identifier and user-visible request number.
• MOVE_ORDER_TYPE, MOVE_ORDER_TYPE_NAME — the lookup code and its translated meaning for the move order type.
• ORGANIZATION_ID, DATE_REQUIRED — owning inventory organization and required date for the movement.
• HEADER_STATUS, HEADER_STATUS_DATE, STATUS_DATE — translated header/line status meanings and their status timestamps.
• LINE_ID, LINE_NUMBER — move order line identity.
• INVENTORY_ITEM_ID, REVISION, UOM_CODE — item, revision and unit of measure for the line.
• FROM_SUBINVENTORY_CODE, FROM_LOCATOR_ID, TO_SUBINVENTORY_CODE, TO_LOCATOR_ID, TO_ORGANIZATION_ID — source and destination subinventory, locator and organization.
• LOT_NUMBER, SERIAL_NUMBER_START, SERIAL_NUMBER_END — lot and serial range attributes for controlled items.
• BACKORDERED_QUANTITY — the derived shortfall, computed as QUANTITY minus QUANTITY_DETAILED. This is the primary searched column.
• REASON_ID, REFERENCE, REFERENCE_TYPE_CODE, REFERENCE_ID — reason and reference context for the move order line.
• PROJECT_ID, TASK_ID — project and task references where the movement is project-related.
• TRANSACTION_HEADER_ID, TRANSACTION_TYPE_ID, TRANSACTION_SOURCE_TYPE_ID, TXN_SOURCE_ID, TXN_SOURCE_LINE_ID, TXN_SOURCE_LINE_DETAIL_ID — transaction linkage to the originating source document.
• PICK_STRATEGY_ID, PUT_AWAY_STRATEGY_ID — strategy identifiers applied to the line.
• FROM_COST_GROUP_ID, COST_GROUP, TO_COST_GROUP_ID — cost group identifiers and resolved cost group names.

Common Use Cases and Queries

Typical uses include monitoring move orders that are partially staged, driving replenishment or expediting workflows, feeding material shortage dashboards, and populating alert notifications for planners. A basic listing of backorders for one organization, ordered by required date, is:

• SELECT request_number, line_number, organization_id, inventory_item_id, uom_code, backordered_quantity, date_required FROM apps.mtl_txn_backorders_v WHERE organization_id = :org_id ORDER BY date_required, request_number, line_number;

Because the view exposes BACKORDERED_QUANTITY directly, aggregate queries are straightforward for shortage analysis by item:

• SELECT inventory_item_id, uom_code, SUM(backordered_quantity) total_backordered FROM apps.mtl_txn_backorders_v WHERE organization_id = :org_id GROUP BY inventory_item_id, uom_code ORDER BY total_backordered DESC;

Filtering by move order type or status meaning supports operational queues, for example restricted to a given MOVE_ORDER_TYPE_NAME or HEADER_STATUS. Integrations can extract the full column list to synchronize backorder demand into external planning systems, keying on HEADER_ID/LINE_ID. Note that only lines with a populated QUANTITY_DETAILED and a positive difference are returned, so fully satisfied move orders never appear.