Search Results get_final_query

Overview

APPS.WMS_WAVEPLAN_TASKS_PVT is a private PL/SQL package in the Oracle Warehouse Management (WMS) module that supports the Wave Planning workbench. Wave planning is the process by which warehouse operations group outbound demand — sales orders, move orders, and transfer orders — into waves, and then generate, sequence, and dispatch the picking, putaway, replenishment, cycle count, and staging tasks required to fulfill that demand. WMS_WAVEPLAN_TASKS_PVT supplies the server-side logic behind the Wave Planning Tasks user interface, giving the workbench its ability to query tasks, assign or modify task attributes, estimate labor, produce distribution summaries, and cancel plans or individual tasks. The package is classified as PVT, meaning it is an internal implementation package intended to be called from the WMS Wave Planning forms, concurrent programs, and sibling WMS packages rather than from customer-written code. Its header carries the version string 120.8.12010000.1, indicating it is the standard 12.1.1/12.2.2-era release, and it is referenced by four other packages within the WMS product family.

Key Procedures and Functions

The package exposes roughly two dozen documented procedures, which fall into several functional groups:

• Row selection and manipulation: MARK_ROWS and UNMARK_ROWS manage the set of wave plan task rows selected in the workbench session. QUERY_TASKS and GET_FINAL_QUERY build and execute the task query, while GET_GENERIC_SELECT, GET_GENERIC_FROM, and GET_GENERIC_WHERE supply the dynamic SQL fragments that drive that query.
• Task maintenance: UPDATE_TASK modifies attributes of an existing task, REMOVE_TASKS deletes tasks from the working set, and SAVE_TASKS persists changes back to the database.
• Cancellation: CANCEL_PLANS and CANCEL_TASK provide the cancel_plans capability the user searched for. CANCEL_PLANS cancels an entire wave plan, and CANCEL_TASK cancels an individual task within a plan.
• Aggregation and reporting: GET_STATUS_DIST and GET_TYPE_DIST return distributions of tasks by status and task type, and CALCULATE_SUMMARY computes summary and labor estimation figures for the selected rows.
• Setup/control: SET_STATUS_CODES, SET_TASK_TYPE, SET_PLAN_TASK_TYPES, and SET_PLAN_STATUS_CODES load the lookup values used to populate lists and validate the task and plan vocabularies, while FIND_VISIBLE_COLUMNS determines which grid columns are displayed to the user.

The header defines collection types — including transaction, task type, result, message, task ID, time-per-task, time UOM, and lookup meaning tables — and constants for task types such as pick, putaway, cycle count, replenish, MO transfer, MO issue, staging move, and inspection.

Tables Accessed

The package reads and writes WMS_WAVEPLAN_TASKS_TEMP, the temporary table that drives the workbench grid, and references MTL_PARAMETERS and MTL_MOBILE_LOGIN_HIST for organizational and session context. It joins to task-related BOM tables — BOM_RESOURCES, BOM_STANDARD_OPERATIONS, BOM_STD_OP_RESOURCES, and BOM_RESOURCE_EMPLOYEES — to derive labor and resource information for estimations. Transaction and cycle count history comes from MTL_MATERIAL_TRANSACTIONS, MTL_MATERIAL_TRANSACTIONS_TEMP, MTL_CYCLE_COUNT_HEADERS, and MTL_CYCLE_COUNT_ENTRIES, and order/reason context from MTL_SALES_ORDERS and MTL_TRANSACTION_REASONS. Grid metadata for the workbench UI is obtained from JTF_CUSTOM_GRID_COLS and JTF_GRID_COLS_B.

Usage Notes

WMS_WAVEPLAN_TASKS_PVT is normally invoked indirectly through the Wave Planning Tasks form in the WMS responsibility; the form calls QUERY_TASKS, MARK_ROWS, and the distribution procedures when the user queries or views tasks, and calls CANCEL_PLANS or CANCEL_TASK when the user cancels a wave plan or a task. Because the package is Private, Oracle does not publish its signatures for customer use, and direct calls from custom code are unsupported. Oracle's documented practices for WMS wave planning — Oracle Warehouse Management User's Guide — describe wave planning workflows at the functional level; any modification or extension should go through supported APIs (such as the WMS public task APIs) rather than through this package, since its behavior may change across patch levels.