Search Results cct_interactionkey_u2

Overview

Table CCT.CCT_INTERACTION_KEYS is an Oracle E-Business Suite seeded reference table owned by the CCT (Interaction Center / Telephony) schema. It stores the predefined interaction key/value pairs consumed by the OA Preferences Administration screen within Oracle Advanced Outbound and the Interaction Center framework. The table resides in the APPS_TS_SEED tablespace, confirming its role as a seed data container rather than a transactional store. ETRM reports its status as VALID, with the FND design data reference resolving to CCT.CCT_INTERACTION_KEYS in both 12.1.1 and 12.2.2 environments.

The heuristic Data Vault classification for this object is hub-leaning. This classification is a modeling suggestion: the table's stable business identity, its unique business-key index, and the relatively narrow set of descriptive attributes align more closely with a hub construct than with a transaction-bearing satellite, though the descriptive and flexfield columns could be normalized into a satellite in a formal Data Vault representation.

Key Information Stored

The table is anchored by the surrogate primary key INTERACTION_KEY_ID, defined through the primary key constraint CCT_INTERACTION_KEYS_PK and enforced by the unique index CCT_INTERACTIONKEYID_U1. This is the column targeted by the search term the user entered. A second unique index, CCT_INTERACTIONKEY_U2, imposes a business-key constraint on INTERACTION_KEY, meaning each interaction key name must be unique within the table.

• INTERACTION_KEY_ID — numeric surrogate identifier; the primary key and the object of unique index CCT_INTERACTIONKEYID_U1.
• INTERACTION_KEY — user-defined interaction key name, 32 characters, enforced unique by CCT_INTERACTIONKEY_U2.
• DESCRIPTION — user-facing description of the key/value pair, 256 characters.
• DATA_TYPE — documented as not used in this release.
• FLAG — reserved for future expansion.
• CONTEXT — descriptive flexfield structure defining column, enabling key flexfield context assignment.
• ATTRIBUTE1 through ATTRIBUTE15 — descriptive flexfield segment columns, each 150 characters.
• PRIORITY, IVR_MAP_ENABLED, ROUTING_ENABLED, SOFTPHONE_ENABLED — channel and routing configuration flags that govern how the interaction key behaves across IVR, routing, and softphone channels.
• SECURITY_GROUP_ID — foreign key to FND_SECURITY_GROUPS, partitioning the interaction keys by security group.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, CREATED_BY, CREATION_DATE — standard WHO audit columns.

The column set totals 31 documented attributes, reflecting the combination of business identifiers, flexfield extension segments, channel flags, and audit metadata.

Common Use Cases and Queries

The most frequent operational requirement is confirming uniqueness and resolving a key name to its surrogate ID before inserting into a dependent table such as CCT_IVR_MAPS. A representative query follows:

• SELECT interaction_key_id, interaction_key, description FROM cct.cct_interaction_keys WHERE interaction_key = :key_name;
• SELECT k.interaction_key, k.description, m.ivr_map_id FROM cct.cct_interaction_keys k, cct.cct_ivr_maps m WHERE k.interaction_key_id = m.interaction_key_id;
• Reporting on channel enablement: filtering where IVR_MAP_ENABLED = 'Y' or ROUTING_ENABLED = 'Y' to audit which interaction keys participate in each channel.
• Migration and setup validation, verifying that the CCT_INTERACTIONKEY_U2 business key holds no duplicates before data movement between environments.

Related Objects

The documented foreign key relationships establish the table's two immediate dependencies:

• CCT.CCT_IVR_MAPS — references CCT_INTERACTION_KEYS through the INTERACTION_KEY_ID column, linking interaction keys to IVR map definitions.
• FND_SECURITY_GROUPS — referenced by the SECURITY_GROUP_ID column of CCT_INTERACTION_KEYS, binding each key to a security group.

Because the table is consumed by the OA Preferences Administration screen, the OA Preferences forms and related CCT setup APIs that maintain preference and interaction configuration should be treated as dependent components. Any change to the INTERACTION_KEY business key or the channel enablement flags propagates into IVR map resolution and preference evaluation logic, so modifications are best performed through the supported administration UI rather than by direct DML.