Results for “associate_lpn”

16 results




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

Overview

APPS.WMS_CONTAINER_PVT is the private implementation body of the Warehouse Management container (License Plate Number, or LPN) API in Oracle E-Business Suite. It encapsulates the business logic that creates, modifies, packs, unpacks, merges, and explodes LPN containers within the Warehouse Management System (WMS). LPNs are the licensable warehouse unit identifiers that track material as it moves through receiving, put-away, inventory, and shipping. Because the object is classified as a PVT package, it is not intended to be called directly by external code; it services the corresponding public API, WMS_CONTAINER_PUB, which is the supported integration point. The package is VALID in the APPS schema and, per the ETRM metadata, is referenced by 22 other packages, confirming its role as a core internal engine for container processing in both EBS 12.1.1 and 12.2.2.

Key Procedures and Functions

The documented API exposes 29 procedures and functions covering the container lifecycle:

Tables Accessed

Per the documented dependencies, the package directly references WMS_LICENSE_PLATE_NUMBERS, WMS_LICENSE_PLATE_NUMBERS_S1 and _S2 (the LPN master and its supporting tables), WMS_LPN_CONTENTS, WMS_LPN_HISTORIES and their _S history tables, and WMS_LPN_PROCESS_TEMP. It also depends on WMS_CARTNZN_WRAP, WMS_CONTAINER_PUB, WMS_DATA_TYPE_DEFINITIONS_PUB, WMS_INSTALL, WMS_USER_TASK_TYPE_ATTRIBUTES, and the WSH container/delivery tables (WSH_CONTAINER_ITEMS, WSH_DELIVERY_ASSIGNMENTS, WSH_DELIVERY_DETAILS). On the inventory side, it reads and writes MTL client parameters, item locations, material transactions, on-hand quantities detail, reservations, serial numbers, lot temp tables, and system items. These integrations allow LPN operations to trigger inventory transactions and shipping delivery assignments.

Usage Notes

Because it is a private package, WMS_CONTAINER_PVT should not be called directly by customer extensions. Applications invoking this functionality—generally through WMS_CONTAINER_PUB or via Oracle Warehouse Management forms and concurrent programs such as LPN creation and pack/unpack processors—rely on the private body to enforce validation, transaction creation, and history recording. Customizations should target the public API or the underlying inventory interfaces rather than this PVT body, since it is subject to change between patch levels.