Search Results create_wave_lines_cust




Overview
Explore in AI Chat

Overview

The APPS.WMS_WP_CUSTOM_APIS_PUB package body is a public, customer-facing extension (hook) package delivered as part of the Oracle Warehouse Management System (WMS) module in Oracle E-Business Suite releases 12.1.1 and 12.2.2. Its purpose is to expose predefined integration points within the Wave Planning workflow where customers and integrators can insert site-specific business logic without modifying Oracle-owned seeded code. This extension strategy preserves supportability and minimizes the impact of patching and upgrades.

The package body follows the standard Oracle EBS hook architecture: the seeded Wave Planning engine invokes a public procedure, the procedure initializes the FND message stack, establishes a savepoint for transactional control, sets a success return status, and then evaluates a Boolean flag indicating whether the custom logic has been implemented. If custom logic is not present, the API returns a value of FALSE for the output parameter x_api_is_implemented, allowing the calling engine to fall back to standard behavior. Where custom logic is present, the implementer is expected to modify the package body to return TRUE and to populate the supplied PL/SQL collection types with the desired data rows and corresponding actions.

Key Procedures and Functions

  • CREATE_WAVE_LINES_CUST — Provides a customization hook for generating or suppressing wave line records during wave planning. The procedure accepts a wave header identifier and returns a Boolean flag indicating whether custom logic was implemented, along with PL/SQL tables representing custom line records and the actions to be applied to those lines (for example, an ADD action). This is the procedure referenced by the search term create_wave_lines_cust.
  • GET_WAVE_EXCEPTIONS_CUST — Offers an extension point for identifying or returning wave planning exceptions according to customer-defined rules, enabling site-specific validation and exception reporting within the wave lifecycle.
  • TASK_RELEASE_CUST — Serves as a customization hook invoked during the release of warehouse tasks, permitting customer-specific processing tied to task release events.

A private helper procedure, PRINT_DEBUG, writes trace messages to the debugging log via INV_MOBILE_HELPER_FUNCTIONS.TRACELOG and is gated by the INV_DEBUG_TRACE profile option.

Tables Accessed

The documented excerpt does not enumerate base tables directly. The custom line structure is derived from the WMS_WAVE_PLANNING_PVT.LINE_TBL_TYP and ACTION_TBL_TYP collection types, and the example logic references the WMS_WP_WAVE_LINES_S sequence for populating WAVE_LINE_ID values together with a WAVE_HEADER_ID. Because this is a customization package, any persistent tables written to are determined entirely by the customer's implementation rather than by Oracle-delivered code. The package is referenced by one other package, indicating it participates in the broader WMS wave planning call chain.

Usage Notes

This package is intended for customers and implementation partners extending Oracle WMS wave planning. It is not typically invoked directly by end users; instead it is called by Oracle's seeded wave planning engine during processing, or by custom concurrent programs and forms that follow the documented hook contract. Implementers must set x_api_is_implemented to TRUE when inserting custom logic and populate the provided PL/SQL tables to communicate results back to the caller. Debug tracing is controlled through the INV_DEBUG_TRACE profile option, and transactional integrity is safeguarded by the savepoint set at the start of each procedure. All modifications should be made to the APPS-owned body with care, as it is overwritten during patching.