Search Results cs_incident_types_b_uk

Overview

The CS_INCIDENT_TYPES_B table is a core master data table within the Oracle E-Business Suite Service (CS) module, specifically for releases 12.1.1 and 12.2.2. It serves as the foundational repository for defining and managing Service Request (SR) type codes. This table stores the non-translated, seed data attributes for each incident type, which are used to categorize and govern the behavior, workflow, and data validation of service requests throughout their lifecycle. Its role is critical for configuring the SR process, as incident types drive associations with business processes, status groups, cycle steps, and other control entities.

Key Information Stored

The table's structure centers on a unique identifier and key relational columns that link the incident type to other configuration entities. The primary key is INCIDENT_TYPE_ID, a unique system-generated identifier. A significant column is INCIDENT_SUBTYPE, which forms a unique key (CS_INCIDENT_TYPES_B_UK) and typically holds the internal code for the SR type. Other crucial foreign key columns define the type's operational context: BUSINESS_PROCESS_ID links to CS_BUSINESS_PROCESSES, STATUS_GROUP_ID links to CS_SR_STATUS_GROUPS_B for valid status transitions, and PARENT_INCIDENT_TYPE_ID enables a hierarchical structure by self-referencing the table. While the provided metadata does not list descriptive columns like NAME, these are typically stored in the corresponding translated table, CS_INCIDENT_TYPES_TL.

Common Use Cases and Queries

This table is central to setup, reporting, and data validation. Common use cases include configuring new SR types, analyzing SR volumes by type, and validating data integrity. Sample SQL patterns often involve joining to related configuration and transactional tables.

• Listing Active Incident Types with Business Process: SELECT b.INCIDENT_SUBTYPE, bp.PROCESS_NAME FROM CS_INCIDENT_TYPES_B b, CS_BUSINESS_PROCESSES bp WHERE b.BUSINESS_PROCESS_ID = bp.BUSINESS_PROCESS_ID;
• Finding Child Types in a Hierarchy: SELECT CHILD.INCIDENT_SUBTYPE FROM CS_INCIDENT_TYPES_B PARENT, CS_INCIDENT_TYPES_B CHILD WHERE PARENT.INCIDENT_SUBTYPE = 'PARENT_CODE' AND CHILD.PARENT_INCIDENT_TYPE_ID = PARENT.INCIDENT_TYPE_ID;
• Reporting SR Counts by Type: SELECT it.INCIDENT_SUBTYPE, COUNT(i.INCIDENT_ID) FROM CS_INCIDENT_TYPES_B it, CS_INCIDENTS_ALL_B i WHERE it.INCIDENT_TYPE_ID = i.INCIDENT_TYPE_ID GROUP BY it.INCIDENT_SUBTYPE;

Related Objects

As indicated by its extensive foreign key relationships, CS_INCIDENT_TYPES_B is a pivotal reference point for numerous configuration and transactional objects. Key related objects include:

• Primary Transaction Table: CS_INCIDENTS_ALL_B references each SR's type via INCIDENT_TYPE_ID.
• Configuration & Workflow: CS_BUSINESS_PROCESSES, CS_SR_STATUS_GROUPS_B, CS_INCIDENT_CYCLE_STEPS.
• Mapping & Categorization: CS_SR_TYPE_CAT_MAPPINGS, CS_SR_TYPE_ITEMCAT_MAPS, CS_SR_PROB_CODE_MAPPING, CS_SR_RES_CODE_MAPPING.
• Customer Support Customizations: CUG_SR_TYPE_ATTR_MAPS_B, CUG_SR_TYPE_DUP_CHK_INFO.
• Translations: CS_INCIDENT_TYPES_TL (holds language-specific names and descriptions).