Search Results wms_transactions_temp_s

Overview

WMS_ENGINE_PVT is the private engine package body within the Oracle Warehouse Management (WMS) module of Oracle E-Business Suite, owned by the APPS schema. It encapsulates the core putaway, replenishment, and rule-evaluation logic that drives the WMS directed-movement engine. The package is classified as a PVT (private) API, meaning it is not intended as a public integration surface; instead, it is invoked by other WMS packages and by the warehouse execution user interface to compute suggested tasks and validate transaction feasibility. In EBS 12.1.1 and 12.2.2, the body coordinates access to inventory and warehouse setup tables, evaluates WMS rules and strategies, and stages intermediate transaction data in temporary tables before the results are consumed by downstream WMS processing. Because APPS.WMS_ENGINE_PVT is not referenced by any database object at the schema-dependency level, it functions as an internal implementation unit whose entry points are called dynamically or through cooperating packages rather than through stored dependencies.

Key Procedures and Functions

• CREATE_SUGGESTIONS — Generates movement or task suggestions based on WMS rule and strategy evaluation. This routine is the principal entry point for producing recommended directed tasks, drawing on rule definitions, strategy assignments, and item/organization setup to determine the appropriate destination or source location.
• CHECK_EXP_LOT_TXN_ALLOWED — Validates whether an expiration-controlled lot transaction is permitted under the current configuration and transaction context. It enforces lot and expiration business rules before a transaction is accepted, returning a determination that the calling process uses to allow or reject the operation.

Tables Accessed

The package reads and writes a broad set of inventory, warehouse, and staging tables, all referenced through APPS synonyms:

• MTL_PARAMETERS, MTL_SECONDARY_INVENTORIES, MTL_SYSTEM_ITEMS, MTL_UNITS_OF_MEASURE_VL, MTL_TRANSACTION_TYPES — Master and organization-level inventory setup used to interpret item attributes, subinventory definitions, and valid transaction types.
• MTL_RESERVATIONS, MTL_TXN_REQUEST_HEADERS, MTL_TXN_REQUEST_LINES — Reservation and move-order data required when suggestions translate into executable material movements.
• WMS_LICENSE_PLATE_NUMBERS, WMS_LPN_CONTENTS — License plate (LPN) identity and contents, central to LPN-directed warehouse operations.
• WMS_RULES_B, WMS_STRATEGIES_B — Rule and strategy definitions that drive the suggestion logic.
• WMS_TRANSACTIONS_TEMP, WMS_TRANSACTIONS_TEMP_S — Temporary staging tables where transaction records are assembled prior to posting or interface processing. The _S table is the sequence-backed companion used to generate staging keys.
• WIP_ENTITIES, PJM_ORG_PARAMETERS — Work-in-process entity and project/organization parameters referenced during rule evaluation.

Usage Notes

WMS_ENGINE_PVT is invoked from within the WMS engine and related private packages rather than directly from public APIs. It is typically executed in the context of warehouse execution forms, directed putaway and replenishment flows, and concurrent or background processes that need rule-based suggestions. The CREATE_SUGGESTIONS routine is called when the system must derive recommended tasks, while CHECK_EXP_LOT_TXN_ALLOWED is called as a validation gate during lot- and expiration-controlled transactions. Because the package is referenced by twelve other packages yet references none at the schema level, customizations should avoid calling it directly and should instead rely on the supported public WMS APIs. The presence of WMS_TRANSACTIONS_TEMP and WMS_TRANSACTIONS_TEMP_S in its dependency list is significant for troubleshooting: these are transient staging structures, and residual rows can indicate interrupted engine processing, making them a common target during diagnostic investigation of WMS transaction failures.