Search Results ieo_svr_protocol_map_pk

Overview

IEO_SVR_PROTOCOL_MAP is a configuration table owned by the IEO schema (Interaction Center Technology) in Oracle E-Business Suite 12.1.1 and 12.2.2. It stores the mapping between a communication server component and the wire protocol that component uses to transmit or receive messages. In practical terms, the table answers the question: which transport protocol (for example, a specific telephony or messaging wire protocol) is bound to which server component within the Interaction Center infrastructure?

The table carries an ETRM-documented status of VALID and contains 11 columns. Its primary key is IEO_SVR_PROTOCOL_MAP_PK, defined on the composite of COMP_ID and WIRE_PROTOCOL. A separate unique index, IEO_SVR_PROTOCOL_MAP_U1, mirrors the same two columns (COMP_ID, WIRE_PROTOCOL), confirming that the combination of component and wire protocol is the natural business key. From a Data Vault modeling perspective, the metadata classifies this object as satellite-leaning: IEO_SVR_PROTOCOL_MAP behaves like an attribute-bearing table that hangs off the component hub represented by IEO_SVR_COMPS, rather than acting as an independent business hub or a pure many-to-many link.

Key Information Stored

The most significant columns in IEO_SVR_PROTOCOL_MAP are the following:

• COMP_ID — The identifier of the server component. It is both part of the composite primary key and a foreign key to IEO_SVR_COMPS, tying each protocol mapping to a specific server component definition.
• WIRE_PROTOCOL — The wire protocol associated with the component. Along with COMP_ID, it forms the primary key and the unique business-key candidate (IEO_SVR_PROTOCOL_MAP_U1), so the pair must be unique.
• PORT — The port number on which the component communicates using the mapped wire protocol.
• EXTRA — A supplementary attribute holding additional protocol- or component-specific configuration data.
• SECURITY_GROUP_ID — The security group that owns the row, with a foreign key reference to FND_SECURITY_GROUPS; this supports multi-tenant or multi-org style data partitioning within EBS.
• OBJECT_VERSION_NUMBER — Used for optimistic concurrency control when rows are updated through the application layer.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard EBS audit columns recording who created and last modified the row and when.

Note that COMP_ID and WIRE_PROTOCOL together constitute the composite surrogate/business key, while SECURITY_GROUP_ID links the row to the broader EBS security framework. There is no separate single-column surrogate key; the primary key is natural and composite.

Common Use Cases and Queries

Administrators and integrators query this table when diagnosing Interaction Center connectivity issues, verifying which protocol is bound to a given component, or auditing port assignments. A typical lookup resolves a component's protocol and port:

• SELECT p.COMP_ID, p.WIRE_PROTOCOL, p.PORT, p.EXTRA FROM IEO.IEO_SVR_PROTOCOL_MAP p WHERE p.COMP_ID = :component_id;
• Joining to the component definition: SELECT c.*, p.WIRE_PROTOCOL, p.PORT FROM IEO.IEO_SVR_COMPS c, IEO.IEO_SVR_PROTOCOL_MAP p WHERE c.COMP_ID = p.COMP_ID;
• Security-scoped reporting: SELECT p.COMP_ID, p.WIRE_PROTOCOL FROM IEO.IEO_SVR_PROTOCOL_MAP p WHERE p.SECURITY_GROUP_ID = :security_group_id;

Reporting use cases include producing a registry of components and their protocols, validating that no duplicate COMP_ID/WIRE_PROTOCOL pairs exist, and reconciling port usage across the Interaction Center topology.

Related Objects

The most significant related objects are:

• IEO_SVR_COMPS — The parent component table; joined on IEO_SVR_PROTOCOL_MAP.COMP_ID = IEO_SVR_COMPS.COMP_ID. This is the primary FK dependency.
• FND_SECURITY_GROUPS — Referenced by SECURITY_GROUP_ID for security grouping.
• IEO_SVR_PROTOCOL_MAP_PK — The composite primary key constraint/index on (COMP_ID, WIRE_PROTOCOL).
• IEO_SVR_PROTOCOL_MAP_U1 — The unique business-key index on (COMP_ID, WIRE_PROTOCOL).
• Other IEO Interaction Center configuration tables that reference IEO_SVR_COMPS indirectly, and EBS audit/security objects that rely on the standard audit columns and SECURITY_GROUP_ID.