Search Results num_of_child_tasks




Overview
Explore in AI Chat

Overview

APPS.WMS_WAVEPLAN_TASKS_V is a reporting and integration view within the Oracle Warehouse Management (WMS) module of Oracle E-Business Suite. It exposes the task-level records that constitute a wave plan execution — the individual work tasks generated when a wave plan is released for picking, moving, put-away, or other warehouse operations. Each row represents a discrete unit of work assigned to a resource, person, or machine within the warehouse.

The view is defined entirely as a projection over a single temporary table, WMS_WAVEPLAN_TASKS_TEMP, without joins to master data tables. This design means the view relies on pre-populated, denormalized columns (such as ITEM, ORGANIZATION_CODE, LOCATOR, and CUSTOMER) that are populated by the wave plan engine rather than resolved through joins at query time. The view therefore performs well for high-volume operational reporting but reflects only the data current at the time the temporary records were generated.

Underlying Base Objects

The only documented base object referenced by this view is WMS_WAVEPLAN_TASKS_TEMP, accessed through a synonym. The view is a direct SELECT of all columns from that table, with no filtering, aggregation, or joins. Consequently, the view inherits the temporary nature of its source: records may be purged or regenerated as wave plans are processed, released, or purged. Application logic is responsible for populating the temporary table before the view is queried, and consumers should treat the data as transient rather than as a persistent record of warehouse task history.

Key Columns

Common Use Cases and Queries

Typical uses include monitoring wave plan task status, calculating workloads per resource, and validating child task hierarchies using NUM_OF_CHILD_TASKS and PARENT_LINE_ID.

Example: identifying tasks and their child counts.

  • SELECT TASK_ID, PARENT_LINE_ID, NUM_OF_CHILD_TASKS, STATUS, PERSON FROM APPS.WMS_WAVEPLAN_TASKS_V WHERE NUM_OF_CHILD_TASKS > 0;

Example: listing open tasks assigned to a person.

  • SELECT TASK_ID, ITEM, TRANSACTION_QUANTITY, ORGANIZATION_CODE FROM APPS.WMS_WAVEPLAN_TASKS_V WHERE PERSON_ID = :person_id AND STATUS != 'Closed';

Because the view has no joins, it is efficient for bulk operational queries. Consumers should nonetheless validate data currency against the temporary table's lifecycle before using results for analytical or historical reporting.