Search Results cct_cmv_pk




Overview
Explore in AI Chat

Overview

CCT_MIDDLEWARE_VALUES is a Telephony Manager (CCT) configuration table in the Oracle E-Business Suite, owned by the CCT schema. Its documented purpose is to hold the parameter values associated with each defined middleware identifier. In practical terms, it is the value store that complements the middleware registry and the middleware parameter catalogue: CCT_MIDDLEWARES defines which middleware instances exist, CCT_MIDDLEWARE_PARAMS defines which parameters those middleware instances may accept, and CCT_MIDDLEWARE_VALUES records the actual configured value supplied for a given middleware and parameter pair. The table is documented as a TABLE object with status VALID in both Oracle EBS 12.1.1 and 12.2.2, and the ETRM 12.2.2 physical schema lists 29 columns under the CCT owner.

Heuristic Data Vault classification mined from the foreign key structure suggests treating this object as a link. That classification is a modeling suggestion rather than a documented fact: the table resolves the association between a middleware instance and a parameter definition, which is characteristic of a link entity. The presence of descriptive payload columns (notably VALUE and CONTEXT) means a satellite treatment could also be layered on that link depending on the modeling objective.

Key Information Stored

The documented primary key is constraint CCT_CMV_PK on MIDDLEWARE_VALUE_ID. A unique index, CCT_MIDDLEWARE_VALUES_ID_U1, also covers MIDDLEWARE_VALUE_ID, reinforcing the surrogate key as the singular row identifier. The most significant columns are:

  • MIDDLEWARE_VALUE_ID — surrogate primary key for each configured value row.
  • MIDDLEWARE_ID — foreign key to CCT_MIDDLEWARES; identifies the middleware instance the value belongs to.
  • MIDDLEWARE_PARAM_ID — foreign key to CCT_MIDDLEWARE_PARAMS; identifies which parameter definition is being populated.
  • VALUE — the configured value supplied for that middleware and parameter combination.
  • CONTEXT — contextual qualifier that scopes the value, allowing differentiated settings for the same parameter.
  • NAME — descriptive name associated with the value record.
  • SECURITY_GROUP_ID — foreign key to FND_SECURITY_GROUPS; enforces multi-org / security group access control on the record.
  • OBJECT_VERSION_NUMBER — optimistic locking version used to detect concurrent updates.
  • F_DELETEDFLAG — soft-delete indicator used by the framework to retire rows without physical removal.
  • CREATED_BY, CREATION_DATE — audit attributes capturing row creation.
  • LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — audit attributes capturing the most recent modification.
  • ATTRIBUTE1 through ATTRIBUTE15 — the standard Oracle EBS descriptive flexfield (DFF) segment columns, available for client-specific extensions.

No business-key unique index beyond the surrogate identifier is documented, so the effective business key is the combination of MIDDLEWARE_ID and MIDDLEWARE_PARAM_ID as qualified by CONTEXT.

Common Use Cases and Queries

The typical use case is diagnostic and configuration reporting: administrators need to confirm what value is currently configured for a given middleware parameter, and whether that value has been soft-deleted. Because the table stores payload rather than transactional data, queries are usually joins across the middleware trio.

  • Retrieving active parameter values for a middleware instance: join CCT_MIDDLEWARE_VALUES to CCT_MIDDLEWARES on MIDDLEWARE_ID and to CCT_MIDDLEWARE_PARAMS on MIDDLEWARE_PARAM_ID, filtering on F_DELETEDFLAG.
  • Auditing configuration drift: compare LAST_UPDATE_DATE and LAST_UPDATED_BY across values to identify recently changed telephony settings.
  • Resolving context-specific overrides: select rows sharing the same MIDDLEWARE_PARAM_ID but differing in CONTEXT to understand precedence.
  • Security-scoped reporting: join SECURITY_GROUP_ID to FND_SECURITY_GROUPS to restrict output to the caller’s authorized security groups.
  • Extensibility reporting: surface populated DFF segments from ATTRIBUTE1…ATTRIBUTE15 where the implementation has customized the setup.

Related Objects

  • CCT_MIDDLEWARES — parent registry of middleware instances; joined via CCT_MIDDLEWARE_VALUES.MIDDLEWARE_ID.
  • CCT_MIDDLEWARE_PARAMS — catalogue of parameter definitions; joined via CCT_MIDDLEWARE_VALUES.MIDDLEWARE_PARAM_ID.
  • FND_SECURITY_GROUPS — security group master referenced through SECURITY_GROUP_ID.
  • CCT_CMV_PK and CCT_MIDDLEWARE_VALUES_ID_U1 — the primary key constraint and supporting unique index that govern row identity.

Collectively, these objects form the Telephony Manager middleware configuration model. CCT_MIDDLEWARE_VALUES should be treated as the value-bearing link between middleware instances and parameter definitions, with security group scoping and standard EBS audit, concurrency, and flexfield columns applied consistently with other CCT configuration tables.