Search Results ieu_wp_ui_comp_datatypes




Overview
Explore in AI Chat

Overview

The IEU.IEU_WP_UI_COMP_DATATYPES table is a configuration metadata object within the IEU – Universal Work Queue (UWQ) module of Oracle E-Business Suite, available in both 12.1.1 and 12.2.2. Its documented purpose is "UI Component – Data Types mapping." The table establishes the permitted data types that each UI component (defined in IEU_WP_UI_COMPONENTS_B) may render or accept within the Universal Work Queue framework, which brokers inbound work items across CRM, TeleService, and other call-center modules.

Each row maps a single UI component to one supported data type, and an administrative identifier (UI_COMP_DATATYPE_MAP_ID) anchors the record. The ETRM relationship metadata classifies this table heuristically as standalone in Data Vault terms; a modeling suggestion would treat it as a small reference or link-style association table rather than a hub or satellite, since its grain is the component-to-data-type pairing and its lifecycle is configuration, not transactional history.

Key Information Stored

The physical schema exposes eleven columns in 12.2.2:

The unique index IEU_WP_UI_COMP_DATATYPES_U1 spans UI_COMP_DATATYPE_MAP_ID and ZD_EDITION_NAME, which is the documented business-key candidate: in 12.2 the edition name disambiguates rows across patch editions, while the surrogate ID remains the stable primary key for joins.

Common Use Cases and Queries

Because this table is configuration-driven, its primary use cases are validating and reporting on UWQ component setup. A typical diagnostic query joins the mapping to its parent component to list supported data types:

  • Listing all data types registered for a given UI component: SELECT m.ui_comp_id, m.data_type FROM ieu.ieu_wp_ui_comp_datatypes m WHERE m.ui_comp_id = :p_comp_id;
  • Detecting orphaned mappings (components referenced but missing from IEU_WP_UI_COMPONENTS_B) using an outer join on UI_COMP_ID.
  • Reporting configuration changes by LAST_UPDATED_BY / LAST_UPDATE_DATE for audit purposes.
  • Filtering by SECURITY_GROUP_ID to confirm row-level visibility for a given responsibility.
  • Verifying 12.2 edition coverage via ZD_EDITION_NAME after an online patching cycle.

Reports typically drive off the unique index and the composite join to the components table; production queries should always include SECURITY_GROUP_ID predicates to respect Multi-Org style security.

Related Objects

  • IEU_WP_UI_COMPONENTS_B — parent component definitions; join on UI_COMP_ID = UI_COMPONENTS_B.UI_COMP_ID.
  • FND_SECURITY_GROUPS — security group reference; join on SECURITY_GROUP_ID.
  • IEU_WP_UI_COMP_DATATYPES_PK — primary key constraint enforcing uniqueness on UI_COMP_DATATYPE_MAP_ID.
  • IEU_WP_UI_COMP_DATATYPES_U1 — unique index on UI_COMP_DATATYPE_MAP_ID and ZD_EDITION_NAME.
  • Related UWQ configuration tables (IEU_WP_UI_COMPONENTS_TL, work queue and routing tables) that reference the same component identifiers.