Results for “css_def_defects_b”

50+ results




Overview
Explore in AI Chat

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

Overview

CSS_DEF_DEFECTS_B is a base table in the Oracle E-Business Suite CSS (Support) product family, historically associated with the defect tracking and quality management functionality delivered through Oracle's Support/CRM module set. Within the ETRM metadata it is explicitly flagged as Obsolete and is documented as "Not implemented in this database," meaning that on Oracle EBS 12.1.1 and 12.2.2 environments where the Support schemas were never provisioned (or were decommissioned), the table may exist only as a residual or non-existent object. Even so, its structure, foreign keys, and downstream dependencies provide a clear picture of a defect (bug) master entity.

From a Data Vault modeling perspective, the heuristic classification for this object is hub-leaning. The primary key, DEFECT_ID, is a surrogate identifier, and the table anchors a large fan-out of dependent child tables that carry descriptive, status, audit, and categorization attributes. A Data Vault practitioner would therefore treat CSS_DEF_DEFECTS_B as a defect hub, with the surrounding CSS_DEF_* child tables acting as satellites and links.

Key Information Stored

The table is centered on the DEFECT_ID surrogate primary key (CSS_DEF_DEFECTS_B_PK). The documented foreign key columns reveal the most significant data elements:

The metadata does not document additional descriptive columns beyond these keys, so business-key candidates cannot be enumerated from the provided source. In practice, practitioners should inspect DBA_IND_COLUMNS for unique indexes to identify natural business keys such as defect number or external reference.

Common Use Cases and Queries

Because the table is obsolete and typically unimplemented, the primary real-world use cases are migration audits, legacy-data reconciliation, and impact analysis of dependent ETRM documentation. A typical inventory query checks for existence:

SELECT table_name, num_rows FROM dba_tables WHERE table_name = 'CSS_DEF_DEFECTS_B';

Analysts reconstructing legacy defect reports join to reference tables to resolve codes into labels, for example joining STATUS_ID, SEVERITY_ID, and PRIORITY_ID to their respective CSS_DEF_*_B lookups, and joining ORIGINATING_CUSTOMER_ID to HZ_PARTIES for customer context. Reporting scenarios include defect aging by STATUS_ID, workload distribution by PHASE_OWNER_ID, and customer-impact analysis through HZ_PARTIES. Because the object is documented as not implemented, any query should be preceded by an existence check against DBA_TABLES and DBA_OBJECTS.

Related Objects

CSS_DEF_DEFECTS_B sits at the center of a substantial dependent cluster. The most significant related tables are:

Collectively, these objects confirm the hub-and-spoke role of CSS_DEF_DEFECTS_B within the legacy CSS Support schema.