Search Results get_rel
Overview
APPS.CN_UPGRADE_UTL_PKG is a utility package body shipped with the Oracle E-Business Suite Incentive Compensation (CN) module. Its principal business function is to support the upgrade and migration of commission and sales-rep compensation data structures across historical release boundaries, most notably from Oracle EBS 11.5.10 (and earlier 10.7, 3i, 11.0, and 11.5 releases) into the Release 12.x data model. The package provides two categories of services. The first is a set of lightweight date lookups against the compensation period status table, allowing upgrade logic to resolve period start and end dates without embedding redundant SQL. The second is a suite of release-detection functions that interrogate the value of the CN_UPGRADING_FROM_RELEASE profile option to determine the originating release, so that the invoking upgrade routines can branch to the appropriate data-transformation path. In Oracle EBS 12.1.1 and 12.2.2, where the Release 12 compensation schema differs materially from its predecessor, this package remains a reference point for how the upgrade framework identifies legacy periods and legacy release context.
Key Procedures and Functions
- GET_START_DATE — Returns the start date of a given compensation period for a specified operating unit, resolving the record from the period status table. Intended to centralise period-date retrieval for upgrade consumers.
- GET_END_DATE — Companion lookup returning the end date of the specified compensation period, using the same resolution logic as GET_START_DATE.
- IS_RELEASE_11510 — Reports whether the upgrading-from release is 11.5.10, returning a numeric indicator that distinguishes the target release from 10.7, 3i, 11.0 and 11.5, and from invalid release values.
- IS_RELEASE_115 — Indicates whether the source release is 11.5.
- IS_RELEASE_120 — Indicates whether the source release is 12.0.
- IS_RELEASE_107 — Indicates whether the source release is 10.7.
- IS_RELEASE_110 — Indicates whether the source release is 11.0.
- IS_RELEASE_3I — Indicates whether the source release is Release 3i.
- IS_RELEASE_121 — Indicates whether the source release is 12.1.
- CNCMAUPD_R1212 — Upgrade routine associated with the 12.1.2 migration path, processing commission data against the current Release 12 structures.
- CNCMHUPD_R1212 — Companion 12.1.2 upgrade routine for the commission header records.
- CNSRPTXN_R1212 — 12.1.2 upgrade routine for sales-rep transaction data.
Tables Accessed
- CN_PERIOD_STATUSES_ALL — Read by the date-lookup functions to resolve period start and end dates, filtered by period and operating unit.
- FND_PROFILE_OPTIONS and FND_PROFILE_OPTION_VALUES — Read by the release-detection functions to retrieve the value of the CN_UPGRADING_FROM_RELEASE profile option, joined on the Incentive Compensation application identifier and the site-level profile hierarchy.
- CN_COMMISSION_HEADERS_ALL, CN_COMMISSION_LINES_ALL, CN_COMM_LINES_API_ALL — Targeted by the R1212 upgrade routines for commission header, line, and API-line migration.
- CN_SRP_PERIOD_QUOTAS_ALL — Accessed to migrate sales-rep period quota data.
- FND_PRODUCT_GROUPS — Read to establish the installed product/release context for upgrade decisions.
Usage Notes
The package is not exposed through standard EBS forms and is not referenced by any other documented package. It is invoked programmatically by the Incentive Compensation upgrade driver and related concurrent programs during the post-install or post-upgrade phases, predominantly by upgrade AD utilities and the CN migration scripts. The release-detection functions are typically called first to establish which legacy-release branch to follow, after which the appropriate R1212 upgrade routines run against the current compensation tables. Because the functions simply read the CN_UPGRADING_FROM_RELEASE profile value, they return the profile’s state at the moment of execution and assume the profile is set correctly for the migration in progress. Customisations should treat CN_UPGRADE_UTL_PKG as internal infrastructure and avoid direct dependency on it, since its contents are bound to specific upgrade paths and may change between patch levels.