Search Results update_params

Overview

The APPS.CCT_MIGRATE_MW package is a PL/SQL migration utility belonging to the Oracle E-Business Suite Contact Center / Telephony (CCT) schema, traditionally associated with the interaction center middleware configuration layer. Its principal business function is to migrate middleware configuration definitions and their associated parameter rows from one middleware instance to another, reconciling the dependent parameter, value, and resource records so that a target middleware definition inherits a complete and internally consistent configuration.

The package is declared with AUTHID CURRENT_USER, meaning its SQL statements execute under the privilege domain of the invoking user rather than the package owner; callers must therefore hold appropriate privileges on the underlying CCT and JTF resource tables. The source header indicates a version history dating to 2004, and the package is classified as OTHER in the ETRM 12.2.2 metadata, indicating it is an internal utility rather than a published integration API. It is referenced by zero other packages, confirming that it is a top-level migration routine invoked directly rather than a shared library routine.

Key Procedures and Functions

The package exposes four documented procedures. No parameter lists beyond the source excerpt are asserted here.

• MIGRATE_MIDDLEWARE — The primary entry point. It performs the migration of configuration from a source middleware definition to a target middleware definition, taking source and target middleware identifiers together with a name used to label or identify the resulting migrated definition.
• DELETE_PARAMS — Removes parameter rows associated with a middleware definition within the scope of a migration, allowing stale or superseded parameters to be cleared before or after the migration is applied.
• UPDATE_PARAMS — Refreshes or realigns standard middleware parameter records so that the target middleware's parameters reflect the migrated source configuration.
• UPDATE_AGENT_PARAMS — Performs the equivalent reconciliation for agent-level (resource-level) parameters, ensuring that resource parameter and value assignments remain synchronized with the migrated middleware definition.

Tables Accessed

The package operates across the CCT middleware configuration tables and the JTF resource parameter tables, accessed through APPS synonyms.

• CCT_MIDDLEWARES — The master middleware definition table; source and target middleware instances are identified here.
• CCT_MIDDLEWARE_PARAMS — Stores parameter definitions attached to a middleware instance; the primary target of the parameter deletion and update logic.
• CCT_MIDDLEWARE_TYPES — Defines the middleware type, providing the structural context that determines which parameters are applicable.
• CCT_MIDDLEWARE_VALUES — Holds the concrete values assigned to middleware parameters, migrated alongside their definitions.
• JTF_RS_RESOURCE_PARAMS and JTF_RS_RESOURCE_VALUES — Resource-layer parameter and value tables used by the agent parameter routines to align telephony or interaction-channel settings for assigned resources.

Usage Notes

CCT_MIGRATE_MW is an administrative migration utility rather than a runtime business API. In Oracle EBS 12.1.1 and 12.2.2 environments it is typically invoked from setup or administration forms within the Telephony / Interaction Center configuration responsibilities, from a concurrent program wrapper, or from DBA-authored SQL*Plus or PL/SQL scripts during environment cloning, configuration uplift, or release-to-release migration of middleware definitions.

Because the package manipulates configuration data directly and is not referenced by other packages, it should be treated as unsupported for extension. Oracle's standard guidance applies: validate all changes in a non-production instance, take a backup of the affected CCT and JTF tables prior to execution, and re-run any required concurrent programs that regenerate middleware configuration caches after the migration completes. Custom code should not call these procedures as part of ongoing transactional processing.