Results for “css_def_severities_b”

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

Overview

CSS_DEF_SEVERITIES_B is a reference (lookup) table within the Oracle E-Business Suite CSS – Support product family. Its purpose is to store the master list of severities that can be assigned to a Defect or Enhancement. As defined in the object metadata, a Severity indicates the seriousness of a problem as identified by the individual who files the Defect or Enhancement. The table also carries a sort order column that ranks severities relative to one another, ensuring that severity values are presented in a consistent, prioritized sequence wherever they are displayed or reported.

The "_B" suffix follows the Oracle EBS convention denoting a base table (as opposed to the "_TL" translation tables used for multilingual deployments). It is important to note that the ETRM metadata explicitly marks this object as belonging to an obsolete module and states that it is "Not implemented in this database." As a result, in Oracle EBS 12.1.1 and 12.2.2 environments, this table may not exist at all, or may exist only in instances where the legacy Support/Defect tracking components were previously installed.

From a Data Vault modeling perspective, the heuristic classification mined from the foreign key structure is hub-leaning. This is consistent with a reference table that holds a stable, uniquely identified business concept (Severity) referenced by multiple dependent (satellite) tables through its primary key.

Key Information Stored

The documented metadata identifies the following significant attributes:

• SEVERITY_ID — The surrogate primary key, defined by the constraint CSS_DEF_SEVERITIES_B_PK. This column uniquely identifies each severity record and is the column referenced by all foreign keys from dependent tables.
• Sort Order column — Documented as ranking the severities within the reference set. While the metadata names no specific column for this attribute, it is the mechanism that controls the display and reporting sequence of severity values.
• Severity name/description attributes — Implied by the table's role as a severity reference list; these hold the human-readable label and any descriptive text associated with each severity level.

Because the table is a base table intended for translated reference data, business-key candidate columns (unique indexes) may exist beyond the surrogate SEVERITY_ID; the documented metadata surfaces only the primary key constraint. In practice, the natural/business key would be the severity name or code that users see when filing a Defect or Enhancement, while SEVERITY_ID remains the surrogate used for all referential integrity.

Common Use Cases and Queries

Typical usage centers on joining severity labels to defect and enhancement records, and on reporting defect volumes by severity. A representative query pattern is:

• Defect severity listing: SELECT d.DEFECT_ID, s.SEVERITY_NAME FROM CSS_DEF_DEFECTS_B d, CSS_DEF_SEVERITIES_B s WHERE d.SEVERITY_ID = s.SEVERITY_ID ORDER BY s.SORT_ORDER;
• Severity distribution reporting: group defect counts by SEVERITY_ID and join to this table to render human-readable severity labels.
• Audit analysis: join CSS_DEF_AUDIT_HISTORY_B to this table to reproduce the severity that applied at each historical change.
• Resolution time analysis: join CSS_DEF_RES_TIMES to this table to measure average resolution time per severity level.

Because the module is obsolete and the table may be absent, any query referencing it should be validated against the target instance before deployment.

Related Objects

The documented foreign key relationships establish the following dependent objects, each joined on SEVERITY_ID:

• CSS_DEF_DEFECTS_B — references CSS_DEF_SEVERITIES_B.SEVERITY_ID via CSS_DEF_DEFECTS_B.SEVERITY_ID; the primary consumer of severity values.
• CSS_DEF_AUDIT_HISTORY_B — references CSS_DEF_SEVERITIES_B.SEVERITY_ID via CSS_DEF_AUDIT_HISTORY_B.SEVERITY_ID; preserves historical severity changes.
• CSS_DEF_RES_TIMES — references CSS_DEF_SEVERITIES_B.SEVERITY_ID via CSS_DEF_RES_TIMES.SEVERITY_ID; links resolution time expectations to severity levels.

These three tables represent the complete documented dependency set for this reference object, with SEVERITY_ID serving as the universal join column across all relationships.