Search Results cct_ccr_pk

Overview

The CCT_CLASSIFICATION_RULES table is a core configuration object within the CCT – Telephony Manager module of Oracle E-Business Suite (documented across 12.1.1 and 12.2.2). It resides in the CCT schema and stores the rule definitions that determine how telephony interaction data is classified. Classification is a foundational step in Telephony Manager processing: incoming or outbound call records are matched against these rules and assigned a corresponding classification, which in turn drives routing, scripting, agent screen-pop behavior, and downstream reporting.

From a Data Vault modeling perspective, the FK topology suggests this is a satellite-leaning structure. Its primary key (CLASSIFICATION_RULE_ID) is a surrogate key, and its most significant foreign key points to CCT_CLASSIFICATIONS, indicating that each rule row describes attributes and behavior belonging to a parent classification. This is characteristic of a descriptive satellite rather than an independent hub or an associative link.

Key Information Stored

The table contains 29 documented columns. The most significant are summarized below.

• CLASSIFICATION_RULE_ID — Surrogate primary key (constraint CCT_CCR_PK) that uniquely identifies each classification rule.
• CLASSIFICATION_ID — Foreign key to CCT_CLASSIFICATIONS; identifies the parent classification to which the rule belongs.
• KEY — The rule key or attribute identifier used for matching incoming telephony data against the classification logic.
• VALUE — The comparison value tested against the KEY during rule evaluation.
• OPERATION — The operator applied when evaluating the rule (for example, equality or a range/match condition).
• CONTEXT — Contextual scoping that qualifies when or where the rule applies.
• SECURITY_GROUP_ID — Foreign key to FND_SECURITY_GROUPS, enforcing multi-org/security-group data segregation.
• ATTRIBUTE1 … ATTRIBUTE15 — The standard Oracle EBS DFF/descriptive flexfield columns, available for customer-specific rule extensions.
• OBJECT_VERSION_NUMBER — Optimistic locking column used by the framework to detect concurrent updates.
• F_DELETEDFLAG — Soft-delete indicator; rows are logically retained rather than physically removed.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — The standard WHO audit columns.

While CLASSIFICATION_RULE_ID is the documented primary key, the practical business-key candidates are the combination of CLASSIFICATION_ID, KEY, VALUE, and OPERATION, since together these uniquely describe a rule definition for a given classification.

Common Use Cases and Queries

Typical scenarios include reviewing which rules belong to a classification, auditing rule configurations prior to an upgrade, and building reporting extracts of routing logic for analytics.

Querying all rules for a specific classification:

SELECT cr.CLASSIFICATION_RULE_ID, cr.KEY, cr.VALUE, cr.OPERATION FROM CCT.CCT_CLASSIFICATION_RULES cr WHERE cr.CLASSIFICATION_ID = :classification_id AND cr.F_DELETEDFLAG = 'N';

Joining to the parent classification to label rules in a report:

SELECT c.CLASSIFICATION_ID, c.NAME, cr.KEY, cr.VALUE, cr.OPERATION FROM CCT.CCT_CLASSIFICATIONS c, CCT.CCT_CLASSIFICATION_RULES cr WHERE c.CLASSIFICATION_ID = cr.CLASSIFICATION_ID;

Because of the SECURITY_GROUP_ID column, queries executed within a multi-org context should include the appropriate security-group predicate to avoid exposing rows belonging to other groups.

Related Objects

The following objects are the most significant relative to this table:

• CCT_CLASSIFICATIONS — Parent table; joined via CCT_CLASSIFICATION_RULES.CLASSIFICATION_ID = CCT_CLASSIFICATIONS.CLASSIFICATION_ID. Defines the classification to which each rule belongs.
• CCT_CLASSIPROC_PARAMS — References this table via CLASSIFICATION_RULE_ID; holds classification process parameters that consume these rules at runtime.
• FND_SECURITY_GROUPS — Referenced via SECURITY_GROUP_ID; governs data-level security segregation.
• CCT Telephony Manager concurrent programs and classification APIs that read rule definitions at call-processing time.

Together these objects form the classification configuration layer that Telephony Manager relies upon to interpret and route telephony interactions within Oracle EBS.