Search Results cs_sr_res_code_mapping




Overview
Explore in AI Chat

Overview

The CS_SR_RES_CODE_MAPPING table is a core data structure within the Oracle E-Business Suite Service (CS) module, specifically for versions 12.1.1 and 12.2.2. It functions as a master definition table for associating resolution codes with specific search criteria. In the context of service request management, resolution codes are standardized solutions or outcomes applied to closed service incidents. This table stores the high-level mapping criteria, such as the incident type and product category, which define the context for a set of resolution codes. The actual detailed associations between a mapping definition and individual resolution codes are maintained in the related CS_SR_RES_CODE_MAPPING_DETAIL table. Its primary role is to enable the structured and rule-based application of resolution codes during the service request resolution process.

Key Information Stored

The table's structure is designed to define the scope of a resolution code mapping. The primary identifier is the RESOLUTION_MAP_ID, which is the table's primary key. Two critical foreign key columns establish the mapping's context: INCIDENT_TYPE_ID, which references CS_INCIDENT_TYPES_B to link the mapping to a specific type of service incident, and CATEGORY_ID, which references MTL_CATEGORIES_B to associate the mapping with a particular product category. While the provided metadata does not list all columns, typical supporting columns would include creation and last update dates, and the user IDs responsible for those changes, as is standard in Oracle EBS.

Common Use Cases and Queries

The primary use case is the configuration and retrieval of valid resolution codes for a service request based on its attributes. For instance, when an agent is closing a service request for a specific product category and incident type, the application queries this table to find the applicable mapping, then retrieves the list of resolution codes from the detail table. A common reporting need is to audit the configured resolution mappings. A sample SQL query to list all mappings with their associated incident type and category would be:

  • SELECT map.resolution_map_id, type.name incident_type, cat.concatenated_segments category
  • FROM cs.cs_sr_res_code_mapping map,
  • cs.cs_incident_types_b type,
  • inv.mtl_categories_b_kfv cat
  • WHERE map.incident_type_id = type.incident_type_id
  • AND map.category_id = cat.category_id;

Related Objects

CS_SR_RES_CODE_MAPPING is centrally linked to several key objects. It has a direct one-to-many relationship with the CS_SR_RES_CODE_MAPPING_DETAIL table, which holds the specific resolution codes for each mapping. It is constrained by two important reference tables: CS_INCIDENT_TYPES_B, which defines valid incident types, and MTL_CATEGORIES_B from the Inventory module, which defines item categories. The primary key constraint CS_SR_RES_CODE_MAPPING_PK enforces uniqueness on the RESOLUTION_MAP_ID column. In application logic, this table is typically accessed via dedicated service request APIs or user interfaces for configuration, rather than through direct SQL manipulation.