Search Results get_api_revision




Overview

The APPS.CS_SERVICEREQUEST_PVT package is the private implementation package that underpins Service Request (SR) processing within Oracle E-Business Suite's TeleService and Service modules. It encapsulates the core business logic used to create, modify, delete, and transition service requests — the central customer-service entities tracked through incident records. Because it is classified as a Private (PVT) API object in ETRM, it is intended for internal consumption by Oracle's own Service application, sibling public APIs, and seeded concurrent programs rather than as a supported integration entry point for external developers.

The package also exposes a revision-identification routine, GET_API_REVISION, which allows callers to programmatically determine the version of the API logic in place. This is significant in 12.1.1 and 12.2.2 because patch levels frequently alter SR behavior, and downstream code that depends on the API needs a reliable way to detect which revision is installed at runtime.

Key Procedures and Functions

Tables Accessed

The package operates primarily against the CS_INCIDENTS_* tables. CS_INCIDENTS_ALL_B and CS_INCIDENTS_ALL_TL hold the base and translated incident details; CS_INCIDENTS_S and CS_INCIDENTS_NUMBER_S supply sequence-based numbering; and CS_INCIDENTS_AUDIT_B, CS_INCIDENTS_AUDIT_S1, and CS_INCIDENTS_AUDIT_TL store audit history. Status and type validation draws on CS_INCIDENT_STATUSES_B, CS_INCIDENT_TYPES_B, CS_INCIDENT_TYPES, and CS_INCIDENT_SEVERITIES_B. Transition rules are enforced via CS_SR_STATUS_TRANSITIONS, while CS_SR_TYPE_MAPPING governs type mapping, CS_SERVICE_RESPONSIBILITY supports ownership, and CS_HZ_SR_CONTACT_POINTS links contact data.

Usage Notes

Because this is a PVT package, it is invoked indirectly — through the Service Request public APIs, the TeleService forms, seeded concurrent programs, and internal Oracle code. The metadata records that it is referenced by 34 other packages, confirming its role as a shared internal workhorse. Custom code should generally call the supported public APIs rather than CS_SERVICEREQUEST_PVT directly; where direct use is unavoidable, callers should first check GET_API_REVISION to confirm compatibility with the installed 12.1.1 or 12.2.2 patch level.