Results for “from_sub_asset”

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

Overview

MTL_TXN_REQUEST_LINES_V is an APPS-owned reporting view in the Oracle Inventory (INV) module that exposes move order line detail in a denormalized, query-friendly form. It joins the move order header and line tables (MTL_TXN_REQUEST_HEADERS and MTL_TXN_REQUEST_LINES) to lookup and transaction type definitions, returning both the raw transaction source and type identifiers and their human-readable names. Because it carries the full lifecycle of a move order line — source and destination subinventory/locator, item and revision, quantities, dates, status, and reference context — it serves as the primary read-only access point for move order data in Oracle EBS 12.1.1 and 12.2.2.

For users searching on txn_source_id, the relevant point is that this view does not expose a column literally named TXN_SOURCE_ID. Transaction source is surfaced through TRANSACTION_SOURCE_TYPE_ID, sourced from MTL_TRANSACTION_TYPES. The txn_source_id term typically maps here to the transaction source type identifier and the associated transaction type columns.

Underlying Base Objects

The view is defined over the following documented objects:

• MTL_TXN_REQUEST_HEADERS — move order header; supplies REQUEST_NUMBER, MOVE_ORDER_TYPE, and DESCRIPTION.
• MTL_TXN_REQUEST_LINES — move order line detail; the core driver of the view.
• MTL_TRANSACTION_TYPES — supplies TRANSACTION_SOURCE_TYPE_ID, TRANSACTION_TYPE_NAME, and TRANSACTION_ACTION_ID.
• MFG_LOOKUPS — resolves MOVE_ORDER_TYPE to its meaning via MOVE_ORDER_TYPE_NAME.
• MTL_SECONDARY_INVENTORIES — joined twice (aliases MSS, MSS1) to enrich from/to subinventory attributes such as locator type, asset flag, quantity-tracked, and material account.
• CST_COST_GROUPS and WMS_LICENSE_PLATE_NUMBERS — supporting cost group and LPN references.

The header/line relationship is keyed on HEADER_ID, with the line's LINE_ID acting as the view's primary identifier.

Key Columns

• LINE_ID, HEADER_ID, LINE_NUMBER — line identity and grouping.
• TRANSACTION_SOURCE_TYPE_ID, TRANSACTION_TYPE_ID, TRANSACTION_TYPE_NAME, TRANSACTION_ACTION_ID — transaction classification (the practical txn_source_id equivalent is the source type ID).
• ORGANIZATION_ID, INVENTORY_ITEM_ID, REVISION, UOM_CODE — item and inventory context.
• FROM_SUBINVENTORY_ID/TO_SUBINVENTORY_ID, FROM_LOCATOR_ID/TO_LOCATOR_ID, plus FROM_/TO_SUB_LOCATOR_TYPE and related secondary attributes.
• QUANTITY, REQUIRED_QUANTITY, QUANTITY_DELIVERED, QUANTITY_DETAILED, DATE_REQUIRED — demand fulfillment metrics.
• LOT_NUMBER, SERIAL_NUMBER_START, SERIAL_NUMBER_END, REFERENCE, REFERENCE_TYPE_CODE, REFERENCE_ID, PROJECT_ID, TASK_ID, LINE_STATUS, STATUS_DATE — traceability and lifecycle.

Common Use Cases and Queries

Typical uses include move order reporting, fulfillment tracking, integration extracts, and source/type analysis. A basic query returns open lines by source type:

• SELECT request_number, line_number, transaction_source_type_id, transaction_type_name, inventory_item_id, quantity, line_status FROM mtl_txn_request_lines_v WHERE organization_id = :org AND line_status < 4;
• SELECT transaction_source_type_id, transaction_type_name, COUNT(*) FROM mtl_txn_request_lines_v GROUP BY transaction_source_type_id, transaction_type_name;
• SELECT request_number, from_subinventory_code, to_subinventory_code, quantity_delivered, required_quantity FROM mtl_txn_request_lines_v WHERE quantity_delivered < required_quantity;

The view is read-only and best used for reporting; for transactional updates, the underlying base tables should be used directly.