Search Results cct_middlewareid_u1

Overview

CCT.CCT_MIDDLEWARES is a configuration table within the Customer Care and Telephony (CCT) module of Oracle E-Business Suite, supported in both Release 12.1.1 and 12.2.2. The table stores the connection definitions required for interfacing EBS telephony components with the middleware layer of a switch or computer-telephony integration (CTI) environment. Each row describes a named middleware endpoint — its network address, port, server group assignment, and middleware type — so that call center, teleset, and IVR configuration can reference a single, reusable middleware definition rather than embedding connection details in each dependent record.

The table is registered against FND Design Data as CCT.CCT_MIDDLEWARES, resides in the APPS_TS_TX_DATA tablespace with PCTFREE 10, and is owned by the CCT schema. From a heuristic Data Vault perspective, the mined relationship structure classifies this object as satellite-leaning: it hangs off the CCT_MIDDLEWARE_TYPES and FND_SECURITY_GROUPS parents while acting as a parent in its own right to several transactional CCT tables. This classification should be treated as a modeling suggestion, reflecting the EBS implementation rather than a formally declared Data Vault construct.

Key Information Stored

The documented schema comprises 35 columns. The most operationally significant are:

• MIDDLEWARE_ID — the numeric surrogate primary key (CCT_MIDDLEWARES_PK) and the column underlying the unique index CCT_MIDDLEWAREID_U1, which the user searched for. Though generated as a surrogate, it functions as the business-key candidate because it is the only documented unique index column on the table.
• CONFIG_NAME — a user-defined VARCHAR2(128) name identifying the middleware configuration; combined with SERVER_GROUP_ID it forms the non-unique index CCT_CALL_CONFIG_N2.
• SERVER_GROUP_ID — foreign key to the CCT_CALL_CENTER table, tying the middleware endpoint to a specific call center or server group.
• MIDDLEWARE_IP_ADDRESS — the DNS name or IP address of the middleware server.
• MIDDLEWARE_PORT — the IP port used to reach the middleware server.
• MIDDLEWARE_TYPE_ID — foreign key to CCT_MIDDLEWARE_TYPES, indexed non-uniquely via CCT_MIDDLEWARE_TYPE_ID_N1, classifying the middleware product or protocol.
• SECURITY_GROUP_ID — foreign key to FND_SECURITY_GROUPS, enforcing multi-org/security partitioning.
• CONTEXT and ATTRIBUTE1–ATTRIBUTE15 — the Descriptive Flexfield structure-defining column and segment columns, providing extensibility without schema change.
• EXTRA1–EXTRA5 — additional expansion columns, numeric and VARCHAR2(128), reserved for implementation-specific use.
• Audit and concurrency columns — LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, CREATED_BY, CREATION_DATE, OBJECT_VERSION_NUMBER (used by the EBS optimistic locking framework), and F_DELETEDFLAG.

Common Use Cases and Queries

The primary use case is resolving the connection endpoint for a given call center or teleset. A typical join pairs the middleware table with the call center and middleware type definitions:

• Listing all middleware endpoints for a server group: SELECT middleware_id, config_name, middleware_ip_address, middleware_port FROM cct_middlewares WHERE server_group_id = :p_group_id AND f_deletedflag = 'N';
• Finding the middleware definition used by a teleset or IVR map, by joining on MIDDLEWARE_ID.
• Validating uniqueness of the business key by querying the CCT_MIDDLEWAREID_U1 index column, or checking for duplicate configurations across a server group using the CCT_CALL_CONFIG_N2 columns.
• Reporting on middleware types in use across all active configurations via CCT_MIDDLEWARE_TYPE_ID_N1 and the CCT_MIDDLEWARE_TYPES lookup.
• Extracting flexfield data by filtering on CONTEXT and reading ATTRIBUTE1–ATTRIBUTE15.

Queries should generally filter on F_DELETEDFLAG and honor SECURITY_GROUP_ID to respect multi-org security.

Related Objects

The table participates in a well-defined dependency network:

• CCT_MIDDLEWARE_TYPES — referenced through MIDDLEWARE_TYPE_ID; supplies the type classification.
• FND_SECURITY_GROUPS — referenced through SECURITY_GROUP_ID; governs security partitioning.
• CCT_CALL_CENTER — the parent implied by the SERVER_GROUP_ID foreign key, defining the server group to which the middleware belongs.
• CCT_MIDDLEWARE_VALUES — child table referencing MIDDLEWARE_ID; stores the configuration values associated with a middleware definition.
• CCT_TELESETS — references MIDDLEWARE_ID, linking agent telesets to their middleware endpoint.
• CCT_IVR_MAPS — references MIDDLEWARE_ID, associating IVR routing maps with the middleware connection.

These relationships make CCT_MIDDLEWARES a central configuration hub for CCT telephony integration, and any change to a row can propagate to teleset, IVR, and middleware value configurations.