Search Results total_tasks

Overview

APPS.WMS_WP_WAVE_DETAILS_GTMP_V is a reporting view in the Oracle E-Business Suite Warehouse Management System (WMS) module. It exposes wave planning and execution metrics held in the global temporary table WMS_WP_WAVE_DETAILS_GTMP, presenting a flattened, read-only projection of wave-level status and progress attributes. In Oracle EBS 12.1.1 and 12.2.2 the view is owned by the APPS schema and serves as a controlled access point for wave detail data, allowing reports, concurrent programs, and integration interfaces to consume wave metrics without directly querying the underlying temporary table.

The view is particularly relevant to users who need to aggregate or monitor the financial and volumetric footprint of waves. The presence of the TOTAL_VALUE column directly supports queries that total the monetary value of goods associated with a wave, which is the attribute most frequently referenced by searches such as "total_value." Because the source object is a global temporary table, the view reflects session-scoped intermediate results rather than permanently stored transactional records, and its contents persist only for the duration of the session or transaction that populated the temporary table.

Underlying Base Objects

The view is defined over a single documented base object: the synonym WMS_WP_WAVE_DETAILS_GTMP, which resolves to the global temporary table of the same name. No joins, unions, or additional tables are present in the view definition; it is a straight SELECT of twenty-five columns from that one source. This design confirms that the view is a lightweight presentation layer rather than a transformation or aggregation object. All filtering, sorting, and aggregation logic is expected to be applied by the consuming query, not by the view itself.

Because the referenced object is a global temporary table, the data visible through WMS_WP_WAVE_DETAILS_GTMP_V is session-private by default. Each concurrent program or user session that populates the temporary table sees only its own rows, which prevents cross-session data leakage but also means the view cannot be used to query wave history in the way a permanent table would allow.

Key Columns

• WAVE_HEADER_ID — Identifier linking the row to the wave header record; the primary join key to wave-level entities.
• WAVE_NAME and STATUS — Human-readable wave identifier and current processing state.
• START_TIME, TARGET_COMPLETION, ACTUAL_COMPLETION — Scheduling and milestone timestamps for the wave.
• TOTAL_LINES, TOTAL_WEIGHT, TOTAL_VALUE, TOTAL_VOLUME, TOTAL_TASKS — Aggregate measures describing the wave's workload and commercial magnitude. TOTAL_VALUE carries the monetary sum associated with the wave.
• TOTAL_EXCEPTIONS, MODERATE_EXCEPTIONS, SEVERE_EXCEPTIONS — Exception counts, graded by severity, for operational monitoring.
• READY_TO_RELEASE, BACK_ORDERED, CROSSDOCK_PLANNED, REPLENISHMENT_PLANNED, TASKED, PICKED, PACKED, STAGED, LOADED_TO_DOCK, SHIPPED — Stage indicators reflecting progress through the wave lifecycle.
• CREATED_BY — Standard audit column identifying the originating user.

Common Use Cases and Queries

The most direct use case is value reporting on waves. A typical query retrieves wave-level totals, optionally filtered by status:

• SELECT wave_name, total_value, total_lines FROM apps.wms_wp_wave_details_gtmp_v WHERE status = 'RELEASED';
• SELECT wave_header_id, total_value, total_weight, total_volume FROM apps.wms_wp_wave_details_gtmp_v ORDER BY total_value DESC;
• SELECT SUM(total_value) FROM apps.wms_wp_wave_details_gtmp_v;

Operational monitoring queries use the exception and stage columns to track wave health and throughput. Because the underlying object is a global temporary table, any query must be executed within the session that populated it; ad hoc querying from an unrelated session will return no rows. This constraint should be respected when designing reports and concurrent programs against the view.