Search Results cs_incident_statuses_b_uk

Overview

The CS_INCIDENT_STATUSES_B table is a core reference table within the Oracle E-Business Suite Service (CS) module, specifically for releases 12.1.1 and 12.2.2. It serves as the master repository for all defined Service Request (SR) or Incident status codes. This table stores the non-translated, seed data for statuses, such as 'Open', 'Closed', 'Pending Customer Input', or custom statuses defined during implementation. Its primary role is to provide a controlled list of valid statuses that can be assigned to a service request throughout its lifecycle, ensuring data integrity and enabling workflow and reporting logic based on status changes.

Key Information Stored

The table's structure centers on a unique status identifier and its classification. The primary key is the INCIDENT_STATUS_ID, a numeric sequence that uniquely identifies each status record. A significant column is INCIDENT_SUBTYPE, which is part of a unique key constraint (CS_INCIDENT_STATUSES_B_UK). This column typically categorizes the status, often distinguishing between standard statuses and those used for specific business processes or service request types. While the provided ETRM excerpt does not list all columns, standard practice indicates the table would also contain columns for controlling status behavior, such as flags indicating if a status is a closing status, an active status, or a system status, along with standard WHO columns (CREATION_DATE, CREATED_BY, etc.) for auditing.

Common Use Cases and Queries

This table is fundamental for reporting, data validation, and configuring service request workflows. Common use cases include generating reports on SR volumes by status, defining allowed status transitions in the CS_SR_STATUS_TRANSITIONS table, and validating status changes via application logic or custom code. A typical query to retrieve all active statuses for reporting might be:

• SELECT status.INCIDENT_STATUS_ID, tl.NAME FROM CS_INCIDENT_STATUSES_B status, CS_INCIDENT_STATUSES_TL tl WHERE status.INCIDENT_STATUS_ID = tl.INCIDENT_STATUS_ID AND tl.LANGUAGE = USERENV('LANG');

Another common pattern is joining to the CS_INCIDENTS_ALL_B table to analyze the distribution of service requests:

• SELECT status.INCIDENT_STATUS_ID, COUNT(inc.INCIDENT_ID) FROM CS_INCIDENT_STATUSES_B status, CS_INCIDENTS_ALL_B inc WHERE status.INCIDENT_STATUS_ID = inc.INCIDENT_STATUS_ID GROUP BY status.INCIDENT_STATUS_ID;

Related Objects

As evidenced by its extensive foreign key relationships, CS_INCIDENT_STATUSES_B is a central hub for status-related data. Key related objects include:

• CS_INCIDENT_STATUSES_TL: The corresponding translated table that provides the language-specific name (NAME) for each INCIDENT_STATUS_ID.
• CS_INCIDENTS_ALL_B: The main service request table, which references the current status of each incident.
• CS_SR_STATUS_TRANSITIONS: Defines valid workflow paths by referencing statuses in both FROM_INCIDENT_STATUS_ID and TO_INCIDENT_STATUS_ID columns.
• CS_SR_ALLOWED_STATUSES and CS_SR_STATUS_GROUPS_B: Control which statuses are available for specific SR types or groups.
• CS_INCIDENT_CYCLE_STEPS, CS_SR_ACTION_DETAILS, CS_SR_ACTION_TRIGGERS: Utilize status IDs to configure automated actions and process steps within the service request lifecycle.