Results for “mtl_txn_request_lines”

50+ results




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

Overview

MTL_TXN_REQUEST_LINES is the Inventory (INV) schema table that stores the individual line records of move order requests in Oracle E-Business Suite. A move order is an internal request to move material from one location to another within or across inventory organizations, and each row in this table corresponds to a single requested movement: an item, a source subinventory and locator, a destination subinventory and locator, a quantity, and a status. The table is owned by the INV schema, is documented as VALID in both 12.1.1 and 12.2.2, and contains 95 documented columns in the 12.2.2 physical schema.

The table operates as a child of MTL_TXN_REQUEST_HEADERS, which holds the move order header information such as the move order number, transaction type, and approval status. Together, headers and lines form the complete move order document used to authorize and track material movements, including subinventory transfers, inter-org transfers, and WIP-related supply movements.

Under a heuristic Data Vault classification derived from the foreign key structure, this table is a hub. It represents the core business concept of a move order line, keyed by a stable surrogate identifier, with descriptive attributes that change over the document lifecycle. This classification is a modeling suggestion and does not affect the physical structure of the table in EBS.

Key Information Stored

The primary key is LINE_ID, supported by the unique index MTL_TXN_REQUEST_LINES_PK. Two unique indexes serve as business-key candidates: MTL_TXN_REQUEST_LINES_U1 on LINE_ID and MTL_TXN_REQUEST_LINES_U2 on the combination of HEADER_ID and LINE_NUMBER. The latter establishes the natural business identity of a line: its move order header plus its line number.

Common Use Cases and Queries

Move order lines are central to warehouse operations, including picking, put-away, staging, and inter-org replenishment. Typical reporting scenarios include open move orders by organization and item, aging of undelivered lines, and reconciliation between requested and delivered quantities.

A query for open lines by organization might join headers and lines as follows:

  • SELECT l.line_id, h.request_number, l.line_number, l.inventory_item_id, l.quantity, l.line_status FROM mtl_txn_request_headers h, mtl_txn_request_lines l WHERE h.header_id = l.header_id AND l.organization_id = :org_id AND l.line_status < 5 ORDER BY l.date_required;

To trace actual executions against a move order line, join to MTL_MATERIAL_TRANSACTIONS.MOVE_ORDER_LINE_ID, which records the completed inventory transaction. Comparing QUANTITY with QUANTITY_DELIVERED identifies partially fulfilled lines and supports backorder analysis. Move order line data also feeds picking and shipping workflows through CSP_PICKLIST_LINES, CSP_PACKLIST_LINES, and CSP_MOVEORDER_LINES.

Related Objects

The most significant related objects, based on the documented foreign key relationships, are: