Results for “parent_lpn_id”

50+ results




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

Overview

The APPS.WMS_PACKING_LPN_CONT_V view is a Warehouse Management (WMS) reporting and integration object that presents the contents of a "To LPN" (License Plate Number) within the WMS Packing Workbench form. In Oracle EBS 12.1.1 and 12.2.2, the Packing Workbench is used by warehouse personnel to build, break down, and confirm the contents of license plates during outbound packing and shipping operations. Because that form must display both the items already physically packed onto an LPN and the items proposed or staged for packing, the underlying data is assembled from several disjoint sources and reshaped into a single, uniform result set.

The view therefore functions as a presentation-layer abstraction. Rather than joining transactional, master, and LPN tables directly in the form logic, the application queries this view, which normalizes heterogeneous rows into a consistent column layout. This makes it well suited to custom reporting, reconciliation, and integration scenarios where the exact contents associated with a target LPN must be inspected. The object is owned by APPS and is marked VALID, indicating that it compiled successfully against the referenced synonyms. The user-facing search term "content_lpn_id" corresponds directly to the CONTENT_LPN_ID column described below.

Underlying Base Objects

The documented 12.2.2 metadata shows the view is defined over the following synonyms: MTL_MATERIAL_TRANSACTIONS_TEMP, MTL_SERIAL_NUMBERS, MTL_SERIAL_NUMBERS_TEMP, MTL_SYSTEM_ITEMS_KFV, MTL_TRANSACTION_LOTS_TEMP, WMS_LICENSE_PLATE_NUMBERS, and WMS_LPN_CONTENTS.

  • WMS_LPN_CONTENTS (aliased WLC) supplies packed item content, including item, revision, quantity, UOM, lot, and secondary quantity/UOM.
  • WMS_LICENSE_PLATE_NUMBERS (aliased LPN) supplies nested LPN contents, where a child LPN sits inside a parent LPN.
  • MTL_SYSTEM_ITEMS_KFV (aliased MSIK) resolves the concatenated item segment description used as the human-readable CONTENT value.
  • MTL_SERIAL_NUMBERS and MTL_SERIAL_NUMBERS_TEMP are outer-joined to bridge serial-number tracking, adjusting quantity to one per serialized unit.
  • MTL_MATERIAL_TRANSACTIONS_TEMP and MTL_TRANSACTION_LOTS_TEMP furnish the intended or pending content rows (SOURCE_TYPE_ID = 2), supporting negative quantities for reversal actions such as action 51.

The UNION ALL structure splits item content (CONTENT_TYPE_ID = 1) from nested-LPN content (CONTENT_TYPE_ID = 2), which is why CONTENT_LPN_ID is populated only for the LPN branch and null for the item branch.

Key Columns

  • SOURCE_TYPE_ID — distinguishes committed packaging content (1) from pending transaction content (2).
  • PARENT_LPN_ID — the LPN whose contents are being displayed.
  • CONTENT_TYPE_ID — 1 for an inventory item, 2 for a nested license plate.
  • CONTENT — the concatenated item segment string, or the license plate number for LPN rows.
  • CONTENT_LPN_ID — the LPN_ID of a child license plate; null when the content row is an item.
  • INVENTORY_ITEM_ID, REVISION, QUANTITY, UOM, LOT_NUMBER, SERIAL_NUMBER — item-level detail; quantity is forced to 1 for serialized rows.
  • SECONDARY_QUANTITY, SECONDARY_UOM_CODE — dual-unit-of-measure support.
  • TRANSACTION_HEADER_ID, TRANSACTION_TEMP_ID — link pending rows back to their material transaction.

Common Use Cases and Queries

Typical usage includes verifying what is packed on an outbound LPN, reconciling pending packing transactions before confirmation, and reporting nested-LPN hierarchies.

  • List item contents of a parent LPN:
    SELECT content, inventory_item_id, quantity, uom, lot_number FROM apps.wms_packing_lpn_cont_v WHERE parent_lpn_id = :lpn_id AND content_type_id = 1;
  • List nested child LPNs:
    SELECT content, content_lpn_id FROM apps.wms_packing_lpn_cont_v WHERE parent_lpn_id = :lpn_id AND content_type_id = 2;
  • Isolate pending versus committed content:
    SELECT * FROM apps.wms_packing_lpn_cont_v WHERE source_type_id = 2 AND transaction_header_id = :header_id;

Because quantities are signed for reversal actions, downstream reports should apply SUM with care when aggregating per LPN.