Results for “content_lpn_number”

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

Overview

The APPS.WSM_INV_TXNS_WIP_LOTS_V view is a reporting and integration object within the WSM (Shop Floor Management) product family of Oracle E-Business Suite. It presents a consolidated, read-only projection of shop floor material transactions tied to Work-in-Process (WIP) entities, combining inventory transaction detail with WIP lot context, transaction source classification, organization attributes, and Warehouse Management System (WMS) License Plate Number (LPN) information. The view carries an OBJECT_TYPE constant of 5, indicating that the row set represents WIP lot transactions, and the leading OBJECT_ID is populated from WIP_ENTITIES.GEN_OBJECT_ID.

The view is owned by the APPS schema and is marked VALID in the ETRM registry for 12.2.2, with equivalent availability under 12.1.1. Its primary role is to expose WIP-related material movements in a flat, denormalized structure suitable for shop floor dashboards, genealogy/where-used reporting, and downstream interfaces that require consistent lot and LPN attributes. Notably, the view exposes a TRADING_PARTNER column; consistent with the search term, this column is present but hard-coded to NULL in the view text, meaning no trading partner value is derived for WIP lot transactions.

Underlying Base Objects

The view is defined over six referenced base objects:

• MTL_MATERIAL_TRANSACTIONS (synonym) — the primary transaction fact source, supplying transaction id, date, quantity, UOM, source identifiers, and the LPN keys.
• WIP_ENTITIES (synonym) — joined on MMT.TRANSACTION_SOURCE_ID = WE.WIP_ENTITY_ID, providing the WIP entity context and GEN_OBJECT_ID.
• MTL_TXN_SOURCE_TYPES (synonym) — resolves the human-readable TRANSACTION_SOURCE_TYPE_NAME.
• MTL_PARAMETERS (synonym) — supplies the ORGANIZATION_CODE for the inventory organization.
• WMS_LICENSE_PLATE_NUMBERS (synonym) — outer-joined three times (aliases WLPN1, WLPN2, WLPN3) to resolve the transaction LPN, transfer LPN, and content LPN numbers.
• INV_OBJECT_GENEALOGY (package) — its GETSOURCE function is invoked to derive the TRANSACTION_SOURCE for source types other than 13. For source type 13, the raw TRANSACTION_SOURCE_NAME is used instead.

The join restricts rows to TRANSACTION_SOURCE_TYPE_ID = 5 (WIP) and a specific set of transaction actions: 1, 27, 30, 31, 32, 33, and 34, which correspond to WIP-related issue, completion, return, and scrap movements.

Key Columns

• OBJECT_ID / OBJECT_TYPE — WIP entity genealogy identifier and a constant 5 denoting WIP lot object class.
• ORGANIZATION_ID / ORGANIZATION_CODE — inventory organization identifier and its code.
• TRANSACTION_ID / TRANSACTION_DATE — unique material transaction identifier and its effective date.
• TRANSACTION_SOURCE_TYPE_NAME / TRANSACTION_SOURCE — the source type description and the resolved source reference (via INV_OBJECT_GENEALOGY.GETSOURCE, or the raw source name when type is 13).
• TRADING_PARTNER, PROJECT, TASK — exposed but always NULL in this view; they exist for structural parity with sibling WSM/INV transaction views and provide no trading partner attribution for WIP lots.
• TRANSACTION_QUANTITY / TRANSACTION_UOM / PRIMARY_QUANTITY — quantity in the transaction UOM and the normalized primary quantity.
• SOURCE_CODE / SOURCE_LINE_ID / TRANSACTION_TYPE_ID — originating document references and transaction type classification.
• LPN_NUMBER / TRANSFER_LPN_NUMBER / CONTENT_LPN_NUMBER — license plate numbers for the transaction, its transfer, and its content, resolved through outer joins so WIP transactions without LPNs still appear.

Common Use Cases and Queries

Typical uses include tracing shop floor material consumption against WIP jobs, reconciling LPN-tracked completions, and feeding lot genealogy reports. A representative query listing recent WIP lot transactions for one organization follows:

• SELECT object_id, transaction_id, transaction_date, transaction_source, transaction_quantity, transaction_uom, lpn_number FROM wsm_inv_txns_wip_lots_v WHERE organization_code = :org AND transaction_date >= :from_date ORDER BY transaction_date;
• SELECT transaction_source_type_name, COUNT(*), SUM(transaction_quantity) FROM wsm_inv_txns_wip_lots_v WHERE organization_id = :org_id GROUP BY transaction_source_type_name;
• SELECT t.*, w.wip_entity_name FROM wsm_inv_txns_wip_lots_v t, wip_entities w WHERE t.object_id = w.gen_object_id;

Because TRADING_PARTNER is always NULL, consumers must not rely on this view for trading-partner analysis; those attributes must be sourced from the appropriate inventory or order management views instead.