Search Results from_incident_id




Overview
Explore in AI Chat

Overview

CS_INCIDENT_LINKS_FROM_V is a read-only dictionary view owned by the APPS schema in Oracle E-Business Suite, defined within the Service (CS) product family. Its functional purpose is to expose every Service Request that has been linked from another Service Request to a given Service Request. In other words, the view reports the inbound side of the incident-linking relationship: for a target SR, it returns the originating SRs and the metadata describing that link.

The view is a reporting and integration aid rather than a transactional object. It flattens the link structure held in the incident link table and enriches it with descriptive attributes such as incident number, summary, severity, status, and document type, so that consumers — concurrent programs, OBIEE/BI Publisher reports, Forms LOVs, or external integrations — do not need to reconstruct the joins themselves. It is marked VALID in the documented ETRM 12.2.2 metadata and is equally applicable to 12.1.1, since the underlying CS incident schema is stable across those releases.

Underlying Base Objects

The view is defined over six APPS synonyms, each resolving to a base table:

The join path is anchored on L.FROM_INCIDENT_ID to INCB.INCIDENT_ID, with the _TL joins constrained by USERENV('LANG') so that names and summaries are returned in the session language.

Key Columns

  • ROW_ID, LINK_ID — unique row identifier and the surrogate key of the link record.
  • FROM_INCIDENT_ID, TO_INCIDENT_ID — the link's direction; FROM is the SR that initiated the link, TO is the target SR.
  • LINK_TYPE — classifies the relationship between the two SRs.
  • DOC_TYPE, DOC_CODE — document classification; DOC_CODE is hard-coded to 'SR' and DOC_TYPE derives from JTF_OBJECTS_TL.
  • DOC_NUMBER, SUMMARY, SEVERITY, STATUS — human-readable attributes of the originating incident.
  • PRODUCT_NUMBER, PRODUCT_DESCRIPTION, PRODUCT_ID — product context. Note that PRODUCT_NUMBER and PRODUCT_DESCRIPTION are returned as NULL literals; only PRODUCT_ID (INCB.INVENTORY_ITEM_ID) is populated.
  • ATTRIBUTE1–ATTRIBUTE10, CONTEXT — descriptive flexfield columns passed through from CS_INCIDENT_LINKS.
  • LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — standard audit (WHO) columns.

Common Use Cases and Queries

Typical applications include incident relationship reports, escalation dashboards, duplicate/related SR analysis, and integration extracts that need the inbound link set for a target SR.

All links targeting a specific SR:

  • SELECT DOC_NUMBER, SUMMARY, LINK_TYPE, SEVERITY, STATUS FROM apps.cs_incident_links_from_v WHERE TO_INCIDENT_ID = :incident_id;

All inbound links created within a date range:

  • SELECT DOC_NUMBER, DOC_CODE, CREATION_DATE FROM apps.cs_incident_links_from_v WHERE CREATION_DATE >= :from_date AND CREATION_DATE < :to_date ORDER BY CREATION_DATE DESC;

Counting inbound relationships per target SR:

  • SELECT TO_INCIDENT_ID, COUNT(*) link_count FROM apps.cs_incident_links_from_v GROUP BY TO_INCIDENT_ID;

Because the view enforces USERENV('LANG') on the translated tables, queries executed under a language lacking the corresponding _TL rows may omit records. Joining to CS_INCIDENT_LINKS directly is preferable when untranslated keys are required, and the complementary outbound perspective is available via the corresponding links-from/to views.