Search Results wms_waveplan_tasks




Overview
Explore in AI Chat

Overview

APPS.WMS_WAVEPLAN_TASKS_PVT is the private implementation body behind the Warehouse Management System (WMS) wave planning task maintenance user interface in Oracle E-Business Suite 12.1.1 and 12.2.2. It supports the Wave Planning Workbench, the form-based screen used by warehouse supervisors and planners to review, update, reassign, and cancel picking, putaway, and staging tasks that have been generated for outbound wave plans. The package encapsulates all of the selection, validation, editing, and summary logic required to drive the workbench grid, including dynamic column visibility, status and task-type translation, generic query construction, and consolidated time, volume, and weight calculations across plan tasks.

The body is defined with the private API classification (PVT), meaning it is not intended as a public integration point. It is invoked exclusively through the WMS wave planning forms and related internal WMS modules, and it depends on temporary staging tables that buffer user edits before they are committed to the base transaction tables.

Key Procedures and Functions

The package exposes twenty-four documented procedures and functions that collectively manage the workbench lifecycle:

  • MARK_ROWS / UNMARK_ROWS — Select or deselect task rows in the workbench grid for subsequent bulk actions.
  • QUERY_TASKS — Retrieves wave plan tasks into the temporary working set based on the current query criteria.
  • UPDATE_TASK — Validates and applies user edits to an individual task, including guards against updating putaway or staging move tasks and unreleasing cross-docking tasks.
  • REMOVE_TASKS — Removes selected tasks from the working set.
  • SAVE_TASKS — Persists staged edits to the underlying transaction tables.
  • GET_STATUS_DIST / GET_TYPE_DIST — Return status and task-type distribution information for the current plan selection.
  • CALCULATE_SUMMARY — Aggregates summarized time, volume, and weight for the selected tasks, validating unit-of-measure consistency and reporting missing item attributes.
  • GET_GENERIC_SELECT, GET_GENERIC_FROM, GET_GENERIC_WHERE — Dynamically construct the query fragments that drive the configurable task grid.
  • CANCEL_PLANS / CANCEL_TASK — Cancel entire wave plans or individual tasks.
  • GET_FINAL_QUERY — Assembles the complete dynamic SQL statement from the generic fragments.
  • SET_STATUS_CODES, SET_TASK_TYPE, SET_PLAN_TASK_TYPES, SET_PLAN_STATUS_CODES — Populate lookup and translation values used in the grid and validation logic.
  • FIND_VISIBLE_COLUMNS — Determines which grid columns are visible for the current user, driving the package-level visibility flags such as allocated LPN, cartonization LPN, delivery, and customer.

Tables Accessed

The package reads and writes configuration and staging tables including WMS_WAVEPLAN_TASKS_TEMP (the primary edit buffer), JTF_CUSTOM_GRID_COLS, JTF_GRID_COLS_B (grid column metadata for visibility rules), MTL_PARAMETERS (organization defaults), and BOM resource-related tables (BOM_RESOURCES, BOM_RESOURCE_EMPLOYEES, BOM_STANDARD_OPERATIONS, BOM_STD_OP_RESOURCES) for resource and employee validation on task assignment. It also references MTL_MATERIAL_TRANSACTIONS and MTL_MATERIAL_TRANSACTIONS_TEMP for transaction detail, MTL_SALES_ORDERS for demand linkage, MTL_TRANSACTION_REASONS for cancellation and adjustment reasons, MTL_CYCLE_COUNT_ENTRIES and MTL_CYCLE_COUNT_HEADERS for count-related task context, and MTL_MOBILE_LOGIN_HIST for mobile user tracking. The mix of base and temporary tables reflects the package's role in staging user-driven changes prior to commit.

Usage Notes

WMS_WAVEPLAN_TASKS_PVT is invoked by the Wave Planning Workbench forms and by four other WMS packages that depend on its task maintenance routines. It is not documented as a public API and should not be called directly from custom code; integrations requiring wave plan or task manipulation should use the supported public WMS APIs. Because the package relies on temporary staging tables and grid visibility metadata, its behavior is sensitive to user session context and to JTF grid configuration established for the logged-in warehouse operator. Cancellation logic (CANCEL_PLANS, CANCEL_TASK) and summary calculations (CALCULATE_SUMMARY) carry specific validation guards — for example, against cancelling released cross-dock tasks or summarizing tasks with inconsistent UOMs — that produce the global error messages defined at the top of the body.