Search Results cct_route_params




Overview
Explore in AI Chat

Overview

CCT_ROUTE_PARAMS is a Telephony Manager (CCT) configuration table in Oracle E-Business Suite 12.1.1 and 12.2.2. It stores the parameter definitions that drive CCT route behaviour: the individual parameters supplied to database procedures invoked by a route, and the parameters evaluated by route rules at runtime. Each row describes a single parameter — its name, its data type, its direction of flow, its ordinal position, and its literal or derived value — and attaches that definition to a parent route in CCT_ROUTES.

From a Data Vault modelling perspective, the ETRM metadata classifies this object as satellite-leaning. That is a heuristic suggestion rather than a physical EBS construct: the table extends a parent business entity (the route, modelled as the hub) with descriptive, change-tracked attributes and their own surrogate key. Its dependency on FND_SECURITY_GROUPS via SECURITY_GROUP_ID also reflects the standard multi-tenant, row-level security pattern used throughout CCT and other EBS modules.

Key Information Stored

The documented physical schema contains 17 columns. The most significant are:

  • ROUTE_PARAM_ID — surrogate primary key, enforced by constraint CCT_CRP_PK. It uniquely identifies each parameter definition and is the column to use in joins and in any API or DML operation.
  • ROUTE_ID — foreign key to CCT_ROUTES. This is the principal business-key candidate: it ties the parameter to a specific route and, combined with PARAM and SEQUENCE, forms the natural identifying context of a parameter definition.
  • PARAM — the parameter name as referenced by the database procedure or the route rule.
  • DATATYPE — the declared type of the parameter (for example character, number, or date), used to validate and bind the value at execution time.
  • DIRECTION — indicates whether the parameter is an input to, an output from, or used in a bidirectional manner by the procedure.
  • SEQUENCE — the ordinal position of the parameter, which governs the order in which arguments are passed or rules are evaluated.
  • VALUE — the literal or resolution value assigned to the parameter.
  • CLASSIFICATION_ID — grouping or classification reference used to organise parameter definitions.
  • OPERATION — the operation context in which the parameter applies.
  • SECURITY_GROUP_ID — foreign key to FND_SECURITY_GROUPS, enforcing row-level access control.
  • F_DELETEDFLAG — soft-delete indicator; rows are logically retired rather than physically removed.
  • OBJECT_VERSION_NUMBER — optimistic locking column used by the EBS framework to detect concurrent updates.
  • LAST_UPDATE_DATE, CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — standard WHO audit columns recording who created and last changed the row, and when.

Common Use Cases and Queries

Typical scenarios include auditing the parameters defined for a given route, verifying that parameter order and data types match the signature of the target database procedure, and reporting on rule parameters used by routing decisions. A representative query lists the parameters of a route in execution order:

  • SELECT rp.PARAM, rp.DATATYPE, rp.DIRECTION, rp.SEQUENCE, rp.VALUE FROM cct.cct_route_params rp WHERE rp.ROUTE_ID = :route_id AND NVL(rp.F_DELETEDFLAG,'N') = 'N' ORDER BY rp.SEQUENCE;
  • Joining to CCT_ROUTES to produce a route-by-parameter report, filtered by security group: ... FROM cct.cct_route_params rp, cct.cct_routes r WHERE rp.ROUTE_ID = r.ROUTE_ID AND rp.SECURITY_GROUP_ID = :sg_id.
  • Detecting stale or soft-deleted definitions by querying F_DELETEDFLAG = 'Y' for cleanup and impact analysis before changing a route.

Related Objects

The following objects are the most significant dependencies:

  • CCT_ROUTES — parent table; joined on CCT_ROUTE_PARAMS.ROUTE_ID = CCT_ROUTES.ROUTE_ID. This is the documented foreign key relationship and the primary access path.
  • FND_SECURITY_GROUPS — joined on CCT_ROUTE_PARAMS.SECURITY_GROUP_ID = FND_SECURITY_GROUPS.SECURITY_GROUP_ID, providing the security group context for the parameter row.
  • Route rules and procedure definitions within CCT — these consume the PARAM, DATATYPE, DIRECTION, SEQUENCE, and VALUE columns when invoking database procedures or evaluating routing logic.
  • FND_OBJECTS and the CCT application definition — the registered application and table metadata that govern concurrent program and form access to this table.
  • Standard WHO audit infrastructure — the CREATED_BY, LAST_UPDATED_BY, and LAST_UPDATE_LOGIN columns reference FND_USER, supporting audit reporting.