Search Results get_sr_tasks

Overview

The APPS.CS_ERES_INT_PKG package is a PL/SQL integration package within the Oracle E-Business Suite Service (TeleService) module. Its name reflects its primary role: providing an interface layer between the Service Request framework and an external or embedded e-research/approval mechanism. In Oracle EBS 12.1.1 and 12.2.2, this package is validated and classified under the APPS schema with an API classification of OTHER, indicating it is not part of the public, officially supported API surface but rather an internal integration utility.

Functionally, the package supports the lifecycle of Service Requests as they move through an approval or research workflow. It assembles the data associated with a Service Request — notes, tasks, related objects, related Service Requests, and status information — into an XML document, initiates an approval process, and then performs post-approval processing. This design allows Service Requests to be routed through a structured review or approval cycle that may involve external systems or an e-research engine, with the outcome reflected back on the Service Request record.

Key Procedures and Functions

The documented interface exposes nine procedures and functions. Their names indicate the following purposes:

• START_APPROVAL_PROCESS — Initiates the approval workflow for a Service Request, likely seeding the data and triggering the e-research/approval cycle.
• GENERATE_XML_DOCUMENT — Constructs an XML representation of the Service Request and its associated child entities for consumption by the approval or external system.
• POST_APPROVAL_PROCESS — Executes the business logic to be performed after an approval decision has been received, updating the Service Request accordingly.
• POST_APPROVAL_PROCCESS — A variant or legacy spelling of the post-approval routine, retained for backward compatibility.
• GET_TARGET_SR_STATUS — Retrieves the target status that a Service Request should assume following the approval outcome.
• GET_RELATED_OBJS — Returns the list of related objects associated with the Service Request.
• GET_RELATED_SRS — Returns the Service Requests related to the Service Request under processing.
• GET_SR_NOTES — Returns the notes attached to the Service Request.
• GET_SR_TASKS — Returns the tasks associated with the Service Request.

Parameter lists are not documented in the metadata and are therefore not reproduced here.

Tables Accessed

The package reads and writes core TeleService tables through APPS synonyms. The central tables are CS_INCIDENTS_ALL_B and CS_INCIDENTS_ALL_TL, which hold the base and translated Service Request records. Supporting tables include CS_INCIDENT_LINKS for relationships, CS_INCIDENT_STATUSES, CS_INCIDENT_STATUSES_B, and CS_INCIDENT_STATUSES_TL for status resolution, the severity and type lookup tables (CS_INCIDENT_SEVERITIES_B/TL, CS_INCIDENT_TYPES_B/TL), and CS_INCIDENTS_AUDIT_B and CS_INCIDENTS_EXT for audit and extension data. Contact information is drawn from CS_HZ_SR_CONTACT_POINTS, while installed base context comes from CSI_ITEM_INSTANCES and CSI_SYSTEMS_TL. These accesses supply the data required to build the XML document and to determine the correct post-approval status.

Usage Notes

CS_ERES_INT_PKG is referenced by CS_SERVICEREQUEST_PVT, the principal Service Request business logic package, indicating that approval and e-research processing is invoked through the standard Service Request processing flow. It is therefore typically triggered indirectly by Service Request forms, concurrent programs, or custom code that calls the Service Request API, rather than being invoked directly. Because the package is classified as OTHER, it is not a published API; customizations should avoid direct calls and instead rely on the supported Service Request interfaces. Its use is most relevant when approval workflows or external research integration are enabled for Service Requests.