Search Results ic_txn_request_lines_v




Overview
Explore in AI Chat

Overview

IC_TXN_REQUEST_LINES_V is an APPS-owned reporting view in Oracle E-Business Suite (12.1.1 and 12.2.2) belonging to the GMI - Process Manufacturing Inventory product. Its documented purpose is narrow and operationally specific: it supplies the move order line data consumed by the OPM Transact Process Move Orders form (ICTOTRX.fmb), retrieving lines according to the criteria entered by the user. In practice it functions as a denormalized presentation layer over the OPM move order request tables, joining line-level inventory movement detail to transaction type and lookup descriptions so that the form and any downstream reports or interfaces can display human-readable values without repeated lookup resolution. It is not a transactional table; it exposes no inserts, updates, or deletes and is intended purely for read access. For reporting and integration purposes, it is a convenient source for move order line status, source and destination subinventory/locator pairs, lot and sublot detail, and quantity information, all resolved to a single row per move order line.

Underlying Base Objects

The view is defined over several documented base objects. IC_TXN_REQUEST_HEADERS supplies header-level context such as REQUEST_NUMBER, MOVE_ORDER_TYPE, and DESCRIPTION. IC_TXN_REQUEST_LINES provides the line detail, including inventory item, from/to subinventory and locator, quantities, lot and sublot, and line status. MTL_TRANSACTION_TYPES contributes the transaction type identifier, action identifier, and TRANSACTION_TYPE_NAME. MFG_LOOKUPS (a view) resolves the move order type into a descriptive MEANING exposed as MOVE_ORDER_TYPE_NAME. MTL_SYSTEM_ITEMS and IC_ITEM_MST are referenced for item-related joins. Because most base objects are referenced as synonyms owned outside APPS, the view presents a consolidated, schema-independent interface to OPM move order lines. Lineage therefore flows from the request header, through the request line, outward to lookup and transaction-type reference data.

Key Columns

The column set mirrors the physical line table but adds resolved descriptions and renames. Identification columns include LINE_ID, HEADER_ID, LINE_NUMBER, and REQUEST_NUMBER. Move order attributes are MOVE_ORDER_TYPE and MOVE_ORDER_TYPE_NAME. Transaction classification is carried by TRANSACTION_SOURCE_TYPE_ID, TRANSACTION_TYPE_ID, TRANSACTION_TYPE_NAME, and TRANSACTION_ACTION_ID. Inventory placement columns are ORGANIZATION_ID, INVENTORY_ITEM_ID, FROM_SUBINVENTORY_ID, FROM_SUBINVENTORY_CODE, FROM_LOCATOR_ID, TO_SUBINVENTORY_ID, TO_SUBINVENTORY_CODE, and TO_LOCATOR_ID. The searched term to_subinventory_id corresponds directly to the TO_SUBINVENTORY_ID column, the destination subinventory for the movement, paired with the readable TO_SUBINVENTORY_CODE. Quantity and scheduling detail are represented by UOM_CODE, QUANTITY, QUANTITY_DELIVERED, QUANTITY_DETAILED, and DATE_REQUIRED. Lot control is captured by LOT_NUMBER and SUBLOT_NO. Lifecycle and audit columns include LINE_STATUS, STATUS_DATE, TRANSACTION_HEADER_ID, and the standard WHO columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE). Descriptive ATTRIBUTE1 to ATTRIBUTEn columns provide the OPM flex field.

Common Use Cases and Queries

Typical scenarios include monitoring open move order lines by destination subinventory, reconciling requested versus delivered quantities, and extracting lot/sublot movements for traceability. A representative query filtering on the searched column is:

  • SELECT line_id, request_number, organization_id, inventory_item_id, from_subinventory_code, to_subinventory_id, to_subinventory_code, lot_number, quantity, quantity_delivered, line_status FROM apps.ic_txn_request_lines_v WHERE to_subinventory_id = :p_to_subinventory AND line_status = 'PENDING';
  • Reporting requested versus delivered quantities grouped by move order type: SELECT request_number, move_order_type_name, SUM(quantity) requested, SUM(quantity_delivered) delivered FROM apps.ic_txn_request_lines_v GROUP BY request_number, move_order_type_name;
  • Traceability extract by item and lot: SELECT request_number, line_number, lot_number, sublot_no, from_subinventory_code, to_subinventory_code FROM apps.ic_txn_request_lines_v WHERE inventory_item_id = :p_item AND lot_number = :p_lot;

Because the view returns one row per move order line and does not aggregate, standard filters on organization, item, subinventory, and status apply cleanly. All access is read-only and subject to the standard GMI inventory security and responsibility-based data restrictions.