Results for “incident_type_id”

50+ results




Overview
Explore in AI Chat

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

Overview

CS_SR_TYPE_CAT_MAPPINGS is a Service (CS) module table in Oracle E-Business Suite 12.1.1 and 12.2.2 that stores the mapping information between the service request type and type category. In functional terms, it acts as the association table that links a specific Incident Type to one or more Service Request Type Categories, enabling administrators to organize service request types into logical groupings used throughout the Service Request lifecycle, including templates, routing rules, and categorization hierarchies.

From a dimensional modeling perspective, the heuristic Data Vault classification mined from the foreign key structure identifies this object as a link. This classification is a modeling suggestion: the table sits between two independent business entities (Incident Types and Service Request Type Categories) and resolves a many-to-many relationship, which is characteristic of a link table rather than a hub or satellite. Its composite primary key further reinforces this interpretation.

Key Information Stored

The documented physical schema in ETRM 12.2.2 lists 11 columns under the CS schema. The most significant columns are:

The surrogate/primary key documented is CS_SR_TYPE_CAT_MAPPINGS_PK, defined over (INCIDENT_TYPE_ID, SR_TYPE_CATEGORY_ID). A separate unique index, CS_SR_TYPE_CAT_MAPPINGS_U1, is also defined over (INCIDENT_TYPE_ID, SR_TYPE_CATEGORY_ID), serving as the business-key candidate confirming that a given type-to-category pairing must be unique. Because the primary key is composed of the two foreign key columns, the table carries no independent surrogate identifier column.

Common Use Cases and Queries

Typical uses include reporting on how incident types are categorized, validating configuration during implementation, and driving LOV or hierarchy queries in Service Request setup. A representative join retrieves type names with their categories:

  • SELECT it.name type_name, cat.name category_name, m.start_date, m.end_date FROM cs.cs_sr_type_cat_mappings m, cs.cs_incident_types_b it, cs.cs_sr_type_categories_b cat WHERE m.incident_type_id = it.incident_type_id AND m.sr_type_category_id = cat.sr_type_category_id AND (m.end_date IS NULL OR m.end_date > SYSDATE);
  • A validation query listing mappings without a valid category, or categories with no mapped types, is common during post-upgrade audits.
  • Because START_DATE and END_DATE are present, date-effective filters should be applied when querying active mappings to avoid returning retired associations.

Related Objects

The following objects are most significant in relation to this table, based on the documented foreign key relationships:

  • CS_INCIDENT_TYPES_B — Referenced via CS_SR_TYPE_CAT_MAPPINGS.INCIDENT_TYPE_ID; the parent type master.
  • CS_SR_TYPE_CATEGORIES_B — Referenced via CS_SR_TYPE_CAT_MAPPINGS.SR_TYPE_CATEGORY_ID; the parent category master.
  • CS_INCIDENT_TYPES_TL — Translation table typically joined to CS_INCIDENT_TYPES_B for display names.
  • CS_SR_TYPE_CATEGORIES_TL — Translation table for category display names.
  • CS_INCIDENTS / SR-type base views and Service Request setup UI — Consume these mappings to render category selections during service request creation.