Search Results cs_incident_links_ext_s

Overview

The APPS.CS_INCIDENTLINKS_PVT package body is a private (PVT) API in the Oracle E-Business Suite Service (CS) module. It encapsulates the core business logic used to create, maintain, and remove the relationships, or "links," that associate a service incident (service request) with other business entities such as related incidents, orders, contracts, or external objects. These links are surfaced to users through the Service Request relationship and "Related Items" regions in the Service Responsibility and are governed by relationship types defined in CS_SR_LINK_TYPES_B. Because the package is classified as PVT, it is intended to be invoked indirectly by the public CS_INCIDENTLINKS API, internal concurrent processes, workflow activities, and other CS packages rather than by external integrations. The documented metadata confirms its role as a dependency-heavy core package: it depends on multiple CS utilities (CS_INCIDENTLINKS_UTIL, CS_SERVICEREQUEST_UTIL, CS_SR_CHILD_AUDIT_PKG, CS_WF_EVENT_PKG) and on the standard Oracle Application Object Library (AOA) error-handling framework (FND_API, FND_MESSAGE, FND_MSG_PUB, FND_LOG).

Key Procedures and Functions

The 12.2.2 documented metadata lists twelve procedures and functions. The primary maintenance routines are:

• CREATE_INCIDENTLINK — Creates a link between an incident and another object, validating the relationship type and persisting the record.
• UPDATE_INCIDENTLINK — Modifies an existing incident link record.
• DELETE_INCIDENTLINK — Removes an existing incident link.
• GET_DOC_NUMBER — Retrieves the document number associated with a linked entity.
• GET_DOC_DETAILS — Returns the descriptive details of a linked document or object.
• CREATE_INCIDENTLINK_EXT — Creates an extended (attribute-flexfield) link record in the extension table.
• UPDATE_INCIDENTLINK_EXT — Updates an extended link record.
• DELETE_INCIDENTLINK_EXT — Deletes an extended link record.

The remaining documented routines support internal validation, sequence generation, and audit or workflow event publishing that underpins the eight routines above. Parameter lists are not reproduced here.

Tables Accessed

The package reads and writes the following documented tables via APPS synonyms:

• CS_INCIDENT_LINKS — the base transactional table storing incident-to-object links.
• CS_INCIDENT_LINKS_S — the primary key sequence/seed table for link records.
• CS_INCIDENT_LINKS_EXT — the descriptive-flexfield extension table for links.
• CS_INCIDENT_LINKS_EXT_S — the sequence source for the extension table; this is the object users reach when searching for cs_incident_links_ext_s.
• CS_INCIDENTS_ALL_B — validates the parent incident and its operating unit context.
• CS_SR_LINK_TYPES_B — provides valid relationship/link type definitions.
• JTF_OBJECT_PURGE_PARAM_TMP — supports the purge/temporary processing of linked objects.
• DUAL — used for sequence and single-value selections.

Usage Notes

Because it is a PVT package, CS_INCIDENTLINKS_PVT is normally called from the public CS_INCIDENTLINKS API, from the Service Request forms, and from workflow or concurrent purge processes. The metadata indicates it is referenced by four other packages. Custom code should avoid calling the PVT routines directly and instead use the supported public API to preserve validation, audit trail, and workflow-event behavior. The presence of FND_LOG and FND_MSG_PUB dependencies means the package participates in the standard AOL debug logging and message stack, so errors surface through the normal EBS error-handling path.