Results for “media_type_name”

50+ results




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

Overview

IEU_UWQ_MEDIA_TYPES_TL is the translation (language-dependent) table for UWQ Media Types within the IEU – Universal Work Queue module of Oracle E-Business Suite. Universal Work Queue provides a unified, multi-channel framework through which agents and knowledge workers receive and manage work items originating from disparate sources such as telephony, e-mail, web, and task systems. Each logical media type (for example, a specific communication channel or work-item category) is defined once in the base table and described in one or more languages through this translation table.

The object resides in the IEU schema with status VALID and carries 13 documented columns in the 12.2.2 physical schema. Because it stores purely descriptive, language-specific attributes keyed to a parent entity defined elsewhere, the mined Data Vault classification is satellite-leaning. In Data Vault terms, this is best modeled as a satellite hanging off the media-type hub, where the hub's business key is inherited from IEU_UWQ_MEDIA_TYPES_B and the translation table contributes descriptive context per language. This classification is a modeling suggestion derived from the foreign-key topology, not a physical schema constraint.

Key Information Stored

The table's most significant columns fall into three groups: identity, descriptive text, and standard EBS audit/security columns.

The primary key is IEU_UWQ_MEDIA_TYPES_TL_PK over (MEDIA_TYPE_ID, LANGUAGE). A second unique index, IEU_UWQ_MEDIA_TYPES_TL_U1 over (MEDIA_TYPE_ID, LANGUAGE, ZD_EDITION_NAME), acts as the business-key candidate and edition-aware uniqueness guard. The surrogate ID alone is not unique in this table—uniqueness requires the language qualifier.

Common Use Cases and Queries

Typical usage centers on NLS-aware lookups of media type names for UI rendering, agent configuration reports, and data extracts that must respect the session language while falling back to the base language when no translation exists. A representative query retrieves the translated name for a given media type:

  • SELECT media_type_name FROM ieu.ieu_uwq_media_types_tl WHERE media_type_id = :id AND language = USERENV('LANG');
  • Joined listing of all channels: SELECT b.media_type_id, t.media_type_name FROM ieu_ieu_uwq_media_types_b b, ieu_ieu_uwq_media_types_tl t WHERE b.media_type_id = t.media_type_id AND t.language = USERENV('LANG');
  • Coverage audit identifying media types lacking a translation in a target language, useful before enabling a locale.
  • Security-group-scoped reporting: filter on SECURITY_GROUP_ID for multi-org visibility.

Because this table is a translation satellite, direct DML is normally performed through the standard translation maintenance UI (Application Object Library / ADF translation forms) rather than ad-hoc SQL, ensuring the who-columns and OBJECT_VERSION_NUMBER remain consistent.

Related Objects

The following objects are most significant to this table, based on documented primary-key and foreign-key relationships:

  • IEU_UWQ_MEDIA_TYPES_B – The base (language-independent) table; joined on MEDIA_TYPE_ID. This is the parent hub from which the translation inherits its key.
  • FND_SECURITY_GROUPS – Referenced via SECURITY_GROUP_ID, governing row-level security and multi-org access.
  • IEU_UWQ_MEDIA_TYPES_TL_PK / _U1 – The primary-key and edition-aware unique indexes that enforce row identity and business-key uniqueness.
  • IEU_UWQ_MEDIA_TYPES_VL – The conventional EBS translation view that joins _B and _TL, exposing translated columns as a single logical entity to forms and concurrent programs.
  • FND_LANGUAGES – Supplies the valid values for LANGUAGE and source-language resolution.

Together these objects form a standard EBS translated-entity pattern: a base table carrying the surrogate key, a translation table carrying language-specific descriptive text, and a view presenting the merged result. Understanding this structure is essential for correct NLS-aware querying and for planning locale rollouts in the Universal Work Queue module.