Search Results cs_sr_uwq_nodes_u1

Overview

CS_SR_UWQ_NODES_B is a Service (CS) schema table in Oracle E-Business Suite that stores the non-translated base definitions for Universal Work Queue (UWQ) non-media nodes. In EBS Release 12.1.1 and 12.2.2, UWQ provides the unified queue framework used by service agents, field service personnel, and contact center users to view and act on work items across multiple channels. Each row in this table defines a queue node: the view or data source that supplies the underlying service request rows, the filtering predicate, the hierarchical placement of the node, and the SQL or cursor mechanism used to populate it. The companion table CS_SR_UWQ_NODES_T holds the translated (language-specific) attributes, so this "_B" table is the master definition record.

From a Data Vault modeling perspective, the heuristic classification for this object is standalone. There are no parent-key relationships fanning out from this table; its foreign keys point outward to reference data (media types and security groups). It therefore behaves most naturally as a hub-like entity keyed on the node identifier, with descriptive attributes that could be modeled as a satellite. This is a suggestion only, not an enforced design.

Key Information Stored

The table contains 22 documented columns. The most operationally significant are:

• NODE_ID — Surrogate primary key (constraint CS_SR_UWQ_NODE_PK) and the identifier of the node. It is also the leading column of the unique index CS_SR_UWQ_NODES_U1 (NODE_ID, ZD_EDITION_NAME), which serves as the business-key candidate under the editioning model.
• NODE_VIEW — The view on which the node metadata is defined; the physical source object the node queries.
• DATA_SOURCE — The data source that supplies the service requests displayed by the node.
• MEDIA_TYPE_ID — Foreign key to IEU_UWQ_MEDIA_TYPES_B, binding the node to a media type (phone, e-mail, web, and so on).
• WHERE_CLAUSE — The predicate applied to filter rows returned to the queue.
• NODE_TYPE / NODE_QUERY — Classify the node and specify whether its query is Single or Cursor based.
• CURSOR_SQL / CURSOR_KEY_COL — The cursor SQL that generates UWQ node rows, and the key column used to build the WHERE clause for cursor-based queries.
• PARENT_ID / NODE_DEPTH — Define the node's position in the UWQ hierarchy (depth and parent linkage).
• HIDE_IF_EMPTY / ENABLED_FLAG — Control node visibility when empty and enable/disable the node.
• RES_CAT_ENUM_FLAG — Default query override option flag for resource category enumeration.
• SECURITY_GROUP_ID — Foreign key to FND_SECURITY_GROUPS, supporting application hosting and data isolation.
• Standard WHO columns (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, OBJECT_VERSION_NUMBER) — Audit and optimistic-locking columns.
• ZD_EDITION_NAME — Editioning column used by the EBS online patching infrastructure in 12.2.x.

Common Use Cases and Queries

Typical uses include auditing queue configuration, diagnosing why a node returns no work items, and reporting the hierarchy of nodes exposed to agents.

• List all enabled top-level nodes and their media types:

  SELECT n.NODE_ID, n.NODE_TYPE, m.MEDIA_NAME
  FROM   CS.CS_SR_UWQ_NODES_B n, IEU.IEU_UWQ_MEDIA_TYPES_B m
  WHERE  n.MEDIA_TYPE_ID = m.MEDIA_TYPE_ID
  AND    n.ENABLED_FLAG = 'Y'
  AND    n.PARENT_ID IS NULL;

• Reconstruct the node hierarchy by self-joining on PARENT_ID to walk NODE_DEPTH.
• Identify nodes with custom CURSOR_SQL or WHERE_CLAUSE overrides that may need review after an upgrade, filtering on RES_CAT_ENUM_FLAG.
• Report nodes hidden when empty to explain gaps in the agent queue display.

Related Objects

• IEU.IEU_UWQ_MEDIA_TYPES_B — referenced via MEDIA_TYPE_ID; defines the media type for each node.
• FND.FND_SECURITY_GROUPS — referenced via SECURITY_GROUP_ID for hosting and security partitioning.
• CS.CS_SR_UWQ_NODES_T — the translated (language) sibling holding node display names.
• CS_SR_UWQ_NODES_U1 / CS_SR_UWQ_NODE_PK — the unique index and primary key constraints enforcing node identity.

These relationships reflect the documented foreign-key and unique-index structure; additional dependencies on UWQ runtime views and service request tables follow from the NODE_VIEW and DATA_SOURCE configuration rather than from declared constraints.