Search Results ieo_svr_groups




Overview
Explore in AI Chat

Overview

IEO_SVR_GROUPS is a table owned by the IEO schema (Interaction Center Technology) that stores the definition of server groups used by Oracle E-Business Suite Interaction Center components. Server groups allow Interaction Center administrators to logically cluster application, telephony, and media servers so that routing, load balancing, and failover behaviour can be managed at a group level rather than individually per server. The table is marked VALID in the ETRM dictionary for EBS 12.1.1 and 12.2.2 and carries 13 documented columns.

Under the heuristic Data Vault classification supplied in the metadata, IEO_SVR_GROUPS is hub-leaning. In Data Vault terms it behaves as a hub: it holds a single, stable business object identifier (a server group), a surrogate primary key, and descriptive attributes, while associations to physical servers are recorded in a separate link-like table (IEO_SVR_SERVERS). This classification should be treated as a modelling suggestion rather than a documented EBS design decision.

Key Information Stored

The primary key is enforced through the constraint IEO_SVR_GROUPS_PK on the column SERVER_GROUP_ID, which is a system-generated surrogate identifier. Business-key uniqueness is separately enforced by unique indexes documented as IEO_SVR_GROUPS_UK1 (and IEO_SVR_GROUPS_U01/U02 in the 12.2.2 physical schema) on GROUP_NAME, meaning the server group name is the human-recognisable natural key.

  • SERVER_GROUP_ID — surrogate primary key and the value referenced by downstream tables.
  • GROUP_NAME — the unique business name of the server group.
  • GROUP_GROUP_ID — self-referencing foreign key that allows server groups to be nested within a parent group.

The table also carries standard EBS WHO (Workflow/Oracle) audit columns — CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, and LAST_UPDATE_LOGIN — plus OBJECT_VERSION_NUMBER for optimistic locking. Descriptive and control columns include LOCATION, DESCRIPTION, SECURITY_GROUP_ID (foreign key to FND_SECURITY_GROUPS), and VISIBLE, which governs whether the group is exposed for selection.

Common Use Cases and Queries

Administrators and support analysts query this table to confirm group membership, hierarchy, and visibility when diagnosing Interaction Center routing or telephony failures. A typical listing joins the group header to its member servers:

  • Lookup by name: SELECT * FROM ieo.ieo_svr_groups WHERE group_name = :name;
  • Resolve membership: SELECT g.group_name, s.* FROM ieo.ieo_svr_groups g, ieo.ieo_svr_servers s WHERE s.member_svr_group_id = g.server_group_id;
  • Hierarchy walk: self-join on GROUP_GROUP_ID to expand nested groups.
  • Security-scoped reporting: join to FND_SECURITY_GROUPS on SECURITY_GROUP_ID for responsibility-based visibility.
  • Change auditing: order by LAST_UPDATE_DATE to identify recently modified group definitions.

Related Objects

The most significant related objects, with the actual join columns from the documented constraints, are:

  • IEO_SVR_GROUPS (self) — GROUP_GROUP_ID references SERVER_GROUP_ID, expressing parent/child grouping.
  • IEO_SVR_SERVERS — MEMBER_SVR_GROUP_ID references IEO_SVR_GROUPS, linking physical servers to their group; USING_SVR_GROUP_ID also references IEO_SVR_GROUPS, identifying the group a server actively consumes.
  • FND_SECURITY_GROUPS — SECURITY_GROUP_ID references the security group, controlling data access.

These relationships confirm IEO_SVR_GROUPS as the central hub of the Interaction Center server topology, with IEO_SVR_SERVERS acting as the surrounding association table.