Search Results cct_lines




Overview
Explore in AI Chat

Overview

CCT_LINES is a Telephony Manager (CCT) table in the Oracle E-Business Suite database, owned by the CCT schema. It stores the configuration of individual telephone lines, tracking each line's extension and its classification as used by the Telephony Manager module. In functional terms, it is the master definition list for telephone lines registered with the EBS telephony integration: each row corresponds to one line, links that line to a physical telephony device (a teleset), and carries attributes such as its extension, purpose, and canonical phone number.

Structurally, the table holds 31 columns, has a primary key constraint CCT_LINES_PK on LINE_ID, and a unique index CCT_LINE_ID_U1, also on LINE_ID. It carries a foreign key reference to CCT_TELESETS via TELESET_ID, tying each line to its assigned teleset, and a reference to FND_SECURITY_GROUPS via SECURITY_GROUP_ID, which participates in Oracle's security-group access control pattern. Heuristically, the foreign key structure suggests a satellite-leaning classification in a Data Vault model: CCT_LINES extends the CCT_TELESETS parent with descriptive line-level attributes rather than operating as a standalone hub or link. This is a modeling suggestion derived from the FK topology, not a formal classification.

The table includes the standard EBS audit and concurrency columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN, OBJECT_VERSION_NUMBER) plus a F_DELETEDFLAG column, which indicates the table participates in a soft-delete pattern.

Key Information Stored

Although 31 columns exist, the business-relevant content is concentrated in a small set. The most important columns are:

  • LINE_ID — the surrogate primary key (CCT_LINES_PK, also enforced by unique index CCT_LINE_ID_U1). It is the join key to dependent objects.
  • LINE_NAME — the descriptive identifier for the line.
  • LINE_INDEX — an ordering or indexing attribute used to sequence lines.
  • LINE_PURPOSE — the classification of the line's intended use, which is central to the table's documented description ("extension/classification").
  • EXTENSION — the telephone extension assigned to the line.
  • CANONICAL_PHONE_NUMBER — the normalized phone number associated with the line, supporting consistent number formatting and matching.
  • TELESET_ID — foreign key to CCT_TELESETS, identifying the physical teleset assigned to the line.
  • SECURITY_GROUP_ID — foreign key to FND_SECURITY_GROUPS, controlling which security group can access the row.
  • F_DELETEDFLAG — soft-delete indicator; active reporting queries should filter on this column.
  • OBJECT_VERSION_NUMBER — optimistic locking column for concurrent updates through EBS forms or APIs.

The remaining columns are the standard audit fields and the 15 descriptive ATTRIBUTE (1–15) and CONTEXT flex columns, which hold customer- or implementation-specific values and should generally not be referenced directly without consulting the descriptive flexfield definition.

Common Use Cases and Queries

Typical usage centers on resolving which line or extension is associated with a teleset, validating line classifications for administrative reporting, and joining line data to teleset configuration.

A basic active-line listing:

  • SELECT LINE_ID, LINE_NAME, EXTENSION, LINE_PURPOSE FROM CCT.CCT_LINES WHERE NVL(F_DELETEDFLAG,'N') = 'N';

Joining lines to their assigned telesets:

  • SELECT l.LINE_NAME, l.EXTENSION, t.* FROM CCT.CCT_LINES l, CCT.CCT_TELESETS t WHERE l.TELESET_ID = t.TELESET_ID;

Filtering by classification or canonical number for contact-center or directory reporting:

  • SELECT LINE_NAME, CANONICAL_PHONE_NUMBER FROM CCT.CCT_LINES WHERE LINE_PURPOSE = :purpose;

Because the table is security-group protected, extracts used for cross-group reporting should join or filter through SECURITY_GROUP_ID consistently with the calling application's security profile, and should avoid returning rows outside the user's authorized groups.

Related Objects

The most significant related objects are:

  • CCT_TELESETS — parent object; joined on CCT_LINES.TELESET_ID = CCT_TELESETS.TELESET_ID. This is the only documented foreign key relationship.
  • FND_SECURITY_GROUPS — referenced through CCT_LINES.SECURITY_GROUP_ID, governing row-level access.
  • CCT_LINES_PK / CCT_LINE_ID_U1 — the primary key constraint and unique index on LINE_ID, which define the identity of each line and are used by any dependent child tables or APIs referencing LINE_ID.

Additional CCT module tables and views that consume line definitions (for example telephony event or agent-assignment objects) reference CCT_LINES through the LINE_ID primary key, so any integration or extract built on CCT_LINES should preserve LINE_ID as the stable join key and account for the F_DELETEDFLAG soft-delete semantics.