Search Results wms_container_grp




Overview
Explore in AI Chat

Overview

WMS_CONTAINER_GRP is a PL/SQL package owned by the APPS schema in Oracle E-Business Suite and is classified as a Group (GRP) package within Oracle Warehouse Management. Its principal business function is the management of License Plate Numbers (LPNs) — the uniquely identified containers used to group, track, and move inventory in a warehouse. The package encapsulates the core LPN lifecycle operations: automatic generation, explicit creation, modification, and purge. Because LPNs are the physical and logical units that Oracle WMS and Oracle Shipping Execution use to model container contents and movement, this package sits beneath higher-level shipping and warehouse transactions rather than being invoked directly by end users.

The ETRM metadata records the package as VALID with four documented procedures: AUTO_CREATE_LPNS, CREATE_LPNS, MODIFY_LPNS, and LPN_PURGE_ACTIONS. It references APPS.WMS_DATA_TYPE_DEFINITIONS_PUB and the SYS.STANDARD package, and it is referenced by five other packages, indicating that it is a foundational utility within the WMS/WSH integration stack.

Key Procedures and Functions

  • AUTO_CREATE_LPNS — Generates LPNs automatically according to the container and numbering rules configured in Oracle WMS. It is the procedure used when the system, rather than the operator, is responsible for producing the next container identifier during an inbound, internal, or outbound flow.
  • CREATE_LPNS — Creates LPN records explicitly when the LPN identifier or attributes are supplied rather than derived from automatic numbering rules. This supports scenarios in which a user or calling process specifies the container to be instantiated.
  • MODIFY_LPNS — Applies updates to existing LPN records, such as changes to container attributes or contents associations, maintaining the integrity of the container hierarchy.
  • LPN_PURGE_ACTIONS — Performs the purge-related processing required to remove or deactivate LPN data as part of housekeeping and data-retention activity, consistent with the shipping purge facilities that reference this package.

The metadata also lists a package-level reference to WMS_DATA_TYPE_DEFINITIONS_PUB, which supplies data type definitions consumed by these LPN operations.

Tables Accessed

The documented table referenced through APPS synonyms is PLITBLM. In Oracle EBS this is a temporary (global temporary) table used by SQL*Loader and bulk-processing routines to stage rows during large data operations. WMS_CONTAINER_GRP uses PLITBLM as a staging area while performing bulk LPN creation, modification, or purge processing, allowing set-based operations over many LPN records instead of row-by-row DML. No base application tables are listed in the ETRM excerpt; the substantive LPN data resides in the WMS container tables managed by Oracle Warehouse Management, which are accessed through this package's logic rather than documented as direct table dependencies.

Usage Notes

WMS_CONTAINER_GRP is an internal, group-level API and is not intended for direct invocation by end users. The ETRM dependency list shows it is referenced by WSH_CONTAINER_ACTIONS, WSH_DELIVERY_DETAILS_GRP, WSH_LPN_SYNC_COMM_PKG, WSH_PURGE, and WSH_UTIL_CORE — that is, by Oracle Shipping Execution's container, delivery detail, LPN synchronization, purge, and utility packages. Practically, this means the package is invoked indirectly whenever shipping transactions require LPN creation or maintenance, or when the purge processes clean up obsolete container data.

Custom code should call the documented WMS public APIs or the higher-level WSH packages rather than this group package, since its signature is not published for external use and may change between releases. Where custom extensions must manipulate LPNs, they should be developed against the referenced WMS_DATA_TYPE_DEFINITIONS_PUB and the supported public interfaces. As with all APPS-owned seeded code, the package should never be modified directly; any required change must be handled through supported Oracle customization mechanisms or the corresponding public API. Its behavior is consistent across Oracle EBS 12.1.1 and 12.2.2, with the 12.2.2 metadata confirming a VALID status in the ETRM repository.