Search Results appl_already_exists

Overview

CS_CF_UPG_UTL_PKG is an Oracle EBS upgrade utility package owned by the APPS schema and classified as OTHER in the ETRM repository. Its primary business function is to evaluate and reconcile Oracle iSupport (CS) profile option settings and configuration data during the upgrade of a customer's existing environment, most notably between 11i and the 12.1.1 / 12.2.2 code lines. The package determines whether seeded out-of-the-box defaults have been changed by the customer and, where a legacy value no longer maps cleanly to the new functional model, flags that remediation or data migration is required. A second, equally important role is the management of Service Request configuration-flow mappings — the relationship between a source context, an application, a responsibility, and the regions that should appear on the Service Request form.

The $Header comment dates the shipped version to January 2006, which is consistent with its lifecycle: the package is a one-time upgrade and diagnostic utility rather than a runtime business API. It is not intended for direct end-user invocation.

Key Procedures and Functions

The metadata documents 31 procedures and functions, which fall into three functional groups.

• Profile option evaluation functions. The largest group, comprising EVAL_SR_ACCOUNT_OPTION, EVAL_SR_PROBLEM_CODE_OPTION, EVAL_SR_ADDR_DISPLAY, EVAL_SR_ADDR_MANDATORY, EVAL_SR_BILLTO_ADDRESS_OPTION, EVAL_SR_BILLTO_CONTACT_OPTION, EVAL_SR_CREATION_PROD_OPTION, EVAL_SR_SHIPTO_ADDRESS_OPTION, EVAL_SR_SHIPTO_CONTACT_OPTION, EVAL_SR_INSTALLEDAT_ADDRESS, EVAL_SR_ATTACHMENT_OPTION, EVAL_SR_TASK_DISPLAY, EVAL_SR_ENABLE_INTERACT_LOG, EVAL_SR_KB_OPTION, EVAL_SR_ENABLE_TEMPLATE, and EVAL_SR_PRODUCT_SELECTION. Each inspects the value of a specific iSupport profile option across the site, application, responsibility, and user hierarchy levels, compares it with the seeded default, and reports whether upgrade action is needed. Eval_SR_Account_Option, shown in the excerpt, reads the IBU_A_SR_ACCOUNT_OPTION profile and tests the site-level value against 'MWOSO'; any divergence sets an upgrade-required flag.
• Existence checks. RESP_ALREADY_EXISTS and APPL_ALREADY_EXISTS answer the question the user referenced — whether a target responsibility or application has already been created or migrated — allowing the upgrade to run idempotently without duplicating seed data.
• Configuration flow utilities. INSERT_NEW_TARGET and CLONE_REGION create and replicate configuration-flow target records and region definitions so that a new responsibility or context inherits the correct Service Request layout.

Tables Accessed

• FND_PROFILE_OPTIONS and FND_PROFILE_OPTION_VALUES — read through the get_profile_option_values and get_profile_option_count cursors to obtain the level identifiers and stored values for each iSupport profile option. These drive every EVAL_* function.
• AK_REGIONS, AK_REGION_ITEMS, AK_REGION_ITEMS_TL — the region metadata used by CLONE_REGION to reproduce a form region and its items, including translated labels, for a new target.
• CS_CF_FLOWS_B, CS_CF_SOURCE_CXT_TARGETS, CS_CF_SOURCE_CXT_TARGETS_S, CS_CF_SOURCE_CXT_TYPES — the Service Request configuration-flow model, where INSERT_NEW_TARGET writes new source-context-to-target mappings and their sequence numbers.
• DUAL — used for scalar lookups. PLITBLM is the standard PL/SQL table and record type library, and V$PARAMETER supplies database-level parameter information.

Usage Notes

CS_CF_UPG_UTL_PKG is invoked from the upgrade driver and diagnostic scripts rather than from a form or concurrent program. The EVAL_* functions are typically called inside an anonymous PL/SQL block that walks the profile hierarchy, accumulates the returned BOOLEAN flags, and reports the set of options that deviate from the seeded defaults so the DBA can decide whether to retain or reset them. RESP_ALREADY_EXISTS and APPL_ALREADY_EXISTS are used as guards before insertion, while INSERT_NEW_TARGET and CLONE_REGION are called to materialize missing configuration-flow rows.

Because the package manipulates AK region and CS_CF tables directly and relies on release-specific profile option names, it should only be executed as part of the sanctioned upgrade path, with a validated backup of the FND and AK schema. All calls should be run as the APPS schema. Neither the package specification nor its logic is designed for reuse in custom extensions.