Search Results check_exp_lot_txn_allowed

Overview

WMS_ENGINE_PVT is the core private engine package within the Oracle Warehouse Management (WMS) module of Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2. It owns the schema APPS and carries the PVT (private) API classification, meaning it is intended strictly for internal consumption by other WMS and Inventory packages rather than for direct invocation by external or customer-facing code. Business-functionally, the package encapsulates the picking, reservation, and suggestion-generation logic that drives warehouse task execution. When a warehouse operator or an automated process requires the system to propose the most appropriate material handling strategy, license plate, locator, or lot, that determination is executed inside this package.

The package is documented as VALID in the ETRM registry and forms part of the WMS engine layer, sitting beneath the strategy, rule, cost group, replenishment, and task dispatch components. Because it is classified as private, Oracle does not publish a supported public signature; the metadata exposes only its dependency footprint and the two documented entry points described below.

Key Procedures and Functions

• CREATE_SUGGESTIONS — Generates WMS engine suggestions used to drive picking, task generation, and strategy resolution. This is the principal mechanism by which the engine evaluates incoming demand and produces recommended sources, locators, or license plates. It relies on the strategy and rule definitions to rank candidates.
• CHECK_EXP_LOT_TXN_ALLOWED — Evaluates whether a lot-controlled transaction is permitted against expiration and lot constraints for a given item, locator, or transaction type context. It provides the compliance gate that prevents expiry-sensitive or disallowed lot movements.

No public parameter lists are documented in the ETRM metadata for either entry point; the two procedures are strictly internal support routines invoked by sibling packages.

Tables Accessed

Through APPS synonyms the package touches setup, transactional, and interface tables:

• Setup and control: MTL_PARAMETERS, MTL_SYSTEM_ITEMS, MTL_SECONDARY_INVENTORIES, MTL_TRANSACTION_TYPES, PJM_ORG_PARAMETERS, WMS_STRATEGIES_B, WMS_RULES_B — these supply organizational defaults, item attributes, subinventory definitions, valid transaction types, strategy master data, and rule definitions that guide suggestion generation.
• Transactional and demand: MTL_RESERVATIONS, MTL_TXN_REQUEST_HEADERS, MTL_TXN_REQUEST_LINES, WIP_ENTITIES — reservation balances, move order headers and lines, and WIP entities that represent demand to be satisfied.
• LPN and staging: WMS_LICENSE_PLATE_NUMBERS, WMS_LPN_CONTENTS — license plate identity and contents used for LPN-directed picking.
• Interface/working tables: WMS_TRANSACTIONS_TEMP, WMS_TRANSACTIONS_TEMP_S — transient staging used during engine computation.

Usage Notes

WMS_ENGINE_PVT is not called directly from Oracle Forms or concurrent program definitions. It is referenced by twelve sibling packages including GME_PICKING_PVT, INV_PPENGINE_PVT, INV_SELECT_INVENTORY_PKG, WMS_COSTGROUPENGINE_PVT, WMS_REPLENISHMENT_PVT, WMS_RULE_PVT, WMS_RULE_EXTN_PVT, WMS_STATEGY_PVT, WMS_TASK_DISPATCH_GEN, WMS_SEARCH_ORDER_GLOBALS_PVT, WMS_UT_PKG, and its own body. These callers invoke it during pick release, move order processing, replenishment, and task dispatch execution. Because it is self-referential and appears in the dependency list of every major WMS engine component, any custom extension should be limited to the supported extension hooks in WMS_RULE_EXTN_PVT rather than direct calls into WMS_ENGINE_PVT. Compilation order matters during patching: the package depends on FND_API, INV_RESERVATION_GLOBAL, and WMS_SEARCH_ORDER_GLOBALS_PVT, so those must be valid before invalidation recovery is attempted. Code referencing this package in custom deployments should use the APPS synonym and rely on the private engine only as an indirect, version-agnostic integration point.