Search Results is_express_pick_task




Overview

WMS_EXPRESS_PICK_TASK is an Oracle Warehouse Management (WMS) PL/SQL package owned by the APPS schema. It encapsulates the server-side logic used to load, stage, and drop express pick tasks within an Oracle E-Business Suite warehouse. Express picking allows an operator to build a picked load on a staging or drop location using a small number of consolidated transactions, rather than stepping through every directed task individually. The package supplies the validation, task creation, and disposition logic that underlies this accelerated material handling workflow. It is declared with AUTHID CURRENT_USER and includes a PRAGMA RESTRICT_REFERENCES directive, indicating that it does not read or write package or database state through the WNDS and WNPS constraints.

Key Procedures and Functions

  • LOAD_AND_DROP — Performs the combined load-and-drop operation, moving material into the target LPN, subinventory, or locator and confirming the resulting task activity for the organization.
  • LOAD_TASK — Creates and loads an express pick task against a template and license plate. In the context of the searched term "load_task," this is the entry point most frequently invoked by picking UIs and custom integrations to instantiate an express pick task.
  • DROP_TASK — Drops a previously loaded express pick task to a destination subinventory or locator, recording the drop against the license plate and task type.
  • HAS_EXPRESS_PICK_TASKS — Determines whether the given user and organization currently have express pick tasks in progress, typically used to branch UI behavior.
  • IS_EXPRESS_PICK_TASK — Returns a value indicating whether a supplied task identifier corresponds to an express pick task.
  • IS_EXPRESS_PICK_TASK_ELIGIBLE — Returns a value indicating whether a given transaction template is eligible for express pick processing.

Tables Accessed

Usage Notes

WMS_EXPRESS_PICK_TASK is an internal warehouse execution API rather than a formally published public interface, and Oracle does not guarantee signature stability across releases. It is normally called from WMS mobile and desktop picking flows, which invoke LOAD_TASK and DROP_TASK as the operator confirms loads and drops, and from concurrent or background processes that complete or reconcile express picks. Custom or third-party code may call LOAD_TASK directly to script express pick creation, but should do so defensively: the standard output convention consists of a return status, a message count, and a message data buffer, and callers must inspect X_RETURN_STATUS rather than relying on unhandled exceptions. Because two other packages reference this one, changes to its behavior can propagate to dependent warehouse logic, and any customization should be regression-tested against standard picking in both 12.1.1 and 12.2.2.