Search Results cct_middleware_type_u2

Overview

The CCT.CCT_MIDDLEWARE_TYPES table is a seed data object in the Oracle E-Business Suite 12.1.1 and 12.2.2 environments, residing in the CCT schema. Its documented role is to list each middleware type supported by the Customer Care / Telephony integration layer, with examples cited in the ETRM metadata including PROSPECT_ASPECT and OPENTEL. It is registered as FND Design Data under CCT.CCT_MIDDLEWARE_TYPES with status VALID.

Under the heuristic Data Vault classification supplied in the metadata, this object is characterised as hub-leaning. In Data Vault terms, this suggests the table functions as a reference hub for the middleware type business concept, with a single business key and no inherent transactional measures. Its physical storage is in the APPS_TS_SEED tablespace with PCT Free 10, consistent with a low-volume, reference-data table containing setup and seed rows rather than transactional content.

Key Information Stored

The table contains 24 documented columns. The primary key is MIDDLEWARE_TYPE_ID (NUMBER, GUI), the surrogate unique identifier for each middleware type, enforced by the unique index CCT_MIDDLEWARE_TYPE_ID_U1. This is the index the user searched for.

The business-key candidate is MIDDLEWARE_TYPE (VARCHAR2 32, USER), the human-readable middleware type name, enforced by the unique index CCT_MIDDLEWARE_TYPE_U2. Together with the surrogate key, these form the two unique index definitions documented for the table.

• MIDDLEWARE_TYPE_ID — surrogate unique identifier (GUI).
• MIDDLEWARE_TYPE — middleware type name (USER).
• CONTEXT — Descriptive Flexfields structure defining column, used to anchor DFF definitions.
• ATTRIBUTE1 through ATTRIBUTE15 — Descriptive Flexfield segment columns, each VARCHAR2 150, enabling user-extensible configuration of middleware type attribute capture.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, CREATED_BY, CREATION_DATE — standard WHO audit columns.
• SECURITY_GROUP_ID — reference to FND_SECURITY_GROUPS, used in hosted/multi-org environments.

Common Use Cases and Queries

Typical usage is to resolve a middleware type name to its identifier when joining downstream transactional tables, or to drive descriptive flexfield configuration for the CCT middleware setup. A common lookup pattern uses the unique index CCT_MIDDLEWARE_TYPE_U2 on the business key:

SELECT mid.middleware_type_id,
       mid.middleware_type,
       mid.context
  FROM cct.cct_middleware_types mid
 WHERE mid.middleware_type = :type_name;

To enumerate all configured middleware types for reporting or validation purposes:

SELECT mid.middleware_type_id,
       mid.middleware_type
  FROM cct.cct_middleware_types mid
 WHERE mid.security_group_id = :sg_id;

A flexfield-driven extract uses the DFF segments:

SELECT mid.middleware_type,
       mid.attribute1, mid.attribute2, mid.attribute3
  FROM cct.cct_middleware_types mid;

Because the table resides in APPS_TS_SEED, bulk queries should include the WHO columns when auditing changes to seed reference data.

Related Objects

• CCT.CCT_MIDDLEWARES — references CCT_MIDDLEWARE_TYPES.MIDDLEWARE_TYPE_ID via the column MIDDLEWARE_TYPE_ID; the primary transactional table linked to each middleware configuration.
• CCT.CCT_MIDDLEWARE_PARAMS — references CCT_MIDDLEWARE_TYPES.MIDDLEWARE_TYPE_ID; holds parameter definitions for each middleware type.
• FND_SECURITY_GROUPS — referenced by CCT_MIDDLEWARE_TYPES.SECURITY_GROUP_ID; used to scope rows in hosted environments.

The two downstream tables, CCT_MIDDLEWARES and CCT_MIDDLEWARE_PARAMS, both resolve their middleware type through the unique MIDDLEWARE_TYPE_ID key, making CCT_MIDDLEWARE_TYPES the reference hub for the CCT middleware schema. Joins should always be performed on MIDDLEWARE_TYPE_ID rather than MIDDLEWARE_TYPE to align with the documented foreign key paths.