Search Results cp_subcomponent_id




Overview
Explore in AI Chat

Overview

APPS.CS_SYSTEM_SR_LINKS_V is a reporting and integration view in the Oracle E-Business Suite Service (CS) module. It exposes the association between service request (SR) records and the systems and customer products they relate to. In Oracle EBS 12.1.1 and 12.2.2, the CS schema uses this view to present a denormalized picture of SR-to-system linkage, combining incident attributes with system identification and customer product configuration data. The view is registered in FND Design Data under the identifier CS.CS_SYSTEM_SR_LINKS_V, has VALID status, and is owned by the APPS schema. Because it is a view rather than a base table, it offers a stable, read-oriented access path for concurrent programs, Oracle Applications-standard reports, and downstream integrations that need to resolve which system or customer product an SR is tied to. Oracle's standard warning applies: the object is intended for Oracle Applications internal use and is not supported for direct customer access except through standard Oracle Applications programs.

Underlying Base Objects

The ETRM metadata documents the view as being defined over three referenced objects:

  • CS_INCIDENTS_ALL_VL (VIEW) — the language-enabled service request incident view that supplies the core SR fields such as INCIDENT_ID, INCIDENT_NUMBER, status, type, urgency, severity, owner, and summary.
  • CS_SYSTEMS_ALL_VL (SYNONYM) — the system definition source that contributes SYSTEM_ID and related NAME values describing the installed system associated with the SR.
  • CS_SYSTEM_SR_LINKS (SYNONYM) — the linkage entity that stores the relationship between incidents and systems, including the customer product configuration references.

This structure indicates that the view joins incident information to system linkage records, projecting the combined result set. The linkage records drive the customer product columns (CP_COMPONENT_ID, CP_COMPONENT_VERSION_ID, CP_SUBCOMPONENT_ID, CP_SUBCOMPONENT_VERSION_ID, CP_REVISION_ID) and the inventory columns (INVENTORY_ITEM_ID, INV_COMPONENT_ID, INV_ORGANIZATION_ID, INV_ITEM_REVISION), while incident and system attributes come from the incident and system views respectively.

Key Columns

The view exposes a broad set of columns organized around two themes: the service request and the linked system/product configuration. The user's search term, CP_COMPONENT_ID, is the customer product component identifier — the primary key of the component within the customer product configuration that the SR is linked against. It is accompanied by version and subcomponent counterparts:

Common Use Cases and Queries

Typical usage resolves the components linked to service requests for a system, or identifies all SRs tied to a given customer product component. A representative query filtering by component follows:

  • List SRs for a specific customer product component:
    SELECT incident_number, name, summary, cp_component_id, cp_component_version_id, customer_product_id FROM apps.cs_system_sr_links_v WHERE cp_component_id = :component_id;
  • List all linked components for a system's incidents:
    SELECT incident_number, system_id, cp_component_id, inventory_item_id, inv_item_revision FROM apps.cs_system_sr_links_v WHERE system_id = :system_id;
  • Retrieve open SRs by status and component:
    SELECT s.incident_number, s.summary, s.incident_status_id, s.cp_component_id FROM apps.cs_system_sr_links_v s WHERE s.incident_status_id = :status AND s.cp_component_id IS NOT NULL;

These queries support service reporting, component failure analysis, and integration extracts. Because the view is Oracle Internal Use Only, it should be consumed only through supported Applications interfaces or carefully controlled reporting, with attention to the 12.1.1/12.2.2 column definitions and the audit and version columns that enforce data currency.