Search Results cct_middleware_params




Overview
Explore in AI Chat

Overview

CCT_MIDDLEWARE_PARAMS is a Telephony Manager (CCT) configuration table in Oracle E-Business Suite 12.1.1 and 12.2.2. It defines the individual parameters that a given middleware type requires for operation within the CRM telephony integration framework. Each row represents one parameter belonging to one middleware type, capturing its name, data type, length, and an optional domain lookup validation source. The table is owned by the CCT schema and is classified as VALID in the ETRM repository.

From a Data Vault modeling perspective, the mined foreign-key structure suggests a satellite-leaning classification: the table carries descriptive, non-identifying attributes (name, type, length, lookup domain) that qualify a parent entity—CCT_MIDDLEWARE_TYPES—rather than acting as an independent hub or a pure link between hubs. It does, however, participate in a genuine referential chain that terminates in the CCT_MIDDLEWARE_VALUES table, so it functions as both a dependent child and a parent in the telephony middleware data model.

Key Information Stored

The table contains 31 documented columns. The most significant are:

  • MIDDLEWARE_PARAM_ID — the surrogate primary key, enforced by CCT_MIDDLEWARE_PARAMS_PK and mirrored by unique index CCT_MIDDLEWARE_PARAMS_ID_U1. It is the column referenced by dependent value records.
  • MIDDLEWARE_TYPE_ID — a foreign key to CCT_MIDDLEWARE_TYPES identifying the parent middleware configuration to which the parameter belongs.
  • NAME — the parameter name. Together with MIDDLEWARE_TYPE_ID, it forms the business-key unique index CCT_MID_NAME_U2, ensuring parameter names are unique within a middleware type.
  • TYPE and LENGTH — the declared data type and maximum length of the parameter, used when validating or rendering runtime values.
  • DOMAIN_LOOKUP_TYPE — an optional reference to a lookup type that constrains permitted parameter values.
  • CONTEXT — the descriptive or functional context in which the parameter applies.
  • ORDERING_SEQUENCE — controls the display or processing order of parameters for a middleware type.
  • SECURITY_GROUP_ID — a foreign key to FND_SECURITY_GROUPS, supporting multi-org and data-security partitioning.
  • OBJECT_VERSION_NUMBER — optimistic locking column used by OA Framework and concurrent updates.
  • F_DELETEDFLAG — soft-delete indicator maintained by the CCT framework.
  • ATTRIBUTE1 through ATTRIBUTE15 — the standard EBS descriptive flexfield columns for extensible, customer-defined attributes.
  • CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard EBS audit columns.

Common Use Cases and Queries

The table is queried when diagnosing telephony middleware configuration, when migrating middleware setups between environments, and when joining parameter definitions to their runtime values. A typical query retrieves all parameters for a given middleware type in display order:

SELECT p.middleware_param_id, p.name, p.type, p.length,
       p.domain_lookup_type, p.ordering_sequence
FROM cct.cct_middleware_params p
WHERE p.middleware_type_id = :type_id
  AND NVL(p.f_deletedflag,'N') = 'N'
ORDER BY p.ordering_sequence, p.name;

A second common pattern joins parameters to CCT_MIDDLEWARE_VALUES to produce a complete middleware configuration report, or joins to CCT_MIDDLEWARE_TYPES to list all parameters across every configured middleware. Reporting use cases include auditing which parameters reference lookup validations, identifying parameters missing values, and comparing parameter definitions across crup/instance clones.

Related Objects

  • CCT_MIDDLEWARE_TYPES — parent entity; joined on CCT_MIDDLEWARE_PARAMS.MIDDLEWARE_TYPE_ID = CCT_MIDDLEWARE_TYPES.MIDDLEWARE_TYPE_ID.
  • CCT_MIDDLEWARE_VALUES — child entity holding actual parameter values; joined on CCT_MIDDLEWARE_VALUES.MIDDLEWARE_PARAM_ID = CCT_MIDDLEWARE_PARAMS.MIDDLEWARE_PARAM_ID.
  • FND_SECURITY_GROUPS — referenced via SECURITY_GROUP_ID; used to resolve security group names for partitioned rows.
  • FND_LOOKUP_VALUES — implicitly referenced through DOMAIN_LOOKUP_TYPE for validating permitted parameter values (not a declared FK).
  • FND_FLEX_VALUES / FND_DESCR_FLEX_COL_USAGE — relevant when the ATTRIBUTE1–15 flexfield columns are enabled.
  • CCT_MIDDLEWARE_PARAMS_PK and unique indexes CCT_MIDDLEWARE_PARAMS_ID_U1 and CCT_MID_NAME_U2 — constraint objects that enforce identity and business-key uniqueness.

Because the CCT module is largely a configuration and integration layer, no public PL/SQL APIs are documented for CCT_MIDDLEWARE_PARAMS; changes are typically made through the Telephony Manager administrative UI or by direct DML during implementation and data migration.