Results for “delete_servicerequest”

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

Overview

CS_SR_DELETE_UTIL is an Oracle EBS service (CS) utility package owned by the APPS schema and classified as a UTIL-type API. It encapsulates the business logic required to remove Service Requests, the transactional records at the heart of the Oracle Service and TeleService modules, together with their dependent contact, extension, and audit data. Rather than allowing direct SQL deletes against the Service Request base tables, Oracle provides this package so that deletion is performed in a controlled, multi-table sequence that preserves referential integrity and maintains the audit trail expected by the Service Request purge model.

The package is a low-level utility rather than a public-facing API. Its procedures are called internally by the Service Request processing layer, most notably by CS_SERVICEREQUEST_PVT, which is the only documented consumer of CS_SR_DELETE_UTIL. Because CS_SR_DELETE_UTIL also references itself, its procedures are designed to be composable, allowing one validation or deletion step to invoke another within the same package. The abbreviated CS_SR prefix identifies it as a Service Request object, and the DELETE_UTIL suffix confirms its exclusive purpose: data removal, not creation or update.

Key Procedures and Functions

The ETRM 12.2.2 metadata documents two procedures for this package:

• DELETE_SR_VALIDATIONS — Performs the prerequisite checks that must pass before a Service Request can be deleted. This procedure centralizes the eligibility rules, ensuring that dependent records, status conditions, and purge constraints are evaluated before any destructive operation begins.
• DELETE_SERVICEREQUEST — Carries out the actual deletion of the Service Request and its associated rows across the incident, contact point, extension, audit, and purge staging tables. It is the operative routine that orchestrates the sequence of deletes described in the following section.

No parameter lists are published in the available metadata and none should be assumed; callers are expected to conform to the signatures defined in the package specification in the APPS schema.

Tables Accessed

Through APPS synonyms, CS_SR_DELETE_UTIL reads and writes a tightly related set of Service Request tables:

• CS_INCIDENTS_ALL_B, CS_INCIDENTS_ALL_TL, CS_INCIDENTS_EXT, CS_INCIDENTS_EXT_TL — the base, translated, and extension tables holding the Service Request header and its descriptive attributes.
• CS_INCIDENTS_AUDIT_B, CS_INCIDENTS_AUDIT_TL, CS_INCIDENTS_EXT_AUDIT, CS_HZ_SR_CONTACT_PNTS_AUDIT, CS_SR_CONTACTS_EXT_AUDIT — the parallel audit (shadow) tables that must be cleaned in step with the base records.
• CS_HZ_SR_CONTACT_POINTS and CS_SR_CONTACTS_EXT — contact point and contact extension data attached to the Service Request.
• CS_INCIDENTS_PURGE_SET_S, CS_INCIDENTS_PURGE_STAGING, CS_INCIDENTS_PURGE_AUDIT_B, CS_INCIDENTS_PURGE_AUDIT_TL — purge staging and purge audit structures that track the deletion lifecycle.

Usage Notes

CS_SR_DELETE_UTIL is an internal utility. In standard configurations it is invoked indirectly through CS_SERVICEREQUEST_PVT, which in turn is driven by the Service Request forms and by Service Request purge concurrent programs. Customers and partners implementing custom purge or archival routines may call the package directly from PL/SQL, but doing so bypasses the encapsulation that the Service Request public API provides. Oracle's recommended approach is to route deletion requests through CS_SERVICEREQUEST_PVT and allow it to delegate to CS_SR_DELETE_UTIL.

The object is reported as VALID in both Oracle EBS 12.1.1 and 12.2.2, and the ETRM metadata is identical across those releases, indicating no signature-level change between them. Because the procedures perform unrecoverable deletes across many tables, they should be executed with the same care as any data-removal operation: in a controlled maintenance window, with validated backups, and with adequate testing against a clone. Its dependence on FND_API and the STANDARD package confirms that normal Oracle EBS error-handling and exception conventions apply.