Search Results clone_regions_for_appl

Overview

CS_CF_UPG_PKG is an Oracle EBS Applications (APPS) PL/SQL package owned by the APPS schema and classified as an "OTHER" API within the ETRM metadata for release 12.2.2. It serves as the upgrade driver for the Service (CS) module's Configurator / Contracts Foundation (CF) region and flow customizations. Its primary business function is to migrate and clone existing AK (Application Kit) region and flow definitions across the three standard Oracle EBS profile hierarchy levels: Responsibility, Application, and Site (Global). The package header declares AUTHID CURRENT_USER and carries a $Header tag dated 2005/06/01, indicating it originated in an earlier release cycle but remains catalogued in the 12.1.1 and 12.2.2 documentation sets.

The package automates what would otherwise be manual cloning of configuration regions and flows when customizations are detected at differing profile levels. Users searching for "do_flow_upgrades_for_global" are typically investigating how global-level flow upgrades are executed during an upgrade or patch cycle.

Key Procedures and Functions

The package exposes sixteen documented program units. The upgrade orchestration entry point is Upgrade_Main, which drives the complete region and flow upgrade process. Two boolean functions determine whether work is necessary: Is_Region_Upgrade_Required and Is_Flow_Upgrade_Required, each of which returns output parameters containing the relevant responsibility, application, and site profile sets.

At the region level, the package provides Do_Region_Upgrade for a single region, Do_Region_Upgrades_For_Resp and Do_Region_Upgrades_For_Appl and Do_Region_Upgrades_For_Global to process upgrades across each profile hierarchy tier. The corresponding clone routines are Clone_Regions_For_Resp, Clone_Regions_For_Appl, and Clone_Regions_For_Global, which perform the actual copying of AK region definitions based on the list of profiles customized at each level.

At the flow level, the package mirrors that structure: Do_Flow_Upgrade is the top-level procedure that internally invokes flow upgrades for each profile level (responsibility, application, and global). Do_Flow_Upgrades_For_Resp, Do_Flow_Upgrades_For_Appl, and Do_Flow_Upgrades_For_Global apply flow upgrades at their respective tiers, while Clone_Flows_For_Resp and Clone_Flows_For_Appl perform the actual cloning of flow definitions. Note that a global-level clone procedure for flows is not separately documented in the ETRM list, though Do_Flow_Upgrades_For_Global is present.

Tables Accessed

The package references the following tables through APPS synonyms. FND_PROFILE_OPTION_VALUES and FND_PROFILE_OPTIONS supply the profile-option hierarchy used to determine which customizations exist at responsibility, application, and global levels. AK_REGIONS and AK_REGION_ITEMS hold the region and item definitions being upgraded and cloned. CS_CF_SOURCE_CXT_TARGETS and CS_CF_SOURCE_CXT_TYPES store the Configurator source context type and target mappings central to the region/flow customization model. DUAL is used for singleton queries, and PLITBLM is referenced within the package body. The package also relies on the CS_CF_UPG_UTL_PKG utility package for the RespTable, ApplTable, and ProfileTable PL/SQL collection types passed between procedures.

Usage Notes

CS_CF_UPG_PKG is an internal upgrade utility rather than a general-purpose runtime API. It is typically invoked during the Oracle EBS upgrade or patch application process, either from upgrade driver scripts or from concurrent programs executed by the system administrator. Because the package header uses AUTHID CURRENT_USER, permissions are resolved against the invoking schema's privileges. The ETRM metadata records zero packages referencing CS_CF_UPG_PKG, confirming that it is not intended for direct invocation by other application code. Custom code should not call these procedures outside of the sanctioned upgrade path. Implementers diagnosing messages such as "Do_Flow_Upgrades_For_Global" should treat them as internal trace output from the upgrade execution rather than as a public API entry point.