Results for “default_incident_status_id”

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

Overview

CS_SR_STATUS_GROUPS_B is a Service (CS) module table that stores non-translated information about status rules governing service requests. It functions as the master definition table for status groups — logical collections of incident statuses that define the valid lifecycle stages a service request may pass through. Each status group acts as a template that is assigned to one or more incident types, allowing Oracle EBS to enforce consistent, type-specific workflow behavior for service requests.

The table resides in the CS schema and is a core configuration object within the Service Request management framework. It carries 13 documented columns and is uniquely identified by the CS_SR_STATUS_GROUP_B_U1 index on STATUS_GROUP_ID. Based on the foreign key topology mined from the ETRM metadata, the object is classified heuristically as hub-leaning in a Data Vault model. This suggests modeling CS_SR_STATUS_GROUPS_B as a hub entity, with its descriptive attributes (such as DEFAULT_INCIDENT_STATUS_ID, TRANSITION_IND, and date range columns) potentially split into an accompanying satellite for historical tracking.

Key Information Stored

The most significant columns are:

• STATUS_GROUP_ID — The surrogate primary key (CS_SR_STATUS_GROUPS_B_PK), also the unique business-key candidate. It uniquely identifies each status group record.
• DEFAULT_INCIDENT_STATUS_ID — Foreign key to CS_INCIDENT_STATUSES_B, specifying the default incident status applied when a service request is created under this group.
• TRANSITION_IND — A flag indicating whether status transitions are governed or restricted for the group.
• START_DATE / END_DATE — Effective dating that controls the active validity window of the status group definition.
• SECURITY_GROUP_ID — Foreign key to FND_SECURITY_GROUPS, supporting multi-org and data-security partitioning.
• ORIG_SYSTEM_REFERENCE_ID — Reference to the originating system, supporting data migration and integration lineage.
• OBJECT_VERSION_NUMBER — Optimistic locking column used by the Oracle EBS framework to manage concurrent updates.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — Standard EBS audit columns capturing who created and last modified each row.

The translated equivalents (name, description) are not held here; they reside in CS_SR_STATUS_GROUPS_TL, which joins on STATUS_GROUP_ID.

Common Use Cases and Queries

Typical uses include validating which statuses are permitted for a given incident type, driving service request workflow transitions, and reporting on status-group configuration across operating units. A representative query joining the group to its default status and its translated name is:

• SELECT g.status_group_id, t.name, g.default_incident_status_id, g.transition_ind FROM cs_sr_status_groups_b g, cs_sr_status_groups_tl t WHERE g.status_group_id = t.status_group_id AND t.language = USERENV('LANG');

Analysts often join CS_SR_STATUS_GROUPS_B to CS_INCIDENT_TYPES_B to list which incident types reference each status group, or to CS_SR_STATUS_TRANSITIONS to enumerate the allowed status-movement rules. Effective-date filtering (START_DATE/END_DATE) is standard practice when producing point-in-time configuration reports.

Related Objects

The following objects reference or depend on CS_SR_STATUS_GROUPS_B:

• CS_INCIDENT_TYPES_B — joins on STATUS_GROUP_ID; assigns a status group to each incident type.
• CS_SR_ALLOWED_STATUSES — joins on STATUS_GROUP_ID; enumerates statuses permitted within the group.
• CS_SR_STATUS_TRANSITIONS — joins on STATUS_GROUP_ID; defines allowed transition rules between statuses.
• CS_SR_STATUS_GROUPS_TL — joins on STATUS_GROUP_ID; holds translated name and description.
• CS_SR_TYPE_MAPPING — joins on STATUS_GROUP_ID; maps types to status groups.
• CS_INCIDENT_STATUSES_B — referenced via DEFAULT_INCIDENT_STATUS_ID; source of the default status.
• FND_SECURITY_GROUPS — referenced via SECURITY_GROUP_ID for security partitioning.

The base table and its language table are typically exposed through Service Request setup and workflow configuration forms, where status-group membership and transition rules are maintained.