Results for “cs_sr_prob_code_mapping”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

The CS_SR_PROB_CODE_MAPPING table is a Service (CS) module reference object within Oracle E-Business Suite 12.1.1 and 12.2.2. It stores the configuration that maps service problem codes to Service Request (SR) incident types and to Inventory items, allowing an organization to control which problem codes, SR types, and products are valid in combination when a service request is created or classified. This routing logic directly influences how an SR is categorized, escalated, and resolved, and which inventory item (product) is associated with the reported issue.

From a dimensional modeling perspective, the mined foreign-key structure suggests a satellite-leaning classification. The table is anchored by its own surrogate key, PROBLEM_MAP_ID, and carries descriptive attributes plus effective-dating columns, which are characteristic of a satellite rather than a pure hub. The 30-column physical schema, owned by the CS schema, is designated VALID in the documented 12.2.2 metadata and is expected to be structurally equivalent in 12.1.1.

Key Information Stored

The table is keyed by the surrogate primary key PROBLEM_MAP_ID, defined through the CS_SR_PROB_CODE_MAPPING_PK constraint and enforced uniquely by the CS_SR_PROB_CODE_MAPPING_U1 unique index. There is no separately documented composite business-key unique index; PROBLEM_MAP_ID functions as the primary unique identifier.

• PROBLEM_MAP_ID — surrogate primary key and unique identifier for each mapping row.
• PROBLEM_CODE — the service problem code being mapped.
• INCIDENT_TYPE_ID — foreign key to CS_INCIDENT_TYPES_B; identifies the SR type associated with the problem code.
• INVENTORY_ITEM_ID — the inventory item (product) tied to the mapping.
• ORGANIZATION_ID — the inventory organization context for the item and mapping.
• CATEGORY_ID — foreign key to MTL_CATEGORIES_B; the item category applied to the mapping.
• START_DATE_ACTIVE and END_DATE_ACTIVE — effective-dating that governs when the mapping is active.
• OBJECT_VERSION_NUMBER — optimistic-locking column used by the OAF/ADF framework.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — standard EBS who-columns for audit and concurrency.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15 — the standard DFF (descriptive flexfield) columns for extensible configuration.

Common Use Cases and Queries

Typical uses include validating problem-code selection in the SR entry flow, driving default SR type from the reported problem, and reporting the set of valid product/problem combinations. Because the table holds both the incident type and the item, a join to CS_INCIDENT_TYPES_B and MTL_CATEGORIES_B is needed to resolve meaningful names.

• Enumerate active mappings for a given SR type:
  SELECT m.PROBLEM_CODE, m.INVENTORY_ITEM_ID, m.CATEGORY_ID FROM cs.cs_sr_prob_code_mapping m WHERE m.INCIDENT_TYPE_ID = :p_type_id AND TRUNC(SYSDATE) BETWEEN NVL(m.START_DATE_ACTIVE, SYSDATE) AND NVL(m.END_DATE_ACTIVE, SYSDATE+1);
• Resolve the SR type name behind a mapping:
  SELECT t.NAME, m.PROBLEM_CODE FROM cs.cs_sr_prob_code_mapping m, cs.cs_incident_types_b t WHERE m.INCIDENT_TYPE_ID = t.INCIDENT_TYPE_ID;
• Report mappings by inventory item and organization, joining MTL_CATEGORIES_B on CATEGORY_ID to display the category name.

Related Objects

The most significant related objects, derived from the documented foreign-key relationships, are:

• CS_INCIDENT_TYPES_B — referenced via CS_SR_PROB_CODE_MAPPING.INCIDENT_TYPE_ID; defines the SR type.
• MTL_CATEGORIES_B — referenced via CS_SR_PROB_CODE_MAPPING.CATEGORY_ID; defines the item category.
• CS_SR_PROB_CODE_MAPPING_DETAIL — child table referencing this table through PROBLEM_MAP_ID, holding the detail/problem-code lines.
• MTL_SYSTEM_ITEMS_B — resolves INVENTORY_ITEM_ID into item names and attributes.
• MTL_PARAMETERS — validates ORGANIZATION_ID against the inventory organization.