Results for “cs_incident_links”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

The CS.CS_INCIDENT_LINKS table is the core relationship store for the Oracle E-Business Suite Service (CS) module. Its design reflects a deliberate choice to model links between Service Requests (incidents) and any other entity recognized by the JTF Objects framework, rather than hard-coding associations to specific products. Because every link row carries an OBJECT_TYPE and SUBJECT_TYPE that resolve to JTF_OBJECTS_B, a single link can tie a Service Request to another Service Request, to a sales order, to a project, or to any custom object registered in the JTF layer. The JTF_OBJECTS_B reference is significant because it is the registry that makes this table extensible: new link targets do not require schema changes.

From a Data Vault modeling perspective, the table is satellite-leaning. It holds descriptive state about a relationship — link type, activation window, object and subject numbers — while its foreign keys (to CS_INCIDENTS_ALL_B, CS_SR_LINK_TYPES_B, and itself) carry the structural relationships. A Data Vault implementation would map the FK pairs to link tables and the descriptive columns to a satellite.

Key Information Stored

The 44 documented columns fall into three functional groups:

• Primary key: LINK_ID is the surrogate PK (CS_INCIDENT_LINKS_PK). A unique index, CS_INCIDENT_LINKS_U1, also exists on LINK_ID, confirming it as the business-key candidate.
• Relationship identifiers: SUBJECT_ID and OBJECT_ID reference the two endpoints of the link, both foreign keys to CS_INCIDENTS_ALL_B; SUBJECT_TYPE and OBJECT_TYPE reference JTF_OBJECTS_B; LINK_TYPE_ID references CS_SR_LINK_TYPES_B; RECIPROCAL_LINK_ID is a self-referencing FK pointing at the mirrored row for bidirectional links. Human-readable counterparts FROM_INCIDENT_NUMBER, TO_INCIDENT_NUMBER, and OBJECT_NUMBER denormalize the numbers for reporting.
• Activation and audit: START_DATE_ACTIVE and END_DATE_ACTIVE define the effective period; standard WHO columns (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, OBJECT_VERSION_NUMBER) and the concurrent program columns (REQUEST_ID, PROGRAM_ID, PROGRAM_APPLICATION_ID, PROGRAM_UPDATE_DATE) support audit and traceability.
• Security: SECURITY_GROUP_ID references FND_SECURITY_GROUPS, enabling multi-org and security-group filtering; SECURITY_GROUP_ID is an important consideration for any query that must respect data isolation.

Common Use Cases and Queries

Typical reporting needs include identifying all Service Requests tied to a given incident, tracing a request-and-response pair via RECIPROCAL_LINK_ID, and filtering links by type or active date range. A common pattern joins the table to itself to resolve the reciprocal side:

SELECT l.LINK_ID, l.FROM_INCIDENT_NUMBER, l.TO_INCIDENT_NUMBER,
       r.LINK_TYPE_ID
FROM   CS.CS_INCIDENT_LINKS l
       JOIN CS.CS_INCIDENT_LINKS r
         ON r.LINK_ID = l.RECIPROCAL_LINK_ID
WHERE  l.FROM_INCIDENT_ID = :incident_id
AND    l.START_DATE_ACTIVE <= SYSDATE
AND    (l.END_DATE_ACTIVE IS NULL OR l.END_DATE_ACTIVE >= SYSDATE);

To discover all objects linked to a Service Request regardless of type, query by SUBJECT_TYPE and join to JTF_OBJECTS_B for the object name. For auditing, filter on CREATION_DATE and CREATED_BY; for purge or expiry reporting, filter on END_DATE_ACTIVE. Because LINK_TYPE_ID is the FK to CS_SR_LINK_TYPES_B, reporting by link category should use that column rather than the legacy LINK_TYPE text column when consistency is required.

Related Objects

• CS_INCIDENTS_ALL_B — parent of OBJECT_ID and SUBJECT_ID; the primary incident master.
• JTF_OBJECTS_B — registry resolving SUBJECT_TYPE and OBJECT_TYPE; central to extensibility.
• CS_SR_LINK_TYPES_B — lookup defining link semantics via LINK_TYPE_ID.
• CS_INCIDENT_LINKS — self-reference via RECIPROCAL_LINK_ID for bidirectional links.
• FND_SECURITY_GROUPS — security-group validation for SECURITY_GROUP_ID.