Search Results sr_upward_status_propagation




Overview
Explore in AI Chat

Overview

CS_SR_STATUS_PROPAGATION_PKG is a service-specific PL/SQL package body in the Oracle E-Business Suite Service (CS) module. Its core responsibility is the management of status transitions within the Service Request (SR) hierarchy. Specifically, it enforces the business rules that must be satisfied before an SR can be closed and manages the cascading of status changes upward through parent-child SR relationships and associated objects such as tasks, repairs, and work orders.

The package body exposes a single global package name constant, G_PKG_NAME, and marshals the standard Oracle EBS API error-handling conventions: an API version, an initialization message list flag, a commit flag, and the standard return status, message count, and message data OUT parameters. This adherence to the FND_API contract makes the package callable from other PL/SQL units, forms, and concurrent programs without special integration logic.

Key Procedures and Functions

  • VALIDATE_SR_CLOSURE — Validates whether a given service request is eligible for closure. It opens a cursor over CS_ESTIMATE_DETAILS to detect charge lines of type IN_PROGRESS or ACTUAL that are flagged as interfaced to Order Management (interface_to_oe_flag = 'Y') but have not yet been submitted to OM. When such unsubmitted charges exist, it raises the CS_UNSUBMITTED_CHARGES_EXIST exception. A second cursor over JTF_TASKS_B and JTF_TASK_TYPES_B checks for open tasks linked to the SR via source_object_type_code = 'SR', raising CS_OPEN_TASKS_EXIST when any open task is found. The procedure therefore acts as a gatekeeper preventing premature closure of an SR with outstanding downstream work.
  • CLOSE_SR_CHILDREN — Closes the child objects associated with a service request as part of an SR closure operation. Based on the documented table usage, the procedure coordinates closure of dependent records such as tasks, repairs, and work orders rather than allowing them to be orphaned or left in an open state when the parent SR is closed.
  • SR_UPWARD_STATUS_PROPAGATION — The procedure targeted by the search term "sr_upward_status_propagation." It propagates a status change from a service request upward through the SR relationship hierarchy, using AHL_UE_RELATIONSHIPS to resolve parent-child linkages. The procedure ensures that parent service requests reflect the consolidated status of their children and that status roll-up remains consistent across the instance and repair structure.

Tables Accessed

The package reads and writes the following documented APPS synonyms:

  • CS_ESTIMATE_DETAILS — inspected to identify unsubmitted charge lines that block SR closure.
  • JTF_TASKS_B and JTF_TASK_TYPES_B — queried to locate open tasks and their associated task-type rules, enforcing the no-open-tasks closure rule and supporting child task closure.
  • CS_INCIDENTS_ALL_B — the primary SR base table, used to read and update SR status.
  • CS_INCIDENT_STATUSES_B — provides valid status definitions applied during propagation.
  • AHL_UE_RELATIONSHIPS — resolves the upward hierarchy between service requests for status propagation.
  • CSD_REPAIRS, EAM_WO_SERVICE_ASSOCIATION, JTF_RS_RESOURCE_EXTNS — support the closure of repair orders, work order associations, and resource linkages attached to the SR.

Usage Notes

This package is invoked during SR closure and status-update flows, most commonly from the Service Request form or from code triggered through the Business Events / API layer. It is not a concurrent program in its own right but is referenced by two other packages, indicating it is a dependency in the broader CS status-management chain. The standard FND_API parameters allow deployment in custom extensions and workflow code that need to validate closure eligibility or roll a status change up the SR hierarchy. Because it operates on incident, task, and repair data, callers should invoke it within a consistent transaction and control commit behaviour through the p_commit flag. On 12.1.1 and 12.2.2 the object resides in the APPS schema and is classified as a general API supporting Service Request lifecycle management.