Search Results is_sr_open

Overview

CSM_SR_EVENT_PKG is a valid PL/SQL package owned by the APPS schema in Oracle E-Business Suite (12.1.1 and 12.2.2). It forms part of the CSM (Customer Support / Service) layer of the Telecommunications and Service industry solution, where it functions as the central event-handling and service request (SR) processing package. Its primary role is to manage the lifecycle of service requests and their associated child entities — contacts, tasks, item instances, and user events — by exposing "event" and "spawn" routines that create, update, delete, and purge related records across the service request subsystem.

The package is classified under the generic API classification OTHER, indicating it is an internal utility package rather than a formal public API. It depends on SYS.STANDARD and is referenced by a family of sibling event packages (CSM_ITEM_INSTANCE_EVENT_PKG, CSM_SR_CONTACT_EVENT_PKG, CSM_TASK_ASSIGNMENT_EVENT_PKG, CSM_TASK_EVENT_PKG, CSM_USER_EVENT_PKG, and CSM_WF_PKG), confirming its role as a shared event-processing hub. It exposes 18 documented procedures and functions and is referenced by six other packages.

Key Procedures and Functions

The documented routines group into several functional categories:

• Purge / concurrent processing: PURGE_INCIDENTS_CONC is a concurrent-program entry point that removes obsolete service request (incident) data.
• Status and predicate checks: IS_SR_TASK and IS_SR_OPEN evaluate the task nature and open state of a service request; IS_SR_DOWNLOADED_TO_OWNER, IS_TASK_STATUS_DOWNLOADABLE, and IS_ASSGN_STATUS_DOWNLOADABLE determine whether task, assignment, or SR statuses are eligible for download to external or mobile systems.
• Spawn / initialization routines: SPAWN_SR_CONTACTS_INS, SPAWN_SR_CONTACT_DEL, SPAWN_ITEM_INSTANCES_INS, and SPAWN_ITEM_INSTANCES_DEL drive child-record creation and deletion for contacts and item instances triggered by SR events. SR_INS_INIT, SR_DEL_INIT, SR_UPD_INIT, SR_ITEM_INS_INIT, and SR_ITEM_DEL_INIT initialize the insert, delete, update, and item-level processing flows.
• Account/incident accumulation: INCIDENTS_ACC_I and INCIDENTS_ACC_D handle accumulation of incident data on insert and delete.
• Lookup/utility: GET_PROFORMA_INVOICE retrieves proforma invoice information associated with a service request.

Tables Accessed

Through APPS synonyms the package reads and writes core service and install-base tables:

• Incident/SR data: CS_INCIDENTS_ALL_B, CS_INCIDENT_STATUSES_B, CSM_INCIDENTS_ALL_ACC, CSM_QUERY_RESULTS_ACC.
• Install-base (CSI) data: CSI_ITEM_INSTANCES, CSI_II_RELATIONSHIPS, CSI_IEA_VALUES, CSI_I_EXTENDED_ATTRIBS, and their accumulation counterparts CSM_ITEM_INSTANCES_ACC, CSM_II_RELATIONSHIPS_ACC, CSM_CSI_ITEM_ATTR_ACC.
• Customer/contact data: HZ_PARTIES, HZ_LOCATIONS, CS_HZ_SR_CONTACT_POINTS.
• Financial/estimate data: CS_ESTIMATE_DETAILS.

These accesses support SR creation, party/contact resolution, item-instance linkage, extended attribute capture, and estimate/invoice lookups.

Usage Notes

CSM_SR_EVENT_PKG is typically invoked indirectly. Standard user flows through the Service Request forms and the Telecommunications service application raise the events that these routines process; the sibling event packages and CSM_WF_PKG (workflow) call into it during event propagation. Custom extensions, concurrent programs (notably PURGE_INCIDENTS_CONC), and workflow activities may call the predicate functions to gate processing. Because it is an internal, unclassified package, direct calls in custom code should be treated cautiously and validated against the specific patch level.