Search Results hr_all_operating_units
Overview
The CS_SERVICEREQUEST_PVT package body is the private implementation layer of the Oracle E-Business Suite Service (TeleService) module's Service Request application programming interface. It encapsulates the core business logic used to create, update, and manage service requests (also referred to as incidents) within Release 12.1.1 and 12.2.2. The package is owned by the APPS schema and is classified as a Private (PVT) API, meaning it is not intended to be called directly by external consumers. Instead, it is invoked by the corresponding public API wrapper and by other internal Service packages. The package constants reveal its scope: it operates on the CS_INCIDENTS_ALL_B base table, uses the subtype INC (incident) as its default service request classification, and maintains an API revision identified by the constant G_API_REVISION set to 1.0. The header comment dated 2008 shows the package has evolved to include workflow launch and abort handling, reflecting its role in orchestrating the full service request lifecycle, from initial creation through status transitions and auditing.
Key Procedures and Functions
The package exposes nineteen documented procedures and functions, several of which are internal helpers prefixed or scoped for private use. The principal entry points include:
- INITIALIZE_REC — Establishes default record structures and global context values prior to processing.
- CREATE_SERVICEREQUEST — Inserts a new service request into the incidents tables, applying business rules and defaults.
- UPDATE_SERVICEREQUEST — Modifies attributes of an existing service request.
- DELETE_SERVICEREQUEST — Removes or logically deletes a service request.
- UPDATE_STATUS and UPDATE_OWNER — Manage status transitions and ownership reassignment, validating against status transition rules.
- GET_API_REVISION — Returns the API revision number for compatibility checking.
- GET_STATUS_FLAG and GET_PRIMARY_CONTACT — Retrieve derived status and contact information for a request.
- CREATE_AUDIT_RECORD and INITIALIZE_AUDIT_REC — Maintain the audit trail of changes made through the API.
- ADD_LANGUAGE — Populates translated (TL) records for multi-language support.
- LOCK_ROW — Acquires a row-level lock to enforce concurrency control during updates.
- PROCESS_SR_EXT_ATTRS — Processes descriptive flexfield and extensibility attributes attached to a request.
- CREATE_ONETIME_ADDRESS and UPDATE_ONETIME_ADDRESS — Manage one-time (non-reusable) addresses associated with a service request contact.
Tables Accessed
The package reads and writes a well-defined set of tables through APPS synonyms. The primary tables are CS_INCIDENTS_ALL_B (base transactional data) and CS_INCIDENTS_ALL_TL (translated text attributes such as summaries and notes). Supporting reference data is drawn from CS_INCIDENT_TYPES_B, CS_INCIDENT_STATUSES_B, and CS_INCIDENT_SEVERITIES_B, which define valid type, status, and severity values. Sequence CS_INCIDENTS_NUMBER_S supplies incident numbers, while CS_INCIDENTS_S generates primary keys. Audit activity is recorded in CS_INCIDENTS_AUDIT_B, CS_INCIDENTS_AUDIT_S1, and CS_INCIDENTS_AUDIT_TL. Contact point associations are handled via CS_HZ_SR_CONTACT_POINTS, and status transition validation uses CS_SR_STATUS_TRANSITIONS. Additional mapping and responsibility logic references CS_SERVICE_RESPONSIBILITY, CS_SR_TYPE_MAPPING, and CS_INCIDENT_TYPES.
Usage Notes
Because this is a private package, it is invoked indirectly through the public Service Request API, typically from the TeleService agent forms, self-service application flows, concurrent programs that process requests in bulk, and custom extensions that require programmatic control over service request data. The package is referenced by thirty-four other packages, underscoring its central role in the Service module architecture. Note that the search term hr_all_operating_units does not correspond to any table documented for this package; operating unit context is instead handled through the standard Multi-Org and global context mechanisms that the API relies upon during initialization and attribute defaulting.