Search Results wms_quantity_required

Overview

WMS_CONTAINER_GRP is the container (License Plate Number, or LPN) management group package in Oracle Warehouse Management. It provides the core programmatic interface through which Oracle EBS creates, modifies, and purges LPNs — the uniquely identified containers that hold inventory in a warehouse. In Oracle EBS 12.1.1 and 12.2.2, LPNs underpin license-plate-driven receiving, putaway, picking, and shipping, so the procedures in this package are invoked whenever the system must generate or change container records. The header comment ($Header: WMSGCNTB.pls 120.5 2005/08/05 16:23:22 qxliu noship $) shows an established, stable code line that has been maintained across releases. The package follows Oracle's standard API conventions: it declares a package-name constant (g_pkg_name), a version constant (g_pkg_version), debug-level constants (G_ERROR, G_INFO, G_MESSAGE), a private mdebug tracing helper that routes messages to INV_TRX_UTIL_PUB.TRACE, and public APIs with p_api_version, p_init_msg_list, p_commit, and standard x_return_status/x_msg_count/x_msg_data out parameters. Inputs and outputs are built from WMS_Data_Type_Definitions_PUB record and table types, keeping the interface consistent with other WMS public APIs. The package is classified in ETRM as a GRP (group) package and is referenced by five other packages, confirming its role as a shared, low-level utility layer rather than a stand-alone user-facing program.

Key Procedures and Functions

• AUTO_CREATE_LPNS — Generates LPNs automatically based on a caller-supplied generation record. The parameter p_gen_lpn_rec (type WMS_Data_Type_Definitions_PUB.AutoCreateLPNRecordType) drives creation, and results are returned in p_lpn_table (type LPNTableType). The body validates required inputs — for example, organization_id (raising INV_ORG_REQUIRED) and quantity (raising WMS_QUANTITY_REQUIRED) — before raising fnd_api.g_exc_error. Internal locals such as l_ucc_128_suffix_flag, l_serial_range, and l_lpn_attr indicate that LPN numbering honours UCC-128 conventions and serial ranges.
• CREATE_LPNS — Creates LPN records explicitly, complementing the automatic generation path. It is the documented entry point used when a caller supplies specific LPN identities rather than asking the system to generate them.
• MODIFY_LPNS — The procedure most often searched for ("modify_lpns"). It updates existing LPN records, supporting changes to container attributes without recreating the LPN. Because callers depend on this routine, it is one of the principal reasons applications reference WMS_CONTAINER_GRP.
• LPN_PURGE_ACTIONS — Handles purge processing for LPNs, removing or deactivating container records as part of housekeeping and data-retention operations.

Tables Accessed

The documented table reference for this package is PLITBLM, accessed through an APPS synonym. In the WMS schema this is the LPN/container transaction and inventory-adjacent base table underlying LPN persistence; the create, modify, and purge procedures read and write against it to maintain container state. All access is performed against APPS synonyms, so custom code should reference the same synonyms rather than the underlying WMS-owned objects.

Usage Notes

WMS_CONTAINER_GRP is an internal group API rather than a user-invoked program. It is called by WMS application forms, concurrent programs, and other WMS public packages (five documented referencing packages) whenever LPNs must be generated, altered, or purged. Because it is classified GRP, Oracle does not guarantee the same backward-compatibility commitment attached to fully supported public APIs, so customizations should treat the procedures as semi-private. Custom code that must modify LPNs should prefer the supported public wrapper APIs where one exists, or call MODIFY_LPNS carefully while supplying correct p_api_version and p_init_msg_list values and always checking x_return_status against fnd_api.g_ret_sts_success. Debug tracing is enabled through the INV_DEBUG_TRACE profile option, which raises the level consumed by mdebug. Ordering of operations matters: Auto_Create_LPNs validates organization and quantity before doing any work and signals errors via the FND message stack, so invoking code must call FND_MSG_PUB utilities to retrieve messages after a failure. As with all WMS container activity, all calls must execute in the correct inventory organization context.