Search Results csm_sr_contact_event_pkg




Overview
Explore in AI Chat

Overview

The APPS.CSM_SR_CONTACT_EVENT_PKG package is a server-side PL/SQL component within the Oracle E-Business Suite Service (formerly TeleService / Customer Support) module. Its documented status is VALID and it resides in the APPS schema, which is the standard repository for shared application logic in EBS 12.1.1 and 12.2.2. The package is classified as an "OTHER" API, meaning it is not a formal public interface but an internal utility used to coordinate Service Request (SR) contact data with the Workflow event subsystem.

The core business purpose of this package is to detect and propagate changes — specifically "dirty" or modified states — in Service Request contact information, and to generate or react to Oracle Workflow events that notify subscribers when contact data changes. It bridges the transactional SR contact tables with the Workflow Event System, allowing other components (such as CSM_SR_EVENT_PKG and CSM_WF_PKG) to receive notifications when a contact, contact point, or incident-account association is inserted, updated, or deleted. Because it references WF_EVENT_T, the package actively participates in the Workflow event queue rather than merely being a passive data access layer.

Key Procedures and Functions

The ETRM metadata documents six procedures and functions within this package. Their names reveal the functional intent:

  • SR_CNTACT_MDIRTY_I — Marks a Service Request contact record as "dirty" (modified) upon insertion, flagging it for downstream event propagation.
  • SR_CNTACT_MDIRTY_D — Handles the dirty-marking or cleanup logic when a Service Request contact record is deleted.
  • SR_CNTACT_MDIRTY_U_FOREACHUSER — Iterates over each affected user to mark SR contact records as modified during an update. The "FOREACHUSER" suffix indicates a per-user loop, suggesting contact visibility or ownership is user-scoped.
  • SPAWN_USERLOOP_SR_CONTACT_INS — Raises or spawns a per-user Workflow event loop following the insertion of an SR contact, driving event notifications to relevant users.
  • SPAWN_USERLOOP_SR_CONTACT_DEL — The deletion counterpart, spawning a per-user event loop when an SR contact is removed.
  • CONTACT_POINT_UPD_WF_EVENT_SUB — A Workflow event subscription routine that processes contact point update events, likely invoked by the Workflow Event System when a matching event is raised.

No parameter lists are documented in the ETRM excerpt, and none are assumed here.

Tables Accessed

The package references the following tables through APPS synonyms:

  • WF_EVENT_T — The Oracle Workflow event table; used to raise and query events related to SR contact changes.
  • CSM_INCIDENTS_ALL_ACC — Stores incident/account associations; used to identify which accounts are affected by a contact change.
  • CSM_SR_CONTACTS_ACC — The core SR contact association table whose "dirty" state the package maintains.
  • CS_HZ_SR_CONTACT_POINTS — Service Request contact point definitions linking SRs to contact points.
  • HZ_CONTACT_POINTS — The TCA (Trading Community Architecture) contact point repository, holding phone, email, and similar contact data.

Usage Notes

This package is invoked indirectly rather than directly by end users. It is referenced by the CSM_SR_CONTACT_EVENT_PKG itself (recursive/overloaded references), CSM_SR_EVENT_PKG, and CSM_WF_PKG. These are the callers that trigger contact-dirty marking and Workflow event spawning during normal SR maintenance. Practically, the package fires when a user creates, updates, or deletes contact information on a Service Request through the Service Request form or related web UI, or when custom code manipulates CSM_SR_CONTACTS_ACC directly. Since it is classified as an OTHER API, customizations should treat it as internal and unsupported for direct calls; integration developers should instead subscribe to the generated Workflow events. This dependency behavior is consistent across both 12.1.1 and 12.2.2.