Results for “cs_system_sr_links”

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

Overview

CS_SYSTEM_SR_LINKS is a Service (CS) module table within the Oracle E-Business Suite 12.1.1 / 12.2.2 schema owned by CS. It functions as an association table that links service incidents (Service Requests) held in CS_INCIDENTS_ALL_B to the systems or configurations recorded in CS_SYSTEMS_ALL_B. The table therefore records the relationships in which a given system is implicated in a given incident — including field service repair scenarios, installed-base support, and configuration-level tracking of customer problems. The table has been classified by ETRM as VALID in the documented schema, containing 12 columns at the 12.2.2 release, and is secured by a security group (SECURITY_GROUP_ID) that follows the standard Oracle multi-org / security group model used across the CS module.

From a Data Vault modeling perspective, the ETRM heuristic classifies this object as a link. It is best understood as a many-to-many associative entity whose grain is a single system-to-incident association, with the hub references pointed at CS_SYSTEMS_ALL_B and CS_INCIDENTS_ALL_B and attributes such as START_DATE/END_DATE qualifying the temporal validity of the link.

Key Information Stored

The most significant columns captured by CS_SYSTEM_SR_LINKS are:

• SYSTEM_SR_LINK_ID — the surrogate primary key defined by the unique index CS_SYSTEM_SR_LINKS_PK and reinforced by the unique index CS_SYSTEM_SR_LINKS_U1. It is the sole documented business-key candidate.
• INCIDENT_ID — foreign key to CS_INCIDENTS_ALL_B identifying the service request / incident to which the system is tied.
• SYSTEM_ID — foreign key to CS_SYSTEMS_ALL_B identifying the system (installed-base configuration item) associated with the incident.
• START_DATE and END_DATE — effective dating that defines when the system-incident association becomes (and ceases to be) valid, allowing historical reporting of system coverage on incidents.
• SECURITY_GROUP_ID — foreign key to FND_SECURITY_GROUPS, enforcing data-level security consistent with the CS module's multi-org convention.
• OBJECT_VERSION_NUMBER — the standard EBS optimistic-locking column used by the OAF / BC4J framework to detect concurrent updates.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — the standard WHO audit columns tracking who created and last modified each link record and from which login session.

Common Use Cases and Queries

A typical reporting requirement is to enumerate all systems associated with a given incident, or conversely all incidents referencing a particular system. For example:

• List systems on an incident: SELECT l.system_id, s.system_name FROM cs_system_sr_links l, cs_systems_all_b s WHERE l.system_id = s.system_id AND l.incident_id = :p_incident_id AND (l.end_date IS NULL OR l.end_date > SYSDATE);
• Locate all open incidents for a system: SELECT l.incident_id FROM cs_system_sr_links l WHERE l.system_id = :p_system_id AND (l.end_date IS NULL OR l.end_date > SYSDATE);
• Historical trend reports on systems involved in service requests, using START_DATE and END_DATE to define reporting windows.
• Data-quality checks for orphaned links — i.e., rows whose INCIDENT_ID or SYSTEM_ID no longer exists in the parent table — are a common reconciliation task.

Related Objects

• CS_INCIDENTS_ALL_B — parent table for INCIDENT_ID, storing the service request header.
• CS_SYSTEMS_ALL_B — parent table for SYSTEM_ID, storing installed-base systems.
• FND_SECURITY_GROUPS — parent for SECURITY_GROUP_ID, controlling visibility by security group.
• CS_INCIDENTS_ALL_TL — translation table used to report incident titles alongside system links.
• CS_SYSTEMS_ALL_TL — translation table used to report system names alongside incident links.
• CS_INCIDENT_ACTIONS and CS_INCIDENT_NOTES — frequently combined with CS_SYSTEM_SR_LINKS in service-request reporting to provide surrounding context.