Results for “value_type”

50+ results




Overview
Explore in AI Chat

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

Overview

JTF_RS_CCT_MIDDLEWARES_V is a valid, APPS-owned database view in Oracle E-Business Suite release 12.1.1 and 12.2.2, belonging to the JTF – CRM Foundation product family. The view's documented purpose is to validate Call Center Parameters, and the ETRM metadata explicitly identifies it as the replacement for the legacy CCT_MIDDLEWARES_V view. It therefore functions as the supported interface through which Call Center middleware configuration data is exposed to forms, reports, and integration code, while shielding consumers from the underlying column naming and datatype conventions of the base table.

The defining characteristic of this view is its translational role. Rather than presenting the base table columns verbatim, the view renames and recasts them so that generic middleware records can be interpreted as call center interaction parameters. This makes the view a validation and presentation layer: Call Center setup logic can query it to confirm that a middleware row is defined and active before an interaction channel is configured or invoked. Systems performing data extraction or interface development should treat the view, not the base table, as the supported access point.

Underlying Base Objects

The view is defined over a single documented base object, CCT_MIDDLEWARES, which is exposed in the APPS schema as a synonym. There are no joins, unions, or aggregation constructs in the view text; it is a straightforward projection over one table. Each row in CCT_MIDDLEWARES yields exactly one row in JTF_RS_CCT_MIDDLEWARES_V, so cardinality is preserved and no filtering predicate is applied. The view text performs only column aliasing and explicit TO_CHAR conversions on the identifier columns. Because the view carries no WHERE clause, consumers must apply their own filters — typically on INTERACTION_CENTER_ID, CONFIG_NAME, PARAM_TYPE, or DELETE_FLAG — to isolate the parameters relevant to a given call center configuration.

Key Columns

  • INTERACTION_CENTER_ID — Aliased from SERVER_GROUP_ID. Identifies the interaction center (server group) to which the middleware configuration belongs.
  • CONFIG_NAME — Exposed with the same name as in the base table. Provides the configuration name associated with the middleware record.
  • PARAM_TYPE — Aliased from MIDDLEWARE_TYPE_ID and converted via TO_CHAR. Identifies the category or type of middleware parameter as a character string.
  • VALUE_TYPE — Aliased from MIDDLEWARE_ID and converted via TO_CHAR. This is the column most frequently targeted by searches for "value_type"; it represents the value associated with the parameter identified by PARAM_TYPE, expressed as a string.
  • DELETE_FLAG — Aliased from F_DELETEDFLAG. Indicates whether the underlying middleware record is logically deleted, allowing consumers to exclude obsolete configuration.

Common Use Cases and Queries

The primary scenario is validating that a given interaction center has the middleware parameters it requires, and retrieving the corresponding values. A typical query filters by center and configuration and excludes deleted rows:

  • SELECT interaction_center_id, config_name, param_type, value_type FROM jtf_rs_cct_middlewares_v WHERE interaction_center_id = :center_id AND config_name = :config_name AND delete_flag = 'N';
  • SELECT param_type, value_type FROM apps.jtf_rs_cct_middlewares_v WHERE interaction_center_id = :center_id AND delete_flag = 'N' ORDER BY param_type;
  • SELECT COUNT(*) FROM apps.jtf_rs_cct_middlewares_v WHERE interaction_center_id = :center_id AND param_type = :param_type AND delete_flag = 'N';

Because PARAM_TYPE and VALUE_TYPE are character representations of numeric identifiers, comparisons involving them should use string literals or explicit conversions, and joins back to type or middleware definition tables should account for the TO_CHAR mapping. These queries are suitable for setup verification, migration validation, report parameter lists, and inbound interface lookups where call center behavior depends on correctly registered middleware values.