Search Results incident_type_name




Overview
Explore in AI Chat

Overview

XNS_INCIDENT_LINKS_V is a reporting view historically shipped within the XNS (Service for Communications) product family in Oracle E-Business Suite 12.1.1 and 12.2.2. It exposes the relationships, or links, that exist between service request incidents, presenting the related service request information for each incident in a denormalized, query-friendly form. The XNS module is documented as obsolete, and the ETRM metadata explicitly records that this view is not implemented in the referenced database. In release 12.2.2 the object carries no documented owner and no documented referenced base objects, reinforcing its status as a legacy artifact retained in the data dictionary for historical or upgrade continuity rather than active use.

The view's functional role is to flatten the parent/child hierarchy defined in the incident link tables so that downstream reports, integrations, or service-desk dashboards can display the counterpart incident (the "other side" of a link) alongside descriptive attributes such as status, incident type, serial number, and owning system. Because the view is defined with a UNION, each stored link appears twice—once oriented from the FROM_INCIDENT_ID and once oriented from the TO_INCIDENT_ID—so that any incident can be queried from its own perspective without the caller needing to know the physical link direction.

Underlying Base Objects

Although the ETRM 12.2.2 metadata documents no referenced base objects, the published view text reveals the underlying tables and views joined by the definition:

The two SELECT branches differ only in link orientation and in the DECODE that reverses the link type ('PARENT' becomes 'CHILD' and vice versa) for the mirrored perspective.

Key Columns

  • ROW_ID — the ROWID of the underlying CS_INCIDENT_LINKS row.
  • FROM_INCIDENT_ID / TO_INCIDENT_ID — the two incidents participating in the link, reoriented per UNION branch.
  • LINK_TYPE — 'CHILD' or 'PARENT', indicating the relationship direction relative to the incident in the FROM position.
  • LINK_ID — the primary-key identifier of the link record.
  • SYSTEM_ID / SYSTEM_NAME — the installed-base system derived from CS_CUSTOMER_PRODUCTS and CS_SYSTEMS; null when no customer product is associated.
  • INCIDENT_STATUS_ID / STATUS_NAME — status code and its translated name.
  • INCIDENT_TYPE_ID / INCIDENT_TYPE_NAME — incident classification and translated label.
  • CURRENT_SERIAL_NUMBER — the serial number captured on the incident.
  • Audit columns — CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN inherited from CS_INCIDENT_LINKS.

Common Use Cases and Queries

Typical usage centers on surfacing the "other" incident in a hierarchy, for example listing all linked incidents for a given service request:

  • Retrieve counterpart incidents: SELECT TO_INCIDENT_ID, LINK_TYPE, STATUS_NAME, INCIDENT_TYPE_NAME, SYSTEM_NAME FROM XNS_INCIDENT_LINKS_V WHERE FROM_INCIDENT_ID = :incident_id;
  • Filter by installed base: add WHERE SYSTEM_NAME = :system to correlate linked incidents to a customer product.
  • Audit link creation: select CREATION_DATE, CREATED_BY, LINK_ID ordered by CREATION_DATE.

Because the metadata confirms the view is obsolete and unimplemented in the referenced database, these queries should be validated against the target instance; where absent, the equivalent logic must be reconstructed directly from CS_INCIDENT_LINKS and the joined incident, product, and lookup tables.