Search Results csm_profile_event_pkg




Overview
Explore in AI Chat

Overview

CSM_PROFILE_EVENT_PKG is an Oracle E-Business Suite PL/SQL package owned by the APPS schema and classified as OTHER in the ETRM metadata for release 12.2.2. The package operates within the Service (CSM) product family, specifically supporting the profile-based configuration of the Service module. Its central business purpose is to keep the user-level profile data structures synchronized with the underlying profile option definitions and profile option values managed by the Oracle Application Object Library (FND). This synchronization is necessary because the Service application maintains its own accelerated or cached profile storage — represented by the CSM_PROFILES_ACC_S and CSM_PROFILE_OPTION_VALUES_ACC tables — rather than querying the FND profile tables directly during runtime. When profile option values change, the cached Service-side data must be refreshed so that the Service application applies the correct behavior for each user. The package therefore acts as a maintenance and refresh mechanism that bridges the generic FND profile infrastructure and the Service-specific profile acceleration layer.

Key Procedures and Functions

  • REFRESH_ACC — A public procedure that refreshes the accelerated profile data. It returns a status and a message output, allowing the caller to determine whether the refresh completed successfully and to capture any diagnostic text. This is the primary entry point for a bulk or system-wide refresh operation.
  • REFRESH_USER_ACC — A public procedure that refreshes the accelerated profile data for a single user, identified by a user identifier. It scopes the refresh to one user rather than the entire population, which is useful when a specific user's profile values have changed or when a targeted correction is required.
  • IS_MFS_PROFILE — A public function that evaluates a profile option name and returns a Boolean result indicating whether the named profile option is an MFS (Multi-Funded/Service-related) profile. This function is used internally by the refresh logic to determine which profile options are subject to the special handling performed by this package.

The package spec header dates from 2008 and carries the standard ETRM footprint (version 120.1.12010000.1), indicating that the interface has been stable across the 12.1.1 and 12.2.2 releases.

Tables Accessed

The package reads from and writes to a defined set of APPS synonyms. FND_PROFILE_OPTIONS and FND_PROFILE_OPTION_VALUES provide the authoritative definition and current value of each profile option. CSM_PROFILES_ACC_S and CSM_PROFILE_OPTION_VALUES_ACC are the Service-side accelerated tables that are populated or corrected by the refresh procedures. ASG_USER supplies user identity information needed when refreshing a specific user's records. JTM_CON_REQUEST_DATA supports the concurrent request or interaction context in which the refresh may execute. PLITBLM is the standard PL/SQL indexed table (array) type used for in-memory collection handling during processing. All access is performed through the APPS synonyms, consistent with standard EBS coding practice.

Usage Notes

CSM_PROFILE_EVENT_PKG is not intended for direct end-user invocation. It is typically called when Service profile data requires synchronization — for example, after profile option values are modified in the System Administrator responsibility, or as part of a concurrent program that periodically reconciles the accelerated profile tables. The two documented procedures, REFRESH_ACC and REFRESH_USER_ACC, are the supported API surface, and they are referenced by two other packages within the application, confirming that the package is invoked programmatically by dependent Service logic rather than by forms directly. Customizations should call the documented procedures only and should not reference the internal function or the underlying tables directly, since the accelerated tables are implementation details subject to change. Because the package touches FND profile definitions, callers should ensure that appropriate privileges are held and that refresh operations are scheduled outside peak processing windows to avoid contention on the profile tables.