Results for “load_seq_number”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

The WMS_WAVEPLAN_TASKS_V view is a Warehouse Management Systems (WMS) reporting object owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It exposes the wave planning task records that drive execution of warehouse work — picking, put-away, replenishment, and miscellaneous movements — generated when a wave plan is released to the floor. Each row represents an individual task assigned to a person, machine resource, or equipment instance, and includes the full from/to location context required for execution and audit.

The view is used principally for operational reporting, dashboards, and integration with external warehouse execution or labour management systems. Because it surfaces task status, priority, time estimates, and physical movement details in a single flattened structure, it is the standard access point for querying wave plan task activity without joining the numerous base task tables directly.

Underlying Base Objects

ETRM metadata documents a single referenced base object: WMS_WAVEPLAN_TASKS_TEMP, accessed via a synonym. This is the temporary staging table populated during wave plan generation and task expansion. The view is a simple projection over that object, selectively exposing the columns required by wave planning consumers. Because the source is a temporary structure, task rows reflect the current state of the wave plan run; persisted task history should be sourced from the corresponding permanent task tables (such as WMS_TASKS) where longer retention is required.

Key Columns

• TASK_ID, TRANSACTION_TEMP_ID, PARENT_LINE_ID — primary task identity and parent/child hierarchy.
• ORGANIZATION_ID, SUBINVENTORY, LOCATOR_ID, LOCATOR — the from-side inventory location.
• TO_ORGANIZATION_ID, TO_SUBINVENTORY, TO_LOCATOR_ID, TO_LOCATOR — the destination location; this is directly relevant to the to_subinventory search term, identifying the target subinventory for a movement.
• INVENTORY_ITEM_ID, ITEM, REVISION, TRANSACTION_UOM, TRANSACTION_QUANTITY — item and quantity moved.
• USER_TASK_TYPE, TASK_TYPE, STATUS, PRIORITY — classification, workflow state, and sequencing.
• PERSON, PERSON_RESOURCE_CODE, MACHINE_RESOURCE_CODE, EQUIPMENT_INSTANCE — assignment and resource context.
• LPN and cartonization columns (FROM_LPN, TO_LPN, CONTENT_LPN, ALLOCATED_LPN, TO_LPN_ID) — licence plate handling.
• Order/shipment attributes (PICK_SLIP_NUMBER, DELIVERY, SHIP_METHOD, CUSTOMER, SHIP_TO_STATE) — outbound context.
• Timestamps (CREATION_TIME, DISPATCHED_TIME, LOADED_TIME, DROP_OFF_TIME) and audit columns — task lifecycle tracking.

Common Use Cases and Queries

Typical uses include wave task status reporting, put-away destination validation, and confirmation of transfer destinations by subinventory.

List open tasks targeting a specific subinventory:

• SELECT task_id, item, transaction_quantity, subinventory, to_subinventory FROM apps.wms_waveplan_tasks_v WHERE to_subinventory = 'STAGED' AND status = 'Pending';

Report task assignment and progress by person:

• SELECT person, status, priority, creation_time FROM apps.wms_waveplan_tasks_v WHERE organization_id = :org AND person IS NOT NULL ORDER BY priority;

These queries should be filtered by ORGANIZATION_ID and creation date range for performance, as the view is unindexed beyond its base object.