Search Results cct_tempagents




Overview
Explore in AI Chat

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

CCT_TEMPAGENTS is a transient working table owned by the CCT schema, the database account associated with the Oracle Telephony Manager (CCT) product in Oracle E-Business Suite. As documented in the ETRM repository for releases 12.1.1 and 12.2.2, its stated purpose is to support Routing Server Workflow definitions by keeping track of the agents returned by individual workflow nodes. During execution of a telephony routing workflow, each node may evaluate conditions and produce a set of candidate agents; those intermediate results are persisted in this table so that subsequent nodes in the same workflow can consume, filter, or forward the agent list without recomputing prior decisions.

Because the table functions as an intermediate staging area rather than a system of record, its contents are typically short-lived and scoped to an active workflow execution or call context. The heuristic Data Vault classification mined from its foreign key structure is standalone; from a modeling perspective this suggests the table behaves more like a transient satellite or staging construct than a durable hub or link. It carries no downstream child tables, and its single documented foreign key points outward to FND_SECURITY_GROUPS rather than to another business entity within CCT.

Key Information Stored

The table is documented with 26 columns in the 12.2.2 physical schema. The most operationally significant are:

  • TEMPAGNET_ID — the surrogate primary key, enforced by the constraint CCT_TEMPAGENTS_PK. The column name as documented carries a typographical variant, but it is the unique row identifier.
  • AGENT_ID — identifies the resource or agent returned by the workflow node and staged in this row. This is the principal business-key candidate for joining back to agent and resource definitions.
  • CALL_ID — associates the staged agent set with a specific interaction or call context, allowing concurrent workflows to be isolated from one another.
  • FILTER_TYPE — records the classification or filter applied to the agent result set at the originating node, distinguishing how the set was derived.
  • CONTEXT — holds workflow or routing context passed between nodes, preserving the state needed for downstream evaluation.
  • SECURITY_GROUP_ID — the foreign key to FND_SECURITY_GROUPS, providing multi-tenant and organizational data isolation consistent with the rest of the EBS data model.
  • ATTRIBUTE1 through ATTRIBUTE15 — the standard Oracle descriptive flexfield (DFF) segment columns, available for client-specific extensions.
  • LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, CREATION_DATE, CREATED_BY — the standard EBS who-column audit set, enabling traceability of when the staged result was written.

Common Use Cases and Queries

Diagnostic queries on this table are primarily used to debug routing behavior — determining which agents a workflow node returned for a given call, and whether a filter removed expected agents. A typical pattern joins the staged rows to the agent entity by AGENT_ID and scopes by CALL_ID to reconstruct a single workflow execution:

  • SELECT agent_id, filter_type, context FROM cct_tempagents WHERE call_id = :call_id;
  • SELECT t.agent_id, r.resource_id FROM cct_tempagents t, jtf_rs_resource_extns r WHERE t.agent_id = r.resource_id;
  • SELECT security_group_id, COUNT(*) FROM cct_tempagents GROUP BY security_group_id;
  • Purge and housekeeping checks: SELECT COUNT(*) FROM cct_tempagents WHERE creation_date < SYSDATE - 1;

Operational and reporting use cases include validating that agent distribution across security groups matches organizational expectations, auditing filter effectiveness, and confirming that transient rows are being cleaned up after workflow completion. Because the data is transient, it should not be used as a historical reporting source; persistent agent routing history resides in the CCT interaction and routing log tables.

Related Objects

  • FND_SECURITY_GROUPS — referenced by the documented foreign key CCT_TEMPAGENTS.SECURITY_GROUP_ID.
  • JTF_RS_RESOURCE_EXTNS and the JTF resource tables — the natural join targets for AGENT_ID, resolving staged agent identifiers to resource records.
  • CCT_TELEPHONY components and the Routing Server Workflow definitions — the consumers that populate and read this table at runtime.
  • CCT interaction and call-detail tables — linked through CALL_ID, providing the durable record of the interaction whose routing produced these rows.
  • The CCT Routing Server APIs and workflow engine packages — the programmatic producers and consumers of CCT_TEMPAGENTS rows during node evaluation.