Search Results node_label

Overview

The view IEU_UWQM_WL_NODE_V belongs to the IEU - Universal Work Queue product family within Oracle E-Business Suite (12.1.1 and 12.2.2). It is documented as a view used for the UWQ selector SpreadTable, meaning it supplies the hierarchical or tabular node structure that the Universal Work Queue selector renders to end users when they drill into work queues. In practical terms, the view presents a small, already-aggregated result set in which a single row corresponds to a resource assigned to a work queue node, together with that resource's total pending work item count and the count of items currently available for immediate processing. Because the rowset is flat and pre-summarized, it can be consumed directly by the UWQ client without additional aggregation logic, and it can equally be queried by reporting or integration components that need a lightweight snapshot of queue depth per resource. Note that the ETRM metadata states this view is "not implemented in this database," so it exists only where the Universal Work Queue selector feature has been configured and the underlying referenced objects are present.

Underlying Base Objects

The view is defined over a single documented base object, IEU_UWQ_SEL_RT_NODES, which stores the selector node definitions (resource-to-node assignments) used by the Universal Work Queue. The ETRM metadata records no other documented base objects; however, the view text also invokes the PL/SQL function IEU_UWQ_GET_NEXT_WORK_PVT.GET_WORKLIST_QUEUE_COUNT, which is called three times per row and is therefore an implicit dependency. Each call is keyed by RESOURCE_ID plus a status argument (0, 1, and 2) and the row's NODE_TYPE. The filter predicates restrict the result set to nodes where NOT_VALID is null or 'N', where SEL_ENUM_ID = 10053, and where NODE_PID = 0 (root-level nodes).

Key Columns

• NODE_LABEL — the display name of the work queue node, presented directly from IEU_UWQ_SEL_RT_NODES.
• COUNT — the sum of three GET_WORKLIST_QUEUE_COUNT calls (status 0, 1, and 2), representing the total queue depth for the resource on that node.
• AVAIL_COUNT — the status-0 invocation only, i.e., items immediately available for the resource to work.
• RESOURCE_ID — the resource identifier used as the key for all three function calls and for correlating back to resource definitions.

The user's search term node_type does not appear as a projected column but is significant: it is passed into each GET_WORKLIST_QUEUE_COUNT call from the base row, meaning it qualifies the counting logic even though it is not returned in the select list. Queries filtering or grouping by node type must therefore join back to IEU_UWQ_SEL_RT_NODES.

Common Use Cases and Queries

The primary use case is populating the UWQ selector SpreadTable, but the view is also convenient for monitoring queue depth per resource and for diagnosing why work items are not surfacing. A representative query listing resources with available work, sorted by workload, is:

• SELECT node_label, resource_id, avail_count, count FROM ieu_uwqm_wl_node_v ORDER BY count DESC;
• SELECT resource_id, SUM(count) total_work FROM ieu_uwqm_wl_node_v GROUP BY resource_id;
• SELECT node_label FROM ieu_uwqm_wl_node_v WHERE avail_count > 0;

Because counts are generated at query time by PL/SQL calls, performance-sensitive reports should limit the rowset (for example, by RESOURCE_ID) and must account for the fact that results are read consistently but not transactionally frozen. Where node type analysis is required, join to IEU_UWQ_SEL_RT_NODES on RESOURCE_ID to expose the NODE_TYPE used in the underlying count calls.