Search Results cct_telesets_pk




Overview

CCT_TELESETS is a Telephony Manager (CCT) configuration table in Oracle E-Business Suite 12.1.1 and 12.2.2. It defines the hardware characteristics of a teleset — the physical or logical telephone device registered with the Telephony Manager infrastructure. Each row captures a discrete teleset, its identity, its assigned hardware number, and the type definition it conforms to. The table resides in the CCT schema and is classified as VALID in the ETRM repository.

Under a heuristic Data Vault classification derived from its foreign-key topology, CCT_TELESETS is satellite-leaning. It holds descriptive attributes about teleset instances rather than acting as a pure junction between two hubs. In practice it behaves as a dependent child of the teleset type reference and a parent to line assignments, so modeling it as a satellite keyed to a teleset hub is the suggested pattern.

Key Information Stored

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

The surrogate key TELESET_ID is the enforcement point; TELESET_NAME and TELESET_HARDWARE_NUMBER function as business-key candidates but are not formally declared unique in the documented metadata.

Common Use Cases and Queries

Typical use cases include teleset inventory reporting, middleware-to-device mapping, and resolution of line assignments to physical hardware.

  • List all active telesets with their type and middleware:
    SELECT t.teleset_id, t.teleset_name, t.teleset_hardware_number, ty.teleset_type_id, m.middleware_id FROM cct_telesets t JOIN cct_teleset_types ty ON ty.teleset_type_id = t.teleset_type_id LEFT JOIN cct_middlewares m ON m.middleware_id = t.middleware_id WHERE t.f_deletedflag = 'N';
  • Find telesets not yet assigned to any line:
    SELECT t.* FROM cct_telesets t WHERE NOT EXISTS (SELECT 1 FROM cct_lines l WHERE l.teleset_id = t.teleset_id) AND t.f_deletedflag = 'N';
  • Inventory by hardware number for reconciliation against switch configuration exports.
  • Security-scoped queries filtering on SECURITY_GROUP_ID for multi-org deployments.

Because CCT_LINES carries a foreign key to TELESET_ID, joining the two tables yields the full line-to-device mapping needed for telephony reporting.

Related Objects

  • CCT_TELESET_TYPES — referenced via CCT_TELESETS.TELESET_TYPE_ID; supplies the teleset type definition.
  • CCT_MIDDLEWARES — referenced via CCT_TELESETS.MIDDLEWARE_ID; identifies the serving middleware.
  • FND_SECURITY_GROUPS — referenced via CCT_TELESETS.SECURITY_GROUP_ID; governs row-level security.
  • CCT_LINES — child table; CCT_LINES.TELESET_ID references CCT_TELESETS.TELESET_ID, linking lines to their teleset.
  • CCT_TELESETS_PK / CCT_TELESET_ID_U1 — primary key constraint and unique index on TELESET_ID.

These relationships define CCT_TELESETS as the central hardware-definition reference within the Telephony Manager schema.

  • Table: CCT_TELESETS 12.1.1

    owner:CCT,  object_type:TABLE,  fnd_design_data:CCT.CCT_TELESETS,  object_name:CCT_TELESETS,  status:VALID,  product: CCT - Telephony Managerdescription: This table defines a hardware teleset characteristics. ,  implementation_dba_data: CCT.CCT_TELESETS

  • Table: CCT_TELESETS 12.2.2

    owner:CCT,  object_type:TABLE,  fnd_design_data:CCT.CCT_TELESETS,  object_name:CCT_TELESETS,  status:VALID,  product: CCT - Telephony Managerdescription: This table defines a hardware teleset characteristics. ,  implementation_dba_data: CCT.CCT_TELESETS

  • eTRM - CCT Tables and Views 12.1.1

    description: This table is used by the Routing Server Workflow definitions to keep track of the Agents returned by the nodes , 

  • eTRM - CCT Tables and Views 12.2.2

    description: This table is used by the Routing Server Workflow definitions to keep track of the Agents returned by the nodes , 

  • eTRM - CCT Tables and Views 12.2.2

    description: This table is used by the Routing Server Workflow definitions to keep track of the Agents returned by the nodes , 

  • eTRM - CCT Tables and Views 12.1.1

    description: This table is used by the Routing Server Workflow definitions to keep track of the Agents returned by the nodes ,