Search Results cct_cpa_pk

Overview

CCT_CLASSIPROC_PARAMS is a Telephony Manager (CCT) application table in Oracle E-Business Suite 12.1.1 and 12.2.2, owned by the CCT schema. Its documented description is "Classification Procedure Paramters table," indicating that it stores the individual parameter rows that drive classification procedures executed during telephony and interaction-processing flows. Each row supplies a KEY/VALUE pair, a CONTEXT, and an OPERATION that a classification rule uses when evaluating or assigning a CLASSIFICATION_ID.

The table is physical and valid in the ETRM reference for both releases. The documented heuristic Data Vault classification is standalone, which suggests modeling this object as an independent satellite-like structure rather than a multi-parent link. The heuristic is a modeling suggestion only; because the table carries both CLASSIFICATION_RULE_ID and SECURITY_GROUP_ID foreign keys, it also behaves as a subordinate detail table to classification rules within the operational entity model. Its 28 documented columns include the standard EBS audit and multi-tenant security columns (LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, CREATION_DATE, CREATED_BY, SECURITY_GROUP_ID).

Key Information Stored

The table's surrogate primary key is CCT_CPA_PK, defined on CLASSIPROC_PARAM_ID, which uniquely identifies each parameter row. The most significant data-bearing columns are:

• CLASSIPROC_PARAM_ID — surrogate primary key (CCT_CPA_PK); the unique row identifier.
• CLASSIFICATION_RULE_ID — foreign key to CCT_CLASSIFICATION_RULES; the rule to which this parameter belongs and the primary business join key.
• CLASSIFICATION_ID — the classification assigned or evaluated in the context of this parameter.
• CONTEXT — the evaluation context under which the parameter applies.
• KEY — the parameter or attribute name being supplied.
• VALUE — the parameter value matched against, or passed to, the classification procedure.
• OPERATION — the comparison or operation applied to KEY and VALUE during rule evaluation.
• SECURITY_GROUP_ID — foreign key to FND_SECURITY_GROUPS; enforces multi-org / multi-tenant data access partitioning.
• ATTRIBUTE1 through ATTRIBUTE15 — the DFF-style descriptive flexfield and extension columns, documented as present (ATTRIBUTE1–ATTRIBUTE15) for customer-specific parameter metadata.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, CREATION_DATE, CREATED_BY — the standard EBS audit who/when columns.

Aside from the primary key, the documented metadata does not list additional unique indexes, so CLASSIFICATION_RULE_ID with CONTEXT and KEY are the practical business-key candidates rather than enforced unique constraints.

Common Use Cases and Queries

Typical uses include auditing classification rule configuration, tracing why an interaction received a given CLASSIFICATION_ID, cloning rule parameters between environments, and reporting on rule coverage or orphaned parameters.

Retrieve all parameters for a rule:

SELECT cpp.classiproc_param_id, cpp.classification_rule_id,
       cpp.context, cpp.key, cpp.value, cpp.operation
FROM   cct.cct_classiproc_params cpp
WHERE  cpp.classification_rule_id = :rule_id
ORDER  BY cpp.context, cpp.key;

Join parameters to their parent rules:

SELECT r.rule_name, p.context, p.key, p.value, p.operation
FROM   cct.cct_classiproc_params p,
       cct.cct_classification_rules r
WHERE  p.classification_rule_id = r.classification_rule_id
AND    p.security_group_id   = :security_group_id;

Detect parameters without a matching rule (orphan check) using a NOT EXISTS against CCT_CLASSIFICATION_RULES, and filter all reporting queries by SECURITY_GROUP_ID to respect multi-tenant partitioning.

Related Objects

• CCT_CLASSIFICATION_RULES — parent rule table; joined via CLASSIFICATION_RULE_ID.
• FND_SECURITY_GROUPS — security partitioning; joined via SECURITY_GROUP_ID.
• FND_FLEX_VALUES / FND_DESCR_FLEX_COL_USAGE — contextual definition for ATTRIBUTE1–15, where flexfield usage is configured.
• CCT_CLASSIFICATION (logical sibling) — referenced through CLASSIFICATION_ID.
• FND_USER — resolves CREATED_BY and LAST_UPDATED_BY audit columns to user names.
• Telephony Manager concurrent programs — classification procedures that read these parameters at runtime.

Queries against CCT_CLASSIPROC_PARAMS should always be schema-qualified (CCT.) and filtered by SECURITY_GROUP_ID where multi-org isolation is required.