Results for “media_type_map”

24 results




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

Overview

The IEU_UWQ_SVR_MPS_MMAPS table resides in the IEU schema and belongs to the Universal Work Queue (UWQ) module of Oracle E-Business Suite, present in both release 12.1.1 and 12.2.2. The table name expands to "UWQ Server (Media Provider) Media Maps," indicating its function as the mapping layer between media provider types and server types within the UWQ infrastructure. Media providers in UWQ encompass telephony, e-mail, chat, and other contact-channel integrations, and this table determines which media server handles each media type for routing and interaction processing.

The table is registered as VALID in the ETRM object inventory. Its documented physical schema carries twelve columns, a surrogate primary key, and two unique constraints. From a Data Vault modeling perspective, the ETRM heuristic classification is satellite-leaning: the table's business identity (MEDIA_TYPE_ID and SVR_TYPE_ID) is captured in a unique index, and most other attributes are descriptive or transactional in nature, suggesting it would map naturally to a satellite on a media-type/server-type link rather than an independent hub.

Key Information Stored

The documented columns of primary interest are:

The business-key candidates are IEU_UWQ_SVR_MPS_MMAPS_UK1 (MEDIA_TYPE_ID, SVR_TYPE_ID), which the user searched for under the alias "ieu_uwq_svr_mps_mmaps_uk1," and the alternate unique index U1 (MEDIA_TYPE_ID, SVR_TYPE_ID, ZD_EDITION_NAME). The foreign key to IEU_UWQ_MEDIA_TYPES_B establishes the core dependency chain.

Common Use Cases and Queries

Typical usage involves resolving which server type is configured for a given media type, and validating that no duplicate mappings exist. A representative query joins the mapping table to the media types base table:

SELECT m.SVR_MPS_MMAP_ID, mt.MEDIA_TYPE_NAME,
       m.SVR_TYPE_ID, m.MEDIA_TYPE_MAP
FROM   IEU.IEU_UWQ_SVR_MPS_MMAPS m,
       IEU.IEU_UWQ_MEDIA_TYPES_B mt
WHERE  m.MEDIA_TYPE_ID = mt.MEDIA_TYPE_ID
AND    m.SECURITY_GROUP_ID = :p_security_group;

Reporting scenarios include auditing media-provider configuration before go-live, diagnosing routing failures when an interaction arrives on an unmapped channel, and verifying that edition-aware lookups reference the correct ZD_EDITION_NAME. A duplicate-detection query against the UK1 columns is often run during setup validation.

Related Objects

The most significant related objects are the foreign-key targets and the indexes that enforce integrity:

  • IEU_UWQ_MEDIA_TYPES_B — parent table linked via MEDIA_TYPE_ID; the primary join partner.
  • FND_SECURITY_GROUPS — referenced via SECURITY_GROUP_ID for row-level security scoping.
  • IEU_UWQ_SVR_MPS_MMAPS_PK — primary key index on SVR_MPS_MMAP_ID.
  • IEU_UWQ_SVR_MPS_MMAPS_UK1 / U1 — unique business-key indexes on MEDIA_TYPE_ID and SVR_TYPE_ID.
  • IEU_UWQ_SVR_MPS_MMAPS_U2 — alternate unique index on SVR_MPS_MMAP_ID with ZD_EDITION_NAME.

Readers should treat editions-aware access patterns as mandatory in 12.2.2 environments, since both unique indexes include ZD_EDITION_NAME.