Search Results cs_incidentlinks_pub




Overview
Explore in AI Chat

Overview

CS_INCIDENTLINKS_PUB is a public PL/SQL API package owned by the APPS schema in Oracle E-Business Suite, classified under the PUB naming convention that designates it as an externally callable, supported interface. Its business purpose is the programmatic maintenance of incident links — the associative relationships that tie a service incident (a customer interaction, service request, or field service issue recorded in Oracle Service / TeleService) to related objects, such as other incidents, notes, or product and asset references. Incident links allow service agents and downstream applications to model dependencies, duplicates, escalations, and cause-and-effect chains across incident records without modifying the base incident rows themselves.

The package is marked VALID in the documented environment and is available in both Oracle EBS 12.1.1 and 12.2.2, where it operates against the same APPS synonyms and follows the standard EBS API architecture layered on FND_API.

Key Procedures and Functions

The ETRM metadata documents ten procedures and functions, organized as a base set and a corresponding _EXT set. The procedures follow the conventional EBS insert/update/delete triad:

  • CREATE_INCIDENTLINK — creates a new link row between an incident and its related record, populating the base incident-links table.
  • UPDATE_INCIDENTLINK — modifies the attributes of an existing incident link, such as link type, status, or descriptive data.
  • DELETE_INCIDENTLINK — logically or physically removes an incident link, terminating the association.
  • CREATE_INCIDENTLINK_EXT — the extension-table variant that creates the link together with its associated _EXT (descriptive flexfield / DFF) attribute rows.
  • UPDATE_INCIDENTLINK_EXT — updates an existing link and its corresponding extension attribute values.
  • DELETE_INCIDENTLINK_EXT — deletes the link along with its extension attribute records.

Consistent with Oracle's public API standard, these routines support caller-controlled commit semantics and return standard FND_API error codes and messages rather than raising unhandled exceptions to the calling application. The dependency listing confirms APPS.FND_API is referenced, which establishes that the package uses the standard API result and message-handling framework.

Tables Accessed

The documented table references are accessed through APPS synonyms:

  • CS_INCIDENT_LINKS — the primary transactional table holding incident-to-object link records; it is the main target of the create, update, and delete operations.
  • CS_INCIDENT_LINKS_EXT — stores descriptive flexfield and extension attributes for each link; maintained by the _EXT procedures and joined to the base link row by the link identifier.
  • CS_INCIDENTS_ALL_B — the base incidents table, referenced to validate that the incident being linked exists and is accessible in the current operating context.
  • DUAL — used for scalar evaluations, sequence or value lookups, and other single-row SQL constructs.

Usage Notes

CS_INCIDENTLINKS_PUB is not an end-user form; it is an integration and extension surface. It is typically invoked from:

  • Concurrent programs and batch processes that build or reconcile incident relationships, including preventive maintenance and product registration flows, as evidenced by the documented referencing packages CSF_PREVENTIVE_MAINTENANCE_PVT and AHL_PRD_DISP_UTIL_PVT.
  • Custom PL/SQL written by implementers who need to create or maintain incident associations from outside the standard Service forms.
  • Wrapper and validation layers such as CS_INCIDENTLINKS_PUB_W, which the repository lists among the four objects referencing this package, indicating a companion validation package is available for callers requiring pre-call checks.

Callers should invoke these APIs only through the public interface, pass a properly initialized FND_API global context, observe the returned result code before committing, and never update CS_INCIDENT_LINKS or CS_INCIDENT_LINKS_EXT directly, since doing so bypasses the validation, extension-attribute maintenance, and error-handling logic that this package provides.