Search Results item_serial_control_code

Overview

WMS_COST_GROUPS_INPUT_V is a reporting and integration view owned by the APPS schema in Oracle E-Business Suite, validated as VALID in both 12.1.1 and 12.2.2. It resides in the WMS (Warehouse Management) product family and is documented in ETRM as the canonical input structure for the WMS cost group rules engine. Functionally, the view joins MTL_TXN_REQUEST_LINES with MTL_MATERIAL_TRANSACTIONS_TEMP so that pending, unprocessed material transaction lines are presented alongside the corresponding move order line attributes. A single row returned from this view serves as the input record consumed by the WMS cost group rules engine. In practice, the view exposes the union of move-order context (source and destination subinventory, locator, project, task, reference information) and the pending transaction context (item, revision, lot, serial range, quantity, UOM, and transaction type). It is used both by the cost group rules engine internally and by technical consultants performing diagnostics on why a given move order was assigned a particular cost group.

Underlying Base Objects

The documented base objects referenced by the view are:

• MTL_TXN_REQUEST_LINES (synonym) — the move order line that drives the record.
• MTL_MATERIAL_TRANSACTIONS_TEMP (synonym) — the pending transaction row that will be costed.
• MTL_INTERORG_PARAMETERS (synonym) — provides inter-org transfer control parameters.
• MTL_TRANSACTION_TYPES (synonym) — classifies the transaction being processed.
• MTL_SERIAL_NUMBERS (synonym) and MTL_SERIAL_NUMBERS_TEMP (synonym) — serial context for the transaction.
• MTL_TRANSACTION_LOTS_TEMP (synonym) — lot context for the pending transaction.
• WMS_COSTGROUPENGINE_PVT (package) — the PL/SQL package that consumes the view's rows as rules engine input.

Because most of these objects are APPS synonyms, the view resolves to INV and WMS base tables in the underlying schema. The join between MTL_TXN_REQUEST_LINES and MTL_MATERIAL_TRANSACTIONS_TEMP is the defining characteristic of the view: it correlates the move order line identity with the in-flight transaction so that cost group rules can be evaluated before the transaction is posted to MTL_MATERIAL_TRANSACTIONS.

Key Columns

The view exposes the combined column list of the move order line and the corresponding pending transaction. Columns of primary interest include:

• LINE_ID, HEADER_ID, LINE_NUMBER — identify the move order line.
• ORGANIZATION_ID — the inventory organization in which the transaction occurs.
• INVENTORY_ITEM_ID, REVISION — the item being moved.
• FROM_SUBINVENTORY_ID / FROM_SUBINVENTORY_CODE, FROM_LOCATOR_ID — source location.
• TO_SUBINVENTORY_ID / TO_SUBINVENTORY_CODE, TO_LOCATOR_ID, TO_ACCOUNT_ID — destination location and the destination account, which is central to cost group assignment.
• LOT_NUMBER, SERIAL_NUMBER_START, SERIAL_NUMBER_END — lot and serial identification.
• UOM_CODE, QUANTITY, QUANTITY_DELIVERED, QUANTITY_DETAILED — quantities to be transacted.
• DATE_REQUIRED, REASON_ID, REFERENCE, REFERENCE_TYPE_CODE, REFERENCE_ID — scheduling and reference context.
• PROJECT_ID, TASK_ID — project accounting context.
• TRANSACTION_HEADER_ID, LINE_STATUS, STATUS_DATE — transaction processing status.
• ATTRIBUTE1 through ATTRIBUTE10 — descriptive flexfield segments carried from the move order line.
• Standard who columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN, REQUEST_ID, PROGRAM_ID, PROGRAM_APPLICATION_ID, PROGRAM_UPDATE_DATE).

Common Use Cases and Queries

The most frequent use cases are (1) diagnosing why a move order was assigned a particular cost group by inspecting the input row that fed WMS_COSTGROUPENGINE_PVT, and (2) auditing pending move order lines whose destination account or subinventory drives cost group derivation. A representative query auditing destination attributes for a pending move order is:

• SELECT line_id, header_id, organization_id, inventory_item_id, from_subinventory_code, to_subinventory_code, to_account_id, quantity, uom_code, line_status FROM apps.wms_cost_groups_input_v WHERE organization_id = :org_id AND header_id = :header_id;
• SELECT to_account_id, COUNT(*) FROM apps.wms_cost_groups_input_v WHERE organization_id = :org_id GROUP BY to_account_id ORDER BY 2 DESC;
• SELECT a.line_id, a.inventory_item_id, a.to_subinventory_code, b.transaction_type_name FROM apps.wms_cost_groups_input_v a, mtl_transaction_types b WHERE a.organization_id = :org_id AND a.attribute1 = b.transaction_type_name;

Because the view populates from MTL_MATERIAL_TRANSACTIONS_TEMP, it is transient: rows appear only while pending transactions exist. Queries should therefore be run during or immediately after move order processing. The user search term "transportation_account" does not map to a documented column on this view; the destination accounting context is exposed through TO_ACCOUNT_ID, and transportation-related accounts are typically held on the shipping or inter-org parameters rather than projected directly through this view.