Search Results uwq_b

Overview

The view APPS.CS_SR_UWQ_NODES_VL is a localized (VL-suffixed) reporting and integration view in Oracle E-Business Suite, owned by the APPS schema. It is part of the Customer Service (CS) module and underpins the Universal Work Queue (UWQ) infrastructure. The view presents the nodes that make up the UWQ navigation tree, combining translatable node labels with their structural and behavioral attributes. Because the view is defined as a "VL" (view with localization) object, it resolves the display label for the session's current language using USERENV('LANG') against the translation table, while exposing the non-translatable node definition from the base table. In Oracle EBS 12.1.1 and 12.2.2 the view serves as the read-consistent, language-aware access point used by the UWQ runtime and by custom reports and integrations that need to enumerate or describe work queue nodes without directly touching the _B and _TL tables.

Underlying Base Objects

The documented ETRM metadata lists the referenced base objects as synonyms CS_SR_UWQ_NODES_B and CS_SR_UWQ_NODES_TL. The _B table stores the language-independent definition of each UWQ node, including its identifier, view name, data source, and query configuration. The _TL table stores the language-dependent node label keyed by NODE_ID and LANGUAGE. The VL view joins these to produce one row per node, with the label resolved for the session language. The view text also performs a self-join of CS_SR_UWQ_NODES_TL as UWQ_TL1 (outer-joined via NODE_ID(+) = PARENT_ID) to derive the parent node label. Both joins to the _TL table are governed by LANGUAGE = USERENV('LANG'), ensuring labels are returned in the user's current language and, where a translation is missing, the outer join preserves the parent relationship so the row is not lost. The view also exposes ROWID from the base table as ROW_ID, supporting row-level addressing in EBS forms and integrations.

Key Columns

The view exposes the full structural definition of each UWQ node alongside resolved labels. Important columns include:

• NODE_ID — Primary identifier of the work queue node; the join key across the view and its base tables.
• NODE_LABEL — The language-localized display name of the node, sourced from CS_SR_UWQ_NODES_TL.
• PARENT_ID / PARENT_LABEL — The parent node identifier together with its localized label, enabling hierarchical navigation and rollup reporting. PARENT_LABEL is derived from the UWQ_TL1 alias.
• NODE_VIEW, DATA_SOURCE, NODE_QUERY, CURSOR_SQL, CURSOR_KEY_COL — The configuration that determines how the node retrieves and presents its underlying work-queue data.
• WHERE_CLAUSE — Restriction applied to the node's data source.
• NODE_TYPE, NODE_DEPTH, HIDE_IF_EMPTY — Structural and presentational attributes controlling node behavior, nesting level, and visibility when no data exists.
• MEDIA_TYPE_ID, RES_CAT_ENUM_FLAG — Media and resource-category enumerator flags relevant to routing and categorization.
• ENABLED_FLAG — Indicates whether the node is active and eligible for display or use.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, OBJECT_VERSION_NUMBER — Standard EBS audit and optimistic-locking columns inherited from the base table.

Common Use Cases and Queries

This view is typically queried to enumerate the UWQ node tree, to build custom navigation hierarchies, or to validate node configuration during troubleshooting or integration work. The following example retrieves enabled nodes with their resolved labels and parent labels:

• SELECT NODE_ID, NODE_LABEL, PARENT_ID, PARENT_LABEL, NODE_TYPE, NODE_DEPTH FROM APPS.CS_SR_UWQ_NODES_VL WHERE ENABLED_FLAG = 'Y' ORDER BY PARENT_ID, NODE_DEPTH;

Because the view filters labels by USERENV('LANG'), query results are automatically returned in the language configured for the session, making it suitable for user-facing reports without additional translation logic. A second common pattern is inspecting the data source and query definition of a specific node:

• SELECT NODE_ID, NODE_LABEL, NODE_VIEW, DATA_SOURCE, NODE_QUERY, CURSOR_SQL, WHERE_CLAUSE FROM APPS.CS_SR_UWQ_NODES_VL WHERE NODE_ID = :node_id;

Integrations that need to map work queue nodes to external routing engines can use the view to extract the enabled node hierarchy and its behavioral flags in a single query, avoiding direct joins against the _B and _TL tables and thereby honoring the localized, read-consistent access contract that the VL view provides.