Search Results wms_parameter_pvt




Overview
Explore in AI Chat

Overview

WMS_PARAMETER_PVT is a private PL/SQL package owned by the APPS schema in Oracle E-Business Suite, classified as a PVT (private) API within the Warehouse Management System (WMS) module. Its principal business function is to encapsulate the storage, retrieval, validation, and caching of warehouse operational parameters that govern putaway, replenishment, picking, and rule execution logic. The package abstracts low-level parameter lookups — flexfield data types, capacity thresholds, and derived capacity metrics — so that higher-level WMS rule, strategy, and consistency engines obtain consistent configuration values through a single, centrally maintained interface. Because it is private, it is not intended for direct customer invocation; it supports the internal behaviour of the WMS engine and its related views and rule packages.

Key Procedures and Functions

The package exposes 65 documented procedures and functions, spanning several functional groupings.

  • Cache management: CLEARCACHE invalidates the package-level cached parameter values so that subsequent calls re-read current configuration.
  • Flexfield helpers: IFFLEXTHENAVAILABLE, GETFLEXDATATYPECODE, GETFLEXNAME, and GETFLEXDESCRIPTION resolve descriptive flexfield metadata associated with WMS parameters, returning the datatype code, flex name, and descriptive text used in parameter-driven logic.
  • Rounding utilities: ROUNDUP and ROUNDDOWN perform directional numeric rounding used in capacity and unit calculations.
  • Unit capacity metrics: GETTOTALUNITCAPACITY, GETOCCUPIEDUNITCAPACITY, GETAVAILABLEUNITCAPACITY, and GETREMAININGUNITCAPACITY report locator unit capacity, consumed units, available units, and residual capacity respectively.
  • Volume and weight capacity metrics: GETTOTALVOLUMECAPACITY, GETTOTALWEIGHTCAPACITY, GETOCCUPIEDVOLUMECAPACITY, GETOCCUPIEDWEIGHTCAPACITY, GETAVAILABLEVOLUMECAPACITY, GETAVAILABLEWEIGHTCAPACITY, GETREMAININGVOLUMECAPACITY, and GETREMAININGWEIGHTCAPACITY provide the equivalent volumetric and weight-based capacity figures used to enforce locator fill limits.
  • Combined capacity: GETMINIMUMTOTALVWCAPACITY returns the governing minimum of volume and weight total capacity, determining the binding constraint for a locator.

Tables Accessed

The package reads and writes a defined set of tables through APPS synonyms. Warehouse structure and inventory data are sourced from MTL_ITEM_LOCATIONS, MTL_ONHAND_QUANTITIES_DETAIL, MTL_SYSTEM_ITEMS, MTL_MATERIAL_TRANSACTIONS_TEMP, MTL_TRANSACTION_LOTS_TEMP, MTL_TRANSACTION_TYPES, and the move-order tables MTL_TXN_REQUEST_HEADERS and MTL_TXN_REQUEST_LINES. Order and receipt context is drawn from OE_ORDER_LINES_ALL, PO_DISTRIBUTIONS_ALL, PO_LINE_LOCATIONS_ALL, RCV_SHIPMENT_LINES, and RCV_TRANSACTIONS. PJM_PROJECT_PARAMETERS supplies project-level parameter context, while FND_APPLICATION identifies the owning application for flexfield and parameter resolution. These accesses support capacity evaluation, parameter lookup, and validation of movement and replenishment scenarios.

Usage Notes

WMS_PARAMETER_PVT is invoked indirectly rather than by end users. It is referenced by 15 other packages, including WMS_PARAMETER_EXT, WMS_PARAMETER_PVT itself (for internal recursive calls), WMS_REPLENISHMENT_PVT, WMS_RULE_PVT, WMS_STRATEGY_PVT, and rule implementations WMS_RULE_3, WMS_RULE_7, WMS_RULE_8, WMS_RULE_9, and WMS_RULE_10. It also underpins several views: WMS_ACCESS_RULES_LOV_V, WMS_PARAMETERS_LOV_V, WMS_RESTRICTIONS_V, WMS_RULES_V, WMS_RULE_CONSISTENCIES_V, and WMS_SORT_CRITERIA_V. Practically, this means the package is exercised during warehouse rule evaluation, replenishment planning, putaway capacity checks, and any LOV or view query that surfaces WMS parameters. Custom code should avoid calling the private package directly and instead use the supported public APIs or views; where capacity or parameter values are required programmatically, the corresponding WMS public interfaces are the correct integration point. CLEARCACHE should be honoured whenever underlying configuration changes, as cached values otherwise persist for the session.