Search Results cct_cmi_uk1

Overview

The CCT_MEDIA_ITEMS table is a core data object within the Oracle E-Business Suite (EBS) Telephony Manager module (CCT). It serves as the central repository for managing media items within the call center infrastructure. In the context of Computer Telephony Integration (CTI), a media item represents a single, addressable unit of inbound or outbound communication, such as a telephone call, email, or chat session, that is queued for processing by an agent. This table is fundamental to the routing, queuing, and tracking of customer interactions across the contact center, enabling the EBS system to manage high volumes of multi-channel communications efficiently and in alignment with business workflows.

Key Information Stored

The table's structure is designed to uniquely identify and manage the lifecycle of each media item. While the full column list is not detailed in the provided metadata, the documented primary and unique keys reveal its critical components. The primary key, MEDIA_ITEM_ID, is a unique system-generated identifier for each interaction. The unique key, CCT_CMI_UK1, enforces uniqueness based on the combination of MCM_SVR_ID (likely identifying the specific media control manager or server instance handling the item) and QUEUE_SEQ_NUM (the sequence number of the item within a specific queue). This combination ensures proper ordering and server assignment for queued interactions. Other typical columns in such a table would store data such as media type, creation timestamp, current status, associated customer or party ID, and the target agent or skill queue.

Common Use Cases and Queries

This table is primarily accessed by the Telephony Manager's internal engine for real-time operations. Common functional use cases include querying for the next available media item for an agent, monitoring queue lengths and wait times, and auditing interaction history. A typical reporting query might involve joining with agent tables to analyze agent productivity or with customer tables to review interaction history. A sample SQL pattern to find items in queue for a specific server would be:

• SELECT MEDIA_ITEM_ID, QUEUE_SEQ_NUM FROM CCT_MEDIA_ITEMS WHERE MCM_SVR_ID = :server_id AND status = 'QUEUED' ORDER BY QUEUE_SEQ_NUM;

Performance tuning and purging of historical data are also key administrative tasks associated with this high-transaction volume table.

Related Objects

Based on the provided relationship data, the CCT_MEDIA_ITEMS table's primary key, MEDIA_ITEM_ID, is referenced by the constraint CCT_CMI_PK. This indicates it is the parent table in foreign key relationships. While the specific child tables are not listed in the excerpt, in the CCT module, it is highly probable that this key is referenced by tables storing media event history (e.g., CCT_MEDIA_EVENTS), agent disposition data, or call detail records. The unique key on MCM_SVR_ID and QUEUE_SEQ_NUM suggests a relationship with a server configuration or queue definition table. Direct dependencies would be found in CCT package bodies (e.g., CCT_INTERACTION_PUB) that contain APIs for media item creation, routing, and retrieval.