Search Results cct_middleware_types




Overview
Explore in AI Chat

Overview

CCT_MIDDLEWARE_TYPES is a reference (lookup) table in the CCT – Telephony Manager product of Oracle E-Business Suite. It enumerates the supported telephony middleware platforms that Oracle EBS can integrate with, such as PROSPECT_ASPECT and OPENTEL. Each row defines a distinct middleware technology that CCT can drive through the middleware configuration and parameter layers, forming the top of the CCT middleware hierarchy. The table resides in the CCT schema and is marked VALID in both the 12.1.1 and 12.2.2 documentation sets.

Under a heuristic Data Vault classification derived from the foreign-key topology, the object is hub-leaning. It behaves as a hub because it holds a stable, non-transactional business key (the middleware type) that is referenced by dependent tables. The modeling suggestion is therefore to treat CCT_MIDDLEWARE_TYPES as the hub for middleware definitions, with CCT_MIDDLEWARES and CCT_MIDDLEWARE_PARAMS as satellites or links hanging off that hub. It is not a transactional or junction table; its rows change infrequently and serve primarily to classify downstream configuration.

Key Information Stored

Although 24 columns are documented in the 12.2.2 physical schema, the functionally significant columns are limited. The surrogate primary key is MIDDLEWARE_TYPE_ID, enforced by the unique index CCT_MIDDLEWARE_TYPE_ID_U1 and by the primary key constraint CCT_CMT_PK. The business-key candidate is MIDDLEWARE_TYPE, enforced by the unique index CCT_MIDDLEWARE_TYPE_U2; this is the human-readable discriminator that identifies the platform (for example, PROSPECT_ASPECT or OPENTEL).

The remaining documented columns fall into three groups:

  • Descriptive and contextual columns: CONTEXT, which scopes the row within the CCT application context, and the fifteen generic ATTRIBUTE1 through ATTRIBUTE15 columns, which provide the standard Oracle EBS descriptive-flexfield-style extension area for product-specific properties of each middleware type.
  • Audit columns: LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, CREATED_BY, and CREATION_DATE, which record who created and last modified each row and when.
  • Security column: SECURITY_GROUP_ID, which references FND_SECURITY_GROUPS and controls row-level access within the Oracle Applications security model.

In practice, most queries and integrations reference only MIDDLEWARE_TYPE_ID, MIDDLEWARE_TYPE, CONTEXT, and SECURITY_GROUP_ID; the attribute columns are reserved for implementation-specific extensions.

Common Use Cases and Queries

The primary use case is resolving the numeric middleware type identifier to a readable name when reporting on middleware configuration. A typical lookup joins the type table to CCT_MIDDLEWARES:

SELECT m.middleware_id, t.middleware_type, m.middleware_name
FROM cct.cct_middlewares m, cct.cct_middleware_types t
WHERE m.middleware_type_id = t.middleware_type_id;

A second common pattern drives configuration validation, confirming that a parameter row in CCT_MIDDLEWARE_PARAMS belongs to a known, active middleware type:

SELECT p.parameter_id, t.middleware_type, p.parameter_name
FROM cct.cct_middleware_params p, cct.cct_middleware_types t
WHERE p.middleware_type_id = t.middleware_type_id
AND t.middleware_type = 'OPENTEL';

Reporting and administrative queries typically list available types, filter by context, or enumerate rows by security group. Because the table is a reference object, it is also a standard candidate for value-set-driven list-of-values definitions and for extract jobs that populate downstream data warehouses with middleware master data.

Related Objects

The most significant dependent object is CCT_MIDDLEWARES, joined on MIDDLEWARE_TYPE_ID; this table records the individual middleware instances configured for each type and is the principal consumer of the type definition. CCT_MIDDLEWARE_PARAMS also references MIDDLEWARE_TYPE_ID and holds the parameters applicable to each middleware type, again joined on the same column. Together these two tables form the configuration body that the type table classifies.

The FND_SECURITY_GROUPS table is referenced through SECURITY_GROUP_ID, establishing the row-level security linkage standard across Oracle EBS. Because the table is delivered as reference data rather than through a public API, integration and reporting generally read it directly, and the documented foreign-key relationships above are the authoritative join paths.