Search Results cct_middlewares_pk

Overview

CCT_MIDDLEWARES is a Telephony Manager (CCT) configuration table in Oracle E-Business Suite, owned by the CCT schema and marked VALID in both 12.1.1 and 12.2.2. It stores the connection and interface parameters that Oracle EBS requires when communicating with a telephony switch through an intervening middleware layer. Rather than binding the application directly to vendor-specific switch protocols, EBS persists the middleware endpoint definition — network address, port, server grouping, configuration profile name, type classification, and a broad set of descriptive flexfield attributes — so that IVR mappings, telesets, and middleware value sets can resolve their runtime behavior consistently.

Under a heuristic Data Vault classification derived from its foreign key topology, CCT_MIDDLEWARES is satellite-leaning. It carries identifying and descriptive attributes (endpoint, port, config name, flex attributes) that describe a middleware entity referenced from other CCT objects. A formal Data Vault design would treat this as a satellite attached to a middleware hub, with CCT_MIDDLEWARES_PK as the surrogate key and MIDDLEWARE_ID as the stable business key. This classification is a modeling suggestion, not a documented Oracle construct.

Key Information Stored

The table is documented with 35 columns. The following are the most operationally significant:

• MIDDLEWARE_ID — the surrogate primary key, enforced by CCT_MIDDLEWARES_PK and reinforced by the unique index CCT_MIDDLEWAREID_U1. Because it is the sole documented unique business-key candidate, MIDDLEWARE_ID also serves as the effective integration key.
• MIDDLEWARE_TYPE_ID — foreign key to CCT_MIDDLEWARE_TYPES, classifying the middleware flavor or protocol family.
• SERVER_GROUP_ID — groups the middleware record with a server pool, supporting load distribution across switch connections.
• CONFIG_NAME — human-readable profile label used to identify the configuration in setup and administration screens.
• MIDDLEWARE_IP_ADDRESS and MIDDLEWARE_PORT — the network endpoint at which the middleware accepts EBS connections.
• CONTEXT — the descriptive flexfield context controlling which of the ATTRIBUTE columns are meaningful for a given row.
• ATTRIBUTE1 through ATTRIBUTE15 — descriptive flexfield segments holding vendor- or deployment-specific parameters not covered by the standard columns.
• EXTRA1 through EXTRA5 — additional extension columns for site-specific middleware settings.
• SECURITY_GROUP_ID — foreign key to FND_SECURITY_GROUPS, enforcing multi-tenant data isolation.
• OBJECT_VERSION_NUMBER and F_DELETEDFLAG — optimistic locking and soft-delete markers used by the CCT concurrent programs.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, CREATED_BY, CREATION_DATE — standard Oracle who-columns for auditing and change tracking.

Common Use Cases and Queries

Typical applications include verifying which middleware endpoints are active before opening a switch integration, auditing configuration drift between environments, and reporting all telesets and IVR maps that depend on a single middleware definition.

Listing active middleware endpoints:

• SELECT m.MIDDLEWARE_ID, m.CONFIG_NAME, m.MIDDLEWARE_IP_ADDRESS, m.MIDDLEWARE_PORT, t.MIDDLEWARE_TYPE_NAME FROM CCT.CCT_MIDDLEWARES m, CCT.CCT_MIDDLEWARE_TYPES t WHERE m.MIDDLEWARE_TYPE_ID = t.MIDDLEWARE_TYPE_ID AND NVL(m.F_DELETEDFLAG,0) = 0 AND m.SECURITY_GROUP_ID = :security_group_id;

Finding dependent telesets and IVR maps for impact analysis:

• SELECT 'TELESET' AS SOURCE, TELESET_ID AS ID FROM CCT.CCT_TELESETS WHERE MIDDLEWARE_ID = :id UNION ALL SELECT 'IVRMAP', IVR_MAP_ID FROM CCT.CCT_IVR_MAPS WHERE MIDDLEWARE_ID = :id;

Reporting flexfield configuration for a given context:

• SELECT CONFIG_NAME, CONTEXT, ATTRIBUTE1, ATTRIBUTE2, ATTRIBUTE3 FROM CCT.CCT_MIDDLEWARES WHERE CONTEXT = :ctx ORDER BY CONFIG_NAME;

Because CCT tables are rarely exposed through supported public APIs, direct SQL is the usual reporting path; always filter by SECURITY_GROUP_ID and respect F_DELETEDFLAG to avoid stale or cross-tenant rows.

Related Objects

• CCT_MIDDLEWARE_TYPES — referenced by MIDDLEWARE_TYPE_ID; supplies the classification of each middleware row.
• CCT_MIDDLEWARE_VALUES — child table referencing CCT_MIDDLEWARES.MIDDLEWARE_ID; holds key-value parameter pairs for each middleware definition.
• CCT_TELESETS — references CCT_MIDDLEWARES.MIDDLEWARE_ID; binds telephony agent sets to a specific middleware endpoint.
• CCT_IVR_MAPS — references CCT_MIDDLEWARES.MIDDLEWARE_ID; associates IVR mapping rules with the middleware that services them.
• FND_SECURITY_GROUPS — referenced through SECURITY_GROUP_ID; governs row-level visibility of middleware records.

Together these dependencies confirm that CCT_MIDDLEWARES functions as the central configuration reference for switch middleware connectivity within the Telephony Manager module.