Search Results ieu_cli_prov_plugins




Overview
Explore in AI Chat

Overview

IEU_CLI_PROV_PLUGINS is a configuration table in the IEU (Universal Work Queue) schema of Oracle E-Business Suite, holding the registry of client-side media provider plugins used by Universal Work Queue. Universal Work Queue is the agent-facing work distribution and routing framework within Oracle EBS, and it relies on media provider plugins to render and interact with different communications channels — inbound and outbound telephony, e-mail, chat, and web interactions. This table tells the UWQ client which Java plugin class to instantiate for a given media provider, and whether that plugin is currently enabled. The table is documented as VALID in the ETRM repository at the 12.2.2 release level and is present in both 12.1.1 and 12.2.2 environments.

From a heuristic Data Vault modeling perspective, the ETRM-derived classification for this object is standalone. In Data Vault terms this would typically be modeled as a satellite (or, where all rows are independent configuration records with no parent hub, as a standalone reference table), since the object holds descriptive, non-transactional attributes identified by a single surrogate key and carries no documented foreign-key relationships to other hubs.

Key Information Stored

The table contains eleven documented columns. The most important are:

  • PLUGIN_ID — the surrogate primary key, enforced by the IEU_CLI_PROV_PLUGINS_PK constraint. This is the value used internally to reference a specific media provider plugin.
  • PLUGIN_CLASS_NAME — the fully qualified name of the Java class implementing the client-side media provider plugin. This is a business-key candidate, protected by the unique index IEU_CLI_PROV_PLUGINS_U1.
  • IS_ACTIVE_FLAG — indicates whether the plugin registration is enabled for use by the UWQ client. Inactive rows are effectively retired plugins retained for history.
  • APPLICATION_ID — the Oracle EBS application that owns the plugin registration, allowing the plugin registry to be partitioned by application context.
  • OBJECT_VERSION_NUMBER — the standard Oracle EBS optimistic locking column used to detect concurrent updates.
  • CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — the standard WHO audit columns capturing who created and last modified each plugin record and when.
  • ZD_EDITION_NAME — the editioning column used by Oracle EBS's online patching (adop) architecture in 12.2; together with PLUGIN_ID this forms the unique index IEU_CLI_PROV_PLUGINS_U2 (PLUGIN_ID, ZD_EDITION_NAME).

Note that PLUGIN_ID appears both in the PK and in the U2 unique index due to editioning; PLUGIN_CLASS_NAME is the only true business identifier.

Common Use Cases and Queries

The most common practical use of this table is troubleshooting and configuration validation: confirming which media provider plugins are registered in a given environment, and whether they are active. A representative query is:

  • SELECT plugin_id, plugin_class_name, is_active_flag, application_id FROM ieu.ieu_cli_prov_plugins WHERE is_active_flag = 'Y';
  • To locate a plugin by class: SELECT * FROM ieu.ieu_cli_prov_plugins WHERE plugin_class_name = :class_name;

Reporting uses include producing an inventory of enabled media channels for an implementation, and auditing which application owns each plugin registration. When investigating UWQ client failures (for example, a missing or uninstantiable provider), DBAs query this table to confirm the expected class name is registered and active.

Related Objects

The ETRM metadata classifies IEU_CLI_PROV_PLUGINS as standalone, with no documented foreign keys and no child tables referencing its primary key. Consequently, related objects are primarily functional rather than referential:

  • IEU_CLI_PROV_PLUGINS is referenced by the UWQ client runtime, which uses PLUGIN_CLASS_NAME to load media provider classes.
  • APPLICATION_ID logically joins to FND_APPLICATION, identifying the owning EBS application.
  • Other IEU Universal Work Queue configuration and media-related tables operate alongside this registry when routing and presenting work items.
  • Standard WHO audit columns associate with FND_USER via CREATED_BY and LAST_UPDATED_BY.

Because no formal constraints link this table to others, joins are by convention (application, user) rather than by enforced referential integrity.