Search Results cs_sr_prob_code_mapping_detail




Overview
Explore in AI Chat

Overview

The CS_SR_PROB_CODE_MAPPING_DETAIL table is a core data object within the Oracle E-Business Suite (EBS) Service (CS) module, specifically in versions 12.1.1 and 12.2.2. It functions as the detailed repository for defining associations between problem codes and specific search criteria. This table is integral to the problem code mapping feature, which enables the system to automatically suggest or assign a problem code to a service request based on the request's attributes, such as incident type and product category. By storing these detailed mapping rules, the table facilitates intelligent, rule-based problem categorization, enhancing the efficiency and consistency of service request logging and analysis.

Key Information Stored

The table's primary purpose is to store the detailed criteria for a problem code mapping rule. Its key columns, as indicated by its foreign key relationships, are the primary identifiers for these criteria. The PROBLEM_MAP_DETAIL_ID column serves as the unique primary key for each mapping detail record. The PROBLEM_MAP_ID column is a foreign key that links the detail record to its parent mapping header in the CS_SR_PROB_CODE_MAPPING table. The detail criteria themselves are stored in the INCIDENT_TYPE_ID column, which references a specific service request type from CS_INCIDENT_TYPES_B, and the CATEGORY_ID column, which references an item category from MTL_CATEGORIES_B. A single mapping rule (PROBLEM_MAP_ID) can have multiple detail records, allowing for complex combinations of incident types and product categories to map to a single problem code.

Common Use Cases and Queries

The primary use case for this table is the runtime and administrative configuration of problem code auto-suggestion. When a user creates or updates a service request, the application can query this table, joined with its parent, to find a matching problem code based on the entered incident type and product category. Administrators use interfaces, likely backed by this table, to define and maintain these mapping rules. Common reporting queries involve analyzing mapping coverage or troubleshooting why certain problem codes are suggested. A typical diagnostic SQL pattern would be:

  • SELECT map.PROBLEM_CODE, detail.INCIDENT_TYPE_ID, detail.CATEGORY_ID FROM CS_SR_PROB_CODE_MAPPING map, CS_SR_PROB_CODE_MAPPING_DETAIL detail WHERE map.PROBLEM_MAP_ID = detail.PROBLEM_MAP_ID;

This retrieves all active mapping rules and their associated criteria for review.

Related Objects

The CS_SR_PROB_CODE_MAPPING_DETAIL table is centrally connected to several key EBS tables through documented foreign key relationships. Its dependencies and associations are as follows:

  • CS_SR_PROB_CODE_MAPPING: This is the parent header table. The DETAIL.PROBLEM_MAP_ID column references the MAPPING.PROBLEM_MAP_ID primary key to link detail criteria to a specific mapping rule.
  • CS_INCIDENT_TYPES_B: The DETAIL.INCIDENT_TYPE_ID column references this table to associate a mapping rule with a specific service request type or incident classification.
  • MTL_CATEGORIES_B: The DETAIL.CATEGORY_ID column references this Inventory table to associate a mapping rule with a specific product or item category.

These relationships ensure data integrity and enable the join logic necessary for the problem code mapping functionality to operate correctly within the Service module.