Search Results create_incidentlink_ext

Overview

CS_INCIDENTLINKS_PVT is a private PL/SQL package in the APPS schema that implements the core business logic for managing incident links in Oracle E-Business Suite Service (TeleService / Field Service) modules. Incident links establish associations between a service request (SR), stored as an incident, and external or internal documents, objects, or related records. The package is classified as a PVT (private) API, meaning it is not intended for direct invocation by external consumers. Instead, it is surfaced through the public wrapper package CS_INCIDENTLINKS_PUB, which enforces the documented public contract. Internally, the private layer performs the validation, DML operations, and error handling required to create, modify, and delete incident link records and their extensions.

The dependency metadata confirms a standard Oracle Application Framework pattern: CS_INCIDENTLINKS_PVT depends on FND_API for the common API error-handling and message-stack utilities, and on SYS.STANDARD for base PL/SQL types. It is referenced by four other packages: CS_INCIDENTLINKS_PUB (the public API), CS_SR_DELETE_UTIL (used during service request deletion), CS_WF_EVENT_PKG (the workflow event package), and IBU_REQ_PKG. This places the package on the critical path of service request lifecycle events, including workflow-driven notifications and record purge/delete processing.

Key Procedures and Functions

The documented interface exposes eight procedures and functions organized around the incident link entity and its extension entity:

• CREATE_INCIDENTLINK — Creates a new incident link record, applying business validation before inserting the base row.
• UPDATE_INCIDENTLINK — Updates attributes of an existing incident link.
• DELETE_INCIDENTLINK — Removes an incident link record, typically invoked during SR deletion or manual unlinking.
• GET_DOC_NUMBER — Retrieves the document number associated with an incident link.
• GET_DOC_DETAILS — Returns descriptive details for the linked document or object.
• CREATE_INCIDENTLINK_EXT — Creates the extension record for an incident link in the extension tables.
• UPDATE_INCIDENTLINK_EXT — Updates the extension record associated with an existing link.
• DELETE_INCIDENTLINK_EXT — Removes the extension record, usually performed alongside the base delete.

Tables Accessed

• CS_INCIDENT_LINKS, CS_INCIDENT_LINKS_S — Base and translated/secure view tables holding the primary incident link rows.
• CS_INCIDENT_LINKS_EXT, CS_INCIDENT_LINKS_EXT_S — Extension tables storing customer-defined or industry-specific link attributes.
• CS_INCIDENTS_ALL_B — The base service request table, used to validate the incident against which the link is created.
• CS_SR_LINK_TYPES_B — Reference table defining valid link types, consulted during validation.
• JTF_OBJECT_PURGE_PARAM_TMP — Temporary purge parameter table used by the object purge framework during cleanup operations.
• DUAL — Used for single-row PL/SQL evaluations.

Usage Notes

Because CS_INCIDENTLINKS_PVT is a private package, it should not be called directly from forms, concurrent programs, or custom extensions. Applications invoke CS_INCIDENTLINKS_PUB, which in turn calls the private procedures to execute the work. The package is also referenced by CS_WF_EVENT_PKG, indicating it participates in workflow event processing for service requests, and by CS_SR_DELETE_UTIL, confirming its role in SR deletion logic. When troubleshooting or extending incident link behavior, developers should trace the public API call into this package and review FND_API error stacks recorded during failure. Direct DML against the underlying tables is strongly discouraged, as it bypasses the validation enforced here.