Search Results wms_wave_planning_pvt




Overview
Explore in AI Chat

Overview

APPS.WMS_WP_CUSTOM_APIS_PUB is a public PL/SQL package within the Oracle Warehouse Management System (WMS) module of Oracle E-Business Suite, present and valid in both release 12.1.1 and 12.2.2. Its name and API classification (PUB) identify it as a custom hook or extension layer that surrounds the core wave planning engine. The package exists to allow organizations to inject customer-specific business logic into the standard wave planning cycle without modifying Oracle's seeded code.

Wave planning in WMS is orchestrated by the private package WMS_WAVE_PLANNING_PVT, which drives wave creation, task generation, and release processing. The ETRM dependency metadata confirms a bidirectional relationship: WMS_WP_CUSTOM_APIS_PUB references WMS_WAVE_PLANNING_PVT, and WMS_WAVE_PLANNING_PVT in turn references WMS_WP_CUSTOM_APIS_PUB. This interdependence indicates that the core engine calls outward to the custom API package at defined extension points, and the custom package calls back into core wave planning services. The practical effect is a controlled customization seam: standard wave logic remains intact, while site-specific rules for line creation, exception reporting, and task release are isolated in a supported, upgrade-friendly package.

Key Procedures and Functions

The documented interface exposes three entry points, each aligned to a distinct phase of wave processing:

  • CREATE_WAVE_LINES_CUST — The customization hook invoked when wave lines are generated. It provides the mechanism for applying customer-specific selection, grouping, or ordering rules to the lines that form a wave, allowing non-standard allocation or consolidation logic to participate in standard wave creation.
  • GET_WAVE_EXCEPTIONS_CUST — Returns wave exception information. This allows a site to define, surface, or classify exceptions raised during wave planning and release, supporting customized exception handling and visibility in downstream monitoring.
  • TASK_RELEASE_CUST — The customization point governing task release. It enables site-specific validation, sequencing, or gating logic to execute when tasks belonging to a wave are released for execution in the warehouse.

All three procedures are customer-facing extension routines. No parameter signatures are documented in the available metadata, and none should be assumed; implementers must obtain signatures from the live package specification in the target environment.

Tables Accessed

The ETRM metadata for this object does not enumerate persistent tables referenced through APPS synonyms. This is consistent with the package's design as an API/extension layer rather than a direct data-access package: its principal interactions are with WMS_WAVE_PLANNING_PVT, which owns the underlying wave, task, and plan tables. Any table access performed by these custom procedures occurs indirectly through core wave planning logic or through custom code the customer adds. Where an implementation requires direct table access, it is introduced by the customer within these procedures and is not part of the documented Oracle interface.

Usage Notes

This package is not intended for direct invocation by end users or standalone batch jobs. Its documented usage pattern is callback-driven: WMS_WAVE_PLANNING_PVT invokes the custom procedures during wave planning operations, so the package executes whenever a wave is created, planned, or released through standard WMS flows. Typical triggering contexts include the wave planning concurrent programs, the WMS wave planning and task release user interfaces, and integrated execution flows invoking the wave planning engine.

Because the dependency is bidirectional, custom code placed in CREATE_WAVE_LINES_CUST, GET_WAVE_EXCEPTIONS_CUST, or TASK_RELEASE_CUST can itself call standard WMS_WAVE_PLANNING_PVT routines to reuse core behavior. Implementers should make extension procedures efficient and defensive, since they execute inline with core processing and any exception raised propagates into wave planning. The PUB designation and the isolated custom package make this a supported extension strategy that preserves Oracle-seeded objects, simplifying patching and upgrades across 12.1.1 and 12.2.2. Before coding, the package specification should be reviewed in each target instance to confirm the exact parameter lists, as these are not captured in the documentation metadata.