Search Results css_def_severities_b




Overview
Explore in AI Chat

Overview

The table CSS_DEF_SEVERITIES_B is a core reference data object within the obsolete Oracle E-Business Suite CSS (Support) module. It serves as a master repository for severity codes, which are critical for classifying and prioritizing reported defects and enhancements. The severity level, assigned by the individual filing the issue, provides a standardized measure of the problem's seriousness, directly influencing workflow prioritization and management reporting. As a base table (indicated by the "_B" suffix), it holds the primary transactional data, with its corresponding translatable descriptions typically stored in a related "_TL" table. The metadata explicitly notes this table is "Not implemented in this database," indicating it may be a legacy artifact in many EBS 12.1.1 or 12.2.2 installations, preserved for reference or potential data migration purposes rather than active transactional use.

Key Information Stored

While the full column list is not provided in the excerpt, the structure and primary key definition imply the table's essential data elements. The central column is SEVERITY_ID, which serves as the unique primary key identifier for each severity code. A critical functional column is the SORT_ORDER, explicitly mentioned in the description. This column numerically ranks the severities, enabling consistent ordering in user interface drop-downs and reports—for example, ensuring "Critical" appears before "High." Other expected columns would include fields for the severity code (e.g., SEVERITY_CODE or NAME) and active status indicators. Descriptive, user-facing text for the severity in various languages would be stored in a companion table, CSS_DEF_SEVERITIES_TL.

Common Use Cases and Queries

The primary historical use case was to provide a validated list of severities for defect tracking. Application logic would reference this table to populate lists of values (LOVs) when users created or updated a defect record. Common reporting queries would join this table to defect tables to analyze issue distributions by severity. A typical analytical SQL pattern might be:

  • SELECT s.SEVERITY_CODE, COUNT(d.DEFECT_ID) AS DEFECT_COUNT FROM CSS_DEF_DEFECTS_B d, CSS_DEF_SEVERITIES_B s WHERE d.SEVERITY_ID = s.SEVERITY_ID GROUP BY s.SEVERITY_CODE ORDER BY s.SORT_ORDER;

Given its obsolete status, current use cases are largely limited to historical data analysis, auditing legacy records, or understanding data relationships for potential archival or migration projects.

Related Objects

As defined by the foreign key constraints, CSS_DEF_SEVERITIES_B is referenced by several core defect tracking tables, establishing its role as a key reference entity. The primary related transactional table is CSS_DEF_DEFECTS_B, which stores the defect records themselves and links to a severity via the SEVERITY_ID column. The table CSS_DEF_AUDIT_HISTORY_B also references it, allowing the audit trail to preserve the severity value at the time of a history record's creation. Furthermore, CSS_DEF_RES_TIMES links to this table, suggesting severity may have been a factor in calculating or storing resolution time metrics. For complete application functionality, this base table would work in conjunction with its translation table, CSS_DEF_SEVERITIES_TL, to provide language-specific labels.