Search Results status_transition_id

Overview

The CS_SR_STATUS_TRANSITIONS table is a core configuration table within the Oracle E-Business Suite Service (CS) module, specifically for versions 12.1.1 and 12.2.2. It functions as the rule engine for governing valid status changes for service requests (SRs) or incidents. The table does not store transactional history of status changes but instead defines the permissible workflow paths. Its primary role is to enforce business logic by ensuring that users can only transition a service request from its current status to a predefined set of next allowable statuses, thereby maintaining data integrity and process control.

Key Information Stored

The table's structure centers on defining a "from" status and a "to" status within a specific rule context. The primary identifier is the STATUS_TRANSITION_ID. The most critical columns define the rule membership and the status transition path. The STATUS_GROUP_ID links the transition to a specific status rule defined in CS_SR_STATUS_GROUPS_B. The transition itself is defined through two pairs of foreign key columns: one pair references the configuration of allowed statuses (CS_SR_ALLOWED_STATUSES), and the other pair references the master list of incident statuses (CS_INCIDENT_STATUSES_B). This dual-reference design allows for flexible rule definition, tying abstract allowed statuses within a group to concrete system status codes.

Common Use Cases and Queries

The primary use case is the validation of a status change attempt within the Service Request UI or API. When a user attempts to update a service request's status, the application queries this table to verify if the transition from the current status to the target status is permitted under the applicable status rule. Common reporting and diagnostic queries include listing all configured transitions for a specific status group or identifying all permissible "next" statuses for a given current status. A typical SQL pattern would be:

• To find allowable next statuses for status 'Open' in group 100: SELECT cis_to.NAME TO_STATUS FROM CS_SR_STATUS_TRANSITIONS tr, CS_INCIDENT_STATUSES_B cis_from, CS_INCIDENT_STATUSES_B cis_to WHERE tr.FROM_INCIDENT_STATUS_ID = cis_from.INCIDENT_STATUS_ID AND cis_from.NAME = 'Open' AND tr.TO_INCIDENT_STATUS_ID = cis_to.INCIDENT_STATUS_ID AND tr.STATUS_GROUP_ID = 100;
• To audit all transitions defined for a status group: SELECT sg.NAME GROUP_NAME, cis_from.NAME FROM_STATUS, cis_to.NAME TO_STATUS FROM CS_SR_STATUS_TRANSITIONS tr, CS_SR_STATUS_GROUPS_B sg, CS_INCIDENT_STATUSES_B cis_from, CS_INCIDENT_STATUSES_B cis_to WHERE tr.STATUS_GROUP_ID = sg.STATUS_GROUP_ID AND tr.FROM_INCIDENT_STATUS_ID = cis_from.INCIDENT_STATUS_ID AND tr.TO_INCIDENT_STATUS_ID = cis_to.INCIDENT_STATUS_ID ORDER BY 1,2,3;

Related Objects

CS_SR_STATUS_TRANSITIONS is a central hub in the status management schema, with documented foreign key relationships to several key configuration tables. The table references the following objects, as per the provided metadata:

• CS_SR_STATUS_GROUPS_B: Joined via STATUS_GROUP_ID. This is the parent rule grouping.
• CS_SR_ALLOWED_STATUSES: Joined via FROM_ALLOWED_STATUS_ID and TO_ALLOWED_STATUS_ID. These links associate the transition with the configured allowed statuses within a group.
• CS_INCIDENT_STATUSES_B: Joined via FROM_INCIDENT_STATUS_ID and TO_INCIDENT_STATUS_ID. These links map the allowed statuses to the actual system status codes used by service requests.

This table is typically referenced by application logic and possibly by views that expose status workflow rules, rather than having child tables with foreign keys pointing to it.