Search Results cs_incident_links_ext




Overview
Explore in AI Chat

Overview

The CS_INCIDENT_LINKS_EXT table resides in the CS (Service) schema and historically served as the repository for relationships between a service request (incident) and external objects. Its structural role is that of a link table: a heuristic Data Vault classification places it as a link entity that resolves associations between an incident record and an external object, rather than storing descriptive attributes about either side of the relationship. The table retains a full audit column set (creation, update, and WHO columns) alongside a SECURITY_GROUP_ID for multi-org data partitioning and an OBJECT_VERSION_NUMBER for optimistic locking.

The single most important fact about this object concerns its lifecycle. Per Oracle documentation, from Release 11.5.9 onward this table is not used. All incident links, whether SR-to-SR or SR-to-external-object, are consolidated into the CS_INCIDENT_LINKS table. Both Oracle E-Business Suite 12.1.1 and 12.2.2 therefore retain CS_INCIDENT_LINKS_EXT only as a legacy, dormant object; the status remains VALID because the structure persists in the dictionary, but no current application logic writes to it. The primary key is enforced by CS_INCIDENT_LINKS_EXT_PK on LINK_ID, with a unique index CS_INCIDENT_LINKS_EXT_U1 also defined on LINK_ID. The schema comprises 25 columns.

Key Information Stored

The columns below represent the functionally significant content of the table.

  • LINK_ID — Surrogate primary key; the unique business-key candidate per index CS_INCIDENT_LINKS_EXT_U1. Each row carries one distinct link identifier.
  • FROM_INCIDENT_ID — Foreign key to CS_INCIDENTS_ALL_B, identifying the incident that originates the link.
  • TO_OBJECT_ID — Identifier of the object at the far end of the link; referenced through the polymorphic FK relationship documented against TO_OBJECT_ID.
  • TO_OBJECT_TYPE — Foreign key to JTF_OBJECTS_B, qualifying the type of the linked object and enabling the polymorphic reference to resolve correctly.
  • TO_OBJECT_NUMBER — The user-visible number of the target object, complementing the numeric TO_OBJECT_ID.
  • DELETE_FLAG — Logical deletion indicator, permitting soft removal of a link without physical row deletion.
  • SECURITY_GROUP_ID — Foreign key to FND_SECURITY_GROUPS, enforcing multi-org security partitioning of link data.
  • OBJECT_VERSION_NUMBER — Optimistic locking version used by the Oracle framework during concurrent updates.
  • UPGRADED_STATUS_FLAG — Migration marker recording whether the row was processed during the transition of link data into CS_INCIDENT_LINKS.
  • LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — Standard WHO audit columns tracking creation and modification.
  • ATTRIBUTE1 through ATTRIBUTE10, CONTEXT — DFF-enabled descriptive flexfield columns available for customer-defined extensions.

Common Use Cases and Queries

Because the table is dormant from 11.5.9 onward, its practical value in 12.1.1 and 12.2.2 is confined to historical data auditing, data-migration validation, and confirming that no residual rows were left behind after upgrade. Typical investigative query against the legacy structure:

  • Count legacy rows per originating incident: SELECT FROM_INCIDENT_ID, COUNT(*) FROM CS.CS_INCIDENT_LINKS_EXT GROUP BY FROM_INCIDENT_ID;
  • Detect undeleted or unmigrated rows: SELECT LINK_ID, FROM_INCIDENT_ID, TO_OBJECT_TYPE, UPGRADED_STATUS_FLAG FROM CS.CS_INCIDENT_LINKS_EXT WHERE DELETE_FLAG = 'N' OR UPGRADED_STATUS_FLAG IS NULL;
  • Reconcile against the active table by joining LINK_ID to CS_INCIDENT_LINKS to confirm migration completeness.
  • Verify security-group isolation: SELECT SECURITY_GROUP_ID, COUNT(*) FROM CS.CS_INCIDENT_LINKS_EXT GROUP BY SECURITY_GROUP_ID;

For all new reporting on incident linkages, use CS_INCIDENT_LINKS, the supported replacement object.

Related Objects

  • CS_INCIDENT_LINKS — The active successor table holding all SR-to-SR and SR-to-external links since 11.5.9; the primary target of migration reconciliation.
  • CS_INCIDENTS_ALL_B — Referenced via FROM_INCIDENT_ID; supplies incident identity and is the base table for SR master data.
  • JTF_OBJECTS_B — Referenced via TO_OBJECT_TYPE; defines the object-type registry used by the polymorphic target reference.
  • FND_SECURITY_GROUPS — Referenced via SECURITY_GROUP_ID; governs multi-org visibility of link rows.
  • CS_INCIDENTS_ALL_TL — Translation table providing language-specific incident descriptions for joined reporting.
  • CS_INCIDENT_LINKS_EXT_PK / CS_INCIDENT_LINKS_EXT_U1 — Primary key constraint and unique index enforcing LINK_ID integrity.