Search Results pack_prepack_container




Overview

APPS.WMS_CONTAINER_PVT is the private PL/SQL API layer that manages License Plate Numbers (LPNs) and containers within Oracle Warehouse Management. In Oracle EBS 12.1.1 and 12.2.2 it encapsulates the core logic for creating, modifying, packing, unpacking, merging, and exploding LPNs, and for maintaining the parent/child hierarchy that represents nested containers. The package header exposes a set of global constants that define every valid LPN context value — Inventory (1), WIP (2), Receiving (3), Stores (4), Pregenerated (5), Intransit (6), Vendor (7), Packing (8), Loaded for Shipment (9), Prepack of WIP (10), Picked (11), and Loaded in Stage (12). These constants are used across WMS to indicate where an LPN physically resides. The record type LPNBulkRecType supports bulk operations by defining collection-based attributes such as LPN_ID, LICENSE_PLATE_NUMBER, PARENT_LPN_ID, OUTERMOST_LPN_ID, LPN_CONTEXT, ORGANIZATION_ID, and SUBINVENTORY_CODE. Because it is a PVT package, it is not intended as a public integration surface; it is called by WMS forms, concurrent programs, and higher-level public APIs.

Key Procedures and Functions

Tables Accessed

The package reads and writes the central LPN table WMS_LICENSE_PLATE_NUMBERS along with its sequences WMS_LICENSE_PLATE_NUMBERS_S1 and _S2. It interrogates MTL_ITEM_LOCATIONS, MTL_ONHAND_QUANTITIES_DETAIL, MTL_RESERVATIONS, and MTL_SECONDARY_INVENTORIES to resolve location, on-hand, and subinventory context. Item and lot validation uses MTL_SYSTEM_ITEMS, MTL_SERIAL_NUMBERS, MTL_SERIAL_NUMBERS_TEMP, and MTL_TRANSACTION_LOTS_TEMP. Transactional impact is recorded through MTL_MATERIAL_TRANSACTIONS_S and MTL_MATERIAL_TRANSACTIONS_TEMP. MTL_PARAMETERS and MTL_CLIENT_PARAMETERS supply organization and client-level settings.

Usage Notes

WMS_CONTAINER_PVT is invoked indirectly: WMS packing, receiving, and shipping forms call it, as do the generator concurrent programs behind GENERATE_LPN_CP and PREPACK_LPN_CP. It is referenced by 22 other packages, confirming its role as the shared private engine beneath public WMS container APIs. Custom code should not call it directly; developers are expected to use the public WMS container APIs, which in turn delegate to this package. Direct calls risk bypassing validation and the LPN context rules encoded in the constants above.