Search Results cct_middleware_delete_sav




Overview
Explore in AI Chat

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

Overview

The APPS.CCT_MIGRATE_MW package body is a database-side utility within the Oracle E-Business Suite middleware configuration layer, historically associated with the Interaction Center / Telephony (CCT) module. Its principal business function is to migrate middleware configuration records from one middleware type to another, preserving parameter and value associations while retiring the obsolete middleware type so that it no longer surfaces in the administrative user interface. The package operates entirely at the table level and is packaged as a "noship" internal utility, as reflected in its header comment ($Header: cctmigmb.pls 115.3 2004/06/22 ... noship $).

The user search term middleware_type_id is central to the package's logic. Every procedure in the body pivots on this column: it is the driving predicate for lookups, updates, and deletions across the CCT middleware tables. Migration effectively re-points middleware_type_id from a source identifier to a target identifier, then reconciles dependent parameter and value rows.

Key Procedures and Functions

  • MIGRATE_MIDDLEWARE — The primary entry point. It accepts a source middleware type identifier, a target middleware type identifier, and an optional configuration name. When a configuration name is supplied, the procedure resolves the specific middleware_id and updates only that configuration; when the name is null, it updates all rows matching the source type. It then calls DELETE_PARAMS and UPDATE_PARAMS to reconcile dependent data, and finally removes the old middleware_type_id from CCT_MIDDLEWARE_TYPES when no surviving middleware_id remains, so the obsolete type does not appear in the Admin UI.
  • DELETE_PARAMS — Purges orphaned middleware parameter values that exist under the source type but have no counterpart in the target type. It uses a MINUS query across CCT_MIDDLEWARE_PARAMS keyed on parameter name, guarded by a savepoint (CCT_MIDDLEWARE_DELETE_SAV).
  • UPDATE_PARAMS — Repoints surviving parameter and value records from the source middleware type to the target, aligning the migrated configurations with the target type's parameter definitions.
  • UPDATE_AGENT_PARAMS — Maintains the corresponding agent/resource parameter and value rows, extending the migration to the JTF_RS_RESOURCE_PARAMS and JTF_RS_RESOURCE_VALUES tables.

Tables Accessed

  • CCT_MIDDLEWARES — The configuration master; source of the middleware_type_id and config_name filters and the target of migration updates.
  • CCT_MIDDLEWARE_PARAMS — Defines parameters per middleware type; used to identify matching parameters by name during the MINUS comparison.
  • CCT_MIDDLEWARE_TYPES — The middleware type registry; obsolete source rows are deleted here to suppress them from the Admin UI.
  • CCT_MIDDLEWARE_VALUES — Stores parameter values; rows are deleted or repointed according to the parameter reconciliation outcome.
  • JTF_RS_RESOURCE_PARAMS and JTF_RS_RESOURCE_VALUES — Agent/resource parameter and value tables updated to keep agent-side configuration consistent.

Usage Notes

The package is an internal utility (classification OTHER) and is not referenced by any other documented package. It is therefore invoked directly rather than through a standard API chain — typically from a migration script, an administrator-driven correction, or a one-off data-fix execution. Because it is shipped as noship, it is not part of a supported public API surface and should be used with caution on 12.1.1 and 12.2.2 instances. Deployments should ensure the target middleware type already defines the parameters expected by migrated configurations; otherwise the DELETE_PARAMS reconciliation will remove values without replacement. Transactions are protected by a savepoint, but callers performing bulk migrations across many types should validate results in CCT_MIDDLEWARES and CCT_MIDDLEWARE_VALUES before committing.