Results for “cs_incident_urgencies_b”

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

Overview

CS_INCIDENT_URGENCIES_B is a Service (CS) module setup table in Oracle E-Business Suite 12.1.1 and 12.2.2 that stores the non-translated attributes of Service Request urgencies. Urgency is a user-defined classification used to rank the relative priority of service requests and to drive escalation, response-time, and routing behavior within Oracle TeleService and related service flows. Because the "_B" suffix denotes the base or non-translated table, this object holds language-independent seed data such as importance level and display color, while translated descriptive text is maintained in a companion "_TL" table.

Under the heuristic Data Vault classification mined from the foreign key structure, this table is identified as hub-leaning. This suggests modeling the urgency itself as a hub entity, with INCIDENT_URGENCY_ID serving as the durable business key around which descriptive and audit attributes (such as name, importance level, and effective dates) are best modeled as satellite attributes.

Key Information Stored

The table contains 32 documented columns. The most significant are:

• INCIDENT_URGENCY_ID — the surrogate primary key (CS_INCIDENT_URGENCIES_B_PK) and the sole documented unique business-key candidate (CS_INCIDENT_URGENCIES_B_U1). It uniquely identifies each urgency definition.
• NAME — the urgency's display name used in setup and on service request forms.
• DESCRIPTION — longer descriptive text for the urgency.
• IMPORTANCE_LEVEL — a numeric ranking used to order urgencies from highest to lowest, driving prioritization logic.
• SEEDED_FLAG — indicates whether the row is a system-seeded value versus a user-defined one.
• START_DATE_ACTIVE / END_DATE_ACTIVE — effective dating that governs whether the urgency is selectable during a given period.
• DISPLAY_COLOR and RGB_COLOR — presentation attributes controlling how the urgency is color-coded in the UI.
• SECURITY_GROUP_ID — foreign key to FND_SECURITY_GROUPS for multi-org / security group scoping.
• OBJECT_VERSION_NUMBER — optimistic locking column used by the framework (ADF) during concurrent updates.
• CONTEXT and ATTRIBUTE1–ATTRIBUTE15 — the standard DFF (Descriptive Flexfield) column set for customer-specific extension.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — the standard "Who" audit columns.

Common Use Cases and Queries

Service administrators configure urgencies once, and the values are then referenced whenever a service request is created or edited. Reporting typically joins this setup table to transactional incident data to produce counts and response analysis. A common pattern retrieves the active urgency list:

SELECT incident_urgency_id, name, importance_level, display_color
FROM cs_incident_urgencies_b
WHERE TRUNC(SYSDATE) BETWEEN NVL(start_date_active, SYSDATE)
AND NVL(end_date_active, SYSDATE)
ORDER BY importance_level;

A second pattern aggregates service request volume by urgency by joining to the incident table:

SELECT u.name, COUNT(*) cnt
FROM cs_incidents_all_b i, cs_incident_urgencies_b u
WHERE i.incident_urgency_id = u.incident_urgency_id
GROUP BY u.name;

Because DFF attributes and effective dates are present, administrators also query for expiring or inactive urgencies and for rows carrying custom context values.

Related Objects

• CS_INCIDENTS_ALL_B — the primary transactional parent. Its INCIDENT_URGENCY_ID column references CS_INCIDENT_URGENCIES_B, linking each service request to its assigned urgency.
• CS_INCIDENTS_AUDIT_B — the audit shadow of the incident table, also carrying INCIDENT_URGENCY_ID, preserving the urgency value on historical incident records.
• FND_SECURITY_GROUPS — referenced by SECURITY_GROUP_ID, providing the security-group context that scopes the urgency definition.
• CS_INCIDENT_URGENCIES_TL — the translated companion that holds language-specific name and description text keyed by INCIDENT_URGENCY_ID.
• CS_INCIDENT_URGENCIES_VL — the standard "_VL" view that joins the base and translated tables, used by Oracle Forms and OAF pages.
• CS_INCIDENT_URGENCIES_B_U1 — the unique index enforcing the business key on INCIDENT_URGENCY_ID.
• CS_INCIDENT_URGENCIES_B_PK — the primary key constraint backing the same column.

Together these objects form the setup-to-transaction chain by which Service Request urgency classification is defined, applied, translated, and reported across Oracle EBS Service.