Search Results get_tasks

Overview

WMS_PLAN_TASKS_PVT is a private PL/SQL package body in the APPS schema that supports the Wave Planning and Task Planning functionality within Oracle Warehouse Management (WMS). Its principal responsibility is to assemble, filter, and return the set of warehouse tasks that the Wave Planning engine and its associated user interfaces display to warehouse operators and planners. The package is classified as a PVT (private) API, meaning it is not intended for direct invocation by external customers or third-party integrations; it is a supporting implementation layer invoked by public WMS APIs, Oracle Forms, and internal planning logic.

The package works primarily against a staging table, WMS_WAVEPLAN_TASKS_TEMP, which holds transient wave plan task rows generated during a planning run. The package provides routines to query inbound and outbound tasks, decode grid columns, and enumerate completed or wide plan records. It also provides a debug utility that routes trace messages to the INV_LOG_UTIL tracing subsystem, enabling support and diagnostics for planning sessions.

Key Procedures and Functions

• DEBUG — A private logging utility that writes trace messages to the INV_LOG_UTIL trace facility. It chunks long messages into 4000-character substrings and supports configurable message destinations.
• QUERY_INBOUND_PLAN_TASKS — Retrieves wave plan task records associated with inbound (receiving/putaway) planning activities.
• GET_PLANS — Returns the set of wave plans available for the current planning context, used to populate plan-selection UI elements.
• GET_TASKS — The central routine that fetches warehouse tasks for a given plan, forming the dataset displayed to the planner. This is the object most commonly searched by users working with task retrieval.
• GET_COL_LIST — Supplies the column definitions for the task grid, working with JTF_CUSTOM_GRID_COLS to drive the customizable grid layout.
• GET_COMPLETED_RECORDS — Returns plan tasks that have already been completed, supporting reconciliation and audit views.
• GET_WDTH_PLAN_RECORDS — Returns width-based or dimensional plan records used in wave task display.
• GET_INBOUND_SPECIFIC_QUERY — Builds and returns the SQL query fragment specific to inbound task selection.
• GET_OUTBOUND_SPECIFIC_QUERY — Builds and returns the SQL query fragment specific to outbound task selection.
• SET_GLOBALS — Initializes package-level global variables (such as organization and plan context) prior to query execution.
• CLEAR_GLOBALS — Resets those global variables to avoid state leakage between calls.

Tables Accessed

The package reads and writes WMS_WAVEPLAN_TASKS_TEMP, its primary staging table for generated tasks. It joins to WMS_OP_OPERATION_INSTANCES and WMS_OP_OPERTN_INSTANCES_HIST to obtain operation execution history. Sales order context comes from MTL_SALES_ORDERS, OE_ORDER_HEADERS_ALL, and OE_ORDER_LINES_ALL. Procurement context comes from PO_REQUISITION_HEADERS_ALL, PO_REQUISITION_LINES_ALL, RCV_SHIPMENT_HEADERS, and RCV_SHIPMENT_LINES. Work-in-process context is drawn from WIP_ENTITIES. Grid metadata is read from JTF_CUSTOM_GRID_COLS. The package also uses DBMS_SQL and PLITBLM for dynamic SQL and index-by-table manipulation.

Usage Notes

WMS_PLAN_TASKS_PVT is invoked internally by the Wave Planning forms and by the concurrent planning programs that populate WMS_WAVEPLAN_TASKS_TEMP. Two other packages reference it. Because it is a private API, customizations should not call it directly; instead, customers should use supported public WMS APIs or the standard Wave Planning UI. When troubleshooting "get_tasks" behavior in EBS 12.1.1 or 12.2.2, confirm that SET_GLOBALS has been called with the correct organization and plan context before GET_TASKS executes.