Search Results cs_sr_link_types_b




Overview

The CS_SR_LINK_TYPES_B table is a core master data table within the Oracle E-Business Suite Service (CS) module, specifically for releases 12.1.1 and 12.2.2. It serves as the central repository for defining and managing all valid relationship types between business objects within the service request ecosystem. Its primary role is to govern how service requests (SRs) can be linked to other service requests and to other business entities, such as tasks, orders, or contracts. By providing a controlled list of link types, it ensures data integrity and consistency when creating associations between records, which is fundamental for tracking dependencies, hierarchies, and related issues in a service management context.

Key Information Stored

The table stores the structural definition of each relationship type. The primary identifier is the LINK_TYPE_ID, a unique system-generated key. A critical column is RECIPROCAL_LINK_TYPE_ID, which establishes a self-referential foreign key to another row within the same table. This mechanism allows the definition of bidirectional relationships; for example, a "Parent Of" link type would have a reciprocal "Child Of" link type. Other columns typically include active status indicators, user-defined codes, and creation/modification metadata. As noted in the documentation, the user-facing description or name of the link type is not stored in this base table but is maintained in the translation table, CS_SR_LINK_TYPES_TL, to support multiple languages.

Common Use Cases and Queries

This table is primarily referenced in transactional and configuration contexts. Administrators use it to set up or modify the list of available relationships in the application. Common reporting and validation queries involve joining this table to transactional link tables. For instance, to generate a report of all service request links with their descriptive type names, a typical SQL pattern would join CS_INCIDENT_LINKS to CS_SR_LINK_TYPES_B and its translation table. Another key use case is within the setup of Service Request Action Plans (CS_SR_ACTION_DETAILS) and Triggers (CS_SR_ACTION_TRIGGERS), where specific relationship types can be configured to automatically create follow-up actions. A sample query to list all active link types and their reciprocals is:

  • SELECT lt.LINK_TYPE_ID, tl.MEANING, lt.RECIPROCAL_LINK_TYPE_ID FROM CS_SR_LINK_TYPES_B lt, CS_SR_LINK_TYPES_TL tl WHERE lt.LINK_TYPE_ID = tl.LINK_TYPE_ID AND tl.LANGUAGE = USERENV('LANG');

Related Objects

The CS_SR_LINK_TYPES_B table has extensive relationships with other Service module objects, as documented by its foreign key constraints. It is referenced by the following key tables:

  • CS_INCIDENT_LINKS: The primary transactional table that stores actual links between service requests and other objects, using LINK_TYPE_ID to validate the relationship.
  • CS_SR_ACTION_DETAILS & CS_SR_ACTION_TRIGGERS: These configuration tables use RELATIONSHIP_TYPE_ID to define automated actions based on specific link types.
  • CS_SR_LINK_TYPES_TL: The translation table that provides the descriptive name (MEANING) for each LINK_TYPE_ID.
  • CS_SR_LINK_VALID_OBJ: Likely a validation table that restricts which object types (e.g., SR, Task) can be used with a given link type.
  • Self-Reference: The table references itself via RECIPROCAL_LINK_TYPE_ID to define paired relationship types.