Results for “sref_type”

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

Overview

The IEO_VDU_INFO table is a configuration repository within the Oracle EBS Interaction Center Technology (IEO) module. It stores detail records describing Voice Data Unit (VDU) setups used by the Interaction Center telephony integration layer. Each row represents a specific VDU instance, capturing the dialer, extension, and PBX-related attributes required to route and manage inbound and outbound telephony interactions.

From a data modeling perspective, the heuristic classification of IEO_VDU_INFO is satellite-leaning, suggesting it functions as a descriptive satellite attached to a parent business entity (represented by IEO_PBX_INFO). Its foreign key to IEO_PBX_INFO, keyed on the combination of SREF_TYPE and PBX_NAME, reinforces this interpretation; the VDU records qualify and extend PBX configuration rather than define an independent hub.

Key Information Stored

The table contains 19 documented columns. The most significant are:

• VDU_INFO_ID — Surrogate primary key (VDU_PK) uniquely identifying each VDU record.
• VDU_NAME — Business identifier for the VDU configuration; likely the primary business-key candidate.
• PBX_NAME — References the parent PBX configuration in IEO_PBX_INFO; part of the foreign key.
• SREF_TYPE — Source reference type, paired with PBX_NAME in the foreign key to IEO_PBX_INFO.
• ACTUAL_PBX_NAME — The effective PBX name, which may differ from the configured PBX_NAME.
• DIALER_PORT, DIALER_TYPE, DIALER_STATUS, and DIAL_PROFILE_NAME — Dialer operational parameters governing outbound and inbound call handling.
• EXTENSION and EXT_QUALIFIER — Telephony extension details associated with the VDU.
• IO_TRACE_FLAG — Debug/tracing toggle for the VDU's input/output activity.
• SECURITY_GROUP_ID — Foreign key to FND_SECURITY_GROUPS, enforcing multi-org data security.
• OBJECT_VERSION_NUMBER — Optimistic locking control column.
• The standard WHO columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN) provide audit trail data.

Common Use Cases and Queries

Administrators and developers query this table to audit VDU configurations, troubleshoot dialer connectivity, and verify extension assignment. A common reporting pattern joins the VDU row to its parent PBX record:

SELECT v.VDU_NAME, v.PBX_NAME, v.DIALER_PORT,
       v.DIALER_STATUS, v.EXTENSION
FROM   IEO.IEO_VDU_INFO v,
       IEO.IEO_PBX_INFO  p
WHERE  v.SREF_TYPE = p.SREF_TYPE(+)
AND    v.PBX_NAME  = p.PBX_NAME(+);

Support teams filter on DIALER_STATUS to identify inactive or misconfigured VDUs, while integration developers inspect IO_TRACE_FLAG to enable diagnostics during telephony troubleshooting. Multi-org-aware queries should additionally constrain SECURITY_GROUP_ID.

Related Objects

• IEO_PBX_INFO — Parent PBX configuration table; joined on SREF_TYPE and PBX_NAME.
• FND_SECURITY_GROUPS — Referenced via SECURITY_GROUP_ID for data-security enforcement.
• IEO Interaction Center runtime components — Consume VDU definitions for call routing and dialer control.
• FND_OBJECTS / WHO columns — Populated via standard EBS audit conventions.

In Oracle EBS 12.1.1 and 12.2.2, IEO_VDU_INFO remains a stable reference object with no documented version-specific structural changes; the primary key and foreign-key relationships are consistent across both releases.