Search Results wms_els_grouped_tasks




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

Overview

WMS_ELS_GROUPED_TASKS_VL is a Multi-Lingual Support (MLS) view owned by the APPS schema in Oracle E-Business Suite, defined within the Warehouse Management (WMS) product. It exposes the grouped task records maintained by the Engineered Labor Standards (ELS) subsystem, which organizes warehouse work into logical task groups that are subsequently assigned to workers and measured against engineered travel and activity standards. The "_VL" suffix denotes that this is a language-dependent (translated) view: it joins a transactional base table with its translation table so that the descriptive text is returned in the runtime session language. Because it surfaces the DESCRIPTION column alongside all operational attributes, the view is suited to reporting, concurrent programs, and integration endpoints that need human-readable group definitions rather than raw identifiers alone. A user searching for labor_txn_source_id will find that attribute exposed here as LABOR_TXN_SOURCE_ID, which ties each grouped task back to the labor transaction source that originated the work.

Underlying Base Objects

The view is defined over two synonyms resolved at runtime against tables in the WMS schema:

The two are joined on ELS_GROUP_ID, with WEL.LANGUAGE restricted to USERENV('LANG') so that only the translation row matching the session's language is returned. This is the standard MLS pattern in EBS 12.1.1 and 12.2.2 and is the only join condition in the view definition; there is no outer join, so a grouped task without a matching translation row for the session language will not appear. All columns projected from the base table are passed through unchanged.

Key Columns

  • ELS_GROUP_ID — primary grouping identifier and the join key to the translation table.
  • LABOR_TXN_SOURCE_ID — identifier of the labor transaction source that generated or seeded the grouped task; the column most commonly used to trace a group back to its originating labor transaction.
  • ORGANIZATION_ID — the warehouse (inventory organization) to which the group belongs.
  • ACTIVITY_ID / ACTIVITY_DETAIL_ID / OPERATION_ID — the engineered standard activity, its detail, and the operation context used for labor measurement.
  • SOURCE_ZONE_ID / SOURCE_SUBINVENTORY / DESTINATION_ZONE_ID / DESTINATION_SUBINVENTORY — the material flow endpoints defining where the group's tasks pick from and drop to.
  • TASK_METHOD_ID / TASK_RANGE_FROM / TASK_RANGE_TO / GROUP_SIZE — how tasks are grouped and the size of the group.
  • EXPECTED_TRAVEL_TIME / ACTUAL_TRAVEL_TIME — standard versus realized travel time, supporting variance analysis.
  • ATTRIBUTE_CATEGORY and ATTRIBUTE1–15 — descriptive flexfield columns available for customer-defined extensions.
  • DESCRIPTION / LANGUAGE / SOURCE_LANG — translated group description and language metadata.

Common Use Cases and Queries

Typical applications include reviewing grouped tasks for a warehouse, reconciling travel-time performance, and tracing groups back to a labor transaction source. The following query lists active groups for an organization, filtered by labor transaction source:

SELECT els_group_id,
       organization_id,
       labor_txn_source_id,
       activity_id,
       group_size,
       expected_travel_time,
       actual_travel_time,
       description
FROM   apps.wms_els_grouped_tasks_vl
WHERE  organization_id = :p_org_id
AND    labor_txn_source_id = :p_labor_txn_source_id;

For variance reporting, aggregate expected against actual travel time by task method:

SELECT task_method_id,
       COUNT(*) AS group_count,
       SUM(expected_travel_time) AS expected_total,
       SUM(actual_travel_time)   AS actual_total
FROM   apps.wms_els_grouped_tasks_vl
WHERE  organization_id = :p_org_id
GROUP  BY task_method_id;

Because the view enforces a session-language translation join, reports must run under a session whose language has a corresponding row in WMS_ELS_GROUPED_TASKS_TL; otherwise valid base records may be silently omitted. When an untranslated listing is required, query the base table directly instead of the _VL view.