Search Results wms_picking_pkg




Overview
Explore in AI Chat

Overview

APPS.WMS_PICKING_PKG is the core PL/SQL package that drives task execution within Oracle Warehouse Management (WMS) in Oracle E-Business Suite 12.1.1 and 12.2.2. It supports directed picking, label picking, cluster picking, and manual picking by retrieving task information, advancing tasks through their lifecycle, validating quantities, and breaking down move-order and task lines into lot- and serial-controlled transactions. The package header declares a versioned header line and a set of package-level global collections, including g_previous_task_status (a BINARY_INTEGER-indexed table of task status values) and g_start_over_tempid, which are used to remember prior task states as operators navigate the picking flow. A weakly typed ref cursor type t_genref is defined to return dynamically shaped task and query result sets to the calling mobile or desktop client. The package is documented under ETRM with the classification OTHER, exposes 24 procedures and functions, references core MTL and BOM tables through APPS synonyms, and is referenced by four other packages.

Key Procedures and Functions

  • GET_NEXT_TASK_INFO — returns task information to the client as a ref cursor. Inputs include sign-on employee and organization, transaction temporary ID (manual pick), cartonization ID (label picking), device ID, cluster pick flag, and carton grouping list.
  • GET_TASKS — retrieves a set of tasks, typically for a device or work area, to populate the operator's task queue.
  • NEXT_TASK — advances task navigation so the operator moves to the subsequent task in the queue.
  • CHANGE_TASK_TO_ACTIVE — transitions a task from its current status to active, taking the transaction temporary ID and returning the standard FND_API return status.
  • VALIDATE_QUANTITIES — checks that entered or suggested pick quantities are valid for the task before confirmation.
  • GET_LOT_NUMBER_INFO and GET_SERIAL_NUMBERS — return lot and serial details respectively for the item, location, or task being picked, enabling correct lot/serial selection.
  • SPLIT_TASK, SPLIT_MMTT, SPLIT_MMTT_LPN — split tasks and material transaction temporary records, including LPN-level splits.
  • SPLIT_WDT — splits WMS device/transaction records supporting the split operation.
  • SPLIT_LOT_SERIAL, SPLIT_SERIAL, SPLIT_MTLT — perform lot/serial controlled splits and split the corresponding material transaction lot temporary records.
  • INSERT_CARTONIZATION_ID, LIST_CARTONIZATION_ID, CLEAR_CARTONIZATION_ID — manage cartonization identifiers used in label and cluster picking.
  • GET_TOTAL_LPNS — reports total LPN counts associated with the pick.
  • LIST_ORDER_NUMBERS and LIST_PICK_SLIP_NUMBERS — return the sales order numbers and pick slip numbers involved in the task set.

Tables Accessed

The package reads and writes MTL_MATERIAL_TRANSACTIONS_S, MTL_MATERIAL_TRANSACTIONS_TEMP, MTL_TRANSACTION_LOTS_TEMP, MTL_SERIAL_NUMBERS, and MTL_SERIAL_NUMBERS_TEMP to build, split, and validate pending pick transactions and their lot/serial detail. MTL_SYSTEM_ITEMS and MTL_SYSTEM_ITEMS_B supply item attributes; MTL_ITEM_LOCATIONS and MTL_SECONDARY_INVENTORIES supply locator and subinventory context; MTL_PARAMETERS provides organization setup; MTL_SALES_ORDERS links picks to sales order demand; and MTL_CROSS_REFERENCES resolves item cross-references. BOM_RESOURCES, BOM_RESOURCE_EQUIPMENTS, and BOM_STD_OP_RESOURCES are used for resource and equipment associations relevant to task execution.

Usage Notes

WMS_PICKING_PKG is typically invoked during mobile picking flows driven from Oracle Mobile Supply Chain Applications (MSCA) pages and WMS picking UIs, and is also called from concurrent or custom programs that process picking tasks. Standard usage is through the documented public procedures only, observing the FND_API return status convention (FND_API.G_RET_STS_SUCCESS or G_RET_STS_ERROR) and the error code, message, and message count outputs. Because four other packages depend on it, changes should be handled as a shared interface, and customization should be limited to wrapping or calling the documented procedures rather than altering the package body directly.