Search Results wave_completion_time

Overview

WMS_WP_WAVE_HEADERS_VL is a bilingual (VL, "_VL") view owned by the APPS schema in Oracle E-Business Suite, defined over the Warehouse Management wave planning data model. It presents the translatable wave-header information stored in WMS_WP_WAVE_HEADERS_TL joined to the operational wave-header attributes stored in WMS_WP_WAVE_HEADERS_B, exposing a single row per wave header whose translated descriptions match the session language. Because it consolidates the wave definition attributes, the wave selection and criteria parameters, and the customer-facing translated name and description in one place, the view functions as the primary reporting and integration surface for wave planning data.

The view is relevant to users who search for columns such as include_planned_lines. That column originates on the operational base table and is surfaced through this view, allowing filters and extracts against the wave header attribute that governs whether planned (unreleased/unallocated) demand lines are swept into the wave.

Underlying Base Objects

The view is defined over two base objects, both resolved through APPS synonyms:

• WMS_WP_WAVE_HEADERS_B — the operational base table holding wave attributes, criteria parameters, flags, output/display columns, and standard WHO audit columns. Aliased as B in the view text and joined on WAVE_HEADER_ID.
• WMS_WP_WAVE_HEADERS_TL — the translation table holding language-specific descriptive text (WAVE_NAME, WAVE_DESCRIPTION). Aliased as T and constrained by T.LANGUAGE = USERENV('LANG') so each session receives the appropriate language row.

The join condition is B.WAVE_HEADER_ID = T.WAVE_HEADER_ID, and the view additionally exposes B.ROWID as ROW_ID. The base tables are documented as valid APPS synonyms in the 12.2.2 reference metadata.

Key Columns

• WAVE_HEADER_ID — primary key linking the header to its translations and downstream child records.
• WAVE_NAME / WAVE_DESCRIPTION — translated identifiers from the _TL table.
• WAVE_STATUS / WAVE_SOURCE / TYPE_ID — classification of the wave and its origin.
• INCLUDE_PLANNED_LINES — flag indicating whether planned order lines are included when the wave is planned; directly relevant to the user's search term.
• START_TIME / WAVE_COMPLETION_TIME / SCHEDULED_DAYS / SCHEDULED_HRS — timing and scheduling attributes.
• PLANNING_CRITERIA / PLANNING_CRITERIA_ID / ADVANCED_CRITERIA — criteria that determine wave content.
• ORGANIZATION_ID / BATCH_ID / TASK_ID / TASK_PLANNING_FLAG — organizational and task association columns.
• SHIP_TO_LOCATION_ID / CUSTOMER_ID / DELIVERY_ID / TRIP_ID / TRIP_STOP_ID — shipping and delivery context.
• RELEASE_IMMEDIATELY / RELEASE_SEQ_RULE / AUTO_CREATE_DELIVERY — release and delivery automation attributes.
• ATTRIBUTE1..15 / ATTRIBUTE_CATEGORY — DFF columns carried through from the base table.

Common Use Cases and Queries

Typical uses include operational reporting on wave configuration, auditing which waves include planned demand, and integration extracts passing wave definitions to external planning systems.

• Listing waves that include planned lines:

  SELECT wave_header_id, wave_name, wave_status
  FROM   apps.wms_wp_wave_headers_vl
  WHERE  include_planned_lines = 'Y';

• Joining to the base table for untranslated attributes:

  SELECT v.wave_name, b.planning_criteria, b.start_time
  FROM   apps.wms_wp_wave_headers_vl v,
         apps.wms_wp_wave_headers_b b
  WHERE  v.wave_header_id = b.wave_header_id
  AND    b.organization_id = :org_id;

• Filtering by wave source and status for a dashboard, using WAVE_SOURCE and WAVE_STATUS together with ORGANIZATION_ID.

Because the view already enforces the language join, it is preferable to the base tables for user-facing reporting, while direct queries against WMS_WP_WAVE_HEADERS_B remain appropriate for attribute-only extracts that do not require translations.