Results for “cs_sr_delete_util”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

CS_SR_DELETE_UTIL is a utility package body owned by the APPS schema in Oracle E-Business Suite, categorized in ETRM as an API of classification UTIL. Its business purpose is to support the deletion (purge) of service request records from the Service (Customer Care / TeleService) module. Service requests span a highly normalized data model: the base incident rows in CS_INCIDENTS_ALL_B and CS_INCIDENTS_ALL_TL, extended attribute rows, contact points, audit records, and related detail tables. A controlled purge must remove or archive all of these related rows in the correct order while respecting foreign keys and audit requirements. CS_SR_DELETE_UTIL encapsulates that logic. It is directly relevant to the seeded concurrent process associated with the CS_INCIDENTS_PURGE_SET_S purge set, which the user searched for, because that purge set identifies the group of service requests to be processed, and CS_SR_DELETE_UTIL performs the validation and deletion work against each set member.

Key Procedures and Functions

ETRM documents two program units in this package body:

• DELETE_SR_VALIDATIONS — Performs validation checks before a service request is deleted. This routine evaluates whether a given service request may be purged, typically by examining dependencies, statuses, and related child records, and returns or raises errors through the FND message/API framework when deletion is not permitted.
• DELETE_SERVICEREQUEST — Executes the actual deletion of a service request and its dependent data. It is the procedural entry point that other purge components (and possibly custom code) call to remove a service request from the incident tables and associated audit, extension, and contact structures.

The metadata does not publish parameter lists, and none are asserted here.

Tables Accessed

The package reads and writes the core incident tables and their satellites. CS_INCIDENTS_ALL_B and CS_INCIDENTS_ALL_TL hold the base and translated service request rows; CS_INCIDENTS_EXT, CS_INCIDENTS_EXT_AUDIT, and CS_INCIDENTS_EXT_TL hold extensible attribute values. Audit history is held in CS_INCIDENTS_AUDIT_B and CS_INCIDENTS_AUDIT_TL, with contact point audit in CS_HZ_SR_CONTACT_PNTS_AUDIT and contact points themselves in CS_HZ_SR_CONTACT_POINTS. Purge-related staging and control data reside in CS_INCIDENTS_PURGE_SET_S, CS_INCIDENTS_PURGE_STAGING, CS_INCIDENTS_PURGE_AUDIT_B, and CS_INCIDENTS_PURGE_AUDIT_TL. Contact extension data is stored in CS_SR_CONTACTS_EXT, CS_SR_CONTACTS_EXT_AUDIT, and CS_SR_CONTACTS_EXT_TL. The package also references supporting packages such as CAC_NOTE_PURGE_PUB, CAC_TASK_PURGE_PUB, JTF_IH_PURGE, IEU_WR_PUB, CS_CHARGE_DETAILS_PVT, and CS_COST_DETAILS_PVT, indicating that notes, tasks, interaction history, and charge/cost details tied to a service request are purged through their respective APIs rather than by direct DML.

Usage Notes

CS_SR_DELETE_UTIL is not referenced by any other database object, so it functions as a leaf-level utility invoked by concurrent processing rather than being called from forms or other packages in the shipped dependency chain. It is typically exercised by the Service Request purge concurrent program that consumes CS_INCIDENTS_PURGE_SET_S to determine which service requests are eligible for deletion. Because it relies on FND_API, FND_MSG_PUB, and FND_LOG, it participates in the standard EBS API error-handling and logging model, and callers should inspect the returned message stack for validation failures surfaced by DELETE_SR_VALIDATIONS. Customizations should not modify the package; instead they should call its documented entry points and honor the same purge set staging conventions.