Search Results wms_globals




Overview
Explore in AI Chat

Overview

WMS_OP_RUNTIME_PUB_APIS is the public runtime API package body for Oracle Warehouse Management (WMS) in Oracle E-Business Suite release 12.1.1 and 12.2.2. It exposes the PL/SQL entry points that the WMS runtime execution layer uses to validate and update operator-facing task actions, such as confirming or redirecting the locator into which a picked quantity is dropped. The package sits in the APPS schema and is classified as an OTHER API in the ETRM repository; it is not a stored interface registered against the standard FND_API error-handling contract, though it does call FND_API, FND_MESSAGE, and FND_PROFILE for messaging and profile lookups.

The user's search term "wms_globals" is directly relevant here: the package body depends on the WMS_GLOBALS package, which is the WMS session/context global used throughout the WMS runtime code path. It also depends on INV_GLOBALS, INV_MOBILE_HELPER_FUNCTIONS, WMS_MDC_PVT, WMS_OP_DEST_SYS_APIS, WMS_UI_TASKS_APIS, and WMS_OP_RUNTIME_PUB_APIS itself (recursive reference). These dependencies confirm the package operates inside the mobile/radio-frequency (RF) WMS execution flow rather than in batch planning.

Key Procedures and Functions

  • UPDATE_DROP_LOCATOR_FOR_TASK — Updates the drop locator associated with a dispatched warehouse task. It is used when the operator changes or confirms the destination locator at runtime, and writes the resulting locator back to the task record so downstream inventory and delivery processing sees the correct destination.
  • VALIDATE_PICK_DROP_LOCATOR — Performs validation of a candidate pick-to/drop locator against WMS rules before the operator commits the action. It returns validation results to the calling UI or task API and is the gatekeeper that prevents invalid locator assignments from reaching the database.
  • LOCK_ORG_PROC — Encapsulates organization-level locking semantics used during runtime task processing, ensuring that concurrent operator actions against the same organization/warehouse context are serialized consistently. Locking protects the integrity of tasks and locator updates during parallel RF activity.

Tables Accessed

  • WMS_DISPATCHED_TASKS — The central dispatched task record; read and updated as operators act on tasks, including locator changes.
  • WMS_OP_PLANS_B and WMS_OP_PLAN_DETAILS — The operation plan header and detail tables that define the planned put-away/pick work against which runtime tasks are executed.
  • WSH_DELIVERY_DETAILS (and the WSH_DELIVERY_ASSIGNMENTS_V view in the dependency list) — Shipping delivery detail data, consulted or updated when runtime locator actions affect outbound delivery lines.
  • MTL_MATERIAL_TRANSACTIONS_TEMP — The temporary transaction interface into which runtime material movements are staged prior to processing.
  • MTL_PARAMETERS — Organization parameters used to drive validation and defaulting logic.
  • PLITBLM — The standard PL/SQL associative-array (index-by table) type supplied under the PUBLIC synonym, used for in-memory collections inside the package.

Usage Notes

WMS_OP_RUNTIME_PUB_APIS is invoked from the WMS runtime execution layer, principally the mobile RF task UI and the task-dispatch APIs (WMS_UI_TASKS_APIS, WMS_OP_DEST_SYS_APIS) that drive operator interactions on dispatched tasks. It is not typically called by concurrent programs directly; instead it is reached through runtime task processing and, in customizations, through direct calls from extension code that needs to validate or redirect a drop locator during execution. Because it honors WMS_GLOBALS and INV_GLOBALS session context, callers should ensure the WMS and inventory global contexts are initialized (organization, user, and mode) before invoking these procedures. The package is not referenced by other database objects in ETRM, but it references two packages and is itself referenced by two packages, confirming it is a mid-tier runtime API rather than a data-layer object.