Search Results is_uwq_server_required

Overview

IEU_PUB is a public PL/SQL package in the Oracle E-Business Suite Applications (APPS) schema that supports the Universal Work Queue (UWQ) framework. UWQ provides a centralized, extensible infrastructure through which agents access work items originating from multiple source applications, including Service (TeleService), Interaction Center, and third-party integrations. The package exposes the runtime data model, enumerator metadata, and node resolution logic that allow a work queue session to determine which resource categories are available to an agent, which media types that agent may handle, whether a UWQ server process is required, and how individual work queue nodes are materialized and rendered.

The package declares a rich set of PL/SQL record and collection types at specification level — including EnumeratorDataRecord, BindVariableRecord, PluginDataRecord, and NodeDetailRecord along with their corresponding BINARY_INTEGER-indexed tables. These types formalize the structure of enumerator definitions stored in the UWQ setup tables and the runtime bind variables applied to node queries. The package is compiled with AUTHID CURRENT_USER, so name resolution occurs against the invoker's schema, which is significant when the runtime views referenced by nodes are owned by different application schemas. The header indicates the base implementation dates to 2005 and has remained stable across the 12.1.1 and 12.2.2 releases.

Key Procedures and Functions

The documented public interface comprises seven callable units:

• ADD_UWQ_NODE_DATA — The procedure most directly relevant to the search term. It populates and registers the data required to render an individual work queue node, assembling the node's metadata (view name, data source, media type, where clause, node type, and related attributes) into the internal structures that the UWQ runtime consumes.
• GET_UWQ_NODE_DETAILS — Returns the resolved detail record for a given node, expanding the base where clause into the complete and raw complete clauses, and exposing refresh view information used to drive periodic node refresh.
• GET_ENUM_RES_CAT — Retrieves resource category enumerator configuration, used to build the navigable category tree presented to agents in the work queue.
• SET_BIND_VAR_DATA — Persists or assigns bind variable name, value, and datatype tuples that are applied to node queries at runtime, allowing parameterized views to execute correctly per session or per node.
• IS_AGENT_ELIGIBLE_FOR_MEDIA — Determines whether a given agent is authorized to work items of a specified media type, supporting queue filtering and routing.
• IS_UWQ_SERVER_REQUIRED — Indicates whether the current configuration requires a dedicated UWQ server process to service queue requests.

Tables Accessed

The package reads and writes the core UWQ configuration tables through APPS synonyms:

• IEU_UWQ_SEL_RT_NODES — Stores the runtime node definitions, including node label, view name, data source, media type, where clause, node type, hide-if-empty flag, refresh view, and resource category enumerator flag. This is the primary source for NODE metadata.
• IEU_UWQ_RTNODE_BIND_VALS — Holds bind variable definitions (name, value, datatype) associated with runtime nodes, consumed by SET_BIND_VAR_DATA.
• IEU_UWQ_SEL_ENUMERATORS — Stores enumerator definitions used to build the selection tree.
• IEU_UWQ_RES_CATS_B — The resource category base table, read by GET_ENUM_RES_CAT.
• DUAL and PLITBLM — Utility references, the latter typically used to iterate over string lists or index-by tables.

Usage Notes

IEU_PUB is invoked primarily from UWQ runtime code paths rather than directly by end users. In practice it is called by the Agent Dashboard, Interaction Center, and Service responsibility screens when a work queue session initializes or refreshes, and by concurrent or server processes when node data is materialized. Because the package is referenced by 25 other packages, customizations should treat it as a stable integration point: extensions should call the published procedures rather than querying or modifying the underlying IEU_UWQ_* tables directly. When developing custom nodes, ADD_UWQ_NODE_DATA and SET_BIND_VAR_DATA are the supported entry points for registering node payloads and their bind variables, while GET_UWQ_NODE_DETAILS provides the means to introspect resolved node definitions at runtime.