Skip to content
EBS Reference

MTL_TXN_REQUEST_LINES

Schema: INVtransactionPer inventory org

Move order lines — each row requests moving a quantity of an item from a source to a destination subinventory, individually statused, allocated (quantity detailed), and transacted (quantity delivered)

Module: InventoryInventory-org partitioned (ORGANIZATION_ID)Header: MTL_TXN_REQUEST_HEADERS
Notes

QUANTITY_DETAILED is the allocated quantity, QUANTITY_DELIVERED the transacted quantity — the difference against QUANTITY is the open balance. Pending allocations live in the transaction staging table until transacted.

What the badges mean
master
Data class: what the table holds — master data, transaction documents, control/configuration, interface/staging, or an APPS-schema view.
In field listings, K marks a primary-key field.

Header & line

MTL_TXN_REQUEST_LINES lines join back to their header MTL_TXN_REQUEST_HEADERS — and the org column — so a line never fans out.

Fields

14 fields · 1 key

Table fields: position, field name, description, data type, and flags. 14 fields.
#FieldDescriptionTypeFlags
1LINE_IDSurrogate key of the move order lineNUMBER
Key
2HEADER_IDThe move order header — joins to MTL_TXN_REQUEST_HEADERSNUMBER
3ORGANIZATION_IDInventory organizationNUMBER
4INVENTORY_ITEM_IDItem to moveNUMBER
5LINE_NUMBERLine number within the move orderNUMBER
6LINE_STATUSLine status — the state that actually drives allocation and transactionNUMBER
7QUANTITYRequested quantityNUMBER
8QUANTITY_DELIVEREDQuantity already transactedNUMBER
9QUANTITY_DETAILEDQuantity allocated (detailed) but not yet transactedNUMBER
10UOM_CODEUOM of the requested quantityVARCHAR2
11FROM_SUBINVENTORY_CODESource subinventoryVARCHAR2
12TO_SUBINVENTORY_CODEDestination subinventoryVARCHAR2
13LOT_NUMBERLot to move, when lot-specifiedVARCHAR2
14DATE_REQUIREDWhen the line is requiredDATE
Filter date

Field provenance: hand-curated. 1 key field.

Boilerplate SQL

Starting point for reading MTL_TXN_REQUEST_LINESon Databricks — real DATE columns need no conversion, and the org anchor and the LAST_UPDATE_DATE watermark are already in place. Set your Unity Catalog location, schema, and org values below; they’re substituted into the SQL and the copy button.

Query parameters
-- ============================================================
-- Table  : MTL_TXN_REQUEST_LINES — Move order lines — each row requests moving a quantity of an item from a source to a destination subinventory, individually statused, allocated (quantity detailed), and transacted (quantity delivered)
-- Purpose: Column-selected read of MTL_TXN_REQUEST_LINES — auto-generated from field metadata
-- Grain  : One row per inventory org (ORGANIZATION_ID) + LINE_ID
-- Notes  : Auto-generated skeleton for Oracle EBS R12 data landed in your lakehouse. Dates are real DATE/TIMESTAMP columns — no conversion needed. WHO audit columns omitted (see the quirks guide); the optional LAST_UPDATE_DATE watermark filter supports incremental extracts.
-- ============================================================
SELECT
  t.LINE_ID AS "Surrogate key of the move order line",
  t.HEADER_ID AS "The move order header — joins to MTL_TXN_REQUEST_HEADERS",
  t.ORGANIZATION_ID AS "Inventory organization",
  t.INVENTORY_ITEM_ID AS "Item to move",
  t.LINE_NUMBER AS "Line number within the move order",
  t.LINE_STATUS AS "Line status — the state that actually drives allocation and transaction",
  t.QUANTITY AS "Requested quantity",
  t.QUANTITY_DELIVERED AS "Quantity already transacted",
  t.QUANTITY_DETAILED AS "Quantity allocated (detailed) but not yet transacted",
  t.UOM_CODE AS "UOM of the requested quantity",
  t.FROM_SUBINVENTORY_CODE AS "Source subinventory",
  t.TO_SUBINVENTORY_CODE AS "Destination subinventory",
  t.LOT_NUMBER AS "Lot to move, when lot-specified",
  t.DATE_REQUIRED AS "When the line is required"
FROM <catalog>.<schema>.MTL_TXN_REQUEST_LINES t
WHERE
  t.ORGANIZATION_ID = <inventory_org_id>  -- inventory org, NOT the operating unit — see quirks guide #two-orgs
  -- AND t.LINE_ID = <LINE_ID>
  -- AND t.DATE_REQUIRED >= DATE '<DATE_FROM>'
  -- AND t.DATE_REQUIRED <= DATE '<DATE_TO>'
  -- AND t.LAST_UPDATE_DATE >= TIMESTAMP '<watermark>'  -- WHO watermark, bulk-stamped by batch jobs; see quirks guide #who-columns
ORDER BY t.LINE_ID;

7 parameters not filled: <catalog>, <schema>, <inventory_org_id>, <LINE_ID>, <DATE_FROM>, <DATE_TO>, <watermark>

Relationships

1-hop neighbors — click a table to navigate there. FND lookup decode and translation edges are highlighted; they’re the joins newcomers most often get wrong.

Join details

  • MTL_TXN_REQUEST_HEADERSMTL_TXN_REQUEST_LINESheader line · 1:N
    ON MTL_TXN_REQUEST_HEADERS.HEADER_ID = MTL_TXN_REQUEST_LINES.HEADER_ID AND MTL_TXN_REQUEST_HEADERS.ORGANIZATION_ID = MTL_TXN_REQUEST_LINES.ORGANIZATION_ID
  • MTL_TXN_REQUEST_LINESMTL_SYSTEM_ITEMS_Bforeign key · N:1
    ON MTL_TXN_REQUEST_LINES.INVENTORY_ITEM_ID = MTL_SYSTEM_ITEMS_B.INVENTORY_ITEM_ID AND MTL_TXN_REQUEST_LINES.ORGANIZATION_ID = MTL_SYSTEM_ITEMS_B.ORGANIZATION_ID

Browse more Inventorytables →

Maintained by Summit Analytics, a supply chain analytics practice. The tools and references are free — the consulting is selective.

Part of the Summit Analytics reference library.

Work with the practice →

Not affiliated with or endorsed by Oracle. Oracle and Oracle E-Business Suite are registered trademarks of Oracle and/or its affiliates.