Results for “txn_source_line_id”

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

Overview

IC_TXN_REQUEST_LINES is the move order line table within the Oracle E-Business Suite Process Manufacturing Inventory (GMI) module. It is owned by the GMI schema and holds the individual line-level details of inventory move orders, each of which is a directive to transfer material from a source subinventory or locator to a destination subinventory or locator within an organization. The table carries a VALID status in the ETRM 12.2.2 reference and comprises 68 documented columns. Lines are the operative unit of a move order: while the parent header (IC_TXN_REQUEST_HEADERS) establishes the overall request, the lines specify the item, quantities, source, destination, and processing status that drive execution.

From a data modeling perspective, the heuristic Data Vault classification for this object is satellite-leaning. It behaves primarily as a descriptive extension of the move order header, capturing the detailed transactional attributes that qualify the parent business entity.

Key Information Stored

The surrogate primary key of the table is LINE_ID, enforced by the IC_TXN_REQUEST_LINES_PK constraint. A second unique index, IC_TXN_REQUEST_LINES_U1, defines the business-key candidate as the combination of HEADER_ID and LINE_ID, tying each line unambiguously to its parent request.

The most significant columns include:

• HEADER_ID — foreign key to IC_TXN_REQUEST_HEADERS; identifies the parent move order.
• LINE_ID — surrogate primary key uniquely identifying the line.
• LINE_NUMBER — the sequence position of the line within the move order.
• ORGANIZATION_ID — the inventory organization in which the move is performed.
• INVENTORY_ITEM_ID — the item being moved.
• FROM_SUBINVENTORY_CODE / FROM_LOCATOR_ID — source subinventory and locator.
• TO_SUBINVENTORY_CODE / TO_LOCATOR_ID — destination subinventory and locator.
• QUANTITY, QUANTITY_DELIVERED, and QUANTITY_DETAILED — ordered, fulfilled, and detail quantities.
• UOM_CODE — unit of measure for the line quantities.
• DATE_REQUIRED — the date by which the movement is required.
• LINE_STATUS and STATUS_DATE — current processing state and its timestamp.
• TRANSACTION_HEADER_ID — linkage to the resulting inventory transaction.
• TRANSACTION_SOURCE_TYPE_ID — foreign key to MTL_TXN_SOURCE_TYPES, qualifying the transaction origin.
• The standard WHO columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE) provide audit context.

Common Use Cases and Queries

Typical reporting retrieves outstanding or completed move order lines by item, organization, or status. A representative query joins the line to its header and item master:

• Open lines by organization: select from IC_TXN_REQUEST_LINES where ORGANIZATION_ID = :org and LINE_STATUS not in ('CLOSED','CANCELLED').
• Quantity reconciliation: compare QUANTITY against QUANTITY_DELIVERED per LINE_ID to measure fulfillment.
• Source-to-destination analysis: aggregate FROM_SUBINVENTORY_CODE and TO_SUBINVENTORY_CODE to analyze internal material flow.
• Audit and lineage: join TRANSACTION_HEADER_ID to inventory transaction tables to trace the move order to its posted transaction.

These patterns support cycle-count variance investigation, warehouse replenishment reporting, and operational dashboards.

Related Objects

• IC_TXN_REQUEST_HEADERS — parent table; joined on IC_TXN_REQUEST_LINES.HEADER_ID = IC_TXN_REQUEST_HEADERS.HEADER_ID.
• MTL_TXN_SOURCE_TYPES — referenced by TRANSACTION_SOURCE_TYPE_ID to classify transaction origin.
• MTL_SYSTEM_ITEMS_B — resolves INVENTORY_ITEM_ID to item descriptions and attributes.
• MTL_ITEM_LOCATIONS — resolves FROM_LOCATOR_ID and TO_LOCATOR_ID to physical locators.
• MTL_SECONDARY_INVENTORIES — resolves subinventory codes and locators.
• MTL_MATERIAL_TRANSACTIONS — the posting target reached via TRANSACTION_HEADER_ID.

Together these objects form the move order execution chain within process manufacturing inventory.