Search Results plan_wave_cp




Overview

The concurrent program PLAN_WAVE_CP is an Oracle Warehouse Management (WMS) component that drives the Wave Planning Plan Wave process. Within the Oracle E-Business Suite Release 12.1.1 and 12.2.2 environments, this program is delivered as part of the WMS – Warehouse Management module and is enabled by default in a standard installation. Its primary function is to execute the wave planning logic that groups eligible pick, move, and replenishment tasks into waves, enabling warehouse operations to release work to the floor in a controlled, batched manner. The program is internally linked to the Wave Planning feature and corresponds to the user-facing name "Wave Planning Plan Wave."

Wave planning is central to outbound and internal warehouse execution. Rather than releasing individual tasks ad hoc, the Plan Wave process evaluates outstanding demand and task criteria—such as carrier, priority, staging lane, order type, or picking rule—and consolidates tasks into waves that operators can process together. This improves travel efficiency, equipment utilization, and dock scheduling. The program is invoked both through the standard concurrent manager and, in some configurations, from WMS mobile or desktop pages that trigger wave planning on demand.

Execution Details

The documented execution metadata for PLAN_WAVE_CP is as follows:

  • Execution Method: PL/SQL Stored Procedure
  • Executable: WMSWPPW
  • Execution File: WMS_WAVE_PLANNING_PVT.Plan_Wave_CP
  • Argument Method: Standard
  • Product: WMS – Warehouse Management
  • Enabled: Yes

Because the Execution Method is PL/SQL Stored Procedure, the concurrent manager invokes the packaged API WMS_WAVE_PLANNING_PVT.Plan_Wave_CP directly, rather than calling a SQL*Plus script or host program. The "Standard" argument method indicates that arguments are passed positionally in the order defined on the concurrent program's parameter form. This package-based design allows the same business logic to be shared between scheduled concurrent runs and interactive page-level invocations.

How to Run

The program is typically submitted through the Standard Request Submission (SRS) interface: navigate to Submit a New Request, locate "Wave Planning Plan Wave," and enter the required parameters. General guidance for submission includes:

  • Warehouse / Organization: Select the specific WMS-enabled inventory organization to be planned, since wave planning is organization-scoped.
  • Wave Criteria: Provide the parameters that define which tasks qualify for inclusion—commonly wave name or batch, carrier, priority range, order type, and cut-off or pick-by date.
  • Plan Mode / Flag Parameters: Some parameters control whether the run opens new waves, appends to existing ones, or performs a validation-only pass.
  • Run Options: Use the concurrent program's scheduling options to run this on a recurring basis (for example, prior to each shift or dock appointment window), or submit it interactively when expedited planning is required.

Users should verify the concurrent program is enabled for the target responsibility and that the request group includes the program, as request group membership governs visibility in SRS.

Related Objects

PLAN_WAVE_CP interacts with several WMS data structures and interfaces that are commonly referenced alongside it:

  • WMS_WAVE_PLANNING_PVT: The PL/SQL package containing the Plan_Wave_CP procedure and its supporting wave-planning logic.
  • WMS Tasks and Task Types: Underlying task records (WMS_TASKS-related tables) that are evaluated and grouped into waves.
  • Wave and Wave Task Tables: The wave header and wave detail tables populated when a wave is created or updated.
  • WMS Rules and Picking/Planning Rules: Rule definitions that determine how tasks are prioritized and assigned to waves.
  • Related Wave Programs: Companion concurrent programs such as wave release, wave pick confirmation, and task generation processes that follow the planning step.
  • Order Management / Inventory Interfaces: Upstream sales order and move-order data that supply the demand being planned.

Because the package procedure is the same entry point used by interactive wave planning pages, any customizations or debugging should focus on WMS_WAVE_PLANNING_PVT.Plan_Wave_CP and the concurrent program definition (Executable WMSWPPW) rather than on external scripts.