Search Results check_loose_quantity

Overview

The APPS.WMS_EXPRESS_PICK_TASK package body is a Warehouse Management System (WMS) component in Oracle E-Business Suite Release 12.1.1 and 12.2.2 that supports the Express Pick workflow for outbound logistics. Express Pick enables warehouse operators working in a mobile or desktop picking environment to consolidate the selection, loading, and dropping of material onto a staging or dispatch location within fewer operator interactions than the standard pick-confirm-putaway cycle. The package encapsulates the business logic that drives this accelerated flow, exposing public procedures for loading a picked task to a destination, dropping it, and for validating whether a given transaction qualifies for Express Pick processing. It is classified in ETRM as an OTHER API rather than a standard open interface, indicating that it is intended for internal consumption by other WMS modules and by Oracle's own mobile supply chain applications rather than by external integrations. The header revision information ($Header: WMSEXPTB.pls 120.1) confirms the package has its origins in the older Warehouse Management code stream and has been carried forward into the 12.x technology stack.

Key Procedures and Functions

The documented application programming interface surface comprises six programs. Four relate directly to task movement and eligibility:

• LOAD_AND_DROP — Convenience program that combines the load and drop steps into a single call, allowing a picked quantity to be moved to its destination location in one operation. The check_loose_quantity search term most plausibly relates to logic embedded in this routine, where loose or unpacked quantities must be validated before a task can be committed.
• LOAD_TASK — Places a picked task onto the target handling unit or destination, updating the WMS dispatched task state.
• DROP_TASK — Completes the movement by dropping the loaded task at the destination, finalising the associated material transaction.
• HAS_EXPRESS_PICK_TASKS — Returns whether any Express Pick tasks currently exist for the calling context; used to gate the user interface.
• IS_EXPRESS_PICK_TASK — Predicate that determines whether a specific task is an Express Pick task.
• IS_EXPRESS_PICK_TASK_ELIGIBLE — Predicate that determines whether a task or transaction is eligible to be processed as Express Pick, typically by inspecting item, subinventory, and locator attributes.

In addition, the package body contains internal helpers including MYDEBUG and PRINT_LABEL. PRINT_LABEL invokes the label printing API for a passed transaction temporary ID and resolves a business flow code from the transaction type and source type — pick for sales order (type 52), WIP issue (type 35), backflush (type 51/source 13), and replenishment (type 64/source 4). Label printing failure is tolerated; the process completes regardless.

Tables Accessed

The package reads and writes the following tables through APPS synonyms:

• MTL_MATERIAL_TRANSACTIONS_TEMP and MTL_MATERIAL_TRANSACTIONS_S — staging and stored material transaction records created as tasks are loaded and dropped.
• MTL_TRANSACTION_LOTS_TEMP — lot and serial detail accompanying the staged transaction.
• MTL_SYSTEM_ITEMS_B — item master attributes used for eligibility and loose-quantity checks.
• MTL_SECONDARY_INVENTORIES — subinventory attributes, including locator and picking controls.
• WMS_DISPATCHED_TASKS — the WMS task record whose status is advanced by LOAD_TASK and DROP_TASK.
• WMS_LICENSE_PLATE_NUMBERS — LPN identifiers associated with loaded handling units.
• DUAL — used for single-row PL/SQL constructs.

Usage Notes

WMS_EXPRESS_PICK_TASK is invoked from Oracle's mobile supply chain applications and from other WMS packages — ETRM records two dependent packages — rather than from a standalone concurrent program or a customer-facing form. Customisations that need to interrogate Express Pick eligibility or task existence should call IS_EXPRESS_PICK_TASK_ELIGIBLE and HAS_EXPRESS_PICK_TASKS rather than querying WMS tables directly, since those predicates encapsulate the necessary rules. Because PRINT_LABEL is designed to be non-fatal on failure, callers should not treat a label print error as a task failure. Debug output is controlled by the INV_DEBUG_TRACE profile option and routed through INV_MOBILE_HELPER_FUNCTIONS.TRACELOG at level 4.