Search Results break_down_lpn

Overview

WMS_CONTAINER_PUB is the public PL/SQL API package within Oracle Warehouse Management (WMS) responsible for creating, updating, and maintaining license plate numbers (LPNs) and their container associations. In Oracle EBS 12.1.1 and 12.2.2, an LPN is the physical or logical identifier—such as a pallet, carton, or tote—used to track material through receiving, put-away, picking, packing, shipping, and manufacturing operations. The package header comment states its purpose explicitly: "This object handles the creation and updating license plate numbers." ETRM classifies it with a public scope and an active lifecycle, and it is registered under the business entity WMS_CONTAINER with the display name "License Plate Number APIs for WMS."

The package defines global constants enumerating every LPN context, including inventory, WIP, receiving, stores, pre-generated, intransit, vendor, packing, loaded-for-shipment, prepack-for-WIP, picked, and staged. These constants allow callers to signal the lifecycle state of an LPN consistently, and the package also declares a subtype based on WMS_LICENSE_PLATE_NUMBERS%ROWTYPE plus a record type for weight and volume changes. The source header identifies the shipped version as 120.6.12010000.2, and the package is referenced by 41 other packages in the E-Business Suite, confirming its role as a foundational LPN service.

Key Procedures and Functions

The documented interface exposes 17 procedures and functions:

• GENERATE_LPN — Generates a new LPN identifier, typically used for pre-generated license plates.
• CREATE_LPN — Creates an LPN record in the system for a given context.
• ASSOCIATE_LPN — Associates an existing LPN with inventory, container items, or a parent container.
• MODIFY_LPN — Updates attributes of an existing LPN.
• MODIFY_LPN_WRAPPER — A wrapper around MODIFY_LPN that simplifies modification calls; this is the API most commonly cited in implementation and support searches, as it hides the underlying complexity of LPN updates for custom integrations.
• PACKUNPACK_CONTAINER — Packs items into, or unpacks items from, a container LPN.
• PACK_PREPACK_CONTAINER — Handles prepack container packing, relevant to WIP prepack operations.
• EXPLODE_LPN — Breaks an LPN structure down into its constituent contents.
• VALIDATE_LPN — Validates an LPN against business rules and context.
• CONTAINER_REQUIRED_QTY — Returns the quantity required to fill or complete a container.
• PREPACK_LPN_CP — Concurrent-program entry point for prepack LPN processing.
• LPN_PACK_COMPLETE — Marks packing of an LPN as complete and moves it to the next state.
• MERGE_UP_LPN — Merges LPN contents upward into a parent LPN.
• BREAK_DOWN_LPN — Decomposes an LPN, releasing its contents.
• INITIALIZE_LPN — Initializes an LPN record or structure.
• REUSE_LPNS — Reuses previously consumed LPN numbers.

Tables Accessed

The package reads and writes several core WMS and Inventory tables through APPS synonyms. WMS_LICENSE_PLATE_NUMBERS and its sequence-backed synonym WMS_LICENSE_PLATE_NUMBERS_S2 hold the master LPN definition, while WMS_LPN_HISTORIES records LPN state and movement history. MTL_ITEM_LOCATIONS and MTL_SECONDARY_INVENTORIES resolve the physical storage context, and MTL_ONHAND_QUANTITIES_DETAIL supports on-hand validation and quantity checks. MTL_MATERIAL_TRANSACTIONS_TEMP, MTL_TRANSACTIONS_INTERFACE, and RCV_TRANSACTIONS_INTERFACE are used to stage inventory and receiving transactions generated by LPN operations. MTL_LOT_NUMBERS and MTL_SERIAL_NUMBERS provide lot and serial control context, MTL_RESERVATIONS supports reservation handling, and MTL_SYSTEM_ITEMS and MTL_PARAMETERS supply item and organization setup data used for validation.

Usage Notes

WMS_CONTAINER_PUB is invoked by WMS mobile pages, Oracle Warehouse Management and Inventory forms, packing and shipping workflows, and concurrent programs such as the prepack LPN processor. Custom code should call the public APIs—particularly MODIFY_LPN_WRAPPER for LPN updates—rather than updating the underlying tables directly, so that history records, context transitions, and interface staging remain consistent. Because the package validates against context constants, callers must supply the appropriate LPN context for the transaction being performed.