Search Results ieo_svr_protocol_map_u1

Overview

The IEO.IEO_SVR_PROTOCOL_MAP table is a repository configuration object within the Oracle E-Business Suite Internet Exchange (iStore/Exchange) subsystem. It stores the mapping between server components and the wire protocols those components support. In practical terms, it acts as a registry that identifies which communication protocols a given component can service, together with optional port assignments and protocol-specific configuration options. The table resides in the APPS_TS_TX_DATA tablespace and is owned by the IEO schema, which is the schema associated with Oracle's Internet Exchange/Commerce server infrastructure.

The table is documented as VALID in Oracle EBS 12.1.1 and 12.2.2. Its FK structure—a parent reference to IEO_SVR_COMPS and a reference to FND_SECURITY_GROUPS—is consistent with a component-level attribute registry. From a heuristic Data Vault modeling perspective, the relationship data suggests this object is satellite-leaning: it holds descriptive and optional attributes (port, extra configuration) that qualify the component relationship rather than representing a pure hub or transactional link.

Key Information Stored

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

• COMP_ID — Foreign key to IEO_SVR_COMPS, identifying the component that owns the protocol mapping.
• WIRE_PROTOCOL — The protocol identifier (up to 32 characters) supported by the component, such as HTTP or HTTPS-style wire protocol values.
• PORT — Optional numeric port on which the protocol is registered or exposed.
• EXTRA — Optional VARCHAR2(1996) column that holds additional protocol configuration or option data for the mapping.
• SECURITY_GROUP_ID — Foreign key to FND_SECURITY_GROUPS, supporting hosted and multi-tenant deployments.
• OBJECT_VERSION_NUMBER — Standard column used by HTML-based Oracle utilities for optimistic concurrency control.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard WHO audit columns tracking creation and modification.

The composite primary key is IEO_SVR_PROTOCOL_MAP_PK, defined on (COMP_ID, WIRE_PROTOCOL). The unique index IEO_SVR_PROTOCOL_MAP_U1 is documented on the same column pair (COMP_ID, WIRE_PROTOCOL) in the APPS_TS_TX_IDX tablespace, making it the primary business-key candidate. In this design there is no standalone surrogate key column; the composite pair serves both as the primary key and as the natural business key candidate.

Common Use Cases and Queries

Typical usage includes validating which protocols a component supports, checking port assignments, auditing protocol registrations, and reporting on component-to-protocol mappings in hosted environments. Because the table is small and configuration-oriented, queries are generally simple joins and lookups rather than heavy aggregate reporting.

• List all protocols for a given component: SELECT WIRE_PROTOCOL, PORT, EXTRA FROM IEO.IEO_SVR_PROTOCOL_MAP WHERE COMP_ID = :comp_id;
• Join to component definitions to resolve names: SELECT m.COMP_ID, c.COMP_NAME, m.WIRE_PROTOCOL, m.PORT FROM IEO.IEO_SVR_PROTOCOL_MAP m, IEO.IEO_SVR_COMPS c WHERE m.COMP_ID = c.COMP_ID;
• Filter by security group for hosted tenancy reporting: SELECT * FROM IEO.IEO_SVR_PROTOCOL_MAP WHERE SECURITY_GROUP_ID = :sg_id;
• Search for a specific protocol across all components: SELECT COMP_ID, PORT FROM IEO.IEO_SVR_PROTOCOL_MAP WHERE WIRE_PROTOCOL = :protocol;

Because the unique index is on (COMP_ID, WIRE_PROTOCOL), lookups on that pair are indexed and efficient. Reporting on PORT or EXTRA generally results in full scans, which is acceptable given expected table size.

Related Objects

The dependency metadata identifies two foreign-key relationships and one dependent reference:

• IEO.IEO_SVR_COMPS — Referenced by IEO_SVR_PROTOCOL_MAP.COMP_ID. This is the parent table defining server components and the most important join target.
• FND_SECURITY_GROUPS — Referenced by SECURITY_GROUP_ID, used for hosted environment partitioning.
• APPS.IEO_SVR_PROTOCOL_MAP — The APPS synonym or view that references the base IEO table and is the object most commonly used from EBS application SQL and forms.

In practice, understanding these relationships—particularly the join to IEO_SVR_COMPS—is essential for interpreting protocol mappings in the context of EBS server configuration and troubleshooting communications between EBS components.