Results for “sel_rt_node_id”

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

Overview

IEU_UWQ_RTNODE_BIND_VALS is a table owned by the IEU schema in Oracle E-Business Suite, belonging to the Universal Work Queue (UWQ) module. Its documented purpose is to store "UWQ Selector Run-Time Nodes Bind variable information." The Universal Work Queue is the infrastructure that presents agents with configurable lists of work items drawn from multiple source systems — service requests, tasks, leads, and similar entities — and bind variables are the mechanism by which selector queries are parameterized at runtime. This table therefore captures the resolved values of those bind variables for each runtime node instance.

From a Data Vault modeling perspective, the metadata-driven heuristic classifies this object as satellite-leaning. That classification is a modeling suggestion rather than an Oracle-imposed designation: the table carries descriptive, context-specific attributes (bind variable names, values, and datatypes) that change over time and depend on a parent node, which is characteristic of satellite behaviour rather than a hub or link. Implementers designing an analytics or integration layer may find it useful to treat the table as a descriptive satellite hanging off the runtime node structure.

Key Information Stored

The table comprises 15 documented columns. The surrogate primary key is RTNODE_BIND_VAR_ID, enforced by the constraint IEU_UWQ_RTNODE_BIND_VALS_PK and reinforced by the unique index IEU_UWQ_RTNODE_BIND_VALS_U2. A second unique index, IEU_UWQ_RTNODE_BIND_VALS_U1, covers RESOURCE_ID, NODE_ID, and BIND_VAR_NAME, making that triplet the principal business-key candidate for identifying a specific bind value within the context of a resource and node.

The most significant columns are:

• RTNODE_BIND_VAR_ID — surrogate primary key uniquely identifying each bind variable row.
• SEL_RT_NODE_ID — foreign key to IEU_UWQ_SEL_RT_NODES, identifying the selector runtime node to which the bind value belongs.
• RESOURCE_ID — the resource (typically an agent or user) against which the bind value is resolved; part of the business-key candidate.
• NODE_ID — the node identifier participating in the business-key triplet.
• BIND_VAR_NAME — the name of the bind variable as referenced by the selector query.
• BIND_VAR_VALUE — the runtime value assigned to that bind variable.
• BIND_VAR_DATATYPE — the datatype descriptor used to interpret the value correctly at execution time.
• SECURITY_GROUP_ID — foreign key to FND_SECURITY_GROUPS, supporting multi-organization / security-group partitioning.
• NOT_VALID_FLAG — indicator used to mark a bind value as no longer valid for use.
• OBJECT_VERSION_NUMBER, CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard Oracle Applications who-columns and optimistic locking support.

Common Use Cases and Queries

Typical uses revolve around diagnosing why a UWQ selector returns unexpected work items, auditing which bind values were applied for a given agent, and reporting on runtime parameter configuration. A diagnostic query joining to the parent node table is common:

• SELECT v.RTNODE_BIND_VAR_ID, v.BIND_VAR_NAME, v.BIND_VAR_VALUE, v.BIND_VAR_DATATYPE FROM IEU.IEU_UWQ_RTNODE_BIND_VALS v WHERE v.SEL_RT_NODE_ID = :node_id ORDER BY v.BIND_VAR_NAME;
• Filtering by RESOURCE_ID to determine the effective parameters for a specific agent's queue.
• Filtering on NOT_VALID_FLAG = 'N' to exclude stale or superseded bind values from reports.
• Joining to FND_SECURITY_GROUPS on SECURITY_GROUP_ID when producing multi-org aware extracts.

Related Objects

The primary parent is IEU_UWQ_SEL_RT_NODES, joined via IEU_UWQ_RTNODE_BIND_VALS.SEL_RT_NODE_ID = IEU_UWQ_SEL_RT_NODES.SEL_RT_NODE_ID; this is the dominant dependency and the one to trace when reconstructing selector behaviour. FND_SECURITY_GROUPS is referenced via SECURITY_GROUP_ID and governs visibility. Additional meaningful context comes from the IEU_UWQ selector node and resource-related tables that supply NODE_ID and RESOURCE_ID semantics, and from FND_USER for resolving CREATED_BY and LAST_UPDATED_BY to named accounts. The unique index IEU_UWQ_RTNODE_BIND_VALS_U1 should be treated as the reliable lookup path for point queries by resource, node, and variable name.