Search Results cct_classifications




Overview
Explore in AI Chat

Overview

CCT_CLASSIFICATIONS is a table owned by the CCT schema within the Oracle E-Business Suite Telephony Manager (CCT) product module. It functions as the classifications table, storing the definitions used to categorize and route inbound and outbound telephony interactions handled by the Telephony Manager infrastructure. In releases 12.1.1 and 12.2.2 the object retains the same ownership and primary key, with the documented physical schema in 12.2.2 exposing 37 columns. The table is central to how the telephony server interprets an incoming call, assigns it to a classification, and applies associated rules for routing, timeout behavior, and database or context resolution.

Based on the foreign key topology supplied in the metadata, a data vault modeling heuristic classifies this object as hub-leaning. It anchors a durable identity (CLASSIFICATION_ID) around which dependent rule and configuration satellites or links are organized. This classification is a modeling suggestion rather than a physical implementation property; the actual EBS table is a conventional normalized relational structure.

Key Information Stored

The surrogate primary key is CLASSIFICATION_ID, enforced through the constraint CCT_CCL_PK. Business-meaningful attributes identify and describe each classification, while numerous technical and audit columns support runtime and integration behavior.

  • CLASSIFICATION_ID — surrogate primary key uniquely identifying each classification record.
  • CLASSIFICATION and CLASSIFICATION_VALUE_ID — the classification name/token and its associated value identifier used during call evaluation.
  • TYPE — indicates the classification category or processing type.
  • DBURL and DB_DRIVER — the database connection URL and driver used by telephony components when the classification requires database access.
  • CONTEXT — contextual binding applied during rule evaluation.
  • TIME_OUT — the maximum wait or processing interval associated with the classification.
  • ROUTE_ID — the route to which qualifying interactions are directed.
  • LOOKUP_TYPE — the lookup type used to resolve classification values.
  • CUSTOM_RULE, RULE_CHAINING, and PRIORITY — govern whether a custom rule is applied, whether rule chaining is permitted, and the precedence order among classifications.
  • ISENABLED and F_DELETEDFLAG — soft enable/disable and logical delete indicators.
  • ATTRIBUTE1 through ATTRIBUTE15 — the standard EBS DFF (descriptive flexfield) columns for extensibility.
  • SECURITY_GROUP_ID — foreign key to FND_SECURITY_GROUPS, providing multi-tenant / data segregation.
  • OBJECT_VERSION_NUMBER and the audit columns CREATED_BY, CREATION_DATE, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — support optimistic locking and standard EBS auditing.

Common Use Cases and Queries

Typical usage centers on reporting and troubleshooting telephony classification configuration. A common pattern retrieves all enabled classifications ordered by priority:

SELECT CLASSIFICATION_ID, CLASSIFICATION, TYPE, PRIORITY,
       ROUTE_ID, ISENABLED
FROM   CCT.CCT_CLASSIFICATIONS
WHERE  ISENABLED = 'Y'
  AND  NVL(F_DELETEDFLAG, 'N') = 'N'
ORDER BY PRIORITY;

Administrators and analysts frequently join classifications to their rules to understand routing outcomes, and filter by SECURITY_GROUP_ID in multi-org or multi-tenant deployments. Flexfield attributes (ATTRIBUTE1–15) are commonly queried where organizations have configured descriptive flexfields to carry site-specific metadata. Migration and audit scripts compare OBJECT_VERSION_NUMBER and LAST_UPDATE_DATE to detect configuration drift between environments.

Related Objects

The most significant dependent object is CCT_CLASSIFICATION_RULES, which references this table through the column CCT_CLASSIFICATION_RULES.CLASSIFICATION_ID, linking each rule to its parent classification. This table itself references FND_SECURITY_GROUPS via SECURITY_GROUP_ID, tying records to EBS security groups. Because classification behavior drives routing and call handling, related Telephony Manager configuration objects and the underlying lookup definitions referenced by LOOKUP_TYPE are relevant. When building reports, CCT_CLASSIFICATIONS is best treated as the hub, joined outward to CCT_CLASSIFICATION_RULES and inward toward FND_SECURITY_GROUPS to present a complete configuration picture.