Search Results cs_sr_type_mapping




Overview
Explore in AI Chat

Overview

CS_SR_TYPE_MAPPING is a Service (CS) module table in Oracle E-Business Suite 12.1.1 and 12.2.2 that maps service request types to the responsibilities authorized to create or work with them. It acts as a configuration and security bridge between incident type definitions and the responsibility-based access model of Service Request management, allowing administrators to restrict which users, by responsibility, can raise or view specific request types. The table resides in the CS schema and is classified as VALID in the ETRM repository. In Data Vault terms, the mined foreign-key structure suggests a link classification, since it resolves a many-to-many association between service request types and responsibilities (and, via APPLICATION_ID, the owning application context) rather than storing descriptive attributes.

Key Information Stored

The table contains 33 documented columns, of which the following are the most significant:

The surrogate/business key is enforced by the unique index CS_SR_TYPT_MAPPING_U1 on (INCIDENT_TYPE_ID, RESPONSIBILITY_ID, APPLICATION_ID). The primary key index CS_SR_TYPE_MAPPING_PK is defined on (INCIDENT_TYPE_ID, RESPONSIBILITY_ID).

Common Use Cases and Queries

Typical uses include auditing which responsibilities can access a given request type, troubleshooting "type not available" errors at service request creation, and reporting on the effective-dated mapping configuration. Representative SQL patterns:

  • List responsibilities authorized for a request type:
    SELECT responsibility_id, start_date, end_date, type FROM cs.cs_sr_type_mapping WHERE incident_type_id = :type_id;
  • Resolve the current active mapping by date:
    SELECT * FROM cs.cs_sr_type_mapping WHERE incident_type_id = :type_id AND SYSDATE BETWEEN start_date AND NVL(end_date, SYSDATE+1);
  • Identify seeded versus custom mappings:
    SELECT incident_type_id, responsibility_id, seeded_flag FROM cs.cs_sr_type_mapping WHERE seeded_flag = 'Y';

These queries are valuable in configuration comparisons across environments (dev/test/prod) and in impact analysis before retiring a responsibility or request type.

Related Objects

  • CS_INCIDENT_TYPES_B – joined via INCIDENT_TYPE_ID; the parent definition of service request types.
  • CS_SERVICE_RESPONSIBILITY – joined via RESPONSIBILITY_ID; the responsibility definition within Service.
  • FND_APPLICATION – joined via APPLICATION_ID; identifies the owning application.
  • FND_SECURITY_GROUPS – joined via SECURITY_GROUP_ID; supports security-group-scoped access.
  • CS_SR_STATUS_GROUPS_B – joined via STATUS_GROUP_ID; ties mappings to status group workflows.

Together, these objects form the configuration and access-control backbone for Service Request type and status behavior in Oracle EBS 12.1.1 and 12.2.2.