Search Results wms_container_pub




Overview
Explore in AI Chat

Overview

WMS_CONTAINER_PUB is the public Warehouse Management Systems (WMS) API package responsible for the lifecycle management of License Plate Numbers (LPNs) and containers within Oracle E-Business Suite Release 12.1.1 and 12.2.2. An LPN represents a uniquely identified physical container — a pallet, carton, tote, or shipping unit — used to group and track inventory as it moves through receiving, warehousing, packing, and shipping operations. The package encapsulates the business logic required to create, modify, associate, pack, unpack, explode, merge, break down, and validate containers, insulating callers from the underlying table structures and validation rules.

The header identifies the source as WMSCONTB.pls and exposes a global constant g_pkg_name plus a debug facility driven by the INV_DEBUG_TRACE profile option. Debug output is routed through inv_trx_util_pub.TRACE, and a package-level transaction_history table stores pack/unpack history for the duration of a session. An internal update_shipping_details routine synchronizes weight and volume changes made to an LPN back into shipping delivery details via the WSH_CONTAINER_GRP API, reflecting the package's integration role between inventory and order fulfillment.

Key Procedures and Functions

The ETRM metadata documents seventeen public procedures and functions. Each addresses a discrete container operation:

  • CREATE_LPN / INITIALIZE_LPN — Establish a new license plate record and initialize an existing LPN context for subsequent operations.
  • GENERATE_LPN — Produce LPN numbers according to configured numbering rules.
  • MODIFY_LPN / MODIFY_LPN_WRAPPER — Update LPN attributes; the wrapper provides a simplified or alternate invocation path.
  • ASSOCIATE_LPN — Link an LPN to a parent container or business entity.
  • VALIDATE_LPN — The procedure surfaced by the user's validate_lpn search. It performs the integrity and eligibility checks that confirm an LPN may participate in a given operation before pack, unpack, or move logic proceeds.
  • PACKUNPACK_CONTAINER — The core transactional engine that packs items into or unpacks items from a container.
  • PACK_PREPACK_CONTAINER / PREPACK_LPN_CP — Support pre-packaged container scenarios, including a concurrent-program entry point.
  • EXPLODE_LPN — Recursively disassembles a container hierarchy, returning constituent contents.
  • CONTAINER_REQUIRED_QTY — Computes the quantity required to fill a container per its capacity definition.
  • LPN_PACK_COMPLETE — Signals that packing for an LPN has finished, triggering downstream status transitions.
  • MERGE_UP_LPN / BREAK_DOWN_LPN — Consolidate child LPNs into a parent, or dismantle a parent into its children.
  • REUSE_LPNS — Return eligible empty LPNs to the available pool.

Tables Accessed

The package operates against core inventory and warehouse tables through APPS synonyms. WMS_LICENSE_PLATE_NUMBERS (and its sequence, WMS_LICENSE_PLATE_NUMBERS_S2) is the primary entity for LPN identity and attributes, while WMS_LPN_HISTORIES records the audit trail of pack and unpack activity. On-hand and transaction state draw on MTL_ONHAND_QUANTITIES_DETAIL, MTL_MATERIAL_TRANSACTIONS_TEMP, and MTL_TRANSACTIONS_INTERFACE, with MTL_SERIAL_NUMBERS and MTL_LOT_NUMBERS supplying serial and lot control validation. Item and location context comes from MTL_SYSTEM_ITEMS, MTL_ITEM_LOCATIONS, MTL_SECONDARY_INVENTORIES, and MTL_PARAMETERS. Reservations and move-order references are handled through MTL_RESERVATIONS and MTL_TXN_REQUEST_LINES, and inbound receipt integration uses RCV_TRANSACTIONS_INTERFACE.

Usage Notes

WMS_CONTAINER_PUB is invoked primarily from the Oracle Warehouse Management and Inventory application forms during LPN-driven receiving, put-away, packing, and shipping transactions. It also serves as the programmatic entry point for concurrent programs such as pre-pack processing, and is referenced by 41 other packages across the EBS codebase, making it a central dependency for any custom development involving container or LPN manipulation. Custom code should call the public procedures exclusively, as the package depends on profile settings (notably INV_DEBUG_TRACE) and on the shipping integration routine to keep delivery details synchronized with LPN changes.