Search Results ieu_wp_ui_components_b




Overview
Explore in AI Chat

Overview

The IEU_WP_UI_COMPONENTS_B table is a core configuration and metadata repository within the Oracle E-Business Suite Universal Work Queue (UWQ) module, owned by the IEU schema. It serves as the master (base) table for defining user interface components that are rendered within the UWQ framework. In Oracle EBS 12.1.1 and 12.2.2, UWQ is the agent-facing console that aggregates work items from multiple source applications—such as Service Requests, Tasks, and Collections—into a unified interface. The records in IEU_WP_UI_COMPONENTS_B describe the reusable UI building blocks (forms, regions, and property classes) that the UWQ runtime engine instantiates dynamically at runtime.

From a Data Vault modeling perspective, this table carries a hub-leaning classification based on its foreign key topology. It anchors a stable business key (UI_COMP_ID) and is referenced by downstream tables rather than itself being a purely descriptive satellite or a transactional link. This suggests it functions as a durable entity hub for UI component identity.

Key Information Stored

The table contains 13 documented columns. The most significant include:

The unique index IEU_WP_UI_COMPONENTS_B_U1 spans (UI_COMP_ID, ZD_EDITION_NAME), confirming that ZD_EDITION_NAME participates in the business key to support edition-aware uniqueness. The surrogate PK remains UI_COMP_ID alone.

Common Use Cases and Queries

Typical scenarios include runtime resolution of UWQ component definitions, auditing component configuration across editions, and joining to translated text. A representative query retrieving component metadata with its translation is:

  • SELECT b.UI_COMP_ID, b.UI_COMP_CATG_CODE, b.FORM_COMP_CODE, t.UI_COMP_NAME FROM IEU.IEU_WP_UI_COMPONENTS_B b, IEU.IEU_WP_UI_COMPONENTS_TL t WHERE b.UI_COMP_ID = t.UI_COMP_ID AND t.LANGUAGE = USERENV('LANG');
  • Filtering by security: ... WHERE b.SECURITY_GROUP_ID = :sgid;
  • Edition-aware lookups in 12.2.2 should include WHERE ZD_EDITION_NAME = 'RELEASE_12_2_2' (or the active edition) to avoid cross-edition duplicates.

Reporting use cases cover gap analysis of undefined components, impact assessment before patching, and data lineage tracing from UI component to translation and datatype bindings.

Related Objects

The following dependency relationships are documented:

  • IEU_WP_UI_COMPONENTS_TL — Translation table; joins on UI_COMP_ID, supplying language-specific names and descriptions.
  • IEU_WP_UI_COMP_DATATYPES — Normalized child holding datatype bindings per component; joins on UI_COMP_ID.
  • FND_SECURITY_GROUPS — Referenced via SECURITY_GROUP_ID for security group resolution.
  • IEU_WP_UI_COMPONENTS_B_PK — Primary key constraint enforcing UI_COMP_ID uniqueness.
  • IEU_WP_UI_COMPONENTS_B_U1 — Composite unique index (UI_COMP_ID, ZD_EDITION_NAME) supporting editioning.

Together these objects form the metadata backbone for UWQ UI rendering and require consistent maintenance during upgrades and edition transitions.