Search Results ieo_svr_comps




Overview
Explore in AI Chat

Overview

IEO_SVR_COMPS is a table in the IEO schema (Interaction Center Technology product family) within Oracle E-Business Suite 12.1.1 and 12.2.2. It stores server component definitions — the individual deployable components that make up an Interaction Center server instance (for example, telephony, media, or application service processes registered against a server). It is not a transactional or high-volume table; it is configuration/reference data that describes how an Interaction Center server is composed from defined component types.

From a dimensional modeling perspective, the mined FK structure classifies this table as satellite-leaning. In Data Vault terms this suggests IEO_SVR_COMPS behaves as a satellite attached to its hub parents, IEO_SVR_SERVERS and IEO_SVR_COMP_DEFS, rather than acting as an independent hub. It carries descriptive and versioning attributes (COMP_NAME, OBJECT_VERSION_NUMBER, SECURITY_GROUP_ID) that are subordinate to those parent entities.

Key Information Stored

The table contains 7 documented columns. The most important are:

  • COMP_ID — the surrogate primary key (IEO_SVR_COMPS_PK), uniquely identifying each server-component row. Also exposed as a unique index (IEO_SVR_COMPS_U1) and the business-key candidate in the documented schema.
  • SERVER_ID — foreign key to IEO_SVR_SERVERS, identifying the parent server. Part of the unique key IEO_SVR_COMPS_UK1.
  • COMP_DEF_ID — foreign key to IEO_SVR_COMP_DEFS, identifying the reusable component definition. Also part of IEO_SVR_COMPS_UK1.
  • COMP_NAME — the component's name, an alternate descriptive business-key candidate (documented in IEO_SVR_COMPS_UK1).
  • SECURITY_GROUP_ID — foreign key to FND_SECURITY_GROUPS, enforcing multi-org / data-security partitioning.
  • OBJECT_VERSION_NUMBER — the standard EBS optimistic-concurrency / row-versioning column.
  • OBJECT_REF — a reference pointer associated with the component object, indicating whether the component is backed by a stored object definition.

The unique key IEO_SVR_COMPS_UK1 (SERVER_ID, COMP_DEF_ID, COMP_NAME) confirms that within a given server, a component definition cannot be registered twice under the same name. A separate SYS_IL index on column 7 (the LOB/object column) supports the OBJECT_REF storage.

Common Use Cases and Queries

Typical uses include auditing server composition, validating that all required component types are present on a server, and reconciling component-to-protocol mappings.

  • List all components of a server: 
    SELECT c.COMP_ID, c.COMP_NAME, d.COMP_DEF_ID
FROM   IEO.IEO_SVR_COMPS c, IEO.IEO_SVR_COMP_DEFS d
WHERE  c.COMP_DEF_ID = d.COMP_DEF_ID
AND    c.SERVER_ID = :server_id;
  • Find components mapped to a protocol: 
    SELECT p.PROTOCOL_ID, c.COMP_NAME
FROM   IEO.IEO_SVR_PROTOCOL_MAP p, IEO.IEO_SVR_COMPS c
WHERE  p.COMP_ID = c.COMP_ID;
  • Identify servers missing a given component definition (comparison against IEO_SVR_COMP_DEFS).

Related Objects

  • IEO_SVR_SERVERS — parent; joined via IEO_SVR_COMPS.SERVER_ID = IEO_SVR_SERVERS.SERVER_ID.
  • IEO_SVR_COMP_DEFS — parent; joined via IEO_SVR_COMPS.COMP_DEF_ID = IEO_SVR_COMP_DEFS.COMP_DEF_ID.
  • IEO_SVR_PROTOCOL_MAP — child; references IEO_SVR_COMPS.COMP_ID.
  • JDR_COMPONENTS — references IEO_SVR_COMPS.COMP_ID.
  • FND_SECURITY_GROUPS — referenced via SECURITY_GROUP_ID for data security.