Results for “css_def_def_item_vers”

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

Overview

CSS_DEF_DEF_ITEM_VERS is a Support (CSS) module table that associates defects and enhancements with the Product, Component, or Sub-component items and their versions. Within a defect or enhancement record, this table captures both the "Planned" and "Fixed" item/version assignments, allowing support analysts to track which product artifacts a defect affects and in which release the correction was scheduled or delivered. The table is documented as obsolete and explicitly noted as "Not implemented in this database," meaning it will not be physically instantiated in a standard Oracle EBS 12.1.1 or 12.2.2 installation; it appears only where the legacy CSS defect-tracking schema was originally deployed.

Based on the foreign-key structure provided in the metadata, the table exhibits a satellite-leaning Data Vault classification. As a modeling suggestion, this indicates the table behaves as a descriptive satellite hanging off a central defect hub (CSS_DEF_DEFECTS_B) rather than as an independent hub or a pure junction link. Its rows enrich the defect record with version-specific item context, with change history implied by the version-oriented design.

Key Information Stored

The documented metadata identifies a narrow but meaningful set of columns:

• DEF_ITEM_VERSION_ID — the surrogate primary key defined by constraint CSS_DEF_DEF_ITEM_VERS_PK. It uniquely identifies each item/version association row.
• DEFECT_ID — the foreign key to CSS_DEF_DEFECTS_B, tying each row to its parent defect or enhancement record. This is the principal join key and the closest documented business-key candidate for linking back to the defect master.

The description further indicates that rows carry Product, Component, and Sub-component item references together with their versions, and that separate Planned and Fixed variants of each may exist. Those item, component, sub-component, version, and Planned/Fixed attributes are the descriptive payload of the satellite, though individual column names are not enumerated in the supplied metadata. Readers should verify actual column names against the deployed schema in their environment, since the table is not implemented in standard installations.

Common Use Cases and Queries

The primary analytic use case is identifying which product versions a defect affects versus the version in which it was resolved. A representative query joins the satellite to the defect hub:

• SELECT d.DEFECT_ID, v.DEF_ITEM_VERSION_ID FROM CSS_DEF_DEFECTS_B d JOIN CSS_DEF_DEF_ITEM_VERS v ON d.DEFECT_ID = v.DEFECT_ID WHERE d.DEFECT_ID = :p_defect_id;
• Reporting on planned versus fixed versions per defect to measure slip between forecast and actual resolution.
• Impact analysis for a given component or sub-component, listing all defects referencing a specific item version.
• Backing extract queries for defect dashboards or migration scripts that move legacy CSS data into a supported repository, given the table's obsolete status.

Because the table is not implemented in the standard database, these patterns apply to legacy or custom-deployed environments; validate existence before executing.

Related Objects

The most significant relationship, and the only one documented, is:

• CSS_DEF_DEFECTS_B — referenced via CSS_DEF_DEF_ITEM_VERS.DEFECT_ID. This is the parent defect/enhancement hub and the mandatory join path for any query.

Other objects in the CSS defect-tracking family (defect history and item/component definition tables within the same legacy schema) are likely companions, but they are not documented in the supplied metadata and should be confirmed against the specific environment. No public APIs or supported views are documented for this obsolete table.