Search Results cursor_key_col

Overview

CS_SR_UWQ_NODES_VL is a translatable (VL) view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the Service (CS) module. It serves as the base view for the form CSXNODES and presents all user-defined Universal Work Queue (UWQ) nodes configured for Service Requests. In the broader EBS architecture, UWQ nodes define the navigable structure and content filters that agents see within the Universal Work Queue, so this view effectively exposes the metadata that drives node rendering, child structuring, and query behaviour.

Because it is a reporting-oriented, denormalised read layer combining base and translation data, the view is the natural access point for reporting, integration, and diagnostic queries that need node definitions in the session language. The _VL suffix indicates that translated label content is resolved automatically, removing the need for callers to join the translation table explicitly. From a reporting perspective, the view isolates consumers from the physical parent/child table design while still surfacing the technical attributes required to reason about node behaviour.

The user search term "node_label" corresponds directly to a first-class column in this view, making CS_SR_UWQ_NODES_VL the correct object when node labels must be retrieved alongside their technical definitions.

Underlying Base Objects

The view is defined over two documented synonym-referenced base objects:

• CS_SR_UWQ_NODES_B — the base (non-translated) table holding the node's structural and behavioural attributes, including identity, hierarchy, query configuration, and audit columns.
• CS_SR_UWQ_NODES_TL — the translation table holding the language-specific NODE_LABEL values.

The view joins CS_SR_UWQ_NODES_B to CS_SR_UWQ_NODES_TL on NODE_ID with the language predicate UWQ_TL.LANGUAGE = USERENV('LANG'), which resolves the label in the current session's language. A second, outer-joined instance of the translation table (UWQ_TL1) resolves the parent node's label via UWQ_TL1.NODE_ID(+) = UWQ_B.PARENT_ID, producing the PARENT_LABEL column. The view therefore supports self-referencing hierarchy traversal without requiring the caller to understand the parent/child link in advance.

Note that the outer-join language predicate is written as UWQ_TL.LANGUAGE(+) = USERENV('LANG') in the documented view text; where no parent label exists, PARENT_LABEL is returned as null.

Key Columns

• NODE_ID — unique identifier of the UWQ node; the primary join key across both base objects.
• NODE_LABEL — the translated, user-visible name of the node, sourced from the translation table in the session language. This is the column referenced by the search term "node_label".
• PARENT_ID / PARENT_LABEL — the parent node identifier and its translated label, enabling hierarchy reporting and root/node listing.
• NODE_TYPE, NODE_VIEW, NODE_DEPTH — classify the node and describe its presentation and position in the hierarchy.
• DATA_SOURCE, WHERE_CLAUSE, NODE_QUERY, CURSOR_SQL, CURSOR_KEY_COL — the technical definition of how the node sources and filters its data.
• MEDIA_TYPE_ID, RES_CAT_ENUM_FLAG, HIDE_IF_EMPTY — display and behavioural flags governing node rendering.
• ENABLED_FLAG — indicates whether the node is active.
• OBJECT_VERSION_NUMBER, CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, ROW_ID — standard audit and concurrency columns.

Common Use Cases and Queries

Typical uses include enumerating all configured nodes for administrative review, building hierarchy reports of parent and child nodes, and validating the query definitions behind each node. A representative query lists enabled nodes with their labels and parents:

• SELECT node_id, node_label, parent_id, parent_label, node_type, node_depth, enabled_flag FROM apps.cs_sr_uwq_nodes_vl WHERE enabled_flag = 'Y' ORDER BY node_depth, node_label;
• Hierarchy inspection: SELECT node_label, parent_label FROM apps.cs_sr_uwq_nodes_vl WHERE parent_id IS NOT NULL;
• Technical audit: SELECT node_id, node_label, data_source, where_clause, cursor_sql FROM apps.cs_sr_uwq_nodes_vl;

Because label resolution depends on USERENV('LANG'), results vary by session language; callers requiring fixed-language output should query the translation table directly or constrain the language explicitly.