Search Results cct_interaction_keys




Overview
Explore in AI Chat

Overview

CCT_INTERACTION_KEYS is a Telephony Manager (CCT) configuration table in Oracle E-Business Suite, owned by the CCT schema. It stores the predefined interaction keys that populate the OA Preferences (OA Prefs) Administration screen, which is the Oracle Applications framework used to present user-level preference values to agents and administrators. Each row defines a discrete interaction attribute — such as a data type, an enabling flag, and its associated display priority — that the Telephony Manager runtime and preference framework consume when rendering or validating agent interaction handling.

From a Data Vault modeling perspective (based on the foreign key structure mined from the ETRM metadata), this table is classified as hub-leaning. It carries a single-column surrogate primary key and holds descriptive, relatively stable reference data, which suggests it functions as a reference hub with satellite-style descriptive attributes rather than a transactional link or an activity satellite. Rows are maintained as setup data, not as high-volume transactional records.

Key Information Stored

The table contains 31 documented columns. The most functionally significant are:

  • INTERACTION_KEY_ID — The surrogate primary key, enforced by the unique index CCT_INTERACTIONKEYID_U1 and the constraint CCT_INTERACTION_KEYS_PK. It uniquely identifies each interaction key and is the column referenced by dependent tables.
  • INTERACTION_KEY — The business-key candidate, protected by the unique index CCT_INTERACTIONKEY_U2. This is the user-visible identifier of the interaction key as presented on the OA Prefs Admin screen.
  • DATA_TYPE — Defines the data type (for example, character, number, or date) expected for the preference value associated with the interaction key.
  • FLAG — A status or applicability indicator controlling whether the key is active or selectable.
  • DESCRIPTION — The descriptive text displayed to administrators alongside the interaction key.
  • CONTEXT — The descriptive flexfield context column, enabling context-sensitive attribute extensions.
  • ATTRIBUTE1 through ATTRIBUTE15 — The standard Oracle descriptive flexfield attribute segments used to store additional, customer-defined metadata for the interaction key.
  • PRIORITY — Controls ordering or precedence when multiple interaction keys are applicable.
  • IVR_MAP_ENABLED, ROUTING_ENABLED, SOFTPHONE_ENABLED — Boolean-style enablement flags that determine whether the interaction key participates in IVR mapping, routing, and softphone integration respectively.
  • SECURITY_GROUP_ID — The multi-tenant / security group reference, which is a foreign key to FND_SECURITY_GROUPS, supporting data isolation by security group.
  • LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, CREATED_BY, CREATION_DATE — Standard Oracle WHO columns capturing audit and ownership history.

Common Use Cases and Queries

The primary use cases involve inspecting or reporting on the interaction keys configured for the OA Prefs Admin screen and determining which integration channels are enabled for each key.

  • Listing active interaction keys with their data types and enablement flags:
    SELECT interaction_key, data_type, priority, ivr_map_enabled, routing_enabled, softphone_enabled FROM cct.cct_interaction_keys WHERE flag = 'Y' ORDER BY priority;
  • Determining which interaction keys are wired into IVR mapping by joining to the dependent mapping table:
    SELECT k.interaction_key, m.* FROM cct.cct_interaction_keys k, cct.cct_ivr_maps m WHERE k.interaction_key_id = m.interaction_key_id;
  • Reporting on security-group-scoped configuration by joining SECURITY_GROUP_ID to FND_SECURITY_GROUPS.
  • Reviewing descriptive flexfield usage by querying CONTEXT and ATTRIBUTE1 through ATTRIBUTE15 for customer-specific extensions.

Related Objects

  • CCT_IVR_MAPS — The principal dependent table; its INTERACTION_KEY_ID foreign key column references CCT_INTERACTION_KEYS, linking each IVR mapping to its interaction key.
  • FND_SECURITY_GROUPS — Referenced by CCT_INTERACTION_KEYS.SECURITY_GROUP_ID, providing the security group definition for multi-tenant isolation.
  • CCT_INTERACTION_KEYS_PK — The primary key constraint on INTERACTION_KEY_ID.
  • CCT_INTERACTIONKEYID_U1 and CCT_INTERACTIONKEY_U2 — The unique indexes that enforce uniqueness of the surrogate key and the business key respectively.
  • The OA Preferences (OA Prefs) Administration framework screens — the consuming application layer that reads this table to render and manage interaction key preferences.