Search Results wms_waveplan_tasks_pvt




Overview
Explore in AI Chat

Overview

WMS_PLAN_TASKS_PVT is a private PL/SQL package in the Oracle Warehouse Management (WMS) module of Oracle E-Business Suite, released under the APPS schema. It serves as the internal processing engine that supports the warehouse planning and task-query infrastructure, most notably the Warehouse Task Planning and Execution workbench used by warehouse supervisors and planners. The package encapsulates the logic required to build, restrict, and return query result sets over warehouse plan tasks — the units of work representing inbound receipts, outbound picks, cross-dock movements, manufacturing supply, and warehousing operations.

A distinguishing feature of the package is its use of a large set of package-level global variables (for example g_organization_id, g_inventory_item_id, g_person_id, g_user_task_type_id, g_from_task_quantity, and the numerous task-status flags such as g_is_unreleased_task and g_is_dispatched_task). These globals act as the internal search-criteria container that mirrors the user-entered filter fields on the WMS task-query screen. The naming convention of these globals closely corresponds to the "generic where" clause construction mandated by the task-search UI, which is the object most frequently associated with this package in support and development searches.

Key Procedures and Functions

  • SET_GLOBALS — Populates the package-level global search criteria variables from the current user-entered or programmatically supplied filter values. This is the entry point that prepares the package for a query execution.
  • CLEAR_GLOBALS — Resets all global search criteria variables to their default null or FALSE state, ensuring that a subsequent query is not polluted by residual criteria from a prior invocation.
  • GET_TASKS — The principal query routine that returns the set of warehouse plan tasks matching the populated global criteria.
  • QUERY_INBOUND_PLAN_TASKS — A specialized query path that returns inbound plan tasks, applying the inbound-specific filter logic.
  • GET_PLANS — Returns warehouse plan header information associated with the task-search context.
  • GET_COL_LIST — Retrieves the configured column list for the task-query result grid, driving the column layout displayed to the user.
  • GET_COMPLETED_RECORDS — Returns historical completed task records, supporting the "completed" view of the task workbench.
  • GET_WDTH_PLAN_RECORDS — Returns records for the width (work-direction) plan view used in planning analysis.
  • GET_INBOUND_SPECIFIC_QUERY — Builds the inbound-specific portion of the dynamic query, enabling the package to append inbound predicates to the generic where clause.
  • GET_OUTBOUND_SPECIFIC_QUERY — Builds the outbound-specific portion of the dynamic query, appending outbound predicates to the generic where clause.
  • DEBUG — Provides internal diagnostic output to assist in troubleshooting query construction and execution.

Tables Accessed

The package reads and writes warehouse operational data through APPS synonyms. JTF_CUSTOM_GRID_COLS supplies the configurable grid columns returned by GET_COL_LIST. WMS_WAVEPLAN_TASKS_TEMP holds transient task result sets. Inbound and outbound order context is drawn from RCV_SHIPMENT_HEADERS, RCV_SHIPMENT_LINES, PO_REQUISITION_HEADERS_ALL, PO_REQUISITION_LINES_ALL, OE_ORDER_HEADERS_ALL, OE_ORDER_LINES_ALL, and MTL_SALES_ORDERS. Manufacturing and warehousing task context comes from WIP_ENTITIES, WMS_OP_OPERATION_INSTANCES, and WMS_OP_OPERTN_INSTANCES_HIST. The package also relies on DBMS_SQL and PLITBLM for dynamic SQL construction and PL/SQL table manipulation — the mechanism by which the generic where clause is assembled at runtime.

Usage Notes

WMS_PLAN_TASKS_PVT is a private (PVT) package and is not intended for direct invocation by external custom code; it is called by the WMS task-planning UI and by the two dependent packages identified in the ETRM metadata. Typical invocation follows a fixed sequence: CLEAR_GLOBALS, SET_GLOBALS with the desired criteria, then GET_TASKS or one of the specialized query routines. Because the package depends on mutable global state, concurrent or re-entrant calls within the same session can produce incorrect results if the globals are not reset between invocations. Customizations should interact with the public WMS APIs rather than this private package; direct calls risk breakage across patches and are not upgrade-safe.