Results for “tare_weight_uom_code”

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

Overview

WMS_LICENSE_PLATE_NUMBERS is the master table in the Warehouse Management (WMS) module of Oracle E-Business Suite that stores information about license plate numbers (LPNs), also referred to as container instances. An LPN is a uniquely identified physical container—such as a pallet, carton, tote, or bin—used to group and track inventory as it moves through receiving, put-away, storage, picking, and shipping. Each row represents a single container instance and captures its identity, contents, physical dimensions, location, status, and genealogy.

The table exists in both Oracle EBS 12.1.1 and 12.2.2 and is owned by the WMS schema. It comprises 57 documented columns and is central to WMS-enabled inventory operations, where material handling is performed at the container level rather than at the individual item level. Heuristically, the mined foreign-key structure classifies WMS_LICENSE_PLATE_NUMBERS as a Data Vault hub: it carries a stable business key (the license plate number) and a surrogate primary key, with descriptive attributes that could be modeled as satellites. This classification is a modeling suggestion only and does not reflect a physical design within Oracle EBS.

Key Information Stored

• LPN_ID — the surrogate primary key (WMS_LICENSE_PLATE_NUMBERS_PK), a system-generated identifier for the container instance.
• LICENSE_PLATE_NUMBER — the business key, enforced by the unique index WMS_LICENSE_PLATE_NUMBERS_U2; this is the operator-visible identifier of the LPN.
• INVENTORY_ITEM_ID — the item associated with the LPN contents, referencing MTL_SYSTEM_ITEMS_B.
• ORGANIZATION_ID — the inventory organization that owns the LPN, referencing MTL_PARAMETERS.
• SUBINVENTORY_CODE — the subinventory in which the LPN resides, referencing MTL_SECONDARY_INVENTORIES.
• LOCATOR_ID — the specific locator within the subinventory, referencing MTL_ITEM_LOCATIONS.
• LOT_NUMBER and REVISION — lot and revision control attributes for the contained material.
• SERIAL_NUMBER — the serial number when the LPN holds serialized inventory.
• PARENT_LPN_ID and OUTERMOST_LPN_ID — the self-referencing genealogy columns that describe nested container hierarchies.
• STATUS_ID and LPN_STATE — the current status and lifecycle state of the LPN.
• GROSS_WEIGHT, TARE_WEIGHT, CONTENT_VOLUME, and CONTAINER_VOLUME — physical measurement attributes with their associated UOM codes.
• LPN_CONTEXT, LPN_REUSABILITY, and HOMOGENEOUS_CONTAINER — operational flags governing how the LPN may be used.
• SOURCE_TYPE_ID, SOURCE_HEADER_ID, SOURCE_LINE_ID, and SOURCE_NAME — the originating document reference (for example, a receipt or move order).
• COST_GROUP_ID — the cost group assignment, referencing CST_COST_GROUPS.
• Standard WHO columns (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY) plus the 15 descriptive ATTRIBUTE columns are also present.

Common Use Cases and Queries

The most frequent requirement is resolving an LPN identifier to its current contents and location, typically joining inventory on-hand for reconciliation and cycle counting:

• LPN content and location lookup — join WMS_LICENSE_PLATE_NUMBERS to WMS_LPN_CONTENTS on PARENT_LPN_ID to enumerate child LPNs or items within a container.
• Physical inventory reconciliation — the user search term mtl_physical_inventory_tags is directly relevant: MTL_PHYSICAL_INVENTORY_TAGS carries PARENT_LPN_ID and OUTERMOST_LPN_ID columns that reference this table, so physical inventory tags can be reported with their associated container context. A representative pattern is:

SELECT t.tag_number, t.parent_lpn_id, l.license_plate_number
FROM mtl_physical_inventory_tags t, wms_license_plate_numbers l
WHERE t.parent_lpn_id = l.lpn_id;

• Container hierarchy reporting — self-joins on PARENT_LPN_ID and OUTERMOST_LPN_ID expose multi-level pallet and carton structures.
• Cycle count analysis — join to MTL_CYCLE_COUNT_ENTRIES via PARENT_LPN_ID or OUTERMOST_LPN_ID to report count entries grouped by container.
• Shipping and history audit — join to WMS_SHIPPING_TRANSACTION_TEMP and WMS_LPN_HISTORIES for movement tracking.

Because the table is a hub with strong foreign-key dependencies across inventory, costing, and physical inventory modules, queries should always constrain ORGANIZATION_ID to satisfy the composite foreign keys and improve performance.

Related Objects

• WMS_LPN_CONTENTS (PARENT_LPN_ID → LPN_ID) — details of the contents held within a container.
• MTL_PHYSICAL_INVENTORY_TAGS (PARENT_LPN_ID / OUTERMOST_LPN_ID → LPN_ID) — physical inventory tag records associated with LPNs; the object that prompted the user search.
• MTL_PHYSICAL_ADJUSTMENTS (PARENT_LPN_ID / OUTERMOST_LPN_ID → LPN_ID) — adjustments generated from physical counts at container level.
• MTL_CYCLE_COUNT_ENTRIES (PARENT_LPN_ID / OUTERMOST_LPN_ID → LPN_ID) — cycle count entries linked to containers.
• MTL_SERIAL_NUMBERS (LPN_ID → LPN_ID) — the serial numbers currently residing within an LPN.
• WMS_LPN_HISTORIES (LPN_ID / PARENT_LPN_ID / OUTERMOST_LPN_ID) — transactional history of container activity.
• MTL_SYSTEM_ITEMS_B, MTL_ITEM_LOCATIONS, MTL_SECONDARY_INVENTORIES, and MTL_PARAMETERS — the referenced master tables for item, locator, subinventory, and organization context.