Search Results to_locator




Overview
Explore in AI Chat

Overview

APPS.WMS_WP_TASKS_GTMP_V is a reporting and integration view within the Oracle Warehouse Management (WMS) module of Oracle E-Business Suite. It exposes the content of the global temporary staging structure that holds warehouse execution task data generated by the WMS task dispatch and work planning engine. The view is defined with an explicit column list drawn from a single underlying synonym, WMS_WP_TASKS_GTMP, and presents one row per warehouse task or task-related transaction record. Its principal role is to provide a stable, named interface over the temporary task staging data so that concurrent programs, mobile device interfaces, and custom reports can consume task attributes without referencing the base temporary table directly. In the context of Oracle EBS 12.1.1 and 12.2.2, the view is a read-oriented object typically queried during wave picking, task confirmation, LPN-directed movement, and inquiry activity.

Underlying Base Objects

The view is defined entirely over the documented base object WMS_WP_TASKS_GTMP, which is exposed in the APPS schema through a synonym. Because the base is a global temporary table, the physical rows visible through the view are session-scoped and are populated and consumed within the same runtime context that generates the tasks. The view adds no join logic, filters, or transformations; it is a projection of selected columns from the base object. This means the view inherits the temporary, session-bound nature of the underlying structure and should not be treated as a persistent historical record.

Key Columns

Common Use Cases and Queries

Because the user search focused on from_lpn, the most relevant scenario is retrieving tasks by their source license plate. A typical query filters the view on FROM_LPN to list all pending movements originating from a given LPN:

SELECT task_id, from_lpn, to_lpn, item, subinventory, locator,
transaction_quantity, transaction_uom, status
FROM apps.wms_wp_tasks_gtmp_v
WHERE from_lpn = :p_from_lpn
ORDER BY task_id;

Other common uses include joining TASK_ID to transaction history for audit reconciliation, filtering by STATUS to identify open tasks, or grouping by USER_TASK_TYPE for workload analysis. Because the underlying structure is temporary, queries are normally issued from within the same session or concurrent request that populated it.