Search Results cs_incident_links

Overview

The CS_INCIDENT_LINKS table is a core data object within the Oracle E-Business Suite Service (CS) module, specifically for versions 12.1.1 and 12.2.2. It serves as the central repository for managing relationships or associations between Service Requests (incidents) and other entities within the application ecosystem. Its primary role is to store link information when a Service Request is connected to another Service Request or to any other business object defined within the JTF Objects framework. This enables comprehensive tracking of dependencies, related issues, and associated transactions, which is fundamental for service management processes like problem escalation, case grouping, and impact analysis.

Key Information Stored

The table's structure is designed to define a relationship between two entities. The most critical columns include LINK_ID, which serves as the primary key for the link record itself. The OBJECT_ID and OBJECT_TYPE columns together identify the primary object initiating the link, typically the Service Request. Conversely, the SUBJECT_ID and SUBJECT_TYPE columns identify the target or related object, which could be another Service Request or a different entity like a Task, Order, or Opportunity. The LINK_TYPE_ID defines the nature of the relationship (e.g., "Related To," "Duplicated By," "Caused By") by referencing the CS_SR_LINK_TYPES_B table. A sophisticated feature is the RECIPROCAL_LINK_ID, which points to the LINK_ID of the reciprocal or inverse link record, ensuring relationship integrity and enabling bidirectional navigation.

Common Use Cases and Queries

A primary use case is reporting on all linked Service Requests to understand the full scope of a customer issue. For instance, support analysts can identify all duplicate tickets or problems linked to a master case. Common SQL queries involve joining CS_INCIDENT_LINKS with CS_INCIDENTS_ALL_B (for Service Request details) and CS_SR_LINK_TYPES_B (for the link description). A typical pattern to find all links for a specific incident would be:

• SELECT cil.link_type_id, lt.name link_type_name, cil.subject_id, cil.subject_type FROM cs_incident_links cil, cs_sr_link_types_b lt WHERE cil.object_id = :p_incident_id AND cil.object_type = 'SR' AND cil.link_type_id = lt.link_type_id;

This data is also crucial for workflows that automatically create related records or for UI components that display a "Related Items" region on the Service Request form.

Related Objects

The table maintains extensive foreign key relationships, as documented in the ETRM. Its primary integration points are:

• CS_INCIDENTS_ALL_B: Linked twice via (OBJECT_ID) and (SUBJECT_ID) to resolve the Service Request details for both sides of the relationship.
• CS_SR_LINK_TYPES_B: Linked via LINK_TYPE_ID to define the relationship category.
• JTF_OBJECTS_B: Linked twice via (OBJECT_TYPE) and (SUBJECT_TYPE) to validate and describe the types of entities being linked (e.g., 'SR' for Service Request).
• Self-Referential Relationship: The RECIPROCAL_LINK_ID column is a foreign key to the table's own LINK_ID, managing paired, reciprocal links.

These relationships ensure data integrity and are essential for any join query intended to extract meaningful link information with descriptive labels.