Results for “css_def_def_attributes”

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

Overview

CSS_DEF_DEF_ATTRIBUTES is an association table within the CSS (Support) product module of Oracle E-Business Suite, historically used by the CRM/Support defect and enhancement tracking subsystem. As documented in the ETRM repository, the table exists to resolve a many-to-many relationship between defect or enhancement records and the tracking attributes applied to them. A single Defect or Enhancement may carry multiple Tracking Groups and/or Environment Variables, and this table records each such association as a discrete row. Tracking Groups are used principally to categorize defects and enhancements for query and reporting purposes, while Environment Variables capture contextual conditions under which a defect or enhancement was observed.

The product module is flagged as obsolete in the metadata, and the table is explicitly noted as "Not implemented in this database." In Oracle EBS 12.1.1 and 12.2.2 environments, this object is therefore typically present only in legacy or upgraded schemas and should be treated as a deprecated artifact rather than an active integration point. Under the heuristic Data Vault classification derived from its foreign key structure, the table models as a link table: it has no independent business identity of its own and exists solely to connect two parent entities.

Key Information Stored

The documented columns of interest are limited but structurally significant:

• DEF_ATTRIBUTE_ID — The surrogate primary key of the row, enforced by the constraint CSS_DEF_DEF_ATTRIBUTES_PK. This is a system-generated identifier with no business meaning and serves only to uniquely identify each association record.
• DEFECT_ID — Foreign key to CSS_DEF_DEFECTS_B, identifying the parent defect or enhancement to which the attribute assignment applies.
• ATTRIBUTE_ID — Foreign key to CSS_DEF_ATTRIBUTES_B, identifying the tracking group or environment variable being assigned to the defect.

No business-key unique index is documented for this table beyond the primary key. The natural uniqueness of the relationship is defined by the combination of DEFECT_ID and ATTRIBUTE_ID, meaning a well-formed row represents one attribute assignment to one defect. The surrogate DEF_ATTRIBUTE_ID should not be treated as a business identifier in downstream reporting.

Common Use Cases and Queries

Because the table is a link entity, the dominant use case is joining defects to their assigned tracking attributes for reporting and analysis. A typical query pattern retrieves all attributes for a given defect:

• Join CSS_DEF_DEF_ATTRIBUTES to CSS_DEF_ATTRIBUTES_B on ATTRIBUTE_ID to return the human-readable attribute name or code for each assignment.
• Join to CSS_DEF_DEFECTS_B on DEFECT_ID to constrain results to a specific defect number, severity, or status.
• Group by ATTRIBUTE_ID to count how many defects or enhancements carry a given tracking group, supporting workload and trend reporting.

Reporting scenarios include defect categorization summaries, environment-variable distribution across open defects, and historical audit of how tracking groups were applied over time. Given the obsolete status of the module, any query written against this table should be validated against the actual 12.1.1 or 12.2.2 schema before deployment, as the underlying Support application may have been replaced by successor functionality.

Related Objects

The table has direct foreign key dependencies on two parent entities and is referenced conceptually as a link between them:

• CSS_DEF_DEFECTS_B — Parent defect/enhancement base table, joined via CSS_DEF_DEF_ATTRIBUTES.DEFECT_ID.
• CSS_DEF_ATTRIBUTES_B — Parent attribute definition base table, joined via CSS_DEF_DEF_ATTRIBUTES.ATTRIBUTE_ID.
• CSS_DEF_DEF_ATTRIBUTES_PK — The primary key constraint on DEF_ATTRIBUTE_ID, which governs row uniqueness and index access paths.

These relationships constitute the documented dependency surface for the object. No additional views, APIs, or concurrent programs are specified in the ETRM excerpt, so integration analysis should focus on the two base tables and the primary key constraint.