Results for “cs_incident_severities_b”

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

Overview

CS_INCIDENT_SEVERITIES_B is a Service (CS) module base table in Oracle E-Business Suite 12.1.1 and 12.2.2 that stores the non-translated (language-independent) definitions of Service Request severities. Severity is the attribute that expresses the operational impact or urgency of a service request, incident, or defect, and this table is the master repository from which users select a severity value when creating or updating a service request. The "_B" suffix designates the base table in the standard Oracle EBS multilingual pair, meaning translated descriptive text resides in a corresponding "_TL" table while this table carries the coded, language-neutral attributes.

The table is owned by the CS schema and is documented in ETRM 12.2.2 with 36 columns. Its primary key, CS_INCIDENT_SEVERITIES_B_PK, is defined on INCIDENT_SEVERITY_ID, and a unique index, CS_INCIDENT_SEVERITY_B_U1, provides the business-key candidate on the same column pair. A heuristic Data Vault classification mined from the foreign-key structure suggests a satellite-leaning profile, since the table holds descriptive and classifying attributes about a core severity entity rather than acting as a hub or a linking table. This classification should be treated as a modeling suggestion, not a contractual definition.

Key Information Stored

The most significant columns in CS_INCIDENT_SEVERITIES_B are:

• INCIDENT_SEVERITY_ID — surrogate primary key and the value referenced by every dependent transaction table.
• NAME — the display name of the severity (for example, Critical, High, Medium, Low).
• DESCRIPTION — extended textual explanation of the severity level.
• INCIDENT_SUBTYPE — participates in the unique index CS_INCIDENT_SEVERITIES_B_UK, allowing severity lists to be scoped by subtype.
• IMPORTANCE_LEVEL — numeric ranking used to order severities relative to one another.
• START_DATE_ACTIVE / END_DATE_ACTIVE — effective-dating window controlling when a severity may be selected.
• SEEDED_FLAG — identifies Oracle-supplied seed data versus customer-defined severities.
• DISPLAY_COLOR / RGB_COLOR — presentation attributes used by Service Request workbenches and dashboards.
• DEFECT_SEVERITY_ID — foreign key mapping the service request severity to a defect severity record.
• PRIORITY_CODE — links the severity tier to priority resolution logic.
• SECURITY_GROUP_ID — foreign key to FND_SECURITY_GROUPS, enforcing multi-org and data-security access control.
• UPGRADED_STATUS_FLAG, OBJECT_VERSION_NUMBER — upgrade and optimistic-locking control columns.
• ATTRIBUTE1–ATTRIBUTE15, CONTEXT — the standard Oracle EBS flexfield descriptor columns for customer extensions.

The surrogate key is INCIDENT_SEVERITY_ID; the documented business-key candidate is the unique index pairing INCIDENT_SEVERITY_ID with INCIDENT_SUBTYPE.

Common Use Cases and Queries

Administrators and implementers query this table to inventory and validate the severity pick-lists presented on the Service Request form. A typical lookup retrieves active severities in ranking order:

• SELECT incident_severity_id, name, importance_level, display_color FROM cs.cs_incident_severities_b WHERE NVL(seeded_flag,'N')='Y' AND SYSDATE BETWEEN NVL(start_date_active, SYSDATE-1) AND NVL(end_date_active, SYSDATE+1) ORDER BY importance_level;

Reporting scenarios commonly join this table to CS_INCIDENTS_ALL_B to count open incidents by severity band, or to BIV summarized materialized views for aging and backlog analytics. Data-security validation joins SECURITY_GROUP_ID to FND_SECURITY_GROUPS to confirm which operating units may reference a given severity. Integration developers also use the table to resolve the DEFECT_SEVERITY_ID mapping when synchronizing service requests with defect tracking.

Related Objects

The following objects are the most significant dependents and references of CS_INCIDENT_SEVERITIES_B:

• CS_INCIDENTS_ALL_B — references this table through INCIDENT_SEVERITY_ID in the FK CS_INCIDENT_SEVERITIES_B → CS_INCIDENTS_ALL_B and is the principal consumer of severity definitions.
• CS_INCIDENTS_AUDIT_B — audit shadow table storing historical severity values for incidents.
• CS_SR_LOAD_BALANCE_WT — assigns service request routing weights by severity.
• OKS_K_LINES_B and OKS_K_LINES_BH — service contract lines that carry an INCIDENT_SEVERITY_ID reference.
• OKS_COV_TXN_GROUPS_INT_ALL — coverage transaction grouping used in contract and entitlement processing.
• BIV_B_AGE_H_SUM_MV, BIV_CLO_SUM_MV, BIV_ACT_SUM_MV, BIV_RES_SUM_MV — Business Intelligence summary materialized views in the Service module that aggregate by severity.
• ISC_FS_009_MV, ISC_FS_011_MV — customer-support fact summary materialized views referencing severity.
• FND_SECURITY_GROUPS — the referenced security group master controlling row-level access.